Overview

When templates are created and deployed on the terminal, users can dynamically modify various element properties in real time. Most often, this involves changing the element's value, but otherwise element properties can also be useful.

Format of Custom Template Commands

The same command is used to dynamically format template screens as used for built-in screens. In the table below we compare CPS field:value pairs to show what should change.

CPS Field	Custom Screen CPS Value	Custom Screen PSP Value	Notes
id	{Anything}	N/A	The id field is definable by the integrator and allows them to know which UI screen the response came from. As a result, it is not used in PSP and is omitted.
type	template	template	type determines the screen type to be used and it is always template in both CPS and PSP.
properties.template	{{templateName}}	{{templateName}}	The template field, nested in the properties array in CPS, is not used in any built-in screens, but is vital in customized screens. It is here that the template that has been created is referenced. You can have multiple screens configured on a single terminal so this allows for the choice to be made.
properties.comp. {{elementName}}. {{propertyName}}	{{value}}	{{value}}	Each property that is defined follows this format. comp Component elementName The name of the element being modified/set propertyName The property being set e.g. value or disable. value The value of the property. Usually either a string, boolean or hex color.
The above line is repeated for each property being modified.