- Adobe Acrobat Sign Integrations
- What's New
- Product Versions and Lifecycle
- Acrobat Sign for Salesforce
- Install the package
- Configure the package
- User Guide
- Developer Guide
- Advanced Customization Guide
- Field Mapping and Templates Guide
- Mobile App User Guide
- Flows Automation Guide
- Document Builder Guide
- Configure Large Documents
- Upgrade Guide
- Release Notes
- FAQs
- Troubleshooting Guide
- Additional Articles
- Acrobat Sign for Microsoft
- Acrobat Sign for Microsoft 365
- Acrobat Sign for Outlook
- Acrobat Sign for Word/PowerPoint
- Acrobat Sign for Teams
- Acrobat Sign for Microsoft PowerApps and Power Automate
- Acrobat Sign Connector for Microsoft Search
- Acrobat Sign for Microsoft Dynamics
- Acrobat Sign for Microsoft SharePoint
- Overview
- SharePoint On-Prem: Installation Guide
- SharePoint On-Prem: Template Mapping Guide
- SharePoint On-Prem: User Guide
- SharePoint On-Prem: Release Notes
- SharePoint Online: Installation Guide
- SharePoint Online: Template Mapping Guide
- SharePoint Online: User Guide
- SharePoint Online: Web Form Mapping Guide
- SharePoint Online: Release Notes
- Acrobat Sign for Microsoft 365
- Acrobat Sign for ServiceNow
- Acrobat Sign for HR ServiceNow
- Acrobat Sign for SAP SuccessFactors
- Acrobat Sign for Workday
- Acrobat Sign for NetSuite
- Acrobat Sign for SugarCRM
- Acrobat Sign for VeevaVault
- Acrobat Sign for Coupa BSM Suite
- Acrobat Sign Developer Documentation
Release notes
Acrobat Sign Document Builder V 1.3
- Advanced relationship mapping: Document Builder now allows you to establish up to five levels of child-to-parent relationships (lookup fields) for related objects. With this enhancement, you can make detailed field mappings to handle your complex Salesforce data models.
Document Builder permits multiple related objects directly linked to the master object within a single object field mapping. However, considering Salesforce limitations, you cannot specify more than 20 parent-child relationships (related objects) in a single SOQL query.
Example of child-to-parent relationship: Contact.Account.Owner.FirstName (considering Contact as the master object, this represents three levels). - Configure Sorting and Filtering of Merged Data: You can now configure the sorting and filtering of merged data within related objects. Learn how to configure Sorting and Merging of Merged Data.
Learn how to Upgrade the Document Builder package to the latest version.
With the release of V 1.3, we've updated the adobesign__Object_Name__c field to match the child relationship name. This field represents the name of the related field within the adobesign__Related_Object_Mapping__c custom object. Document Builder templates with related fields in object field mapping will seamlessly function in Document Builder 1.3 and future versions. However, the Document Builder templates created in V 1.3 and later won't work with Word templates that have tags for related fields from templates made before Document Builder V 1.3.
Resolved issues
Issue number | Corrected issue description |
---|---|
29923 |
Resolved the issue where users could not select a sample record in Document Builder templates using a mouse. |
- Enhanced template handling: With the latest PDF services API version 3.x.x, Document Builder package can efficiently handle larger Word templates, accommodating sizes of up to 5.5 MB. This enhancement empowers you to design and work with more extensive and intricate templates within the Document Builder package.
- Searchable combobox fields: When creating Document Builder templates, you’ll find it notably expedited as combobox fields are now searchable. This means you can easily search and populate fields like Sample Data, Salesforce fields, and Sample Record Data, streamlining the template creation process.
- Sandbox integration: The Document Builder package now seamlessly integrates with the Sandbox environment, providing you with even more flexibility and testing capabilities in your workflow.
Use Document Builder templates on Community cloud portals: The current package includes a permission set for community users that enables them to use the Dcoument Builder templates on their Community cloud portal. Admins must assign permissions to the records either via profile or via sharing settings on those objects.
- For community login user, you must use community user profile to grant viewAll access to 'Document Builder Template' and 'Object Field Mapping'.
- For community login plus user and partner community user, you must use sharing rules to grant access to 'Document Builder Template' and 'Object Field Mapping'. To do so, go to Setup > Security > Sharing Settings and then select the object to share read only access based on roles and subordinates.
- Support for 'group' OAuth scope: With the addition of a new public custom setting called 'Acrobat Sign DOCBLDR Settings,' Salesforce admins can now create an OAuth connection with a group-level admin.
- Fixed the issue in merge mapping when the language is switched from English to French.
- Resolved the problem where merging data using Document Builder and subsequently sending an agreement with a Document Builder template resulted in a failure with the error
: "Insert failed. First exception on row 0; first error: STRING_TOO_LONG, Merge JSON Data: data value too large..." The current package now supports longer field lengths.
- Improved image merging feature: You can now seamlessly merge images into a document template using DocGen API tags.
- Fixed the issue in Related object field mapping: With the current release, you can seamlessly map a related object via a lookup relationship. It allows you to generate a document from a master object (such as WorkOrder) and include child line items (such as WorkOrder related lists) in the document.
- Fixed the issue in filtering standard objects: The current release resolves the related object filter issue where a custom object was filtered out when a child custom object relationship is added. The added custom objects now show up in the related object list.
Overview
Document Builder is an Adobe Acrobat Sign for Salesforce feature that provides the ability to automatically generate documents using Salesforce data. It is a part of the existing Sign Agreement Template functionality. Salesforce admins can enable teams or individual team members to use Document Builder for creating documents, such as proposals, quotes, or agreements. The generated document is sent as an attachment with the Acrobat Sign Agreement template and can be easily tracked and managed in Salesforce.
Document Builder is an extension package to the Adobe Acrobat Sign for Salesforce base package and does not require any additional purchase. The feature provides a step-by-step wizard for creating rules for merging data from salesforce object fields into a Word document template.
Adobe Acrobat Sign for Salesforce: Document Builder User Guide helps you understand how to:
- Install and configure the Document Builder package
- Apply Adobe Acrobat Sign Permission Sets
- Add 'Document Builder Template' Picklist Value
- Create new Document Builder templates
- Send agreements using Document Builder templates
- Upgrade Document Builder base package to a later version
- Troubleshoot common problems
Document Builder is supported only on the Salesforce Lightning platform.
Document Builder is not supported on Government Cloud or for agreements that are subject to HIPAA compliance.
Prerequisites
Before installing the Document Builder extension package, you must:
- Log in to the Salesforce account using your admin credentials. You must sign-up for a new account if you do not already have a Salesforce account.
- Install (or upgrade) and configure Acrobat Sign for Salesforce v 24.0 or later.
- Authorize Adobe Acrobat Sign account to Salesforce using the Set Up Wizard. For details, refer to the Adobe Acrobat Sign for Salesforce: Installation Guide.
-
In the Install Acrobat Sign Document Builder page that displays:
- Select Install for Admins Only.
- Select the checkbox to acknowledge the installation.
- Select Install.
- In the Approve Third-Party Access dialog that appears, select the consent checkbox and then select Continue.
It displays a notification saying that the installation process will take some time.
Once the package is successfully installed, admins must provide users with the right Perrmission Sets to enable them to use the Document Builder package for sending agreements from Salesforce. To do so, admins must add the following permission sets of Document Builder based on the required functionality:
- Acrobat Sign Documnet Builder Admin
- Acrobat Sign Document Builder Community User
- Acrobat Sign Document Builder User
To support Document Builder templates, the Type__c field of the Attachment_Template__c object now includes a new picklist value called 'Document Builder Template'. For the Document Builder templates to function properly after upgrading the base package to v24.x, Salesforce admins must add Document Builder Template picklist value to the existing picklist for the Type__c field of the Attachment_Template__c object.
All existing users of Adobe Acrobat Sign for Salesforce who upgrade to v24 must add the 'Document Builder Template' Picklist Value using the instructions below.
In case of a clean install of Adobe Acrobat Sign for Salesforce v24, users do not need to add the 'Document Builder Template' Picklist Value.
-
To localize the new Attachment Type value through the translation workbench:
- Navigate to Setup > Platform Tools > User Interface > Translation Workbench > Translate.
- If prompted to enable the translation workbench, select Enable.
- Select the Language that you want to localize to.
- Select the Setup Component as Picklist Value.
- Select Object as Add File Attachment.
- Under Master Picklist Value Lable, select + Attachment Type to expand the menu.
- Next, double-click the column space next to Document Builder Template to open the text field where the translation can be entered, and enter the appropriate localized value.
- Select Save when done.
Once the Document Builder extension package is installed and connected to the Adobe Acrobat Sign account, authorized users can access it within Agreement Templates under the Attachment tab. Salesforce admins can create a new Document Builder template or use an existing template as an attachment to their Agreement template.
To create a new Document Builder template:
-
From the Agreements Templates tab in the Adobe Acrobat Sign for Salesforce lightning page, open an existing agreement template.
Or, select Agreement Templates > New Agreement Template to initiate the process of creating an agreement template. For more details, see how to Create an Agreement Template.
-
Under the Template Details tab:
- Provide a name for the agreement template.
- In the Salesforce Object field, select an object.
Note: The Document Builder template uses the selected Salesforce object as the main data source. So, you must select the Salesforce master object before using Document Builder.
- Fill in the other details, as required.
- Select the Attachment tab.
-
To add the fields that you want to include in your agreement template, select + Add and select a field name from the drop-down list. After you have added and verified all the required fields, select Next.
To configure Sorting and Filtering of Merged Data:
- Ensure that you've added related fields and non-relationship fields to the related object field mapping.
- Select the drop-down arrow next to the added field and then select Table Options.
- In the Table Options dialog that appears:
- Open the Select Sort Field dropdown menu and select a desired sorting field.
The available options are derived from the selected fields in the related object field mapping. - In the Select Sort Order field, select a desired sorting order.
- In the Query Filter field, input your filtering criteria.
Ensure that your criteria adhere to the Salesforce query language guidelines.
- Open the Select Sort Field dropdown menu and select a desired sorting field.
Бележка:In case you enter an invalid query filter, the application displays a message containing a link to the relevant Salesforce documentation.
-
From the Tag Document tab, copy the anchor text for each field and paste it into your Word template. Or, select Download JSON to download the entire JSON file.
Once the file is downloaded, you see a message confirming the download. You can use the downloaded JSON file to import all the tags into your Microsoft Word template using the free Adobe Document Generation Tagger add-in.
-
To tag the template, open the Microsoft Word document and generate tags using Document Generation add-on.
See how to install and use the Adobe Document Generation add-in for Microsoft Word.
See how to add text tags to MS Word template using the Adobe Document Generation Tagger.
-
Once you tag the document, return to the Document Builder wizard page and select Upload File to upload your tagged word template. Once the file is uploaded, select Done to close the dialog.
The uploaded file is automatically assigned a template name. You may edit the Generated File Name field to rename the template file.
Once you create and add a Document Builder template, you can further configure the Agreement Template to send it to the recipients for signature. You can send an agreement with the Document Builder template for signature via:
- The Agreements tab
- The Agreements panel in an object record
To send agreements via the Agreements tab:
Once you create and add a Document Builder template to an agreement using the instructions above, follow the steps below to send that agreement for signature from the Agreements tab:
-
In the new agreement draft page that opens, fill in the following information as required:
- Under Recipients, select a recipient role from the Signer drop-down menu.
- In the Search Contacts field, search for the recipient's contact. Else, select Email from the drop-down menu and add the recipient's email address.
- Select I need to sign to add yourself as a signer. Select Sign Last or Sign First to set the signing order for yourself. Select Host signing for the first signer if needed.
- To add more recipients, select Add Recipient.
- To set a password for identity verification of the recipients, select Password from the drop-down menu under Identity Verification. Next, enter and confirm your password.
Note: The recipient's email id is the default method of identity verification. - Optionally, add a message for the agreement recipients.
- To add the Document Builder agreement template, select Add Files. In the Add Files dialog that opens, select the checkbox for the file that you want to include and then select Add Files.
Alternatively, to add files from your computer, select Upload from My Computer and follow the workflow.
-
Under Options:
- To password protect your signed document, select Password protect signed document. Next, assign a password in the password fields that appear.
- To set a Completion Deadline, select the calendar icon and chose a completion date.
- To send reminders to the signers, select an appropriate option from the Create Reminders drop-down menu.
- Optionally, select an alternate recipient language for the agreement.
- Select the Signature Type as E-Signature or Written Signature, as required.
-
In the Preview window that opens, do one or more of the following actions, as required:
- To add the signature fields for all recipients, select each recipient and then drag-and-drop the fields from Signature Fields menu in the right panel.
- To add signer's title, company name, or other related fields, open Signer Info Fields drop-down menu and add the appropriate field.
- To add data fields, open the Data Fields drop-down menu and add the desired data field type.
- To insert a file attachment, open More Fields drop-down menu and drag-and-drop File Attachment. Double-click the File Attachment field and fill in the required details in the dialog. You may add Hyperlink if required.
- To include a Participation Stamp or add a Transaction number, open Transaction Fields drop-down menu and add the desired option.
To send agreements from the Agreements panel in Object record:
A Document Builder template uses the Salesforce object that you select while creating an Agreement template. You can use the same Salesforce master object to send agreements with the Document Builder template to recipients for signature.
Follow the steps below to send agreements from the Agreements panel in an object record:
-
In the Agreements panel, open the Send Agreement for Signature drop-down menu and select the agreement that you want to send for signature.
It opens the Agreement in draft mode, as shown below. Note that agreement includes the files from the agreement template that you selected in the step above.
Бележка:If you do not see the Agreements panel in the Object record page, you can add the panel using the steps below:
- From the Opportunity object record page, select Setup > Edit Page.
- In the left panel of the page that opens, scroll down the Components list to locate Custom-Managed components.
- From the Custom-Managed list of components, select AgreemnetPanel and drag-n-drop to a desired location on the page.
- From the top-right corner, select Activation.
- In the dialog that opens, follow through the workflow.
- Select Save.
You can upgrade the Adobe Acrobat Sign Document Builder package from the Salesforce AppExchange. This section provides instructions on how to upgrade Adobe Acrobat Sign for Document Builder from an older version to the latest version.
Each version of Adobe Acrobat Sign Document Builder has new features and enhancements that can provide key improvements to your document workflows. We strongly recommend that you upgrade to the latest release since Adobe discontinues support of older versions over time.
To find the package version of the Adobe Acrobat Sign Document Builder that is currently installed:
- Log in to Salesforce using your admin credentials.
- Navigate to Setup > Platform Tools > Apps > Packaging > Installed Packages.
To upgrade Adobe Acrobat Sign Document Builder package:
-
Go to the Adobe Acrobat Sign Document Builder package on the Salesforce AppExchange and log in using your Salesforce account credentials.
- I get an 'Invalid refresh token' error when I try to sign in to Adobe Acrobat Sign for Salesforce. How do I fix the error?
To troubleshoot the 'Invalid refresh token' error, the Salesforce admin must ensure that OAuth to Sign is performed properly for the Document Builder package.
- I get an error while uploading the Word template file for creating the Document Builder template. Why am I unable to upload the Word file?
The Word template used in the Document Builder template cannot exceed ~4.4MB. Depending on the mapping rules set in the Document Builder template and the data pulled from the Salesforce org, the allowed Word template size might be even smaller. So, you must ensure that the Word template file size is not larger than the limit.