Include a Trip Sequence in a Method Action’s Arguments
You can use Method Actions to automatically perform actions on items in the database in response to alarm situations (see Perform Action/Invoke Method Redirection).
If the method that is specified for a Method Action includes string argument(s), you can optionally include any of the Trip Sequences Supported by Redirection Actions in those arguments. This example demonstrates how a trip sequence might be used in such an argument. (Trip sequences only apply to Method Actions—methods that are triggered by alarm redirection. Trip sequences do not apply to methods that are not directly associated with alarm redirection (such as stand-alone Method Calls, or User Methods).)
Example:
A Method Action on a particular Geo SCADA Expert system is used to trigger the ‘Acknowledge with Comment’ method on a digital point. The ‘Acknowledge with Comment’ method has a single string argument. The trip code %O is used to specify the scanner with which the point is associated, and to include that information in the comment that is logged when the point’s alarm is acknowledged.
The Method Action is referenced on the Redirection tab of each database item that is to trigger this particular redirection action, Define the Method Action Details..
Whenever the Method Action is triggered, any alarms that are in existence for the Method Object are acknowledged. The record that is logged in the Event Journal in relation to the alarm acknowledgment is appended with the Comment that is defined by the Comment argument. Within the comment itself, the %OScannerId.Name% trip sequence is replaced by the scanner’s name.