某些 Creative Cloud 应用程序、服务和功能在中国不可用。
The Adobe Sign for Dynamics application 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 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 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.
- Templates are built and controlled under the Administrators authority.
- Templates are now tied to Entities, giving the ability to make functional templates that preformat agreements with recipient chains, custom messages, pre-attached files, and other options.
- With templates becoming function based, Data Mapping is tied closely to template function, ensuring that as templates are used, the correct data exchange is taking place.
- Templates now have an Auto-Send option that will send an agreement for signature once it is selected, without opening the configuration window/send page.
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.
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+
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.
Twitter™ and Facebook posts are not covered under the terms of Creative Commons.