Decision table in flow designer

[SivaranjaniR]

Hi Team,

I’m working on a flow where:

• A request is submitted through a Service Catalog item.

• I need to send approval tasks to different groups based on the requester’s department.

• There are about 40 departments and 10 approval sets.

What I’ve done so far:

1. Created a Decision Table with:

   • Input: department (cmn_department).

   • Output: assignment group.

2. In Flow Designer:

   • Get Catalog Variable (requestor_department).

   • Use Make Decision (Decision Table).

   • Create Catalog Task.

   • Update the Catalog Task → set Assignment Group = decision output.

Question:

• Is this the best approach to handle large mappings (40+ departments → groups), or should I consider sub-flows/lookup tables instead?

• How can I make sure the decision output (assignment group) is reliably applied to the created task?

• Is there a more scalable way to maintain these mappings without hardcoding in the Decision Table?

I have run several test ,  decision table output hard to map through the flow .

Thanks in advance!

[kaushal_snow]

Hi @SivaranjaniR ,

Using a Decision Table inside Flow Designer works decently for your scenario mappings when you expect changes, but for scale, a lookup table and subflow gives better flexibility and maintainability.... Make sure your flow gets the department reference, then call the decision or lookup, capture its output in a variable, then use that to set the assignment group after task creation (or update immediately)......

If you found my response helpful, please mark it as ‘Accept as Solution’ and ‘Helpful’. This helps other community members find the right answer more easily and supports the community.