Release 2601.1

🚀 release 2601 1 is live in sandbox 🗓️ production deployment is scheduled for february 18, 2026 this release enhances salesforce files integration by automatically attaching quote pdfs with version control, introduces subscription renewal price uplift automation through apex global methods, and fixes cancellation quote date calculations for accurate financial reporting new e signature features include the ability to cancel docusign envelopes, correct recipient information, and prevent duplicate signature requests while tracking signing status in salesforce the update also enables programmatic cross selling through change orders across all api surfaces and adds native sphere integration for real time multi jurisdiction tax calculations upgrade notes we’ve introduced a behavior change to the generated quote pdf (order form) previously, the generated pdf was stored as an attachment (salesforce object attachment ) going forward, it will be stored as a file (salesforce object contentdocument ) this change will apply to all quotes if you have flows or integrations referencing the attachment object, you must update them to use contentdocument otherwise, your existing flows or soql queries may not function as intended feature enhancements lifecycle manager attach quote pdf to quote as a file this change will apply to all quotes if you have flows or integrations referencing the attachment object, you must update them to use contentdocument otherwise, your existing flows or soql queries may not function as intended sales reps can now generate quote pdfs that are automatically attached to the quote record as salesforce files instead of legacy attachments this modern approach leverages salesforce files’ built in versioning if the same template is used, a new version is created; if a different template is selected, a new file is generated the file is named “quote pdf for {quote name} ({template name})” for clarity admins have precise control over whether generated pdfs are attached to the quote, the opportunity, or both, based on system settings this ensures a streamlined, auditable, and integrated quote document workflow that supports seamless e signature processes and robust compliance why it matters ensures compliance and auditability by maintaining a clear version history and a single source of truth for each quote pdf reduces manual document management, eliminates file duplication, and enables seamless e signature workflows increases operational efficiency and flexibility for sales, legal, and admin teams by automating attachment logic based on business needs learn more customer use cases use case 1 after negotiating with a customer, a sales rep updates the quote and generates a new pdf because the template hasn’t changed, the system creates a new version of the existing file, preserving the document’s history for legal and compliance review use case 2 an admin enables settings to attach generated pdfs to both the quote and the associated opportunity when a sales rep generates a quote pdf, it is instantly available to both sales and finance teams, supporting fast approvals and downstream processes use case 3 during an e signature workflow, the latest attached quote pdf is automatically selected and sent for signature the resulting signed pdf is uploaded as a new version, ensuring all parties have access to the most current, fully executed document apply subscription level price uplift on renewal via global methods nue now supports applying price adjustments at the time of subscription renewal through the apex global methods sales teams can automate renewal workflows that include price uplifts in a single operation — no manual quote edits or multi step processes required whether applying a standard annual escalation across all customers or negotiating custom pricing for strategic accounts, sales ops teams can define the exact uplift method, scope, and timing to match their renewal pricing strategy adjust price change now has the ability to apply on top of configured docid\ kfvznlsd7qf saxljp il why it matters eliminates manual effort when applying annual price increases at renewal instead of reps editing each renewal quote individually, uplift rules are applied automatically enabling sales ops teams to scale renewal operations across their entire customer base supports complex multi year renewal agreements with escalating pricing each year of the contract can carry a different uplift percentage, ensuring the pricing schedule reflects what was negotiated without requiring separate change orders for each period protects and scales subscription level uplift logic the uplift can be applied directly on top of the prior term’s net sales price and supports subscription specific rates, aligning with how some customers want to carry forward net sales price into the renewal term & manage annual uplifts per subscription rather than a single global percentage learn more customer use cases use case 1 use case 1 standard annual uplift across all bundle products a saas company enforces a standard 5% annual price uplift on all subscription renewals as part of their pricing policy when a subscription reaches the end of its term, sales ops triggers the renewal workflow which automatically applies the 5% increase across all products in the customer's bundle including the parent subscription and all add ons a draft order is generated for the rep to review before activation, removing the need for reps to manually calculate and adjust pricing on each renewal quote this ensures pricing consistency across the entire customer base while freeing reps to focus on customer conversations rather than administrative tasks use case 2 use case 2 multi year renewal with escalating annual pricing a mid market customer negotiates a 3 year renewal agreement with escalating annual pricing 3% uplift in year 1, 5% in year 2, and 8% in year 3 rather than creating separate renewal workflows for each year or manually tracking escalation schedules, sales ops configures all three uplift tiers within a single renewal operation each year is assigned its own pricing adjustment with a distinct start date, ensuring the contract accurately reflects the agreed upon escalation schedule from day one this is particularly valuable for companies that offer long term contracts with built in annual escalators tied to other benchmarks use case 3 use case 3 selective uplift parent product only, add ons stay flat a company renews a product bundle but only wants to increase pricing on the core platform subscription, keeping add on products at their current rate for the renewal term this is common when add on pricing is contractually locked or when the uplift policy only applies to the primary product the renewal workflow allows scoping the uplift to the parent product only, without cascading the increase to bundle children this gives sales ops granular control over which products are affected by price changes, ensuring contractual commitments on add on pricing are honored while still capturing the planned uplift on the core subscription see https //docs nue io/apex global methods and services#apply a subscription level price uplift on renewal for more details on use cases & examples improved header start and end date calculation for cancellation quotes and orders this release corrects how the quote/order header start date and end date are determined when processing subscription cancellations in lifecycle manager previously, cancellation only quotes set the header start date and end date to the same value (the cancellation date) to designate length of the active subscription term which caused issues with downstream automations, acv calculations, and the cancellation period determination used by finance teams with this update, nue now applies distinct logic depending on whether a quote contains only cancellation lines or a mix of cancellations and new/change products why it matters accurate header dates on cancellation quotes are essential for downstream financial operations when the header start and end dates were identical, it broke automations that used these dates to calculate the cancellation period, led to incorrect acv values, and created confusion in billing and revenue recognition workflows this fix restores predictable, finance friendly behavior for organizations managing subscription cancellations at scale makes complex change orders easier and safer for sales teams learn more customer use cases use case 1 a sales rep at a saas company needs to cancel a customer’s 12‑month subscription mid‑term because the customer is churning the original subscription runs from 12/03/2025 12/03/2025 to 12/02/2026 12/02/2026 , and the rep sets the cancellation effective date to 01/05/2026 01/05/2026 before this fix, the quote header start date and end date both snapped to 01/05/2026, making it look like the entire transaction only covered one day finance could no longer infer the true cancellation window from the header, and their cancellation acv logic broke after this release, the rep still selects 01/05/2026 as the cancel date, but the cancellation‑only quote now shows header dates that cover the full cancellation period (for example, 12/03/2025 – 12/02/2026), and the customer’s downstream logic correctly interprets the term being cancelled use case 2 cancel and replace (rip & replace) let's say the same subscription as above was cancelled on 01/05/2026 and adds a new replacement product co termed to 10/31/2026 the header start date will be 01/05/2026 (the earliest line start) and the end date will be 10/31/2026 (the new product's end date, ignoring the cancel line) this ensures the replacement subscription drives the quote's header dates use case 3 a customer success manager wants to back‑date a cancellation to a specific past date or schedule it for a future date while still representing the full subscription term on the order they work with a subscription that runs from 12/03/2025 12/03/2025 to 12/02/2026 12/02/2026 and create a change order that cancels the subscription effective 03/01/2026, either retroactively or prospectively with the updated logic, the header start and end dates remain a range representing the cancellation window instead of collapsing to the single effective date, so the csm can adjust the effective cancellation date as needed without breaking analytics or integrations that read header dates disable bundle reconfiguration on line editor this release introduces a system level setting, disable bundle reconfiguration on the line editor that prevents sales reps from removing individual child products from configured bundles directly in the quote line editor (qle) when the setting is enabled, bundle composition must be changed through the bundle configurator, ensuring product group min/max rules remain enforced after configuration why it matters prevent invalid bundle configurations that break product group min/max rules protect compliance or coverage critical components in bundles reduce downstream errors in order processing, billing, and fulfillment learn more customer use cases use case 1 a revops admin at a saas company configures an “enterprise suite” bundle with an “add on modules” group that requires at least two modules to be selected a sales rep builds a quote, configures the bundle with three add on modules in the configurator, and moves into the quote line editor without this feature, the rep can delete two of those module lines in qle, leaving only one and silently violating the minimum requirement—yet the quote still saves and proceeds with disable bundle reconfiguration on the line editor disable bundle reconfiguration on the line editor turned on, the rep no longer sees an active remove action on those child lines if they try to adjust the composition, they are guided back into the bundle configurator, where the min/max rules are enforced and the bundle stays valid use case 2 a growing revenue team wants tighter control over bundle definitions while still allowing flexible pricing on deals the revops admin enables disable bundle reconfiguration on the line editor disable bundle reconfiguration on the line editor so that child products and quantities defined in the bundle configurator remain locked from removal in qle sales reps continue to adjust quantities (when allowed), discounts, and net prices on those bundle child lines directly in the grid, but any attempt to remove a component—or zero out its effective quantity—must go back through the configurator this keeps the structural integrity of bundles intact while preserving day to day pricing flexibility on the quote how it works admins turn on disable bundle reconfiguration on the line editor disable bundle reconfiguration on the line editor in nue app → settings → line editor when enabled, the system setting disablebundlereconfigonle disablebundlereconfigonle is set to true and applies org wide when the setting is enabled and qle determines a line is a bundle child (it has a parent bundle relationship), the line level “remove/delete” action is disabled or hidden for that line; the rep can no longer delete it directly from the grid the restriction covers any action that would remove a bundle child line or effectively reduce its quantity to zero; to change composition, the rep uses the existing bundle reconfigure icon on the parent line to reopen the configurator where product group min/max rules are enforced the setting does not block removing an entire bundle reps can still delete the parent bundle line, which cascades removal of all its children, and they can still adjust quantities and pricing on bundle children when permitted by other settings export/download order form as word document (preview) nue supports the conversion of an order form pdf file to a word type document this feature is limited and not available by default in the tenant if you would like to try or enable this feature, please contact the nue support team this feature enables sales reps to export or download any order form as a microsoft word ( docx) file directly from the nue platform this allows users to obtain an editable version of the order form—using the same template and latest data as the pdf—supporting use cases such as legal review, contract negotiation, redlining, and offline collaboration access to this feature is controlled by both a system setting and a custom user permission, ensuring only authorized users can generate word documents each export action is logged in the document’s audit history for traceability why it matters empowers sales and legal teams to negotiate, redline, and revise order forms in word, the industry standard editable format, accelerating deal cycles and reducing friction meets enterprise customer requirements for compliance, procurement, and regulatory review processes that mandate docx documents before e signature enhances professionalism and customer experience by delivering branded, consistent, and flexible contract documents—while maintaining auditability and permission controls learn more customer use cases use case 1 a sales rep is finalizing a large contract with a customer whose procurement team requires contract review in word format before signature the rep clicks the “download as word” icon on the order form, retrieves the docx file, and sends it to the customer the customer returns a redlined version, which is reviewed and incorporated in nue, ensuring the negotiation process is seamless and tracked use case 2 a legal team needs to archive all executed order forms in editable format for compliance they use the feature to bulk export order forms as word documents, store them in their document management system, and maintain a full audit trail of who exported each file use case 3 a partner manager wants to share a draft order form with an external reseller for review and feedback by downloading the order form as a word document, they enable the partner to make comments and edits offline, returning the file for finalization before sending for e signature for more info about this feature, please refer to docid\ nixygybcel cmwltnykbk enable canceling the e sign process (preview) this feature allows sales representatives to void or cancel an in progress e signature (docusign envelope) request directly from the quote or order form record in the nue ui or salesforce this action is available for any envelope that is not fully signed (i e , in "sent" or "delivered" status) upon cancellation, users are prompted to provide a reason, recipients are notified, the document status is updated to "canceled," and the action is logged in the signing history for audit and compliance purposes this aligns nue with best practices of modern cpq and billing systems, increasing control and flexibility throughout the sales process why it matters reduces operational and legal risk by allowing correction of mistakes or withdrawal of documents before they become binding improves sales efficiency by enabling fast retraction and re initiation of the e signature process without manual intervention enhances customer and compliance experience by supporting auditability, transparency, and rapid response to change requests or cancellations learn more customer use cases use case 1 a sales rep sends an order form via e signature to a customer, but soon realizes the pricing information was incorrect before the customer signs, the rep uses the "cancel" action to void the envelope, enters a reason, and the customer is notified that the process is canceled the correct order form is then updated, and a new e signature request is sent, ensuring only accurate documents reach the customer use case 2 a customer reviews the agreement sent for signature and requests a change to a contract term the sales rep cancels the current e signature envelope, logs the reason, and updates the contract the updated document is then resent for e signature, keeping the process transparent and efficient for all parties use case 3 a deal is called off after the e sign process has started the sales rep cancels the active envelope, providing a cancellation reason recipients receive a notification, and the voided status is tracked in the quote’s signing history, ensuring compliance and a clear audit trail for more details, please refer to docid\ i2uoxjkirteiel rez4ua correct recipient information for sent order forms (preview) sales reps can now correct recipient information—including name, email address, role, and signing order—for order forms that have already been sent for e signature via docusign, as long as the envelope is not yet completed this allows mistakes or last minute changes to be addressed without voiding and resending the envelope, streamlining the e signature workflow and reducing delays why it matters reduces friction sales reps can quickly fix errors (like typos or outdated info) in recipient details without needing to restart the e signature process, speeding up deal closure improves data accuracy ensures that legal documents are always sent to the correct individuals, minimizing compliance risks and costly mistakes minimizes operational overhead avoids the need to void, recreate, and resend envelopes—saving time and reducing the administrative burden on sales and revops teams learn more customer use cases use case 1 a sales rep sends an order form for signature and later realizes the customer's email address had a typo instead of voiding the envelope and starting over, the rep uses the correction feature to update the email address, instantly notifying the correct recipient and keeping the deal on track use case 2 mid process, a recipient’s legal name changes due to a company merger the sales rep updates the recipient’s name and role in the envelope, keeping the signing process compliant and up to date—without disruption use case 3 a change in company policy requires a manager to sign before an employee after sending the envelope, the rep updates the signing order so the manager receives and signs first, ensuring the workflow matches new requirements for more details, please read docid\ i2uoxjkirteiel rez4ua track document signing history and envelope status in salesforce (preview) this feature introduces real time tracking of docusign envelope status and recipient signing history directly within salesforce opportunities and quotes sales reps, managers, and revops users can now see the complete lifecycle and audit trail of documents sent for e signature—all without leaving salesforce or relying on manual updates why it matters accelerates time to close by enabling proactive follow up based on real time signing status, reducing cycle delays caused by blind spots in the process reduces context switching and operational overhead, as users no longer need to check docusign separately or request status from admins strengthens compliance and forecasting by maintaining a detailed, tamper evident audit trail of every signing action, supporting dispute resolution and regulatory reviews learn more customer use cases use case 1 a sales rep sends a quote for e signature and needs to know when each stakeholder signs with this feature, the rep sees real time status and timestamps for every recipient directly on the quote record, enabling timely follow ups and avoiding lost deals due to signature delays use case 2 a revops analyst responds to a customer dispute about contract terms by reviewing the detailed signing history—including who signed, when, and any corrections or voids—the analyst quickly resolves the issue with a court admissible audit trail for more info about this feature, please read docid\ i2uoxjkirteiel rez4ua prevent sending quote for e signature multiple times (preview) this update introduces a critical compliance safeguard for order form e signature workflows sales reps can no longer send the same quote for e signature more than once while another signing request is active the system now enforces a strict rule—both in the ui and api—to ensure that only one active e signature request can exist per quote at any given time why it matters prevents costly errors and contract confusion by blocking duplicate sends, the feature eliminates the risk of customers or internal signers receiving multiple signature requests for the same quote, which could cause confusion, conflicting records, or even legal disputes reduces operational and compliance risk ensuring only one active e signature process per quote simplifies audit trails, supports regulatory compliance, and protects your organization from accidental contract execution errors streamlines sales and revops workflows automated checks (in both ui and api workflows) reduce manual oversight, prevent user mistakes, and allow sales teams to focus on closing deals—not on chasing down duplicate envelopes or voiding errors learn more customer use cases use case 1 after a sales rep sends a quote for e signature to a customer, they attempt to send the same quote again (perhaps after a minor detail is changed, or by mistake) the system immediately blocks the second attempt and shows a message “this quote already has an active e signature request please cancel or complete the existing signing process before sending a new one ” this prevents the customer from receiving multiple signature requests for the same deal, maintaining a clean, professional experience and reducing back and forth use case 2 a revops manager is reviewing contracts and notices that, due to a previous system, multiple envelopes were sometimes sent for the same quote, causing confusion during audits with this update, the manager sees that only one envelope can be out for signature per quote, making contract status reporting and compliance checks much more reliable use case 3 a developer integrates the nue api to automate quote workflows if their automation tries to send a quote for e signature that is already in process, the api responds with an error, indicating the duplicate attempt was blocked the developer can then build logic to alert the user or prompt for a cancellation before retrying for more details, please refer to docid\ i2uoxjkirteiel rez4ua upload a new version of the order form to quote (preview) this feature allows sales reps to upload a pdf file as a new version of the existing order form pdf on a quote they can upload a new pdf (for example, a scanned wet‑signed copy), optionally add notes, and choose to mark the file as completed behind the scenes, nue creates a new salesforce contentversion for the same contentdocument so all versions of the order form stay linked to the same quote file why it matters supports offline and customer‑owned signature workflows by letting reps bring back wet‑signed or externally e‑signed pdfs into the standard quote document lifecycle in salesforce/nue, without forcing a specific e‑signature provider reduces risk and audit gaps by storing all versions (draft, sent, signed) as versions of a single salesforce file with signing history and notes, instead of scattered attachments or ad‑hoc uploads improves revops and legal efficiency frontline reps can finalize quotes end‑to‑end (generate, send offline, upload signed copy, mark as completed) without admin help, while admins still control who can upload signed documents and when via system settings and custom permissions learn more customer use cases use case 1 a sales rep generates an order form from a quote and emails it as a pdf to the customer’s legal team, who insist on printing and signing the document after the customer returns a fully signed pdf, the rep adds the signed pdf as a new version of the existing order form file and marks the file status as completed the signing history clearly shows that the deal is fully executed, and revops can safely proceed to booking and billing without hunting for the final contract in email threads use case 2 a customer prefers to use their own docusign tenant instead of nue’s integrated docusign flow the account team downloads the order form pdf from nue, sends it via the customer’s docusign instance, then downloads the fully executed envelope as a pdf instead of creating a brand‑new attachment on the quote, the rep uploads that executed pdf via the upload action, which creates a new version of the same file so the quote continues to have a single, authoritative order form with clear status and history use case 3 late in negotiation, a customer requests a small handwritten change to one clause the rep prints the order form, annotates the clause with the customer, and they both initial and sign on paper the rep scans the updated contract and uploads it as a new version of the order form via the upload flow they add a note summarizing the change, and because everything is versioned on one salesforce file, anyone reviewing the deal later can see both the original generated version and the final annotated, signed copy with contextual notes for more details, please refer to docid\ i2uoxjkirteiel rez4ua developer experience cross sell via change orders programatically cross sell via change orders introduces the ability to add entirely new products to an existing customer account as part of a change order — enabling true cross sell workflows without creating a separate new business order sales teams, revops, and self service portals can now bundle cross sell products alongside amendments (quantity changes, term extensions, cancellations) in a single transaction, streamlining the quoting to activation process across all three api surfaces global methods, revenue lifecycle apis, and commerce apis why it matters unifies cross sell with amendments in a single transaction , eliminating the need for separate orders when a customer wants to add new products while modifying existing subscriptions programatically, reducing order volume and simplifying billing reconciliation supports full bundle and add on hierarchies , allowing new standalone products with configured add ons, dynamic add ons, and recursive nesting, so even complex product catalogs with multi tier bundles can be cross sold through a single api call enables pricing flexibility with netsalesprice overrides for global method , giving sales teams and integrations the ability to set negotiated prices at any level of the product hierarchy, bypassing standard price book calculations while preserving discount transparency works consistently across all api surfaces , so whether the change order originates from a salesforce automation (global methods), an external erp or cpq integration (revenue lifecycle apis), or a customer self service portal (commerce apis), the same newproduct capabilities are available learn more customer use cases use case 1 salesforce flow driven cross sell (global method) salesforce flow driven cross sell (global method) a salesforce admin builds a flow that triggers when a customer's usage crosses a threshold the flow invokes globalchangeorderservice changeorder() with a newproduct change type to automatically add a capacity expansion product to the customer's account, co termed with the existing subscription via cotermasset, priced at a negotiated rate using netsalesprice, and including bundle add ons the entire cross sell is handled programmatically within salesforce without leaving the platform, and the order activates automatically as part of the flow more details at docid\ upanqs 1lf0n z1z uh55 use case 2 external system integration (revenue lifecycle api) external system integration (revenue lifecycle api) an erp or billing system needs to programmatically add new products to customer subscriptions based on external business logic, such as for example, provisioning a new module after a contract amendment is signed in docusign the external system calls post /cpq/change order wit h a newproduct asset change, and the api validates against salesforce price books, calculates proration, and creates the order this enables external systems to drive cross sell without direct salesforce ui access o h a newproduct asset change, and the api validates against salesforce price books, calculates proration, and creates the order this enables external systems to drive cross sell without direct salesforce ui access o r apex knowledge more details https //api docs nue io/creating draft change orders use case 3 customer self service portal (commerce api) customer self service portal (commerce api) a commerce portal allows customers to browse and add new products to their existing subscription directly the portal calls post /change orders with the new product in the products array alongside any amendments (upgrades, cancellations) in assetchanges the commerce api handles pricing, invoice preview, and activation with sub second response times on aws infrastructure, then syncs the resulting order products back to salesforce more details https //api docs nue io/change orders integrations sphere integration nue now supports a native integration with sphere as an external tax engine once connected with a sphere api key, nue can calculate real time sales tax, vat, and gst for quotes, orders, invoices, and credit memos, using product level tax modes (tax inclusive vs tax exclusive) and customer/location data tax results are persisted at both the transaction header and line level for downstream reporting and audit why it matters an out of the box and streamlined tax integration , the sphere integration helps manage tax compliance risk by delegating rate and rule maintenance to sphere while ensuring nue always calls sphere in real time for quotes, orders, invoices, and credit memos thereby enabling tax in single and multi jurisdiction scenarios (us sales tax, canadian gst/hst/pst, and international vat) end‑to‑end consistency across quote → order → invoice → credit memo → self‑service the same sphere calculation logic is used in cpq, billing, and self‑service flows, reducing reconciliation issues and “mismatched totals” between sales and finance systems simplified tax configuration and safer operations product tax configuration in nue is reduced to a tax mode flag; tax codes and complex mappings are centrally managed in sphere better seller and customer experience sellers see tax on quotes/orders in real time and can correctly handle tax‑exempt entities from inside crm/nue to learn more about the integration docid\ ddabz3lwbp9a ziqmk 4n