Resources

Tutorials

All you need to know about workflows in evalink talos.

Back to blog

Workflows within evalink talos

Workflows define how an incoming alarm is handled. Thanks to many integrations and high flexibility, workflows can be used for many cases within and outside of an alarming environment. In addition, every workflow can be created efficiently by choosing from manual or automatic workflow options. 

image (5).png

Workflow functions 

There are several functions available under the categories within the workflow creation. In the following, the distinct functions are shortly explained. 

Manual / automated workflows 

evalink talos users can set up workflows that can be handled fully manually or through automated steps. With manual workflows, the evalink talos operator manages the alarm directly in the user interface and handles all incoming alarms by hand. In comparison with automated workflows, incoming alarms are executed fully automatically regarding matching attributes. evalink talos will then handle the alarm step by step, as set up within the automatic workflow. Within evalink talos, manual workflows are symbolized with a persona, automated workflows with a cloud icon. 

Site / site group / global workflows 

Workflows can be created on diverse levels, regarding if they should be valid for one single site, a site group, or globally. Workflows for a specific site are managed within the site itself, site group workflows are managed within the defined site group, and global workflows are managed within the company. 

For site group and global workflows, you can choose whether they are triggered before, after, or instead of a local workflow. If a site group and a global workflow are present, only the site group workflow is triggered. 

When there are more local workflows defined, only one is executed. Priority: 

  1. the first automatic workflow in alphabetical order 
  2. the first manual workflow in alphabetical order 
Using templates 

Templates can be created and stored within the company folder. The templates are available in the workflow tab within the site or site group. By using a workflow template, evalink talos creates a copy of the original template. This copy can then be adapted to fit the use case of the site. Adapting this copied workflow does not alter the stored template. 

Workflow trigger 

If an alarm is entering into evalink talos, all the defined workflows are selectable. If the alarm condition matches a workflow condition, this workflow is shown as default but can be changed by the operator. 

How to add a new Workflow 
  1. Go to a site or a site group and then click on Workflow or Group Workflow. 
  2. Click the plus sign and add a name for the workflow. 
  3. Choose if you want to create a manual or an automatic workflow and choose a template (optional). 
  4. Then you can choose the alarm conditions. For automated alarms, at least one condition is mandatory. 
  5. Add a function by clicking the plus sign right next to the last function. Then, on the right side, you can configure the function. 
  6. Save the workflow by clicking on the save icon on the right. 
  7. Test the workflow by clicking on the bug icon on the right. 

Manual Actions 

Manual actions need the interaction of an operator. They must be processed manually, based on the information within the workflow action. 

Call someone 

The operator must call one or more contacts, contact lists, or individual phone numbers. Each call must be initiated manually by the operator. 

Deploy alarm response 

The operator is instructed to deploy an intervention team to handle the alarming reason directly on site. 

Write a report 

The operator is obliged to write a report regarding the incoming alarm. Therefore, the proceeding is not possible until a report is written. 

Wait for restore 

The operator must wait until the alarm is restored. Then, if a remark filed is set, the operator must enter a remark. Otherwise, it is optional. 

Generic Action 

Asks the operator to do a generic action before he can proceed. A descriptive text and icon can be assigned to the generic action. Then, if a remark filed is set, the operator must enter a remark. Otherwise, it is optional. 

Manual Decisions 

A manual decision forces the operator to interact and approve the alarm. Manual decisions are used to decide if a threat is present or a false alarm. 

Check Milestone Camera 

The operator has to check the connected camera to confirm if a threat on site is present. 

Call someone 

The operator can call one or more contacts, contact lists, or individual phone numbers. Each call must be initiated manually by the user. After the call, the operator must decide if the call was successful, or the target was unreachable. The follow-up action for a successful call and an unreachable call must be defined within the workflow. 

Yes/No 

The operator must make a yes or no decision. For each decision, a follow-up action must be defined. Then, if a remark filed is set, the operator must enter a remark. Otherwise, it is optional. 

Ask a question 

The operator chooses one of the answers to a question. For each answer, a follow-up action must be defined within the workflow. Then, if a remark filed is set, the operator must enter a remark. Otherwise, it is optional.

Automated Actions 

An automated action within a workflow defines an action after a specified event is triggered within the workflow. For example, automatic actions are normally used to inform the site owners or an operator at an ARC. 

Deploy Baviloc alarm response 

Baviloc units get a direct intervention call to check the status of an alarm on-site. 

Send Email 

Sends a predefined email to one or more recipients (contacts, contact lists, individuals). The operator does not see the email text and cannot edit it. 

Twilio Group Call 

Executes a conference and calls everyone within the defined contact list. Optionally a text-to-speech message can be used when a recipient takes the call. However, the evalink talos operator is not part of the group call! 

Send Slack Message 

Sends a predefined message to the Slack channel defined within the Slack integration. The evalink talos operator does not see the message and can't edit it. 

Twilio send SMS 

Sends a predefined Message to one or more recipients (contacts, contact lists, individuals). The operator does not see the SMS text and can't edit it. 

Trigger Webhook 

An integrated webhook sends a signal to evalink talos and triggers the associated alarm condition. The alarm condition can be defined by the site owner and is flexible. 

Send SIA Message 

Sends an SIA message to your device and can be used to trigger a physical action initiated by your device.

Note: This only works with the evalink ipTNA devices

Switch Actor 

Switches an actor on your device and changes the state of this actor. A predefined event is triggered when the actor is switched. 

Note: This only works with the evalink ipTNA devices

Set Tag 

A Tag is set and attached to the site where the alarm was triggered. The Tags are named and created by the evalink talos user. The Tag is visible in the site overview and can be found through the search functionality. 

Wait some time 

The workflow is waiting a defined time before the following action or decision is triggered. The evalink talos operator cannot abandon this step. 

Automated Decisions 

An automated decision within a workflow is used to define if it is a real threat or a false alarm. evalink talos is doing all the steps automatically to decide, based on predefined conditions. 

Twilio Alarm Verification 

Calls someone (or multiple people) and let them verify the alarm by entering a numeric code on the keypad. At least two codes must be set (verified alarm / false alarm), but more codes can be added. Follow-up actions must be defined for a correct code, wrong code, unreachable caller, and execution error. A text-to-speech message to the recipient can be used. 

Twilio Call 

Calls one or more people and optionally requires input by pressing a key for acknowledging and another for dismiss. A text-to-speech message to the recipient can be used. When using a contact list, a minimum number of successful calls needed can be defined, and if the contacts are called sequential or parallel. 

Follow-up actions must be defined for successful calls and execution errors. 

Check Time of Day

Define one or more timeslots. The operator must select the valid timeslot manually. For each timeslot and default (no valid time slot), a follow-up action must be defined. 

Wait for Alarm 

Wait a specified time for one or more alarms of the related site. Different incoming alarm conditions can be defined (e.g., code, zone, value, source…). Automatically evaluates the alarm condition and only pushes it to the UI if the conditions are fulfilled. 

Follow-up actions must be defined for success and execution failure. 

Check Alarm Attributes 

Checks the attribute of an alarm and checks if it matches with a defined condition (e.g., code, zone, value, source…). Automatically evaluates the alarm attributes and only pushes it to the UI if the conditions are fulfilled. 

Follow-up actions must be defined for success and execution failure. 

Check Schedule 

Checks a defined schedule and matches the alarm to the schedule condition within the workflow. Schedules can be set on-site, site group, and global level. For each schedule and default (no valid schedules), a follow-up action must be defined. 

Check Tag 

evalink talos checks whether a defined Tag exists. A follow-up action must be set for existing Tag and missing Tag conditions. 

Other

Under the Other options, you find workflow closing options and actions that do not need a decision to be executed.

Jump 

Use the jump functionality to jump to another location within the workflow quickly. For example, this can jump to the beginning of a workflow if the defined workflow was not successful. 

Repetition Counter 

Possibility to repeat a step within the workflow numerous times. The number of repetitions can be set when creating the workflow. The action is only repeated if it was unsuccessful; if the step was successful, the workflow carries on as defined. 

Do Nothing

No action is triggered. 

Close Workflow 

After this step, the workflow is closed. It must be the last instruction within a workflow. It also can be used within decisions. 

Conclusion

As you can see, the workflows within evalink talos are incredibly flexible and feature-rich. Furthermore, with the ongoing addition of new integrations, the possibilities within the workflows are growing monthly. This allows evalink talos users to tailor their workflows to their demands. 

Interested in trying evalink talos?

Start free trial month now

and see how it can be used within your company. No credit card needed.