Issue Number
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.
A new OAuth Scope setting now allows Adobe Sign group-level admins to create a connection between Adobe Sign and Salesforce.
Adobe Sign users can no longer choose Web Identity or Social ID as the identity verification method. However, users can continue to verify signers' identity via password, phone, or knowledge based authentication (KBA).
The Adobe Sign icon used throughout the application has been updated to the new branding.
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:
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.
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:
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:
The analytics setting is enabled by default for most new customer installations
When enabled, a record is automatically added to your CSP Trusted Sites for the adobe.io site name:
Disabling the analytics settings automatically removes the adobe.io record from the CSP Trusted Sites page.
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 |
Issue Number | Corrected Issue Description |
---|---|
20326 | The agreement name field has been increased to 255 characters |
20977 | Added the country code for Uruguay for phone authentication |
21126 | Fixed an issue where the email option for authentication would not be disabled if deselected |
21765 | Corrected an issue where the Upload or Drop files component was not available on the Agreement page. |
22107 | Fixed an issue where custom agreement triggers could not work from a related list |
22116 | Fixed a cookie issue that could break Hosted Signing |
22220 | Fixed an issue with the Agreement visual force page that could prompt a Document Not Available error |
22329 | Fixed an issue with AutoSend templates that could generate a 404 error when sending |
22517 | Fixed an issue where documents could become unviewable in salesforce after data governance is applied |
The Adobe Sign for Salesforce package is supported for two major versions beyond the current major version.
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.
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:
Issue Number | Corrected Issue Description |
---|---|
15644 | Fixed an issue where the agreement template would fail if there was no attachment under the Master object |
17112 | Corrected a situation that could cause recipients to get the agreement in incorrect order |
18791 | Corrected an issue where the password was masking instead of displaying "Enter/Confirm Password" |
18834 | Improved Contact load speed on the Send page |
18889 | Fixed an issue where File Mapping could fail when signed agreements were returned as separate PDFs |
19063 | Corrected an issue where agreements "Send on behalf" of someone else could not be Removed/Canceled by API |
19197 | Corrected an issue that could trigger an error when sending via the Adobe Sign Opportunity Publisher in Lightning |
19301 | Fixed an issue that could cause "Callback failed" errors if the phone number was malformed |
19333 | Improved search to reduce CPU timeout errors |
19420 | Fixed an issue where the final PDF would not attach to the agreement object |
19626 | Fixed an issue where email notification to intermediate recipients would send when disabled |
19646 | Fixed an issue where the Status of the agreement would become blank if the agreement was canceled/declined |
19661 | Fixed an issue that could cause supporting attachment document to not attach to the agreement object when there is more than one. |
19683 | Expanded the Adobe Sign Community User permission set to include group mapping |
19888 | Improved agreement name management for Developer accounts to prevent them being stuck in Draft status |
19910 | Improved our Lightning Component, AgreementPanel styling to better accommodate Salesforce Paths. |
19917 | Fixed an issue where long agreement names with an apostrophe could get stuck in Draft status |
19979 | Fixed an issue where an attached file would open a bytestream of a file instead of the formatted file |
20007 | Corrected the Hide blank recipient" placeholder when using runtime variables |
20023 | Improved product line mapping to better support multiple filter criteria |
20146 | Improved the functionality of pasting an email into the recipient field by right-clicking. |
20239 | Corrected an issue that could cause the page top jump when clicking a button |
20254 | Improved attachment logic to mitigate an error if Salesforce CRM Content is not enabled |
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:
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 |
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.
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.
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:
Manually updating an agreement now updates all elements of an agreement (recipients, events, Images, etc) instead of just the status.
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:
The manual update process has been improved to update the entire suite of Agreement objects, including all links, images, events, status, and data mappings.
The event descriptions for agreements are being updated with three changes:
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.
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.
The Agreement Template interface has been updated to provide improved clarity of the template content in five tabs.
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.
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.
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.
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.
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.
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.
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.
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
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.
A new setting has been added to expose the API name of a field when defining data or merge mapping.
To enable this feature:
3. Click the Manage button
4. Click New (or Edit, if you have configured settings before)
• The Adobe Sign Settings page will load
5. Use your “Find” function (cmd/ctrl + f) to locate Show File API Name
6. Click Save
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 |
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
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.
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.
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.
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:
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.
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.
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.
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.
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.
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:
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.
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)
Enable Norwegian as a language option
Update Translations
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 |
o Click Save
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) |
o Click Save
Master Picklist Value Label |
Picklist Value Label Translation |
---|---|
Constant |
Konstant |
Salesforce Object Field |
Salesforce-objektfelt |
o Click Save
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 |
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:
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.
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 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.
In the Lightning Experience, the Adobe Sign pages have a new, cleaner look.
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.
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
6. Select a related Contract
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.
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.
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.
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.
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.
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.
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:
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.
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.
The Send page displays in limited editing mode and you cannot make changes in the Recipients or Message sections.
In this Send page, you can add, delete, replace (delete then add), and reorder documents.
To add a document, do one of the following:
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.
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 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.
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.
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.
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.
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.
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 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.
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 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.
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.
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.
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.
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.
You will receive a Success! message when the wizard has linked your account to enable automatic status updates.
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.
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.
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.
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:
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.
Fully rebranded the application to Adobe Document Cloud eSign services for Salesforce
Enabled OAuth as the authentication method for the package
Salesforce 1 Enabled
Do it all on mobile – send and track agreements from Salesforce1
Send from anywhere
Comply with business policies on the go
Manage agreements on the road
Close deals on-site with in-person signing from Salesforce1
Verify signer identity – get higher assurance with phone authentication
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
Easily change authentication method
Send and manage in batch – save time and effort
Drive efficiency and create many documents in batches:
Send and manage agreements effortlessly
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:
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
Send Agreements from Chatter
Significant Improvements to Data Mappings
Globally Translated Experience for Senders in Salesforce
Optimized Sending
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
Highlights for Version 13 Release
Optimize document workflows for your business needs
Better identify your signers for critical documents
Get instant updates and collaborate in real-time to close deals with speed
Set up faster and hit the ground running
Setup Wizard and Improved Admin Page
Send Documents for Approval
Advanced Signer Identity Verification
Use Case Example
Knowledge Based Authentication (KBA)
Web Identity Authentication
Enhanced Workflows for Agreement Templates
Merge Data from Salesforce to Create Documents
Push Data Back to Salesforce
Adobe EchoSign for Chatter
Automated Sync for Salesforce Profiles and EchoSign Groups
EchoSign for Salesforce Guided Walk-thrus
EchoSign Spring 2013 Features
Highlights from Version 12 Releases
Version 12 released in Spring 2012:
Version 12 update (dot release) launched September 2012:
Improved Admin Page
Merge Data from Salesforce into EchoSign Agreements
Agreement Templates and Send to EchoSign button
Include the Signed Agreement and Audit Trail in Salesforce
Advanced Customization Options
Attach Files from Salesforce Content
Collect Supporting Documents
Adobe PDF Certification For All EchoSign Documents
Conditional Data Fields
Additional EchoSign Form Fields Enhancements
Additional Features
Update Salesforce.com with EchoSign Form Field Data
تسجيل الدخول إلى حسابك