need help in flow

[nameisnani]

We have a catalog item with the following fields:

• Related Category (Mandatory) – Choice field with values:
  • Collaboration and Communication
  • Cyber Security Services
  • Hardware
  • Infrastructure
  • Software
• Application Name – Reference field to the Business Application table

---

 Current Behavior

When both fields are selected:

Example:

• Related Category = Hardware
• Application Name = ServiceNow Production

Flow:

1. Line Manager Approval
2. Hardware Group Owner Approval
3. Application Support Group Approval (based on Application Name)
4. Catalog Task is created for ServiceNow Production Support Group

This is working as expected.

---

 New Requirement

If:

• Related Category is selected
• Application Name is NOT selected (empty)

Then after:

1. Line Manager Approval
2. Category-based Group Owner Approval

The request should route to default fulfillment groups based on category, as below:

Related Category Default Fulfillment Group

Collaboration and Communication	Infrastructure-SUP
Cyber Security Services	CyberSecurity_Tools-SUP
Hardware	TechHub-SUP
Infrastructure	TechHub-SUP
Software	SUP

can anyone please help me in scrp

 @Ehab Pilloor  need your help here

Ehab Pilloor

Mega Sage

z

[Sanjay191]

Hi @nameisnani 

As I can see, you have multiple conditions in this flow. Could you please consider using a Decision Table? It will make the logic easier to maintain, reduce the number of steps, and improve the overall readability of the flow.

If my answer has helped with your question, please mark my answer as accepted solution and close the thread for the future readers
Thank You

[RaghavendraGund]

Hi @nameisnani,

Building on what @Tanushree Maiti shared — here's exactly where and how.

You don't need a separate If block. Go to your "If application_name is not empty" condition (step 15) and add an Else to that same condition using the "+". Since Related Category is mandatory, it's always populated — so the Else automatically represents your exact case: category selected + Application Name empty. No need to re-check Related Category.

Also note: by the time the flow reaches this point, the Line Manager and Category (second-level) Group Owner approvals have already run. So the Else branch doesn't need any new approval — it only needs to create the task.

In the Else branch:

1. Create Catalog Task
2. Set Assignment group = the default fulfillment group for the selected category

You're already inside a category-specific branch (e.g. "If Collaboration and communication"), so you can set the group directly per branch:

• Collaboration and Communication → Infrastructure-SUPPORT group
• Cyber Security Services → CyberSecurity_Tools-SUP
• Hardware → TechHub-SUP
• Infrastructure → TechHub-SUP
• Software → SUP

Tip to keep it clean: instead of hardcoding the group in every category branch, create a small lookup table (Category → Default Group), seed those five rows, and use a Look Up Record action to fetch the group dynamically. Then a single Create Catalog Task handles all categories, and future changes are just data — no flow edits.