Click here to access the current Adobe Acrobat Sign for Salesforce package on the Salesforce AppExchange
Instructions on upgrading your Adobe Acrobat Sign for Salesforce package to the newest version.
The Adobe Acrobat Sign for Salesforce integration package is available from the Salesforce AppExchange. This guide is designed to help current customers of Adobe Acrobat Sign for Salesforce upgrade from an older version to the most current released version.
Refer to the release notes for additional information on the newest features in Adobe Acrobat Sign for Salesforce.
Refer to the installation guide if you are installing a new instance of the package.
Be advised that the Adobe Acrobat Sign for Salesforce objects may change as the package evolves.
If you build a custom solution that depends on these objects, and they change, you may be required to update your customization.
Each version of Adobe Acrobat Sign for Salesforce has new features and enhancements that can provide key improvements to your document workflows. Adobe strongly recommends that you upgrade to the latest release, as Adobe will be discontinuing support of older versions over time.
To find the package version of the Adobe Acrobat Sign for Salesforce integration you currently have installed:
Upgrading from a version prior to 21.5.11 requires that you install the 21.5.11 package before you can install the current package. Attempting to install the current package before 21.5.11 is in place results in a failed update.
Click here to access the current Adobe Acrobat Sign for Salesforce package on the Salesforce AppExchange
Click the Get It Now button
Select Log in to the AppExchange and enter your credentials to continue
Determine where you would like to install the upgrade (production or sandbox)
Review the installation information and terms and conditions, confirm that you have read and agree to the conditions, then click Confirm and Install! to start the installation process
When prompted to login to your Salesforce organization:
When the Upgrade Adobe Acrobat Sign page displays:
If the Approve Third Party Access popup displays:
During installation, a notification page displays telling you this all could take some time...
Click Done and then wait to receive the email notifying you that the package has been installed successfully
Configure any manual updates listed in the What's New section
Refresh the OAuth connection between Adobe Acrobat Sign and Salesforce:
Navigate to Setup > Platform Tools > Apps > Packaging > Installed Packages
Click the Configure link for the Adobe Acrobat Sign package.
If the Setup Wizard doesn’t launch automatically:
In “Step 1: Link your Adobe account to Salesforce” of the Setup Wizard:
Click Next on the successful Step 1 notification
In “Step 2: Enable Adobe Sign Automatic Status Updates”, click the Enable button
Click Next at the bottom of the page to proceed
When the Setup Wizard displays Congrats! Your setup is complete, click Done
Once the installation and configuration of the new package is complete, you should refer to the appropriate sections in this guide for information on which settings and fields were added in previous versions.
You must manually enable these new settings and field values in your org in order for the new package to work correctly. For example, if you are upgrading from v19 to v23, you should enable any manual edits listed for versions v20, v21, and v22.
This feature has been put in place to allow Adobe Sign to collect usage data to improve the product. This data is used only for development and not for marketing purposes.
Admins can enable or disable this feature on the Adobe Sign Admin tab or by running the set-up wizard.
Starting in v23 of the Adobe Sign for Salesforce package, the Files document storage object will be the primary object used in development.
Customers upgrading from versions prior to v23.0 will have their existing default storage type grandfathered into their upgrade (Attachments in most cases) to ensure no breakage of process is experienced.
Admins are advised to evaluate the impact of changing the document storage type to Files to best take advantage of future features.
To support the admin control of the document storage type, a new control has been added to the Custom Settings > Adobe Sign Settings set of controls.
This UI maps to the custom object Agreement_Document_Storage_Type__c
Viable setting values are:
The introduction of Workflows into the Salesforce package requires additional access permissions to be enabled.
If you intend to use workflows, then you must refresh the OAuth links
No manual configurations or system changes are required
Any existing installation that upgrades from a version prior to 21.5.9 must install the 21.5.11 package first.
After v21.5.11 is installed, the current package can be installed.
Chatter must be enabled to install the v21.5.11 package
Before you start the upgrade process, verify that Chatter is enabled:
v21.x brings several updates to the way Adobe Sign for Salesforce operates.
It is strongly recommended that you install v21.x into your sandbox environment first, to verify that all aspects of the application work as you expect.
Developers should take care to review the changes to the update order, and the change in Apex method.
As of v21.0, the SIGN_Signed_Agreement__c object (label name: Signed Agreement") has been deprecated.
Customers that would like to obtain the signed agreement URL should use the REST API agreement call GET /agreements/{agreementId}/combinedDocument/url
Note: The returned URL from the API call is secured, and only viable for a limited time.
Below is the new sequence (as of v21.0) in which the agreement and its related objects are updated:
As of v21.x all asynchronous processes (which include automatic updates and data mappings) have been switched from future methods to queuebale, the new approach recommended by Salesforce.
Due to this change, any customizations in the subscriber org which add jobs to the Salesforce queue as part of the auto update and/or data mapping mapping process will fail with an error "System.LimitException: Too many queueable jobs added to the queue: 2"
This happens because a queuebale process can only add one child queueable job, which is already taken up by Adobe Sign (refer to the "Queueable Apex Limits" section here).
"When chaining jobs, you can add only one job from an executing job with System.enqueueJob, which means that only one child job can exist for each parent queueable job. Starting multiple child jobs from the same queueable job isn’t supported."
The symptom of this error is that the agreement status does not change and/or the data mapping does not run correctly.
To resolve this error, look for the offending trigger, process builder, or workflow and deactivate it or switch it to use a synchronous call or schedule it in the future, for example 1 hr later.
After the upgrade is completed:
In v20, the Callback user in Salesforce was not required be an Adobe Sign licensed user.
The improvements to Push Mapping in v21 require that the Callback user have an active userID in the Adobe Sign account that is connected to the Salesforce organization.
v20 Customers using PushMapping should ensure that the Callback user is already provisioned in Adobe Sign prior to upgrading. Otherwise the PushMapping will stop functioning (until the user is provisioned) after upgrading to v21.
The Push Mapping functionality that automatically linked related objects using the setting ‘Copy Contact Account/Opportunity’ has been expanded to include Agreements sent from Salesforce.
Prior to v21, Chatter feeds were only populated when the agreement was sent from within Salesforce.
This update expands the Chatter feed to include agreements sent from outside Salesforce (Push Agreements)
Prior to v21, the Agreement View only updated the PDF image and URL after the first recipient completed their action.
The image and URL now update earlier, when in a Prefill status, or when Out for Signature to the first recipient.
No configuration is required to enable this functionality.
A new Agreement status of Waiting for My Delegation is being introduced to reflect when an agreement is waiting for the Sender to delegate the current recipient authority.
No configuration is required to enable this status.
The Agreement Template has a "Days Until Expiration" field (echosign_dev1__Days_Until_Expiration__c). This is a numeric field, and has been deprecated in v21.
A new "Days Until Expiration" field (api name: echosign_dev1__Days_Until_Expiration2__c) has been added, but is a text field, allowing it to reference other fields in the Master Object (e.g.{!Expiry_Date__c})
When upgrading from a previous version, any form data mapped to the legacy expiration field is automatically copied to the new field, so no direct action is required.
The Account, Opportunity, and Contract fields are no longer available on the template page.
Admins can configure these fields in the template using the Map Data into Agreement Fields feature
Previously, Senders could define their absolute position in the signature stack as "Sender Signs First" or "Sender Signs Last".
This field is no longer available on the New Template pages. Senders have the option to insert themselves in any position of the signature stack.
The toggle to control the overall signature flow as "Sequential" or "Parallel" has been removed.
The new template style allows a fully configurable workflow that can be wholly sequential (Signer index 1 through 1+N), parallel (All Signer indexes are 1) or a mixture of sequential and parallel where the signature index is configured to the specific workflow.
Five settings have been deprecated in v21. All settings were in the Adobe Sign Settings section of Custom Settings.
The five settings are:
Customers that are using the above settings can configure the new setting under Adobe Sign Agreement Update Settings.
Deprecated Setting (under Adobe Sign Settings) |
New Setting (under Adobe Sign Agreement Update Settings) |
---|---|
Add Audit PDF to Attachment List |
Add Audit Report |
Add Signed PDF as Separate Attachments |
Add Signed PDF as Separate Attachments |
Add Supporting Files to Attachment List |
Add Supporting Files |
Add Signed PDF Link for Pushed Agreements |
Add Signed PDF URL |
Add Signed PDF for Pushed Agreements |
Add Signed PDF |
Version 20.9 of the Adobe Sign for Salesforce package shifts the authorization for the objects used in large document support from the Site user to a licensed “callback” user that is explicitly granted authority.
Please remove all existing permissions on sensitive or nonpublic objects assigned to the site user on the respective site used for Large files or Push Agreement.
My Domain must be configured prior to configuring the Large Document Service to permit the OAuth authentication of the Callback User
For existing customers that are upgrading to 20.9 or beyond, the recommended process is to:
1. Upgrade the Adobe Sign for Salesforce package to 20.9 (or later)
2. Create the new Callback User profile
Only one Callback User is permitted for Adobe Sign. If you already have one established, configure that existing Profile/User.
3. Enable the Attachment Service Invocation Count for the Callback User profile
4. Create a new user using a standard Salesforce License
5. Define the Callback User
5. Update the existing Site
Version 20.9 of the Adobe Sign for Salesforce package shifts the authorization for the objects used in push agreement support from the Site user to a licensed “callback” user that is explicitly granted authority.
Please remove all permissions assigned to site user on the respective sites.
My Domain must be configured prior to configuring Push Agreements to permit the OAuth authentication of the Callback User
For existing customers that are upgrading to 20.9 or beyond, the recommended process is to:
1. Create the new callback user
Only one Callback User is permitted for Adobe Sign. If you already have one established, configure that existing Profile/User.
2. Create a new “callback” user using a standard Salesforce license
3. Upgrade the Adobe Sign for Salesforce package to 20.9 (or later)
4. Define the Callback User
5. Update the existing Site
Organizations that use the Lightning interface in Salesforce must have My Domain enabled for v20 of the Adobe Sign package to function properly.
Organizations using the Classic interface are not required to have My Domain configured at this time.
v20 of the Adobe Sign package includes three new recipient roles:
To gain access to these roles, they must be added in a three step process (four steps if you want to localize the roles to non-english languages).
Enable the roles in Adobe Sign:
Enable the roles in the custom settings (Salesforce):
The setting values are:
Delegators – All recipient roles have a "delegator" version. Delegator roles are used when the known recipients are not expected to complete the identified role. Rather, they will delegate their role to another party.
Delegator roles are enabled by the same process described above.
The available delegator setting values are:
The status values of the recipient and agreement objects are tied directly to the roles that are enabled in the system. If you are enabling additional roles, then you also need to add the associated role values to various object picklists. The process is consistent for each object, with some variation in the values added depending on the context of the object.
The object > fields that need to be updated are:
The field values that should be added are:
Object Name |
Field |
New Values to be Added |
---|---|---|
Agreement |
Agreement Status |
Out for Form-Filling Waiting for Counter-Form-Filling Form-Filled Out for Acceptance Waiting for Counter-Acceptance Accepted Out for Delivery Waiting for Counter-Delivery Delivered |
Recipient |
Recipient Role |
Acceptor Form Filler Certified Recipient Delegate to Acceptor Delegate to Form Filler Delegate to Certified Recipient |
Recipient |
Status |
Accepted Form-Filled Delivered Waiting for Acceptance Waiting for Form-Filling Waiting for Delivery |
Add Recipient |
Recipient Role |
Acceptor Form Filler Certified Recipient Delegate to Acceptor Delegate to Form Filler Delegate to Certified Recipient |
Field Mapping |
Map on Events |
Out for Form-Filling Waiting for Counter-Form-Filling Form-Filled Out for Acceptance Waiting for Counter-Acceptance Accepted Out for Delivery Waiting for Counter-Delivery Delivered |
File Mapping |
Map on Events |
Out for Form-Filling Waiting for Counter-Form-Filling Form-Filled Out for Acceptance Waiting for Counter-Acceptance Accepted Out for Delivery Waiting for Counter-Delivery Delivered |
The process to add the values and localize them is consistent across all objects.
Below is the process for Recipient > Recipient Role, and can be applied for each object in turn.
Add the roles to the Recipient picklist:
Once the new roles are enabled, the pick list values for the fields must be updated to include them.
1. Navigate to Setup > Platform Tools > Objects and Fields > Object Manager
2. Select Recipient form the list on the left
3. Select Fields & Relationships form the left rail
4. Select the Recipient Role field
5. Scroll down the page to the Values section, and select New
6. Enter the new Role values that you have enabled. Valid values are:
7. Click Save when done
The resulting picklist should look like this (assuming you added all roles):
Localize the role statuses through the translation workbench:
1. Navigate to: Setup > Platform Tools > User Interface > Translation Workbench > Translate
2. Click Save when done
The Document field of the Agreement object contains a hyperlink to the agreement. There are two changes to this field in the v20 release:
Prior to v20, hyperlink text contained the agreement name and the status “- signed” or “- approved” appended to the end:
Version 20 removes the appended status, leaving just the agreement name:
In the v20 package, the Document field always contains the latest PDF version of the Agreement:
The Help Text for the Chatter event Post when Agreement Sent can be updated to remain consistent with the new recipient roles.
4. Update the Help Text to read: Post Chatter update when agreement is sent for signature/approval/acceptance/ form-filling/delivery.
5. Click Save
With the v19 release, the organization's CRUD and FLS settings on both standard and custom objects are enforced. As a result, many configured features must be updated to include explicit access to the various objects needed.
Two steps may be involved:
Please see the Manual Update listings below for the various features/processes that are impacted.
As Adobe Sign has expanded, the infrastructure has shifted to more robust data centers, and this has caused some changes in the IP ranges that your Salesforce organization needs to trust to ensure optimal communication between the services.
Below are the incremental changes from v18 to v19. Ensure that any sites configured are updated in addition to the core trusted networks.
ADD: India: |
13.126.23.0/27 |
REMOVE: North America: |
166.78.79.112/28 207.97.227.112/28 |
With the v19 release, the organization's CRUD and FLS settings on both standard and custom objects are enforced. The App checks object and field level, read and write permissions. If the user doesn't have appropriate access, a permission denied error is shown.
After upgrading to v19, if a salesforce users gets permission denied error similar to:
Permission denied. Unable to insert field echosign_dev1__Contract__c in object: echosign_dev1__SIGN_Agreement__c
then the salesforce admin needs to add both read and write permissions to the agreement object, and for any custom fields they have created, to the relevant profiles.
There is one deprecated custom settings in version 19:
There is one new tab in v19: Agreement Types
Add the parent lookup field called Agreement Type (Agreement_Type__c) to the Agreement Template Page Layout:
Upgrading customers are strongly recommended to adopt use of the Lightning page to ensure that new features are available as development continues to improve the product.
That said, there may be very good reasons you need to stay on one of the older page layouts. Refer to the guide on adjusting your Salesforce page layout to determine if moving to the Lightning page is best.
When the Adobe Sign application for Salesforce is upgraded from versions lower than v14 to the current build, users might not be able to perform actions such as Delete, Cancel, View, Remind, or Update on the existing agreements that were sent by other users before upgrade.
Users may prompt an error when one of these actions is executed, similar to:
“INVALID_DOCUMENT_KEY” or “An internal server error has occurred”
This happens due to a legacy document key style that was used in versions of the application before version 14.
A one-time migration of those legacy keys is required. To this end, a new affordance as described below:
After completing the set-up steps, the following links will be available on the Adobe Sign Admin page:
In case there are any agreements that don’t have associated document keys, it will fetch document keys for them as well
Once the agreements have new document keys, users will be able to perform all agreement actions on existing agreements sent by other users.
The links for Fetch Missing Document keys and Update Legacy Document keys are only visible when the admin upgrades from a version lower than v14 to v19.4.
If the admin updates a package between v14 and v19.2, the links are hidden by default. In this case, the admin can contact Adobe Sign Support to manually expose the links.
This action requires that you grant log in access to Adobe Sign Support.
Add Signed PDF Link for Pushed Agreement - This setting applies only for pushed agreements sent outside of Salesforce. Enable this setting to add a link for signed PDF to the Agreement record.
Any user directly interacting with Group Mappings, will need to ensure that they have the correct permissions.
Below is an explicit listing of the objects, and the required fields, if using the permission set is not acceptable for any reason:
Object |
Field |
Required values |
Standard/Custom |
Adobe Sign Permission Set |
---|---|---|---|---|
Echo Sign Group Mapping |
|
Read, Delete, Create, Modify |
Adobe Sign - Custom |
Adobe Sign Admin |
|
All Fields |
Read, Modify |
|
|
|
|
|
|
|
EchoSign User Sync Result |
|
Read, Delete, Create |
Adobe Sign - Custom |
Adobe Sign Admin |
|
All Fields |
Read, Modify |
|
|
Any user that uses the Adobe Sign API will require the Adobe Sign User permission set.
Below is an explicit listing of the objects, and the required fields, if using the permission set is not acceptable for any reason:
Object |
Field |
Required values |
Standard/Custom |
Adobe Sign Permission Set |
---|---|---|---|---|
Recipient |
|
Read |
Adobe Sign - Custom |
Adobe Sign User |
|
Status |
Read |
|
|
|
Order Number |
Read |
|
|
|
Source Recipient |
Read |
|
|
|
Agreement |
|
|
|
|
|
|
|
|
Agreement |
|
Read |
Adobe Sign - Custom |
Adobe Sign User |
|
Authoring |
Read |
|
|
For users to interact with the Self Signing component for Adobe Sign:
Below is an explicit listing of the objects, and the required fields, if using the permission set is not acceptable for any reason:
Object | Field | Required values | Standard/Custom | Adobe Sign Permission Set |
---|---|---|---|---|
Contact | Read | Salesforce -Standard | ||
Read | ||||
Agreement | Read | Adobe Sign - Custom | Adobe Sign User | |
Name | Read | |||
Status | Read | |||
Date Signed | Read | |||
Error Message | Read | |||
Signed PDF | Read | |||
Document Key | Read | |||
Agreement Template | Read | Adobe Sign - Custom | Adobe Sign User | |
All Fields | Read | |||
Agreement Type | Read | Adobe Sign - Custom | Adobe Sign User | |
Name | Read | |||
Recipient | Read | Adobe Sign - Custom | Adobe Sign User | |
Agreement | Read | |||
Status | ||||
Date Time Complete |
Users that interact with the Agreement Templates require:
Below is an explicit listing of the objects, and the required fields, if using the permission set is not acceptable for any reason:
Object |
Field |
Required values |
Standard/Custom |
Adobe Sign Permission Set |
---|---|---|---|---|
Master Object Specified By User |
|
|
|
|
|
All Fields Specified by User |
Read |
N/A |
|
|
|
|
|
|
Agreement template |
|
Read |
Adobe Sign - Custom |
Adobe Sign Admin |
|
Name |
Read |
|
|
|
Master Object Type |
Read |
|
|
Users that trigger batch actions will require:
Below is an explicit listing of the objects, and the required fields, if using the permission set is not acceptable for any reason:
Object |
Field |
Required values |
Standard/Custom |
Adobe Sign Permission Set |
---|---|---|---|---|
Agreement |
|
Read |
Adobe Sign - Custom |
Adobe Sign Admin |
|
Document Key |
Read |
|
|
|
Cancel Delete Reason |
Read |
|
|
|
Cancel Delete Notify Signer |
Read |
|
|
|
Partner Server URL |
Read |
|
|
|
Status |
Read |
|
|
|
Last Event ID |
Read |
|
|
Any user that uses Adobe Sign through S1 Mobile will require:
Below is an explicit listing of the objects, and the required fields, if using the permission set is not acceptable for any reason:
Object | Field | Required values | Standard/Custom | Adobe Sign Permission Set |
---|---|---|---|---|
Opportunity | Read | Salesforce -Standard | ||
Name | Read | |||
Account | Read | Salesforce -Standard | ||
Name | Read | |||
Contract | Read | Salesforce -Standard | ||
Name | Read | |||
Contract Number | Read | |||
Contact | Read | Salesforce -Standard | ||
Name | Read | |||
Read | ||||
Lead | Read | Salesforce -Standard | ||
Name | Read | |||
Read | ||||
Document | Read | Salesforce -Standard | ||
Name | Read | |||
Type | Read | |||
Content Type | Read | |||
Body | Read | |||
Agreement Event | Read | Adobe Sign - Custom | Adobe Sign User | |
All Fields | Read | |||
Agreement Template | Read | Adobe Sign - Custom | Adobe Sign User | |
Agreement | Read, Create, Delete, Modify | Adobe Sign - Custom | Adobe Sign User | |
All Fields | Create, Modify | |||
Recipient | Read, Create, Delete, Modify | Adobe Sign - Custom | Adobe Sign User | |
All Fields | Create, Modify | |||
Library Templates | Read, Create, Delete, Modify | Adobe Sign - Custom | Adobe Sign User | |
All Fields | Create, Modify |
Users that need access to the Administration tab require the Adobe Sign Admin permission set.
Below is an explicit listing of the objects, and the required fields, if using the permission set is not acceptable for any reason:
Object |
Field |
Required values |
Standard/Custom |
Adobe Sign Permission Set |
---|---|---|---|---|
Agreement Template |
|
Read |
Adobe Sign - Custom |
Adobe Sign Admin |
|
|
|
|
|
Agreement |
|
Read |
Adobe Sign - Custom |
Adobe Sign Admin |
|
|
|
|
|
Document |
|
Read |
Adobe Sign - Custom |
Adobe Sign Admin |
|
Body |
Read |
|
|
Users that leverage the Publisher actions require:
Below is an explicit listing of the objects, and the required fields, if using the permission set is not acceptable for any reason:
Object | Field | Required values | Standard/Custom | Adobe Sign Permission Set |
---|---|---|---|---|
Contact | Read | Salesforce -Standard | ||
Name | Read | |||
Read | ||||
Lead | Read | Salesforce -Standard | ||
Name | Read | |||
Read | ||||
Opportunity | Read | Salesforce -Standard | ||
Name | Read | |||
Account | Read | Salesforce -Standard | ||
Name | Read | |||
Document | Read | Salesforce -Standard | ||
Name | Read | |||
Content Type | Read | |||
Body | Read | |||
Type | Read | |||
Quote | Read | Salesforce -Standard | ||
Agreement | Create, Modify | Adobe Sign - Custom | Adobe Sign User | |
All Fields | Modify | |||
Agreement Template | Read | Adobe Sign - Custom | Adobe Sign User | |
Password | Read | |||
Name | Read | |||
Default | Read | |||
Recipient | Create | Adobe Sign - Custom | Adobe Sign User | |
All Fields | Modify | |||
Library Templates | Create | Adobe Sign - Custom | Adobe Sign User | |
All Fields | Modify |
Users that edit Templates will require:
Below is an explicit listing of the objects, and the required fields, if using the permission set is not acceptable for any reason:
Object | Field | Required values | Standard/Custom | Adobe Sign Permission Set |
---|---|---|---|---|
Contact | Read | Salesforce -Standard | ||
Lead | Read | Salesforce -Standard | ||
Document | Read | Salesforce -Standard | ||
URL | Read | |||
Agreement Template | Read, Delete, Create, Modify | Adobe Sign - Custom | Adobe Sign Admin | |
All Fields | Read, Modify | |||
Add Recipients | Read, Delete, Create, Modify | Adobe Sign - Custom | Adobe Sign Admin | |
All Fields | Read, Modify | |||
File Attachments | Read, Delete, Create, Modify | Adobe Sign - Custom | Adobe Sign Admin | |
All Fields | Read, Modify | |||
Add Form Field Template | Read, Delete, Create, Modify | Adobe Sign - Custom | Adobe Sign Admin | |
All Fields | Read, Modify | |||
Map Data Into Agreement | Read, Delete, Create, Modify | Adobe Sign - Custom | Adobe Sign Admin | |
All Fields | Read, Modify |
The Agreement Template Processor requires:
Below is an explicit listing of the objects, and the required fields, if using the permission set is not acceptable for any reason:
Object | Field | Required values | Standard/Custom | Adobe Sign Permission Set |
---|---|---|---|---|
Contact | Read | Salesforce -Standard | ||
Mobile Phone | Read | |||
Lead | Read | Salesforce -Standard | ||
Mobile Phone | Read | |||
Opportunity | Read | Salesforce -Standard | ||
Account | Read | Salesforce -Standard | ||
Quote | Read | Salesforce -Standard | ||
Attachment | Access based on parent record. | |||
Agreement | Create, Modify | Adobe Sign - Custom | Adobe Sign User | |
Signature Type | Modify | |||
Status | Modify | |||
Days Until Signing Deadline | Modify | |||
Enable Automatic Reminders | Modify | |||
Remind Recipient | Modify | |||
Recipient Addresses | Modify | |||
More Recipients | Modify | |||
Signature Order | Modify | |||
Authoring | Modify | |||
Process Template | Modify | |||
Recipient | Create | Adobe Sign - Custom | Adobe Sign User | |
Recipient Type | Modify | |||
Recipient Role | Modify | |||
Order Number | Modify | |||
Email Address | Modify | |||
Library Template | Create | Adobe Sign - Custom | Adobe Sign User | |
All Fields | Modify | |||
Agreement Type | Read | Adobe Sign - Custom | Adobe Sign Admin | |
Agreement Template | Read | Adobe Sign - Custom | Adobe Sign Admin | |
All Fields | Read | |||
Add Recipients | Read | Adobe Sign - Custom | Adobe Sign Admin | |
All Fields | Read | |||
File Attachments | Read | Adobe Sign - Custom | Adobe Sign Admin | |
All Fields | Read | |||
Add Form Field Template | Read | Adobe Sign - Custom | Adobe Sign Admin | |
All Fields | Read | |||
Map Data Into Agreement | Read | Adobe Sign - Custom | Adobe Sign Admin | |
All Fields | Read |
Users that edit agreements require:
Below is an explicit listing of the objects, and the required fields, if using the permission set is not acceptable for any reason:
Object | Field | Required values | Standard/Custom | Adobe Sign Permission Set |
---|---|---|---|---|
Lead | Read | Salesforce -Standard |
||
Company | Read | |||
Event | Create | Salesforce -Standard | ||
All Fields | Modify | |||
Agreement | Read, Create, Modify, Delete | Adobe Sign - Custom | Adobe Sign User | |
All Fields | Read, Modify | |||
Recipient | Read, Create, Modify, Delete | Adobe Sign - Custom | Adobe Sign User | |
Agreement | Read | |||
Status | Read | |||
Date Time Completed | Read | |||
Order Number | Read | |||
Recipient Type | Read | |||
Agreement | Read | |||
Email Address | Read | |||
Recipient Type | Modify | |||
Recipient Role | Modify | |||
Order Number | Modify | |||
Email Address | Modify | |||
Library Template | Create, Modify, Delete | Adobe Sign - Custom | Adobe Sign User | |
All Fields | Read, Modify | |||
Agreement Type | Read | Adobe Sign - Custom | Adobe Sign User | |
Name | Read | |||
Agreement Template | Read | Adobe Sign - Custom | Adobe Sign User | |
Agreement Type | Read | |||
Name | Read | |||
Default | Read | |||
Auto Send | Read | |||
Signed Agreement | Read | |||
Merge Mapping | Read | Adobe Sign - Custom | Adobe Sign User |
Users that edit the Merge Mappings require:
Below is an explicit listing of the objects, and the required fields, if using the permission set is not acceptable for any reason:
Object | Field | Required values | Standard/Custom | Adobe Sign Permission Set |
---|---|---|---|---|
Any object which is mapped to. | Read, Modify | |||
Any field which is mapped to. | Read, Modify | |||
Agreement | Read | Adobe Sign - Custom | Adobe Sign Admin | |
Document Key | Read | |||
Form Field Import | Read, Delete, Create, Modify | Adobe Sign - Custom | Adobe Sign Admin | |
All Fields | Read, Modify | |||
Form Field Mapping | Read, Delete, Create, Modify | Adobe Sign - Custom | Adobe Sign Admin | |
All Fields | Read, Modify | |||
Form Field Mapping Entry | Read, Delete, Create, Modify | Adobe Sign - Custom | Adobe Sign Admin | |
All Fields | Read, Modify | |||
Form Field Child Mapping | Read, Delete, Create, Modify | Adobe Sign - Custom | Adobe Sign Admin | |
All Fields | Read, Modify | |||
Form Field Child Mapping Entry | Read, Delete, Create, Modify | Adobe Sign - Custom | Adobe Sign Admin | |
All Fields | Read, Modify | |||
Merge Mapping | Read, Delete, Create, Modify | Adobe Sign - Custom | Adobe Sign Admin | |
All Fields | Read, Modify |
Users that leverage merge mappings require:
Below is an explicit listing of the objects, and the required fields, if using the permission set is not acceptable for any reason:
Object | Field | Required values | Standard/Custom | Adobe Sign Permission Set |
---|---|---|---|---|
Any object which is mapped to | Read, Modify | |||
Any field which is mapped to | Read, Modify | |||
Account | ||||
Name | Read | Salesforce -Standard | ||
Opportunity | ||||
Name | Read | Salesforce -Standard | ||
Agreement | Read | Adobe Sign - Custom | Adobe Sign User | |
Document Key | Read | |||
Additional Options | Read | |||
Name | Read | |||
Merge Mapping | Read | |||
Merge Mapping Error | Read | |||
Merge Mapping Result | Read | |||
Account | Read | |||
Opportunity | Read | |||
Form Field Import | Read | Adobe Sign - Custom | Adobe Sign User | |
All Fields | Read | |||
Form Field Mapping | Read | Adobe Sign - Custom | Adobe Sign User | |
All Fields | Read | |||
Form Field Mapping Entry | Read | Adobe Sign - Custom | Adobe Sign User | |
All Fields | Read | |||
Form Field Child Mapping | Read | Adobe Sign - Custom | Adobe Sign User | |
All Fields | Read | |||
Form Field Child Mapping Entry | Read | Adobe Sign - Custom | Adobe Sign User | |
All Fields | Read | |||
Merge Mapping | Read | Adobe Sign - Custom | Adobe Sign User | |
All Fields | Read |
Users that edit the Data Mappings require:
Below is an explicit listing of the objects, and the required fields, if using the permission set is not acceptable for any reason:
Object | Field | Required values | Standard/Custom | Adobe Sign Permission Set |
---|---|---|---|---|
Any object which is mapped to | Read, Modify | |||
Any field which is mapped to | Read, Modify | |||
Agreement | Read | Adobe Sign - Custom | Adobe Sign Admin | |
Document Key | Read | |||
File Mapping | Read, Delete, Create, Modify | Adobe Sign - Custom | Adobe Sign Admin | |
All Fields | Read, Modify | |||
Field Mapping | Read, Delete, Create, Modify | Adobe Sign - Custom | Adobe Sign Admin | |
All Fields | Read, Modify | |||
Object Mapping | Read, Delete, Create, Modify | Adobe Sign - Custom | Adobe Sign Admin | |
All Fields | Read, Modify | |||
Data Mapping | Read, Delete, Create, Modify | Adobe Sign - Custom | Adobe Sign Admin | |
All Fields | Read, Modify |
Data Mapping processing requires:
Below is an explicit listing of the objects, and the required fields, if using the permission set is not acceptable for any reason:
Object | Field | Required values | Standard/Custom | Adobe Sign Permission Set |
---|---|---|---|---|
Any object which is mapped to | Read, Modify | |||
Any field which is mapped to | Read, Modify | |||
Attachment | Access based on parent record. | |||
Agreement | Read, Modify | Adobe Sign - Custom | Adobe Sign Integration | |
All Fields | Read, Modify | |||
File Mapping | Read | Adobe Sign - Custom | Adobe Sign Integration | |
All Fields | Read | |||
Field Mapping | Read | Adobe Sign - Custom | Adobe Sign Integration | |
All Fields | Read | |||
Object Mapping | Read | Adobe Sign - Custom | Adobe Sign Integration | |
All Fields | Read | |||
Data Mapping | Read | Adobe Sign - Custom | Adobe Sign Integration | |
All Fields | Read |
The Chatter integrations requires:
Below is an explicit listing of the objects, and the required fields, if using the permission set is not acceptable for any reason:
Object |
Field |
Required values |
Standard/Custom |
Adobe Sign Permission Set |
---|---|---|---|---|
Agreement Event |
|
Read |
Adobe Sign - Custom |
Adobe Sign Integration |
|
Type |
Read |
|
|
|
Description |
Read |
|
|
|
|
|
|
|
Recipients |
|
|
Adobe Sign - Custom |
Adobe Sign Integration |
|
Recipient Type |
Read |
|
|
|
Email Address |
Read |
|
|
|
Order Number |
Read |
|
|
|
Use Email Address |
Read |
|
|
Push Agreements require that the linked Callback User have:
Below is an explicit listing of the objects, and the required fields, if using the permission set is not acceptable for any reason:
Object | Field | Required values | Standard/Custom | Adobe Sign Permission Set |
---|---|---|---|---|
Account | Read | Salesforce -Standard | ||
Contract | Read | Salesforce -Standard | ||
Opportunity | Read | Salesforce -Standard | ||
Lead | Read, Create | Salesforce -Standard | ||
Read, Modify | ||||
Name | Read, Modify | |||
Company | Read, Modify | |||
Contact | Read, Create | Salesforce -Standard | ||
Read, Modify | ||||
Name | Read, Modify | |||
Account | Read, Modify | |||
Agreement | Read, Create, Modify | Adobe Sign - Custom |
Adobe Integration User | |
All Fields | Read, Modify | |||
Agreement Type | Read | Adobe Sign - Custom | Adobe Integration User | |
Mutexes | Read, Create, Modify | Adobe Sign - Custom | Adobe Integration User | |
All Fields | Read, Modify | |||
Triggers | Create | Adobe Sign - Custom | Adobe Integration User | |
All Fields | Modify | |||
Recipient | Create | Adobe Sign - Custom | Adobe Integration User | |
All Fields | Modify | |||
Agreement Event | Create | Adobe Sign - Custom | Adobe Integration User | |
All Fields | Modify | |||
Data Mapping | Read | Adobe Sign - Custom | Adobe Integration User | |
Merge Mapping | Read | Adobe Sign - Custom | Adobe Integration User |
The Callback User must be configured and linked:
Additionally, the Site profile must be edited to:
Below is an explicit listing of the objects, and the required fields, if using the permission set is not acceptable for any reason:
Object |
Field |
Required values |
Standard/Custom |
Adobe Sign Permission Set |
---|---|---|---|---|
Agreement |
|
Read, Modify |
Adobe Sign - Custom |
Adobe Integration User |
|
Attachment Service Invocation Count |
Read, Modify |
|
|
Prijavite se v svoj račun