PLM — chapter 8.9 (Query Type),

in document mantis/04-04-05 from the PLM Services 1.0 specification, chapter 8.9 (Query Type), the behavior a next_query concerning the exact scope of elements applying to it should be precised, for example as following: 'ALL objects which were used as start nodes for the predecessor query, plus ALL the objects selected by the predecessor query, including those objects enclosed through the multiplicity conditions (in the sense of Issue #7883), build the start nodes set for the Next_query.' Because of performance reasons, it should however be possible to restrict this start nodes set to some object types. For example a design_discipline_item_definition_query returns instances of item, item_version and ddid. Each of these objects may be referenced by a person_organization_assignment. A Next_query Associated_organization_query would return the person_organization_assignments of all organizations associated to the item(s), the item_version(s) as well as the ddid(s) => it should be possible to restrict the scope to the item_version(s), for example. An alternative would be to restrict implicitly the scope by replacing the above statement by: 'Only the objects selected by the predecessor query (not the ones which were used as start nodes for the predecessor query, nor the objects enclosed through the multiplicity conditions (in the sense of Issue #7883)), build the start nodes set for the Next_query.' In this case, the Associated_organization_query would be mentioned (if wished) explicitly in each predecessor query. Regards,

No Data Available