Before you start

You need workflow-management permission. Available steps and integrations depend on your organisation’s configuration.

Step by step

  1. Open Orchestrations and choose the builder or an existing workflow you can manage.
  2. Define the intended outcome and trigger. Use a scope that matches the records and teams involved.
  3. Configure the available steps and their inputs. Include accountable owners and approval points for material decisions.
  4. Review the flow for missing inputs, access requirements and failure handling. Use the available validation or test path before activation.
  5. Monitor runs and open a run’s context to resolve blocked or failed steps.
Local product example · sample dataClick to enlarge ↗
Connect stages into an accountable business path

The example draft connects a trigger to Document Intelligence, an analyst review task and an approval decision. Select a stage to configure it. Connections and owner roles define the intended path; the example is not a published or executed workflow.

Use the Orchestrations workspace

Open Orchestrations in the menu. Active lists live/draft workflows; Templates provides starting points; Builder edits designs; My Work shows owned tasks and approvals. Workflows can coordinate business data, documents, integrations, AI and human decisions—not only evidence.

Build and validate a draft

  1. Name the intended outcome and define the trigger/inputs.
  2. Configure each step’s inputs, accountable role and outputs, then connect the intended routes.
  3. Check document source, OCR, classification and review/output settings where applicable.
  4. Save, Validate and inspect every reported item. Use Dry run before publication.
  5. Publish through the permitted action and verify the recorded version.

Design changes are not execution recovery

A successful dry run is not a live result. Inspect run status, step outcomes, mapped tasks and timeline. Removing a step changes the draft and does not undo past execution. Read the separate remove-step and run-recovery guides before changing a workflow with existing work.

What happens next

A workflow coordinates work; it does not bypass record permissions or required human decisions.

Local product example · sample dataClick to enlarge ↗
Tell the document stage which records to use

Workflow input reads document identifiers from the configured input variable. Other source modes use their own location reference and filters. Check that upstream stages supply the required values; leaving a filter blank does not create a connection to an external repository.

If something does not look right

If a run stops, inspect the failed step and its inputs. Resolve the recorded issue before retrying, especially where repeating an action could duplicate external activity.