Creating an Alarm Filter

Filters are configured as expressions. You can create the same sorts of filters as in AlarmWorX™64 MMX, but the syntax and the names of attributes may be different.

For example, the source attribute name in AlarmWorX™64 Server is now called OriginalSource in Alarm Server. OriginalSource contains the full path to the alarm, including the areas.

So this AlarmWorX64 MMX filter:

x=like({{Source}},$"MyAlarm"$,0)

Would become:

x=like({{OriginalSource}},$"/MyAlarmArea1/SubArea.MyAlarm"$,0)

You can add an Alarm Viewer to a GraphWorX™ display and subscribe to your alarm server to see the available attributes and their values. This can be useful when creating filters.

To create an alarm filter, select your component. For instructions, click the component that you selected.

• Alert Notifications

  To create an alarm filter for an alert notification:

  1. In Workbench, go to Alarms and Notifications > Alert Notifications.
  2. Expand either Email Nodes or SMS/Text Nodes and edit your node.
  3. Go to Message Settings and update the Filter Expression.

  Twilio, Vonage, AT&T, SendGrid, Microsoft Azure Communication Services (ACS), Microsoft Teams, and Brevo do not support direct alarm subscriptions. You must use Bridging or Connected Field Service for these features.

• Connected Field Service

  To create an alarm filter for Connected Field Service:

  1. In Workbench, go to Alarms and Notifications > Connected Field Service > Workflows.
  2. Expand your configuration and edit your workflow.
  3. Go to Workflow Execution and update the Filter Expression.

• Bridging

  To create an alarm filter for Bridging:

  1. In Workbench, go to Bridging > Transactions.
  2. Expand your configuration and edit your transaction.
  3. Go to Transaction Execution.
  4. For Execute transaction using, choose either Alarms or Alarms and Triggers.
  5. Update the Filter Expression.