About Templates

You can create a template from an existing process app, then use the template as a starting point for additional process apps. For example, you may want to create custom form styles, then create a template to ensure that forms in all of your process apps use the same styles.

To convert a process app to a template, refer to Creating a Template.

You can then add templates to your local library so they are always available to you as you create process apps. For details, refer to Adding Templates to Your Library.

A template has the following characteristics:

• A template cannot be referenced by other process apps. (For information about references, see About References.)
• A template can reference other process apps (for example, the Global Process App).
• A template cannot be published or deployed.
• A template can be exported.
• A template has an .mst file extension. (A blueprint has an .msd file extension.)
• A template can be imported, with all settings preserved.
• You can add templates to your template library so they are readily available as you create process apps.
• All process apps created from a template have unique design numbers. Templates do not have design numbers. (For information about design numbers, see Managing Internal Identity and Design Numbers.)
• A blueprint can be converted into a template, but a template cannot be converted to a blueprint.