Fill in the new document

1. On the General page, specify

   • The document's Revision and Lifecycle phase. You can modify the proposed revision or lifecycle values. For example, if you're making a new iteration simply to move the document to a new lifecycle (say, from Preliminary to Production), then you can change the lifecycle and use the previous revision to show that the technical content hasn't changed.

   • The Document name (title). The starting value is copied from the document type's Text template value. See the Document types: Document title template help topic.

     The Name{a} button inserts the values on the Custom page into the part type's Text template. The button is visible only when custom attributes have been specified on the part type. To make a new document name, first enter the custom attribute values, and then click the Name{a} button to make the name. The new name completely replaces the previous name. You can edit the new name after the custom attributes have been inserted.

     Keep in mind any naming constraints of downstream computer systems. For example, some MRP/ERP systems can accept only 30 characters, or are limited to ANSI Basic alphanumeric characters. Export queries can, for example, convert the name to uppercase, but converting Unicode to ANSI or correctly shortening a long description is more difficult. Some data fields show a character counter in the upper right of the box that show the current text length.

2. Provide more information or keywords in the Release description and Revision area that can be used to help users search for this document.

   • The Revision area may be used to identify where the change occurs (say, drawing Zone A2 or Requirements 2.1 & 4.3).

   • The Release description briefly summarizes how the technical content has been changed (for example, Increased hole diameter). This is shown on the change form Affected list as a note to reviewers.

3. If you need to apply security access settings related to a Product Families collection member, drag the member from the Collection Explorer and drop it on the Product families list box.

4. Use the data on Attributes to identify people and organizations that affect the document's contents, and identify and access rights that control document distribution or usage.

1067