Best practices for workflow design

Follow these practices so your workflows run well and fit your needs. To build a workflow first, see Create a workflow.

Give each step at least one action

A workflow can have many steps. Give each step at least one action that leads to another step. Otherwise the workflow gets stuck at that step, or has no destination at the end.

Keep at least one path from START to END

Each workflow needs at least one path from START to END. A path is a series of steps linked by actions. Without one, the workflow circles back through the same steps and never ends.

Assign the Responsible Company, and the user later if needed

Each step has two assignee fields: Responsible Company and Responsible User.

If you are not sure who is responsible for a step, assign only the Responsible Company. Leave the Responsible User empty.

While the workflow runs, you can then assign a user from that company.

In short, you can start or schedule a workflow without responsible users, and assign them during the workflow.