Are Pega generated PDFs PDF/A ?
Pega-7 can generate PDF documents and attach them, ...
However does anyone know if these are PDF or PDF/A, and if they are PDF can they be converted to PDF/A format?
* The PDF/A format is Archive-able, i.e. completely self-contained with embedded font info etc., can be rendered perfectly without external metadata.
* Ordinary PDF documents may be smaller files, but may contain links to external font definition metadata and so cannot be rendered without a connection to the outside world.
Accepted Solution
Pegasystems Inc.
GB
I shall mark this thread as 'Answered' although the answer is incomplete. Setting the parameter pyPDFGeneratePDFA to "true" when calling the HTMLtoPDF activity results in a PDF file that is more or less in PDF/A format, at least AlFresco reports the file as being in PDF/A; however when using the PDF test website to check the file for PDF/A running the file it produces the errors as shown in Jeroen's post above. So it is not completely PDF/A.
Pegasystems Inc.
GB
Update: There is a website where you can upload a PDF file and test it against various PDF standards. I generated a PDF using my customer's Pega 7.2 system and tested it in this way, and received the following report (below). Basically, the Pega 7.2 PDF is not acceptable PDF/A format.
Unfortunately, my customer is a government agency in the Netherlands, and they mandate a PDF/A file as a requirement.
Does anybody know how to make Pega generate PDF/A?
Validating file "Testfile01.pdf" for conformance level pdfa-1a
The key Metadata is required but missing.
The key StructTreeRoot is required but missing.
A device-specific color space (DeviceRGB) without an appropriate output intent is used.
The value of the key CA is 0 but must be 1.0. (2)
The value of the key ca is 0 but must be 1.0. (2)
The key S has a value Transparency which is prohibited. (2)
The font Helvetica must be embedded.
The font Helvetica-Oblique must be embedded.
The font Helvetica-Bold must be embedded.
The document does not conform to the requested standard.
The document contains device-specific color spaces.
The document contains fonts without embedded font programs or encoding information (CMAPs).
Update: There is a website where you can upload a PDF file and test it against various PDF standards. I generated a PDF using my customer's Pega 7.2 system and tested it in this way, and received the following report (below). Basically, the Pega 7.2 PDF is not acceptable PDF/A format.
Unfortunately, my customer is a government agency in the Netherlands, and they mandate a PDF/A file as a requirement.
Does anybody know how to make Pega generate PDF/A?
Validating file "Testfile01.pdf" for conformance level pdfa-1a
The key Metadata is required but missing.
The key StructTreeRoot is required but missing.
A device-specific color space (DeviceRGB) without an appropriate output intent is used.
The value of the key CA is 0 but must be 1.0. (2)
The value of the key ca is 0 but must be 1.0. (2)
The key S has a value Transparency which is prohibited. (2)
The font Helvetica must be embedded.
The font Helvetica-Oblique must be embedded.
The font Helvetica-Bold must be embedded.
The document does not conform to the requested standard.
The document contains device-specific color spaces.
The document contains fonts without embedded font programs or encoding information (CMAPs).
The document contains transparency.
The document's meta data is either missing or inconsistent or corrupt.
The document doesn't provide appropriate logical structure information.
Done.
Pegasystems Inc.
NL
Tried however still getting some issues:
| Validating file "AanvraagPdf_1465917664415.pdf" for conformance level pdfa-1b |
| xmp:CreateDate :: Wrong value type. Expected type 'Date'. |
| xmp:MetadataDate :: Wrong value type. Expected type 'Date'. |
| The value of the key CA is 0 but must be 1.0. |
| The value of the key ca is 0 but must be 1.0. |
| The key S has a value Transparency which is prohibited. |
| The document does not conform to the requested standard. |
| The document contains transparency. |
| The document's meta data is either missing or inconsistent or corrupt. |
| Done. |
Any suggestions how we get those attributes in?
Accepted Solution
Pegasystems Inc.
GB
I shall mark this thread as 'Answered' although the answer is incomplete. Setting the parameter pyPDFGeneratePDFA to "true" when calling the HTMLtoPDF activity results in a PDF file that is more or less in PDF/A format, at least AlFresco reports the file as being in PDF/A; however when using the PDF test website to check the file for PDF/A running the file it produces the errors as shown in Jeroen's post above. So it is not completely PDF/A.