Template Manager view

The Template Manager is the primary view of the Template Service. It facilitates upgrading deployed templates by monitoring the version and status of deployed templates, and allowing modifications to the source template. At which point, the upgrade may be applied to all out-of-date deployed templates or only to selected instances. By default, this view compares the deployed templates against your locally available templates, meaning the templates found in the ~templates folder on your local Workbench PC.

The view displays a table listing all of the deployed templates in the station. Subtemplates are indicated with a path that is indented from the parent template’s path. The Path column data displays the deployed component names. The table contains the following information for each deployed template or subtemplate:

location, name, vendor, and version
number of inputs, outputs, and relations, and default passwords
available version (of the template on the local Workbench PC)
modified (detected changes to objects in a deployed template instance )
status (untitled column, shows the status of the deployed template instance)

NOTE: The Modified column displays a red “X” if something has changed in a deployed template instance. Such a change will be lost if the template is upgraded or redeployed.

Each deployed template listed in the view displays one of the following statuses:

Up to Date — the version of the deployed template instance is equal to (or higher) than the locally available template version
Out of Date — the version of the deployed template instance is older than the locally available template version
Updated —
Not Available — a deployed template instance is detected however the template file is not in the ~templates folder on the local Workbench PC

Figure 4. Template Manager view compares deployed templates to locally available templates

In the above example, /FunMeter, /NoIoTemplate; /NoIoTemplate1, and /Templates/playground1 are all “top-level” deployed template instances that are not a deployed subtemplate. All the other rows are the contained subtemplates of the deployed top-level templates.

By examining the Path column, you can determine the following:

The FunMeter template definition does not contain any subtemplates.
The NoIoTemplate template definition contains a FunMeter subtemplate.
The LoopControl template definition contains a FunMeter template instance and a NoIoTemplate template instance.
The playground template definition contains a Economizer3 template instance and 4 LoopControl template instances.

NOTE: If a deployed template has any unbound inputs, outputs, or relations, the view displays those table cells with the Fault background color. Right-clicking one of the Fault rows displays an additional command, LinkUnboundIO. Selecting this steps, you go through the process of linking all of the unlinked inputs, outputs, and relations.

Template Manager view

Figure 4. Template Manager view compares deployed templates to locally available templates

Related Links