Migrating from legacy Vlocity to OmniStudio Standard Runtime may need to preserve existing DocuSign integrations that support document generation and eSignature business processes. A common migration scenario involves moving legacy DocuSign configuration while maintaining existing functionality.
This includes migrating:
At this time, these components are not supported for automated migration to OmniStudio Standard Runtime.
OmniStudio Standard Runtime currently does not provide feature parity or automated migration support for legacy Vlocity DocuSign assets, including:
Additionally, the OmniStudio Migration Assistant does not assess or migrate these assets. As a result, legacy DocuSign configurations and OmniScript DocuSign Action references do not have a supported automated migration path to Standard Runtime.
Engineering has confirmed that this is a product gap rather than a configuration defect.
At this time:
005389878

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 are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security 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 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.