For complex, multi-point business logic involving external data, an Integration Procedure with an Apex class provides the most robust, maintainable, and testable solution. It cleanly separates the core business logic (in Apex) from the presentation flow (in the OmniScript). The Set Values element can then use the returned result to control navigation, keeping the OmniScript itself simple and declarative.

In Vlocity CPQ, product attributes are assigned to a Pricebook Entry via an Attribute Matrix. If the attributes are not mapped there, they will not be populated during the Order creation process, even if the DataRaptors are functioning correctly. This is a common and specific point of failure for missing attribute data in Quote-to-Cash automation.

FlexCards are designed to consume data through their declarative Data Source pipeline. For complex data shaping, using the built-in Query, Filter, and Transform nodes is the most aligned and efficient approach. It leverages the platform’s caching and optimization without requiring custom Apex, keeping the logic within the low-code toolset for easier maintenance.

Vlocity metadata has dependencies. When deploying via tools like Vlocity Build or ANT, components must be deployed in a specific order. A core rule is that dependent components (like DataRaptors, Integration Procedures, Templates) must be deployed before the components that reference them (like OmniScripts, FlexCards). Failing to follow this order causes ‘missing dependency’ errors.

Calculation Procedures are the Vlocity platform’s native, reusable engine for complex business calculations, especially in CPQ contexts. They are designed to be invoked from Pricing Matrices, Integration Procedures, or other Calculation Procedures. This keeps the logic centralized, maintainable, and separate from UI or flow-specific code.

The platform includes a scheduled Apex job (‘BatchDeleteSavedOmniScriptSessions’) that automatically purges saved OmniScript sessions after a default period. To control the lifespan of drafts, an administrator must configure the schedule and frequency of this job in Vlocity Administration > Batch Jobs, or customize the batch class logic.

The Vlocity Integration Framework manages database transactions for an IP execution. As long as all steps execute sequentially in the same path (not using ‘Continue on Error’ for critical steps), a failure at any point will automatically roll back all DML operations (from DataRaptor Loads, etc.) that occurred within that same IP transaction. This is a key feature for ensuring data integrity.

Lazy loading, or deferring the loading of non-essential data until it’s needed, is a highly effective UI performance pattern. Instead of loading all products when the OmniScript starts, you can structure it so the product list is fetched via a separate Action element only when the user reaches the relevant step. This dramatically improves perceived initial load time.

Pricing Plans are the central configuration that ties together which Pricing Matrices, Calculation Procedures, and other rules apply to a quote. If a location change doesn’t trigger re-pricing, the most likely cause is that the quote’s Pricing Plan either does not include the location-based Pricing Matrix, or the matrix’s conditions are not correctly evaluating the new location value.

For complex, multi-point business logic involving external data, an Integration Procedure with an Apex class provides the most robust, maintainable, and testable solution. It cleanly separates the core business logic (in Apex) from the presentation flow (in the OmniScript). The Set Values element can then use the returned result to control navigation, keeping the OmniScript itself simple and declarative.0