Add-ons¶

Add-ons are installed, updated, and uninstalled from readable source-code ZIP files.

Overview¶

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

Typical workflow¶

Upload and check a module ZIP file. Use the available search, filter, and detail views. Clear or change filters if expected records do not appear.
Distinguish between a new installation and an update. Perform the function in the designated form and immediately verify the result in the corresponding overview or on the affected ticket.
Track daemon execution of file operations. Perform the function in the designated form and immediately verify the result in the corresponding overview or on the affected ticket.
Deactivate or uninstall a module. First check which existing records or users are affected. Where possible, deactivate entries instead of deleting them permanently.
Check compatibility and API capabilities. Perform the function in the designated form and immediately verify the result in the corresponding overview or on the affected ticket.
Use module settings and custom administration programs. 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.