Examples: Workflows

Creating an entity (with a single validating role):

The process for this workflow is as follows:

1. Start of the workflow (startEvent).

2. Sending notification to the owner role (Sent Notification Task).

3. Validation by the owner role (User Task).

4. Validation gateway.

5. The final processes in Anjana are executed before the workflow ends, whether the workflow has been approved or rejected (LastExecution Task).

6. Notification to the creating user (Sent Notification Task).

7. Activiti is notified of the cancelled workflow (Cancel Workflow Task).

8. Final notification that the workflow has been approved (Sent Notification Task).

9. Notification to the person in charge, indicating that the workflow has been rejected (Sent Notification Task).

10. End of the workflow (End Event).

Creating an entity by reducing the configured tasks. The relevant notification is sent as part of the validation task:

The process for this workflow is as follows:

1. Start of the workflow (startEvent).

2. Sending notification to the owner role and validation (User Task). To send the notification, the notificationCode is included in the task in the same way as indicated in the SentNotification task type.

3. Validation gateway.

4. The final processes in Anjana are executed before the workflow ends, whether the workflow has been approved or rejected (LastExecution Task).

5. Notification to the creating user (Sent Notification Task).

6. Activiti is notified of the cancelled workflow (Cancel Workflow Task).

7. Final notification that the workflow has been approved (Sent Notification Task).

8. Notification to the person in charge, indicating that the workflow has been rejected (Sent Notification Task).

9. End of the workflow (End Event).

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

Adherence request (with two validating roles)

Workflow steps:

1. Start of the workflow (StartEvent).

2. Sending notification to the owner role for validation (Sent Notification Task).

3. Validation by the owner role (User Task).

4. The final processes in Anjana are executed before the workflow ends, whether the workflow has been approved or rejected (LastExecution Task).

5. Activiti is informed of the rejection (Cancel Workflow Task).

6. When the owner role approves, the notification is sent to the next validating role, the destination owner (Sent Notification Task).

7. Validation by the destination owner role (User Task).

8. Final notification to the creator (Sent Notification Task).

9. Final notification to the validating roles (Sent Notification Task).

10. End of the workflow (End Event).

Changing the organizational unit of an entity (with three validating roles)

The workflow steps are as follows:

1. Start of the workflow (StartEvent).

2. Sending notification to the data owner role for validation (Sent Notification Task).

3. Validation by the data owner role (User Task).

4. When the data owner role approves, a notification is sent to the admin role for validation (Sent Notification Task).

5. Validation by the admin role (User Task).

6. When the admin approves this step of the workflow, a notification is sent to the last role involved, compliance, for validation (Sent Notification Task).

7. Validation by the compliance role (User Task).

8. If the compliance role validates the last step, Anjana's internal processes that will change the object's organizational unit are started (Last Execution Task).

9. Final notification to the creator (Sent Notification Task).

10. Final notification to the validating roles (Sent Notification Task).

11. If any validating role indicates that it rejects the workflow, Anjana's internal processes are started (Last Execution Task).

12. Activiti is informed of the workflow cancellation (Cancel Workflow Task).

13. A KO notification is sent to the person responsible for the workflow (Sent Notification Task).

14. End of the workflow (End Event).

Creating an entity with attribute evaluation to allow branching (with validating roles dependent on the object to be validated)

The process for this workflow is as follows:

1. Start of the workflow (startEvent).

2. Gateway for the following branch

3. Condition that checks whether the object to be validated is NOT a dataset (${OBJECT_SUB_TYPE != "DATASET"})

4. Sending notification to the data owner role and validation (User Task).

5. Sending notification to the admin role and validation (User Task).

6. If the admin role approves, Anjana's internal processes that will change the object's organizational unit are started (Last Execution Task).

7. Final notification to the creator (Sent Notification Task).

8. Final notification to the validating roles (Sent Notification Task).

9. Condition that checks whether the object to be validated IS a dataset (${OBJECT_SUB_TYPE=="DATASET"})

10. Sending notification to the data steward role and validation (User Task).

11. Gateway for the following branch

12. Condition that checks whether the pi attribute of the object to be validated is true (${pi == 'true'})

13. Condition that checks whether the pi attribute of the object to be validated is false (${pi == 'false'})

14. Sending notification to the developer role and validation (User Task).

15. If any of the validators rejects the workflow, Anjana's internal processes are started (Last Execution Task).

16. Activiti is informed of the workflow cancellation (Cancel Workflow Task).

17. A KO notification is sent to the person responsible for the workflow (Sent Notification Task).

18. End of the workflow (End Event).