
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-10-2022 09:39 AM
I have a case in our Change Management where if a change gets rescheduled we kick off a new flow. The prior approval tasks are getting cancelled properly via a script, but when the new flow does the ask for approval for the group it is skipping that step. I am guessing because it sees that there was a prior approval for that same group on the RFC that was cancelled? Any ideas how to resolve this?
Solved! Go to Solution.
- Labels:
-
flow designer

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-11-2022 01:18 AM
Hi,
How about deleting those old approval records instead of setting them to cancelled.
Will that work for you?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-11-2022 01:18 AM
Hi,
How about deleting those old approval records instead of setting them to cancelled.
Will that work for you?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-14-2022 02:04 PM
I thought of that option as well, but sadly our Change Management team wants the prior approvals to be documented in the system even if they were cancelled because of the change in flow.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-15-2022 12:03 AM
Then I might suggest that you instead of setting the old approval records to Cancelled, set them to "No longer required"
That should work (not tested).

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-07-2022 02:42 PM
That was basically it. Since it is a group approval, I just added a query to look for the old group approval and delete it.