For environments where Arbortext uses content that is external to Windchill, we would like to see a bursting rule that excludes certain objects based on sourcetype and XPath from bursting into Windchill. A notice or some other signifier can be placed into Windchill on the Arbortext object that lets the user know there is a dependency on content contained within another system of record.
An example use case is in an environment where an external graphic repository (i.e. DAM) is used to manage marketing, hazard, or other regulated graphics or content external to the core PDM/SLM process.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.