Release 2602.2

🚀 release 2602 2 is live in sandbox 🗓️ production deployment is scheduled for april 2, 2026 this release introduces the nue ai chatbot for prospects, allowing sales reps to create opportunities and quotes for prospect accounts directly through a conversational interface it also includes new product catalog publishing settings to ensure the ai always has up to date pricing information performance improvements cut lifecycle manager load times by 40% and line editor load times by 54% with lightning web security enabled, alongside new subscription metrics and expanded/collapsed state management for better portfolio visibility a wide range of bug fixes address quote to opportunity sync transparency, multi year renewal accuracy, bundle reconfiguration reliability, netsuite/stripe reconciliation, and high volume billing performance feature enhancements nue ai preview this feature is currently in preview mode please contact your account manager to request access to nue ai create quotes instantly with ✨nue ai customer chatbot nue users can now launch the nue ai customer chatbot directly from a prospect account by clicking the “customer chatbot” button on the account page or the “let’s chat” (✨) icon in the nue customer card the customer chatbot enables users to seamlessly manage the entire opportunity and quoting workflow — all within a conversational interface for accounts without existing subscriptions, users can create a new opportunity build and preview quotes using the product catalog create the quote and launch it in salesforce in addition, users can view and manage all opportunities mark a quote as primary progress opportunities to closed/won generate and view quote pdfs perform key sales actions — all in one place create opportunity why this matters this feature represents a core part of nue’s vision quote creation should not be confined to a single interface traditionally, quoting has been locked inside a rigid line editor on the other hand, ai driven experiences are often limited to chat only workflows at nue, we believe the future is both with the nue ai customer chatbot users can start quickly in a conversational interface — ideal for speed, guidance, and intent driven actions and then seamlessly transition into the line editor for more complex configurations, fine tuning, and advanced pricing this creates a flexible experience where simple tasks are fast and intuitive complex deals remain fully controllable in other words, quoting happens wherever it makes the most sense for the user — not constrained by the tool this hybrid approach allows sales teams to move faster without sacrificing control, making the entire process more natural, efficient, and scalable key business scenarios new prospect, no subscriptions quickly create an opportunity, configure products, preview pricing, and generate a quote — all from scratch active deal management review opportunities, update deal stages, and mark quotes as primary without navigating across multiple pages quote generation and sharing instantly generate and access quote pdfs for customer communication guided selling experience sales reps can rely on the chatbot to guide them through required inputs and best practices, reducing errors and improving consistency here’s a polished, customer facing release note with clear business value and scenarios enable automatic publishing for product catalog to power nue ai the newly introduced https //docs nue io/release 2602#enable publish everything for self service catalog makes it easier to keep your product catalog up to date and ready for use with nue ai new capabilities include publish all active products with a single click automatically republish products when changes are saved automatically publish products, price tags, and product relationships upon activation why this matters nue ai operates on the published product catalog to fully leverage ai driven selling — including quote creation, pricing, and recommendations — your products must be published and up to date previously, keeping the catalog published required manual steps, which could lead to missing or outdated products in ai workflows inconsistent pricing or configuration behavior delays in sales execution with these new settings, you can ensure your catalog is always ai ready , reducing operational overhead and eliminating friction in the sales process nue platform introduces nue help center access via header icon replaces the existing question mark icon with a new nue help center icon that links directly to the support portal the icon is displayed only for users with the access support center permission additionally, the nue knowledge center icon is updated to a book icon, with no change to its existing functionality billing & collection enable autocharge invoices on due date nue now supports automatically charging payment methods on an invoice’s due date instead of only at invoice activation admins can configure a tenant level “autocharge timing” setting to choose whether eligible invoices autocharge on activation or on the due date why this matters aligns automatic collection with net terms and review periods many finance teams need to offer net 15/net 30 terms so their customers can review invoices before paying with “charge on due date,” invoices can still be auto‑collected exactly when they become due, instead of forcing an immediate charge at activation lifecycle manager accelerate line editor page load reduced server calls during quote and order line editor initialization through a two phase optimization effort, cutting total calls nearly in half from the original baseline 22% reduction in server processing time from the phase 1 baseline faster time to first interactive render, especially on higher latency connections immediate loading spinner eliminates the blank page during initial data fetch accelerate lifecycle manager page load reduced server calls during lifecycle manager (customer 360 view) initialization by eliminating duplicate data fetches and optimizing metadata queries what changed 40% reduction in total server processing time ( 10s to 6s) 6 fewer network round trips on every page load summary component server time lifecycle manager 40% improvement line editor 54% improvement view subscription metrics in the nue subscription list with expand all / collapse all options see key subscription kpis at a glance with a new metrics summary bar on lifecycle manager → assets → subscriptions the bar shows # of customers , # of products, today’s arr , and total amount , and automatically updates as you filter by status, customer, product, or currency (for multi currency orgs) why it’s important this turns the subscriptions page into an immediate portfolio dashboard for revops, finance, and cs faster qbr and account prep – filter by a single customer and instantly see their footprint (how many products, how much arr, and total contract value) without opening individual records or exporting to spreadsheets better product and segment insights – filter by product (or product family) to quantify adoption and arr for specific skus or bundles, helping prioritize packaging, pricing, and roadmap decisions multi currency views – use the currency selector to analyze arr and total amount in a single currency in addition, we added an expand all / collapse all control to the lifecycle manager → assets → subscriptions page and ensures that each subscription’s expanded or collapsed state is preserved across typical page operations (search, filter, sort, pagination, and refresh) by default, bundle level subscriptions are collapsed, and revops users can switch between compact and detailed views of the full subscription hierarchy with a single click expand all / collapse all action icon track status of quote to opportunity sync on quote creation this release introduces a dedicated quote → opportunity sync status experience so users no longer have to guess whether a primary quote successfully synced its products to the related opportunity when a primary quote is saved from the line editor and the async sync job runs in the background, the quote record now shows a status banner indicating if the sync is not started , in progress , successful , errored , or timed out for error and timeout cases, a user facing error message from salesforce is displayed directly on the quote, along with apex job ids for admins to investigate further why it's important eliminates silent failures silent failures in quote → opportunity sync by surfacing job status and errors on the quote, so sales and revops immediately know when an opportunity is out of sync and why reduces downstream finance, billing, and provisioning issues caused by mismatched opportunity products and amounts, especially for customers who rely on opportunity as a system of record for revenue workflows lowers support and admin overhead by turning common sync failures (validation rules, approval locks, lookup filters, governor limits) into clear error messages that customer admins can self resolve how it works on the quote details page, click on setup on the top right corner & click edit page to open the lightning app builder in the left hand components panel, search for the custom lwc that surfaces the quote to opportunity sync job status async job status card async job status card drag the component onto the desired region of the page, as visible below save and activate the changes on the page, to ensure it applies to all records integrations map stripe ids to netsuite payments and refunds nue’s netsuite connector now lets you pass stripe payment ids and stripe refund ids from nue into netsuite payment and refund records specifically when a payment is collected via stripe and represented as a payment application in nue, the stripe payment id can now be mapped into a field on the corresponding netsuite customer payment when a refund is issued via stripe and represented as a refund application in nue, the stripe refund id can now be mapped into a field on the corresponding netsuite refund object in netsuite this enables downstream tools like the stripe connector for netsuite to automatically reconcile deposits and bank fees against the correct payment and refund records using these ids why it matters business impact 1 finance teams can now automate bank reconciliation in netsuite by using stripe charge/payment ids and refund ids on netsuite payment and refund records, rather than manually matching stripe payouts to open items business impact 2 customers can continue to use stripe’s own netsuite payout reconciliation tooling while still using nue for invoicing and payments, because stripe can key off the ids nue now stamps onto netsuite records business impact 3 reduces errors and operational overhead in month‑end close payments and refunds coming from nue/stripe are clearly identifiable in netsuite, minimizing unapplied cash and misapplied fees during reconciliation to learn more about setting this up, see the documentation here docid\ wjolvhq otzcxrqrepj8o sync customer field updates to netsuite the nue–netsuite connector now synchronizes customer field updates from salesforce to netsuite on an ongoing basis previously, customer data was only transferred to netsuite at the time of initial customer creation — any subsequent changes to mapped fields (e g , address, payment terms, custom fields) required manual dual entry in both systems to stay in sync with this enhancement, a scheduled batch job runs every 12 hours to detect and push updated customer fields to the corresponding netsuite customer record, using both standard and custom field mappings configured in the netsuite connector why it matters eliminates dual data entry by automatically propagating customer field changes from salesforce through nue to netsuite, reducing manual work and the risk of data drift between systems keeps downstream netsuite processes accurate — netsuite now reflects the latest customer information without requiring finance teams to manually update records supports both standard and custom field mappings so any field configured in the netsuite connector configuration wizard (e g , address, payment terms, website, or custom fields) is included in the update sync bug fixes nue ai improved plugin submission experience in price builder chatbot before when users asked the price builder chatbot to generate a pricing plugin and then submitted that plugin (for example “apply 3 5% discount to the product nue platform if existing product nue on salesforce”), the plugin was actually submitted successfully, but an error message appeared just before completion this was confusing because it looked like the submission had failed, even though the plugin was created and submitted as intended what we changed we identified that the issue was related to how the plugin type was being handled during submission the plugin type is now set to a safe default (“any”), and the chatbot is no longer allowed to override this value we also updated the related documentation and tests to align with this behavior and prevent regressions lifecycle manager create quote/order api now resolves to the best matching price book entry id for dynamic bundle add‑ons use case you call the global quote/order apis (createquote, createorder) with a bundle whose add‑ons are chosen dynamically (via pricing attribute filters), and you maintain special prices for partners or segments before even when the account was a channel partner / reseller, the global apis priced the dynamic add‑on at the default list price (e g , $29 90) instead of the partner price (e g , $18 80) now when you create quotes or orders through the global methods or rest apis, dynamic bundle add‑ons automatically use the correct partner or segment price, just like static options — no manual overrides needed create quote/order api now revoles pricing attributes values from quote/order header fields use case your integration sets a tier on the quote or order header (for example, a service tier or crm tier picklist) and expects the global methods or rest apis to price products based on that choice before createquote and createorder could not reliably read those header fields, leading to “ no pricebook entry found ” errors or falling back to a default price instead of the intended tier now the global methods or rest apis read tier values directly from the request header and consistently select the matching tier price (e g , basic vs premium or 3k/6k/12k), so your integrations can safely drive pricing from header‑level fields resolve lifecycle manager and line editor compatibility with lightning web security resolved an issue where occasionally the lifecycle manager would fail to load when lightning web security (lws) was enabled, showing an indefinite loading spinner what changed both the lifecycle manager and line editor now load and function correctly when lws is enabled improved error handling for external service calls (intercom chat, ai assistant) to fail gracefully without blocking page load impact customers can enable lightning web security without losing access to the lifecycle manager or line editor no configuration changes required — the fix is included in the package update newproduct changes now carry over bundle add on's included units via the global method api resolved an issue where included units were not being taken into account when adding a newproduct change type to a change quote or order what changed when using globalchangeorderservice changeorder() with a newproduct change type to cross sell a bundle, add on order products now auto populate includedunits c from the product option's configured included quantity a new optional includedunits field on newproductaddon also allows explicit override impact bundle add ons with "allow x units free" configured now correctly receive system discounts on change orders created via the global method this unblocks programmatic subscription migration workflows where pricing accuracy on included units was silently broken rollup arr now stays accurate for large account hierarchies for customers using lifecycle manager rollup metrics in salesforce, the nightly rollupaccountmetricsbatchable job was intermittently failing with a salesforce governor limit error system queryexception aggregate query has too many rows for direct assignment, use for loop when this happened, the job still showed as “completed” but with multiple errors in apex jobs today’s rollup arr on some parent accounts was not recalculated as designed (parent + children), and instead became incorrect or stale this meant hierarchical arr views (parent + children) in lifecycle manager and related reports could not be fully trusted for affected accounts, even though quoting, ordering, billing, and renewals continued to work normally the underlying cause was that the batch class queried account hierarchies and related billing data in a way that could exceed salesforce’s aggregate row limits in larger orgs, causing the rollup job to fail partway through impact if you previously saw discrepancies where a parent’s today’s rollup arr did not match the expected parent + children total (or appeared stale), you should see those values align after the fix once the rollup batch has run multi‑year renewal quantity changes now supported across years what changed quote line editor's manage subscriptions & add additional changes flow was blocking multiple quantity updates for the same subscription, even when they were on different renewal years/dates, and could result in duplicate, non removable child renewal lines the ui change queue validation and button disable logic have been updated to be date aware for update quantity and renew with quantity update, allowing multiple changes on different effective dates while still preventing true same date duplicates impact sales reps can now process multi year renewals with different quantities per year in a single flow from the line editor, without relying on separate follow up change orders quantity changes queue and apply correctly per renewal year, child products no longer generate duplicate renewal lines, and the overall renewal configuration in lifecycle manager more reliably matches the intended multi year ramp structure renewal quote start date now correct for ramp subscriptions what changed updated the renewal quote start date logic for ramp subscriptions so that only renewal period ramp items are used when calculating the quote header subscription start date excluded previous order (expiring) ramp items and display only rows from the minimum start date calculation, aligning server side logic with how the line editor already treats these items impact renewal quotes with ramp pricing now show a correct subscription start date on the quote header, matching the dates shown in the line editor agreements and quote documents generated from these renewal quotes will now reflect the correct renewal start date standard (non ramp) renewals are unchanged and continue to behave as before line price tag “price impact” now updates when subscription term changes what changed we corrected the save path so that, whenever user saves from the quote line editor, the updated price impact for each line price tag is now persisted to rubylinepricedimensions priceimpact c the value stored in salesforce now matches the recalculated price impact shown in qle after subscription term changes, for both price tags and discount tags this ensures that downstream logic (formulas, approvals, reporting, pdfs, etc ) that depends on line price tag price impact sees the same, term adjusted value that users see in the quote line editor impact pricing data is consistent qle display and backend line price tag records stay in sync when terms change more accurate metrics any “annual list price” or list/discount calculations that use priceimpact c will now reflect the correct, current subscription term reduced manual checks sales and ops teams no longer need to manually reconcile differences between the ui and reports after changing subscription terms on quotes bundle reconfiguration now preserves existing add‑ons what’s changed we have updated the bundle reconfiguration behavior in the lifecycle manager quote and order split ui so that existing bundle children are always preserved at their contracted quantities when you reconfigure a bundle to add new add‑ons, unless you explicitly change a child’s quantity in the configurator the configurator now correctly initializes quantities by falling back from productoptionquantity → quantity → catalog default, so existing subscriptions with null productoptionquantity still retain their actual quantities existing children are recognized as existing lines (not treated as new), which prevents spurious cancel and re‑add lines from being generated for unchanged items only newly added add‑ons, or children whose quantities you explicitly modify, generate change lines on the quote impact with this fix reconfiguring an active bundle to add new add‑ons is now safe and accurate your existing add‑ons remain untouched unless you change them quotes generated from the reconfigure flow now show only the true incremental change (upsell or down sell) from what you added or modified, and the quote header’s changesummaryprice reflects just that delta instead of a large negative value from unintended cancellations add to existing quote checkout now works reliably from lifecycle manager earlier after processing a change to a subscription in lifecycle manager and choosing "add to existing quote" from the cart, the experience would loop back to lifecycle manager instead of opening the existing quote the change line was not added to the selected quote, and users did not see any error message explaining what went wrong what changed this release includes a coordinated fix across apex, lwc, and the ui component used by lifecycle manager the quote lookup now retrieves all relevant quote fields (including custom and formula fields) so that checkout can proceed without soql field errors if a checkout error does occur, lifecycle manager now surfaces a salesforce toast notification with error details instead of silently looping back, so users understand what went wrong the quote selection logic has been adjusted so that the "add to existing quote" option no longer depends on there being an open opportunity; this prevents failures when valid quotes exist without open opportunities impact users can now reliably add subscription changes from lifecycle manager into an existing quote using "add to existing quote," and be taken to the quote line editor as expected, rather than being looped back to lifecycle manager customers who previously had to create new quotes as a workaround can return to their standard process of stacking additional changes onto an existing quote, reducing quote sprawl and manual cleanup everything billing improved performance and reliability for high volume monthly usage billing schedules what changed we optimized the database path used when updating invoice information for large sets of usage records by adding an index and improving how data is written to the temporary table in performance testing, the time for the critical update statement was reduced by roughly 70% impact high volume monthly usage billing schedules now complete significantly faster and more reliably the optimized usage update step no longer risks timing out when processing large batches of records credit pool inflow/outflow filtering now correctly scopes by selected pool what changed the credits tab in lifecycle manager was not properly filtering inflow and outflow transactions when switching between credit pools in the dropdown selector the pool filter logic in the ui components (ruby ui component and ruby revenue builder sf) has been corrected impact selecting a specific credit pool (e g , "conversions" vs "data points") in the credits tab now correctly displays only the inflows and outflows that belong to that pool balances, inflows, and outflows are no longer mismatched across pools improved invoice taxstatus handling during activation what changed added support for passing taxstatus on both the invoice header and invoice items via the invoice activation api supported values are notcalculated (default), calculated , error , committed impact tax engines and custom tax workflows can now explicitly set and rely on taxstatus as the source of truth for whether tax is calculated , in error , or committed at activation time prevents downstream confusion caused by invoices remaining in notcalculated after tax was already synced and a final status was provided developer experience change orders now populate contract and carve segment fields from product what changed the change order engine now loads the product after cloning the previous order product and stamps contractliabilitysegment, contractrevenuesegment, carvesliabilitysegment, carvesrevenuesegment, and carveseligible onto both summary and detail lines — matching initial order behavior impact change orders no longer sync null segment values to salesforce if the initial order doesn't have those fields populated revenue recognition and carve allocation in sf and downstream systems like rightrev receive the correct segments without manual data fixes credit burndown products with partial term proration enabled no longer reject non integer terms from self service what changed self service pricing requests (draft orders and change orders) now include the tenant's enablecreditsproration setting in the options payload sent to the pricing engine when enableproratecreditsforpartialterm is off, the existing integer only validation still applies impact tenants with credit proration enabled can co term credit burndown products to existing subscriptions via self service apis without hitting a 500 error on non integer terms partial term pricing, activation, and sf sync all work end to end salesforce to nue order sync now remaps changereferenceorderproductid to the correct nue internal id what changed when a change order (e g , cancel) syncs from salesforce to nue via post /orders/sync, the changereferenceorderproductid field is now remapped from the salesforce orderitem id to the corresponding nue uuid — matching the existing remapping behavior for assetid, assetnumber, and changeassetid impact cancel and other change orders created in salesforce against self service originated subscriptions no longer store a mismatched sf id in changereferenceorderproductid the service uses this field to determine which original order product was referenced to cancel with the fix, it now resolves to the correct order product, which is important for downstream integrations such as rightrev