A collection order gets into a workflow in three ways: you state the workflow when you deliver it (file or API), you let the starting workflow of the client decide, or you start a workflow manually from the customer page.
When you deliver with a file
- Go to Send > Deliver collection orders.
- Choose the file and the file mapping.
- Choose the workflow (in production only published workflows). If you leave this empty, the starting workflow applies.
- Choose the start date and time and, if you want, a batch name, and process the file. See What is coming.
Through the API
When you create a collection order, send the field workflow_id. If you send flow_id, a classic flow starts; you cannot send both at once. You can only leave out both if the client has a starting workflow (or starting flow). See API v3.
From the customer page
- Open the customer page, tab Collection orders.
- For a collection order that is not running in a workflow, choose Start workflow; for a running one, choose Switch.
- Choose the workflow and confirm.
Starting workflow
The starting workflow is the default for collection orders that have no workflow given. You recognize it by the star in the workflow overview. A client has at most one; in production it must be a published workflow. See Workflow settings.
Good to know
- You do not start collection orders again that are already running in a workflow; use Switch.
- You can also move a collection order from a classic flow to a workflow with the classic flow step "Switch to workflow". See Migrating classic flows to workflows.
- The first node of a workflow runs right after the start, within the send times of the client.