Go to app launcher and from the upper-right corner, select Adobe Acrobat Sign.
- Install the Package
- Configure the Package
- User Guide
- Enable Digital Authentication
- 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 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
- Adobe Acrobat Sign Integrations
- Product Versions and Lifecycle
-
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 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
Overview
Adobe Acrobat Sign for Salesforce: Field Mappings and Templates guide provides instructions on how to use templates and how to configure the Data and Merge Mapping feature.
Acrobat Sign enables you to use interactive forms to collect data from your signers, position signature and initial fields in your documents, collect two-party information from both senders and signers, and more.
You can create your own Acrobat Sign template library by storing Acrobat Sign forms and templates in your Salesforce Documents tab.
Adobe Acrobat Sign for Salesforce: Field Mappings and Templates guide provides instructions on how to:
- Create forms and text tags
- Configure Merge & Data Mappings
- Use Data Mappings to push signer data & files to Salesforce records
- Use Merge Mappings to generate documents with Salesforce data
- Create Agreement templates and workflows
- Enable Acrobat Sign Workflows
- Enable 'Send for signature' button
- Enable Post Sign options
- Enable sending on behalf of others
- Enable only the sender to sign an agreement
- Add AgreementPanel (or AgreementPanelWide) and AgreementList Components
- Use onLoadActions
Successful mapping requires that you've pre-built forms with defined field names so you can logically relate the SFDC object field to the Acrobat Sign form field.
A simple form is illustrated below. The fields are defined by the curly bracket pairs on either side (defining the width of the field) and the field name (the string of characters between the curly brackets).
You can use Acrobat Sign text tags to:
- Set specific locations on documents for customers to add signatures and initials.
- Collect data from signers that can later be pushed back into your Salesforce account.
- Merge data from Salesforce into document fields before sending for signature.
You can create Acrobat Sign forms by adding special text tags to any document (Word, PDF, Text, and more) that you send through Acrobat Sign.
Text tags can include additional arguments beyond the name value, including validations, calculations, and regular expressions. An in-depth understanding of form building can dramatically improve the quality of data that you capture during the signature process.
With the Text Tag shortening feature, you can create forms with field mapping, establishing a standardized convention for recurring field names across documents. This feature brings the following benefits:
- Save time by avoiding the need to recreate formal tags.
- Improve data mapping consistency across multiple forms and serve as a reference for future forms.
For more details, refer to the Adobe Acrobat Sign text tag guide.
You can use the following settings to configure Merge and Data Mappings in your Sign for Salesforce account:
Optional settings
- Enable Mapping Error Notification (Enabled by Default): Enable this setting to send email notifications to the data mapping or merge mapping owner any time there are errors when the mappings are executed.
- Show Fields API Name (Disabled by Default): Enable this option to show API Name for every field and relationship of the salesforce objects while setting data mapping and merge mapping.
Suggested setting
- Upload field names to Salesforce forms: You can populate the SFDC object fields with Merge & Data Mapping field names by uploading the field names into Salesforce. This allows you to select field names from a picklist instead of freehand typing the field names into a text field.
Follow the steps below to upload field names to Salesforce object fields:- Create a form with all fields defined.
- Send the form for signature through Salesforce with an obvious agreement name, such as W4 Field Template. It helps you in finding the right template while mapping the fields.
- Enter some content into every field that you want to map, and then sign the agreement so it registers as completed in Salesforce.
The template is now available for you to select when you use the Import feature of data/merge mapping
You can use Acrobat Sign Merge Mappings to merge field data from Salesforce into your documents fields before sending them out for signature.
For example, you can populate a Lead’s address and phone number from a Salesforce record automatically into the agreement before sending it for signature. You can also change the status of an Opportunity when the agreement is fully signed and executed. Merged data fields can optionally be updated by signers if you choose to map the signer updates back to Salesforce.
You can also use merge mappings to automatically add the product lists tied to an opportunity. You can set which product attributes (like quantity and price) are included in your agreements and also specify how to sort and filter the associated products.
About Merge Mappings
A data source type for a merge mapping can be a specific constant value or a value from a Salesforce object field that can be referenced from the Acrobat Sign Agreement. The target for each merge mapping item is a designated field on an Acrobat Sign agreement.
For example, the mapping below updates the Acrobat Sign document fields for “FirstName” and “LastName” with the Salesforce Recipient (Contact) field data. It also fills in the company field in the document with the name of the account.
When you select an object to map, you’re starting at the Agreement object, and going to a parent/lookup object. The association between the objects must already be established at runtime.
Acrobat Sign form field data mappings help you define how Acrobat Sign will update Salesforce objects with signers data. For example, you can update a signer’s contact record in Salesforce.com with the address and phone number they provided when completing and signing your document. Also, you can also push back the Acrobat Sign signed agreement, audit trail, and any uploaded supporting documents from recipients into Salesforce objects by setting up file mappings.
About Data Mappings
Acrobat Sign Data Mappings update Salesforce objects when an Acrobat Sign agreement is signed or at a specified stage in the agreement workflow. Each Data Mapping is set up ahead of time and includes data mapping rules. Each data mapping rule defines the data source and the target Salesforce field that it must update.
A data source for a mapping can be an Acrobat Sign form field, a specific constant value, or a value from an Adobe Sign agreement field. The target for each data mapping item may be any field in any Salesforce object that can be referenced from the Acrobat Sign agreement.
For example, the mapping below updates the signer’s first and last name (as entered by the signer) in the Contact object. It also updates the Opportunity Stage and adds the signed agreement and audit trail to the Opportunity when the agreement is signed.
Other examples for using data mappings to update Salesforce include:
- Updating recipient contact information
- Adding a PO number to the Opportunity
- Updating payment information to the Account
- Changing Opportunity Stage when the contract is signed
- Adding the signed PDF and audit trail to the Contact.
To use Data Mappings to push signer data & files to Salesforce records, you must learn how to:
Adobe Acrobat Sign Agreement Templates allow you to set up default values and settings for your agreements ahead of time. You can also link an agreement template to a ‘Send for Signature’ button.
About Agreement Templates
Agreement templates allow you to pre-define agreement fields including name, message, language, expiration dates, and security options. You can also associate a particular data mapping, merge mapping, and object (such as Opportunity, Account, Contact, Lead, Opportunity, Contract) to the agreement template. Additionally, you can preset the recipient definitions, map fields to agreement fields, and pre-define the file attachments.
You can also set up a ‘Send for Signature’ button that appears on a related object record (for example, Opportunity) so that it links to an agreement template by default. To generate an agreement using an agreement template, you can select Send for Signature.
Log in to Salesforce and launch the Adobe Acrobat Sign for Salesforce App and select the Agreement Templates tab.
To create a new Agreement Template:
-
In the dialog that appears, enter a template name and select a workflow for the template, if desired.
Note: You see the option to select a workflow only if workflows are enabled and the linked Sign account has active workflows configured.
See how to Enable workflows. -
It displays the new Agreement Template page with the template name at the top. From the upper-right corner, select the drop-down icon to edit the following options:
- Edit Name - Change the name of the current template.
- Change Owner - Change the owner of the current template. Must be assigned to a current user in the Salesforce organization.
- Clone - Duplicates the current template with a unique Salesforce ID number.
- Delete - Deletes the current template from Salesforce.
Under the Save button, the page displays the template ID and the meta data around who created, owns, and last modified the template. You can toggle the Active check box to make the template available or not. New templates are created in an Active state.
-
It includes the core details that relate to the agreements created by the template by referencing a Salesforce object. To provide template details, fill in the following fields:
- Agreement Name: It defines the default name of the Agreement. All agreements are initially created with this name.
Text fields, such as the Agreement Name, can use Salesforce variables as part of the definition to dynamically generate meaningful field values. For example, you can customize the Agreement Name to include a recipient's name when the agreement is generated, such as Acme Corp Agreement - {!Name}. - Salesforce Object: Select the Salesforce Master Object that you want to use as the master reference for certain optional definitions in the agreement template.
For instance, you can specify Recipients, Field Mappings, or Attachments in the agreement, using fields and data from the Master Object or related lookup objects. If you have defined a Master Object in the Agreement Template, you can initiate the agreement by clicking a 'Send for Signature' button on the Master Object.
See how to Enable the Send for Signature Button. - Mapped data: Select Map data into agreement fields and select a Mapping method:
- Select from Object: It requires a Salesforce Object to be defined. Based on the master object you set up, select a field Source and a Target Agreement field. For example, if the Master Object is ‘Opportunity’, then in the next screen, select the source field from your master object (e.g., Opportunity) and also select the target Agreement object field where the data will be mapped.
- Input Specific Value: Push a literal value into a Target Agreement field.
All mapped fields are listed on the template where they can individually be edited or deleted.
To be able to map data to or from a secondary object that is linked to the Master object, you must implement the following steps:
- On the Master Object, ensure that there is a lookup field to the secondary object. Data cannot be mapped to or from a related list.
- On the Agreement object, ensure that there is a lookup field to the secondary object.
- On the Agreement Template, select Map data into agreement fields and select Select from Object.
- For the Source type field, select the lookup field for the secondary object.
- For the Target agreement field, select the lookup field for the secondary object.
- Select Save.
- On the agreement template, select Save to save your settings.
- Follow the steps to set up Data mapping or Merge mapping as described in the sections below.
- Auto Send: Enable this option if you've automated workflows that you want to use to trigger the sending of agreements or if you want to automatically send an agreement after a user selects the Send for Signature button from a Salesforce record. For Auto Send to work, you must have at least one recipient and one attachment defined in the agreement template.
- Agreement Type: Select from the list of defined Agreement Types.
- Language: Defines the language used in the communications to the recipient, including the emails and on-screen instructions
- Select the signature type for this agreement:
- E-Signature: To collect electronic signatures by default.
- Written Signature: Select this option to instruct recipients to download the document, physically sign it, scan the signed document, and upload it to Acrobat Sign.
You must attach one or more documents that the template is expected to deliver. If no documents are attached to the template, the sender will have to select the document when configuring the Agreement.
If the template is set to Auto Send, at least one document should be attached to the template.
The Document Builder option is disabled for Government Cloud customers.
To attach documents:
- Select Upload files and upload a file through a menu-driven wizard.
Or, drag-and-drop a file from the desktop.
Note: All uploaded files are added to the Salesforce CRM & Files content and are owned by the uploader.
- Under Select to add documents, select one of the below options and search for a document by specific libraries using the Search bar:
- Salesforce CRM & Files - It is your personal library. Any documents you upload from your system are stored in this library for future use.
- Salesforce Documents- It is the Salesforce library that is shared amongst users.
- Acrobat Sign Library - It refers to the library content stored in the Acrobat Sign system.
- Advanced Search - It is an interface with all of the above options available.
- Under Advanced Options, optionally select Choose Document Source. It allows you to select a document or object from a Salesforce object or runtime variable. Some salesforce master objects offer additional options for the source of the document. For example, if the Salesforce Object on the Template Details tab is Opportunity, you have an additional source option of Add from Opportunity Quote. There are three options:
- Add from Salesforce Object
- Source Type - Choose the object type for the document between File or Attachment
- Document Selection - Select the document to attach based on one of these criteria: Latest Document (Most recent Creation Date), Oldest
- Document (Oldest Creation Date), or All Documents (All documents found).
- Add from Opportunity Quote
- Quote Type: Latest Quote or Oldest Quote.
- Quote Type Determined By: Last Modified Date or related Date.
- Quote Document Type: Latest Document, Oldest Document, or All Documents.
- Runtime Variable
- Dynamically add an attachment from an object.
- Add a runtime variable name: Specify the variable and ID type from your Salesforce object.
- Add from Salesforce Object
- To import a field template from the Adobe Sign library, use the search bar under Add Form Field Template field.
You can use the Recipients tab to add recipients and control the stack of recipients for the agreement. To do so, fill in the following details:
- Under the Signing workflow, select one of the following two options:
- All Recipients Sign: All the recipients defined in the template are required to participate in the process, according to the roles applied to them. Select this for all agreements that are not required to be signed by the sender only.
- Only Sender Signs: Enable this option to add the "Only I Sign” functionality to the template. You must select Enable Sender Signs Only setting to use this option. Depending on your requirements, this option can be set to read-only using the Read Only Sender Signs Only setting.
- Under Recipients, select a recipient role from the Signer drop-down list.
- In the Search Contacts field, search for the recipient's contact. Else, select Email from the drop-down list and add the recipient's email address. Recipients can be added by:
- Salesforce object - Contact, User, Lead, or Group.
- Email - Any email address is acceptable.
- Runtime Variable - Dynamically insert a recipient based on an imported value from a variable on the master object (as defined on the Template Details tab).
- To add more recipients, select Add Recipient.
- To add yourself as a signer, select Add Me. Select Sign Last or Sign First to set the signing order for yourself. Select Host signing for the first signer if needed.
- To change the identity verification method, select Email to open the identity verification menu. From the drop-down, select one of the following verification methods, as required: Password, KBA, Phone, or Government ID.
- Optionally, add a message for the agreement recipients.
- Under Advanced Options:
- To facilitate hosted, in-person signing, select Enable hosted signature (in-person signature).
- To allow you to preview the agreement and to drag and drop form fields onto it before sending it out for signature, select Enable Preview and Position Fields.
- To send the agreement on behalf of a specific user, select Send on Behalf of and specify a user record ID. Learn how to enable the 'Send on Behalf of Others' feature.
- Optionally select Advanced Verification Methods to configure the verification methods for recipients if you're controlling signer verification based on internal or external recipient status.
On the Data Mapping tab, you can optionally specify which data mapping or merge mapping (or both) to automatically run when sending agreements using this agreement template.
- Merge Mapping: Select a data mapping to merge Salesforce fields into an agreement before sending it.
- Data Mapping: Select a data mapping to be used to map inputs from a signed agreement back into Salesforce.
You can configure additional rules to automate common agreement tasks. To do so, fill in the following fields, as required:
- Under Automatic Reminders, select one of the following options from the drop-down menu: Never, Every Day, Until Signed, Every Week, Until Signed.
- Under Days Until Expiration, enter the number of days until the agreement expires. The number of days entered is added to the current date when the agreement record is generated from the agreement template to dynamically calculate the expiration date.
Note: If using the package version 21.x or earlier, you see the Days Until Expiration as a number field. Customers using the package version 21.x or later see the field as a Text field, allowing it to reference other fields in the Master Object, such as {!Expiry Date}. Customers who have upgraded from a version prior to v21 will have both fields. - Under Post Sign Redirect URL, enter a URL to automatically redirect the signers of an agreement to the specified URL after they sign. The Enable Post Sign Options setting must be enabled to use this option.
- If you've enabled the Post Sign Options setting and specified a Post Sign Redirect URL Is specified, under Post Sign Redirect Delay (seconds) field, enter the number of seconds that should elapse before executing the redirect.
- Select Password protect the signed document checkbox to encrypt the signed PDF that is sent to the signers.
- Select Set as default template for all agreements checkbox to set this as the Default agreement template for your new agreements. You can also define a specific agreement template to associate with other agreements, which can override the default agreement template. For example, you can create a custom ‘Send for Signature’ button for the Account object that is associated with a specific agreement template. See Enable the Send for Signature Button for more information about custom buttons.
- Select Enabled as a Chatter Publisher Actions to enable this Agreement Template if you have enabled Chatter Publisher Actions on your organization. The Chatter Publisher Action allows users to send agreements from Chatter. Check this box to enable this agreement template for the Chatter Action for any of the following master objects: Contact, Account, or Opportunity. For example, if the Master Object is Opportunity, then checking this box enables users to send with this agreement template from any Opportunity Chatter feed. If you leave the master object blank, you can enable the agreement template on the home page Chatter feed.
For more information, refer to the Adobe Acrobat Sign Chatter Publisher Action.
The Enabled as a Chatter Published Actions option is not visible for Government Cloud customers since Chatter is currently supported only on Commercial Cloud.
Salesforce can easily be configured to import Workflows from Acrobat Sign, allowing agents the flexibility to send from both environments with the same recipient structure, authentication methods, mail distribution, and so on.
Using Workflows as the source for Salesforce templates also allows for using multi-purpose document templates that can gracefully include or skip recipients as needed.
Defining the Salesforce template is slightly modified when a workflow is attached, as the workflow modifies the Recipients tab to align with the workflow, and inserts some configured elements that you would normally define in the SFDC template.
The list below calls out the differences in the setup process:
Changes made to a Salesforce template will not save automatically.
Make sure to click the Save button in the upper-right corner of the screen to save your edits.
The ‘Send for Signature’ button is associated with the default agreement template or with any specific agreement template that you configure. By default, the Acrobat Sign for Salesforce integration includes a ‘Send for Signature’ button that you can add to your Opportunity, Account, Contact, Lead, or Contract page layouts. You can also create multiple custom ‘Send for Signature’ buttons that can be added to other objects and associated with different agreement templates.
Here is an example of how to enable the ‘Send for Signature’ button for the Opportunity object:
-
Navigate to Setup > Platform Tools > Objects and Fields > Object Manager.
-
Select the object that you want to edit (Opportunity in this example) from the list of objects on the left.
-
From the left panel, select Page Layouts.
-
Select the page layout that you want to edit.
-
From the list on the left panel, select Buttons.
-
Drag the button Send for Signature from the top section to the ‘Custom Buttons’ box in the Opportunity Detail section.
You can enable post-sign options to take your signers to a landing page of your choice. This makes the ‘Post Sign Redirect URL’ and ‘Post Sign Redirect Delay’ options available on the send agreement page. Signers of an agreement are redirected to the specified URL after they sign. For example, you can redirect signers to your company website or a survey page. This option can be made read only for senders using the Read Only Post Sign Options setting.
To enable post sign options:
-
Navigate to Setup > Platform Tools > Custom Code > Custom Settings.
-
Select Adobe Sign Settings.
-
Select Manage.
-
Select New (or Edit).
-
Find the Enable Post Sign Option and modify as desired.
Optionally, find the setting for Read Only Post Sign Options and modify as desired.
-
Select Save.
For Adobe Acrobat Sign for Salesforce v 11.7 or later, you can enable the 'Send on Behalf of' feature in Salesforce to allow individuals to send agreements on behalf of others. This functionality applies to all agreement-sending scenarios, including background actions initiated by updating the 'Background Actions' field or using the 'Auto Send' option in Agreement Templates. Additionally, you can streamline the process by setting a user lookup in an Agreement Template for an automatic population when the agreement is generated.
To enable the 'Send on the Behalf of' feature, you must assign the 'Adobe Acrobat Sign Admin' permission set to Salesforce admins. It grants admin users access to the following two fields that are required for enabling the 'Send on behalf of' feature:
- User.EchoSign_Allow_Delegated_Sending__c
- User.EchoSign_Email_Verified__c
Note: All users of the Adobe Acrobat Sign package must be assigned Adobe Acrobat Sign User permissions before they can use the service.
Implement the following steps to allow sending on behalf of others:
-
Add the ‘Allow Sending as Other Users’ field to the User record layout using the following steps:
- Navigate to Setup > Platform Tools > Objects and Fields > Object Manager.
- Select User from the Object Manager.
- From the left rail of the User object page, select User Page Layouts.
- Select User Layout.
- With Fields selected, select Allow Sending As Other Users and drag it to the “Additional Information (Header visible on edit only)” section of the layout.
- Select Save.
-
Add the ‘Adobe Acrobat Sign Email Verified’ field to the User record layout:
- From the Fields section of the User Page Layout page, select Adobe Acrobat Sign Email Verified option and drag it to the “Additional Information (Header visible on edit only)” section of the layout.
- Select Save.
-
Enable the ‘Allow Sending on Behalf of Others’ setting using the following steps:
- Navigate to Setup > Platform Tools > Custom Code > Custom Settings.
- For Adobe Sign Settings listing, select Manage.
- Select New (or Edit).
- Find (ctrl/cmd +f) the Allow Sending On Behalf of Others setting and edit it as needed.
- Select Save.
- Navigate to Setup > Platform Tools > Custom Code > Custom Settings.
-
For the specific user that you want to send on behalf of, you must enable the two settings as follows:
- Navigate to Setup > Administration > Users > Users.
- For a specific user, select Edit.
- On the User Edit page, under the Additional Information section, enable Adobe Sign Allow Sending as Other Users and Adobe Acrobat Sign Email Verified options.
- Select Save.
Enable this setting to display and enable the ‘Sender Signs Only’ option in the Recipients section of the send agreement page. When the ‘Sender Signs Only’ option is used, the agreement or document is presented to the sender to sign. This functionality is similar to the ‘Fill & Sign’ functionality in Adobe services. This option can be set to read only using the Read Only Sender Signs Only setting.
To enable the Sender signs only feature:
-
Navigate to Setup > Platform Tools > Custom Code > Custom Settings.
-
Select Adobe Sign Settings.
-
Select Manage.
-
Select New (or Edit).
-
Find the setting Enable Sender Signs Only and edit as needed. Optionally, find the setting for Read Only Sender Signs Only and edit as needed.
-
Select Save.
Acrobat Sign for Salesforce allows you to view and manage agreements via the Agreements Panel and Agreements List. You can add AgreementPanel (or AgreementPanel-wide) and AgreementList components to the Lightning page of any of the following Salesforce standard objects and use them to send and manage agreements for any record within that object:
- Account
- Contact
- Contract
- Lead
- Opportunity
- User
Follow the steps below to add AgreementPanel (or AgreementPanelWide) and AgreementList to a Salesforce object:
-
Ensure that ‘My Domain’ set up for your account.
See how to set up My Domain to use Adobe Acrobat Sign in the Salesforce environment. -
Open any record for any Salesforce object. The example below adds the components to a record in Opportunity object.
-
From the top-right corner of the record page, select the Settings icon to open the menu and then select Edit Page.
It opens the page in Edit mode. -
From the left panel, scroll down to the list of Custom-Managed components.
-
To add an Agreement panel, drag-n-drop AgreementPanel to the desired location, as shown below.
If required, you may add AgreementPanelWide instead of the AgreementPanel. Both components provide similar functionalities but AgreementPanelWide gives a wider view.
-
To add an Agreements list, drag-n-drop AgreementList to the desired location, as shown below.
-
From the top-right corner, select Save.
-
If prompted to activate the page to make it visible to the users, select Activate.
-
In the dialog that appears, select the required form factor and then select Next. Then, review the assignment and select Save.
It saves the changes and activates the page for users.
Salesforce can automatically trigger actions via the onLoadAction URL parameter supported by Acrobat Sign for the Agreement button actions: Send, Remind, Delete, Cancel, Update, and View. The URL parameter will respect the Toolbar Settings (see the Advanced Customization guide) set by the administrator so that only those that are enabled will be available.
Example of URLs with onLoadAction:
- Send: Make sure you have an agreement with the status Draft in your account.
https://echosign-dev1.ap1.visual.force.com/apex/EchoSignAgreementAdvanced?id=[agreementID]&sfdc.override=1&onLoadAction=send
- Remind: Make sure you have an agreement with the status Out for Signature in your account.
https://echosign-dev1.ap1.visual.force.com/apex/EchoSignAgreementAdvanced?id=[agreementID]&sfdc.override=1&onLoadAction=remind
- Delete: Make sure you have an agreement with the status Out for Signature in your account.
https://echosign-dev1.ap1.visual.force.com/apex/EchoSignAgreementAdvanced?id=[agreementID]&sfdc.override=1&onLoadAction=delete
- Cancel: Make sure you have an agreement with the status Out for Signature in your account.
https://echosign-dev1.ap1.visual.force.com/apex/EchoSignAgreementAdvanced?id=[agreementID]&sfdc.override=1&onLoadAction=cancel
- Update: Make sure you have an agreement with the status Out for Signature in your account.
https://echosign-dev1.ap1.visual.force.com/apex/EchoSignAgreementAdvanced?id=[agreementID]&sfdc.override=1&onLoadAction=update
- View: Make sure you have an agreement with the status Out for Signature, Signed, or Canceled in your account.
https://echosign-dev1.ap1.visual.force.com/apex/EchoSignAgreementAdvanced?id=[agreementID]&sfdc.override=1&onLoadAction=view