-
Key: PLM2_-1
-
Legacy Issue Number: 11624
-
Status: closed
-
Source: T-Systems Enterprise Services ( Hirel, Guillaume)
-
Summary:
The parameters Add_period, Add_start_definition and Add_end_definition are missing (refer to the WSDL). Add_concerned_organization should be also added as parameter and in the WSDL. More generally, the handling of WSDL-Attribute of kind: type="xsd:IDREFS" minOccurs="0" is not handled in an homogen way throughout the specification: . some of them are retrieved by a dedicated specific_query (for example work_request_scope_query) . some of them are retrieved automatically when the object is retrieved (for example Associated_aproval_query always retrieve is_approved_by and scope) . some of them are retrieved if some parameter of kind add_... is set to TRUE (for example in effectivity_query) . some of them are not retrieved at all, since they are not handled in the 3 ways described above. These are for example: activity.concerned_organization activity.supplying_organization cartesian_coordinate_space.unit_of_values ddid.additional_context document_property.languages document_file.external_id_and_location product_component.is_influenced_by product_component.is_relevant_for product_function.is_relevant_for property.allowed_unit work_request.notified_person Proposal: define add_parameter (analog to effectivity_query) for simple objects which do not imply the retrieval of too many objects. For the other ones: define a dedicated specific query that may be combined with further queries to complete the result
-
Reported: PLM 2.0b2 — Fri, 19 Oct 2007 04:00 GMT
-
Disposition: Resolved — PLM 2.0
-
Disposition Summary:
Add the requested three attributes Add_period, Add_start_definition and Add_end_definition to the signature of the Effectivity_query.
-
Updated: Sat, 7 Mar 2015 03:31 GMT