Configure Adobe 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

Prerequisites

The Callback User (required for configuring both the Large Documents and Push Agreements) requires two elements:

Note:

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


Establishing the Site for the services

Establishing the Large Document and Push Agreement services first requires for the callback environment to be defined.

The same site and user can be used for one or both services.

The below instructions recommend that a new and dedicated user and profile be established. This ensures a known, minimally authorized set of permissions are in effect, and establishes a user that is not likely to be disabled, breking functionality.

The overview of steps required are:

Define the Callback User

Establish the Callback Site

Configure the individual service


Define the Adobe Sign Callback User

A dedicated user is recommended to grant object permissions for the callback process. 

1. Create the new callback user profile

  • Clone the Standard User profile
    • Name the new profile with an intuitive name (eg: Adobe Sign callback user)
  • Edit the profile
    • Under Custom Tab Settings, ensure that both Adobe Sign Admin tabs are set to Default On
    • Ensure these Visualforce pages are enabled 
      • echosign_dev1.EchosignAdmin
      • echosign_dev1.SalesforceOAuthPage
  • Save the profile
1_clone_standarduserprofile
2_name_the_profile

2. Create a new user using a standard Salesforce License

  • Give the user an intuitive name (eg: Adobe Sign Callback)
  • Assign a Salesforce license
  • Assign the profile you created above
4_create_a_new_user
  • Save the new user
  • Verify the user to establish the known password

 

3. Link the Callback User to Adobe Sign

  • Log in to Salesforce as the Callback User
  • Navigate to the Adobe Sign Admin page (App Launcher > Adobe Sign for Salesforce > Adobe Sign Admin)
  • Click Link an Account under the Callback User header
5_1_link_the_callbackuser

The Allow Access? page is presented 

  • Click Allow
5_4_allow_access-accept

  • Verify on the Adobe Sign Admin page that the callback user is correctly linked
5_5_authenticatedcallbackuser
  • Log out of Salesforce
  • Log back in as your Salesforce Admin


Establish the Callback Site

You must set up and configure a site for the Adobe 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 Sign has for callback URLs.

  1. Navigate to Setup > Platform Tools > User Interface > Sites and Domains > Sites
  2. Register your site domain name
    1. Type the name of your desired domain in the text field after the http://
    2. Click the Check Availability button to ensure the domain is available for your use
      1. Once you have an available domain, a Success message displays.
    3. Accept the Terms of Use, and click the Register My Force.com Domain button
Sites Configuration panel

The Sites page refreshes to show your new Site

  3. Click the New button

  • The Site Edit page loads
Adobe Sign Callback parameters

4. In the Site Edit page, do the following:

  • Set the Site Label value to: Adobe 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 would be the account admin.
  • Set the Default Web Address value to: AdobeSignCallback
  • Enable the Active control.
  • Set the Active Site Home Page value to: EchoSignCallback
    • EchoSign is a legacy name for the Adobe Sign product

 

The fields should look like this:

Adobe Sign Callback

    5. Click Save 

 


Add the IP ranges for the site

    6. Add the IP ranges for public access settings in the Site so that it is restricted properly to Adobe Sign IPs

        a. From the Site Details page for your Callback Site, click the Public Access Settings button

        b. Click the Login IP Ranges link to jump to the appropriate section

        c. Click the New button

        d. 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: Adobe Sign

        e. Click Save

enter_the_ip_addressrange

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.

 

        f. Repeat steps b-e above for all of the below IP address ranges:

Start IP

End IP

Description

40.67.154.249 40.67.154.249 Adobe Sign
40.67.155.112 40.67.155.112 Adobe Sign
40.67.155.147 40.67.155.147 Adobe Sign
40.67.155.185 40.67.155.185 Adobe Sign

52.35.253.64

52.35.253.95

Adobe Sign

52.48.127.160

52.48.127.191

Adobe Sign

52.58.63.192

52.58.63.223

Adobe Sign

52.196.191.224

52.196.191.255

Adobe Sign

52.65.255.192

52.65.255.223

Adobe Sign

13.126.23.0 13.126.23.31 Adobe Sign

 

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

ip_ranges


Configure individual services

Configure for Large Document Service

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
Custom Object Permissions


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
invocation_countsettings


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
Public Access

 

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

Enable Apex Class

 

  • 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
Enable Apex Class


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
2b_sites_configdsaved

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:

Site URL

 

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
Adobe Sign Settings

 

7.  Click the Manage button

Adobe Sign Settings: Manage

 

8. Click New or Edit

  • The Adobe Sign Settings Edit page will load.
Adobe Sign Settings: New

 

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’.
Callback URL setting

10. Click Save to save your settings.

 

The Large Document Service is now enabled.

Configure for Push Agreements

You can use the Adobe Sign API to send agreements for signature or create Widgets 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
click_the_full_namelinkofthecallbackuser

 

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

edit_assigned_permissionsets

 

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

  • Click the Add button
  • Click Save
5_assign_the_integrationuserpermissionsettothecallbackuser


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
6_click_the_sitelabel

 

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

callback_vf_page

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

callback_add_vf


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:
Contact Account Opportunity
Lead Contract  
  • 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 widget 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.

This work is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License  Twitter™ and Facebook posts are not covered under the terms of Creative Commons.

Legal Notices   |   Online Privacy Policy