The Adobe Sign for Salesforce release notes are ordered below with the current release at the top, and rolling back in time as you scroll down the page.

אזהרה:

It is strongly recommended that you install or upgrade into your sandbox environment first, to verify that all aspects of the application work as you expect, and do not conflict with any other customizations, settings, or applications.

Customers that are upgrading from a version prior to v21.5.11 must upgrade to the v21.5.11 package first and then upgrade to the newest package.

Adobe Sign for Salesforce v23.x

Rebranding of the Adobe Sign icon

The Adobe Sign icon used throughout the application has been updated to the new branding.


Update your Salesforce org to use Files as the default storage object for documents

Version 23 of the Adobe Sign for Salesforce package shifts the default object type for stored documents from the legacy Attachments object to the relatively new Files object.

This update reinforces the Salesforce Lightning experience, which only supports Files (the Salesforce classic experience does not support Files) and aligns with many third-party solutions commonly paired with Adobe Sign who are upgrading in a like manner.

Impacted documents include:

  • Agreement Documents
  • Data Mapping
  • Agreement Templates
  • Agreement Updates
  • Large File Send
  • Custom Settings
  • Push Agreements

No action is required from the Admin updating to this version at this time, as the existing storage object is grandfathered in for the organization, ensuring that operations can continue with no disruption.

However, admins are encouraged to investigate how they can migrate their org to use Files before Attachments are deprecated.

הערה:

  • UPDATING from an Adobe Sign for Salesforce version prior to 23.0 will honor the existing storage object after the update (Attachments for most customers). No action is required to continue operating as normal
  • NEW installations of the Adobe Sign for Salesforce package will have Files set as the default storage object, but can manually switch to Attachments
  • Controls are available to the Salesforce admin to switch the storage object between Files and Attachments


New custom setting to control the document storage type

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:

  • {empty} - If the value is empty, the default behavior is based on the install version of the package
    • Version 23.0+ will default to Files as the default storage type
    • Versions prior to 23.0 will default to Attachments as the default storage type
  • Files - Strongly defines Files as the default storage object for Adobe Sign document
  • Attachments - Strongly defines Attachments as the default storage object for Adobe Sign document
Doc Type Setting


Analytics Settings

An optional Analytics setting has been added to allow Adobe Sign to collect usage data to improve the product. This data is used only for development and not for marketing purposes.

This setting can be controlled from the Adobe Sign Admin tab by clicking the Analytics Settings link in the right rail:

Analytics Settings

The analytics setting is enabled by default for most new customer installations

  • New customer installations in Canada and the European Union will have analytics disabled by default
  • Upgrading customers will have the setting disabled by default to match their current experience. Admins can enable the setting at will on the Adobe Sign Admin tab

When enabled, a record is automatically added to your CSP Trusted Sites for the adobe.io site name:

CSP Trusted Sites with Adobe.io added

Disabling the analytics settings automatically removes the adobe.io record from the CSP Trusted Sites page.


Resolved Issues

Issue Number Corrected Issue Description
15687 Fixed an issue where a library template removed from Adobe Sign manage page could still be accessed by the Salesforce Template
18890 Fixed a spelling inconsistency for the status of Canceled agreements
20380 Fixed a formatting error for dates
20420 Improved the menu placement for the customized tool bar so it wouldn't open off-screen
20436 Fixed an issue with the cursor not showing related links as clickable on agreements
20631 Fixed an issue where image files attached to an agreement would open in a browser tab instead of downloading
20638 Improved the cancelation reason field to allow more than 255 characters
20678 Fixed an issue where a Salesforce custom theme would be lost on the Adobe Sign tabs
20972/21359 Fixed an issue where Adobe Sign library templates would not be accessible if the access token expired
21126 Fixed an issue where the Email recipient type would not be removed from the recipient options if disabled in the custom settings
21426 Corrected an issue that could block access to Adobe Sign library templates if the user's library has a very large library list (1000+)
21512 Improved management of file extensions in the agreement title

הערה:

The Adobe Sign for Salesforce package is supported for two major versions beyond the current major version.

  • The current version is 23.0
  • Support is provided for version 21+

Customers running unsupported versions have elevated security risk and are strongly encouraged to upgrade to the new package to ensure the continuation of support.

Contact your success manager if you have any questions or need assistance in upgrading your org.


Previous Releases

Salesforce agreement templates now have the option to hook into Adobe Sign's custom workflows, allowing you to map complex signature processes in Adobe Sign, and then import that structure into a Salesforce Tempalte:

Workflows in Salesforce Templates

Resolved Issues

Adobe Sign for Salesforce 21.5.11 is a required installation point for organizations that want to continue using Adobe Sign under the new security frameworks being put into place by Salesforce and Adobe Sign (ie: Upgraded APIs).

The 21.5.11 package dereferences two pages (MyEchoSign.page and AboutEchoSign.page) clearing the way for their ultimate removal.

No changes are made in feature capability or user functionality for this package, though some issues have been resolved:


Resolved Issues

Issue Number Corrected Issue Description
19681 Improved the package to remove Chatter requirements that were blocking installs if Chatter was disabled
20013 Corrected a problem where Agreement status updates were not working for agreements that used Adobe Sign Authentication as the verification method
20045 Fixed an issue where custom settings for lightning UI configurations were only working for System Admins


Supporting Salesforce "Files" as the storage object in File Mapping

The Winter 2019 Adobe sign for Salesforce (v21) release updates three core elements to the package for new deployments, while maintaining backwards compatibility for existing customers:

Additionally, adjustments have been made to bring the Salesforce experience into better alignment with the Web experience.  To this end, 

When mapping file storage through the Data Mapping process, a new check box has been added to explicitly force the storage as an Attachment.

If this option is not selected, the content is stored as a File.

add_file_mappingv21

Improved Agreement update process

v21 changes the update process for Agreements in Salesforce. Instead of pushing updates to Salesforce, Adobe Sign will notify Salesforce that updates are available, and then Salesforce can pull them in. This helps alleviate issues where Salesforce is offline at the time Adobe Sign pushed the update.

Additionally, agreements now update asynchronously, where all previous version were synchronous.


New Custom Setting Section: Adobe Sign Agreement Update Settings

custom_settings_-agreementupdatesettings

To support the new update process, a new section has been added to the Custom Settings section in Salesforce: Adobe Sign Agreement Update Settings

Five previously existing settings have been relocated to this category from the Adobe Sign Settings section:

Adobe Sign Settings

Adobe Sign Agreement Update Settings

Add Audit PDF to Attachment List

Add Audit Report

Add Signed PDF Link for Pushed Agreement

Add Signed PDF URL

Add Signed PDF for Pushed Agreements

Add Signed PDF

Add Signed PDF as Separate Attachments

Add Signed PDF as Separate Attachments

Add Supporting Files to Attachment List

Add Supporting Files

 

Three new settings are being added:

  • Show Images – When enabled, images of the agreement PDF are displayed on the agreement page
  • Update Agreement Events – When enabled, Salesforce will update the events for agreements when notified by Adobe Sign
  • Update Agreement Status – When enabled, Salesforce will actively update agreement statuses when notified by Adobe Sign

Manually updating an agreement now updates all elements of an agreement (recipients, events, Images, etc) instead of just the status.

old image


Renamed Custom Setting Section: Adobe Sign Push Mapping Settings is now Adobe Sign Agreement Recipient Settings

The Push Map Settings have been re-worked to apply broadly to all Agreements, so the custom settings section that governed these settings has been renamed to better reflect that they apply to the recipients of all agreements, and not just Push agreements.

Additionally, five new settings have been added to expand the ability to update the recipients related to agreements:

  • Create Missing Recipients (enabled by default) - Enable this setting to create missing recipients
    • New recipients get created in the case of Agreement Push Mapping, Replace Signer, or Delegate Signer workflow
  • Enable Participation Sets - Enable this setting to create and update Participation Sets
  • Update Delegated Recipients (enabled by default) - Enable this setting to mark the recipients as Delegated when they are delegated by the Signer or Sender
    • These recipients are hidden from the Agreement View page
  • Update Recipients (enabled by default) - Enable this setting to update existing recipients attributes such as Status
  • Update Replaced Recipients (enabled by default) - Enable this setting to mark the recipients as Replaced when they are replaced by the Sender from the Manage page
    • These recipients are hidden from the Agreement View page
adobe_sign_agreementrecipientsettings


Improved Manual Update

The manual update process has been improved to update the entire suite of Agreement objects, including all links, images, events, status, and data mappings.

update_agreementv21


Updated Event descriptions

The event descriptions for agreements are being updated with three changes:

  • The generic term “Document” is being used instead of the agreement’s name
  • The email address of the user is being inserted after the name value
  • The IP address is being included
agreement_events


New authentication method: Government ID

The new Government ID authentication method has been added as a custom option in the Adobe Sign Settings section.

Government ID is a premium identity authentication method that must be enabled by your success manager before it can be deployed.

govt_id_selectionv21


Drag and Drop support for adding files
(Lightning only)

The Lightning experinece now allows you at add docuemts to your new Agreements by dragging them from your local system and dropping them in the Files area.

Documents added via drag and drop are uploaded to your personal Files in Salesforce.


New Agreement Template format

The Agreement Template interface has been updated to provide improved clarity of the template content in five tabs.

drag_and_drop_v21
template_requirements


Simple Sign

Simple Sign is an easy out of the box component to allow community portal users to sign self service agreements. Add this component to any Salesforce Community Cloud portal (customer, partner, employee, etc.), or embed the component into other Lightning components.


Adobe Sign for Salesforce CPQ:
"Generate Adobe Sign" button

The Adobe Sign CPQ component has been improved to streamline the process of attaching the Quote PDF to the Agreement in one button click using the Generate Adobe Sign button or LEX component.

Click the Generate button in the LX component

Resolved Issues

Overview

The Summer 2018 Salesforce (v20) release expands the functionality within the Lightning experience, and enables several new high-demand features that customers have been asking for.

הערה:

In version 20 of Adobe Sign for Salesforce we further aligned with the Lightning experience to optimize overall performance.

Part of the optimization is moving the agreement list to a Lightning component. Previous versions used a Visualforce page with an embedded “Lightning Out” component.  A result of this move is when launching a new agreement from a related list on a standard object  (Contact, Opportunity, Account, Contract, etc.) it will not automatically associate the agreement to the object. This is due to Salesforce lack of support for the "Ikid" parameter being passed directly into a Lightning component.

This limitation is only observed when using the Lightning page layouts. Using the Advanced page layout continues to enable this functionality.

Changing page layouts is described here.

 

Support for the Salesforce Process Builder

Actions have been added to support the Salesforce Process Builder. 

Admins can create processes that can trigger Agreement creation from a template, as well as Send, Remind, Update, Cancel and Delete actions.

process_builder

 

Expanded Roles for recipients

Three new roles, with the accompanying delegator roles for each, have been added!  Now you can create signature flows that include Acceptor, Form Filler, and Certified Recipients, as types of participants.

expanded_recipients

 

Improved Sandbox support

On 3/16/2019, Salesforce will automatically enable a critical update that will strip the URL of the shard identification.

Prior to v20, the URL was used to parse out the shard information, and instruct Adobe Sign as to the nature of the SFDC instance that was attempting to communicate (Production or Sandbox).

After 3/16/2019, customers on v19 or older will need to contact Support to flag their Sandbox environments, allowing the OAuth process to connect.

Customers that have v20+ installed will gracefully navigate the OAuth process, without having to involve Adobe Sign support.

remove_instance_fromurl

 

Recipients related to each event they trigger

The Agreement Event object now relates the events with the recipient that triggered the event, allowing for a detailed understanding of the step by step signature process as it relates to the recipients.

agreement_events-recipient

 

Recipient IP address field added

The Agreement Event object has had a new field added: Acting User IP Address

This new field imports the IP address for any event logged against the agreement, and relates it to the user that triggered the event.

Reports can be generated to expose the IP information

agreement_event_-ipaddress

 

Fetch and Update Legacy Document Keys

Accounts that are still using Adobe Sign for Salesforce v13 or older can now upgrade to a modern version of the package, and update the respective document keys for their existing agreements.

fetch_missing_documentkeys

 

v20.8 (Incremental Patch)

Field API Names added to the select list for Data/Merge Mapping

A new setting has been added to expose the API name of a field when defining data or merge mapping.

api_name_in_mapping

To enable this feature:

  1. Navigate to Setup > Platform Tools > Custom Code > Custom Settings
    • This loads the Custom Settings page
  2. Click the label Adobe Sign Settings
    • The Adobe Sign Settings page will load
3_adobe_sign_settings

3. Click the Manage button

4_adobe_sign_settingmanage

 4. Click New (or Edit, if you have configured settings before)

• The Adobe Sign Settings page will load

5_adobe_sign_settings-edit

5. Use your “Find” function (cmd/ctrl + f) to locate Show File API Name

show_fields_api_name

6. Click Save

 

Resolved Issues

Issue Number Corrected Issue Description
14931 Error Message when sending an agreement with the "basic" page layout
15012 Recipient not auto-populated in the EchoSign Agreement Advanced VF page
14578 File mapping fails unless data mapping has an entry to map to an additional object
13169 Auto Provisioning error
12457 Recipient is not retained if the recipient order changes
14541 Error prompted if more than 11 recipients are defined

 

v20.9 (Security Patch)

Customers that are upgrading and have large files or push agreements configured should carefully review the upgrade process before installing the new package:

Upgrade process for large file service

Upgrade process for push agreements

 

Callback User to replace the Callback Site Profile

Due to security concerns around granting broad object access to a Salesforce callback site, v20.9 introduces a new user-based authentication process which helps ensure superior control over access to agreement objects.

Callback sites have traditionally been used for customers that enable large file service and push agreements. All customers that have one or both of these features enabled are strongly advised to upgrade to v20.9, enable the new Callback User feature, and remove all permissions from the Site user.

The Callback User is enabled through a new control on the Adobe Sign Admin page, just under the Adobe Account link.

calback_user_on_adminpage

 

v20.11 (Incremental Patch)

Issue 621/14678 overcomes a previous limitation of the Lightning environment that prevented the automatic relationship between an agreement and the parent SFDC object that launched the agreement.

 

Resolved Issues

Issue Number Corrected Issue Description
621/14678 Improved the Lightning experience in terms of automatically relating the agreement to the parent SFDC object
15441 Improved the ability to query encrypted fields in Salesforce for lookup fields
15686 Corrected a problem with the Edge browser when retrieving a signing URL on the Agreement page when using Hosted signing

The Winter 2018 Salesforce (v19) release expands the functionality within the Lightning experience, and enables several new high-demand features that customers have been asking for.

 

Batch actions from the Lightning pages

The ability to Create, Send, Remind, Cancel, Delete, and Update agreements in bulk is now available to the Lightning interface, with an improved process that summarizes the action being taken, before the final execution of the action.

19-1_-_batch_enabledinlightning

 

New Permission Sets to speed user enablement

Admins that install the Adobe Sign for Salesforce application, but can't opt for the "All Users" option, were faced with a significant manual process to make objects and fields accessible to individual users.

But no more!  With the addition of three new permission sets, Admins can quickly apply all of the permissions to individual users without having to step through each field for each object.

The three options are:

  • Adobe Sign User - Minimum required permissions for an Adobe Sign for Salesforce sender user. Includes limited access to the required components included in the managed package: objects, fields, tab, classes and pages.
  • Adobe Sign Admin - Minimum required permissions for an Adobe Sign for Salesforce administrator user. Includes full access to all of the components included in the managed package: objects, fields, tab, classes and pages.
  • Adobe Sign Integration User - All required permissions for an Adobe Sign for Salesforce integration user. Includes all admin access as well as access to all org data.
19-2_-_permissionsets

 

Superior Written Signature workflow

Get the accuracy and auditability of electronic signing with handwritten signatures. Let signers fill, print, sign, scan, and return documents without a fax machine. Everything is captured and managed electronically, so you’ll get legible text plus signer verification data in the audit trail.

The Written Signature workflow replaces the antiquated Fax process, and produces a much more consistent and professional result.  Check here for more details.

19-3_-_written_signatureflow

 

Email components for Outlook and Gmail

The Adobe Sign for Salesforce Email component will function on the Microsoft Outlook Web App (OWA), Outlook 2016, Outlook for Mac 2016, or Outlook 2013. This same component package also works for the Gmail for Work integration.

The email component is a separate installation, but only takes a few minutes to install and configure.

Click here for installation details.

19-4_-_email_component

 

Improved reflowable Send page for multiple screen sizes

Smaller screen devices are becoming more and more common for regular business actions, and left-right scrolling is painful when you want to get something done efficiently. To help those users that love their tablets, the Send page has been refactored to be flowable into a much wider range of screen widths, without losing any functionality.

19-5_-_reflowablesendpage

 

Integration component for Salesforce CPQ

Speed your delivery of CPQ quotes directly from Salesforce to your customer's email box, ready to sign using the Adobe Sign CPQ connector component.

19-6_-_cpq_send_button

 

Salesforce Community Cloud Portal (Self-Signing) support

Community portals can now include an Adobe Sign component that provides agreements ready to be signed by portal users.

Salesforce Admins have the ability to publish agreements, establish a deadline date, and define a renewal cycle as needed.

Users can access the community site, generate a new agreement, and sign it right from the portal.

19-7_-_communityportal

 

v19.4 - Released January 2018

Update Legacy Document keys if upgrading from a version older than v14 

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.

הערה:

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.


Resolved Issues

Issue ID

Description

8014 Improved functionality with Conga in terms of Cancel and Remind actions
8979 Resolved a condition that caused a "Maximum view state size limit exceeded" error
9709 Corrected a problem where the AgreementEventType is missing the WRITTEN_SIGNED event type
9832
Resolved a Permission Denied error for Salesforce platform users
9927 Corrected a problem where files were attempting to attach to agreements without the extension of the file

9934

Improved handling of geolocation fields
10367 Provided a docKey solution for customers that are updating from package versions 13 and older

 

v19.5 - Released February 2018

Localization for the Norwegian language has been added.

הערה:

If you are using the Norwegian localization, and have updated to Adobe Sign for Salesforce 19.0-19.4, you will need to update the 19.5 translation tables manually.

 

When upgrading from v19.0 – v19.4 to 19.5

Enable Translations (If you already use a localized version of Salesforce, these steps will be done)

  • Log in to Salesforce as an Admin
  • Navigate to Setup > Platform Tools > User Interface > Translation Workbench > Translate
  • Click Enable

 

Enable Norwegian as a language option

  • Log in to Salesforce as an Admin
  • Navigate to: Setup > Platform Tools > User Interface > Translation Workbench > Translate Settings
  • In the Language pick-list, select Norwegian
  • Click Save
select_language

Update Translations

  • Navigate to: Setup > Platform Tools > User Interface > Translation Workbench > Translate
    • Select the Language as Norwegian
    • Select the Setup Component as Picklist Value
    • Select Object as Agreement

 

  • In the Master Picklist table, expand the Agreement Status folder
  • Double-click the column space next to the English status to open the text field where the translation can be entered. Enter the values per the table below:      

Master Picklist Value Label

Picklist Value Label Translation

Approved    

Godkjent

Cancelled / Declined                

Avbrutt / avslått

Created

Opprettet

Draft

Kladd

Expired

Utgått

Out for Approval                        

Ute til godkjenning

Out for Signature                        

Ute til signering

Pre-Send                                        

Før sending

Send in Progress                        

Sending pågår

Signed      

Signert

Waiting for Counter-Approval   

Venter på kontragodkjenning

Waiting for Counter-Signature        

Venter på kontrasignatur

edit_the_translationtables

 

o   Click Save

 

  • In the Master Picklist table, expand the Language folder and enter the below values:

Master Picklist Value Label

Picklist Value Label Translation

Chinese (Mainland China)

Kinesisk (Kina)

Chinese (Taiwan region)

Kinesisk (Taiwan region)

Czech (Czech Republic)

Tsjekkisk (Tsjekkia)

Danish (Denmark)

Dansk (Danmark)

Dutch (Netherlands)

Nederlandsk (Nederland)

English (United Kingdom)

Engelsk (Storbritannia)

English (United States)

Engelsk (USA)

Finnish (Finland)

Finsk (Finland)

French (France)

Fransk (Frankrike)

German (Germany)

Tysk (Tyskland)

Icelandic (Iceland)

Islandsk (Island)

Indonesian (Indonesia)

Indonesisk (Indonesia)

Italian (Italy)

Italiensk (Italia)

Japanese (Japan)

Japansk (Japan)

Korean (South Korea)

Koreansk (Sør-Korea)

Malay (Malaysia)

Malayisk (Malaysia)

Norwegian (Norway)

Norsk (Norge)

Polish (Poland)

Polsk (Polen)

Portuguese (Brazil)

Portugisisk (Brasil)

Portuguese (Portugal)

Portugisisk (Portugal)

Russian (Russia)

Russisk (Russland)

Spanish (Spain)

Spansk (Spania)

Swedish (Sweden)

Svensk (Sverige)

Thai (Thailand)

Thai (Thailand)

Turkish (Turkey)

Tyrkisk (Tyrkia)

Vietnamese (Vietnam)

Vietnamesisk (Vietnam)

edit_languages

o   Click Save

 

  • Change the Object pick-list to Form Field Mapping Entry
  • Expand the Source Type folder
  • In the Master Picklist table, expand the Language folder and enter the below values:

Master Picklist Value Label

Picklist Value Label Translation

Constant Konstant
Salesforce Object Field Salesforce-objektfelt

 

edit_source_type

 

o   Click Save

 

 


Resolved Issues

Issue ID

Description

6227 Corrected an incorrect Approver icon when replacing the recipient in some workflows
6816 Fixed a problem where replacing a signer using the EchoSign Advanced VF page threw a null 404 error
6956 Fixed a problem with importing an excessive number of fields, resulting in a Maximum view state size limit error
10426 Corrected an error where the Lead object required all fields to have access explicitly allowed to permit data mapping
10676 Improved Date formula to always show the users local timezone offset 
10979 Corrected an issue where the Manage Agreement tab was requiring access to View Setup under System permissions