Overview
The Workflow Builder lets you create end-to-end workflows that map your real processes, assign tasks and responsibilities, and track progress across multiple stages. It builds on the capabilities of Automations while adding visual stages, conditional logic, and progress tracking, giving you greater control and flexibility. This feature can be used for incidents, contracts, suppliers, risks, and other workflows across your organization.
Setting up a workflow
You can create or configure a workflow by navigating to Operations -> Workflows.
Create a new workflow: From the workflows page, click on + Add Workflow. You have the option to create one from scratch or use a template.
If you're creating a workflow from scratch, add a name, description, or optionally specify a folder, and enable the workflow either immediately or after creation.
Full-screen editor: To view or edit your workflows, you will have to access the workflow editor, via the ''builder'' button. This gives you a full-screen view of your workflow for easier navigation and better clarity.
In this view, you can:
Pan and zoom across the workflow to focus on specific stages or see the full process at a glance.
Benefit from a cleaner, more intuitive layout, including updated colors and visual cues, which make it easier to understand complex, compliance-driven workflows.
Customize your workflow: Workflows can be organized into stages, each with its own set of actions, tasks, and responsibilities. To do that, click on + Add Stage. For example, you could organize your workflow into any of these stages: detection, triage, response, communication, recovery, reporting to authorities, and post-incident review.
In each stage, you can decide what actions, events or conditions have to happen before the workflow moves to the next stage. You can also add descriptions to stages to clarify their purpose and ownership. This is a flexible builder, so you can adapt it to your regulatory or business operations needs.
You can also delete empty stages (only if no functions/nodes are present). Just click on the bin button to delete a stage if you created it by mistake, for example.
If you want to add a new function/node, you can click on "+" and you have the option to choose whether you want to add it in the current stage, or in any stages underneath.
The latest function we introduced is the ''wait for'' function/node. This lets you pause a workflow until a specific event occurs or a condition is met. For example, in incident management, you can wait until a task is completed and the incident is acknowledged before moving to the next stage. Again, this can be adapted to any scenario you need. To add this, click on ''+'' and choose wait for.
At the moment, you can only add a wait for condition for: a task is completed, and questionnaire response is completed.
After you choose the wait for condition, you must select a value. Keep in mind that a task or a questionnaire must exist in your workflow, before you can use them in this function.
If you have created many tasks in your workflow, a good way to keep track of them is to look at the numbers in front. The numbers help you get an overview of the functions/nodes in your workflows. And by looking at the symbols you can also determine which function that is.
Action: lightning strike
Condition: branching arrows
Wait for: hourglass
Loop: looping arrows
So, if we take the example below, we are looking at Action number 2. This means it's the second action in my workflow, so this refers to my previous action to create a task.
After you select the value of your "wait for" function, press Save.
Let's take a look at another example below. In my workflow, you can see I added a ''wait for'' condition. This means that a pre-requisite to starting the Resolve phase, is the completion of a task. If that task is still pending, the workflow won't continue to the next step: update incident.
Once you've mapped out all your stages and action steps, press Save and make sure the workflow is enabled.
If you're unsure if a step or phase has completed or not, check out the Runs tab inside Workflows. Here you can also see if a workflow has failed, and why, so you can amend it.
Click on Details, and you'll see the complete account of what has run so far in your workflow and the current status.
Workflow Progress
From the detail page of an Incident, Evidence, or Resource, you can view the status and progress of workflows that were triggered by that specific item. For example, if a workflow is triggered when an Incident is created, it will be visible on that Incident’s detail page, but not on related Evidence or Resources.
The workflow overview shows:
name,
creation date and time,
stage progress and status,
steps history.
This overview gives a clear picture of all active and completed workflows triggered by the item.
If you have any completed workflows associated with this incident, toggle on (Show completed) and you will see them all in this overview.
Using the Workflow Builder in practice
The workflow builder is a very flexible functionality, and can be adapted to a wide range of needs. Below are some of the most common scenarios where it’s particularly useful.
In Incident Management, you can map the full process from first reporting to exporting reports for authorities, while keeping track of deadlines and responsibilities.
For Contract Management, you can visualize the contract lifecycle, assign tasks at the appropriate stage, and manage the process without juggling multiple automations.
For Supplier Management, it allows you to send questionnaires, assign responsibilities at each stage, and track risk levels connected to each supplier.
In Risk Management, the builder enables you to map and track cross-departmental processes, ensuring all tasks are completed on time.
Good to Know
If you're removing a step all subsequent actions and stages will be deleted. This will be remedied in a future update.
At the moment, the ''wait for'' function/ node uses only ''and'' logic.
In the coming months, we will be adding more functionality to the workflow builder such as ability to branch out and merge back into one branch, and others. If you have a special need or general feedback, you can submit a feature request at this link.
We hope this article was helpful!
If you have any additional questions, please reach out to us via chat in the bottom right corner of the page — our team is always happy to assist you further.