The changes I applied to a workflow are not being executed; the behavior from a previous version persists. How can I fix this?
If after applying changes in the BPM (adding/modifying a Notification Task, adding/modifying a User Task, creating/modifying a Gateway, creating/modifying a Flow, etc.), these changes are not reflected in the behavior of the workflows (validation flows) of the Data Portal, it is advisable to review the following:
-
Verify that the workflow being worked on in the BPM is the same one being launched in the Portal, i.e., confirm that the workflow ID in the BPM matches the ID configured for the object sub-type and action being performed (Object Sub-types table in the configuration panel)
-
Verify in the BPM editor that the workflow has been validated (Validate) and deployed (Deploy)
-
Verify in the Activiti database tables that the deployed version corresponds to the workflow version
Sometimes Activiti does not correctly manage versioning and does not pick up the latest version of the workflow. In this case, the recommendation from Anjana Data is as follows (Important: steps must be followed in the order indicated):
-
Modify the ID and Name of the workflow, using a completely new name (Important: do not reuse old values)
-
Perform a Save As and save with the new name in the desired folder
-
Validate and deploy the workflow
-
Modify the Object Sub-types table in the configuration panel for the records to which the workflow should be applied, using the new ID
-
Clear caches from the configuration panel (Actions -> Clear caches)
How to configure a Workflow with automatic validation steps?
In many cases it can be very useful to configure automatic validations when certain conditions are met — for example, to manage automatic approvals when a request is made to access publicly available data. Even when the validation is automatic, it is necessary to configure a workflow (approval flow); the difference compared to others is that one or more validation steps will be automatic, meaning they will not require participation from a validator.
To configure automatic validation steps, the following must be set up:
-
Add a task (Create task) and configure it as a User Task
-
In the Field Injections tab of the created task, add 2 fields:
-
In the first position, the field “automatic” with the properties “Name”, “Type” and “Value” with the respective values “automatic”, “String” and “true”, as shown in the following screenshot:
-
Unknown Attachment
b. In the second position, the field “validatorRole” with the properties “Name”, “Type” and “Value” with the respective values “validatorRole”, “String” and “automatic”, as shown in the following screenshot:
Unknown Attachment
How to configure more than 2 parallel flows within a Workflow?
Currently BPMN does not support logical gateways with more than 2 parallel paths. To achieve the execution of more than 2 parallel flows, we must rely on the elements currently available and combine them appropriately. For this, we will use a logical gateway of type “Parallel Gateway”
Unknown Attachment
This logical gateway allows us to branch out 2 flows in parallel. To achieve the desired effect, we only need to combine several Parallel Gateways until we reach the required number of paths. The following image shows how the flow sends 3 notifications in parallel by combining 2 Parallel Gateways.
Unknown Attachment
When trying to validate a workflow I encounter an error stating it must be executable. What should I review in the configuration?
If, when validating a workflow, this error appears:
Unknown Attachment
It is necessary to review the workflow configuration to confirm that the Executable flag is checked:
Unknown Attachment