Release 2507.1 - 11/06/2025

🚀 release 2507 1 is now live in sandbox 🗓️ production deployment is scheduled for november 6, 2025 this release introduces enhanced customer management features including a redesigned customers list view with unified nue salesforce records, a customer chatbot for quick actions, and the ability to set default payment methods at the account level new integrations include a scheduled batch mode for netsuite transaction syncing to handle high volume processing while managing api rate limits, and template builder improvements with collapse/expand controls and manual save options critical bug fixes address product search functionality in credit memo creation and improve customer search performance for organizations with large customer databases feature enhancements lifecycle manager view list of customers with customer chatbot and launch in salesforce actions please ensure the integration user has access to all fields on the account object ​​for detailed steps, please refer to nue on salesforce setup and configuration guide we’ve redesigned the customers list in nue app (nue > revenue manager > customers > list view) to give revops a single, powerful view of all customer accounts — across both nue and salesforce unified records view customers created in either nue or salesforce in one place smart sorting customers are listed by customer since (newest first) to help you prioritize recent accounts users can create their own sorting criteria with up to 3 sort fields quick contact info the contact column now shows the order primary contact ’s email for easy outreach contextual actions customer chatbot is available for customers with a not null “customer since” date this will launch the customer chatbot docid\ rua3gafej p9h4wdpr2l2 for customers, where users can query and update customer information, query for subscriptions, assets and entitlements and make any mid term changes such as renewals, co terming, price adjustments, etc launch in salesforce appears when the customer record also exists in salesforce salesforce connection status the transaction hub icon indicates salesforce connection status flexible views configure columns — including custom fields synced via fields exposed to nue — and reset layouts anytime efficient browsing use search , filters , and tabs for business , consumer , or all customers to find what you need fast, and click refresh to pull the latest data why it matters revops gains a single system of action for customer visibility and next steps via ai, ensuring crm alignment the updated customer list with customer chatbot and salesforce launch learn more search and filter efficiently quickly find customers across the business , consumer , and all tabs use filters like customer since , industry , or any custom column to narrow your target list in seconds customize and verify list layouts tailor your customer list by adding salesforce synced fields , reviewing data for accuracy, and resetting layouts to system defaults whenever needed stay in sync with salesforce click refresh action icon to pull the latest updates from salesforce — for example, when an industry field changes from finance to technology act on customers instantly launch the chatbot for active customers (those with a customer since date) or open the corresponding salesforce record directly when available flexible sync options work seamlessly with nue only customers , salesforce only accounts , or both , depending on your salesforce integration settings and filters (e g , created date ≥ today − 30 days ) end to end creation and visibility create customers through the self service api and see real time status updates the chatbot remains disabled until customer since is populated, and contacts sync automatically once they’re used in an active create order flow everything billing manage default payment method for account this feature enables finance users to designate a single default payment method at the account level within the lifecycle manager this default is automatically used to pay invoices for the account unless a subscription level default payment method is set users can set, change, or identify the default payment method via a clear, permission controlled ui and api, ensuring only one method is marked as default at a time the system provides visual cues (heart icon for default, lightning icon for autocharge), atomic backend updates, and immediate ui refresh why it matters improves user experience for finance and operations teams, who can now easily manage and visualize default payment methods from a single place learn more customer use case use case 1 as a finance administrator for a saas company, alex frequently onboards new customers with multiple subscriptions by setting a default payment method at the account level, alex ensures that all new invoices are automatically paid unless a specific subscription level override is provided this reduces manual follow up for missed or delayed payments how it works only one payment method can be set as the default for an account at any time setting a new default automatically unsets the previous one users can set or change the default via the lifecycle manager ui (heart icon action) or patch api endpoint (/accounts/{accountid}/default payment method) dependencies and limitations requires payment methods module enabled in lifecycle manager only one default per account is allowed edge cases such as disabling a payment method, require manual intervention template builder enhancements the template builder now includes two usability upgrades designed to improve control and scalability as templates grow in complexity per‑component collapse/expand controls for the settings panel, enabling users to focus on relevant options and reduce on‑screen clutter an optional manual save mode (in addition to auto‑save), giving users deliberate control over when changes are persisted why it matters simplifies navigation and configuration as the number of settings increases, reducing cognitive load improves accuracy and confidence by preventing unintended saves and supporting intentional review before committing changes enhances management of complex templates, making it easier to organize, adjust, and maintain configurations over time learn more dependencies and limitations the expand/collapse state is not persisted across sessions or users—if a user leaves and returns, all settings reset to default (first expanded, others collapsed) auto‑save mode is enabled by default for any new template, and the save mode (auto vs manual) is a template‑level setting—changes to this setting apply only to the current template developer expericence propagate default payment methods for auto charge enable consistent auto charge behavior by automatically updating customer payment methods in self service api when a payment method is provided on the order and autochargeenabled is set to true, the system now assigns that method to the customer’s `paymentmethodid for future auto charges when a payment method is specified at the order product level, it continues to apply only at the subscription level, with no updates to the customer account this enhancement unifies auto charge handling across channels, simplifies setup during activation, and reduces manual billing configuration, improving both consistency and reliability integrations batch enable scheduled netsuite transaction sync this release introduces a new scheduled batch mode for the netsuite connector in nue, designed to streamline the processing of high volume transactions when enabled via a checkbox in the netsuite integration configuration, all relevant transactions (such as order activations and invoice activations) are initially parked in the transaction hub with a "not transferred" status every 10 minutes, a scheduled job automatically processes these transactions in batch, leveraging existing tray connector logic to create corresponding records in netsuite this mode helps manage api rate limits, increases reliability, and provides clear error handling and audit trails why it matters reduces risk of netsuite api throttling by batching transactions and enforcing rate limits (5 api calls per minute) increases reliability for customers processing large volumes of orders and invoices, ensuring transactions are not lost or partially transferred enhances operational transparency and auditability, with clear status tracking and error handling in transaction hub learn more use case 1 high volume invoice syncing a saas company processes thousands of invoices at month end previously, syncing these to netsuite would often fail due to api rate limits, leaving finance teams with incomplete records and manual re work with batch mode enabled, invoices are queued and processed in scheduled intervals, ensuring all invoices sync without hitting netsuite limits errors are clearly logged in transaction hub, so any failures can be quickly identified and retried use case 2 large order import and catch u p during a major data migration, a customer imports thousands of historical orders without batch mode, simultaneous sync attempts would fail or queue up indefinitely now, the batch processor picks up orders every 10 minutes, syncs them in manageable chunks, and logs any errors with codes/descriptions—enabling efficient, error resilient migration use case 3 automated financial operations monitoring a finance admin wants immediate visibility into integration health with enhanced error handling, any failed transaction (such as a credit memo sync) posts a clear, actionable entry in transaction hub and, if configured, sends an email notification to the admin and support team for rapid triage bug fixes everything billing product search functionality restored in standalone credit memo creation previously, when users attempted to search for a product by name or product code while creating a standalone credit memo, the search did not filter results as expected instead, all products were displayed regardless of the search input with this fix, product search during standalone credit memo creation now works as intended users can filter products by entering a product name or code and pressing either the 'enter' key or the 'arrow' icon improved customer search performance in credit memo creation previously, when users attempted to create a new credit memo in the nue platform, the interface would attempt to load and display all customers synced from salesforce this became problematic after a large scale sync of over 500,000 customer accounts, resulting in significant performance issues and making it difficult or impossible for users to efficiently select a customer with this fix, the create new credit memo ui now prompts users to search for a specific customer when entering customer information, rather than attempting to display all customers at once this change dramatically improves performance and usability for organizations with large customer lists, ensuring a smoother and more responsive experience when creating or editing credit memos