Thank you Carles for confirming this.
This is for existing project. Since we are interfacing with automation systems a lot of tags and alarms are involved. Scripting capability would help to handle large amount of tags, namely by allowing to encode information.
For example, instead of separately addressing 2000+ Boolean properties (each property corresponding to an alarm/trip condition) I could potentially encode them as a 32 bit integer and decode afterwards in the composer; dynamically create alerts, etc.
This is what I'm actually doing with Siemens S7-300/400 systems and it is relatively easy to implement since I can directly access memory location of a data block.
With Allen Bradley (RSLinx) however is different story, alias names are used for individual tags. With scripting capability I would've hoped to choose which tags to encode (text file for the reference perhaps) and send corresponding integer value. Ideally I'd like to send alarm name, definition and real time stamp.
This is just one example. Machines I'm dealing with are from different eras, the same tag could be scaled differently, different tag name can be used for the same parameter, etc. Having such flexibility would help to unify machines under fewer templates, relieve the platform from unnecessary processing, etc.
