• WTDocument, WTDocumentMaster, and EPMDocument are only affected if the relevant Windchill ESI RPC supports documents and if the Windchill ESI RPC invocation requests that documents be included. Windchill ESI RPCs GetPart, GetBOM and GetECN do support documents.

• Attributes described in the table as “modeled” attributes are presumed to have public getter methods.

• Non-mapped attributes are not included in the Windchill ESI Open API RPC responses.

• Windchill ESI uses the Windchill Adapter Query-Object webject to obtain all the attributes of parts and part master objects. As long as the Query-Object webject returns the attribute, that attribute is available to Windchill ESI mapping logic.

• Windchill WTPart objects are related to WTPartMaster objects by a complex relationship that is defined by the Windchill code generation tool. The relationship is central to product structure navigation and to the release of parts by Windchill ESI. Changing the relationships will disrupt Windchill ESI logic. These are the kinds of modifications that require java coding to repair the disruption of Windchill ESI logic:

◦ Replacing the existing relationship implementation with a link class

◦ Creating a new object, extending WTPart, that disrupts the inherited relationship to WTPartMaster

◦ Creating a new object, extending WTPartMaster, that disrupts the inherited relationship to WTPart

• The properties define the name of the part class and the part master class. If these property values are changed, then it will only be possible to release the extension objects identified by the values. The GetPart RPC will no longer support WTPart and/or WTPartMaster.

• The properties define the name of the part class and the part master class. If these property values are changed, then it will only be possible to release the extension objects identified by the values. The GetPart RPC will no longer support WTPart and/or WTPartMaster.

• Declare the document soft type.

• The Windchill ESI GetPart RPC will still support for WTPart and WTPartMaster in this case.

• In this category extensions do not include soft types. Adding a new soft type document is a configuration option. See above

• GetPart, GetBOM and GetECN could be customized in this case, but such a customization would be vulnerable to future ESI DSU maintenance. A custom RPC is a safer choice.

• For example, modifying the part alternate relationship.

• Although the above table lists only use cases pertaining to parts, BOMs, change notices and associated documents, use cases on exactly similar lines are also possible with standalone documents (in both object-centric and CN-centric modes), promotion requests and all of the MPMLink objects that are supported – viz., process plans and resources such as tooling, process materials and skills. The relevant RPCs for these objects would be GetDocument, GetPromotionRequest, GetProcessPlan and GetResource, and the affected objects would be WTDocument, EPMDocument, PromotionNotice, MPMProcessPlan, MPMSequence, MPMOperation, MPMTooling, MPMProcessMaterial and MPMSkill among others.

• By GetXXX PRC is meant the getXXX() API of the concrete implementation of ESIService (StandardESIService by default).

• The contents of the Relevant Event column in the table simply refer to the user action that triggers the publication (for example, setting the lifecycle state of an object to Released). It is important to be aware that no event is emitted by ESI services and passed to the EAI software components upon triggering the publication of an object; instead, ESI services proceed to generate the ESI response directly and hand it over to the EAI software components.