Converting an Action Set to a Workflow

You need to recreate your AlarmWorX™64 MMX action sets as Connected Field Service or Bridging workflows. These workflows are more flexible than action sets, but are configured very differently.

The workflow templates for Connected Field Service or Bridging work the same way, but are configured in different places and offer different activities. Bridging cannot recreate many elements of an action set, whereas Connected Field Service should be able to recreate and enhance any action set logic.

To edit a workflow template, select a component:

• Connected Field Service

  In Workbench, go to Alarms and Notifications > Connected Field Service > Templates.

  The following table describes how different parts of your action set might translate to a Connected Field Service template.

  AlarmWorX64 MMX Action Set Element	Connected Field Service Template Element
  Action destination and media template	Use either a worker lookup or fixed contact list activity to choose a worker, and then use a notification activity, such as Send Email, Send SMS, Send Voice Message, Send WhatsApp, or Teams IM to specify the type of action and its content.
  Alarm states, such as in alarm, acknowledged, and return to normal	Use the ack (acknowledged), alarm, and normal activities to control how your workflow responds to alarms in these states.
  Looping and stop conditions	Use the condition activity and a counter variable to stop after a certain number of loops through your transaction. You can use alarm variables or worker variables in your condition expression to change the flow based on elements of the alarm or worker.
  Delay	Use the delay or alarm delay activities. The alarm delay activity can end its delay period when there's a new update for the alarm, such as it has returned to normal or there has been a change in quality.
  Escalation	Use filters in worker lookup activities to identify different groups of workers, such as managers.

  The sample configuration for Connected Field Service contains some useful example templates:

  • Ack Loop Template: This example shows how to look up a list of workers to be notified of an alarm via email. It iterates over the list notifying a worker, waiting for a delay, and then checking to see if the alarm was acknowledged, before moving on to email the next worker. If a worker acknowledges the alarm or everyone has been notified, then the workflow stops running.

  • Escalation Template: This example is similar to the Ack Loop Template. However, it only notifies the first two workers in the list. Then if the alarm is still unacknowledged, it will escalate by looking up the managers and notifying the first one.

• Bridging

  In Workbench, go to Bridging> Templates.

  The following table describes how different parts of your action set might translate to a Bridging template.

  AlarmWorX64 MMX Action Set Element	Bridging Template Element
  Action destination and media template	Use a notification activity, such as Send Email, Send SMS, Send Voice Message, Send WhatsApp, or Teams IM to specify the type of action and its content.
  Alarm states, such as in alarm, acknowledged, and return to normal	Bridging cannot easily respond to changes in alarm state. Consider using Connected Field Service instead.
  Looping and stop conditions	Use the condition activity and a counter variable to stop after a certain number of loops through your transaction.
  Delay	Use the delay activity.
  Escalation	Bridging cannot easily handle escalation. Consider using Connected Field Service instead.

If you are using only Alert Notifications without Connected Field Service or Bridging, there is no equivalent to action sets. You do not need to set up anything for this step.