In general, any batch bigger then 50 documents should be done via Batch Backend.
Batch Backend advantages:
- Much faster processing
- more scalable
- better error handling
- can generate a merged PDF or ZIP file
- Is the future of Batch processing in PDF Butler so main innovations will come to this platform
After installation of the add-on package, follow the following steps:
1) Register
- Go to tab: BULK Butler Admin
- Enter the PDF Butler Username and password
- Check the Addendum agreement and register
- After registering, contact PDF Butler Support to make sure you have the License for BULK generation via Batch Backend
2) Assign Permission Set “PDF Butler Batch” to each User that requires to use the batch
3) Create Batch Info with RecordType “Batch Backend”
4) Configure the Batch Info
- Cron: Schedule your jobs weekly, monthly, … (read online documentation from Salesforce on what is supported for CRON Jobs in Salesforce)
- SOQL: SOQL that will select the records to process
- Count SOQL: same SOQL as above but with only 1 field “Count()”
- Make sure the amount of records selected by the Count SOQL is the same as the SOQL! So the WHERE or LIMIT clauses must match
- DocConfig or Pack: documents to generate.
- AFTER Actionables on the DocConfig or Pack will be ignored
- BEFORE (AFTER DATASOURCES) Actionables are taken into account
- BatchSize: set to 100
- Delivery Type: BASE64 if you do not want save the file to the record. FILES if you do not want to save the file
- Alternative/Locale/Currency Locale API fields: the field on the record that sets the values for these settings. This cannot be a field through a Lookup
- Make sure the API field is added to the SOQL!
5) AFTER Actionables (OPTIONAL)
- Merging or Zipping the PDFs
- Record Type: Batch Backend Action
- Backend Batch Action: Files will be linked to the Batch Run record
- MERGED_PDF: will merge all PDFs. If more then 1000 records, each merged PDF will have max 1000 records and there will be multiple merged PDFs
- ZIP_FILE: will put all PDFs in a zip file. If more then 1000 records, each zip file will have max 1000 records and there will be multiple ZIP files
- Active: Check this or the Actionable will be ignored
- No Unique Id Per File: If you check this box, you must make sure that each PDF generated has a unique name (via the Doc Config Title). If not, all documents with the same name will overwrite each other! With this option, BULK Butler will make sure the documents do not overwrite each other by adding a unique Id to the name.
- Batch Backend Upload Action: If you want the Merged PDFs or the ZIPs stored in SharePoint (only SharePoint via COLLABORATION Butler is supported for now). Leave empty if you want them stored in Salesforce FILES related to the Batch Run record.
- Record Type:
- Class: cadmus_una.Actionable_GetUploadSession
- more info here: COLLABORATION Butler – Actionable Upload To SharePoint
- AFTER Actionables – PDF/SIGN/COLLABORATION Butler or Custom Actions
- Just create the Actionable on the BatchInfo as you would normally do on a DocConfig or Pack
