-
Key: PLM2-21
-
Legacy Issue Number: 11218
-
Status: closed
-
Source: PROSTEP AG ( Guido Adolphi)
-
Summary:
PLM Services 2.0, mantis/07-03-01 Update, Chapter 9.7.45 and Figure 9.61 Cause: The Conditional_query has no relationships to Location_step but to PLM_query. The Location_path instances are missing as glue between the instances of Conditional_query and Location_step. Furthermore, Location_step instance inverse_item_classification_hierarchy_step wants to select elements by the no named relationship related (denoted by role_name="related") from Specific_item_classification_hierarchy elements. However, Specific_item_classification_hierarchy only provides the named relationship sub_classification. New Specification Text: In figure 9.61 two Location_path instances have to be included each referencing one of the existing Location_step instances. The Conditional_query instance equivalent_query_instance has to refer to the new Location_path instances instead. In Location_step instance inverse_item_classification_hierarchy_step the attribute role_name has to be set sub_classification.
-
Reported: PLM 1.0.1 — Fri, 27 Jul 2007 04:00 GMT
-
Disposition: Resolved — PLM 2.0b2
-
Disposition Summary:
In figure 9.61 two Location_path instances have to be included each referencing one of the existing Location_step instances. The Conditional_query instance equivalent_query_instance has to refer to the new Location_path instances instead. In Location_step instance inverse_item_classification_hierarchy_step the attribute role_name has to be set sub_classification.
-
Updated: Fri, 6 Mar 2015 20:58 GMT
PLM2 — Item_classification_hierarchy_query Reference
- Key: PLM2-21
- OMG Task Force: PLM Services V2.0 FTF