The PDF Merge Plugin gives administrators a way to combine up to 5 PDF documents into a single file. These PDFs can be uploaded or created using our PDF Generator plugin.
Plugin Configuration
To configure the PDF Merge Plugin select it from the Tasks options and drag it onto your process canvas.
The PDF Merge plugin may be configured as either a system or user task giving you the following options:
- System task - No recipients assigned to task. This will allow the merge to auto-complete as it is placed in the process.
- User task - If a recipient is assigned they will receive a task and dialog box that links to the merged document. It is important to note that until they click "OK" the task will not complete and the process will not continue to any additional tasks that remain.
Select Configuration > Configure Task to access the window below:
The following fields are required to configure the PDF Merge:
- Name of PDF to be created - This can be a static or dynamic name. To use Dynamic Naming add {{FILE_NAME}} to the PDF title. Once you save this configuration you will get an additional tab to map this dynamic name to a source. The file extention ".PDF" must be included in the file name.
- Task to generate PDFs - You will have the option to select any of the tasks and fields within your process as the sources of the merged PDF. You should order the mapping in the order in which you want the documents to be displayed in the final file.
Click "Save"
The Mappings tab will now be added to the configuration window:
To add a mapping click on "Add Mapping" - since the File Name is the only available variable it will be pre-populated as the parameter name. Select the source of the data or request variable that you would like to use for the File Name (for example, the requester's Last Name or name of the Request).
Click "Save" then "Close".
Training Example
In our training example we have a simple form that collects two PDF documents and then merges them into a single file:
The PDF Merge task is configured to be system-driven and to add the last name of the Requester to the PDF name. The configuration is set as follows:
And the Mapping for {{FILE_NAME}} is as follows:
The result when the request is processed is that the final PDF file is dynamically named and available as part of the request history.
Comments