Hi all,   Broad question, but I am undertaking some alarm rationalization work and am wondering if there is an efficient way to query what the value of all alarm severity fields are across all relevant object classes in a ClearSCADA database?   The only way I know of currently is to individually query object classes like CeNetAnalog, CPointAlg, etc. one by one for all of their alarm severity fields and manually compile all the information somewhere like a spreadsheet. Quite a time-consuming process and my main concern is that it is very easy to accidentally miss alarms on object types that I'm not aware even had configurable alarms in the first place. For example, I only just learnt that CRootGroup has a WSEventSeverity field for workstation events as well as multiple aggregates that each have severity settings too.   I'm just thinking could there be a way to work backwards instead and somehow start from the severity settings in Server Config and somehow grab a list of all references to that? ... View more

I had this trip me up on CS2017R2: Write a script to build and call an ad-hoc trend of an analog point using TrendSpec. Read the units property of the analog and include it in the YAxis Label string. Run this script on an analog point with units '%'. Ad-hoc trends builds fine on ViewX. Run this same script on the same analog point in a WebX client. WebX throws up an XML error. Change the units of the analog point to '%25'. Run script on WebX again, it magically works.   My understanding is the TrendSpec string is encoding the '%' character to '%25' for the URL version of the SCX address. However, because the '%' character is in another nested string within the SCX string, it needs to be encoded twice ('%2525' instead of just '%25') which ClearSCADA is not doing. I seem to be able to hack this by replacing the '%' with '%25' somewhere in the script (or in the units field).   Is anyone aware of this issue being fixed in later versions of ClearSCADA? ... View more

I'd like to know more about the performance difference between the two execution methods mentioned in the thread title.   To my understanding, 'Input Processed' causes the script to execute when it detects an change in one of its VAR inputs in the program, while setting a Trigger causes the execution when it detects a change in any database object that you specify in that property field.   However, since Triggers are used as part of 'On Interval' execution, setting a Trigger also requires setting a timed interval for the program to periodically check the value of that Trigger input, while you don't need to set any such interval to check inputs for 'Input Processed' - it seems to fire off the program instantaneously on input change. Would this imply that, compared to 'Input Processed', there is some extra performance overhead from using 'On Interval' with Trigger due to the need to explicitly query the trigger object on a periodic basis?   As an example, say I need Program A to execute when the value of Input B changes but Input B isn't actually used in the program. The obvious way would be to use On Interval execution and set the Trigger to look at Input B. However, I would need to specify a period for the program to explicitly check that input.   However, I could also declare Input B as a VAR in the program itself and not actually use it at all. Then I can set the Execution Method to 'On Input Processed' and the program executes as soon as Input B changes without having to specify a timed interval for it to check that input.   Would the second method be more efficient in this case in terms of logic execution? ... View more