Skip to main content

Approval task

Use the Approval task step to have a user or a group approve or reject something, and continue along the Approved or Rejected path. The flow waits until the task is decided – for hours or days if need be. How users, groups, the inbox and the waiting work is described in AutoFlow Tasks.

Typical use cases:

  • An incoming invoice above a limit needs the approval of two people from FINANCE.
  • A new vendor bank account must be confirmed by the purchasing manager before it is used.
  • A price change goes to the product manager, with the item and the price list attached.

Configure the step​

Description​

The step's label on the canvas – and the subject of the task in the inbox, so name it like the task: Approve invoice.

Instructions​

What the approver should check, shown on the task card. SmartFields are resolved when the task is created, so you can put the document number, the vendor and the amount into the text.

Assign to​

User or Task group.

Assignee​

The user name or the task group code. Pick one with the lookup, type it, or insert a SmartField that holds it – for example the purchaser of the document. An unknown or disabled user stops the flow with an error. Approvers need no AutoFlow Tasks seat – approvals are part of every paid AutoFlow license.

Approvals needed​

Shown for a task group: how many different members must approve. One rejection rejects the task right away. The group must have at least this many members.

Due date​

Optional. A date, or a SmartDate such as [@calc({{today}}, "+5D")@]. Overdue tasks are highlighted in the inbox, and users can get reminders and digests.

Attachments​

What the approver needs to look at. Each line is one of:

  • Record – a record from a SmartField, opened from the task card.
  • Document – an AutoFlow document or an incoming document attachment, shown in the preview.
  • Link – a web address, opened in a new browser tab.

If a line's SmartField holds a list – the result of Find records, for example – every element becomes an attachment. A line that resolves to nothing is left out. Caption names the attachment on the card.

Outputs​

OutputContent
resulttrue when approved, false when rejected – decides the path
approvedthe same as result
commentthe approver's comment; with several approvals, all comments
decidedBywho approved, or who rejected
taska reference to the task itself – for example to link it to the document or to report on it

A comment is optional when approving and required when rejecting.

Where the step is available​

The step is not available in flows that cannot wait for a person – the Document and Page triggers, the report triggers and sub-flows – see How a flow waits.