Summary of Changes for Windchill REST Services 2.2
Changes in Windchill REST Services .2.2 are described in this section.
General Capabilities
• Introduced telemetry support for Windchill REST Services.
◦ Starting in Windchill 12.0.2.0, data will be collected on Windchill REST Services requests.
◦ Request URL, status code are primary artifacts; sensitive user data is scrubbed from the URLs.
• The annotation PTC.Capability is deprecated in WRS 2.2 and replaced by PTC.Capabilities that has entries for Workable and Reservable entities.
• Included support for single argument isof() filter function.
• Domain validation now can include request information, supporting a model for backend-for-frontend (BFF) client development internally.
• Updated documentation to include a section on authorizing WRS in an OAuth environment.
• Added an additionalInfo map on EntityProcessorData for domain authors to use during processing.
• Updated framework to be compatible with version 2 of Log4J library, while maintaining compatibility with previous streams using version 1 of library.
• Improved catalog handling of actions which create entities.
• Generated entities now inherit the PTC.Operation annotation from their base entity type.
• Fixed issue where $orderby was not processed on requests which were custom actions or where processors acquired the data on their own rather than through search layer.
• Reference attribute properties are now marked as read only to communicate they cannot be updated.
Updates to the Change Management Domain
There are several updates to the Change Management domain:
• The AffectedObjects navigation for Problem Reports, Variances, Change Requests, and Change Tasks now includes the following information:
◦ The defined model and soft attributes on the link.
◦ A URL for the changeable object in its native domain.
• The Resulting Objects navigation and the Unincorporated Objects navigation for Change Tasks now includes the following information:
◦ The defined model and soft attributes on the link.
◦ A URL for the changeable object in its native domain.
• A stand-alone Problem Report and Variance can be created with defined model and soft attributes
• A stand-alone Change Notice with associated Change Tasks can be created.
• An existing Problem Report and Variance can be modified with the following information:
◦ The defined model and soft attributes can be modified
◦ An “Affected Object” can be added
◦ The “Affected Object” link attributes can be modified
• An existing Change Request can be modified with the following information:
◦ The defined model and soft attributes can be modified.
• An existing Change Notice can be modified with the following information:
◦ The defined model and soft attributes can be modified
◦ A New Change Task can be created with the defined model and soft attributes
• An existing Change Task can be modified with the following information:
◦ The defined model and soft attributes can be modified.
◦ An Affected Object can be added with corresponding model and soft link attributes.
◦ The Affected Object link model and soft attributes can be modified.
◦ A Resulting Object can be added with corresponding model and soft link attributes.
◦ The Resulting Object link model and soft attributes can be modified.
• An attachment can be added, removed, or have attributes modified for an existing Problem Report, Variance, Change Request, or Change Notice.
• The following services for Pending Effectivities are supported:
◦ The Pending Effectivities for a Resulting Object can be obtained.
◦ A Pending Effectivity for a Resulting Object can be created.
◦ A Pending Effectivity for a Resulting Object can be deleted.
◦ The attributes of an existing Pending Effectivity can be modified.
• The following supporting services have been added for all Change Management objects:
◦ Submit a Change Management object into its workflow.
◦ A Change Management object can be reserved, have its reservation released, and check the status of the reservation.
◦ Get the Affected Object and Resulting Object link types to use for the Change Management object.
Added Functionality to MPMLink
Manufacturing Process Management domain is enhanced with APIs for managing Work Center or Resource allocation to an Operation.
QMS Capability Added
CAPA and NC domains has enhanced their capability to support API’s for managing Part Instances under Affected Objects table.