Flow Designer Subflow - Multiple User Approvals from Variable

[Sirri]

Hi Team,

I am working on a ServiceNow Flow Designer requirement and would appreciate guidance on the best approach.

Requirement

I have a hidden catalog variable named approval_managers (Single Line Text).

This variable stores multiple user sys_ids based on business conditions, for example:

62826bf03710200044e0bfc8bcbe5df1,6816f79cc0a8016401c5a33be04be441,5137153cc611227c000bbd1bd8cd2005

I need to:

1. Read these user sys_ids from the variable.
2. Trigger approvals to all users represented by those sys_ids.
3. Ensure all approvers must approve before the process proceeds.
4. Build this logic within a Subflow.
5. Return the final approval status back to the Parent Flow through a Subflow output.
   
   

   Subflow Design

   Inputs:
   Label                     -  Name                   - Type
   Requested Item -requested_item - Reference to sc_req_item

   
   Outputs:
   Label                   - Name                      - Type
   Approval result -approval_result -String

   
   

   Questions

   1. What is the recommended approach to read multiple user sys_ids from a catalog variable and create approvals for all users?
   2. Should I use:
      • Script Action
      • Flow Logic
      • Custom Action
      • Script Step in Subflow
   3. How should the Subflow output (approval_result) be populated and mapped so that the Parent Flow can consume the result?
   4. Can someone provide a detailed step-by-step solution with screenshots for:
      • Subflow Input Configuration
      • Subflow Output Configuration
      • Script Inputs/Outputs
      • Mapping output values
      • Approval Activity configuration
      • Parent Flow consumption of the Subflow output
   5. If any Script Action or Script Step is required, could you please share a sample implementation and explain where the inputs and outputs should be configured?
      
      
      

   Expected Outcome

   • Multiple user sys_ids are read from the hidden variable.
   • Approval records are created for all users.
   • Workflow waits until all approvers respond.
   • Subflow returns:
     • Approved
     • Rejected
     • Cancelled (if applicable)
   • Parent Flow uses the Subflow output for further processing.

   Any detailed guidance, screenshots, or sample implementations would be greatly appreciated.

   Thank you.