Merging Options
The Expere Engine supports the following ancillary options for merging of PDFs:
MergedCopyPDFPdfMergeMergedCopyPDFDiscretePartyPdfMergeDiscretePartyPdfMergeWithDocInstancesPdfMergeWithDocInstancesDiscreteParty
General merging guidelines
The following options are applicable to all merging-related ancillary options:
- Expere sets the merged PDF files' Document Title to the original PacketName when passing in any of the merging-related ancillary outputs. The packet name is specified in the PKG file in the content library or in EZ Config Packages and Packets.
- All merging-related ancillary outputs are supported when Packets are authored as part of the PKG file in the content library or in EZ Config Packages and Packets.
- The merged PDF is named as follows: OriginalPacketName.pdf; for example:
CombinedAccountOpening.pdf. If no packet name is specifed, the file name would beDefault.pdf. - if using an ancillary option that results in individual PDF document
generation, each individual PDF document is named as follows:
Packet-InstanceDisplayName; for example:
"CombinedAccountOpening-PrivacyNotice-M2.pdf".
Unsupported Scenarios
The following merged PDF-related scenarios are not supported when a combination of Expere eNote, SmartSign Web, and SmartSign Plus is present:
MergedPDFDiscretePartyorMergeCopyPDFDiscretePartywith an Expere eNoteMergedPDFDiscretePartyorMergeCopyPDFDiscretePartywith SmartSign WebMergedPDFDiscretePartyorMergeCopyPDFDiscretePartywith SmartSign Web an Expere eNoteMergedPDFDiscretePartyorMergeCopyPDFDiscretePartywith SmartSign PlusMergedPDFDiscretePartyorMergeCopyPDFDiscretePartywith SmartSign Plus and an Expere eNoteMergedPDForMergeCopyPDFwith SmartSign PlusMergedPDForMergeCopyPDFwith SmartSign Plus and an Expere eNote
Note: SmartSign Plus does not currently support merged PDF's.