Workflows: Support for multiple execution paths

Not all workflows follow a single, straightforward path. Instead a specific criteira need to determine the direction a proces takes. Until now, Omega 365 have followed a single, predefined path. We are now updating workflow functionality to suppport alternative paths involving a subset of steps.
Johnny Vik
Johnny Vik

What are multiple execution paths?

Not all workflows follow a single, straightforward path. Instead a specific criteira need to determine the direction a process takes. Until now, Omega 365 have followed a single, predefined path. We are now updating the workflow functionality to suppport alternative paths involving a subset of steps.

With the introduction of multiple execution paths, users can now define points within a workflow,  including at the initiation of the workflow.. The worfklows adapt dynamically, following different paths based on the configuration of the workflow process.

When is this useful?

This improvement has broad relevant across various workflow scenarios. Here are some examples where multiple paths is needed for a streamlined process:

Request for Modification

Suppose a project modification request involves a major change (e.g., exceeding 1 million euros). In this case, the workflow can dynamically route the request through additional approval and review steps, ensuring the right level of oversight and control. Simpler modifications, on the other hand, can proceed through a more streamlined path


Example of a process for handling requests for modifications, where different execution paths is required.

Incident Reporting

Incident workflows can now differentiate between incidents with and without injury on a person. For instance, when an injury is involved, the process can automatically branch to include additional steps for compliance, documentation, and reporting, ensuring that the case receives the necessary attention and follow-up.

Security-Critical Bug Fixes

In cases where a bug fix impacts security, the workflow can be configured to take a separate path involving additional scrutiny and testing steps. This ensures that security-critical issues receive enhanced oversight while non-critical bugs can be resolved efficiently.

How does it work

When configuring a workflow process, you need to set which step where one selects which execution path to use.

In the "Steps" tab page, one selects which execution paths there should be:

Finally, for each step (after the step where execution path is selected), set which execution path it applies to. Note that it can be multiple:

When the use completing the step "Review", they can now select which execution path to use:



Based on the selected execution path, the succeeding steps will be determined. In this case, option "A" is selected,and the next steps will be "Internal Approval -> Detailed Engineering -> Execute -> Close Out". If option B has been selected it would be: "Pre-Study -> Sanction -> Basic Engineering -> Detailed Engineering -> Execute -> Close Out". 

What's next

Currently, users manually select the appropriate execution path. However, automation is a potential enhancement, allowing the system to determine the path based on previously selected values, such as cost impact or the presence of a personal injury incident.

We are also considering additional improvements based on feedback from our early adopters, which may lead to further updates in functionality