Need to develop a flow
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi Team,
I need to develop a flow for below requirement :
1.when RITM is created , a catalog task should be created and assigned to 'x' group. Once this task is closed , another task should be opened and it goes for approval.
2.if approval is rejected , first task should be reopened and once this is closed it should reopen 2nd task and again approval should trigger and this should go on till 2nd task approvals are approved and its closed complete.
3.once 2nd task is closed complete , then 3rd task should be created and on completion it should closed RITM.
I am good with workflow , but not sure on how to do this on flow . Please help me with this . I am stuck at 2nd point.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
I am able built whole flow , task 1 and wait till it gets completed. Then task 2 and approvals.
But if apporval on task 2 is rejected then task 1 should re open and after its completion , task 2 should open and approvals should go to requested state.
in workflow there is a activity called roll back for these kind of cases , where we can loop but in flow how do I do it ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
And reason to re open task 1:
there are documents submitted in task 1 , and in task 2 they are verified by approvers of task 2. if they are rejected task 1 is re opened and documents are re submitted and then task 2 is opened again.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi,
Instead of looping around and trying to reopen task 1 over and over again, I would suggest that you create a new task each time the approval-rejection happens.
This will be a much easier approach.
Also, you will need to configure some form of additional exit condition, to avoid an neverending loop of record creation and approval generation (without it the loop continues to generate records until the approval is approved, effectively denying a rejection to end the process).