Book a Demo

Quick start: task assignment process

Step-by-step setup of the task assignment process in Cabinee (Task Tracker)

User Story (Context)

As a manager at the Drimis company,
I want to give assignments to employees and control their completion,
so that tasks are completed, deadlines are met, and company goals are achieved.

Solution: Model a business process for task assignments and create a space (Workflow) for it with supporting catalogs.


Prerequisites

  • Space (Workflow) owner permissions
  • A configured mail channel for sending notifications
  • A .bpmn process model Task Tracker
    task-tracker.bpmn (download the file)

Step 1. Create a space (Workflow)

  1. Go to Spaces → All Spaces
  2. Click Create
  3. Specify:
    • Name: Work tasks
    • Code: generated automatically, or enter it manually
    • Active: enabled
  4. Save the changes

Details: Space (Workflow)


Task Tracker process diagram

The BPMN model of the assignment process used in this setup is shown below:

Task Tracker process diagram

Process stages:

  1. The manager creates a ticket (assignment) and assigns an executor (New assignment)
  2. The executor takes the assignment into work (In progress)
  3. After completing the work, the executor submits the result for review (Under review)
  4. The manager reviews the result and:
    • returns the assignment to work — if rework is needed,
    • completes the assignment (Task completed)
  5. The assignment can be cancelled at any time.

Step 2. Import and publish the BPMN model

  1. Open the created space (Workflow) Work tasks
  2. Go to the ⚙️ Artifacts (Definitions) tab
  3. Click Create, select type BPMN, and import the task-tracker.bpmn file
  4. Rename the model from New BPMN to Task Tracker
  5. Click Save

The model is saved to the internal Cabinee repository. Deployment to the orchestration cluster is performed separately — Camunda Modeler, zbctl, or a CI step; see Deploying models to Camunda 8 :

zbctl deploy resource task-tracker.bpmn --address <camunda-host>:26500

Until the model is deployed to the cluster, its key will not appear in the list on the next step.


Step 3. Bind BPMN to the space (Workflow)

  1. Make sure the BPMN model is displayed in Artifacts
  2. Open the settings of the Work tasks space (Workflow) (⚙️ → Edit)
  3. Set the Process key field to: taskTracker
    (the key must match the process id in the BPMN model)
  4. Save the changes

Step 4. Configure ticket statuses (Ticket States)

  1. In the space (Workflow) settings, open the Ticket statuses tab
  2. Click Create and add statuses (by activityId from BPMN):
    • New assignment
    • In progress
    • Under review
    • Cancel task
    • Task cancelled
    • Task completed (mark as final)
  3. Configure the order and icons
  4. Make sure at least one status is marked as final

Details: Ticket statuses


Step 5. Assign permissions (Permissions)

  1. In the space (Workflow) settings, go to the Permissions tab
  2. Click + add group or + add user
  3. Add, for example, the Team group that participates in the process

Details: Permissions


Step 6. Testing

  1. Create a ticket, for example: Prepare a presentation for the meeting
  2. Make sure the process starts
  3. Check status changes and the available actions shown
  4. Complete the task and verify that the ticket close date is set