Skip to content
Linear flows, yes/no decisions, and parallel paths
Qisutu AddOn
Kim – Processes
A naturally written instruction becomes an editable BPMN process template for structured, email-driven service workflows.
Version1.0.1
CompatibilityQisutu 1.0.1 or newer
Languages11
LicenseAGPL-3.0-or-later
Module overview
Kim – Processes
The key use cases and capabilities at a glance.
Steps with queues, groups, states, services, SLAs, fields, and recipients
REST calls, response evaluation, reminders, and an immutable process copy per ticket
Create business processes with Kim and run them in tickets.
Create and edit process templates and configure every work step.
Kim instruction, BPMN model, and configuration for each work step
Start a stored process or inspect the current execution.
Capabilities in detail
Capabilities in detail
The following capabilities are part of this independent Qisutu module.
- Use “Action” to open the configuration for the respective work step.
- Available directly in the module: REST interface.
- Available directly in the module: Authentication.
- Available directly in the module: Response mapping.
- Available directly in the module: Reminder active.
- Available directly in the module: Switch to Yes branch.
- Available directly in the module: Switch to No branch.
- Available directly in the module: Parallel.
- Available directly in the module: Approvals / email recipients.
- Available directly in the module: Dynamic fields.
- Available directly in the module: Restart process after repair.
How the module works
How the module works
The typical workflow is integrated directly into day-to-day work in Qisutu.
- 01
Linear flows, yes/no decisions, and parallel paths
- 02
Steps with queues, groups, states, services, SLAs, fields, and recipients
- 03
REST calls, response evaluation, reminders, and an immutable process copy per ticket
- 04
Use “Action” to open the configuration for the respective work step.
- 05
Available directly in the module: REST interface.
- 06
Available directly in the module: Authentication.
Requirements
Requirements
These technical and organizational requirements are relevant for deployment.
- Qisutu 1.0.1+
- Kim API token
- Qisutu daemon
- Email-driven work steps
Administration and operation
Administration and operation
Configuration, background processing, and control remain centralized in Qisutu.
- Available directly in the module: Activation, secret Kim token, and reminders.
- The API address and Kim model are fixed in the module and cannot be changed by customers.
- A token is stored. Leave the field empty to keep it.
- Available directly in the module: Enable reminders for open work steps.
- Available directly in the module: Reminder after working hours.
Security and control
Security and control
Credentials, permissions, and automated decisions are handled transparently and securely.
- The API address and Kim model are fixed in the module and cannot be changed by customers.
- A token is stored. Leave the field empty to keep it.
- Available directly in the module: Continue despite error.
- Available directly in the module: Success condition.
Scope and boundaries
Scope and boundaries
The module extends Qisutu for a defined purpose while remaining separate from the Qisutu core.
- Installation through Administration → AddOns
- Independent ZIP module with no changes to Qisutu core files
- 11 fully supported interface languages
- AGPL-3.0-or-later
Questions about this AddOn?