Update DocuSign Account Id In Omnistudio Data Mapper
Your credentialing specialist can verify whether the DocuSign sent to the provider after
primary source verification is signed. Update the default DocuSign Account ID in the Omnistudio
Data Mapper Interface with your DocuSign Account ID.
Required Editions
Available in:
Lightning Experience
Available in: Enterprise and
Unlimited Editions with Health Cloud and Health Cloud for Experience Cloud
Sites
User Permissions Needed
To edit an Integration Procedure:
Omnistudio admin
From the App Launcher, find and select Omnistudio Integration
Procedures.
Search for and expand HealthCloudPNM/GetDocuSignStatus, and then
select DocuSignStatusCheck (Version 1).
In the Structure panel, select HealthCloudPNMDocuSignStatusInput to
access its properties.
Under Properties, click next to the linked Omnistudio Data
Mapper.
In the Omnistudio Data Mapper Configuration, locate the
DocuSignAccountId field under the output JSON path that contains the
default account id.
Clone the Omnistudio Data Mapper and assign it a new name, such as
HealthCloudPNMDocuSignStatusInput2.
Replace the default value of the DocuSignAccountId field with your specific DocuSign
Account ID.
Go back to the properties section of HealthCloudPNMDocuSignStatusInput and update the
Omnistudio Data Mapper name to match the new name assigned during cloning, that is,
HealthCloudPNMDocuSignStatusInput2.
Note Version control is available for Integration Procedure in the
latest version of Omnistudio, so you're not required to update the Data Mapper name in the
properties in the final step.
Did this article solve your issue?
Let us know so we can improve!
Loading
Salesforce Help | Article
Cookie Consent Manager
General Information
Required Cookies
Functional Cookies
Advertising Cookies
General Information
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.