With versioning, you can easily track your process definition’s evolution.
Here is a quick walkthrough video:
Overview:
Streamlined Data Display:
Key Information Included:
View details like process definition name, published version branch name, and published version state with the following convention:
Actions:
“Branching Modal” feature provides more visibility and control over the process definitions. The process definition header includes details about the current version, such as its state (work in progress or submitted changes) and branch name.
A “publish icon” will be displayed if the current version is set as published. You can access the branching modal using a button, and it can also be closed from the right corner close button.
The Work-in-Progress (WIP) Versioning feature enhances the version control capabilities by allowing you to manage ongoing updates without interfering with already submitted versions.
You can initiate a new work-in-progress version while keeping the submitted version intact. A work-in-progress version is automatically created under the following circumstances:
You can submit changes exclusively on work-in-progress (WIP) versions. Changes can be submitted using the designated action within the version menu. Upon triggering the submission action, a modal window appears, prompting you to provide a commit message.
A string of maximum 50 characters, mandatory for submission. Only letters, numbers, and characters [] () . _ - / are allowed.
The placeholder indicating work-in-progress is replaced with a “submitted” state within the graph view.
You have the flexibility to modify submit messages after changes are submitted. This can be accomplished using the action available in the version menu.
Using versioning you can work on a stable copy of the process definition, isolated from ongoing updates by other users. You can create a new branch starting from a specific submit point. The initiation of new branches is achieved using the dedicated action located in the left menu of the chosen submit point (used as the starting point for the branch).
A string of maximum 16 characters, mandatory for branch creation.
You can incorporate updates made on a secondary branch into the main branch or another secondary branch. To ensure successful merging of changes, adhere to the following criteria:
The graph representation is updated to display the new version on the selected parent branch and the merged version is automatically selected, facilitating further development and tracking.
The Conflict Resolution and Version Comparison feature provides a mechanism to identify and address conflicts between two process versions that, if merged, could potentially disrupt the integrity of the process definition.
The system displays both the version to be merged and the current version on a single screen, providing a clear visual representation of the differences. Conflicts and variations between the two versions are highlighted, enabling users to readily identify areas requiring attention.
Not all changes are considered conflicts, changes in node positions are not treated as conflicts. Primary causes lie in identifying differences within business rules, expressions, and other scripts.
You can specify which version will run by default from a container app.
When a process is created, the default published version settings are as follows:
You can change the branch and version used as the default by the container app.
This is done through the following settings:
Branch: A dropdown menu displaying available branches (both opened and merged).
Version: The type of version that should be used:
Latest Work in Progress
Latest Submitted Work
Custom Version
Options are ordered reverse chronologically by submit datetime.
The Read-Only State feature allows you to access and view submitted versions of your process definitions while safeguarding the configuration from unintended modifications. By recognizing the visual indicators of the read-only state, you can confidently work within a controlled environment, ensuring the integrity of process definitions.
The “Open Audit View” provides you with a detailed audit log of actions related to work-in-progress (WIP) versions of a process. The primary goal is to ensure transparency and accountability for actions taken before the commit or save process.
You can quickly access and review the history of WIP versions, facilitating efficient decision-making and collaboration.
More details on how to use the audit log, you can find in the following section:
My Favorites feature allows you to mark processes as favorites. This is a convenient way to identify and prioritize processes that are important to, streamlining your workflow. With the addition of the favorite process feature, we have included a dedicated tab within the process definition list.
The “Open Audit View” provides you with a detailed audit log of actions related to work-in-progress (WIP) versions of a process. The primary goal is to ensure transparency and accountability for actions taken before the commit or save process.
In Favorites tab, the Branch tag will always display the most recently modified branch.
In My Favorites tab, the Branch tag will always display the most recently modified branch.
To add a process to the “Favorites” tab, simply follow these steps:
The “Copy version as new process” feature enables users to duplicate an existing process version as a new process definition. This functionality proves beneficial when initiating work on a use case closely resembling an existing process or when undertaking significant modifications to an existing process definition.
After copying the version and creating a new process definition, the following will happen:
For detailed instructions on exporting and importing process definition versions, please refer to the following section:
With versioning, you can easily track your process definition’s evolution.
Here is a quick walkthrough video:
Overview:
Streamlined Data Display:
Key Information Included:
View details like process definition name, published version branch name, and published version state with the following convention:
Actions:
“Branching Modal” feature provides more visibility and control over the process definitions. The process definition header includes details about the current version, such as its state (work in progress or submitted changes) and branch name.
A “publish icon” will be displayed if the current version is set as published. You can access the branching modal using a button, and it can also be closed from the right corner close button.
The Work-in-Progress (WIP) Versioning feature enhances the version control capabilities by allowing you to manage ongoing updates without interfering with already submitted versions.
You can initiate a new work-in-progress version while keeping the submitted version intact. A work-in-progress version is automatically created under the following circumstances:
You can submit changes exclusively on work-in-progress (WIP) versions. Changes can be submitted using the designated action within the version menu. Upon triggering the submission action, a modal window appears, prompting you to provide a commit message.
A string of maximum 50 characters, mandatory for submission. Only letters, numbers, and characters [] () . _ - / are allowed.
The placeholder indicating work-in-progress is replaced with a “submitted” state within the graph view.
You have the flexibility to modify submit messages after changes are submitted. This can be accomplished using the action available in the version menu.
Using versioning you can work on a stable copy of the process definition, isolated from ongoing updates by other users. You can create a new branch starting from a specific submit point. The initiation of new branches is achieved using the dedicated action located in the left menu of the chosen submit point (used as the starting point for the branch).
A string of maximum 16 characters, mandatory for branch creation.
You can incorporate updates made on a secondary branch into the main branch or another secondary branch. To ensure successful merging of changes, adhere to the following criteria:
The graph representation is updated to display the new version on the selected parent branch and the merged version is automatically selected, facilitating further development and tracking.
The Conflict Resolution and Version Comparison feature provides a mechanism to identify and address conflicts between two process versions that, if merged, could potentially disrupt the integrity of the process definition.
The system displays both the version to be merged and the current version on a single screen, providing a clear visual representation of the differences. Conflicts and variations between the two versions are highlighted, enabling users to readily identify areas requiring attention.
Not all changes are considered conflicts, changes in node positions are not treated as conflicts. Primary causes lie in identifying differences within business rules, expressions, and other scripts.
You can specify which version will run by default from a container app.
When a process is created, the default published version settings are as follows:
You can change the branch and version used as the default by the container app.
This is done through the following settings:
Branch: A dropdown menu displaying available branches (both opened and merged).
Version: The type of version that should be used:
Latest Work in Progress
Latest Submitted Work
Custom Version
Options are ordered reverse chronologically by submit datetime.
The Read-Only State feature allows you to access and view submitted versions of your process definitions while safeguarding the configuration from unintended modifications. By recognizing the visual indicators of the read-only state, you can confidently work within a controlled environment, ensuring the integrity of process definitions.
The “Open Audit View” provides you with a detailed audit log of actions related to work-in-progress (WIP) versions of a process. The primary goal is to ensure transparency and accountability for actions taken before the commit or save process.
You can quickly access and review the history of WIP versions, facilitating efficient decision-making and collaboration.
More details on how to use the audit log, you can find in the following section:
My Favorites feature allows you to mark processes as favorites. This is a convenient way to identify and prioritize processes that are important to, streamlining your workflow. With the addition of the favorite process feature, we have included a dedicated tab within the process definition list.
The “Open Audit View” provides you with a detailed audit log of actions related to work-in-progress (WIP) versions of a process. The primary goal is to ensure transparency and accountability for actions taken before the commit or save process.
In Favorites tab, the Branch tag will always display the most recently modified branch.
In My Favorites tab, the Branch tag will always display the most recently modified branch.
To add a process to the “Favorites” tab, simply follow these steps:
The “Copy version as new process” feature enables users to duplicate an existing process version as a new process definition. This functionality proves beneficial when initiating work on a use case closely resembling an existing process or when undertaking significant modifications to an existing process definition.
After copying the version and creating a new process definition, the following will happen:
For detailed instructions on exporting and importing process definition versions, please refer to the following section: