DRAFT: Release 2604

sandbox deployment is scheduled for may 11, 2026 production deployment is scheduled for may 14, 2026 summary of the release upgrade notes in case we need it feature enhancements nue ai lifecycle manager everything billing enable salesforce reporting on credit balances and consumption history nue now syncs credit, accountcreditpool, and creditflow records from nue to salesforce as nue managed custom objects ( ruby credit c , ruby accountcreditpool c , ruby creditflow c ) sales reps can build salesforce reports and dashboards on live credit data alongside their existing account, opportunity, and subscription information revops managers control sync from a single toggle in settings → credits → synchronize credit objects to salesforce why it matters equip sales reps with current credit balance and consumption context inside salesforce, without switching into lifecycle manager > credits enable native salesforce reports and dashboards covering credit balances, consumption trends, expiry timelines, and committed burndown progress give revops a single setting to enable sync where reporting is needed and disable it to manage salesforce storage when creditflow volume is high learn more customer use case use case 1 a sales rep at a usage based saas company is preparing for a renewal conversation with a key enterprise customer from the customer's salesforce account record, they open related lists of ruby accountcreditpool c and ruby creditflow c and immediately see the current pool balance plus recent consumption transactions the rep enters the call grounded in the customer's actual credit position, without context switching into nue or pulling in revops use case 2 an account executive managing a portfolio of accounts with committed credits wants to identify expiry risk before quarterly business reviews using a salesforce report on ruby credit c filtered and sorted by end date , they surface every grant expiring in the next 90 days they check the committed field and consumed committed credits to see which accounts are tracking ahead or behind on burndown, and use that signal to anchor expansion and renewal conversations use case 3 a revops manager rolling out credit reporting to the sales organization wants to control which credit data flows into salesforce as new committed credit deals ramp up from settings → credits , they enable the synchronize credit objects to salesforce toggle to begin populating reports if high frequency usage consumption later drives creditflow volume that would strain salesforce storage, they disable the toggle without losing existing records, preserving control without engineering involvement how it works a revops manager enables sync from settings → credits → synchronize credit objects to salesforce (disabled by default) when enabled, nue writes new and updated credit, accountcreditpool, and creditflow records to mirrored nue managed custom objects in salesforce ruby credit c , ruby accountcreditpool c , and ruby creditflow c records are linked to the salesforce account via standard lookups, and credit and creditflow records reference their parent accountcreditpool the synced objects are read only in salesforce dependencies and limitations the toggle is disabled by default; sync only begins after a revops manager enables it the synced objects are managed by nue and should be treated as read only in salesforce disabling the toggle stops further writes but does not remove existing synced records view and export a log of consumption threshold alert events the consumption threshold alerts setting has been enhanced to include an alert activity log, showing every threshold breach event — with alert configuration, credit pool, customer, threshold percentage, fire time, email delivery status, and webhook delivery status now, revops managers can filter the log and download it as csv from settings → credits → consumption threshold alerts why it matters track alert activity end to end — confirm which alerts fired, when, and whether email and webhook deliveries succeeded guide customer outreach strategies by exporting a filtered list of accounts that crossed thresholds, allowing evaluation of alert campaigns and outreach strategies optimize webhook driven internal workflows by reconciling fired events against downstream automations and catching delivery gaps before they affect customer conversations related resources see consumption threshold alerts docid\ akbs4c3 1z2qhiuypu127 for detailed information about this feature and how to enable and configure alerts developer experience integrations bug fixes nue ai lifecycle manager multi currency bundle orders no longer fail with a price book mismatch for create quote api what was happening before? when sellers created new business orders for bundles in multi currency catalogs — where each child product has a separate price record per currency — the order failed validation regardless of the currency they ordered in tenants using the standard one product option per currency catalog pattern hit this every time, blocking new business motions on the affected bundles entirely what we changed bundle expansion now picks the matching product option for the order's currency — and, when more than one option shares that currency, the one whose pricing attributes (such as customer channel) match the order single currency tenants and bundles with a single option per child are unchanged impact of the fix sellers can quote and place new business orders for bundles in any supported currency — including bundles that mix pricing attributes like customer channel within a single currency — without needing data quality cleanups in the catalog or workarounds in the order flow viewing subscriptions from an order in lifecycle manager now returns the order's subscriptions what was happening before? in lifecycle manager on salesforce , account managers reviewing a customer's orders tab and clicking "view subscriptions" on an individual order saw an empty subscriptions tab — even when the order clearly had active subscriptions tied to it navigating directly to the subscriptions tab still showed the same data correctly, so the gap only appeared on the orders → subscriptions path what we changed clicking "view subscriptions" on an order now lists the subscriptions tied to that order navigation between the orders and subscriptions tabs is consistent, and the same subscriptions appear in both places impact of the fix revops and account teams working in lifecycle manager can move from a specific order to its subscriptions in a single click, restoring the routine workflow used to investigate provisioning, renewals, and customer questions everything billing developer experience integrations microsoft dynamics and telenor are now valid external systems for transaction hub events what was happening before? when tenants used the tray framework to push integration events into nue's transaction hub for microsoft dynamics (and telenor), the calls were rejected with an error even though those external systems were already in active use for the tenant workflows that previously synced cleanly stopped completing, and downstream invoice and customer records couldn't be marked as transferred what we changed nue now recognizes microsoft dynamics and telenor as valid external systems when recording transaction hub events calls referencing these external systems succeed and the corresponding transaction hub records are created as expected impact of the fix tray driven flows for microsoft dynamics and telenor integrations can resume writing transaction hub events without operator intervention, restoring the audit trail that downstream invoice and customer sync depend on