This filter condition extracts the appliances manufactured by a specific manufacturer, along with additional information selecting all TracesTo relationships that are suspect. The following example shows the results of the filter:
<PRRequirement> <FullTag>PR1</FullTag> <Priority>Medium</Priority> <Status>Incorporated</Status> <TracesTo> <Relationship> <Suspect>true</Suspect> <RelationshipType>Traceability</RelationshipType> <Direction>TracesTo</Direction> <RelationshipID>{10C4D0CE-24CF-4C80-8167-E5A849FC821B}16{10C2D0CE-84CF-4C80-9166-E5A849FC821B}1RelationshipID>{10C2D0CE-84CE-4C80-9166-E5A849FC821B}16{10C2D0CE-84CF-4C80-9166-E5A849FC821B}1</RelationshipID> <RelatedRequirement/> </Relationship> [… More matching relationships] </TracesTo> </PRRequirement>
You can use XPath syntax to retrieve values that are deeper in the hierarchy. However, you may supply only one value for the filter to evaluate. If you supply multiple values, the expression is considered undefined. For example, the PRRequirement has a related document. This is defined in the schema as xs:element with a maxOccurs of 1 and a minOccurs of 0:
xs:element maxOccurs="1" name="Document" type="ReqDocument" minOccurs="0".
Because there can never be more than one related document, the expression can be evaluated. If there is no related document, there is no match. The fields expression for the multi-path setting is:
fields=Project/Requirements/PRRequirement[Document/Extension=prd]/(*|Document/*.