Order of Operations Explained When an Order is Activated

order activation overview when an opportunity is marked closed won , nue automatically converts the associated primary quote into an activated order (there are other automation options please refer to automating order generation from primary quote at key opportunity stages docid 9njvesm0hqyw5fn7tmnir ) this process ensures that subscriptions, entitlements and assets, billing records, and downstream metrics are created accurately and consistently, without requiring manual intervention the activation workflow consists of both immediate system actions and several background processes that finalize prorations, credit handling, platform synchronization, and revenue recognition this guide explains the order of execution, dml boundaries, and the synchronous versus asynchronous automation that nue runs upon order activation immediate system actions (seconds after close won) as soon as the opportunity is closed as won, nue performs several real time operations order creation and activation the primary quote is converted into a draft order, and the order is immediately marked activated this activation signals the system to generate all the necessary subscription, asset, and entitlement records tied to the order’s product catalog nue encapsulates the order activation business logic within salesforce apex triggers, allowing you to activate a draft order using code below is an example of how to activate an order with apex id orderid = '801xxxxxxxxxxxx'; // replace with your order id order ord = new order( id = orderid, status = 'activated' ); update ord; assets, entitlements and subscriptions generation all order line items are processed based on their product type—creating or updating subscriptions for recurring or term based products assets for items delivered or provisioned to the customer entitlements for support or service based offerings change orders (renewals or amendments) generate updated subscription and asset records that reflect the new term or quantity account and billing updates the system updates relevant account level metrics, including total contract value (tcv) customer since dates associations between sold to, bill to, and related accounts these updates ensure that sales, billing, and finance teams access consistent customer lifecycle data bill cycle day alignment billing cycle day assignments are propagated to subscriptions, assets, and entitlements so billing schedules start correctly and consistently background processing (0–4 minutes after activation) following the immediate activation, several asynchronous processes finalize billing, metrics, and platform synchronization credit balance review and pricing adjustments if your organization uses prepaid credits or financial commitments, nue checks credit balances and adjusts pricing if needed this ensures the order reflects correct proration and usage based consumption subscription metrics calculation the system calculates subscription level metrics such as monthly recurring revenue (mrr) annual recurring revenue (arr) total contract value (tcv) these metrics feed forecasting, analytics, and revenue management processes revenue metrics schedules arr by fiscal period is automatically generated, creating period by period revenue values based on subscription start and end dates nue origin vs salesforce origin orders salesforce origin orders orders created from salesforce (via opportunity → primary quote) activate immediately within salesforce, then sync into the nue platform in the background nue origin orders orders created directly in nue follow a different process typically they activate in nue first, and salesforce does not finalize activation until the nue platform confirms completion this ensures nue remains the source of truth for activation timing when the system setting ' sync draft orders with their associated quotes when the orders serve as the primary orders ' is set, the draft order will be synchronized to nue automatically upon saving operational reliability all activation steps both synchronous and asynchronous are designed with safeguards and retry mechanisms to ensure data consistency background jobs can be safely re run if needed without impacting already activated orders this process ensures that your orders, subscriptions, assets, entitlements, billing records, and revenue schedules are always created accurately and consistently, supporting a smooth end to end customer lifecycle