Navigator Address: Common > Correspondence > PDF Merge
New Menu: Configuration > Correspondence > PDF Merge
This functionality provides the ability to create letters from PDF files, removing the need to translate changes into XSL: Formatted Object file types. It allows multiple PDF documents to be merged together to form one letter. The PDF files are stored within the application.
In the PDF Merge screen, a user can select the Letter Template and configure the PDFs against the products and/or benefits and/or riders.
Letters are created manually via the Create Request wizard or automatically by a process or activity (as per letter translation configuration). If a letter template is configured with the PDF Merge merge method the Create Request process will merge the pdf files into one document and store them within the application.
When the Product Letters job is run or Correspondence is previewed from an enquiry screen, the merged document is retrieved and displayed on the screen or sent to a printer.
Go to Common>Correspondence>Letter Template and make the following changes to the template to which PDF files need to be merged:
Go to Common>Correspondence>PDF Merge
The PDF Merge screen is made up of three panels:
The tree view in the left hand pane displays a list of the letter templates that are configured to use the PDF Merge merge method. This tree is not editable.
The top right hand pane displays a list of all products, benefits and riders (depending on which tab is chosen) currently configured in the application. These lists are not editable.
The bottom right hand pane allows PDF files to be uploaded & linked to the products and/or benefits and/or riders.
If the document has changed, the user can attach a new file. Multiple PDF files can be linked to riders with the same effective date. The file name must be unique within the effective date group.
Product and benefit PDF files cannot have multiple PDF files with the same effective date.
The merge process selects the most recent file(s), even if it is future dated.
The user can upload the same file to another rider/product.
The description must be unique across ALL products, benefits and riders.
A rulebook can be assigned to the PDF file in order to stipulate conditions with which the PDF file should generate for the rider.
This is helpful where there may be different policy wordings for the same rider. The rulebooks are configured in static/code TYPE : RPRB. The code tags for these are bespoke and coded according to the business requirement.
Files can be future or back dated.
Product and benefit PDF files cannot have the same Effective Date.
Rider PDF files can be added with the same Effective Date if they have different PDF file names.