I believe you would need to build this out in a single workflow. Once an approval is added to a ticket no other workflow will run on the ticket.

You should be able to use conditions to check for each selection that could be made. But that sounds unrealistic with how many potential combinations there could be. 

The approval node prevents other workflows to run if you have anything after it, it includes both approved and reject.  The Event “approval status change” do not work if you have anything after the approval node as well. 
​​​​​​

Are the CAB Approval Area a multiselect field? 
As we don’t have loops yet there are no good way to use them. 

You can as you say have 15 different flows(WFA) and each send out an approval matching one of the selected value in the multi select. They will send out all approvals at the same time. 
I guess you could play with having both Change Raised and Approval status event on all of the events. 
Using tags to check if another area need to approve first.  It’s going to a bit tricky and I’m not sure it can be done, to complex 

You can use the Workflow Automator to handle this efficiently. Since your company has 15 different CAB approval areas, a change requestor can select anywhere from one to all 15 areas for approval. The goal is to make sure that all selected CABs can approve or reject the change at the same time, speeding up the process.

First, you need to configure the CABs in Freshservice. Go to Admin > User Management > CAB, and create groups for each approval area. Then, assign the right members to each group. This ensures that when an approval request is sent, it reaches the right people.

Next, set up a workflow in Workflow Automator. The trigger should be when a change request moves to "Awaiting Approval." Add conditions to check which CABs have been selected. For each selected CAB, configure an action to send an approval request. Make sure these approval actions are running in parallel, so that each CAB can approve or reject independently without waiting for others.

One important thing to note is that Freshservice processes one workflow per change request at a time. So, instead of creating separate workflows for each CAB, you should include all conditions and actions in a single workflow. This way, all necessary CABs will receive their approval requests at the same time.

Have you tried using Custom object for selecting the correct approvers ? 

I know exactly who should be looped in here, our SME  ​@Dominic Dilip , any thoughts or insights you can share on this?

Hi all,  
Sending Approvals Dynamically can be done with using a combination of Workflow automator and custom objects . 
The parallel approvals is a feature request that will be available in few months.
But prior to this feature, we only did sequential approvals and below i an example of sending approvals to different stakeholders based on the change type. 

Interesting challenge, Patrick!

I’m working on a farming-sim inspired project (based on Stardew Valley) where different “departments” (like farming, mining, fishing) need to approve resource changes before the next game cycle begins — so kind of like CAB approvals in parallel.

In my case, I’m manually simulating approvals from all selected zones at once. But in Freshservice, is there a way to loop through multiple selected values in a dropdown (like CAB areas) and send parallel approval emails using a single workflow?

Or do I need to create a child workflow per option and call them conditionally?

Hi Patrick,

I’ve faced a very similar situation while designing parallel approval paths across multiple departments. The challenge, as you mentioned, is that standard workflows tend to process sequentially or stop after the first condition is met.

One workaround that worked well for us was using custom flags or hidden boolean fields tied to each CAB area. Once a request is submitted, a script parses the selected CAB areas and sets the relevant flags. Then, individual workflows can be triggered based on these flags rather than relying on the original dropdown value. This way, each area’s workflow can trigger in parallel without conflicting with others.

Alternatively, if your platform supports it, consider using flow orchestration tools or branching logic in a master workflow to loop through each selected CAB area and initiate separate approval threads asynchronously.

Hope this helps get you closer to a smoother process! Would love to hear how you implement it in the end.