Adobe Acrobat Sign for Salesforce: Large Documents & Push Agreements Service Guide

Search

Overview

Adobe Acrobat Sign for Salesforce: Large Documents & Push Agreements Services Guide explains how to configure Acrobat Sign for Salesforce to send Large Documents (greater than 4.0 MB from the send agreement page and 9.0 MB when sending in batch) or Push Agreements for agreements created outside of the Salesforce environment.

To establish and use the Large Documents and Push Agreement services, you must define the callback environment. The callback environment can be used for one of both services. The callback environment requires you to create a new and dedicated user and profile, which ensures that:

  • A known and minimally authorized set of permissions are in effect.
  • The functionality does not break due to a disabling of the user.

To establish the Callback environment and use Large Documents and Push Agreements services, you must complete the following steps:

Prerequisites

Note:

Neither Large Document transactions nor Push Agreements are supported in the Salesforce Professional Edition. 

Define the Callback User

You must create a dedicated user to grant object permissions for the callback process. To do so:

  1. Navigate to Setup > Administration > Users > Profiles.

  2. From the list of user profiles, select Clone for the Standard User listing.

  3. In the Clone Profile page that opens, provide a profile name and then select Save.

    clone-profile

  4. On the Profiles page, select Edit for the profile you created above (ABC Sign Callback User). Then, on the Profile Edit page:

    1. Under Custom Tab Settings, ensure that both options of Adobe Acrobat Sign Admin are set to Default On.
    2. Ensure these Visualforce pages are enabled: 
      • echosign_dev1.EchosignAdmin
      • echosign_dev1.SalesforceOAuthPage
    3. Select Save.

  5. Create a new user using a standard Salesforce License using the following steps:

    1. From the left panel, select Users. 
    2. On the Users page, select New User.
    3.  On the New User Edit page, give the user an intuitive name, assign a Salesforce license, and assign the profile you created above. Select Save.

  6. Add the Adobe Acrobat Sign Integrator permission set to the Callback User

    1. Navigate to Setup > Administration > Users > Users.
    2. Select the Full Name link of your callback user.
    3. Hover over Permission Set Assignments and then select Edit Assignments.
    permission-sets-edit

  7. On the Permission Set Assignment page:

    1. Select Adobe Acrobat Sign Integration User permission set.
    2. Select Add to move the permission set into the Enabled column.
    3. Select Save.
    add-callback-user

  8. Follow the steps below to activate the Callback User in Adobe Acrobat Sign by sending an agreement:

    1.  Log in to Salesforce as the Callback User.
    2. Navigate to App Launcher > Adobe Acrobat Sign for Salesforce > Agreements.
    3. Select New to open a new agreement page.
    4. Configure the agreement by adding a recipient and attaching a file.
    5. Select Send.
    agreements-tab-recipients

  9. On the post-send page, select OK to return to the Agreement, and then select Cancel to cancel the agreement.

  10. Link the Callback User to Acrobat Sign as follows:

    1. Navigate to App Launcher > Adobe Acrobat Sign for Salesforce > Adobe Acrobat Sign Admin.
    2. Under the Callback User, select Link an Account.
    3. .On the Allow Access? page, select Allow.
    4. On the Adobe Acrobat Sign Admin page, verify that the callback user is linked.
    5. Log out of Salesforce and log in again using your Salesforce Admin credentials.
    callback-user-link-account

    link-callback-allow-access

    Authenticated Callback user

Establish the Callback Site

You must set up and configure a site for the Adobe Acrobat Sign Callback so that agreement updates can be pushed to Salesforce in a timely manner.

Note:

If you have not used Salesforce sites in your Salesforce org, you must first register a Force.com domain name that will be used for all your Salesforce sites in the account. (See Registering a Custom Force.com Domain in the Salesforce.com help). Keep in mind that if you are registering a new domain name, it is recommended that you don’t have a very long domain name or the secure web URL may exceed the 255 character limit that Adobe Acrobat Sign has for callback URLs.

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

  2. Register your site domain name as follows:

    1. Type the name of your desired domain in the text field after the http://
    2. Select Check Availability to ensure that the domain is available. Once you have an available domain, a Success message displays.
    3. Accept the Terms of Use and select Register My Force.com Domain.

  3. On the refereshed page, select New.

  4. On the Site Edit page:

    • Set the Site Label value to Adobe Acrobat Sign Callback.
    • Set the Site Name value to Adobe_Sign_Callback.
    • Set the Site Contact value to a Salesforce user who will receive notifications about Sites. In most cases, this is the account admin.
    • Set the Default Web Address value to AdobeSignCallback.
    • Select Active checkbox.
    • Set the Active Site Home Page value to EchoSignCallback.
      EchoSign is a legacy name for the Adobe Acrobat Sign.
    Adobe Sign Callback

  5. Select Save. 

  6. Add the IP ranges for public access settings in the Site to restrict them to Adobe Acrobat Sign IPs. To do so:

    1. From the Site Details page for your Callback Site, select Public Access Settings.
    2. Select Login IP Ranges.
    3. Select New.
    4. In the Login IP Ranges dialog, enter the first IP address range:
      • Start IP Address: 52.71.63.224
      • End IP Address: 52.71.63.255
      • Description: Acrobat Sign
    5. Select Save.
    6. Repeat steps 2-5 for the IP address ranges listed in the table below.

    Note:

    If the error “The list of IP Ranges does not cover your current IP address….” displays, enable the Save this IP Range even though it does not cover my current IP address option and click Save again.

    Start IP End IP Description
    13.126.23.0 13.126.23.31 Adobe Acrobat Sign
    3.236.206.64 3.236.206.95 Adobe Acrobat Sign
    40.67.154.249 40.67.154.249 Adobe Acrobat Sign
    40.67.155.112 40.67.155.112 Adobe Acrobat Sign
    40.67.155.147 40.67.155.147 Adobe Acrobat Sign
    40.67.155.185 40.67.155.185 Adobe Acrobat Sign
    44.234.124.128 44.234.124.159 Adobe Acrobat Sign
    51.105.221.160 51.105.221.191 Adobe Acrobat Sign
    52.196.191.224 52.196.191.255 Adobe Acrobat Sign
    52.35.253.64 52.35.253.95 Adobe Acrobat Sign
    52.48.127.160 52.48.127.191 Adobe Acrobat Sign
    52.58.63.192 52.58.63.223 Adobe Acrobat Sign
    52.65.255.192 52.65.255.223 Adobe Acrobat Sign
    52.71.63.224 52.71.63.255 Adobe Acrobat Sign

    The final Login IP Ranges for the Adobe Acrobat Sign Callback Site should display as follows:

    IP Ranges

Configure the individual services

Large documents are automatically supported for sending transactions and background actions. Each feature has a specific size limit for the supported documents, as follows:

  • Send Transactions— You can send a single document of up to 4.0 MB or multiple documents with a total size of up to 4.0 MB by selecting Send for Signature on the Agreements page.
  • Background Actions—You can use background actions to send a single document up to 9.0 MB or multiple documents with a total size of up to 9.0 MB. 
    For more information on background actions, see the Advanced Customization guide.

To enable larger documents:

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

Edit the Callback User profile

To enable Object Level Permissions for the Adobe Acrobat Sign Callback Site User:

  1. on the Adobe Acrobat Sign Callback Profile page, select Edit.
  2. Scroll down to Custom Object Permissions and enable all the Agreements object permissions: Read, Create, Edit, Delete, View All, Modify All
  3. Enable the echosign_dev1. AgreementAttachmentDownloadService Apex class.
  4. Select Save.

Enable the Attachment Service Invocation Count for the Callback User profile

  1. Navigate to Object Manager > Agreement > Fields & Relationships. 
  2. Select the field label Attachment Service Invocation Count.
  3. Select Set Feild-Level Security.
  4. Enable both Visible and Read-Only for the Callback User profile.
  5. Select Save.


Edit the Site to enable the LargeFileDownloadService Apex class

You must also customize the profile for your Adobe Acrobat Sign Callback site to add the LargeFileDownloadService Apex class to make it visible.

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

  2. Select Adobe Acrobat Sign Callback site.

  3. Select Public Access Settings.

  4. Select Enable Apex Class Access and then select Edit. 

  5. From the Available Apex Classes list on left, select echosign_dev1.LargeFileDownloadService and then select Add to move it to the Enabled Apex Classes list. Then, select Save.

Update the Custom Settings to use the Callback URL

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

  2. Select Acrobat Sign Callback.

  3. Under the Custom URLs section, select View.

  4. From the new tab, copy the value of the URL in the browser and paste it into a text file.
    If testing on Sandboxes, copy the http URL and not the https URL. Below is an example of how the URL should look.

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

  6. On the Custom Settings page, select Adobe Sign Settings.

  7. On the Adobe Sign Settings page, select Manage.

  8. Select New or Edit.

  9. On the Adobe Acrobat Sign Settings Edit page, set the Callback URL Adobe to Salesforce Site value to the value of the ‘Secure Web Address’ you copied after configuring your Adobe Acrobat Sign Callback site. Ensure that the address prefix is ‘https’ and not ‘http’.

  10. Select Save to save your settings.

    The Large Document Service is now enabled.

You can use the Acrobat 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 specific configurations, depending on how you intend to use Adobe Sign.

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

  1. Navigate to Setup > Administration > Users > Users.

  2. Select the Callback User name to open the User Detail page.

  3. Hover over Permission Set Assignments and select Edit Assignment.

  4. In the Available Permission Sets section:

    1. Select Adobe Acrobat Sign Integration User.
    2. Select Add. 
    3. Select Save.

  5. Step text


Edit the Callback Site to add the EchoSignAgreementPushCallback Visualforce page

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

  2. Select Adobe Acrobat Sign Callback site.

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

  4. Locate and select echosign_dev1.EchoSignAgreementPushCallback, and then select Add to move the page to the Enabled Visualforce Pages side. Then, select 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. Follow the steps below to edit the page:

  1. Select Public Access Settings to open the Profiles page.
  2. On the Profiles page, select Edit. 
  3. Scroll down to the Standard Objects Permissions section.
  4. Enable Read and Create for the following objects: Account, Contact, Contract, Lead, and Opportunity.
  5. Select Save. It returns you to the callback profile.
  6. To make field-level adjustments where required, scroll down to the Field-Level Security section and edit Standard Field-Level Security as follows:
    • 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 want all of the agreements in your account that were sent outside of Acrobat Sign to be created and pushed into Salesforce, follow these instructions:

  1. Copy the secure URL address from the Acrobat Sign Callback Site you created and append /echosign_dev1__EchoSignAgreementPushCallback to compose the callback URL. 
  2. Contact Adobe Support and provide them with your callback URL to set as your AdobeAcrobat Sign account’s default callback URL.
    For example: If your site address is: https://echov11-dev.na12.force.com/AdobeSignCallback the callback URL will be: https://echov11-dev.na12.force.com/AdobeSignCallback/echosign_dev1__EchoSignAgreementPushCallback
  3. Adobe Support should also enter your Adobe Acrobat 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:

  1. Copy the secure URL address from the Adobe Sign Callback Site you created and append /echosign_dev1__EchoSignAgreementPushCallback to create the callback URL to use in the Adobe Acrobat Sign API.
    For example: If your site address is https://echov11-dev.na12.force.com/AdobeSignCallback, the URL you should use in the Adobe Sign API is: https://echov11-dev.na12.force.com/AdobeSignCallback/echosign_dev1__EchoSignAgreementPushCallback
  2. When sending an agreement or creating a web form through the API you need to provide a callback URL.
    See https://secure.echosign.com/redirect/latestApiMethods and reference the API parameter ‘CallbackInfo’.
  3. Ensure 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 Acrobat Sign support.
  4. Go to Push Mappings Settings to define preferences for how records are created when agreements are pushed to Salesforce.
Adobe logo

Sign in to your account

Quick links

View all your plans Manage your plans

Legal Notices    |    Online Privacy Policy