The recommended approach is to use a pre-submit element in the OmniScript that calls a custom Integration Procedure. This leverages the native, configurable order management framework to execute business logic at a precise moment (pre-submit) based on a condition (the checkbox). It keeps the logic maintainable within the declarative tools, avoiding hard-to-manage code like Apex triggers for core order flow logic.

Lazy loading via separate DataRaptor Extract transforms called at the point of need is the strategic Vlocity pattern. It aligns with the framework’s strengths, improves perceived performance by loading data incrementally, avoids timeout risks from large monolithic calls, and keeps the integration logic configurable and reusable within the toolbox.

Pricing is highly dependent on the context provided by the active Pricing Plan and its effective date. An incorrect price with identical matrices most commonly points to a contextual issue: the wrong Pricing Plan version being active or the order date falling outside the effective date range of the pricebook entries in UAT. This is a fundamental and common configuration checkpoint.

Creating a new Order Lifecycle State is the correct architectural approach. It formally models the new business stage in the order’s journey, provides a clear status, and can be integrated with Actions, approvals, and UI (like a console view filtered on that state). It’s more robust and trackable than just adding a field or a script step, which doesn’t formally represent a stage in the process.

Leveraging an Order Lifecycle Action tied to the ‘Activated’ state is the native, declarative Vlocity pattern. The Integration Procedure can orchestrate the Document Generation (using a template) and then use an Attachment DataRaptor Post-Transform to attach the resulting file to the Order record. This keeps the entire process configurable within the Vlocity framework.

The hierarchical relationship between cart items is established through the `vlocity_cmt__RootItemId__c` and `vlocity_cmt__ParentItemId__c` lookup fields. If the Add to Cart Integration Procedure or the surrounding logic does not correctly set these relationships (often based on Product Relationships or bundling logic), items will appear as siblings rather than in a parent-child structure. This is a core concept for modeling complex product bundles.

Complex discounting logic based on customer attributes and order metrics is a core function of the Vlocity Pricing Engine. Implementing it as an Adjustment with an Eligibility Rule (checking Loyalty Tier and order total) and a Formula ensures it is evaluated centrally during the pricing call, respects all pricing precedence rules, and is reusable across quotes and orders. This is the declarative and scalable approach.

The standard, low-code Vlocity pattern for external integration is: Integration Procedure (orchestrator) -> HTTP Action (call) -> DataRaptor Transform (response mapping). This IP is then invoked declaratively from an OmniScript Data Source or a Remote Action element. This keeps the entire flow configurable, debuggable, and within the supported framework without requiring custom code.

The most user-friendly and declarative approach is to control the UI element’s visibility. By configuring the FlexCard that displays the line items, you can set the visibility of the ‘Delete’ button (or action) to be conditional on the parent order’s status not being ‘Pending Fulfillment’. This proactively guides the user by removing the unavailable option, rather than letting them attempt the action and see an error.

The recommended approach is to use a pre-submit element in the OmniScript that calls a custom Integration Procedure. This leverages the native, configurable order management framework to execute business logic at a precise moment (pre-submit) based on a condition (the checkbox). It keeps the logic maintainable within the declarative tools, avoiding hard-to-manage code like Apex triggers for core order flow logic.0