Second Level Approval Validation

[trupti65]

PR Description:

Use Case:

When a catalog item requires a two-level approval process — Primary Level (Single Approver) and Secondary Level (Group/Department Approvers) — the system should exclude the Primary Approver from the Secondary Approval Group, if the same user is a member of both levels.

Example:

A catalog item first requires Manager ABC’s approval as the Primary Approver.

Next, it moves to the Department/Group Approval stage.

If Manager ABC is also part of the Group/Department Approvers, they should be excluded from the second-level approval to prevent duplicate approvals.

Pull Request Checklist

Overview

• I have read and understood the CONTRIBUTING.md guidelines
• My pull request has a descriptive title that accurately reflects the changes
• I've included only files relevant to the changes described in the PR title and description
• I've created a new branch in my forked repository for this contribution

Code Quality

• My code is relevant to ServiceNow developers
• My code snippets expand meaningfully on official ServiceNow documentation (if applicable)
• I've disclosed use of ES2021 features (if applicable)
• I've tested my code snippets in a ServiceNow environment (where possible)

Repository Structure Compliance

• I've placed my code snippet(s) in one of the required top-level categories:
  • Core ServiceNow APIs/
  • Server-Side Components/
  • Client-Side Components/
  • Modern Development/
  • Integration/
  • Specialized Areas/
• I've used appropriate sub-categories within the top-level categories
• Each code snippet has its own folder with a descriptive name

Documentation

• I've included a README.md file for each code snippet
• The README.md includes:
  • Description of the code snippet functionality
  • Usage instructions or examples
  • Any prerequisites or dependencies
  • (Optional) Screenshots or diagrams if helpful

Restrictions

• My PR does not include XML exports of ServiceNow records
• My PR does not contain sensitive information (passwords, API keys, tokens)
• My PR does not include changes that fall outside the described scope

[ravichandra1998g]

Hello @trupti65

You have created a SubFlow folder under Specialized Areas, but this is not a sub flow.

The script expects group sys id and requestor_id as input, and returns and array.
This suits more for an action.

We have Actionpack Repo introduced in Hactoberfest 2025 to capture Flow Actions.

Closing this for now. Kindly submit this use case as action under action pack.