Salesforce: Configure Large Document Service / Push Agreements

Large documents are automatically supported for send transactions and background actions up to certain limits:

• Send Transactions—When clicking the Send for Signature button on the Agreements page, you can send a single document that is up to 4.0 MB or multiple documents whose summed size is up to 4.0 MB.
• Background Actions—When sending document using background actions, a single document up to 9.0 MB or multiple documents whose summed size is up to 9.0 MB can be sent. (See the Advanced Customization guide for more information on background actions.)

To enable larger documents, you must do the following:

• Edit the Callback User profile to grant additional access
• Enable the Attachment Service Invocation Count for the Callback User profile
• Edit the Site to enable the LargeFileDownloadService Apex class
• Update the Custom Settings to use the Callback URL

Edit the Callback User profile

To enable Object Level Permissions for the Adobe Sign Callback Site User, do the following.

• Click the Edit button on the Adobe Sign Callback Profile page and scroll down to Custom Object Permissions
• Enable all the Agreements object permissions (Read, Create, Edit, Delete, View All, Modify All)
• Enable the echosign_dev1. AgreementAttachmentDownloadService Apex class
• Click Save

Enable the Attachment Service Invocation Count for the Callback User profile

• Navigate to Object Manager > Agreement > Fields & Relationships 
• Click on the Field Label Attachment Service Invocation Count
• Click the Set Feild-Level Security button
• Enable both Visible and Read-Only for the Callback User profile
• Click Save

Edit the Site to enable the LargeFileDownloadService Apex class

You must also customize the profile for your Adobe Sign Callback site to add the LargeFileDownloadService Apex class so it is visible

1. Navigate to Setup > Platform Tools > User Interface > Sites and Domains > Sites
2. Click the site label for the Adobe Sign Callback site
3. Click the Public Access Settings button

    4. Click the Enable Apex Class Access link to jump to that section, then click Edit. 

• From the Available Apex Classes list on the left, select the echosign_dev1.LargeFileDownloadService and click Add to move it to the Enabled Apex Classes list on the right as shown below.
• Click Save

Update the Custom Settings to use the Callback URL

1. Navigate to Setup > User Interface > Sites and Domains > Sites

2. Click the Site Label for the callback site

3. In the Custom URLs section, click the View link

• A new tab will open

4. From the new tab, copy the value of the URL in the browser and paste it into a text file.

• If you are testing on Sandboxes, copy the http URL and not the https URL.

Your URL should look something like the URL shown below:

5. Navigate to Setup > Platform Tools > Custom Code > Custom Settings

• This loads the Custom Settings page

6. Click the label Adobe Sign Settings

• The Adobe Sign Settings page will load

7.  Click the Manage button

8. Click New or Edit

• The Adobe Sign Settings Edit page will load.

9.  Set the Callback URL Adobe to Salesforce Site value to the value of the ‘Secure Web Address’ you copied after configuring your Adobe Sign Callback site (see Step 7 above).

• Make sure the address prefix is ‘https’ and not ‘http’.

10. Click Save to save your settings.

The Large Document Service is now enabled.

You can use the Adobe Sign API to send agreements for signature or create web form and embed them on your website and have all those agreements pushed and created in Salesforce just as if they were sent from Salesforce. You can also send agreements via the echosign.adobe.com web application and have them all pushed back to Salesforce.

To enable these Push Agreements, you must:

• Edit the Callback User to provide the Adobe Sign Integration User permission set 
• Edit the Callback Site to add the EchoSignAgreementPushCallback Visualforce page
• Edit the Site Object and Field level permissions
• Any use sepcific configurations, depending on how you intend to use Adobe Sign

Edit the Callback User to provide the Adobe Sign Integration User permission set

1. Navigate to Setup > Administration > Users > Users
2. Find the Callback User and click on the Full Name link to open the User Detail page

3. Mouse over the Permission Set Assignments link and click the Edit Assignment button

4. In the Available Permission Sets section, select Adobe Sign Integration User

• Click the Add button
• Click Save

Edit the Callback Site to add the EchoSignAgreementPushCallback Visualforce page

1. Navigate to Setup > Platform Tools > User Interface > Sites and Domains > Sites
2. Click the site label for the Adobe Sign Callback site

3. Scroll to the Site Visualforce Pages section then click Edit

4. Locate echosign_dev1.EchoSignAgreementPushCallback and single click it to select it

5. Click Add to move the page to the Enabled Visualforce Pages side

6. Click Save

Edit the Site Object and Field level permissions

After adding the Visualforce page, you are returned to the Site Details page for the callback site.

• Click Public Access Settings to open the Profiles page
• Click Edit on the Profiles page
• Scroll down to the Standard Objects Permissions section
• Enable Read and Create for the following objects:

• Click Save, which returns you to the callback profile

Several objects require field level adjustments also:

• Scroll down to the Field-Level Security section and edit:
  • Standard Field-Level Security
    • Contact
      • Account > ensure Read and Edit Access are enabled
      • Email > ensure Read and Edit Access are enabled
      • Name > ensure Read and Edit Access are enabled
    • Lead
      • Company -> ensure Read and Edit Access are enabled
      • Email -> ensure Read and Edit Access are enabled
      • Name -> ensure Read and Edit Access are enabled

Use specific configurations

If you would like all of the agreements in your account that were sent outside of Adobe Sign to be created and pushed into Salesforce, follow these instructions:

• Copy the secure URL address from the Adobe Sign Callback Site you created and append /echosign_dev1__EchoSignAgreementPushCallback to compose the callback URL. Contact Adobe Support and provide them with your callback URL to set as your Adobe Sign account’s default callback URL. For example: If your site address is: https://echov11-dev.na12.force.com/EchoSignCallback the callback URL will be: https://echov11-dev.na12.force.com/EchoSignCallback/echosign_dev1__EchoSignAgreementPushCallback
• Adobe Support should also enter your Adobe Sign userID for the default callback URL API user setting. All accounts using Salesforce should also have their accounts set to append the document key to the callback URL.

If you are sending agreements via the API, follow these instructions:

• Copy the secure URL address from the Adobe Sign Callback Site you created and append /echosign_dev1__EchoSignAgreementPushCallback to create the callback URL to be used in the Adobe Sign API.
  • For example: If your site address is: https://echov11-dev.na12.force.com/EchoSignCallback
    the URL you should use in the Adobe Sign API will be: https://echov11-dev.na12.force.com/EchoSignCallback/echosign_dev1__EchoSignAgreementPushCallback
• When sending an agreement or creating a web form through the API you will need to provide a callback URL (see https://secure.echosign.com/redirect/latestApiMethods and reference the API parameter ‘CallbackInfo’.)
• Also make sure that your account settings are set to append the document key to the callback URL that should be the default for Salesforce customers using Adobe Sign. For any issues, contact Adobe Sign support.
• Additionally, go to Push Mappings Settings to define preferences for how records are created when agreements are pushed to Salesforce.