Overview

Summary

Print Tickets with advanced formatting, including images.

Usage

Following installation, this package is active and usable right away.

Tickets and their articles are now printed in their original styling. This especially includes content such as inline images.

The logo to be printed at the top of the page can be specified with : Ticket::Frontend::AgentTicketPrint###PrintLogoFile

A complete list of options can be found in the Ticket::Frontend::AgentTicketPrint###Configuration Reference

Setup

For the print function to work properly, it is required that a headless Google Chrome browser is running.

If running in docker, it is necessary for a file which the package includes to be in place. Please put the file scripts/docker-compose/seccomp_profile.json in the directory where the docker-compose file of the OTOBO installation is located, e.g. to /opt/otobo-docker/docker-compose/seccomp_profile.json.

After that, please edit the file /opt/otobo-docker/docker-compose/otobo-base.yml and insert the following two lines ( without the plus signs ), directly below the line command: web:

 # The HTTP port might be specified in a docker-compose extension file, e.g. docker-compose/otobo-override-http.yml.
 # For HTTPS no HTTP port is exposed.
 #ports:
 #    - "80:5000"
 volumes:
   - opt_otobo:/opt/otobo

 command: web
+security_opt:
+  - seccomp:seccomp_profile.json
 healthcheck:
   test: curl -s -f http://localhost:5000/robots.txt

Following this, please restart the containers by executing docker-compose down, followed by docker compose up -d.

System requirements

Framework

OTOBO 11.0.x

Packages

-

Third-party software

-

Configuration Reference

Core::GoogleChrome

GoogleChrome::Bin

Defines the path to the Google Chrome or Chromium binary. If set, this binary will be used instead of PhantomJS::Bin.

Frontend::Agent::View::TicketPrint

Ticket::Frontend::AgentTicketPrint###PrintLogoFile

Specifies the file for the logo in the page header encoded to base64 (700 x 100 pixel).

Ticket::Frontend::AgentTicketPrint###DynamicFieldWidgetDynamicFieldGroups

Dynamic fields groups for dynamic field widget. The key is the name of the group, the value contains the fields to be shown. Example: ‘Key => My Group’, ‘Content: Name_X, NameY’.

Ticket::Frontend::AgentTicketPrint###Widgets###0100-TicketInformation

Printing information usually visible in the Ticket Information Widget for the Zoom View sidebar.

Ticket::Frontend::AgentTicketPrint###Widgets###0200-CustomerInformation

Printing information usually visible in the Customer Information Widget for the Zoom View sidebar.

Ticket::Frontend::AgentTicketPrint###DynamicFieldWidgetDisplay

Display settings to override defaults for dynamic field widget for Tickets.

About

Contact

Rother OSS GmbH

Email: hello@otobo.io

Web: https://otobo.io

Version

Author: Rother OSS GmbH / Version: 11.0 / Date of release: 2026-04-30

Index