Go to the Microsoft AppSource page for Adobe Acrobat Sign for Microsoft Dynamics 365 package and select Get it now.
Acrobat Sign offers a plug-and-play integration solution with Microsoft Dynamics CRM that provides the following benefits:
Adobe Acrobat Sign for Microsoft Dynamics 365 online: Installation Guide provides instructions on how to:
To upgrade your already installed Adobe Acrobat Sign for Microsoft Dynamics 365 package to the latest version, refer to the Upgrade Guide.
Contact customer support if you've any questions or concerns regarding the installation process.
To be able to successfully install and use Acrobat Sign for Microsoft Dynamics 365, you must ensure that:
For Microsoft Dynamics to work seamlessly in the Microsoft Edge browser you must trust the below sites in your browser security configuration:
Go to the Microsoft AppSource page for Adobe Acrobat Sign for Microsoft Dynamics 365 package and select Get it now.
For a free trial of Adobe Acrobat Sign, request a 30-day free trial of Adobe Acrobat Sign for Dynamics CRM.
On the Confirm your details dialog that appears, verify your user details and review permission details. Once done, select Get it now.
On the Install Adobe Acrobat Sign for Microsoft Dynamics 365 dialog that opens:
If a previous Adobe Acrobat Sign for Dynamics package is already installed, then the package gets upgraded to the new version.
On the Power Platform admin center page that opens, verify the progress of the installation. It may take about 30 minutes. Refresh the page to update the status.
After installing the Acrobat Sign for Microsoft Dynamics 365 package, you must implement the following configuration settings:
When you install Acrobat Sign for Microsoft Dynamics 365 online for the first time, you must generate an Integration key in Acrobat Sign and enter it into Dynamics 365 online environment. The integration key is the access token that authenticates the Acrobat Sign and Dynamics environments to trust each other and share content.
To generate an Integration Key in Acrobat Sign:
Log in to Microsoft Dynamics 365 using your admin account credentials.
You admin account in Acrobat Sign holds the Integration Key.
Navigate to Account > Acrobat Sign API > API Information. Next, select Integration Key.
If you don't see the Integration Key link on your API Information page, contact Customer Support to modify your account settings to expose this required functionality.
On the Create Integration Key interface:
On the Access Tokens page that opens:
Return to the Dynamics CRM environment and complete the following steps:
O the Acrobat Sign Home page that appears:
On the Enable Adobe Sign activity feeds dialog that opens, you may select Enable to enable the Adobe Sign activity feeds.
You can manually enable or disable activity feeds on the Admin Settings > Configuration page.
You must disable legacy form rendering to use Acrobat Sign. To do this:
On the Dynamics CRM environment, navigate to Settings > Administration and then select System Settings.
On the System Settings dialog, ensure that the Use legacy form rendering setting is set to No. Then, select Ok.
Every Dynamics user who is expected to use the Acrobat Sign application must have one of the following security roles configured in the Dynamics environment:
To configure the security roles:
On the Dynamics environment, navigate to Settings > Security.
On the Security page that opens, select Users.
On the Users page that opens:
The real-time automatic status updates feature uses Acrobat Sign webhooks to trigger a Power Automate flow whenever an agreement status changes.
To enable real-time agreement status updates:
On the Dynamics 365 page, select the app launcher from the top-right corner and select Power Automate to switch to Power Automate.
Add the Adobe Acrobat Sign connector to your Power Automate list of connectors using the following steps:
From the left panel, select Templates and then use the search bar to find and add Update Dynamics Agreement record on agreement state change in Adobe Sign.
Authenticate to the following template services:
Once you successfully authenticate to the services, a green checkmark appears next to the authenticated service. Once done, select Continue.
On the template details page that opens:
You can build templates, map data, and create custom workflows using the tools available on the Acrobat Sign Admin Settings page.
To access the settings:
Account and Setup
It holds the Integration key and checklist for the initial account setup process. You can any time remove the integration key to disconnect the Acrobat Sign services.
The Setup Checklist shows the installation progress as measured by the key configuration points:
Configuration
It includes quick links to the most common admin functions and documentation, as well as optional flags for the user experience.
Note: New users who are automatically provisioned in Acrobat Sign have a randomized password. Since the integration works as an authenticated application via API, there is no functional problem within the Dynamics environment. However, if the user wants to log in to Acrobat Sign, they must reset their password via the “I forgot my password” link on the Acrobat Sign home page.
You can configure any authentication method that you want to enable for users in your Acrobat Sign account. To do so:
Learn more about Acrobat Sign authentication methods.
If your work process requires you to have CFR 21 part 11 compliant signatures, you must configure your Bio-Pharma controls in your Adobe Acrobat Sign account. To do so:
You can remove the current Integration Key from your Dynamics environment to break the trust relationship between Dynamics CRM and Adobe Acrobat Sign, thus stopping all new transactions and updates for existing transactions. Once the key is removed, it can be re-applied at any time to resume the interaction between the two systems.
You can also revoke the integration key from your Acrobat Sign account. Revoking the key permanently disables the key from usage in Acrobat Sign.
You can use Data Mapping to:
For successful data mapping, you must have pre-built forms with defined field names to allow you to logically relate the CRM field to the Adobe Acrobat Sign form field.
A simple form is illustrated below. The fields are defined by the curly bracket pairs on either side (defining the width of the field) and the field name (the string of characters between the curly brackets).
Text tags can include additional arguments beyond the name value, including validations, calculations, and regular expressions.
See how to build forms and improve the quality of data you capture during the signature process.
See how to build forms in PDF format.
The Text Tag Shortening feature can be very useful in form design and field mapping by establishing a convention for the field names that repeat on every document (and saves time by not having to re-create the formal tag). This expressly improves data mapping across multiple forms and builds an anchor for future forms.
To define a Data Mapping Template, you can use one of the two following ways:
You can create relationships between Dynamics CRM field names and the Acrobat Sign form field names that you've defined. Data mappings are configured based on how the data flows:
Once the new field relation is processed, it appears under the configuration settings.
If you added Reverse direction mapping, you see the new relationship populate under the Acrobat Sign to CRM configuration fields also.
If you opted to Override the content protection, you see that indicated on the relationship record.
The process for discretely creating a mapping from Adobe to CRM is the same as above except there is no option to Add Reverse Direction Mapping.
You can delete one or more mapped relationships by:
If you define a field on an Adobe Acrobat Sign form that might be filled by one of several CRM fields, then you can create an ordered list (hunt group) of CRM attributes that will seek to populate the Adobe Acrobat Sign field.
For example, you may have the CRM field First Name mapped to a form field named FName, and then map the CRM field Yomi First Name to that same form field name. The application will first attempt to fill the field with content in the First Name field, and if no content is found, Adobe Acrobat Sign will attempt to use content in the Yomi First Name field. If no content is found in any element of the hunt group, the field is left empty.
To define the hunt group:
Once the record is updated in the system, you see that the records have changed to include a prefix in front of the Entity Attribute:
# will be in front of the primary/default attribute. This field will always be the first field checked for content. Subsequent relations will be numbered 1-N. The first alternate field relationship is indicated by (1) and will always be the first alternate field checked. (2) would be the second alternate field, and so on.
Once an agreement is fully signed and executed, Adobe Acrobat Sign will produce a PDF copy of the document and an audit trail of the signing process. It is possible to have these documents attached as PDF files to any other CRM Entity that is related to the template’s parent Entity.
In the MAP SIGNED AGREEMENT AND AUDIT TRAIL TO CRM ENTITY section of the template page, you will find three Document Types available via drop-down:
You can attach one or more files to any related Entity, but you must explicitly map them individually.
To map an attachment:
Attachment relationships will be listed under the configuration settings.
As an Acrobat Sign Admin in the Dynamics environment, you have the authority to create agreement templates that can pre-configure a majority of the agreement fields, attach files, and tie that agreement to relevant data mapping.
Templates are tied to a Dynamics entity, and become available for agreements sent from that entity when they are flagged as Active.
Data Maps are at the core of Agreement Templates and should be defined before the Agreement Template is configured.
Use one of the following ways to configure a new Agreement Template:
Via Agreement Templates
Via Admin Settings
The Agreement Template has four tabs each containing editable values that you can configure:
The template details show the Template - Entity - Data Map relationship for this template.
The name of the template is expressed in large font at the very top
The Recipients section contains the list and signing order of recipients that you want to pre-configure for the template.
Recipients – You can hard code a recipient list within a template by clicking the New Recipient icon in the upper-right of the window. A pop-down opens exposing the configuration options.
The Agreement Details section contains four sections:
Both the Agreement Name and Message fields permit the insertion of Dynamics field values, to improve personalization for the recipient. To open a list of possible values, type a left brace: {
This section allows you to pre-attach a file for the agreement. For example, if you create a template for an NDA, then you can attach the company NDA file directly in the template so the sender doesn’t have to.
This section defines the default verification method for the recipients, and the optional password for the final PDF document
If your company has deployed Adobe Acrobat Sign for Dynamics version 9.2 or later, you have access to the Adobe Acrobat Sign functionality on the Dynamics Sales Hub, Customer Service Hub, and Field Services.
These Hubs offers the same functionality with improved formatting, allowing direct access for phones, tablets, and any other mobile device.
The Sales Hub Dashboard gives you a quick graphical report of the agreements associated to your user.
The reports allow you to drill down in to each element and produce new graphs specific to that sub-set of data.
The page is broken out into three default sections:
The Agreements section gives you a full listing of your agreements as well as the ability to sort the Agreements by their meta-data (status, creation date, signed date, etc).
It is also possible to create a new Agreement as needed.
Users that have access to Data Mappings can sort, review, and edit existing Data Mappings.
New Data Maps can also be created.
Users that have the system authority to access Templates can review, sort and edit existing templates.
New Agreement Templates can also be created.
Dynamics Administrators can access and edit the admin-level settings for the Adobe Acrobat Sign integration.
Several built-in CRM entities are included in the Adobe Acrobat Sign package that you can relate your agreements to:
You can add your custom CRM entity (or any other built-in CRM entity) to this scope by following a few steps.
Custom entities can only start an agreement from the Request Signatures menu item.
You cannot use the Quick Create system to start an agreement from a custom entity.
For our example, let’s assume there is a custom CRM entity called “Customer”.
The Customization page loads
The Default Solution page opens in a separate window
In the left side rail under Components
A new Relationship window opens
Create the new relationship:
2. Paste the name of your custom entity (“new_customer” in our example) into the Display Name field.
3. Click Save and Close
Logga in på ditt konto