מדריך למשתמש ביטול

Configure Large Documents and Push Agreements Service

  1. Adobe Acrobat Sign Integrations
  2. What's New
  3. Product Versions and Lifecycle
  4. Acrobat Sign for Salesforce
    1. Install the package
    2. Configure the package
    3. User Guide
    4. Developer Guide
    5. Advanced Customization Guide
    6. Field Mapping and Templates Guide
    7. Mobile App User Guide
    8. Flows Automation Guide
    9. Document Builder Guide
    10. Configure Large Documents
    11. Upgrade Guide
    12. Release Notes
    13. FAQs
    14. Troubleshooting Guide
    15. Additional Articles
  5. Acrobat Sign for Microsoft
    1. Acrobat Sign for Microsoft 365
      1. Installation Guide
    2. Acrobat Sign for Outlook
      1. User Guide
    3. Acrobat Sign for Word/PowerPoint
      1. User Guide
    4. Acrobat Sign for Teams
      1. User Guide
      2. Live Sign Guide
      3. Mobile User Guide
      4. Release Notes
      5. Microsoft Teams Approvals
    5. Acrobat Sign for Microsoft PowerApps and Power Automate
      1. User Guide
      2. Release Notes
    6. Acrobat Sign Connector for Microsoft Search
      1. User Guide
      2. Release Notes
    7. Acrobat Sign for Microsoft Dynamics 
      1. Overview
      2. Dynamics Online: Installation Guide 
      3. Dynamics Online: User Guide 
      4. Dynamics On-Prem: Installation Guide 
      5. Dynamics On-Prem: User Guide
      6. Dynamics Workflow Guide
      7. Dynamics 365 for Talent
      8. Upgrade Guide
      9. Release Notes
    8. Acrobat Sign for Microsoft SharePoint 
      1. Overview
      2. SharePoint On-Prem: Installation Guide
      3. SharePoint On-Prem: Template Mapping Guide
      4. SharePoint On-Prem: User Guide
      5. SharePoint On-Prem: Release Notes
      6. SharePoint Online: Installation Guide
      7. SharePoint Online: Template Mapping Guide
      8. SharePoint Online: User Guide
      9. SharePoint Online: Web Form Mapping Guide
      10. SharePoint Online: Release Notes
  6. Acrobat Sign for ServiceNow
    1. Overview
    2. Installation Guide
    3. User Guide
    4. Release Notes
  7. Acrobat Sign for HR ServiceNow
    1. Installation Guide
  8. Acrobat Sign for SAP SuccessFactors
    1. Cockpit Installation Guide (Deprecated)
    2. Recruiting Installation Guide (Deprecated)
    3. Recruiting User Guide
    4. Cloud Foundry Installation Guide
    5. Release Notes
  9. Acrobat Sign for Workday
    1. Installation Guide
    2. Quick Start Guide
    3. Configuration Tutorial
  10. Acrobat Sign for NetSuite
    1. Installation Guide
    2. Release Notes
  11. Acrobat Sign for SugarCRM
  12. Acrobat Sign for VeevaVault
    1. Installation Guide
    2. User Guide
    3. Upgrade Guide
    4. Release Notes
  13. Acrobat Sign for Coupa BSM Suite
    1. Installation Guide
  14. Acrobat Sign Developer Documentation
    1. Overview
    2. Webhooks
    3. Text Tags

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 or 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:

Verify prerequisites

הערה:

Salesforce professional edition doesn’t support Large document transactions or Push agreements.

Define the Callback User

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

  1. Log in to your Acrobat Sign for Salesforce account using admin credentials.

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

  3. Locate Standard User in the list of user profiles and then select Clone for the listing.

    Define callback user in Acrobat Sign for Salesforce.

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

    The example profile here uses 'Demo callback user' as the profile name.

    Create callback user profile in Acrobat Sign for Salesforce.

  5. Follow the steps below to create a new user using a standard Salesforce License:

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

  6. Add the 'Adobe Acrobat Sign Integration User' permission set to the callback user using the following steps:

    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.
  7. On the Permission Set Assignment page:

    1. Under Available Permission Sets, select Adobe Acrobat Sign Integration User.
    2. Select Add to move the permission set into the Enabled column.
    3. Select Save.
    Add Adobe Acrobat Sign Integration User in Acrobat Sign for Salesforce.

  8. Link the user to Acrobat Sign using the steps corresponding to the environment that you are using. 

    1. Log in as the newly created callback user.
    2. Navigate to App Launcher > Adobe Acrobat Sign Admin.
    3. Under the Callback User, select Link an Account.
    4. On the Allow Access dialog, select Allow.
      It prompts you to log into your Salesforce account again. 
    5. Once you are logged in, go to the Adobe Acrobat Sign Admin page and verify that the callback user is linked.
    Link callback account on Acrobat Sign for Salesforce admin page.

    link-callback-account-2

    Linked callback account.

    1. Log in to Acrobat Sign for Salesforce account using Standard System Admin profile.
    2. On the ‘Sign for Salesforce’ lightning page, select Adobe Acrobat Sign Admin tab.
    3. Under the Callback User, select Link an Account.
    4. On the Allow Access dialog, select Not you? 
    5. On the Salesforce log-in page, enter the credentials for the callback user and then log in.

    It takes you back to the Adobe Acrobat Sign Admin page. Verify that the callback user is linked.

    Link Callback user for 'Acrobat Sign for Salesforce' commercial cloud.

    Link Callback user for 'Acrobat Sign for Salesforce' commercial cloud.

    Log in to Salesforce account of callback user of Acrobat Sign.

Establish the Callback site

Acrobat Sign admins, on the Commercial Cloud, must establish and configure a site specifically for the Adobe Acrobat Sign Callback. This setup ensures that agreement updates are promptly pushed to Salesforce and large documents can be easily downloaded. Please note that the push agreements feature isn’t available for Government Cloud users.

הערה:

Before using Salesforce sites in your organization, you must register a Force.com domain, which is used for all the Salesforce sites in your account. When choosing a domain name, keep it short to prevent exceeding Adobe Acrobat Sign's 255 character limit for callback URLs.

  1. Using the Search Setup bar at the top, search for Sites and then from the search results, select Sites. Alternatively, navigate to Setup > Platform Tools > User Interface > Sites and Domains > Sites.

  2. If you want to use an already registered site, you can skip this step.

    Else, follow these steps to register your site domain name:

    1. Enter the desired domain name in the text field after the https://
    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:

    1. Set the Site Label value to Adobe Acrobat Sign Callback.
    2. Select the Site Name field. It automatically sets the value to Adobe_Acrobat_Sign_Callback.
    3. Set the Site Contact value to a Salesforce user who will receive notifications about Sites. In most cases, this is the account admin.
    4. Set the Default Web Address value to AdobeAcrobatSignCallback.
    5. Select Active checkbox.
    6. Set the Active Site Home Page value to EchoSignCallback.
      EchoSign is a legacy name for the Adobe Acrobat Sign.
    7. Select Save.
    Create callback site in in Acrobat Sign for Salesforce.

  5. 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 in the table below.

    To determine the IP ranges associated with your region, refer to one of the following list of IP addresses based on the environment that you are using: 

    List of sample IP address ranges:

    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

    הערה:

    If you get a “The list of IP Ranges does not cover your current IP address….” error, enable the Save this IP Range even though it doesn’t cover my current IP address option and then select Save.

Configure the individual services

Large documents provide default support for sending transactions and background actions, each with its own size limit as follows:

  • Send transactions— You can send a single document or multiple documents totaling up to 4.0 MB via the 'Send for signature' option on the Agreements page.
  • Background actions—These allow sending of a single document or multiple documents totaling up to 9.0 MB. For more details, see the Advanced customization guide.

To enable sending large documents, you must complete the following steps:

  1. Edit the Callback User Profile to grant additional access.
  2. Enable the LargeFileDownloadService Apex class for the site.
  3. 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. Navigate to the Profiles page and then for the callback user that you created (Demo callback user in this example), select Edit.
  2. Scroll down to Custom Object Permissions and enable all the permissions for Agreements object: Read, Create, Edit, Delete, View All, Modify All.
  3. Select Save.
Configure Acrobat Sign for Salesforce for sending large documents.

Enable the LargeFileDownloadService Apex class

You must adjust your Adobe Acrobat Sign Callback site to include the 'LargeFileDownloadService' Apex class for visibility.

The instructions below align with the enhanced profile interface. For details on profile interfaces, see Salesforce Profiles.

  1. Using the Search Setup bar at the top, search for Sites and then from the search results, select Sites. Alternatively, navigate to Setup > Platform Tools > User Interface > Sites and Domains > Sites.

  2. Select Adobe Acrobat Sign Callback site.

  3. Select Public Access Settings.

    Configure Acrobat Sign for Salesforce for sending large documents.

  4. Select Enabled Apex Class Access and then select Edit

    Configure Acrobat Sign for Salesforce for sending large documents.

  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.

    Configure Acrobat Sign for Salesforce for sending large documents.

    Configure Acrobat Sign for Salesforce for sending large documents.

Update the Custom Settings to use the Callback URL

  1. Using the Search Setup bar at the top, search for Sites and then from the search results, select Sites.

    Alternatively, navigate to Setup > User Interface > Sites and Domains > Sites.

  2. Select Adobe Acrobat Sign Callback.

  3. Under the Custom URLs section, select View.

    Configure Acrobat Sign for Salesforce for sending large documents.

  4. From the new tab that opens, copy the value of the URL in the browser and paste it into a text document.
    The URL should resemble: https://<my-domain>.my.salesforce-sites.com/AdobeSignCallback

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

  6. For the Adobe Sign Settings label, select Manage > Edit or New.

    Configure Acrobat Sign for Salesforce for sending large documents.

  7. On the Adobe Acrobat Sign Settings Edit page:

    1. In the Callback URL Adobe to Salesforce Site field, paste the URL of the ‘Secure web address’ that you copied after configuring your Adobe Acrobat Sign Callback site.
      Ensure that the address prefix is ‘https’ and not ‘http’.
    2. Select Save.

    It enables the Large Document Service.

    Configure Acrobat Sign for Salesforce for sending large documents.

The Acrobat Sign API allows you to send signature requests, create web forms, and embed them on your website. These agreements are then pushed and created in Salesforce as if dispatched directly from it. You can also send agreements via the adobesign.com web application, and they'll sync back to Salesforce.

To enable Push Agreements:

הערה:

To enable the Push Callback Agreements to function properly post the webhook 2.0 migration, you must add the Webhook IP addresses to the Site callback user profile.  

Add 'EchoSignAgreementPushCallback' Visualforce page to the Callback Site

  1. Using the Search Setup bar at the top, search for Sites and then from the search results, select Sites.

    Alternatively, navigate to Setup Platform Tools > User Interface > Sites and Domains > Sites.

  2. Select Adobe Acrobat Sign Callback.

    Configure callback site for pushing agreements to Acrobat Sign for Salesforce.

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

  4. On the Enable Visualforce Page Access page:

    1. From the list of Available Visualforce Pages, locate and select echosign_dev1.EchoSignAgreementPushCallback.
    2. Select Add.
      It moves the page to the list of Enabled Visualforce Pages.
    3. Select Save.
    Configure Acrobat Sign for Salesforce for pushing documents back to Salesforce.

Edit Site Object and Field level permissions

After adding the Visualforce page, you’re returned to the Site Details page for the callback site. Follow the steps below to edit the page:

  1. Select Public Access Settings.
  2. On the Adobe Acrobat Sign Callback Profile page, select Edit. 
  3. Scroll down to the Standard Objects Permissions section.
  4. Enable Read and Create for the following objects: Account, Contacts, Contracts, Leads, and Opportunities.
  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 then edit the settings for the the following fields, as described:
    • Contact
      • Account: ensure that you select the checkboxes for Read Access and Edit Access.
      • Email: ensure that you select the checkboxes for Read Access and Edit Access.
      • Name: ensure that you select the checkboxes for Read Access and Edit Access.
    • Lead
      • Company: ensure that you select the checkboxes for Read Access and Edit Access.
      • Email: ensure that you select the checkboxes for Read Access and Edit Access.
      • Name: ensure that you select the checkboxes for Read Access and Edit Access.

Add specific configurations

To have all agreements sent outside of Acrobat Sign in your account created and transferred to Salesforce, follow these steps:

  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 Adobe Acrobat Sign account’s default callback URL.

    Example: If your site address is https://<MyDomain>.my.salesforce-sites.com/AdobeSignCallback, your Acrobat Sign API URL should be: https://<MyDomain>.my.salesforce-sites.com/AdobeSignCallback/echosign_dev1__EchoSignAgreementPushCallback.

    Adobe Support must enter your Adobe Acrobat Sign userID for the default callback URL API user setting. Ensure all Salesforce accounts are set to add the document key to the callback URL.

For sending agreements via the API:

  1. Copy the secure URL from the Adobe Sign Callback Site you've created and append /echosign_dev1__EchoSignAgreementPushCallback to create the callback URL for the Adobe Acrobat Sign API.

    Example: If your site address is https://<MyDomain>.my.salesforce-sites.com/AdobeSignCallback, your Acrobat Sign API URL should be: https://<MyDomain>.my.salesforce-sites.com/AdobeSignCallback/echosign_dev1__EchoSignAgreementPushCallback

  2. When sending an agreement or creating a web form through the API you must provide a callback URL.
    See the current list of Acrobat Sign Document API Methods and refer to 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 Support.

  4. Go to Push Mappings Settings to define preferences for how records are created when agreements are pushed to Salesforce.

 Adobe

קבל עזרה במהירות ובקלות

משתמש חדש?