OTHER USER MANUAL VERSIONS
Sepasoft - MES Modules
Cirrus Link - MQTT Modules
Knowledge Base Articles
Template Properties (called Template Parameters) allow each template instance to reference different data. Because the primary use of templates are the ease of maintaining repeated user interface elements, correct use of Template Parameters is very important. This is very similar to the concept of Parameterized Popup Windows. In that case, any Custom property on the Root Container of the window is used as a parameter, and is passed into the window when it is opened. With Templates, you have a property in the root of the master template that is exposed when you drop a Template Instance on a window.
When you open the Custom Properties window (right-click the checkered-box of the template and select Customizers > Custom Properties), you'll notice it is different than the Custom Properties of all other components. There are two kinds of custom properties here, as follows:
These properties cannot be used as parameters in your instances. They show up when designing the template master, but it does not show up on the template instances. Internal properties are bindable from within the template master design. These properties are intended to be used for the internal workings of the template.
There are two primary ways to achieve indirection when using templates. Let's continue to use the example of a motor. Your system has many motors in it, and your template is used to display the status of the motors and control the motor's running mode. The goal is to be able to drop instances of the template onto your windows, and configure them in a single step to point to the correct motor's tags.
If the tags representing the datapoints of each motor are arranged in an orderly way in folders or with a consistent naming convention, you can use standard indirection to configure your template. You can add a parameter such as MotorNum to the template. Then you configure the contents of the template using indirect tag binding, where the value of MotorNum is used for the indirection.
If your motors are represented by a User Defined Type (UDT), you can save some effort and use a property of that type directly. Make your indirection property the same type as your custom data type. Then inside your template, you can use simple property bindings to create a link to the members of the UDT. When you create a template instance, you can simply bind that property directly to the correct Motor Tag, and all of the sub-Tags of motor are correctly mapped through the property bindings.
When you specify parameters in the Custom Properties window (right-click the checkered-box of the template and select Customizers > Custom Properties, you can set one of the parameters as the Drop Target. This allows you to drop a Tag of that type onto your template instances or onto a window to facilitate even quicker binding. For example, let's say that you have a parameter that is an integer and you've made it the drop target. If you drop an integer tag onto a window, your template appears in the menu dropdown list of components which is displayed. Choosing your template creates a template instance and binds that parameter to the tag.
This also works for UDT tags. Lets say you have a custom data type called Motor and a template with a Motor-typed parameter set as the drop target. If you drop a motor tag onto a window, it creates an instance of your template automatically. If you have more than one template configured with Motor drop targets, you have to choose which template to use.
Global Templates work the same as any other Template with the added bonus that they are globally scoped and available to be used and edited across all Projects. This is useful for very generic Templates which will be used across multiple Projects. For Templates specific to a certain Project, it is still recommended that they be created in the Project Templates space, so that they are not accidentally modified in a Project that is not using them.
Ignition allows you to save and retrieve templates from Inductive Automation's online repository, the Ignition Exchange. In the Ignition Exchange, you can access resources, templates, and tools that you can use in your own Ignition projects. Ignition assets designed by others in various industries can be shared through the Exchange. This collection encompasses anything that can be built inside of Ignition including screens, graphics, templates, views, reports, alarm pipelines, scripting functions, database backups, projects, full systems, Ignition demos, and more.
Cloud Templates have been moved to the new Ignition Exchange, and the Cloud Templates browser is not usable in any Ignition version. The browser itself has been removed as of 7.9.13. All Cloud Templates have been automatically moved to the Ignition Exchange and are still available.