Creating an application template

Application templates are created in the Workbench that connects to a running station with a completed set of component logic, device networks, and graphics.

NOTE: To avoid future problems, make sure that you tag and configure devices correctly before making a template and using it to configure other devices. Additionally, you must copy all relevant tag dictionaries (with the exception of the Niagara tag dictionaries) from the tag dictionaries Service to the tag dictionaries folder in your User Home file space before the template is first created (or edited), and during template deployment to be successful. Also, the system does not automatically apply subsequent template changes to the configured devices.

Perform the following steps:

Expand Station > Config in the Nav tree and right-click the Config.
Select Templates > Make Application Template from the option.
A Template View opens.
NOTE: This view is the same for all template types (Application, Device, Component), except that the application template does not have inputs, outputs, or relations.
Click each of the tabs to configure the application template as needed.

NOTE: The Component tab includes the components for the entire station source for the template. You can add, modify, and delete the template components in this view. The Nav Tree for application templates show component icons with badges to indicate the deployment status of the component. Certain components are contained in the template but not deployed to the station during the installation.These are restricted to several critical Services and the NiagaraNetwork container under the Driver. These will be displayed with the red “+” badge. Components that will be deployed are displayed with the gray “+” badge. Container components that have both deployable and non-deployable child components do not have a badge.
To generate the template file, click Save.
The file is saved to the applicationTemplates folder in the user home. If the file name already exists, Workbench prompts for confirmation before overwriting the existing file. The file can be re-opened for editing by finding the file in the Nav Tree sidebar and double-clicking on the template NAPL file.
Application templates are not available in the Template sidebar due to the destructive nature of the application template deployment. The Version and State of the template can be modified, if changes are made. The version is maintained on the deployed templates in the Template Config component in the Application Service.

Creating an application template

Related Links