Flow Designer 'Cancel' flow requirement.

[B_3]

Requirement: Need to do via Flow Designer.

1) Need to update the State/Stage of RITM and Parent Request if RITM gets cancelled before Approval. (This is when 1 REQ has 1 RITM)

2) Only update the parent Request state to 'Cancelled' if all child RITMs are cancelled. (If 1 REQ has multiple RITM).

3) If parent REQUEST is cancelled (BEFORE APPROVAL ONLY) then all child RITMs (IF ALL NOT approved ) should be cancelled.

Having a Cancel button on portal for parent REQUEST (visible only if all child RITM's are pending approval) and for all individual child RITMs (visible only for those pending approval) so if 1 REQ has 1 RITM and if user cancel that RITM, state will be change to 'Cancelled' and that will be used as IF condition in Flow Designer.

We already have a flow designer working for Service Catalog (using as trigger) and is working for If Approved and If Rejected. Now we need Cancel flow in that designer as well but that too before approval.

[Allen Andreas]

Hello,

Thanks for posting your requirement.

• What have you tried thus far?
• What has worked/hasn't worked?
• What troubleshooting, etc. have you done?

Please mark reply as Helpful, if applicable. Thanks!

[OlaN]

Hi,

Your requirement doesn't make sense.
Why would a RITM/REQ be cancelled before the approval? Isn't that why you have implemented an approval in the first place? So that the approver can decide whether the RITM/REQ should be processed or not.

Then you handle the Flow so that if the approval gets rejected, then update the state/stage on the RITM to cancelled and so on.

Please explain the use case here.

[B_3]

Hello OlaN,

Thank you for your response.

There is functionality that is developed to show Cancel Button on portal against each RITM ONLY if it is not approved so that end user can cancel RITM if they want to ONLY if is it not approved.

Same goes for REQUEST, the cancel button will only appear if all the child RITMs are NOT approved.

One they cancel the RITM form portal the state will be changed to 'Cancelled' and the idea is to use the state change as trigger to cancel the pending approval than Stage then REQ state.

Same goes for REQ, if REQ is cancelled then respective child RITMs should be cancelled.

i.e., RITM state, approval and Stage should be changed.

[OlaN]

I see. Then you have implemented two ways of doing kind of the same thing.

If one is to press cancel button on the portal the Flow should be cancelled.

If one is to select reject on the approval, that would also lead to the same result, to cancel the Flow.

How about changing the behaviour of the Cancel button on the portal, so that when pressed, it would do the same thing, set the approval to rejected, then you would not need anything else to happen, it is already handled by your current flow.