Publishing and versions
Saving stores the editable definition. Publishing creates the executable contract for new runs.
Publish a definition
- Confirm that the builder reports Valid.
- Save the latest changes.
- Open More Actions and choose Publish.
- Confirm the publication prompt.
- Return to the definition grid and verify Published and the active version number.
Only users with the publish permission can make a version live. A definition can also be archived and later restored through the supported management actions or API.
Version history
Click Versions in the builder to see each stored version, its status, creator, publisher and timestamps. One published version is marked active.
Runs retain their definition version. If a workflow changes while an approval is open or a wait is pending, the existing run does not silently switch to the new graph.
Safe change process
For a production change, export the current definition, edit the draft, validate it, simulate every changed route, and publish during a controlled window. Trigger a known test case and confirm the active version and final run state.
Do not use a display-name edit as a substitute for a new business-process review. Changes to event names, expressions, switch cases, side-effect targets and task decisions can all change runtime behavior even when the canvas still looks similar.