Znuny Ticket System – Process Management

The process management module in Znuny enables the graphical design, automation, and monitoring of your business workflows. From the initial request capture to the final approval, clearly structured processes ensure increased efficiency, reduced error rates, and complete transparency in your workflows.

Table of Contents

1. Core Benefits at a Glance
2. Creating and Managing Processes
3. Activity Types in Detail
4. Transitions and Associated Actions
5. Export & Import of Processes
6. Best Practices & Recommendations

---

Core Benefits at a Glance

• Consistency: Standardized workflows significantly reduce manual errors.
• Transparency: Every process step is documented and can be traced for audits.
• Automation: Automatic transitions and actions accelerate the entire workflow.
• Integration: External services and user inputs are seamlessly integrated into the process.

---

Creating and Managing Processes

1. Access Module: Navigate to Processes & Automation → Process Management.
2. Create New Process: Click on Add Process to open the graphical editor.
3. Label & Description: Assign a unique name and briefly describe the purpose and scope of the process.
4. Deploy: After modeling, click on Save & Deploy to make the process available for tickets.

---

Activity Types in Detail

`DynamicField_Status = ‘approved’“

Script Task Activity

Execute Znuny-internal scripts, for example, for data processing or preparation. Central Configuration Fields:

• Activity Name
• Script Selection
• Parameters (as key/value pairs)

Service Task Activity

Integrate external Web Services and process their responses directly within the process flow. Central Configuration Fields:

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

User Task Activity

Actively involve agents or customers to make decisions or provide additional information. Central Configuration Fields:

• Activity Dialog
• Define Mandatory Fields
• Visibility (Agent / Customer)

---

Transitions and Associated Actions

Between individual activities, you define Transitions (conditions for process flows) as well as Transition Actions.

1. Create Transition: Draw an arrow from one activity to the next.
2. Define Condition: For example, DynamicField_Status = 'approved'.
3. Add Actions: In the “Actions” section, you can
   • Change the Queue
   • Adjust the Owner
   • Trigger email notifications

---

Export & Import of Processes

Share your process definitions with colleagues or transfer them to other instances:

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

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

---

Best Practices & Recommendations

• Use Test Mode: Use the Test Mode to check workflows without making actual ticket changes.
• Modular Processes: Break down extensive workflows into clear sub-processes for better maintainability.
• Version Control: Create a new process version for every release – this keeps previous versions available.
• Meaningful Descriptions: Maintain helpful comments for every activity and every transition.
• Monitoring & Logs: Enable extended output in Daemon logging to monitor processes during operation.

---

With Znuny process management, you create a solid foundation for efficient, error-free, and traceable business processes. Good luck with your implementation!

Znuny automation & custom integrations

Integrate Znuny seamlessly with your IT landscape: We implement web services, business process workflows, and REST integrations.

Discuss automation

Frequently asked questions

How do I create and deploy a new process in Znuny's Process Management?

To create a new process in Znuny, begin by navigating to the Processes & Automation section and then selecting Process Management. Here, you will find the Add Process button, which opens the graphical editor. Within this editor, you must assign a unique name and provide a clear description that outlines the purpose and scope of your process. Once you have graphically modeled your workflow, defining its activities and transitions, you can make it active and available for tickets by clicking Save & Deploy. This action publishes your process, enabling it to manage ticket lifecycles according to your defined logic.Quellen- Znuny Ticket System – Process Management | Znuny Community Docs- OTOBO Ticketsystem – Prozessmanagement

What are the main activity types available in Znuny Process Management and how are they used?

Znuny Process Management offers three primary activity types to build comprehensive workflows. The Script Task Activity allows you to execute Znuny-internal scripts, useful for data processing or preparation, configured with an activity name, script selection, and key/value parameters. The Service Task Activity integrates external Web Services, enabling you to process their responses directly within your workflow; its configuration involves selecting the Web Service, configuring the invoker, and setting timeout/error handling. Lastly, the User Task Activity is designed to involve agents or customers actively, prompting them for decisions or additional information through configurable activity dialogs, mandatory fields, and visibility settings. These activities are the building blocks for automating and structuring diverse business processes.Quellen- Znuny Ticket System – Process Management | Znuny Community Docs

How do I define transitions and associated actions to control the flow between activities in a Znuny process?

In Znuny Process Management, Transitions define the conditions under which a process flow moves from one activity to the next, while Transition Actions specify what happens during that movement. You create a transition by drawing an arrow from a preceding activity to the subsequent one in the graphical editor. For each transition, you can define specific conditions, such as DynamicField_Status = 'approved', which must be met for the transition to occur. Furthermore, in the 'Actions' section, you can configure various automated actions. These actions can include changing the ticket's queue, adjusting its owner, or triggering email notifications, thereby automating critical steps and ensuring the workflow progresses logically and efficiently based on predefined criteria.Quellen- Znuny Ticket System – Process Management | Znuny Community Docs

What are the recommended best practices for testing and maintaining processes in Znuny?

To ensure the reliability and maintainability of your Znuny processes, several best practices are highly recommended. Always utilize the Test Mode to thoroughly check workflows without making any actual changes to live tickets, preventing unintended disruptions. For complex or extensive workflows, adopt Modular Processes by breaking them down into smaller, clear sub-processes, which significantly improves maintainability and readability. Implement Version Control by creating a new process version for every major release or significant change, ensuring that previous working versions remain available for reference or rollback. Additionally, maintain Meaningful Descriptions for every activity and transition to enhance clarity and understanding for all agents. Finally, enable extended output in Daemon logging for Monitoring & Logs to effectively track and troubleshoot processes during live operation.Quellen- Znuny Ticket System – Process Management | Znuny Community Docs

What are the steps and important considerations for exporting and importing processes between different Znuny instances?

Exporting and importing processes in Znuny allows you to share process definitions with colleagues or transfer them efficiently between different Znuny instances, which is invaluable for development, testing, and deployment workflows. To export a process, simply select the desired process from the management interface and choose the Export JSON option. This generates a JSON file containing your process definition. For importing, navigate to the target Znuny system, select Import Process, and upload the previously exported JSON file. A crucial prerequisite for a successful import is that all queues, roles, and dynamic fields referenced within the process definition must already exist in the target environment. Failure to meet this requirement will result in errors and prevent the process from functioning correctly, highlighting the importance of environment consistency.Quellen- Znuny Ticket System – Process Management | Znuny Community Docs

How does Znuny Process Management benefit an organization by improving workflows and reducing errors?

Znuny Process Management offers significant benefits to organizations by streamlining operations and enhancing service delivery. It establishes Consistency through standardized workflows, which dramatically reduces the potential for manual errors and ensures uniform handling of requests. Transparency is greatly improved as every step within a process is meticulously documented and fully traceable, providing clear audit trails and accountability. The module also drives Automation, utilizing automatic transitions and actions to accelerate the entire workflow, reducing response times and agent workload. Furthermore, it allows for seamless Integration of external services and user inputs directly into the process, creating a cohesive and efficient operational environment. Ultimately, these core benefits lead to increased efficiency, minimized human error, and complete visibility into your business processes.Quellen- Znuny Ticket System – Process Management | Znuny Community Docs