With the following properties you can configure the PDF export.

Specifies the panel that will be displayed in the navigation panel of the PDF viewer.
The valid values are "Bookmarks" and "Pages".

Specifies if the PDF file will be created according to the PDF/A or PDF/UA standards. For PDF/A, you can select one of PDF/A-1b, PDF/A-2b, PDF/A-3b, PDF/A-4¹⁾. For PDF/UA, you can select one of PDF/UA-1, PDF/UA-2.

The PDF/A standard describes PDF documents that are intended for long-term archiving. The PDF/UA standard defines requirements for the accessibility of PDFs. Encryption and transparent colors are not permitted. Fonts must always be embedded.

Both, PDF/A and PDF/UA documents do not support disabling printing, copying, or encryption of the PDF.

Note: If the report contains FacturX, the PDF/A-3b standard is required.

Specifies if a web optimized PDF will be created. If it is activated, then the PDF reader can display the first pages while it downloads the other pages of the PDF file.
The export of an web optimized PDF file may be slower and can consume more memory. Therefore this property is disabled by default.

To activate the encryption of the PDF file it is necessary to specify at least one of the passwords. The User Password is necessary to open and read the PDF file and the Owner Password is necessary to edit the properties of the PDF file.

PDF tags, like alternative text for images, are useful for screenreader. With this property, it is possible to enable / disable PDF tags in the created PDF file. It overrides the value of the server property.

In the PDF/UA format, cross-tabs and strictly structured table layouts are tagged as tables in the PDF. If the layout of a report cannot be tagged as a table, the reason can be identified in the DEBUG log for reporting. A report is recognized as a table if the following conditions are met:

1. Matching Labels and Fields:
   • The number of labels in the header must match the number of fields in the detail section.
2. Header Requirements:
   • Labels in the header must vertically overlap. (Labels must be aligned along a single horizontal line.)
3. Detail Section Requirements:
   • Fields in the detail section must vertically overlap.
   • Fields must be aligned along a single horizontal line.
4. Order:
   • Labels and fields must be arranged in ascending z-order, from left to right.
5. Alignment of Labels and Fields:
   • Each label must horizontally overlap with its corresponding field. (The label and field must be positioned directly above one another.)