Docs
Sign in

Workflows

Define multi-stage processes with stages, steps and requirements, publish versions, and move running processes from stage to stage.

A workflow is a named process that something moves through in stages, like a purchase request going from Draft to Manager review to Finance approval to Approved. You define the stages and the steps between them once, publish the workflow, and then every process that runs on it follows the same rules and can always answer “what stage is this at?”.

Where to find it#

Open Workflows from the sidebar. The page lists every workflow with a Live or Draft badge, what it applies to, how many processes are running or finished on it, and its live version number.

Key concepts#

Workflow
The definition of a process: a name, a key and the kind of record it applies to.
Version
Each workflow has numbered versions. A version is a draft while you build it and live once published. A live version can never be edited.
Stage
A place a process can be, such as “Manager review”. Every stage has a kind: Start, Step, Approval, Waiting, Finished, Rejected or Cancelled.
Step
A named move from one stage to another, such as “Submit for review”. A step can start from a specific stage or from any stage.
Blocked until
A requirement that must be met before a step can be taken: an approval, a finished checklist or filled-in fields.
Process
One record going through a workflow. It sits in exactly one stage at a time, and one record can only have one live process at a time.

Workflows or automations?

A workflow remembers where something is; an automation doesn’t. If you keep asking “what stage is this at?”, you want a workflow. If you want something to happen once when an event occurs, you want an automation.

Who can use it#

Permissions

automation.viewautomation.manage
automation.view lets you see workflows, their versions and running processes, and take steps on a process. Creating workflows, adding stages and steps, publishing and starting a new version need automation.manage. An individual step can also require its own permission, shown as a badge on the step.

Create a workflow#

  1. Fill in the new workflow form

    At the top of Workflows, type a Name such as “Purchase request”. The Key is suggested from the name (purchase_request) and you can change it. The key is how a process is started on the workflow, so it stays the same even if you rename the workflow later. Keys must be unique in your organization.

  2. Choose what it applies to

    Pick Applies to: Work items, Projects, Approvals, Requests, Documents or Business processes (the default). A process can only run on records of this kind.

  3. Create the draft

    Select Create. The workflow is created as a draft. Select Edit draft v1 on its row to start building it.

Build the stages and steps#

Add the stages#

  1. Name the stage

    Under Stages, type a Stage name. Its key is created from the name and shown next to the stage once added.

  2. Choose its kind

    Pick a Kind from the list below. Once a version has a Start stage, the Start option is disabled, because a workflow can only have one.

  3. Set a time limit, if you need one

    Optionally enter Overdue after (working minutes). Time is counted in your organization’s working time, not calendar time (see Business calendars). The stage then shows “Overdue after N working minutes”.

  4. Add it

    Select Add stage. Repeat for every stage.

KindUse it for
StartThe stage every process begins in. Exactly one per workflow.
StepAn ordinary working stage, such as “Drafting”.
ApprovalA stage where the record is waiting for someone to approve it.
WaitingA stage where the process is paused on something outside it, such as a supplier reply.
FinishedA successful ending.
RejectedAn ending where the request was turned down.
CancelledAn ending where the process was abandoned.

Add the steps between them#

  1. Name the step

    Under Steps, type a Step name, such as “Submit for review”. This is the label people see when they move a process.

  2. Choose where it goes from and to

    Pick From and To. Leave From as Any stage for a step that can be taken from anywhere. This is how a “Cancel” path is normally written, so you don’t have to repeat it on every stage.

  3. Say what has to happen first

    Under Blocked until, choose one of:

    • Nothing — always available
    • An approval comes through
    • The checklist is finished (offered only for workflows that apply to work items)
    • Some fields are filled in. Enter the field names under Which fields, separated by commas, such as cost, justification.
  4. Add it

    Select Add step. The step appears as “From stage → To stage”, with a badge for any requirement, such as “Needs an approval”.

Publish a version#

When the draft is ready, select Publish at the top of the version page. UnitX checks the whole definition first and refuses to publish, listing every problem, if:

  • there is no Start stage, or more than one;
  • there is no ending stage (Finished, Rejected or Cancelled), so nothing could ever finish;
  • a non-ending stage has no step leaving it, so a process could get stuck there;
  • a step leads to a stage that isn’t in this version.

Once published, the version is marked Live, the workflow’s badge changes to Live, and new processes use this version.

Change a live workflow#

A live version can’t be changed, because processes are already running on it and changing the rules underneath them would change decisions already partly made. To make changes:

  1. Start a new version

    On Workflows, select New version on the workflow’s row. The new draft starts as a copy of the live version. A workflow can only have one draft at a time; if one exists, its row shows Edit draft vN instead.

  2. Edit and publish the draft

    Add the stages and steps you need, then select Publish. New processes use the new version. Processes already running stay on the version they started on until they finish.

Select View live on a workflow’s row to open the version currently in use.

Watch and move processes#

The Running processes section at the bottom of a version page lists the processes on this workflow, ten at a time, with Previous and Next to page through. Each row shows the current stage, the kind of record and the start of its ID, and a status badge.

  1. Open a process

    Select a running process to expand it. You see every step available from its current stage.

  2. Read what’s still missing

    Steps that can’t be taken yet are still listed, with the reason next to them, for example “These still need a value: cost.”, “2 checklist items still to tick off.” or “Waiting on 1 approval.”. A blocked step stays visible so you can see what to do next.

  3. Take a step

    Select Take next to an available step. The process moves to the step’s To stage. If the step is refused, the message says why.

Note

A process is started for a specific record through the UnitX API, naming the workflow’s key and the record. There is no button to start one from this page. If nothing has started yet, the section says so.

Rules and limits#

  • A published version is never edited. Make a new version instead.
  • One live process per record at a time, so there is only ever one answer to “what stage is this at?”.
  • A process stops itself after 50 steps. That points to a runaway loop, not a long process.
  • A process can only start on a workflow that has a published version and applies to that kind of record.
  • Stages and steps can be added to a draft but not removed from this page, so plan the shape before you build it.

Troubleshooting#

“This workflow cannot be published.”

Something about the shape is wrong, such as no Start stage, no ending, or a stage with no way out. The message lists each problem. Add the missing stage or step and publish again.

“The conditions for that step are not met.”

The step exists, but something it depends on isn’t true yet. Steps are listed even when they can’t be taken, with the reason, so check the text next to the step.

“You do not have permission for this step.”

The step requires a permission your role doesn’t include. Ask someone who holds it to take the step, or ask an administrator about your role.

Why is there no Edit button on a live version?

Live versions can’t change. Go back to Workflows and select New version to get an editable copy.

Still stuck? Search the docs with ⌘K, open Help inside UnitX, or contact support.