Getting data out of templates presently requires writing scripting......Either scripting inside the template to write values out to "template parameters" that the containing display can read, OR scripting within the containing display to read values out of template "internal properties". While these approaches work, they are cumbersome and not "user friendly".
To improve ease-of-use, implement a way of directly binding to template outputs from inside Ignition Designer.
Maybe breaking "template parameters" into 2 categories might facilitate this.
"Inputs to template" would be bindable only in the window containing the instances of the template, and the template would simply pull values from these parameters.
"Outputs from template" would be bindable only in the template itself, and the window containing the instances of the template would simply pull values from these outputs.