Hi Theresa and Chloe,
The possibility to use the ID in combination with *-FLD-* or *-SET-* + the usage of the heading- and/or location-fields is a nice work-around. However, the work around has still some disadvantages. Let me explain in an example.
We have some project, where we are interested on exporting particular requirements that live in only some folders in our structure. Therefore, we use a filter to query them (see following picture).
When applying the filter, we have many empty folders that we would need to manage "by hand".
We could use the heading to pick up only the relevant folders, but this is
There are other, more automated work abounds, like reuse the containing structure, then filter on not-relevant-elements, delete them and finally exporting the remaining elements.
If you compare this work around or the usage of Heading with the simple feature (e.g. a standard option on the filter window) of including antecessors on a filter, I think we can all agree that the last option is the more elegant and user-friendly one.
@Jama-team: If you are interested in knowing in detail what we are trying to achieve and why is this feature relevant for our processes, we could make a web-conference.
Side note: I previously worked with rational doors in the automotive industry in my previous firm. There we used this feature (include antecessors) in almost all filters. I would even dare to say that this feature was essential in our systems engineering and specification processes.
Thanks one again in advance for your help.
Hi Chloe – That works (I didn't realize the views worked differently in that respect).
HEADQUARTERS|135 SW Taylor Suite 200, Portland, Oregon, 97204