Issue #
This document provides detailed information about the new features and changes that are included in the current release of the Adobe Sign integration for Microsoft Dynamics 365 CRM
Due to the updated API calls that enable the 9.3 functionality, customers upgrading their existing Dynamics 365 Online accounts from a version prior to 9.3 will need to recreate the real-time automatic status updates with Power Automate using the updated Template: Update Dynamics Agreement record on agreement state change in Adobe Sign.
Adobe Sign for Dynamics V 9.5.8 is a minor version update with focus on fixing known issues. Note that the classic UI is no longer supported with the release of v 9.5.8.
Issue # |
Description |
---|---|
22286 |
Fixed the issue where duplicate agreements are generated when running Dynamics 9.3.7.0. |
22367 |
Fixed the Dynamics online error where the Action field displays 'No' for a signed agreement that is sent using 'one-click send'. |
22579 |
Improved performance of Data Mappings that reference to many related entities. |
22715 |
Fixed the issue where users are not able to upgrade the Adobe Sign package in Dynamics On-prem. |
22755 |
Fixed the issue where users are not able to create a template and save it without a password. |
22772 |
Fixed the issue where changing the authentication to a method other than the default Email resets back to Email. |
22835 |
Fixed the issue where upgrade from Dynamics OnPrem 8.0.0.2 to 9.5.4.0 fails due to missing components. |
22873 |
Dynamics online now shows the agreement status even without the need to click the 'Update' button. |
22879 |
Fixed the error in importing solution into organizations with non-default date/time format. |
22902 |
Fixed the Adobe Sign CreateAgreement plugin's timeout error. |
22925 |
Fixed the error where user are blocked from sending agreements after upgrading to v9.5.4.0. |
22953 |
Fixed the error where redudant user association is created for existing and provisioned users. |
22964 |
Fixed the issue in the integration with Adobe Sign app. |
22996 |
Fixed the issue where on-prem Dynamics failed to do a clean install for V 9.5.5.1 or upgrade to V 9.5.5.1. |
23042 |
Fixed the on-prem Dynamics error in creating a new agreement. |
23058 |
Fixed the issue that blocked the users from upgrading Dynamics Online 8.0.0.2 to 9.5.4.0. |
23080 |
Fixed the UI error caused when the browser tab is refreshed while sending an agreement. |
23119 |
Error messages now indicate the reason for failed sending. |
The 9.5 update provides interface changes in the Home page for online environments, as well as the New Agreement and Admin Settings pages for both online and on-premises organizations.
The Home landing page (online version only) has been updated to provide a cleaner interface, with direct access to the most recently updated agreements owned by the user.
The Admin Settings page has been streamlined to better expose the options for administrators.
The New Agreement page has been updated to consolidate the security settings into the Options panel and remove legacy controls.
An Add me button has been added to the recipient's section. This option adds the current user to the agreement's recipient list.
Add me also allows the user to create an agreement for only the creator to sign, allowing for internal templates like time-off requests.
Additionally, the Authentication method can now be edited in the agreement interface by clicking the field and selecting the new method from a dropdown list.
Signed/approved agreements provide information on the current status and next steps at the top of the recipient section:
GetAgreementId is used to get the IDs of agreements that are not created from within a workflow.
This Activity enables a user to create a workflow (using GetAgreementId as the first step) to return an agreement ID that can be used in subsequent steps (add recipients, add documents, etc.), providing a means to automate agreement manipulation when an agreement is created from the new agreement UI.
21160 |
Improved data mapping processing speed for agreements with 50+ fields |
21962 |
Fixed an issue where the "Send report for Signature" option would not appear when "All Languages" is selected |
22094 |
Corrected a timeout error when a very large number of fields is present on a document |
22126 |
Fixed an issue where the Send report for signature option would not show up on custom entities |
22135 |
Fixed an issue that blocked dynamic values from being used in the Agreement subject and message in templates |
22297 |
Improved interaction with templates to support sending all template documents or just the active ones |
21160 |
Improved data mapping processing speed for agreements with 50+ fields |
21962 |
Fixed an issue where the "Send report for Signature" option would not appear when "All Languages" is selected |
22094 |
Corrected a timeout error when a very large number of fields is present on a document |
22126 |
Fixed an issue where the Send report for signature option would not show up on custom entities |
22135 |
Fixed an issue that blocked dynamic values from being used in the Agreement subject and message in templates |
22297 |
Fixed an issue where inactive contacts and templates could still be used in agreement creation |
The focus of this minor version update is to address a vulnerability we have identified internally.
Adobe is not aware of any exploits "in the wild" for the issues addressed in this update. However, to help protect the customer base, this update is mandatory.
The popular Send Report for Signature package has been integrated into the new Unified Interface, removing the need for a separately installed package.
The Home landing page now has a top banner that will report news, warnings, and errors.
Messages are ordered by date, and can be dismissed by the user:
The Adobe Sign authentication method has been added to the identity verification methods, allowing for Bio-pharma compliant signatures to be applied to agreements generated in Dynamics 365.
Adobe Sign for Dynamics 365 On-Premises v9.3.9 is supported on the Dynamics Unified Interface, but does not have support for features which are available in Adobe Sign for Dynamics 365 On-line such as:
Issue # |
Description |
21103 |
Corrected an issue that would cause the agreement events to be re-generated when the record was opened in Dynamics |
20681 |
Corrected an issue that could cause templates to not populate the recipients or attachments when linking custom entities and attempting to pickup specific lookup fields |
Adobe Sign now leverages the Unified Interface.
Adobe Sign functionality has been expanded to the Field Service and Customer Service Hub modules.
Issue # |
Description |
18726 |
Improved handling of a Business Process error generated when using Quick Create : Recipient |
20363 |
Corrected an issue that could error when downloading a signed agreement |
20619 |
Improved the error handling for agreements missing a valid email address |
20733 |
Fixed an issue that could cause an error when manually updating an agreement status |
20952 |
Fixed an issue where the Entity field on templates wasn't clickable for IE browsers |
20964 |
Fixed an issue where an activity feed exception could block an agreement from updating |
Real-time agreement status updates are available for all accounts that install/upgrade to the new 9.1.0.5 version of Adobe Sign for Dynamics 365.
This enhancement leverages the Adobe Sign webhooks to trigger a Power Automate workflow to update all agreement status changes as they happen.
Support has been added to the Sales Hub to allow multiple files to be attached at once.
Issue # |
Description |
19070 |
Fixed an issue where the status under Action Complete was not getting updated |
19097 |
Corrected an issue where the audit report was getting attached to Notes separately |
20085 |
Corrected an issue where a scripting error could trigger while sending agreements from the UCI environment |
20106 |
Corrected an issue where the status of an agreement would not update unless the record was open |
The Adobe Sign for Dynamics aspplication has been fully localized to support French, German, and Japanese languages.
Issue # | Description |
18430 | Fixed an issue where Identity Verification was appearing locked in the agreement page |
18536 | Adopted the Universal Sortable Date Time Pattern for event time/date stamps |
18614 | Corrected an issue where an agreement created from a Service Activity entity would not include Recipient & Files attached when the Recipient is a Lead contact email |
18685 | Corrected a problem where the action completed was not getting updated for multiple recipients with same email id |
18722 | Resolved a Business Process error for an Adobe Sign user if user provisioning is turned off in Dynamics |
19200 | Corrected an issue where identity verification of the recipient was not being applied |
19210 | Improved error notification for unsupported file types |
19403 | Resolved a Script Error that occurred when switching back and forth from the agreement page |
19659 | Improved status refresh for agreements that are WAITING FOR AUTHORING |
19698 | Corrected a state where an Uploaded file from the local system resulted in an error |
19909 | Fixed an issue with uploading files containing upper case extensions |
20022 | Corrected an issue where a new agreement produced blank values in the agreement name and message |
The Adobe Sign for Dynamics 365 v8 package extends functionality into the Sales Hub for customers that have deployed on Dynamics 365 9.x.
The Sales Hub makes available all of the Adobe Sign functionality for web browsers, tablets, and other mobile devices.
The Adobe Sign for MS Dynamics v8 package is focused primarily on rearchitecting the solution to improve overall security and performance. Creating Agreements, data mapping, and agreement template process have been significantly improved.
The user interface has been completely redesigned to comply with the Dynamics 9.x web client UI refresh.
Both the Admin and User interface have been refactored to better expose available features in a more compact browser footprint.
Dynamics workflows are fully supported with the addition of six activities, two commonly used actions, and one fully prepared workflow.
The LinkedIn Sales Navigator can be exposed by the Dynamics Admin, allowing users to authenticated to their Team or Enterprise LinkedIn accounts, and retrieve the LinkedIn profiles for their recipients.
Users can Create a new agreement directly from the New (+) icon in the top ribbon.
Users only need to supply the Entity that is related to the Template they want to send, the recipient, and the actual template from a list.
Hybrid Routing allows for a complex signature flow that includes both sequential signature steps, and parallel signatures in the same signature process by using the Recipient Order fields to indicate individuals, or groups of individuals in the same order step.
A new feature that allows a user to sign a document without having to involve any other recipients. This works well for internal documents where your team can selected documents they need to sign by themselves.
Post-Sign URL redirection has been added, allowing you to deliver your signer to a web site of your choosing after they have signed their document.
The Agreement Name and Message fields now allow insertion of Dynamics field values. Type a left brace { into the field, and you are presented with a list of field names from the entity that the agreement (or template) is tied to. These field names will insert the related field content when the agreement is sent, creating an automated system for personalizing your communications.
The Send Report for Signature feature has been removed for compliance with MSFT regulations.
You’ll see Adobe Sign where you previously saw Adobe Document Cloud eSign (or Adobe eSign Services for short) as evidence of the rebranding.
MS Silverlight is no longer a required element to using the application. Browser support includes IE 9+, Chrome, Firefox, and Safari 3+
Mac users rejoice! Adobe Sign for MS Dynamics now fully supports users that prefer Apple systems.
A new custom preference has been added for v5. When enabled, users who send agreements in MS Dynamics are automatically auto-provisioned with an Adobe Sign user account.
To improve efficiency, flexibility and processing speed, Adobe Sign—and consequently the integration for MS Dynamics—has migrated from SOAP-based to REST-based APIs.
Administrators can store commonly used documents on the Adobe Sign server and make them available to all users via a drop-down on the New Agreement page.
Turbo Forms can now be leveraged for quicker document generation
All users have a personal Agreement Template to customize the default values for any new Agreement they open.
登录到您的帐户