Activiti & Activiti Cloud Developers Guide
  • Introduction
  • Overview
    • 12 Factor Apps
    • Personas
    • Previous Versions (5.x & 6.x)
    • References
    • Cloud Native BPMN support
    • BPMN Comformance
      • BPMN Comformance Set 0
      • BPMN Comformance Set 1
      • BPMN Comformance Set 2
      • BPMN Comformance Set 3
      • BPMN Comformance Set 4
      • BPMN Comformance Set 5
      • BPMN Comformance Set 6
  • Getting Started
    • Getting Started - Activiti Cloud
      • Amazon EKS
      • Google Cloud GKE
      • Docker Compose
      • Jenkins X
        • Amazon EKS
        • Google GKE
    • Getting Started - Activiti Core
  • Components
    • Spring Cloud
    • Activiti Cloud Infrastructure
      • Gateway
      • Identity Management / Single Sign On
    • Activiti Cloud Application
      • Activiti Cloud Runtime Bundle
      • Activiti Cloud Connectors
      • Activiti Cloud Query Service
      • Activiti Cloud Audit Service
      • Activiti Cloud Notification Service
  • FAQs
    • Activiti Core FAQs
    • Activiti Cloud FAQs
  • BluePrints
    • Trending Topic Campaigns
  • Community
    • Roadmap
    • Repositories
    • Contributing
  • Releases
    • 8.2.0
    • 8.1.0
    • 8.0.0
    • 7.11.0
    • 7.10.0
    • 7.9.0
    • 7.8.0
    • 7.7.0
    • 7.6.0
    • 7.5.0
    • 7.4.0
    • 7.3.0
    • 7.2.0
    • 7.1.0-M17
    • 7.1.0-M16
    • 7.1.0-M15
    • 7.1.0-M14
    • 7.1.0-M13
    • 7.1.0-M12
    • 7.1.0-M11
    • 7.1.0-M10
    • 7.1.0-M9
    • 7.1.0-M8
    • 7.1.0-M7
    • 7.1.0.M6
    • 7.1.0 M5
    • 7.1.0 M4
    • 7.1.0 M3
    • 7.1.0 M2
    • 7.1.0 M1
    • 7.0.0 SR1
    • 7.0.0 GA
    • 7.0.0 RC1
    • 7.0.0 Beta5
    • 7.0.0 Beta4
    • 7.0.0 Beta3
    • 7.0.0 Beta2
    • 7.0.0 Beta1
    • 7.0.0 Early Access 201802
    • 7.0.0 Early Access 201801
    • 7.0.0 Early Access 201712
    • 7.0.0 Early Access 201711
    • 7.0.0 Early Access 201710
    • 7.0.0 Early Access 201709
Powered by GitBook
On this page
  1. Overview
  2. BPMN Comformance

BPMN Comformance Set 2

PreviousBPMN Comformance Set 1NextBPMN Comformance Set 3

Last updated 3 years ago

This scenario checks User Tasks and basic assignments properties. It also check the events generated by the Task Runtime. Task Operations are used to interact against Task resources. The .

    • We should be able to start the process and check that the Status after start is RUNNING

    • This process instance has a concrete assignee: “user1”

    • We should query for the tasks for the assigned user and check that we get just one task

    • We should check that User2 doesn’t have any task

    • We should be able to get the task by id using User1

    • Start Process Operation:

      • PROCESS_CREATED

      • PROCESS_STARTED

      • ACTIVITY_STARTED

      • ACTIVITY_COMPLETED

      • SEQUENCE_FLOW_TAKEN

      • ACTIVITY_STARTED

      • TASK_CREATED

      • TASK_ASSIGNED

      • TASK_UPDATED

    • User1 should be able to complete the task

    • Task Complete Operation

      • TASK_COMPLETED

      • ACTIVITY_COMPLETED

      • SEQUENCE_FLOW_TAKEN

      • ACTIVITY_STARTED

      • ACTIVITY_COMPLETED

      • PROCESS_COMPLETED

    • We should be able to start the process and check that the Status after start is RUNNING

    • This process instance has no concrete assignee

    • We should query for the tasks for the candidate user and check that we get just one task

    • We should check that User2 doesn’t have any task

    • We should be able to get the task by id using User1

    • We should check that User2 cannot get the task by id

    • Neither User1 or User2 should be able to complete the task before having an assignee set (different errors User2 not found, User1 cannot complete without assignee)

    • User1 should be able to claim the task

    • After claim the assignee should be set

    • If User1 is an assignee he/she should be able to complete the task

    • We should check that the assignee was removed after release

    • Start Process Operation:

      • PROCESS_CREATED

      • PROCESS_STARTED

      • ACTIVITY_STARTED

      • ACTIVITY_COMPLETED

      • SEQUENCE_FLOW_TAKEN

      • ACTIVITY_STARTED

      • TASK_CREATED

    • We should get the following events after claiming the task

    • Claim Task Operation:

      • TASK_ASSIGNED

      • TASK_UPDATED

    • We should get the following events after releasing the task

    • Release Task Operation:

      • TASK_COMPLETED

      • ACTIVITY_COMPLETED

      • SEQUENCE_FLOW_TAKEN

      • ACTIVITY_STARTED

      • ACTIVITY_COMPLETED

      • PROCESS_COMPLETED

    • We should be able to start the process and check that the Status after start is RUNNING

    • Start Process Operation

      • PROCESS_CREATED

      • PROCESS_STARTED

      • ACTIVITY_STARTED

      • ACTIVITY_COMPLETED

      • SEQUENCE_FLOW_TAKEN

      • ACTIVITY_STARTED

      • TASK_CREATED

    • This process instance has no concrete assignee

    • We should query for the tasks for the candidate user and check that we get just one task

    • We should check that User2 doesn’t have any task

    • User1 should be able to claim the task

    • The task status should be ASSIGNED

    • User1 should be able to release the task

    • The task status should be CREATED

    • Claim Task Operation

      • TASK_ASSIGNED

      • TASK_UPDATED

    • Release Task Operation

      • TASK_ASSIGNED

      • TASK_UPDATED

    • We should be able to start the process and check that the Status after start is RUNNING

    • This process instance has no concrete assignee

    • We should query for the tasks for the candidate group Group1, User1 and User3 get one task

    • We should check that User2 doesn’t have any task

    • We should be able to get the task by id using User1 and User3

    • We should check that User2 cannot get the task by id

    • Neither User1 or User2 should be able to complete the task before having an assignee set

    • User1 should claim the task

    • User3 will no longer see that task because it was assigned to User1

    • Start Process Operation

      • PROCESS_CREATED

      • PROCESS_STARTED

      • ACTIVITY_STARTED

      • ACTIVITY_COMPLETED

      • SEQUENCE_FLOW_TAKEN

      • ACTIVITY_STARTED

      • TASK_CREATED

    • Claim Task Operation

      • TASK_ASSIGNED

      • TASK_UPDATED

    • Release Task Operation

      • TASK_COMPLETED,

      • ACTIVITY_COMPLETED

      • SEQUENCE_FLOW_TAKEN

      • ACTIVITY_STARTED

      • ACTIVITY_COMPLETED

      • PROCESS_COMPLETED

    • We should be able to start the process and check that the Status after start is RUNNING

    • Start Process Operation

      • PROCESS_CREATED

      • PROCESS_STARTED

      • ACTIVITY_STARTED

      • ACTIVITY_COMPLETED

      • SEQUENCE_FLOW_TAKEN

      • ACTIVITY_STARTED

      • TASK_CREATED

    • This process instance has no concrete assignee

    • We should query for the tasks for the candidate user and check that we get just one task

    • We should check that User2 doesn’t have any task

    • We should be able to get the task by id using User1

    • We should check that User2 cannot get the task by id

    • Neither User1 or User2 should be able to complete the task before having an assignee set

    • Claim Task Operation

      • TASK_ASSIGNED

      • TASK_UPDATED

    • Release Task Operation

      • TASK_ASSIGNED

      • TASK_UPDATED

    • User3 and User1 should be able to see the task again after release

    • We should be able to start the process and check that the Status after start is RUNNING

    • Neither User1 or User2 should be able to see any task, due the task has no assignee, candidateUser or candidateGroup

    • A user with ACTIVITI_ADMIN role should be able to see the task, but more on Admins later

    • A process creates a task and the user execute delete on it

    • The user is the assignee of the task, so no need to claim

    • Calling delete on a task that belongs to a process should produce an ActivitiException: “The task cannot be deleted because is part of a running process”

    • A process creates a task and the user execute delete on it

    • The user is the candidate of the task

    • Calling delete on a task that belongs to a process should produce an ActivitiException

  • TBD

  • TBD

source code of these tests can be found here
User Task with User Assignment
User Task with Candidate User
User Task with Candidate User Claim & Release Task
User Task with Candidate Group
User Task with Candidate Group Claim & Release Task
User Task without Assignments
User Task For Assignee Delete
User Task For Candidate Delete
User Task Details
User Task With Data / Variables