Hi @nikitapatel
1. NEVER make changes to a LIVE SYSTEM unless you are certain of what you are doing
2. GOLDEN RULE. Always make a backup.
Export the Form.
Export the Workflow.
Copy the Form and Workflow files to a USB Thumbdrive.
3. You should attempt to duplicate the workflow to a TESTING or DEVELOPMENT SYSTEM.
Copy the List structure, the form and the workflow to the Testing system.
Make the changes and test it there.
Once you have done the above 3 steps, Here is what you need to do next
The highlighted Run-if is preventing the rest of the workflow to run when the FPAD Rejects (or does not Approves).
There is 2 possible ways to continue.
a) Add another condition to the existing condition.
I suggest you to refer to the top Run-IF FPAD Rejected condition.
FPAD_Approval Equals "Approved" (Pls check the exact term - "Approve", "Approves")
OR
FPAF_Approval Equals "Rejected" (again, pls check the exact term)
b) Add an Action Set
Drag all the actions in the Run-IF FPAD Approved action into the new Action Set.
Collapse any action that can be collapsed and drag it.
Be sure to retain the exact structure.
Publish and test out the workflow in the Test Systems.
Once it working correctly, perform the changes to the Live system
Remember to make a backup prior to making any changes
Hi,
I tried option A in the sandbox environment however, it still ended the workflow and didn't proceed to the next set of approvers.
I also attempted option B and it failed to work as well
Hi @nikitapatel
Smart idea to try the sandbox environment.
1) Can you show what is the condition of both the original Run-IF?
Just want to verify that the exact words for the condition values.
2) Transfer all the item in the Run-If into the action set.
End result is:
All the actions inside the Run-if has been transferred into the action set.
Leaving an Empty Run-IF.
Hello,
I wanted to come back here and mention that after I made those changes, the workflow still continues after a rejection is made... but now... when the first approval task gets approved - it stops the workflow and completes it and doesn't move forward.
Today, the approver approved the first task, and it completed the workflow right there. It should have gone to the second and third approval tasks, but it didn't. Last time when the first approver rejected it completed the workflow and it didn't go to the second and third approver.
My requirements for this process are:
- There are 3 sets of approvals needed - whether they are approved or rejected
- Even if the first approval task is rejected/approved, the workflow has to continue sending out the notification email with the task to approve or reject until it reaches the last approver
Attached is how the process looks... please help with the best way to go about this.
