RITM stage not being updated when Flow and subflows are completed

[AbbasP]

Hello all,

I have an interesting problem which I am hoping the community can assist with.

I have a Flow which gets multiple business applications from a list collector (in the catalog) and checks the CI Class manager for their relevant owners.

The flow then creates a task for each application and sends an approval out to the relevant owner as a subflow. This was created to meet the requirement of all the approvals being sent out instead of waiting for them to be approved sequentially.

So far, testing has been successful when performing the following actions:

1. If the application owner approves for all TASKS, the parent RITM has its state marked as Open and Stage is marked as Fulfilment (expected behavior)

2. If the application owner rejects while others approve, , the parent RITM has its state marked as Open and Stage is marked as Fulfilment (expected behavior)

The issue:

I have created another flow which checks all RITMS where the TASKS have been closed and if they are all closed, it will close the RITM.

This is to cater for the requirement if all the approvers reject the TASKS in the RITM.

This is currently working; however, I am unable to update the STAGE in the RITM to closed rejected.

My question:

1. How can I have the RITM stage updated (preferably using flow designer)?

2. Is this the best way to do this?

Thanks for your help..

[J Siva]

Hi @AbbasP 
Yes, you can update the RITM stage by using the flow in two ways.

1. Updating the stage field  of the RITM

Make sure that you've created the choice value "Closed rejected" under stage field.

2. Adding the flow stage

Hover b/w the two steps. You'll get an option to add a stage

Hope this helps.
Regards,
Siva

[AbbasP]

Thanks @J Siva ,

This is what I have currently. I am looking to solve my initial issue of how to update the stage from waiting for approval to request cancelled if all the child tasks are rejected.

[AbbasP · Accepted solution]

All,

For those having the same issue, I was able to find the solution by building another subflow. Details of how this can be done was shown in another post in the community:

Solved: Re: Flow - How to properly wait for ALL sc_task re... - ServiceNow Community