An application template is a standard framework for users to employ when they create applications. In the application template, you can specify the application properties, environment properties, and environment gates for an application. You can also create a framework that describes attributes of the components, environments, and application processes that an application initially contains. Application templates can contain as many of these elements as required to guide users through the application creation process and to standardize their environments.
Instead of identifying which components must be used in the application, you can specify which tags that the components that users assign to the application must use.
To control which components users can assign to an application by using the template, you must create a naming scheme for component tags that is relevant to your company. You must also consistently apply the tags to components and component templates. See Adding tags to objects.
For example, a simple three-tier web application uses a database, web interface, and application logic. You might tag these components with the following tags: database, web_ui, and app_logic. When you create an application template for this web application, you can specify that the application contain three components, one that uses each of those tags. When users create an application from the template, they can assign to the application one component per tag.
To ensure that users can create only applications that adhere to templates, you might create a role for users who create applications from templates. See Creating roles and assigning permissions. For more information about role permissions that prevent users from modifying applications to deviate from the application templates, see Application template permissions reference.