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.

Adobe Sign for Salesforce v20.9 (Security Patch)

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 ensures 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 process, and disable the site callback configuration.

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

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

Adobe Sign for Salesforce 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

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.

Opomba:

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

Agreement Events object expanded

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


Previous Releases

Opomba:

Support for the Adobe Sign for Salesforce integration v16 and v17 will be ending on  November 15, 2018

Product updates, security updates and technical support for Adobe Sign for Salesforce v16 and v17 is ending November 15, 2018.

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

Version 19.x

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.

Opomba:

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.

Opomba:

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 (China)

Kinesisk (Kina)

Chinese (Taiwan)

Kinesisk (Taiwan)

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

Version 18

The Spring 2016 Salesforce (v18) release introduces the Lightning experience, and the newest update to the Adobe Sign for Salesforce package is "Lightning Ready".  Enabling the Lightning experience is completely up to you, and you can switch back to Salesforce Classic at any time.

In Lightning, the navigation menu on the left provides quick access to your Salesforce objects. You can use the App Launcher to access the Adobe Sign integration package.

See Find Your Stuff in Lightning Experience in the Salesforce Help for more information.

 

Lightning Experience

Enabling the Lightning Experience is easy:

  1. From Setup
  2. Click Lightning Experience in the left navigation menu to change the default settings before you switch the view. 
  3. Select Switch to Lightning Experience from your profile menu, to change to the Lightning view.
SFDC settings to switch to Lightening

See Enable Lightning Experience in the Salesforce Help for more information. 

 

 

Switching back to Salesforce Classic

If you are working in the Lightning Experience, switching back to Salesforce Classic is also easy. Simply click your profile picture in the upper right corner, and select Switch to Salesforce Classic from the menu.

Click your profile picture in the upper right corner, and select Switch to Salesforce Classic

 

Accessing the Adobe Sign integration application

Once Lightning is enabled, you can click the App Launcher to display the available apps, then click Adobe Sign.

See Opening a Different App in Lightning Experience in the Salesforce Help for more information.

The App Launcher

The menu for Adobe Sign displays. From this menu you can access all the familiar Adobe Sign pages and features. Note that the Manage Agreements and Adobe Sign Admin pages are currently only available in Salesforce Classic.

The menu for Adobe Sign display

In the Lightning Experience, the Adobe Sign pages have a new, cleaner look.

The Adobe Sign Lightning Experience

 

Enhanced Agreement page

The enhanced Agreements page can be used in both Salesforce Classic and Lightning. Before using this new Agreement page, you must enable the enhanced Agreement page style.

 

Enhanced Agreement Layout experience:

The enhanced Agreement page layout provides senders with all of the functionality of the previous layout plus additional features. The enhanced agreement page is available in both Salesforce Classic and Lightning.

To get to the enhanced agreement page, choose ‘Agreements’from the ITEMS menu on the lightning page or the left navigation menu on the Classic page.

The enhanced Agreement page layout

1. Recipients are numbered now as shown above. You can use recipient numbering to reorder recipients to create sequential routings and to create hybrid and parallel routings.

2. Sender can now quickly add themselves as a recipient anywhere in the routing, not just first or last, using Add Me and numbering.

3. Groups can be specified as recipients.

4. Private message can be added. Clicking the message bubble icon displays the Add a Private Message dialog. The bubble will appear slightly gray if you have a message.

5. Identity Verification

Define the details of the transaction

6. Select a related Contract

Enter the email addresses of the recipient

7. Select files from your document library or online storage accounts—You can now click Add Files to access the Select Files dialog and all the file sources that are enabled.

 

New recipient role: Delegator

In addition to Approver and Signer, admins and senders can now add Delegator to the recipient workflows. Delegators receive the agreement, but are not expected to sign.  Instead they will route the agreement to the approver or signer they choose. 

Great for situations where the signer/approver isn’t known until the signature process is underway, these two new roles will give you the flexibility to start gathering signatures immediately, and identify the proper downstream recipients at a later time.

The Delegator Roles in Salesforce

 

Private messages

You can create unique messages for each recipient in the signing process before sending a document for signature or approval. To add a message, click the Add a private message icon. 

Create unique messages for each recipient

Recipients can easily read the private message during the signing experience. When someone has left a message for one of the recipients, the color of the message bubble will be light gray.

 

Hybrid routing

In addition to being able to create sequential and parallel recipient routing, you can use the new recipient ordering feature to create hybrid routing that includes parallel and sequential components using the new Send page. You can specify which participants need to sign at the same time (in parallel) and which need to sign in sequential order by dragging and dropping or using numbering order to define the signing sequence. 

 

Creating hybrid routing:

1. Enter the email addresses of the recipients.

Enter the email addresses of the recipients

2. To designate two recipients to sign second—in this example severtonea@gmail.com and kmaggerstein@gmail.com—enter a “2” in the routing order field for both. 

Enter a “2” in the routing order field for bot

When you save the agreement, the email addresses for severtonea@gmail.com and kmaggerstein@gmail.com display as parallel recipients in the second position. Note that the order of subsequent recipients will update to reflect the new routing order. 

The order of subsequent recipients will update to reflect the new routing order.

 

Recipient Group

You can speed up the signing processes by giving multiple team members the authority to sign on behalf of the entire group. Add a recipient group first, and then add multiple recipients to the group. Any one of the recipients listed can sign on behalf of the entire group. Recipient groups integrate with Salesforce groups.

 Add a recipient group

 

Modifying Agreements

You can make on-the-fly document corrections using the new modify agreements feature instead of canceling agreements and starting over. You can use Modify Agreements to add, delete, replace (delete then add), and reorder documents. You can also use the authoring environment to modify fields.

The modify agreements feature is available only on the new Send page. However, it can be used to modify agreements that were initiated before the November 2015 release as long as the transaction meets the “modifiable” criteria. If a document is modifiable, a Modify Agreement link displays on the Manage Agreements page when the document is selected. A modifiable agreement is one that meets the following criteria:

  • The agreement has not been signed, approved, or delegated to a signer or approver by the delegator to whom it was assigned.
  • The agreement does not include a digital signature or fax signature.
  • The agreement has not been initiated from a workflow.

 

 

Administration for modify agreements

The modify agreements feature must be turned on globally for your organization, and then the last check box, Allow senders to modify agreements after they have been sent for signature, will appear in the Account | Send Settings options for each user.

Account administrators and group administrators can specify whether you can modify documents that you have sent for signatures by checking the “Allow senders to modify agreements that have been sent for signature” in the Attaching Documents section of the Send Settings parameters in your Account. 

Allow senders to modify agreements that have been sent for signature

 

Modifying an agreement

If the modify agreements setting is enabled for your organization or group, you can modify agreements that are in the Out for Signature or Out for Approval sections. (See Modify agreements for more information.)

1. Click the Manage Agreements tab.

2. Click to select a modifiable agreement from the Out for Signature or Out for Approval section, then click the agreement description in the upper-right corner.

Click the agreement description in the upper-right corner.

The Send page displays in limited editing mode and you cannot make changes in the Recipients or Message sections.

The Send page

In this Send page, you can add, delete, replace (delete then add), and reorder documents.

To add a document, do one of the following:

  • Click Add Files.
Click Add Files.
  • Or, drag-and-drop files from your computer to the Drag More Files Here area.
Drag-and-drop files from your computer to the Drag More Files Here area.
  • To delete a document, click the delete icon (X) to the right.
Click the delete icon (X) to the right.
  • To recorder documents, click the grab bar and drag the document to its new position.
Click the grab bar and drag the document to its new position

Depending on your Send settings, you may be able to use the Preview & Add Signature Fields option to add form fields to the document or documents in the modified agreement. 

Opomba:

When you modify an agreement, the form fields that were originally added by the sender to documents using the authoring environment are discarded. Form fields that were added to library documents when they were created and form fields added to documents with text tags are automatically reprocessed.

  • If you do not need to add form fields or do not have the Preview & Add Signature Fields option, then click Update to save your changes.
  • If you need to add form fields, enable the Preview & Add Signature Fields option if necessary, then click Update to open the authoring environment. When done in the authoring environment, click Update.

If the agreement has already been signed, when the sender clicks Update the sender gets a message indicating that the recipient has signed, approved, or delegated it.

The "Cannot Modify Agreement" message

If the Modify Agreements feature has not been turned on globally for your organization, there are still a few ways that you can make modifications after an agreement has been sent for signatures.

If you scroll down to the bottom of the agreement description, you will see three ways that you can modify an agreement.

Replace Signer and Upload Copy links in the transaction metadata.

The actions you can perform on an existing agreement include replacing a signer, uploading a signed copy, and adding an expiration date.

To replace the current signer, enter the new signer’s email address and the reason that you are replacing the original signer. For example, the original signer might be out-of-the-office during the time you need to have the documents signed. Click the Replace Signer button when you’re finished.

Replace Current Signer interface

To upload a signed copy, click the Replace Signer link in the agreement description. Type the email address of the new signer and a short message about the reason for replacing the original signer. Note that until the new signer adds their signature, the original signer can still sign the document.

Upload a Signed Document interface

To add an expiration date, click the Add link in the agreement description. Then click the calendar icon to select the expiration date. Select the Notify Current Recipients check box, if you want the recipients to get notified.

The Add Expiration Date window.

 

Signing, approving, or delegating a modified agreement

The recipient of a modified agreement is notified that the agreement has changed before they can sign, approve, or delegate it.

The "Agreement has been modified" notification message

The recipient can click OK to continue. The signing, approving, or delegating process proceeds as usual.

However, if the agreement has just been modified while the recipient is on the eSign page, the recipient is informed and must click Refresh to continue.

The "Agreement Has Been Modified" error panel

 

Viewing the history and audit trail of a modified agreement

Information on the events specific to the modification of a document (e.g., Agreement was modified, Agreement modification was acknowledged) can be viewed from the Manage Agreements page.

1. Click the Manage Agreements tab.

2. Single click an agreement to select it, then click the History tab on the right side of the page.

The Adobe Sign Manage tab

The event history for the agreement displays in the information panel. The transactions related to the modification by the sender and the recipient’s acknowledgement of the modification are noted.

The Adobe Sign Event List

3. Click the Audit Report link in the upper-right corner of the History frame to open a PDF Audit Report. The transactions related to the modification by the sender and the recipient’s acknowledgement of the modification are noted.

The Adobe Sign Audit Report

 

Multiple templates per Salesforce object

For customers who are using Salesforce Lightning, our v18 integration will enable admins to configure having more than one template available for any SFDC object.  This is new flexibility for users and admins, enabling them to select the correct template to start the send process. For example, now a user can send an MSA or Partner agreement from an SFDC Account object; both could be available if needed, through Lightning components.

Agreement Templates

 

Support for Salesforce Lightning Components 

For Administrators using the Lightning experience, there is a new and extremely easy way to add Adobe Sign into standard and custom SFDC pages. We offer three components to allow the Admins flexibility in building the pages as they see fit.: Adobe Sign Send and Agreement component and an Adobe Sign agreement list

 

Enhanced Adobe Sign Admin page

The Admin Page has a new cleaner look and all functionality is now on a single page. The tabs have been eliminated. Switch to the Lightning Experience to use the new Adobe Sign Admin Page.

Enhanced Adobe Sign Admin page

 

Improved Setup Wizard

Use the improved Setup Wizard to link your Adobe Sign account to your Salesforce account. The Setup Wizard is available from both the Classic and Lightning user interfaces. If your accounts are not already linked, you will see the Setup Wizard when you choose Adobe Sign from within Salesforce.  

 The improved Setup Wizard to link your Adobe Sign account to your Salesforce account

You will receive a Success! message when the wizard has linked your account to enable automatic status updates.

Success! message when the wizard has linked your account to enable automatic status updates.

Version 17

Dynamic product list creation

You can now automatically add your product lists to an agreement for signature. The merge mappings have been expanded to include all products tied to an opportunity. You can set which product attributes (like quantity and price) are included in your agreements as well as sort and filter the associated products.

17-1

 

Only I Sign

Your team can now sign any given document with "Only I Sign.” To do so, the sender can select the Sender Signs Only option on the Send Agreement page. The sender can then upload the document, drag and drop any required form fields onto it, and sign it. The document can be sent to the sender and any additional recipients specified. A record of this process is automatically generated in Salesforce, and a copy of the document is stored there as well. The Sender Signs Only option appears if the Enable Sender Signs Only setting is enabled, and it can be set to read-only using the Read Only Sender Signs Only setting.

17-2

 

Custom landing pages post-signing

You can now auto-redirect the signers of an agreement to a specified URL after they sign. For example, you can redirect signers to your company website or a survey page. Also specify how many seconds elapse before executing the redirect. The option to enter a redirect URL and specify the number of seconds is available on the Send Agreement page when the Enable Post Sign Options setting is enabled, and it can be set to read-only using the Read Only Post Sign Options setting.

17-3

 

Support for larger file sizes

Previously, additional setup steps were required to send transactions that included large files. Now you can send larger transactions as follows:

  • Manual Workflow—When clicking the Send for Signature button on the Agreements page, you can send a transaction that is up to 4MB, including multiple documents whose summed size is up to 4MB.
  • Background Actions—When sending a document using background actions, a single document up to 9MB or multiple documents whose summed size is up to 9MB can be sent.

Note:   Transactions larger than the noted sizes are supported with additional setup.

 

E-sign alerts within Salesforce

Your team members can now be alerted from within Salesforce when an agreement they’ve sent is about to expire. This option is controlled using the Create Sign Deadline Reminder Event and the Days Sign Deadline Reminder Event. The sender sees a pop- up alert in Salesforce and can then take action by contacting the signer and possibly extending the deadline.

 

Digital signatures

You can send an agreement out for a digital signature. Digital signatures are preferable to electronic signatures in certain regions (such as the EU) and industries (such as pharmaceutical). The digital signatures feature is currently in beta. Contact Adobe Support if you would like to use digital signatures before November 2015, when it will become generally available.

 

Simplified Setup Wizard

The new Setup Wizard makes it easier than ever to configure Salesforce after installation. Now you simply need to select the acknowledge option to allow Adobe Document Cloud eSign services to add a trusted remote site for your organization.

 

Admin control: Hide custom sidebar

If a custom sidebar has been added to the Agreement Editor page—accessed using the View Agreement button—you can now hide this sidebar by enabling the Hide Sidebar for Agreement Editor Page setting.

 

Admin Control: Auto-provisioning

In previous releases, users were automatically provisioned when they sent or managed agreements. Now you have the option to eliminate auto-provisioning using the Disable User Provisioning setting. Note that this setting does not control the auto- provisioning that occurs when Update Agreement is clicked from the Agreement list

 

Push releases

With v17, periodic patch updates can now be automatically pushed to your organization, eliminating the extra steps of downloading and installing a new package for dot releases.

 

Show Me How in-product tutorials

Using a new feature called “Show Me How,” team members can watch easy-to-follow tutorials covering the topics that typically lead to the most confusion.

 

Service Cloud/Console frames

Adobe Document Cloud eSign services can now be viewed as a frame within the Console view. This eliminates pop-up windows when using Service Cloud or Sales Cloud.

Version 16

Fully rebranded the application to Adobe Document Cloud eSign services for Salesforce

Enabled OAuth as the authentication method for the package

Version 15

Salesforce 1 Enabled

  • Fully native integration
  • Highest rated e-signature app
  • e-signatures you trust

 

Do it all on mobile – send and track agreements from Salesforce1

Send from anywhere

  • Send documents for signature from Android or iOS devices

Comply with business policies on the go

  • Automatically populate recipients, documents, and agreement options
  • Automatically merge Salesforce data into contracts and push signer data back

Manage agreements on the road

  • Get real-time notifications and status tracking

 

Close deals on-site with in-person signing from Salesforce1

  • Initiate contract for in-person signature
  • Hand device over to client to sign with finger or stylus
  • Close the deal and automatically store contract in Salesforce

 

 

Verify signer identity – get higher assurance with phone authentication

  • Get a streamlined, mobile friendly user experience for identity verification
  • Enable two-factor authentication
  • Automatically send a verification code via voice or SMS text message

 

 

Enable different levels of identity assurance for each signer

Verify identities of participants with two factor authentication

Select a different identity verification method for each recipient

  • Unique password
  • KBA
  • Social identity
  • (NEW)  Phone authentication

 

 

Easily change authentication method

  • Easily reset identity verification settings on documents out for signature
  • Use the Manage page to make changes and review other document protection settings

 

 

Send and manage in batch – save time and effort

Drive efficiency and create many documents in batches:

  • Partner agreements
  • NDAs
  • Consent forms
  • Renewal agreements

 

Send and manage agreements effortlessly

  • Create Agreement
  • Send Reminder
  • Cancel Agreement
  • Update Agreement Status
  • Delete Agreement
  • Change Owner

 

 

Deploy globally – enable e-signatures for your global workforce

Automatically work in language specified in the user’s Salesforce settings

Get a fully localized experience for global Salesforce users:

  • Senders
  • Signers
  • Administrators

 

 

Standardize forms and templates to meet business requirements

Upload and reuse documents from EchoSign document library

Apply a form field template to quickly add fields to commonly generated documents

 

 

Send contracts in record time – the best experience just got better

  • Work with an easier, more modern UI
  • Drag and drop to reorder recipients and documents
  • Use calendar picker to select expiration dates
  • Replace current signer when document is out for signature
  • Let recipients sign in any order

Version 14

Send Agreements from Chatter

14-1

 

Significant Improvements to Data Mappings

14-2
14-3

 

Globally Translated Experience for Senders in Salesforce

14-4

 

Optimized Sending

14-5

Agreement Templates Improvements:

  • Automatically pull recipients from Account Contact Roles
  • Automatically attach Quotes when sending from Opportunity object
  • Automatically associate the Opportunity and Account to Agreement record when sending from those objects
  • Use specific Attachment ID for Agreement attachment
  • Use Agreement Templates with Conga Composer

 

Other  Enhancements:

  • Send to more than 6 recipients or send for approval with Conga
  • Option to retain Agreements from Lead record even if converted to Account, Contact, or Opportunity

 

 

Salesforce Identity Integration

Adobe EchoSign has been tested, validated and documented to integrate with Salesforce Identity, making it easier than ever for IT organizations to enable critical identity and access management features seamlessly and securely

Learn more at: http://www.salesforce.com/identity

Version 13

Highlights for Version 13 Release

 

Optimize document workfows for your business needs

  • Send documents for approval
  • Send quote PDFs and use custom contacts with agreement templates
  • Create formulas to calculate data from other felds

Better identify your signers for critical documents

  • Enable advanced signer authentication

Get instant updates and collaborate in real-time to close deals with speed

  • Adobe EchoSign for Chatter brings you up to date wherever you are

Set up faster and hit the ground running

  • Leverage the simple setup wizard and new admin page
  • Synchronize Salesforce profiles and EchoSign groups
  • Quickly enable document data merge or push signer data back to Salesforce
  • Experience step by step guided walk-thrus of key features

 

Setup Wizard and Improved Admin Page

13-1

 

Send Documents for Approval

13-2

 

Advanced Signer Identity Verification

13-3

 

Use Case Example

13-4

 

Knowledge Based Authentication (KBA)

13-5

 

Web Identity Authentication

13-6

 

Enhanced Workflows for Agreement Templates

13-7

 

Merge Data from Salesforce to Create Documents

13-8

 

Push Data Back to Salesforce

13-9

 

Adobe EchoSign for Chatter

13-10

 

Automated Sync for Salesforce Profiles and EchoSign Groups

13-11

 

EchoSign for Salesforce Guided Walk-thrus

13-12

EchoSign Spring 2013 Features

  • Create powerful, dynamic forms with calculations and then merge calculated data back to Salesforce
  • Add or change signing deadlines after agreement is out for signature
  • Exclude internal signers from document deadlines
  • Improved document readability during preview or signing
  • Require signers to accept your organization’s custom terms of use during signing
  • Updated iOS mobile app with offline signing capabilities

 

Version 12

Highlights from Version 12 Releases

Version 12 released in Spring 2012:

  • Merge data from Salesforce to documents before sending
  • Define default agreement options and preferences through agreement templates

Version 12 update (dot release) launched September 2012:

  • Associate supporting documents collected from signers with Salesforce objects
  • Attach files stored in Salesforce Content repository to send for signature
  • Separately attach each signed document to a Salesforce object when multiple documents were sent in a transaction

 

Improved Admin Page

12-1

 

Merge Data from Salesforce into EchoSign Agreements

12-2

 

Agreement Templates and Send to EchoSign button

12-3

 

Include the Signed Agreement and Audit Trail in Salesforce

12-4

 

Advanced Customization Options

12-5

 

Attach Files from Salesforce Content

12-6

 

Collect Supporting Documents

12-7
12-8

 

Adobe PDF Certification For All EchoSign Documents

12-9

 

Conditional Data Fields

12-10

 

Additional EchoSign Form Fields Enhancements

12-11

 

Additional Features

12-12

Version 11

Update Salesforce.com with EchoSign Form Field Data

 

11-1
11-2
11-3
11-4

Za ta izdelek je bila izdana neprenosljiva licenca za priznanje avtorstva, nekomercialno uporabo in skupno rabo pod enakimi pogoji 3.0  Objav v storitvah Twitter™ in Facebook ne urejajo pogoji pogodbe Creative Commons.

Pravna obvestila   |   Pravilnik o zasebnosti v spletu