Instructions on upgrading your Adobe Sign for Salesforce package to the newest version.

The Adobe Sign for Salesforce integration package is available from the Salesforce AppExchange. This guide is designed to help current customers of Adobe 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 Sign for Salesforce.

Refer to the installation guide if you are installing a new instance of the package.

Note:

Support for the Adobe Sign for Salesforce integration v18 has ended as of March 1, 2019

Product updates, security updates and technical support for Adobe Sign for Salesforce v18 has ended.

If you are on version 18 or older, please upgrade to the new package to ensure the continuation of support.


Upgrading from a previous release

Caution:

Be advised that the Adobe 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 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 Sign for Salesforce integration you currently have installed:

  1. Log into Salesforce as your account admin ID
  2. Navigate to Setup > Platform Tools > Apps > Packaging > Installed Packages
version


Important upgrade notes for all customers

  1. If you have users in your Salesforce org who belong to multiple Adobe Sign accounts, reach out to your Adobe client success manager or to Adobe support before upgrading.
  2. Before upgrading your production account, Adobe recommends testing the upgrade process in your Salesforce sandbox environment.
  3. Ensure that your email address in the Sandbox environment is one that you have access to in case you need to change the email for your Adobe Sign account.


Upgrading the package

Caution:

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.

  1. Do not uninstall your existing Adobe Sign for Salesforce package.
    • Uninstalling the package will result in the loss of all your Adobe Sign data in Salesforce.
  2. Ensure that the Lock sessions to the IP address from which they originated setting is disabled.
    • To do this, navigate to Setup > Settings > Security > Session Settings
  3. Review the "What's New" sections below to determine if there are options you need to manually configure. 
    • A number of new features/settings are added in every release.  Often these new features require a manual update to to the service configuration to expose their use.


Installing the Adobe Sign for Salesforce update

  1. Click here to access the current Adobe Sign for Salesforce package on the Salesforce AppExchange.
  2. Click the Get It Now button.
  3. Select Log in to the AppExchange and enter your credentials to continue.
  4. Determine where you would like to install the upgrade (production or sandbox)
    • It is strongly recommended that every installation/upgrade be tested in the sandbox environmenty first
  5. 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.
  6. When prompted to login to your Salesforce organization, enter your Salesforce Username and Password then click Login in to Salesforce.
  7.  When the Upgrade Adobe Sign page displays:
    • Select Install for All Users 
    • Click Upgrade (Installation can take a few minutes.)
  8.  If the Approve Third Party Access popup displays:
    • Check Yes, grant access to these third-party web sites
    • Click Continue to start the installation.
  9. During installation, a notification page displays telling you this all could take some time...
  10. Click Done and then wait to receive the email notifying you that the package has been installed successfully.
    • The Installed Package page now displays your current package version
  11. Configuree any manual updates listed in the What's New section

Post-Install Configuration

A few simple setup steps are required before you can start sending Adobe Sign agreements from Salesforce.

  1. Navigate to Setup > Platform Tools > Apps > Packaging > Installed Packages
  2. Click the Configure link for the Adobe Sign package
    • The Adobe Sign for Salesforce Setup Wizard should launch.

Note:

If the Setup Wizard doesn’t launch automatically:

  1. Navigate to the Adobe Sign Admin tab
  2. Click the Launch Setup Wizard link

Launch setup

    3. In “Step 1: Link your Adobe account to Salesforce” of the Setup Wizard:

  • Click Sign in to Adobe 
  • Log in with your Adobe Sign admin user
  • Allow Access if challenged
    • You should get a message saying Success! You have successfully authorized your Adobe account.

    4. Click Next on the successful Step 1 notification

    5. In “Step 2: Enable Adobe Sign Automatic Status Updates”, click the Enable button

  • When challenged to allow access to Adobe Sign, click Allow
  • A message should pop up: Success! You have successfully enabled Automatic Status Updates for your account.

    6. Click Next at the bottom of the page to proceed

    7. When the Setup Wizard displays Congrats! Your setup is complete, click Done.

Note:

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 v18 to v22, you should enable any manual edits listed for versions v19, v20, and v21.


What’s new:

Package version 22.x

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


Package version 21.5.11
Required installation package for all versions that pre-date v21.5.9

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:

  • Navigate to: Setup > Platform Tools > Feature Settings > Chatter > Chatter Settings
  • If Chatter is Disabled, click the Edit button
    • Check the Enabled check box
    • Save the page
Enable Chatter


Package version v21.x

Note:

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:

  1. Attachments 
  2. Recipients 
  3. Agreement (status and its other attributes)
  4. Agreement Events 
  5. Chatter Feeds 

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.

  • The agreement status is now updated after the documents and recipients are updated
    • Prior to v21 the status was set before.
  • The Signed Agreement object (which stores the Image URLs) is now not inserted at all
    • Prior to v21 it was inserted after all of the other updates were completed
  • Maximum size of callout request or response is limited to 12MB for asynchronous Apex as per Salesforce governor limits: https://developer.salesforce.com/docs/atlas.en-us.210.0.apexcode.meta/apexcode/apex_gov_limits.htm
    • Documents larger than 12MB can not be fetched from Sign due to above limit.
  • Agreement event descriptions have changed. It now matches the description as returned by Sign API and with the audit reports.
  • The update process is now run as a native Apex batch process (which is an asynchronous process) within Salesforce
    • Before it was an update using API calls from outside of Salesforce
    • Triggers off these status updates which kick off async processes no longer work because Salesforce limits calling another async process from an already running async process
  • Prior to v21, the agreement attribute updates were split up into separate update calls, now agreement object is updated all in one transaction.
  • Prior to v21, failed agreements could be only retried by doing a manual update from within Salesforce
    • Now updates are more reliable as the Sign backend automatically retries failed events for a specified number of times.
  • Manual updates now update all aspects of agreements including the related objects.
  • Push agreements now run in async mode, same as regular updates and additional attributes are updated, the same as regular updates.
  • There are new settings introduced to enable disable updates of different aspects of the agreement.
  • When a signed PDF is stored in Salesforce, there will no longer be a descriptor (-signed or -approved) appended to the end of the PDF file name.

After the upgrade is completed:

  • Navigate to the Adobe Sign Admin tab 
  • Click the Enable Automatic Status Updates link to reestablish the OAuth connection to Adobe Sign
  • Click Enable
  • Click Allow to allow access
enable_status_updates

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.

  • e.g. Agreements sent from Salesforce will automatically copy the first Contact recipient’s Opportunity lookup to the Agreement’s Opportunity lookup and first Contact recipient’s Account lookup to the Agreement’s Account lookup, if the agreements sent do not have any linked Account/Opportunity

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:

  • Add Audit PDF to Attachment List—Enable this setting to attach the PDF of the audit trail to the Agreement record after the agreement is signed.
  • Add Signed PDF as Separate Attachments—Enable this setting to attach the PDF of the signed agreements as separate attachments when there are multiple documents sent in a single transaction. To stop receiving the signed agreement as a merged PDF, please contact Adobe Support for assistance. 
  • Add Supporting Files to Attachment List—Enable this setting to attach the PDFs of the supporting documents to the Agreement record after the agreement is signed. Through the supporting document fields in the agreement, the signers upload and attach the supporting documents to the agreement transaction.
  • Add Signed PDF Link for Pushed Agreements (Enabled by Default)—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.
  • Add Signed PDF for Pushed Agreements (Enabled by Default)—The setting applies to agreements sent from outside of Salesforce and pushed into Salesforce. Enable this setting to attach the signed PDF to the Agreement record. 

 

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


Security Patch v20.9 - Modifications for Callback Sites

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.

Note:

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

Note:

Only one Callback User is permitted for Adobe Sign. If you already have one established, configure that existing Profile/User.

  • 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
      • Under Custom Object Permissions, enable all values for the Agreement object
      • Ensure these Visualforce pages are enabled 
        • echosign_dev1.EchosignAdmin
        • echosign_dev1.SalesforceOAuthPage
      • Enable the echosign_dev1. AgreementAttachmentDownloadService Apex class
    • Save the profile

 

3. 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

 

4. 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
  • Save the new user
  • Verify the user to establish the known password
  • Log out of Salesforce

 

5. Define the Callback User

  • Log in to Salesforce as the Callback User
  • Navigate to the Adobe Sign Admin page
  • Click Link an Account under the Callback User header
    • An Allow Access? page is presented seeking to link the currently authenticated userID
  • Click Allow
    • Verify that the callback user is correctly linked
  • Log out of Salesforce

 

5. Update the existing Site 

  • Log in as your Salesforce Admin
  • Navigate to Platform Tools > User Interface > Sites and Domains > Sites
  • Click the Site Label to open the site details
  • Click the Public Access Settings button
  • Mouse over the Enabled Apex Class Access link, and click the Edit button
    • Remove the AgreementAttachmentService class
    • Add the LargeFileDownloadService class
    • Save the page
  • Click the Edit button on the Adobe Sign Callback Profile page
    • Remove all permissions explicitly assigned to Site User
    • Click Save

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.

Note:

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

Note:

Only one Callback User is permitted for Adobe Sign. If you already have one established, configure that existing Profile/User.

  • Clone the Standard User profile
  • Name the new profile with an intuitive name (eg: Adobe Sign callback user)
  • Save the profile

 

2. Create a new “callback” 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
    • Save the new user
  • Assign the Adobe Sign Integration User permission set to the callback user created above
    • Save the permission set

 

3. Upgrade the Adobe Sign for Salesforce package to 20.9 (or later)

 

4. Define the Callback User

  • Once the upgrade is complete, 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
    • An Allow Access? page is presented seeking to link the currently authenticated userID
  • Click Allow
    • Verify that the callback user is correctly linked
  • Log out of Salesforce

 

5. Update the existing Site 

  • Log in to Salesforce as your admin user
  • Navigate to Platform Tools > User Interface > Sites and Domains > Sites
  • Click the Site Label to open the site details
  • Click the Public Access Settings button
  • Click the View Users button
  • Click on the Full Name link of the Site user
  • Mouse over the Permission Set Assignments link, and click the Edit Assignments button
  • Remove the Adobe Sign Integration User permission set
  • Remove all other permissions explicitly assigned to Site User
  • Click Save

 


Package version 20.x

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:

  • Acceptor - The Acceptor role is appropriate when the Recipient needs to acknowledge an acceptance of the Agreement without formally approving the content
  • Form Filler - Designed specifically for customers that have a need to fill in form content during the signature process
  • Certified Recipient - Certified Recipients can have no (zero) form fields assigned to them. During their "signature" process, they will be asked to either delegate, decline or acknowledge the agreement

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:

  1. Log in to Adobe Sign as an administrator
  2. Navigate to Account > Account Settings > Send Settings > Allowed Recipient Roles
  3. Enable the roles you need to support
  4. Click Save
navigate_to_rolesinadobesign

 

Enable the roles in the custom settings (Salesforce):

  1. Log into Salesforce as and administrator
  2. Navigate to Setup > Platform Tools > Custom Code > Custom Settings
  3. Click the label Adobe Sign Settings
  4. Click the Manage button
  5. Click New (or Edit, if you have configured settings before)

The setting values are: 

  • Enable Acceptor Role - Recipients marked as acceptors accept the document. They may be required to enter field data
  • Enable Form Filler Role - Form fillers are enabled to fill in field level data
  • Enable Certified Recipient Role - Certified Recipients acknowledge the agreement, but do not sign. They may be required to fill in field data

Note:

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:

  • Enable Delegate Acceptor Role - Needed when you want to delegate an Acceptor role
  • Enable Delegate Certified Recipient Role - Needed when you plan to delegate a certified recipient
  • Enable Delegate Form Filler Role - Used when you have to delegate a Form Filler role
  • Enable Recipient Delegate Approver Role – Needed when you plan to delegate to Approvers
  • Enable Recipient Delegate Signer Role – Needed when you are going to delegate to Signers

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:

  • Recipient > Recipient Role
  • Recipient > Status
  • Add Recipient > Recipient Role
  • Agreement > Agreement Status
  • Field Mapping > Map on Events
  • File Mapping > Map on Events

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:

  • Acceptor
  • Form Filler
  • Certified Recipient
  • Delegate to Acceptor
  • Delegate to Form Filler
  • Delegate to Certified Recipient

7. Click Save when done

role_picklist

 

The resulting picklist should look like this (assuming you added all roles):

full_role_picklist

 

Localize the role statuses through the translation workbench:

1. Navigate to: Setup > Platform Tools > User Interface > Translation Workbench > Translate

  • Select the Language that you want to localize to
  • Select the Setup Component as Picklist Value
  • Select Object as Recipient
  • In the Master Picklist table, expand the Recipient Role folder
  • Double-click the column space next to the English status to open the text field where the translation can be entered, and enter the appropriate localized value 

2. Click Save when done

translate_recipientroles

The Document field of the Agreement object contains a hyperlink to the agreement. There are two changes to this field in the v20 release:

  • The hyperlink text no longer has the status of the agreement appended to it. 

Prior to v20, hyperlink text contained the agreement name and the status “- signed” or “- approved” appended to the end:

 

document_link_update-statusintext

Version 20 removes the appended status, leaving just the agreement name:

document_link_update-nostatusintext

 

  • Prior to v20, the Document field contained the hyperlink only when the agreement transaction was completed successfully. 

In the v20 package, the Document field always contains the latest PDF version of the Agreement:

real-time_pdf_versions

The Help Text for the Chatter event Post when Agreement Sent can be updated to remain consistent with the new recipient roles.

  1. Navigate to Setup > Platform Tools > Custom Code > Custom Settings
  2. Click the label Adobe Sign Chatter Settings
  3. Click the Edit link next to Post when Agreement Sent
edit_chatter_setting

4. Update the Help Text to read: Post Chatter update when agreement is sent for signature/approval/acceptance/ form-filling/delivery.

5. Click Save

chatter_help_tectchange


Package version 19.x

Note:

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:

  • All features can be updated using a Permission Set  to grant access to the Adobe Sign objects
  • Some features that must access Salesforce objects may require enablement of specific objects and/or fields

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.

  • Navigate to: Setup > Administration > Users > Profile > {Profile name} 
  • Scroll down to the Custom Field-Level Security section and click the View action for the Agreement object
  • Provide Read and Edit access to relevant fields
enable_agreementfieldlevelsecurity

There is one deprecated custom settings in version 19: 

  • Enable Send Written Signature To Fax – Adobe Sign no longer supports sending an agreement to a phone number. Written signatures instead follow the same process as electronic signature until the first signer has to apply their signature. Then they download, sign, scan and upload that file back to Adobe Sign. 

>> More details on the Written Signature

There is one new tab in v19: Agreement Types

  • A new custom object called Agreement Type (Agreement_Type__c) has been introduced to define an agreement type. It has one standard Name field, but additional fields can be added later to define your own custom fields. An object is used instead of a simple text field because this allows a unique record to define a type, which is more flexible and extensible. It also separates the type from the agreement template and the agreement, so the agreement template can change without being tied to the type and multiple templates can set the same type.
  • A new parent lookup field called Agreement Type (Agreement_Type__c) has been added to the Agreement Template object, which points to the Agreement Type object. The field will appear in the Agreement Template Detail section on the agreement template page.
  • A new parent lookup field called Agreement Type (Agreement_Type__c) has been added to the Agreement object, which points to the Agreement Type object. The field will not appear on the Agreement editor page.

 

Add the parent lookup field called Agreement Type (Agreement_Type__c) to the Agreement Template Page Layout:

  • Navigate to Setup > Platform Tools > Objects and Fields > Object Manager > Agreement Template > Page Layout > Agreement Template Layout
  • Select the Fields option
  • Click the Agreement Type field and drag it onto the page layout
  • Click Save
add_the_agreementtypefieldtothepagelayout

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:

  • Fetch Missing Document Keys – Clicking this link will perform a batch action for fetching missing document keys for existing agreements
  • Update Legacy Document Keys - Clicking this link will flush out the existing legacy document keys and fetch the new document keys for all the agreements existing in the org. 

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.

Note:

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.

  • This is best achieved by adding the Adobe Sign Admin permission set to the user
  • The user's profile must have the View Setup and Configuration permission enabled

 

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:

  • The Adobe Sign User permission set should be applied to the user
  • The Salesforce Contact object must have Read enabled
    • The Email field on the Contact object must have Read enabled

 

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

  • The Adobe Sign Admin permission set to be added
  • Access to all fields for the specified Master Object in Salesforce

 

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:

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

  • The Adobe Sign User permission set
  • The Salesforce Opportunity object must have Read enabled
    • The Name field on the Opportunity object must have Read enabled
  • The Salesforce Account object must have Read enabled
    • The Name field on the Account object must have Read enabled
  • The Salesforce Contract object must have Read enabled
    • The Name field on the Contract object must have Read enabled
    • The Contract Number field on the Contract object must have Read enabled
  • The Salesforce Contact object must have Read enabled
    • The Name field on the Contact object must have Read enabled
    • The Email field on the Contact object must have Read enabled
  • The Salesforce Lead object must have Read enabled
    • The Name field on the Lead object must have Read enabled
    • The Email field on the Lead object must have Read enabled
  • The Salesforce Document object must have Read enabled
    • The Name field on the Document object must have Read enabled
    • The Type field on the Document object must have Read enabled
    • The Content Type field on the Document object must have Read enabled
    • The Body field on the Document object must have Read enabled

 

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    
  Email Read    
         
Lead   Read Salesforce -Standard  
  Name Read    
  Email 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:

  • The Adobe Sign User permission set
  • The system permission Insert System Field Values for Chatter Feeds enabled 
  • The Salesforce Opportunity object must have Read enabled
    • The Name field on the Opportunity object must have Read enabled
  • The Salesforce Account object must have Read enabled
    • The Name field on the Account object must have Read enabled
  • The Salesforce Contact object must have Read enabled
    • The Name field on the Contact object must have Read enabled
    • The Email field on the Contact object must have Read enabled
  • The Salesforce Lead object must have Read enabled
    • The Name field on the Lead object must have Read enabled
    • The Email field on the Lead object must have Read enabled
  • The Salesforce Document object must have Read enabled
    • The Name field on the Document object must have Read enabled
    • The Type field on the Document object must have Read enabled
    • The Content Type field on the Document object must have Read enabled
    • The Body field on the Document object must have Read enabled
  • The Salesforce Quote object must have Read enabled

 

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    
  Email Read    
         
Lead   Read Salesforce -Standard  
  Name Read    
  Email 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:

  • The Adobe Sign Admin permission set
  • The Salesforce Contact object must have Read enabled
  • The Salesforce Lead object must have Read enabled
  • The Salesforce Document object must have Read enabled
    • The URL field on the Document object must have Read enabled

 

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:

  • The Adobe Sign Admin permission set
  • The Salesforce Contact object must have Read enabled
    • The Mobile Phone field on the Contact object must have Read enabled
  • The Salesforce Lead object must have Read enabled
    • The Mobile Phone field on the Lead object must have Read enabled
  • The Salesforce Opportunity object must have Read enabled
  • The Salesforce Account object must have Read enabled
  • The Salesforce Group object must have Read enabled
  • The Salesforce Quote object must have Read enabled

 

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:

  • The Adobe Sign User permission set
  • The Salesforce Lead object must have Read enabled
    • The Company field on the Lead object must have Read enabled
  • The Salesforce Event object must have Create enabled
    • All fields on the Event object must have Modify enabled

 

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:

  • The Adobe Sign Admin permission set
  • Any object/field that the merge maps accesses requires Read and Modify enabled

 

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:

  • The Adobe Sign User permission set
  • The Salesforce Account object must have Read enabled
    • The Name field on the Account object must have Read enabled
  • The Salesforce Opportunity object must have Read enabled
    • The Name field on the Opportunity object must have Read enabled
  • Any object/field that the merge maps accesses requires Read and Modify enabled

 

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:

  • The Adobe Sign Admin permission set
  • Any object/field that the merge maps accesses requires Read and Modify enabled

 

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:

  • The Adobe Sign Integration User permission set
  • Any object/field that the data maps accesses requires Read and Modify enabled
  • The Salesforce Attachment object requires access based on the parent record

 

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:

  • The Adobe Sign Integration User permission set
  • The Salesforce system permission Insert System Field Values for Chatter Feeds enabled

 

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:

  • The Adobe Sign Integration User permission set
  • The Salesforce Account object must have Read and Create enabled
  • The Salesforce Contract object must have Read and Create enabled
  • The Salesforce Opportunity object must have Read and Create enabled
  • The Salesforce Contact object must have Read and Create enabled
    • The Name field on the Contact object must have Read and Modify enabled
    • The Email field on the Contact object must have Read and Modify enabled
    • The Account field on the Contact object must have Read and Modify enabled
  • The Salesforce Lead object must have Read and Create enabled
    • The Name field on the Lead object must have Read and Modify enabled
    • The Email field on the Lead object must have Read and Modify enabled
    • The Company field on the Lead object must have Read and Modify enabled

 

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  
  Email Read, Modify    
  Name Read, Modify    
  Company Read, Modify    
         
Contact   Read, Create Salesforce -Standard  
  Email 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:

  • The Adobe Sign Integration User permission set added
  • The Callback User profile must enable the Administrative Permission for Modify Metadata

Additionally, the Site profile must be edited to:

  • Add the LargeFileDownloadService class
  • Remove the AgreementAttaqchmentService class

 

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