Reference Leaf Attributes
The table lists the attributes of a leaf.
| Attribute | Description |
| Abbreviated Name | Short name for a leaf. |
| Attribute | Description |
| Comments | Notes for reference. |
| Creation Date | The date a leaf was created. |
| Description | Text that describes a leaf. |
| Document ID | Universal Unique Identifier (UUID) of the published document. |
| Due Date | The completion date of a leaf. |
| Keywords | Text to search for a leaf. |
| Last Repository Data Retrieval | The last date a DMS Sync was run against this leaf. |
| Leaf ID | Unique number that identifies a leaf; read-only value. |
| Link Text | Link information entered when a link destination is not found. |
| Modified File Override | Name of the modified file that replaces the original file. |
| Modified Leaf | The leaf modified when performing the lifecycle operation. Includes the leaf name and the sequence number. For example., Cover Letter (P0004). |
| Name | Name of the leaf. |
| Number | A number used internally to identify a leaf. |
| Operation | Leaf operation such as append, delete, replace, new. |
| Output File |
Relative path and/or the file name of the published output for the leaf. — The value you enter cannot exceed 500 characters. — Avoid extra periods in the file name, such as output.file.doc, as this can result in an invalid file name in a DMS. |
| Note: For a reference leaf, this attribute is presented as a read-only field. | |
| Owner | The owner of the leaf. Default = current user. |
| Priority Number | The display order of Context of Use. See Unchanged Priority Number, Priority Number Calculation Rules. |
| Reference Leaf Application | The link to the application. |
| Reference Leaf Assembly | The link to the assembly. |
| Reference Leaf Hierarchy | The path to the leaf the reference leaf links to. |
| Attribute | Description |
| Reference Leaf ID | The ID of the leaf the reference leaf links to. |
| Title | The title of the leaf. |
| Use Application Prefix | Indicates if an application prefix is necessary when the reference leaf exists in another application or assembly. |
| Use Native File |
Use to choose source files or renditions for publishing. — To include both the native SPL XML and a PDF rendition, create a second leaf, assign the same document and choose No for Use Native File. — Do not assign a publishing effect (special sheet, TOC) or more than one document to a leaf when Use Native File is set to Yes. During publication, the publishing effect or document will not be added to the leaf, and no error message will be generated to indicate this. |