Approval task
How-to9 minPractitioner
Before you start
An Approval task creates a task for a person or a role and stops the workflow until it is decided. Use it when a purchase order, a leave request or an RFx needs someone’s yes before work goes on.
When should I use an Approval task?
Section titled “When should I use an Approval task?”Use it for any decision a person must make. The step has two paths, Approved and Rejected. Put a Record manager on each to change the record, or a Send email to tell someone. For the full picture of tasks in App space, read Approvals and tasks.
Add an Approval task
Section titled “Add an Approval task”- Click + and choose Approval task. It sits in the Records group.
- Under The task, write the Title people will see and a Description.
- Choose a Priority: High, Medium or Low.
- Type the number of days in Overdue after.
- Under Who decides?, choose People, A role, A field on the record or Smart Script, and name who.
- Click + on Approved and on Rejected to add the steps that follow.
The Title people will see and a Description appear in the task.
Priority and Overdue after, counted from when the task is created.
Who decides? offers four ways to pick.
Rejected and Approved are the two paths out.
What do the settings do?
Section titled “What do the settings do?”| Setting | What it does |
|---|---|
| Title people will see | The task’s title. Plain text, or text with inserted data |
| Description | Shown under the title |
| Priority | High, Medium or Low |
| Overdue after | Whole days from when the task is created. After that the task is marked overdue |
| Who decides? | People, A role, A field on the record, Smart Script |
| Write back to the record | Optional: Set a stage on the record, Add the rejection reason to the record, Add the assigned user to the record |
| Advanced | Let the approver return it to the sender, Check the data with another workflow first, Open the record’s Smart view by default, Approve a different record than this workflow’s |
Who can decide?
Section titled “Who can decide?”- People: everyone listed sees the task. The first person to decide completes it for all.
- A role: anyone with that role can decide. The first decision counts.
- A field on the record: goes to whoever is in a User field when the task is created. Add a User field to the module first.
- Smart Script: returns one or more email addresses, separated by commas. Each must belong to a user.
Worked example: approve a new RFx
Section titled “Worked example: approve a new RFx”Omar’s RFx workflow starts when a record is created. An Approval task titled New RFx is set to High with Overdue after 2. One person decides. On Approved, a Record manager updates the RFx event. On Rejected, another one does.
- RFx created
- Approval task
- Approved: update status
- Rejected: update status
What should I watch for?
Section titled “What should I watch for?”- Overdue after marks the task overdue when its days pass.
- The stage and the assigned user are written when the task is created, so a stage works as “waiting for approval”. To set a stage on approval or rejection, add a Record manager on that path.
- Every write-back goes to the record that started the workflow, even when the task is about a different record.
- The rejection reason is written to the chosen field when the task is rejected.