The needs of our users are more complex every day, which is why we have developed a new component that helps generate a PDF file from 1 or more DocConfig, which is flexible, customizable, and easy to use.
This will help you save time generating and sending files to the end user.
You can find the Step by Step Guide here:
You can watch how to do it here:
Overview of output parameters:
- docConfigs: List of mandatory docConfig Ids
- optionalDocConfigs: List of mandatory docConfig Ids
- imgContentVersions: List of Content Version Ids of images (PNG/JPG)
- docxContentVersions: List of Content Version Ids of DOCX files
- pdfContentVersions: List of Content Version Ids of PDF files
- packs: List of mandatory pack Ids
- alternative: Alternative to use
- locale: Locale to use
- sendSeparate: Boolean setting to merge all pdfs or process them separate (eg in mails or SIGN Butler)
- subtitle: Subtitle of the component. This will show on the header of the component
- allowFileUpload: Shows the file upload component. All files uploaded are shown in a pill under the file upload component. Uploaded files will be added to the end of the document or when “sendSeparate” is true, they will be added as separate files to the end of the list of files.
- keepDocConfigType: Type is Boolean. This will generate the DocConfig not as a PDF (unless STATIC PDF) but as the actual type of the template. eg MAIN Word => it would generate a DOCX
- When this setting is “true”, the “sendSeparate” will always be “true”. So all documents will be handled separately.
- When using this setting, there will be an extra button next to the “Preview” button, “Generate by type”. The preview will still generate as PDFs, the “” will generate the type of the DocConfig
- generateByPack: Type is Boolean. This setting indicates that all DocConfigs will be handled as 1 in a Pack. This can be interesting when merging complex PDFs with formfields
- This will mean that all generated PDFs together must be smaller then the SFDC limit of 4 to 5MB!
- When this setting is “true”, the “sendSeparate” has to be set to “false”. So all documents will be merged into 1 PDF
-
generateByPackPackId: Type is String. Used with “generateByPack” if you need BEFORE Actionables with our DocConfigs. When running a Pack, the Actionables on the DocConfigs do not run! Only Actionables linked to the Pack will be run.
- When this variable is not set, a dummy pack will be used. This is a Pack that PDF Butler can use to group DocConfigs but has no BEFORE nor AFTER Actionables.