Publishing releases a workflow version. Before publishing, test the intended paths and confirm that your edits have saved.
Prepare the draft
Open the Process Validator, fix errors, and review warnings. Check the workflow type, required Part associations, first step, references, fields, and trigger settings.
Use Preview for the process logic. Before production release, check signatures, saved records, and external integrations using an appropriate published test version and controlled test sessions. For a first draft, preview it first, publish it in the test environment, then run those real-session checks.
Start publishing
Click Publish in the header. The editor performs local and server validation.
If the button is unavailable, check edit permissions, read-only/locked state, and whether this version is already released. If the modal reports errors, resolve the specific issue and retry.
Complete the release details
Where the release form is shown:
Enter a meaningful release name.
Describe what changed and why.
Choose minor, major, or eco from the Change Type dropdown according to your version policy.
Supply the ECO number when choosing eco.
Submit the release.
The editor may offer a simplified first-release path. Follow the controls shown for the workflow's current state rather than expecting identical fields on every release.
Handle additional prompts
Variable compatibility: a referenced workflow can require variables that are missing or configured differently. Use the offered variable-management action where available. Some mismatches must be corrected in the referenced workflow itself.
Similar workflows: review a reported conflict involving the workflow type and Part mapping. Do not bypass it by changing a production association without understanding the intended mapping.
Related open forms: review any forms offered for resolution and select only those this release actually addresses. This is a separate record action associated with the release.
Parent workflows: after the child releases, review the parent-workflow republish choices and results. Check each parent that needs the new child version. A parent failure does not necessarily undo the child release.
Verify the release
The More menu groups workflow-wide actions. The capture shows a read-only example; availability can differ with the selected version and permissions.
Open More → Versions. Confirm the version and Live/Latest status, then preview the relevant version.
Launch a new test session through the intended route and check the version it actually uses. Work Order and revision policies can affect version selection; do not assume an existing session changes version merely because you published.
Compare, lock, or correct a version
Use More → Versions to compare versions or create a version from a chosen source. Use Workflow Settings → Actions → Lock Workflow Version when a fixed version is required.
If a released instruction needs correction, create/edit the appropriate draft, test it, and publish the correction. A History action or a source-version fork alone is not a replacement release.
Saving, history, and version locks
Saving preserves draft edits. History concerns editing states; Versions concerns workflow versions and releases. Creating a version from an older source does not itself release it. A version lock through Workflow Settings is different from the temporary editing lock held by another editor.