Configuring Products or Libraries for Dynamic Documents
Products and libraries that will be used primarily for managing dynamic documents are generally no different from products and libraries used for managing parts. When setting up a product or library for this purpose, review all of the activities described in Typical Duties of Product and Library Administrators, keeping in mind that the main business object type being managed is the Dynamic Document object type.
Since the out-of-the-box context templates do not have anything specifically set up for this object type, you may want to look closely at the following administration activities as they relate to managing this type of object:
• Create folders for use in organizing the dynamic documents that are checked into your Windchill solution.
• Create additional subtypes and attributes for dynamic documents. The subtypes and attributes correspond with Arbortext document types and attributes that are set up for use with the Arbortext Editor.
For more information, see Type and Attribute Management.
• Set up specific teams, life cycle templates, and workflow templates for use with dynamic documents. For more information about these topics, see Equipes, Life Cycle Management, and Workflow Management.
• Review and set object initialization rules for Dynamic Document subtypes. For more information on setting object initialization rules, see Object Initialization Rules.
 |
Autonumbering must be turned on for the Dynamic Document subtype and its subtypes. By default, autonumbering is turned on for the wt.epm.EPMDocument type and all of its subtypes through an object initialization rule in the site context. Since dynamic documents are subtypes of the wt.epm.EPMDocument type, the rule automatically applies dynamic documents unless additional rules have been set up that override the site context rule.
For more information about numbering objects, see Changing Numbering Schemes.
|
• Set access control policies on the Dynamic Document subtypes. For more information on setting access control policies, see Administering Domains and Policies.
Additionally, there are activities unique to using the Arbortext Editor and the Arbortext Publishing Engine with product and libraries that need to be performed. These include the following:
• Establish the configuration settings used by the Windchill connection to Arbortext Editor. For more information, see the Windchill connection online help accessible from the Arbortext Editor.
• Manage the bursting rules used when a dynamic document is stored in Windchill. For more information on bursting rules, see the Arbortext Editor online help.
• Manage additional attributes for WTDocument object type that are used by the publishing agent when publishing dynamic documents. For more information on specifying publishing rules, including specifying rules for the resulting documents, see About Publish Rules.