Help with Catalog Item approvals

[EricG2]

I have a request to create a Catalog Item for access to a Third Party web application.

In this app, there are several "modules" that a person can have access to and each may have different person that need to approve access.

I have a simple form that show the Module with a Yes / No response.

Under those, i'm showing their required fields for setting up access.

I've also added a Decision Table for the form to help determine the approvers.

So far everything is working.

The issue i'm facing is, if the user has selected more than 1 module (lets say 3) and one of the 3 approvals is rejected.  The whole ticket is getting rejected.

My flow is only updating the work notes to document that X approver rejected the request and adding that to the flow output message.

So when the RITM is hopefully opened, the Description field with show in full Which Modules have been approved to help the team add the user in the Online Application to the correct modules.

I've tried looking at the business rules and script includes to hope fully find what is causing the whole ticket to be placed in a Closed Rejected state and Inactive.

Can anyone advise what rule is causing this?  I'm not sure exactly what else to post, as the activities in the flow are pretty simple and strait forward.

I'm wondering if i should break each module out and combine them into an order Guide.

[lpruit2]

Greetings @EricG2. Great use-case for using a Decision Table! The issue you are describing sounds like one of the known limitations of Flow Designer that it cannot handle multiple approvals against a single record very well without a workaround. I'll attach a great article that describes the different scenarios in more details. In short, you can try a couple of different options (which are outlined better in the link below).

1. In your Ask for Approval step, remove the value in the Approval field. 
2. Create individual Task records for each module ahead of each Ask for Approval step. Then fire the Ask for Approval step against the individual Task that was just created. 

Flow Designer Approvals Overview - Workflow Automa... - ServiceNow Community

[MaxMixali]

The issue: Cost plans showing incorrect values after migrating to Next Experience Resource Management, impacting financial reporting.

Most likely root cause: Rate card configuration issues (60% probability) - Next Experience RM uses a completely different rate card structure than Classic RM, and rates weren't properly migrated or mapped.

Immediate mitigation: Follow the 3-phase investigation approach, then apply the tiered fix strategy based on findings.