Skip to main content

Workflows

A workflow is the list of steps that turns one kind of email into finished work in MCS: a supplier invoice, a breakdown report, an off-hire request.

You build workflows yourself in the app, in Workflows, from a fixed set of step types. No code is needed. See the workflow editor.

What a workflow looks like​

A workflow is read from top to bottom, like a checklist. For example, a simple supplier invoice workflow:

  1. Identify the contact: known suppliers only
  2. Read the documents: Invoice
  3. Check: required values, totals, bank details unchanged, not a duplicate
  4. A person approves: until the sender is trusted
  5. Create in MCS: Incoming invoice
  6. File in MCS: the original email, on the new invoice

There are no hidden jumps. Where a workflow needs to go one of two ways, a choice runs one of two sets of steps and then carries on. See example workflows for more.

Workflows are data, not code​

Everything about a workflow (its fields, steps and settings) is set in the editor. Nothing about a particular kind of email is built into Rent Stream AI, so you can build a workflow for any kind of email your business receives.

How a workflow gets its mail​

A workflow is fed by a virtual mailbox. A workflow only takes mail once it is published and switched on. Until then, mail for it waits in To sort.

Versions​

Workflows are versioned. Changes are made in a draft, tested on real emails, then published. Work items already running finish on the version they started on. See testing and publishing and versions.