Qisutu daemon¶

The instance-specific daemon processes recurring and asynchronous tasks.

Overview¶

This page explains how to use the Qisutu daemon and describes its main effects. Test changes in a test environment first whenever they may affect existing tickets, permissions, notifications, or automations.

Typical workflow¶

Retrieve email accounts regularly. Perform the function in the designated form and immediately verify the result in the corresponding overview or on the affected ticket.
Process triggers and scheduled rules. Perform the function in the designated form and immediately verify the result in the corresponding overview or on the affected ticket.
Check escalations. Perform the function in the designated form and immediately verify the result in the corresponding overview or on the affected ticket.
Install, update, and uninstall add-ons. Open the existing record, change only the required fields, and check dependent assignments before saving.
Process module tasks and persistent module events. Perform the function in the designated form and immediately verify the result in the corresponding overview or on the affected ticket.
Use instance-specific locks. Perform the function in the designated form and immediately verify the result in the corresponding overview or on the affected ticket.

Notes¶

Visible menu items and actions depend on the signed-in agent’s group and program permissions.
Deactivated entries are often retained for existing tickets and reports, but are no longer available for new assignments.
After making changes, test at least one realistic use case with a user in the affected role.