Setup Detail
This is an example of using the IF Canceled logic blocks in different instances.
IF Logic detail
The initial IF block will look to see if a Cancel signal has come in before the operator gets the alarm and will log and close the alarm if so.
If the Operator gets the alarm they will work it accordingly. While in the ELSE block possible Cancel situations include a Cancel type signal event, a Customer created cancel from the alarm, or on the password verification dialog box.
In the web client or VB client we will do the following:
1. Let the operator know if there are unread notifications and let them cancel, view, or continue.
2. Ask to switch to a higher priority alarm if we received one and haven't already switched.
3. Check to see if we can close the alarm without forcing it to close so that if there is any required things still left in the AP then it will warn them and let them continue to close if they choose.
Previous behavior was that the customer canceled and ignored all action pattern lines other than CLOSE. With this change, the customer cancels or receives a signal that cancels will ignore all action pattern lines other than CLOSE and it will also not ignore action pattern lines within an IF CANCELED logic block.
Previous behavior was that if a password was verified and the operator clicked the checkbox to Cancel Alarm and Close Alarm then the alarm was forced closed. With this change, if there are action pattern lines that are in an IF CANCELED logic block and are still REQUIRED or MUST CALL then the web client will let the operator know and ask them if they want to continue closing the alarm.
Customer canceling or receiving a signal that cancels will cancel REQUIRED action pattern lines unless they're in an IF CANCELED logic block.
In the VB client, there will be no option to cancel in any form once the Action Pattern is in an IF Canceled/Else logic block. Unlike in the web client, the Operator will not receive a dialog box asking if they wish to close without all required actions being done. They will be forced to continue working through the alarm until all the required actions are completed.
If a Cancel signal comes in after the alarm has been handled it will NOT mark the alarm as canceled. This is existing and expected behavior. The multiple IF blocks in the above example are based on whether the Alarm is canceled via the customer, not a cancel alarm event.
