Improvements to the Integration of Arbortext Editor
The 9.1 release adds a number of features to the integration of the Arbortext Editor.
PDM & Process Solutions
|Product / Module||
PTC Arbortext Content Manager
PTC Windchill PDMLink
PTC Windchill ProjectLink
|Product Functional Area||
Arbortext Document Management
Structured Content Management
|User Interface Location|
|Processes, Initiatives, and Best Practices||
Technical Information Creation & Delivery
Benefits and Description
The following features have been added to the Arbortext Editor integration:
Show user-defined icons for Dynamic Document soft types
The Arbortext bursting rules allow you to burst xml content into different Windchill object types (sub-types of “Dynamic Document”). For example, a docbook might burst into objects of type “Chapter”, “Section”, “Caution” and “Warning”. Using the Windchill type Manager, it is now possible to specify your own icons for each of these types. The customer-specified icons will display in the html UI, allowing instant visual recognition of the different types in lists such as search results and folder listings.
Support for “Save As…” of Dynamic Documents
The “Save As… command allows a user to copy an entire Dynamic document structure to create a new independent document. During the “Save As…” operation, the user can elect to create copies of the original child objects, or re-use the same object. For example, when creating a new book by copying an existing book, the user may choose to create copies of chapters and sections that will be changed in the new book, but could elect to keep the links to the same source for common elements such as a Copyright notice or other standard textual or graphical content.
Allow bi-directional modification of attributes for Arbortext Dynamic Documents
In previous releases, users could configure bursting rules to forward select xml content from an Arbortext document to Windchill object attributes. Beginning with release 9.1, it is now possible to edit those attributes in Windchill and have the new values passed back into the xml content upon subsequent document retrieval.