Directory structure

The directory structure separates entry points, business logic, the interface, installation files, and runtime data.

Overview

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

Typical workflow

  1. Use ``bin/`` for CGI and command-line programs. Perform the function in the designated form and immediately verify the result in the corresponding overview or on the affected ticket.

  2. Use ``core/config/`` for configuration and program descriptions. Perform the function in the designated form and immediately verify the result in the corresponding overview or on the affected ticket.

  3. Use ``core/module/`` for page modules. Perform the function in the designated form and immediately verify the result in the corresponding overview or on the affected ticket.

  4. Use ``core/system/`` for business logic. Perform the function in the designated form and immediately verify the result in the corresponding overview or on the affected ticket.

  5. Use ``core/output/`` for templates and output. Perform the function in the designated form and immediately verify the result in the corresponding overview or on the affected ticket.

  6. Use ``core/language/`` for de, en, fr, and it. Perform the function in the designated form and immediately verify the result in the corresponding overview or on the affected ticket.

  7. Use ``install/`` for the schema, master data, and updates. Perform the function in the designated form and immediately verify the result in the corresponding overview or on the affected ticket.

  8. Use ``var/static/`` for frontend assets. Perform the function in the designated form and immediately verify the result in the corresponding overview or on the affected ticket.

  9. Use ``t/`` for automated tests. 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.