Skip to main content
It would not be useful if your workflows always ended prematurely each time someone rejected a task you assigned them as part of that workflow. So as you build your workflow, you can specify different outcomes based on whether someone approves or rejects a task.  In case of a rejection, you can:
  • re-direct the workflow to a previous task outcome step;
  • assign a general task to another individual before redirecting to a previous task outcome step; or
  • end the workflow
A common example — a contract approval process Relay moves the contract along until it arrives at the desk of the group Vice President. The VP is unhappy with the terms stated in the contract, and rejects it, advising in a comment that they want to make certain changes. In this case Relay has been configured to send the contract back to the originating sales rep via a general task assignment. The sales rep revises the contract, thus completing the task, and Relay routes the workflow to a previous approval task outcome to go through the process again. Here’s what that workflow could look like, in sequential order: Trigger: File uploaded to folder labelled Contracts for Review. Outcome 1: General task to sales rep to update file. Outcome 2: Approval task to sales manager.
  • if rejected: Go to outcome 1
  • if approved: Go to next outcome (outcome 3)
Outcome 3: Approval task to sales VP.
  • if rejected: Go to outcome 1
  • if approved: Go to next outcome (outcome 4)
Outcome 4: Move file into folder labelled Final Contracts. Notes When assigning tasks, try to keep folder permissions in mind.  It is possible that when a task is rejected and returns to an earlier task assignee, the file that is the subject of the workflow will have moved to a folder to which the earlier assignee may not have access. Related Links