Skip to main content
Administration → Approval workflows is where you decide which actions need a signature before they happen — a purchase order over a value, a new asset category, a work order moving to closed — and who signs each step. One approval engine serves the whole product: requisitions, purchase orders and requests for quotation are held by exactly the same mechanism described here (see requisitions). The approval workflows screen, with the list of workflows and the selected workflow's version, roles, condition and chain The approval workflows screen, with the list of workflows and the selected workflow's version, roles, condition and chain To see which chains are running or stuck, use Workflow activity. The approvals themselves are made on Approvals.

Who can use this screen

Copy also needs Add rules, and Delete needs Remove rules. Each button is only shown to people who hold its permission.

The list

Nothing is held for approval — every write goes straight through means no workflow exists yet.

Creating a workflow

The New workflow dialog The New workflow dialog It starts turned off. Nothing is held until a version is published. Some acts can be held in more than one way — a register’s move can be made by two different actions, for example — and then each way is offered as its own choice, with a sentence under it saying what it holds: “Some of these can be held in more than one way, and each way is its own chain. The sentence under each says which one it holds.” A chain on one way is never asked about the other. If another chain on the same act already has the same name, the dialog warns you: two are allowed — a value ladder is one chain per rung — but a name that says which rung this is will be easier to find again. Create the draft saves it; Cancel closes the dialog.

A workflow’s page

Selecting a workflow shows its page. The header reads Held on [register] · [act] — with the sentence saying which way it holds the act, where there is more than one — and Showing version N · published/draft, with when and by whom it was published.

Who can trigger this

Role(s) narrows which people’s actions the workflow holds; roles held only by service accounts are not offered. No roles chosen — this workflow applies to everyone. Select all ticks every role. Use it, for example, to hold a technician’s request but let a manager’s go straight through.

With each decision

What every approver on the chain is asked for beside their decision, under With each decision: “Shown to every approver when they approve or reject. A rejection always asks for a remark. A file given here is kept with the approval, not on the record. A file is not asked for when several requests are approved at once from Approvals.” These belong to the workflow rather than to a version, like Who can trigger this, so a change reaches requests already in flight at their next decision without publishing a draft. See deciding a step for what the approver sees.

When does this workflow run?

The condition on the whole chain decides whether this chain holds a given request at all. An empty condition means every request for this action is held. When it does not hold, this chain is not asked at all and the next one down the list is. The builder is the same one rules use. Clauses can read the record’s own fields, its custom fields (… (custom field)), its status and, for an edit, a field’s value before the edit (… (before the edit)). On a status change, it can also read where the move is going: The status being moved into, The category being moved into, The status being left and The category being left — so “anything moving into Retired is signed off” is one clause. Status (the record’s) on a move is the status being left. A chain whose condition names the move asks for a signature by itself, without a rule having to require one. Save the condition writes it (on a draft).
Every clause needs a field and a value. A condition the server cannot read holds every request rather than none — so the chain would ask for a signature on everything.

Several chains on one act

A register and act can carry more than one chain — a ladder, checked in the Asked at order, each with its own condition. The first whose condition holds takes the request. A requisition that signs differently above a threshold is written as two or three whole chains rather than one chain that branches. A published purchase order workflow, with a condition on the total amount, a single step and Edit as a new draft A published purchase order workflow, with a condition on the total amount, a single step and Edit as a new draft

The chain

The chain is drawn as steps and arrows, because the order signatures come in — including two steps that must both close before a third opens — is a shape a list cannot show. A published version says Published — open a draft to change it. Tell the requester, above the chain, says whether whoever raised a request is emailed as each level approves it — At every level — or Only at the end. It is read off the steps: it reads At some levels where only some of them are set, with how many, for example 2 of 3 levels tell the requester. Turn this on to tick them all. Turning it on ticks every step that needs a decision; turning it off unticks them. Change it for one step in that step’s settings. The requester is always told once the whole request is approved, whatever this says. Changed on a draft. A rejection at any step ends the whole request; the steps behind it are never decided. An approver can also roll a request back to the level before theirs, send it back to whoever raised it for revision, or forward their place on the step to somebody else — see the five answers. Publishing is refused, with a message saying why, when a version has no first step, when a step cannot be reached from the first, or when a step names nobody to sign. A step its only signer’s own request would stop at. Nobody may sign a request they sent, so a step whose only possible signer is also allowed to send requests is a step every request of theirs waits at forever. Such a step is drawn on the chain in the on-hold colour, and a list under the chain names it: “If … sends a request, it will wait at this step forever: nobody may sign a request they sent, and this step cannot be signed without them.” The step’s own settings say the same, with the three ways out: name somebody else who can sign it as well, turn on The raiser may sign this step if signing it is their own authority, or leave them out of Who can trigger this. It is worked out from the roles people hold today, so it is a warning rather than a refusal — Publish stays open, because a chain that is short of a second signer may be exactly what was meant until one is hired.

A step’s settings

Add somebody who can sign adds an authority: Ask for this field adds a field to What this level asks for:

Copying a workflow

Copy opens Copy workflow: “The copy starts turned off, as a draft. Nothing is held until it is published.” The copy is of the version on screen — the draft while one is open, otherwise what is running. On the same register and act, the copy gets the steps, who signs each one, the fields each step asks for, the condition, the roles and what approvers are asked with each decision. It is asked straight after the original, so while the original is live with the same condition every request still goes to the original. Change the copy’s condition, or where it is asked, before publishing it. Copied to another register or act, the dialog checks what comes across before you press Copy. Approvers come across as they are, so check they suit the new register. Where requests there do not carry the fields the condition reads, the condition is left out — and a copy with no condition holds every request there once published, so set one before publishing. Fields a step asks for that the new register cannot ask the same way are left off their steps, and the dialog lists them. The copy is asked after any workflows already on that register and act.

Deleting a workflow

Delete removes a workflow on which no request has ever been raised. It asks “Delete …?” first and warns that the workflow disappears from the list with every version and step, and cannot be brought back — copy it first if it may be wanted again. A workflow that has held requests cannot be deleted, because the decisions taken on it are a record. Its Delete is greyed, and pressing it says how many requests it has held and to turn it off instead: switched off, it stops holding new requests and the decisions already taken stay on record.

Trying it before it is live

What would happen to a record walks the version on screen against a real record you choose (Pick the … to try it on, then Try it). Nothing is held, performed or written, and a draft can be tried before it is published. The answer lists each step as Would open, Would be skipped or Never reached, or says the chain would not take the record — its condition does not hold, so the action falls to the next chain or goes straight through. An unreadable condition holds the request rather than releasing it. For a Create workflow, the record does not exist until somebody asks, so a condition reading what is being asked for comes back unreadable in a trial — which means the chain would hold the request.

Draft and publish

A workflow is versioned. A draft can be reshaped freely; a published version cannot, because live approvals are already running against it.
Edit a live workflow and the edit lands on a new draft. Publish it and new requests use it; a request already in flight finishes against the version it started on, so changing the approvers never rewrites who signed something already underway.

While a request is open

A record with an approval open on it is held whole until the request is decided — or, once approved, until what was approved has been carried out. That includes a request that has been sent back to its initiator for revision: it has not been decided, and it comes back to the approver who asked. Every other change to it is refused, not just the one the workflow guards: a job waiting on a sign-off cannot be edited, moved or rescheduled underneath the person deciding it, and an asset waiting on a disposal cannot also be transferred. A pending transfer holds its asset the same way. The screens say so. On the asset, work order and work request registers and on the administration lists, a held row is tinted blue, its checkbox becomes a lock so it cannot be picked for a bulk action, and an Approval column names the request, linked to it. A line above the table says how many records on the page are waiting and that they cannot be edited or selected until the approval is decided. On the record itself, a banner says which approval holds it, and the controls that would be refused are withdrawn with the reason: This record is waiting for approval and cannot be changed yet. An import that creates records your workflow approves sends one request per row, exactly as the form would; rows on other sheets that name one of those records are refused until it is approved.