Skip to content
yaml
description: >
  Discover how OTOBO / Znuny process management can support your organization through efficient workflows
  and the reduction of human errors.

OTOBO / Znuny Ticket System – Process Management

Create New Process

The OTOBO Process Management module enables graphical modeling, automation, and monitoring of your business processes. From requirement capture to final approval, clearly defined workflows ensure higher efficiency, lower error rates, and transparent workflows.


Table of Contents

  1. Benefits at a Glance
  2. Creating and Editing Processes
  3. Activity Types – Details & Screenshots
  4. Transitions and Actions
  5. Export & Import
  6. Best Practices & Tips

Benefits at a Glance

  • Consistency: Standardized workflows minimize manual errors.
  • Traceability: Every step is documented; logs can be audited.
  • Automation: Automatic transitions and actions accelerate the process.
  • Integration: External services and user inputs are seamlessly incorporated.

Creating and Editing Processes

  1. Open Module: Navigate to Processes & Automation → Process Management.
  2. Create New Process: Clicking Add Process opens the canvas.
  3. Name & Description: Give your process a unique name and a brief note on its purpose and scope.
  4. Save & Deploy: After modeling, click Save & Deploy so tickets can use the new process.

Canvas Overview


Activity Types – Details & Screenshots

Script Task Activity

Execute OTOBO-specific scripts, e.g., for data preparation.

Script Task Details

Most Important Fields:

  • Activity Name
  • Script Selection
  • Parameters (Key/Value Pairs)

Service Task Activity

Call external web services and process their responses.

Most Important Fields:

  • Web Service Selection
  • Invoker Configuration
  • Timeout & Error Code

User Task Activity

Involve agents or customers to make decisions or supplement information.

User Task Dialog

Most Important Fields:

  • Activity Dialog
  • Required Fields
  • Visibility (Agent / Customer)

Transitions and Actions

Between activities, you define Transitions (conditions for process flow) and Transition Actions.

Create Transitions

  1. Create Transition: Drag an arrow from one activity to the next.
  2. Define Condition: e.g., DynamicField_Status = 'approved'.
  3. Add Actions: Under "Actions," you can:
    • Change queue
    • Adjust responsible agent
    • Trigger email notification

Add Transition Action


Export & Import

Share your process definitions with team colleagues or other instances:

  • Export: Process → Export JSON
  • Import: Import Process and upload the JSON file

Prerequisite: All referenced queues, roles, and dynamic fields must exist in the target environment.


Best Practices & Tips

  • Activate Test Mode: Use Test Mode to check workflows without affecting tickets.
  • Modular Processes: Break down extensive workflows into sub-processes for better maintainability.
  • Versioning: Create a new version for each release – this preserves previous workflows.
  • Detailed Descriptions: Maintain meaningful comments for each activity and transition.
  • Monitoring & Logs: Enable extended output in the daemon logging to monitor workflows in operation.