Document types
You can define three types of documents in the library: manual document library entry, binary document library entry, and eForm document library entry.
Manual document library entry
A manual document entry defines a document that is sourced from outside the parent case. The system does not generate any forms to fulfill this kind of document requirement.
It indicates that an image of a particular document must be delivered to meet the requirement. An example of this type of document requirement is the applicant’s most recent tax return, or a passport copy. A manual document in the library does not require keys since it does not cause any form generation.
Binary document library entry
A binary document entry defines a PDF document that is generated by the system b ased on a RuleFile-Binary Pega Platform rule, which is a binary image. This allows for generation of a static document. It does not allow data from the parent case to be included in the form. An example of this document type is a blank application form or standard disclosure documents. A binary document in the library has key fields that identify the Rule-File-Binary used to generate the document.
EForm document library entry
An EForm document entry defines a PDF document that is generated by the system based on a Rule-File-eForm/Rule-Map-eForm Pega Platform rule pair. Together, these rules define a PDF form and the rules for mapping data from the parent case into the document. This allows for generation of a document that is prefilled with data from the parent case. An example of this document type is an application form that has been prefilled with applicant data. An EForm document in the library has key fields that identify the Rule-Map-eForm used to generate the document.
Previous topic Document-based requirements Next topic Configuring document entries in requirement rules