Allow an Approver To Reject a Submitted Section of an App

Why would you create a Rejection Branch?

By enabling rejection branches, you can create separate continuation routes for the initial user to traverse, for when their approver approves, or rejects the assessment. 

For example, the user is submitting a procurement request and is applying for an exemption from a regular process, so their application is accelerated through a simplified process. If the exemption is not justified, a reviewing manager (i.e. approver) can reject the exemption request and send the assessment down the normal path of a regular procurement process. In some circumstances, rejection branches can lead straight to the end of the assessment - e.g. if the procurement request is rejected and the submitter has no grounds to appeal this decision.



What’s the difference between a Rejection Branch and Sending back an assessment?

If the rejection branch is disabled and the approver rejects the user’s submission, the assessment is sent back to the user for resubmission. Users must repeat this process until the approver approves. However, if the rejection branch is enabled, the user will continue their assessment down a specified path regardless of whether their submission is approved or rejected by the approver.



How to Enable the Rejection Branch

  1. Click onto a Workflow block on your App

  2. On the right panel under “Configure Workflow Settings”, check the Rejection Branch checkbox

  3. The Workflow block will then have a green Yes and red No node which can be routed to different paths (as shown in the image below) or to the same path

Note: Inside the assessment, if the approver clicks “Accept”, the user will continue the assessment in the route flowing from the GREEN node. If the approver clicks “Reject”, the user will continue the assessment in the route flowing from the RED node.

19.png

Note: As mentioned above, it is possible to configure both your nodes to follow the same route. This will allow the user to continue the assessment on the same route regardless of whether their submission has been approved or rejected. See example below.

A situation like this happens rarely in our experience, but sometimes you want to capture the Approver’s decision by using the ACT variable that emulate Yes/No variables (e.g. ACT47==”Approve” or ACT47==”Reject”) associated with the Approval Workflow Block, so both Approve and Reject routes will lead down the same path. The outcome of the decision can simply be referenced using {{ACT2}}. Learn more on variables.

20.png



Related Articles