PDF/A validation

The application can be configured to validate PDF/A conformance validation on PDF files, when a signing order is created. The purpose of this function is to warn the user if the uploaded file does not meet the standards required by organisation policy.

Configure the system by indicating what PDF/A flavours are allowed. If NO_FLAVOUR is configured, all PDF/A flavours will be accepted. If no flavour at all is configured, the validation is skipped.

Tag Description
NO_FLAVOUR
All PDF/A flavours
PDFA_1_A
 1a PDF Version 1 Level A
PDFA_1_B
 1a PDF Version 1 Level B
PDFA_2_A
2a PDF Version 2 Level A
PDFA_2_B
2b PDF Version 2 Level B
PDFA_2_U
2u PDF Version 2 Level U
PDFA_3_A
3a PDF Version 3 Level A
PDFA_3_B
3b PDF Version 3 Level B
PDFA_3_U
3u PDF Version 3 Level U
PDFA_4
4 PDF Version 4
PDFA_4_F
4 PDF Version 4 Level F
PDFA_4_E
4 PDF Version 4 Level E
PDFUA_1
ua1 PDF Version 1
WCAG2_1
wcag PDF version 2.1

Example configuration to allow 1a PDF Version 1 Level A and 3a PDF Version 3 Level A

"usePdfAFlavours": ["PDFA_1_A", "PDFA_3_A"]

See reference

The default behavior to warn the user can be changed to reject the invalid PDF and not allow the order to be created at all. This will disable the "Create" button in the final step and also present a red warning text if the PDF standard is not met.

To activate the function, add "rejectInvalidPdfA": true to the signingOrders section of the config.json.