The workflow aggregation is part of the version control system. It works like configuration packs and also uses VCS records. However, the workflow aggregation has its specific features.
Role required: admin.
Concept
A workflow consists of the following elements:
- workflow activities
- transitions
- activity exits
- workflow version
However, when working on a local pack for further implementation, you do not need to include them one by one. Instead, the system compiles record versions of all these entities into a single VCS record after the publication.
The scheme below represents a simplified process of workflow export and import. See the following articles to learn more:
The workflow import is the same as the common import process. See the Importing Configuration Packs to learn more.
Export a workflow
There are two ways to prepare a workflow for export and implementation:
- create a local pack and start configuring the workflow.
- move the workflow VCS record to the local pack you need.
Pack a workflow
To create a workflow in a local pack, perform the following steps:
- Navigate to Configuration → Local Packs.
- Click New and fill in the fields.
- Click Set Current and Save to make this local pack current.
- Navigate to Workflow → Workflow Editor.
- Click New and configure the workflow.
- When the workflow is completed, open the hamburger menu
and click Publish.
As a result:
- The workflow VCS record is put in the current local pack. It is ready for export and implementation.
Move versions between packs
To move the workflow VCS record to the local pack you need, perform the following steps:
- Navigate to Configuration → VCS Records.
Find the workflow by its title in the Document Record column.
- Open the record.
- In the Local Pack field, select the local pack you need.
- Click Save or Save and exit to apply the changes.
As a result:
- The workflow VCS record is put in the current local pack. It is ready for export and implementation.
