Space (Workflow)
A space (Workflow) is a configuration entity used to organize a business process (or a group of processes).
Depending on needs, a space can be:
- A support queue (Service Desk);
- A project that contains tasks;
- An approval queue for an electronic document management system;
- A deal funnel;
- A business unit (for example, the HR department) and the related processes (hiring, leave requests, and so on);
- Any other production or management process.
Each space corresponds to a separate tenant in the process engine .
This applies only when multi-tenancy is enabled in the cluster. While it is disabled, Cabinee substitutes the tenant with
<default>(camunda-eight-client.force-default-tenant), and all spaces share one process-engine tenant. This does not affect access control inside Cabinee itself.Spaces available to the user can be found in the Spaces navigation menu item or on the All Spaces page.
A new space can be created on the All Spaces page.
When a space is created (or edited), the system retrieves information from the process engine about process models published in the tenant associated with the space. Model keys are shown as a list in the Process key field when creating or editing a space.
Attributes
Owner (owner)
User
The space owner is a system user who performs the duties of the space owner (manager), a business unit lead, or a project lead. Selected from the system user directory.
The user who creates a space automatically becomes its owner unless another user is specified as the owner at creation time.
Space owner permissions:
- Full access to the space (edit and delete);
- Full access to all tickets in the space;
- Configuration of ticket types ;
- Configuration of ticket states ;
- Configuration of milestones ;
- Configuration of permissions ;
- Receiving notifications about new tickets in the space;
- Creating, editing, and deploying space artifacts
Name and code
String
- Name (name) - specified by the user at creation, displayed on the ticket page and in the navigation menu. Can be changed.
- Code (code) - generated automatically from the name. Can be changed.
Space code generation algorithm:
The maximum code length is controlled by a configuration parameter :
application.workflow.code-max-length=10
- If the name consists of several words, the first letters are taken (an acronym). For example, for Customer Onboarding the code is automatically generated as CO.
- If the name is a single word, that word is used as the code.
- In both cases, the code length is limited according to the code-max-length setting.
Process key (process key)
String
Process key is the bpmnProcessId of the model started for tickets in the space.
The value is chosen from a list: when creating or editing a space, Cabinee reads deployed process definitions via /v2/process-definitions/search, so only processes already present in the cluster appear. See Deploying models to Camunda 8
.
If the space uses several models, the key is set not here but on ticket types .
Active (Active)
Boolean
Active determines whether the space is available to system users. When deactivated, the space and related elements are hidden from the interface and remain available only to the system administrator or the space owner.
⚙️ Settings
To create a new space, complete the following configuration:
- Configure an outbound mail channel for sending notifications .
- Create or import a process model .
- (Optional) If the space is expected to use several different process models, configure the Ticket types catalog.
- Configure the Ticket states catalog.
- Grant Permissions to users or user groups that will work with the space tickets .
- (Optional) Configure the Milestones catalog.