Archive PDF/A-1 workflow
This workflow is engineered specifically for preparing documents for archiving, specifically where PDF/A-2 or PDF/A-3 conformance is not allowed.
This workflow is disabled by default because it is recommended you use Archive PDF/A 2 workflow for archiving. Since PDF/A-2 is based on a newer version of the PDF standard, more PDF features are allowed such as transparency, layers, embedded files, and a less restrictive internal file structure.
For these reasons, fewer conversion errors and a better conversion quality can be achieved with the Archive PDF/A-2 workflow, particularly if you have installed the service on a Docker container where document content rasterization.
More information on PDF/A-2, read PDF/A-2 overview.
Supported file formats for Archive PDF/A-1 workflow
This workflow supports these file formats:
| Extension / Type | |
|---|---|
| Document formats | PDF 1.x, PDF 2.0, PDF/A-1, PDF/A-2, PDF/A-3 |
| Image formats | JPEG, JPEG200, TIFF, BMP, GIF, JBIG2, PNG, HEIC, HEIC |
| EML, MSG (without encryption) | |
| Word | DOC, DOT, DOCX, DOCM, DOTX, DOTM, RFT, XML (WordprocessingML 2003) |
| Excel | XLS, XLT, XLSX, XLSM, XLTX, XLTM, XML (SpreadsheetML 2003) |
| PowerPoint | PPT, PPS, PPTX, PPTM, PPSX, PPSM |
| OpenOffice | ODT, ODS, ODP |
| Other | CSV, HTML, HTM (prepared for archiving), TXT, XML, ZIP (without password protection) |
PDF conversion of OpenDocument Format depends on the rendering in Microsoft Word, Excel or PowerPoint. In particular, visual differences may occur with tables and tabs. The visual differences caused by the rendering of shapes are usually not acceptable.
HTML documents need to be self-contained (layout information and images are either inline or available on the web) and suited for portrait page layout. JavaScript content is disabled during processing.
Layout information and images need to be available on the web.
The conversion of most file formats is enabled by default in the profile's Convert Mode Configuration for Child Documents (Attachments).
Features and limitations
Compared to the PDF/A-2 workflow, this workflow has the following features and limitations:
Convert to PDF/A-1
Collect mode configuration
The PDF/A-1 standard does not allow embedded files. Therefore, the only collect mode configuration available is Merge.
Document content rasterization
Certain graphical features of PDF documents are not allowed in PDF/A-1; for example, transparency. The removal of these features can lead to severe visual differences that may render the page's content unreadable.
The Windows version of the product can preserve the visual appearance of such documents by converting the pages' content to images (content rasterization).When doing so, a content rasterized warning is generated. If possible, content rasterization preserves the pages' extractable text, links, outlines and viewer preferences.
The Docker version cannot rasterize pages. Therefore, the conversion of such files leads to transparency removed or visual differences warning depending on whether the visual differences are caused by the removal of transparency.
PDF/A-1 specific conversion warnings
The following warnings occur more frequently when converting to PDF/A-1:
- Annotation removed
- Content rasterized
- Layers removed
- Transparency removed
- Visual differences
So the profile's conversion settings for these warnings is particularly important.
Note: Content rasterized warning appears only in Windows where content rasterization is available; Transparency removed warning only appears in Docker image, where content rasterizaiton is not available.
Sign
Document signing is currently not implemented.