Examples: Workflows | Anjana Data Documentación

The process of this workflow will be as follows:

The workflow is started (startEvent).
Notification sent to the owner role (Sent Notification Task).
Validation by the owner role (User Task).
Validation gateway.
The last processes in Anjana are executed before the workflow ends, whether the workflow has been approved or rejected (LastExecution Task).
Notification to the creating user (Sent Notification Task).
Activiti is notified of the cancelled workflow (Cancel Workflow Task).
Final notification that the workflow has been approved (Sent Notification Task).
Notification to the responsible party, informing them that the workflow has been rejected (Sent Notification Task).
End of the workflow (End Event).

Creation of an entity reducing the configured tasks. The validation task incorporates the sending of the relevant notification:

The process of this workflow will be as follows:

The workflow is started (startEvent).
Notification sent to the owner role and validation (User Task). For sending the notification, the notificationCode is included in the task in the same way as described for the SentNotification task type.
Validation gateway.
The last processes in Anjana are executed before the workflow ends, whether the workflow has been approved or rejected (LastExecution Task).
Notification to the creating user (Sent Notification Task).
Activiti is notified of the cancelled workflow (Cancel Workflow Task).
Final notification that the workflow has been approved (Sent Notification Task).
Notification to the responsible party, informing them that the workflow has been rejected (Sent Notification Task).
End of the workflow (End Event).

This reduction of tasks was achieved by merging the notification sending and the role validation into a single user task, configured as follows:

Workflow steps:

Workflow start (StartEvent).
Notification sent to the owner role for validation (Sent Notification Task).
Validation by the owner role (User Task).
The last processes in Anjana are executed before the workflow ends, whether the workflow has been approved or rejected (LastExecution Task).
Activiti is informed of the rejection (Cancel Workflow Task).
When the owner role approves, a notification is sent to the next validator role, the destination owner (Sent Notification Task).
Validation by the destination owner role (User Task).
Final notification to the creator (Sent Notification Task).
Final notification to the validator roles (Sent Notification Task).
End of the workflow (End Event).

The workflow steps are as follows:

Workflow start (StartEvent).
Notification sent to the data owner role for validation (Sent Notification Task).
Validation by the data owner role (User Task).
When the data owner role approves, a notification is sent to the admin role for validation (Sent Notification Task).
Validation by the admin role (User Task).
When the admin approves the workflow step, a notification is sent to the last role involved, compliance, for validation (Sent Notification Task).
Validation by the compliance role (User Task).
If the compliance role validates the last step, the internal Anjana processes that will change the organizational unit of the object are initiated (Last Execution Task).
Final notification to the creator (Sent Notification Task).
Final notification to the validator roles (Sent Notification Task).
If any validator role rejects the workflow, the internal Anjana processes are initiated (Last Execution Task).
Activiti is informed of the workflow cancellation (Cancel Workflow Task).
A KO notification is sent to the workflow owner (Sent Notification Task).
End of the workflow (End Event).

The process of this workflow will be as follows:

The workflow is started (startEvent).
Gateway for the following branching
Condition that checks whether the object to be validated is NOT a dataset (${OBJECT_SUB_TYPE != "DATASET"})
Notification sent to the data owner role and validation (User Task).
Notification sent to the admin role and validation (User Task).
If the admin role approves, the internal Anjana processes that will change the organizational unit of the object are initiated (Last Execution Task).
Final notification to the creator (Sent Notification Task).
Final notification to the validator roles (Sent Notification Task).
Condition that checks whether the object to be validated IS a dataset (${OBJECT_SUB_TYPE=="DATASET"})
Notification sent to the data steward role and validation (User Task).
Gateway for the following branching
Condition that checks whether the pi attribute of the object to be validated is true (${pi == 'true'})
Condition that checks whether the pi attribute of the object to be validated is false (${pi == 'false'})
Notification sent to the developer role and validation (User Task).
If any of the validators rejects the workflow, the internal Anjana processes are initiated (Last Execution Task).
Activiti is informed of the workflow cancellation (Cancel Workflow Task).
A KO notification is sent to the workflow owner (Sent Notification Task).
End of the workflow (End Event).