One differential of the PDFBUNDLE is automate and set CONFORMANCE (PDF/A) in all processed documents.
Conformance (PDF/A) ensures that a document can be long-term and independent of specific software like Adobe, Foxit and so on. A long-term PDF file is readable for any future PDF reader, and to fulfill this, it should not contain many particular features that some current usual software adds to it. In addition, a long-term document should include all the fonts used, exactly to ensure compatibility with any future software.
We recommend using PDF/A-3B to get most of the features used today in modern PDF software and make the document compatible for long-term storage.
IMPORTANT: signed PDF/A documents must have a Digital Certificate that also supports specific long-term requirements.
|
Click on the PROCESS button. |
|
Check the SIGN box to access all documents signing options in the top menu bar. |
Once you had selected "SIGN" in the menubar, scroll down the sidebar until you see the image below:
|
1.PDF/A - LONG TERM: enable the creation of a long-term PDF, according to the most adequate CONFORMANCE type (see next topic).
2.Conformance Type: we suggest utilize the 3B mode, since it is modern and recognizes fields, OCR and different fonts. To see the meaning of each mode, access the link on Wikipedia.
3.METADATA: optionally you can provide METADATA information for long-term documents - and this is highly recommended.
METADATA can provide helpful information for archiving and legal compliance. PDFBUNDLE allows companies to enter relevant data to achieve this goal. PDFBUNDLE can process metadata files (XLS/XLSX and CSV files), which contain the necessary filing information for each package..
Important: whether using CSV files, the metadata within must be separated by semicolons. XLS/XLSX files does not require this.
PDFBUNDLE will seek for these fields in the metadata file, obligatorily in that order and with these names:
✓FILENAME It represents the file’s name (or full file pathname) on the disk. If using full pathname, this will be suppressed from METADATA page.
✓AUTHOR It represents the name of the document owner (person or company).
✓CREATOR It represents the company name responsible for digitalizing/process this document.
✓KEYWORDS The words utilized as indexes to this file archiving (free text format).
✓SUBJECT Description of this document (free text format).
✓TITLE The optional title of this document (free text format).
Any other field can be added after these ones above. See the sample below.
Warning: the limit of METADATA fields is 25 (twenty five), including the above, due to page physical bounds and performance issues.
4.GUIDE TO METADATA: clicking on this button you will get a one-page document to guide you how to create the metadata file.
5.METADATA POSITION ON PAGE: by default, all METADATA is placed in a new last-page of all documents. Here you can fine tune the position on this page, according to the type of signature you wish to place there.
6.CODEPAGE: Some languages have special characters that can be misinterpreted by ADOBE if present in PDF METADATA fields (a problem related to some PDF standards). Here you can make them PDF/A compliant, ensuring their correct display, search, and print functions. |
