Understanding Standard Runtime in OmniStudio

What is a Standard Runtime?

OmniStudio was originally part of the Vlocity managed package. As with any managed package, Vlocity stored its configuration data within managed custom objects rather than Salesforce metadata. This approach is common among managed packages, including CPQ and others.

However, when Salesforce acquired Vlocity, it significantly enhanced OmniStudio by enabling standard Salesforce metadata support. This means that configurations such as OmniScripts, FlexCards, and DataRaptors are now stored as Salesforce metadata. Consequently, these configurations are processed by Salesforce core services rather than managed package code.

Benefits of Standard Runtime

Better Performance: Using Salesforce metadata improves the performance of OmniStudio tools.

Enhanced Integration: Standard runtime allows the use of OmniStudio components in native Salesforce tools such as Dynamic Forms, Community Builder, and custom LWCs.

For the purpose of this blog, I have created a test OmniScript and deployed a Standard Runtime Compatible LWC for it using the button highlighted in the screenshot below.

Once you deploy a Standard Runtime Compatible LWC, it creates a wrapper LWC.

If you want to further extend the generated wrapper LWC to be displayed in screens like Flow and Community Builder, you can do so by adding the targets in the meta.xml file of the generated LWC. And, it works like a charm!

This blog post aims to provide you with a clear understanding of the standard runtime in OmniStudio and its benefits. If you have any questions or need further clarification, feel free to leave a comment below!