Business processes / Business Process
Deploy a business process
Select a published process version and make it available to a Legal Entity.
Select a screenshot to open the original image in a new tab. Organizations, names and records in the examples are Demo data; use the corresponding information for your own work.
Before you start
Prepare a published, company-wide shared definition version. Definitions owned by one Legal Entity are not selected through this shared-process catalog. You need deployment read permission and either create permission for a new deployment or update permission to change one. Making a process available does not grant start, definition-management, or task-completion authority.
Read the availability catalog
Read the Legal Entity selector together with the availability and selected-version columns. The available state and pinned v1 in the example identify what this entity can use. Publishing another version does not by itself establish that the selected version in this list changed; confirm the applied result.
Example: change the version for new work
Suppose a shared process has published versions 1 and 2, and one Legal Entity currently uses version 1. After applying version 2 for that entity, confirm the active version in the list. Work already started on version 1 keeps its bound definition, so the deployment list is not evidence that existing runs have changed.
Open deployments
Open Business Process → Business Process availability (/workbench/process/deployments) and choose a Legal Entity available to you. The list describes availability for that selection.
Find the process
Locate the process in the deployment catalog. Read its availability and current version. If it is missing, check whether an eligible published definition exists.
Review definition and version
Check the version choices and the intended process before applying a change. Select the specific published version you intend to use.
Create a deployment
- Select the entity that will use the process, such as DEMO-KR. This example uses Meeting room inspection · Shared.
- Open that row's three-dot Actions menu and choose Make available.
Check the row name before opening its menu so that you change the intended process.
- Check the process name and Version in the dialog. Select Version 1 for this example.
- Choose Make available and wait for confirmation.
The dialog applies a version to new work. It does not change work already running.
Change the active version
For an existing deployment, choose Change version, select the intended version, and apply it. This action requires update authority for the selected Legal Entity.
Compare before and after deployment
| Situation or review point | What to check and do |
|---|---|
| Legal Entity | Confirm the selected entity before changing it and read the same entity’s list afterward. |
| Active version | Note the intended published version and compare it with the list after success. |
| Running work | Existing instances keep their bound definition; the new deployment does not edit those runs. |
Confirm deployment
Read the same row in the same Legal Entity. The example now shows Available and v1 fixed, confirming that the selection was applied. A failed request is not evidence of a version change.
Confirm both the state and version before moving on.
Understand running instances
Deployment determines the version used for new runs that resolve through this deployment. Existing instances keep their bound definition; changing availability does not rewrite their steps. Review running instances separately when coordinating an operational change.
If something goes wrong
If no version is selectable, check publication and scope. If the action is absent, check create or update authority. If a save is rejected, reload the catalog and review the server message before trying again.
Learn more
More guides for this capability
Nexia Cloud OS
Deploy a business process
Select a published process version and make it available to a Legal Entity.



