Release 2509.1

🚀 release 2509 1 is now live in sandbox 🗓️ production deployment is scheduled for january 20, 2026 this release introduces key enhancements including the ability to set signing order for e signature recipients, restrict price tag visibility by user role, and a new netsuite integration that creates distinct sales orders for each nue order platform updates include custom domain support for branded magic links the release also fixes an acv calculation bug that was affecting quotes with new products upgrade notes netsuite integration due to soap deprecation by oracle netsuite, required authentication and upgrade needed for all active and new netsuite integrations by march 1st, 2026 feature enhancements lifecycle manager set signing order for e signature recipients (preview) this feature enables sales representatives to specify the signing order for recipients when sending an order form or quote for e signature via nue’s order form e signature integration by default, all recipients are set to parallel signing (order 1), but users can configure strict sequential or mixed (parallel + sequential) workflows by assigning custom signing order numbers the system enforces the designated sequence, ensuring recipients receive e signature requests in the correct order this applies to both signers and recipients who only need to view or receive a copy the feature is available in both the user interface and api and tracks status throughout the process why it matters ensures compliance with legal or business mandated signing sequences, reducing risk of improper document execution and audit failures increases operational efficiency by automating complex approval chains and minimizing manual follow ups or errors provides flexibility to support diverse customer workflows (sequential, parallel, or mixed), meeting requirements of enterprise customers based on their business needs learn more customer use cases use case 1 a sales rep at a saas company needs both the cfo and ceo to sign an order form, but compliance requires the cfo's signature before the ceo's when sending the order for e signature, the rep assigns signing order 1 to the cfo and 2 to the ceo the system ensures the ceo only receives the request after the cfo has signed this eliminates manual monitoring and guarantees the company’s signature policy is followed use case 2 a procurement manager regularly sends contracts to multiple department heads who can sign independently by setting all recipients to signing order 1, the system routes the e signature requests in parallel, allowing all parties to sign at their convenience and accelerating deal closure use case 3 a legal team adds an additional recipient to receive a copy of the signed agreement for records the recipient is assigned a signing order after the primary signers, ensuring they only get the finalized, fully executed document, supporting compliance and internal controls for more details, please read docid\ i2uoxjkirteiel rez4ua ability to restrict price tags from being viewed by users this release introduces granular permission controls in nue lifecycle manager, that allow system administrators to prevent sales reps from viewing price tags and discount tags in the quote and order line editors a new custom permission, view price or discount tags view price or discount tags , has been added to the https //docs nue io/nue on salesforce permission sets#nue permissions framework admins can now configure permission sets so that only specific roles (e g , admins, deal desk) can view, add, edit, or delete price and discount tags, while sales reps can be limited to using only the discretionary discount field for special pricing this addresses critical compliance and business process needs by ensuring that complex pricing structures remain accessible only to authorized users why it matters prevents unauthorized access to sensitive pricing information, supporting compliance and customer specific security requirements enables differentiated workflows for sales reps, managers, and deal desk, improving operational efficiency and reducing risk delivers a seamless transition for existing customers no data migration or manual permission updates are required; legacy users retain their access learn more customer use cases use case 1 an enterprise customer, requires that sales reps should not be able to view any price tags, relying instead on the discretionary discount field for all special pricing with this enhancement, their system admins can configure the sales rep permission set with all price/discount tag permissions disabled as a result, reps would no longer see the price tag icon in the line editor, ensuring sensitive pricing structures remained hidden while still allowing reps to offer custom discounts via the approved field use case 2 a revops team at a saas company wants to allow only deal desk users to manage price and discount tags, while sales managers can view but not modify them, and sales reps cannot see them at all using the new permissions, the admin assigns appropriate permission sets to each group ensuring only approved users can see or manage pricing adjustments, reducing the risk of errors and unauthorized pricing changes how it works view price or discount tags permission is added to nue custom permissions when this permission (or add/edit/delete) is active, the price tag icon/button appears in the quote and order line editors if a user has none of the tag permissions, the price tag icon is hidden and price tags are inaccessible ui updates are real time changes to a user’s permissions take effect on next login/refresh backward compatibility is maintained users with add/edit/delete tag permissions prior to this change automatically retain access, even if “view” is not explicitly set for more details on price tag permission click https //docs nue io/nue on salesforce permission sets#nue permissions integrations launching nue lifecycle manager (cpq) and netsuite integration for sales order sync this new netsuite integration ensures that every activated nue order created through nue lifecycle manager (cpq) results in exactly one netsuite sales order (or return authorization for negative changes) instead of appending change and renewal lines onto an existing sales order, each new, change, and renewal order now creates its own distinct netsuite transaction, with a shared original contract identifier for traceability it is designed specifically for customers who use nue lifecycle manager (cpq) with netsuite as their downstream system of record, but who are not relying on nue billing for invoicing the result is a predictable, auditable, and finance‑friendly order sync pattern that aligns with how netsuite customers expect to manage sales orders and revenue arrangements why it matters finance teams get a clean, audit‑ready trail each nue order maps to exactly one netsuite sales order (or return authorization), eliminating ambiguity about which amendments belong to which contract and simplifying sox and external audit reviews order reconciliation and reporting become dramatically simpler because no netsuite sales order is ever updated or reused once created under this mode, accountants can rely on standard netsuite reporting and arm flows without reverse‑engineering complex “living” orders with multiple appended changes nue lifecycle manager (cpq) customers who do not use nue billing can still leverage a robust, productized integration with netsuite for further details, please visit the following documentation coming soon netsuite soap connector deprecatation action required netsuite integration rest and oauth 2 0 connector & required re‑authentication summary all netsuite integrations using the soap connector are at risk of disruption due to oracle netsuite’s deprecation of soap web services and tray’s corresponding deprecation of the netsuite soap connector we have migrated to a new netsuite rest connector (oauth 2 0) to ensure continued reliability and improved security what’s changed authentication has been upgraded to use the netsuite rest connector with oauth 2 0 , ensuring continued access to the netsuite integration and strengthening authentication security soap based connector steps have been replaced with rest based operations where soap batch operations were previously used, workflows have been updated to use looped single record rest calls existing workflows have been validated to continue working as expected once customers complete reauthentication and update their connector configuration with the new rest credentials and restlet endpoint reauthentication required all customers with an active netsuite integration must reauthenticate using the new netsuite rest connector (oauth 2 0) connector configuration update required as part of this change, customers must create an oauth 2 0 integration record in netsuite (with the required rest scopes) deploy/update the nue restlet from the nue connector bundle enter the new client id, client secret, and restlet url into the netsuite integration configuration in nue/tray post migration validation recommended customers should validate end to end flows (product, order, invoice, and payment syncs) after migration to confirm that mappings and downstream posting behave as expected customer communication & deadline we have sent a customer email titled “action required netsuite integration – soap deprecation & oauth 2 0 upgrade” outlining the exact steps required to update the integration (including netsuite ui steps and nue configuration changes) this update requires timely attention from all customers currently using a netsuite integration that was configured with the soap connector cut off date all netsuite customers must complete the migration to the rest connector by march 1, 2026 to avoid any risk of integration failure or disruption as oracle and tray deprecate soap based endpoints platform custom domain for magic links this feature enables nue customers to configure and use their own branded domains (e g , docs customer com) for all customer facing magic links—such as invoices, quotes, and orders—instead of the default nue domain (app nue com) the system provides a self service ui and api for domain registration, dns validation, and fully automated ssl certificate management if a custom domain becomes unavailable or unverified, all links automatically revert to the default domain to ensure uninterrupted access why it matters delivers trusted, branded communications enterprises can present a seamless, branded experience in portals, boosting trust, recognition, and conversion rates enables enterprise compliance and security meets strict it/security policies for customer communications, including requirements to avoid using third party domains learn more use case 1 a global saas enterprise wants every invoice, quote, and order sent to customers to appear under its own domain (e g , invoices acme com) instead of nue’s generic domain the admin configures a custom domain in nue, receives dns setup instructions, and, after dns and ssl validation, all future magic links automatically use the branded domain when end customers click invoice links, they see the company’s trusted, branded domain, which increases confidence and engagement use case 2 a compliance focused organization requires all customer facing documents to avoid third party branding for regulatory reasons by configuring their own domain, they ensure every link sent to customers meets internal and external compliance needs, while it can monitor domain and ssl health from within nue for more details, please read docid\ nhpwxylrn3kgpquxqxalb bug fixes lifecycle manager corrected annual contract value (acv) calculation using default plugin for quotes with new products with this fix, the acv is now correctly calculated for all quotes, including those with new product additions the ordermetricsextension c acv c ordermetricsextension c acv c field will reflect the accurate value, ensuring that the quote’s acv is reflected correctly this resolves issues with approval rules, reporting, and downstream processes that rely on accurate acv calculations no customer action is required; the fix is applied automatically