• Scheduling of jobs from the Windchill side. This integration is designed to perform all job initiation from Creo Elements/Direct Model Manager. For more information, see User-Driven Publishing and Rule-Driven Publishing.

• Initiating certain changes in objects from the Windchill side. Because publishing with Windchill Gateway for Creo Elements/Direct Model Manager is unidirectional, care must be taken not to overwrite in Windchill data that is published from Creo Elements/Direct Model Manager. On the Windchill side, you can add to the data published from Creo Elements/Direct Model Manager, but need to avoid changes that can cause publishing errors or data loss of Windchill-side generated values, which may be overwritten by the next publishing update from Creo Elements/Direct Model Manager. The following items are precautions to observe when modifying objects in Windchill published by the Windchill Gateway for Creo Elements/Direct Model Manager

◦ When adding attachments to MMModel or MMDrawing documents in Windchill, avoid naming attachments starting with the model or drawing name; otherwise, these attachments will not be honored in the next iteration. Avoid customizing the default naming format of file attachments in Creo Elements/Direct Model Manager.

◦ Avoid adding an .mmlf file as an attachment for MMModel and MMDrawing documents in Windchill; otherwise, the attachments created in Windchill will not be honored in subsequent iteration.

◦ Avoid modifying ‘Described By’ and ‘Describes’ relations for MMParts and MMDocuments published from Creo Elements/Direct Model Manager in Windchill. In case of conflict, the modification coming from Creo Elements/Direct Model Manager will prevail.

◦ Publishing of masterdata from Creo Elements/Direct Model Manager always goes to the MMPart revision that matches the masterdata version in Creo Elements/Direct Model Manager. Do not revise MMModel or MMDrawing documents in Windchill. If a user revises an MMPart in Windchill, the masterdata for the MMpart present in Creo Elements/Direct Model Manager must also be revised simultaneously to keep the revisions in sync. Otherwise, in further publishing, only the latest revision sent fromCreo Elements/Direct Model Manager will be updated in Windchill.

◦ The property, IteratePartOnNewDocumentIteration, present in GatewayConfig.xml should not be set to ‘false.’ (Leave it set to its default value of ‘true.’)

◦ Avoid adding a representation with the same name as its model in Windchill; otherwise, sending a representation for the same masterdata of the model in Creo Elements/Direct Model Managerwill fail. In this case, the representation name in Windchill should be renamed for successful import.

◦ Updates from Creo Elements/Direct Model Manager pertaining to objects that are checked-out in Windchill will be blocked; so make sure to not leave those objects checked-out in Windchill. If an update failed, make sure to check-in or cancel the checkout in Windchill before republishing from Creo Elements/Direct Model Manager.