Template Versions Dialog

This is a unique ID used to identify this template. Client files will use this ID to reference their source templates where components originated, so this ID should be unique for each individual template and it should remain constant once engagement files are created based on this template. Client files may have the document structure of one template and the mapping structure of another, for example, and this identifier will be used to distinguish between varied sources.

Use this area to update the version numbers for the various template components and trigger an update notification in live client files. Components are version independent, so each component has its own version number. When any of these components are upgraded to a new version in the template, the client file will register this change and initiate the template update process unless the version in the client file is equal to or greater than the version in the template. Version numbers are always listed as A.B.C, where A is a Major Version Number, B is a Minor Version Number, and C is a Revision Number. The version numbers can range from 1.0.0 to 999.999.999.

Enable update from template notification on this template

Select which map number properties may be preserved in live client files based on this template. Selecting a property in this list allows the client to choose whether or not that property should be updated as part of the Template Update process. A similar list is presented in the Template Update wizard in which clients can select which properties should and should not be updated. Options which are not checked in the Template Versions dialog will be grayed out and unavailable to the client in the Template Update wizard.

Select to force all new document identifiers created to be unique. This option cannot be enabled until all identifiers are unique. If you have documents and folders without document IDs, a document ID will not be assigned by enabling this option.