A workflow lives in test and production at the same time, but you can only edit it in test. With Publish you put the current test version into production as a new version. Earlier versions are kept; you can roll back to an earlier version.
How to publish
- Open the workflow in the test environment, save your changes and check that there are no validation errors. Publish is disabled while the editor has unsaved changes.
- Click Publish. The version that is open in the editor is the version you publish.
- Choose the client you publish to. If there is only one target, it is already selected. Next to each client you see which version is live there now, or that nothing is published yet.
- Check the overview of changes and confirm. The new version gets a sequence number.
Environment-specific settings (templates, task lists, labels, settlement profiles) are translated to their counterparts in production when you publish. If a counterpart is missing, the portal tells you before you publish.
Running collection orders
Collection orders that are still running when you publish keep running. You do not choose a strategy for them when you publish.
Rolling back
- Open the workflow and choose Versions.
- Open an earlier version and click Publish. The earlier version becomes the active version again; the version in between is kept.
Good to know
- A workflow that was never published only exists in test and cannot be chosen in production (also not as the starting workflow).
- A change in test only shows in production after you publish. Do not forget this after a small change.
- Workflows with active collection orders can still be changed; always test a change with a few collection orders first.
- Publish is not available when there is no client to publish to.