Hi Simon,
When I talked about parents it was in an inheritance kind of way, rather than element heirarchy.
However, reading your reply - it has dawned on my why it isn't working.
I'm trying to filter out Activity and BusinessProcess elements, but not ActivityPartition elements. If I filter Activity I don't get anything.
This is because the fragment is being called from an activity and therefore is being filtered out before it get's chance to find the child elemenets.
I have the "Include child elements even if the parent element is filtered out" ticked, but that doesn't seem to do anything.
So, the fragment is called in an activity, but I want to process the children that are ActivityPartitions. However, I can't call a template from within Child Elements, just within Element.
This is connected with my query about skipping heading levels previously - I'm trying to generate a document which refers to the pools and lanes, but doesn't make them part of the heirarchy - there would just be too many levels.
So if my tree looks like this...
Activity A
|--Pool X
| |--Lane Y
| | |--Activity B
| |--Lane Z
| | |--Business Process C
| | | |--Pool Q...
What I'm trying to get is
1. Activity A
Pool - X (ActivityPartition only fragment)
Lane - Y (ActivityPartition only fragment)
Activity B (Fragment called from ActivityPartition Fragment)
Lane - Z (ActivityPartition only fragment)
Business Process C
1.1 Activity B
...
1.2 Business Process C
Pool - Q...
I therefore want to produce a second summary heirarchy using the pools and lanes, and then ignore the pools and lanes in the main hierarchy.
If I filter ActivityPartition in the main document, I don't get any of the child activities, even with the "Include child elements..." checkbox ticked.
I'm sure theres a logic to how the "Include child elements..." checkbox works, but I don't understand it.
I realise that I'm trying to subvert the heirarchy, but I thought I'd be able to do that using fragments.
Thanks!