Workflow aggregation is part of the version control system. It works like configuration packs and uses VCS records as well. However, workflow aggregation has its peculiarities.
Role required: admin.
Concept
Workflow consists of the following elements:
- workflow activities
- transitions
- activity exits
- workflow version
Yet, when working on a local pack for further implementation, you do not have to include them one by one. Instead, the system compiles record versions of all these entities into one VCS record after publication.
The scheme below represents a simplified process of workflow export and import. Refer to the following articles to learn more:
Workflow import does not differ from common import process. See the Importing configuration packs to learn more.
Exporting workflow
There are two ways to prepare a workflow for exporting and implementation:
- create a local pack and start configuring a workflow
- move the workflow VCS record to the local pack you need
Development in local pack
To create a workflow within 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 will be put in the current local pack. It is ready for export and implementation.
Moving version between packs
To move a 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 changes.
As a result:
- The workflow VCS record will be put in the current local pack. It is ready for export and implementation.
