Workflows Management refers to selecting different management options available for a workflow display name, version and timestamp and applying them to have a better management of the workflow structure.
Edit Info Element
A workflow is represented by a three level structure: display name, version and timestamp. The edit option is available for all three levels of a workflow. In order to edit a workflow's display name, right click over it and select the Edit option, as seen below:
The Edit display name window will be opened. Type in the new display name, select language and click Save:
In order to edit a workflow's version, right click over it and select the Edit option, as seen below:
The Edit Version window will be opened. Type in the new version and click Save:
In order to activate/deactivate a workflow's timestamp, right-click over it and choose the Activate/Deactivate option.
In order to edit a workflow's timestamp, right-click over it and choose the Edit option.
The Edit Workflow wizard will be opened. The Edit Workflow wizard consists of three different steps.
- Step 1/3: on this step, all workflow details can be changed, except the workflow's Filename. Click Next to go to the next step, or Finish to complete the editing.
- Step 2/3: on this step, user permissions can be changed for the timestamp. Click Next to proceed to the next step, Previous to go back to the previous step or Finish to complete the editing of the workflow. Click Close to abort the current operation.
- Step 3/3: this step only presents the editing summary. Click Previous in order to go back to the previous step (if other changes are necessary) or Finish in order to complete the workflow editing process. Click Close to abort editing process.
Delete Workflow
The edit option is available for all three levels of a workflow. The deletion can be done by right clicking over a workflow display name, version or timestamp and select the Delete option.
Assign Workflow To Category
This option is only available on the timestamp level. In order to assign a workflow timestamp to a different category, right click over it and select the Assign To Category option:
If the timestamp display name does not exist on the new category, it will be created once the assignment is completed.
Converting a snippet workflow into a workflow can be done by assigning the snippet workflow to a new category, different than Snippets category or by cloning (option only available in Flowster Designer) a snippet workflow and selecting a different category than Snippets category.
NOTE: converting a workflow to a snippet workflow can be done the same way, by changing the parent category of the workflow into Snippets category.
- List Of items
The list of items which have been successfully loaded is displayed per tenant. These items are loaded to compare the matching dependencies of the staging workflow. The user can select to Add/Overwrite/Skip the conflict dependency.
E.g. if the workflow has a global variable as dependency and the destination tenant has a global variable with identical name, the user has the option to solve the conflict by skipping/overwriting the value of that global variable.
When the loading of items is finalized, for each tenant selected a new tab will be displayed with a sub-menu to select:
- Destination Category
User can select the destination category for the workflow to be transferred (displayed the list of categories from the destination tenant, where the staging user has rights). It is mandatory to select one category:
- Global Variables
User can visualize the conflicts between the workflow’s global variables/attributes dependencies and the destination tenant’s items. In the following example, the workflow to be transferred has one global variable, that already exists on the destination tenant so the user must solve the conflict by selecting Overwrite/Skip option:
- Snippets
User can visualize the conflicts between the workflow’s snippet dependencies and the destinations tenant’s items. If the dependent snippets have nested snippets, user can decide to solve conflicts on each level of nesting. In the following example, the workflow to be transferred has a snippet as dependency with two level nested snippets, but the dependent snippet already exists on the destination tenant, except the third level nested snippet, therefore user must solve the conflict by selecting Add/Skip option:
- Scripts
User can visualize the conflicts between the workflow’s scripts dependencies and the destination's tenant’s items. In the following example, the workflow to be transferred has two scripts as dependency and none of the scripts versions exist on the destination tenant so they will be automatically added without conflicts:
- Profiles
User can select which profiles to be added to the destination tenant. The last selected profile will be automatically applied:
- Scheduled Workflows
Users can check which scheduled configuration of the workflow should be transferred. If the workflow is not currently scheduled, this list will be empty.
- Miscellaneous
User can check the Make workflow active after transfer option to configure the Is Active setting to ON for the timestamp transferred.
User can check the Same settings for all Tenants option to apply all the settings (conflicts resolution) for each selected tenant.
- Next -> Summary
The list of selected workflow’s dependencies is displayed in the Summary page. The staging process will start after clicking on Finish button. Users can follow the operations performed during staging:
