Skip to main content

End with Rejection Action

End an approval workflow with a Rejected status so the request owner can edit and resubmit the form.

Use End with Rejection on the route that handles a rejected approval task.


Connect the rejection branch

Open the workflow designer and add the end node to the rejection branch.

  1. Draw a line from Assignment Task to End with Rejection.

  2. Select the line and open its settings with the gear icon.

  3. In Condition editor, select Add Condition and choose Rejected. The condition is Outcome == Rejected.

  4. Select OK to save. Connect the approved outcome to its own next step.

Workflow example. Line Manager Approval sends Rejected to End with Rejection and Approved to the next step on the approval branch.


Configure the end action

Select End with Rejection and open its Settings.

  • End the process after reaching this node. Select this option to stop the workflow when this branch reaches the node. This also ends active activities in other branches.

  • Enable email. Turn this on to notify recipients when the workflow reaches the rejection end. Review and customize the sample email content before saving.


How parallel end actions are resolved

If parallel branches reach End and End with Rejection at the same time, the rejection takes priority. The workflow ends as Rejected even if the normal End node is also set to stop it.


Test the rejection route

Reject a test request and confirm its status changes to Rejected. Check that the request owner can open, edit, and resubmit the form. If you enabled email or termination of other active activities, verify those results too. Approve a separate test request to confirm it follows the approval branch.

Did this answer your question?