PDF is the usual format for archiving, printing, and distributing reports. The following options can be set in the export settings dialog or via the report URL parameters.

The dialog is grouped into Settings, PDF Standard, and Encryption.

• Web-optimized PDF file: When enabled, the PDF is optimized so viewers can show the first pages while the rest is still loading. Export may be slower and use more memory.
  • Default value: No

• Content in the navigation: Chooses which panel the PDF viewer shows in its navigation pane.
  • Values:
    • None
    • Bookmarks
    • Pages
  • Default value: None

• PDF/A Standard: Produces a PDF that conforms to PDF/A for long-term archiving, ISO 19005. Fonts are embedded; encryption and disabling print/copy are not allowed with this standard.
  • Values:
    • None
    • PDF/A-1b - PDF 1.4, most restrictive: no transparency, layers, or attachments
    • PDF/A-2b - PDF 1.7, allows transparency, layers, and PDF/A attachments
    • PDF/A-3b - PDF 1.7, like 2b but allows any file as attachment, e.g. FacturX
    • PDF/A-4 - PDF 2.0, latest archiving standard
  • Default value: None

• Accessibility: Produces a PDF that conforms to PDF/UA for accessibility, ISO 14289.
  • Values:
    • None
    • PDF/UA-1 - PDF 1.7, accessibility for assistive technologies
    • PDF/UA-2 - PDF 2.0, newer semantic tags and stronger accessibility focus
  • Default value: None

• PDF tags for screen readers: Adds tags to the PDF for screen readers, e.g. alternative text for images. Overrides the server default. Not available when Accessibility (PDF/UA) is not None.
  • Values: Default, True, False
  • Default value: Default

• Encrypt PDF file: When enabled, you must set at least one of the two passwords. User Password is required to open and read the file; Owner Password is required to open and change the PDF properties. Encryption is not available when PDF/A or PDF/UA is selected.
  • Default value: Off

Note: If the report contains FacturX, PDF/A-3b is required. In PDF/UA, cross-tabs and strictly structured table layouts are tagged as tables; see the logging configuration for the debug log if a layout is not tagged.

In the PDF/UA format, cross-tabs and strictly structured table layouts are tagged as tables in the PDF. A report is recognized as a table if the number of labels in the header matches the number of fields in the detail section, labels and fields overlap as required, and they are arranged in ascending z-order with each label above its corresponding field.