Release 2602

🚀 release 2602 is live in sandbox 🗓️ production deployment is scheduled for march 10, 2026 this release focuses on streamlining the quoting and subscription management workflow, most notably by embedding lifecycle manager capabilities directly into the quote line editor so sales reps can discover, update, and manage existing subscriptions without leaving their primary workspace it also introduces several developer and admin enhancements, including synchronous payment processing for self service orders, a one click catalog publishing tool, configurable docusign recipient selection, and a new apex method for merging renewal and price adjustment lines into a single change line on the bug fix side, the update resolves issues with billing and shipping address population on change orders, improves usage sync reliability to salesforce, and corrects incorrect payment status handling for credit memos synced to erp systems feature enhancements lifecycle manager manage subscription lifecycle directly on the quote line editor (qle) this feature will be available only after the production release on march 10th, 2026 this feature will be available only after the production release on march 10th, 2026 this feature will enable sales reps to discover and manage a customer’s existing subscriptions directly from the quote line editor, without leaving the quote or navigating to lifecycle manager a new manage existing subscriptions manage existing subscriptions button on a quote (new or existing) opens a side panel that lists all contracted subscriptions on the account, and guided prompts help reps decide whether to update an existing subscription or create a new one when they add products to a quote why it matters reduce friction and errors for mid‑term changes by bringing subscription discovery and change actions (renew, update quantity, adjust price, etc ) into the rep’s primary quoting workflow, instead of directing them through account > opportunity > lifecycle manager > change quote → qle account > opportunity > lifecycle manager > change quote → qle prevent duplicate or conflicting subscriptions by detecting when a quoted product already exists as a subscription (same sku/price book entry) and prompting the rep to modify the existing subscription instead of creating a new one increase upsell, cross‑sell, and renewal velocity by giving reps a single workspace (qle) where they can see all active/ended subscriptions, queue multiple changes into a “change cart,” review the impact, and apply them to the quote in one go—reducing clicks and cognitive load while keeping pricing and term logic consistent with lifecycle manager learn more customer use case use case 1 a sales rep is working on an upsell for additional seats of an existing vroom enterprise vroom enterprise bundle from a new opportunity, they can open the primary quote and go straight to the qle instead of switching to lifecycle manager to find the right subscription, they can click manage existing subscriptions, manage existing subscriptions, scan the side panel for the customer’s current claude subscriptions, and open the relevant subscription card there, they could select update quantity, specify the incremental seats and start date, add the change to the cart, review it, and apply it to the quote never leaving the editor or risking a new, duplicate subscription line use case 2 during a renewal, a sales rep also wants to cross‑sell a higher tier product they drag the new bundle into the qle nue detects that the customer already has active subscriptions with the same sku & auto selects the side drawer filters to only the compatible subscriptions, and they use the subscription cards to both renew existing lines and upsell an existing subscription to the higher tier, ensuring correct continuity and avoiding cancel‑and‑replace complexity use case 3 a renewal manager is preparing a standard renewal quote that also requires some mid‑term clean‑up (price adjustments and small quantity corrections) on the qle, they hit manage existing subscriptions manage existing subscriptions and see a hierarchical list of all contracted subscriptions on the account they open each subscription card, choose renew, adjust price, or update quantity as needed, and add each change to the cart the review changes view summarizes all pending changes, and after a final check they apply everything to the quote at once, ensuring the renewal and in‑term corrections are coordinated and consistent with lifecycle manager rules merge renew + adjust price into single change line via apex global services this feature introduces a new docid\ upanqs 1lf0n z1z uh55 that lets you merge a renew subscription change and an adjust price uplift for the same subscription term into a single change line any uplift from adjust price is represented as a negative discount percentage on the merged renewal line this keeps customer‑facing quotes and orders clean, while still honoring renewal uplift logic and existing change order pricing behavior key capabilities a new apex global service overload on globalchangeorderservice is added to accept both standard change requests (such as globalrenewrequest and globaladjustpricerequest ) and a list\<globalmergechangelinetype > mergetypes parameter, allowing the engine to merge eligible change lines for the same subscription and date range specifically, renew + adjustprice for this release into a single change line the uplift is specified via globaladjustpricerequest discountchange with a negative discountpercentage (for example, 10 for a 10% uplift), and the merged output is a single renew subscription line whose discount % field reflects that negative uplift and whose net sales price and total price are recalculated accordingly, all controlled explicitly by apex callers that choose to invoke this overload and supply the desired mergetypes to implement a renew + uplift global change for scenarios where pricing needs to increase by x% year over year based on the previous term’s net sales price , you should configure the change order pricing logic to reuse net sales price from the last subscription term this setting ensures that the renewal calculation starts from the actual net sales price of the prior subscription term rather than recalculating from the current list price once this option is enabled, the uplift can be applied as a percentage adjustment on top of the prior term’s price the rule can be applied broadly to all products or selectively using the filter products option to target specific skus or product groups this approach preserves the historical negotiated price and ensures that the uplift is calculated correctly relative to the previous year’s pricing rather than the base list price ruby globalchangeorderresult result = service changeorder( new ruby globalchangeorder(options, changerequests), mergetypes // list\<ruby globalmergechangelinetype> ); why it matters this feature lets you decide where and how to collapse renew + uplift into a single economic line item without hard‑coding that choice into the core product you can keep separate renew and adjust price lines in nue for clear arr analytics, then merge them in apex only for the flows that feed your erp or order form, or conversely generate a single merged line directly from globalchangeorderservice for specific customers, product families, or integration paths that flexibility means finance and revops can preserve high‑fidelity reporting in nue while giving netsuite or other erps the simpler, one‑line view they prefer, and implementation teams can evolve or segment these behaviors over time (by region, segment, or integration) just by changing apex logic, not by changing global settings or shared ui behavior learn more for example, in the scenario from the erp integration doc where a renewal change order produces two lines renew subscription for $12,000 and adjust price for a 10% uplift of $1,200 over the same 12‑month term (economically a single $13,200 acv) you can keep that two‑line structure in nue for arr reporting (base vs uplift, nrr, pricing power), but use an apex global‑service flow to generate a single merged renewal line (with uplift as a negative discount %) only for the path that syncs to netsuite, rather than pushing the merge into the core engine or ui for all customers and all integrations here’s a concrete side‑by‑side for the same economic scenario (12,000 base renewal, 10% uplift = 1,200) scenario change line change type net sales price (nsp) discount % not merge change line 1 renew subscription 12,000 0% change line 2 adjust price 1,200 (uplift amount) 10% merge change line renew subscription 13,200 13,200 (12,000 + 1,200) 10% 10% (uplift) show instant validation messages without clicking the bell icon in the line editor via the price builder plugin this release adds a new showimmediately option to the docid\ x6e13mb90quos 12c1pig ( $$addmessage ) so pricing plugins can surface validation messages instantly when a sales rep edits a quote or order line, without requiring them to click the messages bell icon first when showimmediately\ true option is set, the relevant message popover automatically opens either inline on the affected row or at the header level bell, depending on whether the validation is line level or header level and how many lines are affected messages without showimmediately continue to behave as before and are only visible when the rep clicks the bell icon this feature is also made available in the docid 7v yj6wavitsfru7vzoma why it matters sales reps now see critical validation messages (errors and important warnings) immediately in the context of the line they just edited, dramatically reducing the chance that important issues are missed because they never clicked the bell icon the feature balances visibility and noise important messages can auto open while non blocking warnings and informational messages can remain behind the bell, visible only when the rep chooses to click it this keeps reps focused while still giving them access to a complete message history when needed learn more use case 1 a sales rep is configuring a large renewal in the quote line editor they adjust quantity and discount on a high value subscription line the customer’s pricing plugin runs on ui afteredit and detects that the discount exceeds the allowed threshold because the plugin calls $$addmessage with showimmediately true an error message automatically pops up next to the line level bell for that row, clearly explaining the issue and what the rep must do the rep corrects the discount immediately and proceeds, without ever needing to notice or click the header bell icon use case 2 another rep is working through a complex multi line quote where several products have soft constraints (recommended configurations, non blocking warnings) the pricing plugin adds these as warning messaages with showimmediately omitted, so they do not interrupt the flow the only visible cue is a badge and color on the bell icon when the rep is ready, they click the bell to review all accumulated warnings and information in one place, decide which to act on, and then complete the quote define default signing order for e‑signature components in template builder (preview) system admins can now set a “signing order” attribute on each e‑signature component (signature, initial, date signed, full name, text, title, etc ) directly in the nue quote/order form template builder by default, every e‑sign component has signing order 1; admins can change this to any integer ≥ 1 for components that share the same tag (i e , belong to the same recipient), the signing order must be identical; otherwise, saving the template will fail with a validation error when a quote is later sent for e‑signature, the system uses these configured signing order values as the default signing order for each recipient in the docusign envelope (for both template‑based and generated‑pdf flows) why it matters enforces consistent signing workflows across all quotes by defining the default recipient order once at the template level, so every sales rep automatically sends documents in the correct sequence (e g , customer → internal legal → executive), reducing process drift and compliance risk saves time for sales and revops by eliminating manual per‑envelope configuration of signing order; the routing sequence is pre‑derived from template metadata and applied automatically when sending for e‑signature learn more customer use cases use case 1 a revops team at a fast‑growing saas company needs every order form to be signed first by the customer’s procurement contact, then by their internal legal team, and finally by their vp of sales in the template builder, the admin sets all “customer”‑tagged e‑sign components to signing order 1, “legal”‑tagged components to signing order 2, and “internal approver”‑tagged components to signing order 3 when sales reps send any quote using this template, docusign recipients are automatically routed in that 1‑2‑3 sequence without the rep touching signing order fields, ensuring consistent approvals and faster close use case 2 a customer needs two stakeholders on their side to sign in parallel while the internal counter‑signer signs only after both have completed the system admin configures two different tags for the customer stakeholders but gives both sets of e‑sign components signing order 1, and sets the internal counter‑signer tag to signing order 2 when the quote is sent for e‑sign, both customer stakeholders receive the envelope at the same time; only after both complete does the internal signer get notified, mirroring the customer’s real‑world approval flow for more details, please check out docid\ i2uoxjkirteiel rez4ua configure dynamic docusign e‑signature recipient selection (preview) this feature lets system admins control exactly how docusign recipients are selected when sending a quote for e‑signature, including restricting options to predefined, policy‑driven recipient lists per tenant in nue settings → docusign integration, admins can now configure a new “recipient options” setting with three selectable modes “from contact or user”, “by name and email”, and “predefined recipients” at least one mode must be enabled, otherwise the configuration cannot be saved when sales reps send a quote pdf for e‑signature, the recipient step in the flow only shows the modes that the admin has enabled, and can leverage a custom plugin to return dynamic lists of allowed recipients (for example, an approved list of internal signers for a given quote and role) why it matters reduces legal and compliance risk by preventing sales reps from sending contracts to unapproved internal signers when “predefined recipients” is enabled, reps can only choose from predefined or plugin‑returned recipient lists for those roles, instead of a free‑form list of all users or contacts saves time for sales reps and revops by standardizing the recipient setup flow admins decide which recipient entry modes are available, and default recipient logic (implemented via the plugin and related work) can automatically pre‑populate customer and internal recipients with the correct signing order, reducing manual lookup and data entry each time a quote is sent learn more customer use cases use case 1 a global sales organization wants every customer contract to be signed first by the customer contact on the quote and then by an internal approver, such as the rep’s manager previously, reps could pick any salesforce user or even type an email, which led to mistakes and delays when envelopes were sent to the wrong approver with the new recipient options setting, the revops admin enables “from contact or user” and “predefined recipients” while disabling free‑form “by name and email” they also predefine the approved recipients, given the quote and the “internal user” tag, returns only manager‑level users who are allowed to sign for that territory now, when a rep clicks “send for e‑signature” on a quote pdf, the customer signer is auto‑populated from the quote contact, the internal approver defaults to the rep’s manager, and the rep can switch to another approved signer only within the curated list, ensuring the envelope always routes correctly use case 2 a security‑sensitive customer wants to prevent individual reps from adding arbitrary internal people into docusign envelopes while still allowing legal or finance to occasionally redirect signatures their admin enables all three modes but configures the plugin so that “predefined recipients” covers all standard internal signers, and the documented policy instructs sales to use only those predefined entries for rare exceptions, a small legal operations group with elevated permissions can still use “by name and email” to insert a one‑off signer in practice, almost all envelopes are assembled purely from the plugin‑driven lists, dramatically reducing accidental exposure of contract terms to the wrong internal stakeholders while preserving flexibility for edge cases for detailed info about this feature, please refer to docid\ i2uoxjkirteiel rez4ua enable preview of generated quote pdf before sending for e‑signature (preview) when sales reps launch the “send for e‑signature” flow on a quote, they can now click the name of a selected generated quote pdf to open a full preview in a new browser tab before sending it to recipients if a user instead selects a template that has not yet been rendered to pdf, the template name continues to display as plain text with no preview link why it matters reduce mis sent contracts when multiple versions exist for the same quote, by giving sales reps a fast, explicit way to confirm exactly which pdf version they are sending for signature increase sales rep confidence and speed by aligning with the familiar docusign pattern of previewing a document before sending, reducing back and forth with revops, and the need to hunt through files or history tabs learn more customer use cases use case 1 a sales rep is preparing a complex quote with several iterations of the order form template they generate a quote pdf and then click “send for e‑signature ” during the e signature process, they can click the selected file name to open a preview in a new tab after confirming that all pricing, terms, and customer details are correct, they return to the e‑sign flow and confidently configure recipients and send the envelope, without needing revops to verify which version is in use for more details, please refer to docid\ i2uoxjkirteiel rez4ua enable multi select picklists on quote & order line items this feature turns salesforce multi picklist fields multi picklist fields on quote line item and order item into true multi select picklists in the quote line editor and order line editor, instead of plain text fields sales reps now get a compact checklist style dropdown that lets them select and deselect multiple values, use “clear all”, and see a readable summary of their selections in the grid multi select and dependent picklists also now participate in required field validation in the create quote/create order general information section, with inline error messages rendered consistently under the fields why it matters accelerate quote and order creation by allowing reps to quickly select, deselect, and clear multiple values in a single dropdown, rather than typing and retyping combinations across many lines, which is especially important for customers with multiple attributes in their products & pricing improve compliance with required data policies by adding inline required field validation for multi select and dependent picklists in general information, so incomplete quotes and orders cannot be saved without capturing mandatory attributes learn more customer use cases use case 1 a sales rep is configuring a quote where each line item must specify the state in which a service is sold previously, this “states” field appeared as a plain text field on the quote line editor, so reps manually typed state names or abbreviations on every line, leading to typos and inconsistent formatting with this feature, the rep opens the quote line editor and sees a dedicated “states” column rendered as a multi select checklist they click into a cell, check multiple states, and close the dropdown to see a compact summary like “ca, ny +2” in the grid when they save and reopen the quote, all selected states persist exactly as chosen use case 2 an operations user managing orders opens the order line editor to adjust products that also carry multi select attributes originally captured on the quote on opening the editor, they see the same multi select checklist behavior on order lines as on quote lines they can add or remove options using the dropdown, rely on clear all clear all when reconfiguring a complex line, and quickly validate that the multi select values round‑trip correctly after saving and reopening the order without any custom order specific logic display pricing attributes applicable to pricebook entries on the bundle configurator this feature enhances nue's quote bundle configurator so that sales reps see only the pricing attribute columns that are actually used by the products and price book entries in the bundle they are configuring, instead of every pricing attribute defined in the specific customer organization the configurator now dynamically evaluates the bundle’s price book entries and shows a pricing attribute column only if at least one entry in that bundle and product category has a non‑null value for that attribute; columns that are null across all entries are hidden why it matters accelerates bundle configuration by reducing visual clutter in the bundle configurator grid, sales reps no longer have to scroll through multiple irreleavant pricing attribute columns and can focus on only the attributes that drive pricing for the current bundle lowers quoting errors for complex pricing models by hiding attributes that are not applicable to the selected bundle, so reps are less likely to misinterpret blank columns or adjust the wrong attribute scales admin configuration without extra overhead revops teams can continue to add pricing attributes and design sophisticated multi‑attribute models, while the ui automatically shows only the subset that each bundle actually uses, without any per‑bundle ui setup learn more customer use case use case 1 a sales rep works in an org where revops has defined more than 10 pricing attributes, and each bundle uses a different subset they add bundle b1, which is configured to use pricing attribute 1 (pa1) & pricing attribute 2 (pa2), popping open the bundle configurator only pa1 and pa2 appear as pricing attribute columns, the other attributes (pa3 pa10) are hidden because they are null for all of b1’s price book entries the rep completes configuration, saves the quote, and later opens bundle b2 on the same quote b2 uses pa3 and pa4, so this time the configurator renders pa3 and pa4 only, with pa1 and pa2 no longer visible the rep can move between bundles in the same quote without columns leaking leaking from one bundle to another, making each configuration session simpler and less error‑prone developer experience enable publish everything for self service catalogs publish everything introduces a one click and fully automated way to publish your entire product catalog—products, price tags, and product relationships—to the self service mirror cache and ai services, plus apis and settings to keep that catalog continuously in sync as you make changes it includes a publish all button in settings > self service that triggers an async job to publish all active products, price tags, and product relationships that belong to self service enabled price books a new auto publish on activation setting and an enhanced republish on save setting so catalog items automatically get published or republished when you activate or edit them—removing the need for ongoing manual publishing for self service customers why it matters for self service customers, going live or rolling out a new pricing model often required manual, one by one publishing of products, price tags, and relationships with publish everything, admins can publish the entire active catalog in a single action or api call, cutting catalog go live time from hours to minutes and reducing setup risk during launches and sandbox refreshes once live, many teams don’t want to think about publishing at all auto publish on activation and republish on save mean that as soon as an admin marks a product, price tag, or relationship active or saves a change, it’s automatically available in self service and ai flows this keeps the storefront and ai suggestions aligned with your latest catalog configuration without extra ops work see more details at docid\ goewmdsoxpchsjenz4bss enable synchronous payment processing for self‑service orders adds a new synchronous payment mode to the order activation api so that payment is confirmed with stripe before any order, invoice, or subscription changes are committed when processpayment=true, the system computes the order fully in memory, confirms payment via stripe, and then commits all billing and subscription state atomically in a single database transaction if payment fails and rollback is requested, nothing is persisted and the order remains in draft for clean retry why it matters reduce reconciliation exceptions by committing subscriptions, invoices, and stripe charges in a single atomic operation so billing data always matches payment outcomes (no more “order active but payment failed” situations) improve customer checkout ux for self‑service orders by returning a definitive payment result (success, partial success, or failure) in the activation response, allowing the client to guide users immediately to “access product,” “update card,” or “try again ” give product and collections teams precise control over payment‑failure handling (rollback vs commit) so they can design flows that either protect revenue integrity (full rollback) or prioritize continuity of service (commit with unpaid invoice) while keeping subscription versioning correct in both cases learn more customer use cases use case 1 a saas customer lands on a self‑service checkout page built on nue’s self service apis the frontend creates a draft order and then activates it with the synchronous payment option the system calculates pricing, taxes, and proration in memory, generates the invoice, and creates and confirms a stripe paymentintent in the same call once stripe returns success, nue commits the order, invoice, and subscriptions in a single transaction and returns http 200/201 with an activated order and paid invoice the application can immediately redirect the user to their workspace, knowing payment is complete and billing data is consistent use case 2 a customer’s card is declined during checkout the client first activates with processpayment=true and cancelonpaymentfail=true stripe rejects the paymentintent, so nue returns http 400 with payment failed and keeps the order in draft; no invoice, charge, or subscription changes are committed the ui prompts the customer to update their card and simply retries activation on the same draft order, this time with a valid payment method the second call succeeds, returning an activated order and paid invoice, without any ghost subscriptions or partial data from the first attempt how it works callers enable synchronous mode by sending options processpayment=true together with options generateinvoice=true and options activateinvoice=true the cancelonpaymentfail option controls failure behavior when true, any stripe failure (or invalid payment configuration) returns http 400 and the order remains draft with no invoice or subscription changes when false, if payment fails, nue returns http 207 partial success, commits order and subscription updates, and leaves the invoice unpaid with failure details in the body dependencies and limitations reconfigure currently does not support synchronous payment for more details, see the activating draft orders documentation https //api docs nue io/activate draft orders integrations enable external client app–based salesforce integration this update replaces legacy salesforce connected apps with salesforce's new external client apps (eca) across all salesforce integration touchpoints in nue, ensuring compatibility with spring '26+ orgs where connected app creation via api is no longer supported what changed salesforce integration setup (connect to salesforce) the settings > salesforce integration flow now provisions an external client app automatically when connecting to a salesforce org admins will see two salesforce authorization prompts instead of one — the first establishes a bootstrap session to create and configure the eca, and the second authorizes the newly created eca for ongoing use the setup still handles certificate upload, named credentials, permission set assignments, and quote/order settings configuration automatically salesforce login on the nue login page the salesforce and salesforce sandbox login buttons on the nue login page now authenticate through the eca based oauth flow users clicking either button are redirected to the appropriate salesforce authorization page (login salesforce com or test salesforce com) and returned to nue upon approval this replaces the previous connected app–based login path that would fail on spring '26+ orgs login to salesforce (auto login from nue) the "login to salesforce" action — which lets connected users jump directly into their salesforce org without re entering credentials — continues to work with eca based integrations the token exchange was updated to ensure compatibility with salesforce's frontdoor session bridging why it matters spring '26 compatibility — connected apps can no longer be created via api on spring '26+ orgs without this update, new integrations and sandbox provisioning would silently fail zero manual setup — eca provisioning (creation or reuse, certificate upload, oauth configuration) is fully automated admins do not need to manually create or configure external client apps in salesforce setup no disruption to existing integrations — existing connected app–based integrations continue to work this change only affects new connections and re connections going forward sandbox management sync product catalog between sandbox and production this feature will be available only after the production release on march 10th, 2026 this feature will be available only after the production release on march 10th, 2026 sandbox management now gives admin users a comprehensive way to manage sandbox environments directly from production the headline capability is product catalog sync , which lets admins copy all or selected catalog objects from a sandbox into production through a guided "sync configurations" flow alongside this, admins can link existing sandboxes to their production tenant, provision new sandboxes , manage the full sandbox lifecycle from creation to deactivation, and sync configuration settings bidirectionally between production and sandbox why it matters reduce go live risk by replacing manual export/import scripts with a guided catalog sync flow that enforces dependency order (e g , uoms before products before bundles) and logs detailed status, so revops and cs teams spend far less time coordinating catalog moves and debugging failures keep sandbox and production aligned without re building products from scratch admins can push fully tested products, bundles, and price structures from sandbox into production, enabling faster iteration and safer regression testing on realistic catalogs preserve selling and self service experiences after a sync by automatically re publishing products, price tags, and product relationships in the destination environment, so storefronts and cpq flows continue to surface the right offers without extra manual steps learn more customer use cases use case push tested catalog to production a revops admin maintains a rich product catalog in a nue sandbox where they experiment with new bundles, price tags, and credit configurations ahead of a major product launch, they open sandbox management in their production tenant, choose the tested sandbox, and click sync configurations on the product catalog tab, they select all with a filter that includes only skus for the new launch family the system exports just those nue products and related objects from sandbox, imports them into production, and then automatically re publishes the affected products and relationships on launch day, sales reps and customers see the new offers immediately use case sync specific catalog objects a revops analyst iteratively designs a new set of add on bundles in a sandbox rather than syncing the full catalog each time, they open the product catalog tab, pick only bundles, bundle suites, and product relationships, and use the product filter to include skus that start with "addon 2026" the sync moves only these new add on structures into production while leaving existing bundles untouched status messages show per object export/import counts and any failures with downloadable logs, so the analyst can quickly correct configuration issues and re run the sync use case provision a sandbox for uat a solutions engineer preparing for a customer uat cycle opens sandbox management in the production tenant and clicks "new sandbox " they provide a name, alias, admin email, and select the appropriate locale settings once provisioned, the engineer logs in to the sandbox and connects it to a salesforce org within the first hour, which automatically triggers a settings sync from production within minutes the sandbox has a complete copy of production's configuration settings, giving the engineer a realistic environment to validate new pricing scenarios without any risk to the live tenant use case link an existing sandbox a solutions engineer has an existing sandbox environment that was set up outside of sandbox management from the production tenant, they navigate to sandbox management, click "connect existing sandbox", and enter the sandbox's tenant id after validation, the sandbox appears in the sandbox management list and can be managed, synced, and monitored just like any provisioned sandbox how it works admin opens settings > sandbox management in a production tenant (with the manage sandboxes permission), where they see all linked sandboxes with their current status to sync configurations, the admin selects a sandbox and clicks the sync configurations action icon, then chooses a direction (production to sandbox or sandbox to production) in the configuration options, all settings categories are pre selected on the product catalog tab (available for sandbox to production direction), they either select all (with optional filters) or choose specific object types when they click proceed , sandbox management exports the selected data from the source, imports it into the destination in dependency safe order, then runs publish steps to ensure self service price books and published products remain active in the destination to link an existing sandbox, the admin clicks connect existing sandbox , enters the sandbox tenant id, and confirms after validation throughout all operations, granular status messages are appended with timestamps, counts, and failure log urls admins can view the last 20 events and paginate through older history dependencies and limitations any admin using this feature must be in a production tenant with the manage sandboxes permission under system settings product catalog sync currently supports sandbox to production direction only production to sandbox product catalog sync is not currently supported only nue products are eligible for catalog sync products without a sku or without a price model are automatically excluded salesforce only or legacy cpq products will not be moved large catalogs or complex dependency graphs may yield partially complete imports or publishes admins should review errors from the provided failure logs before re running the sync only published templates are synced, with a maximum of 30 templates per sync operation all settings are synced together; individual settings cannot currently be deselected from the sync the usage rating user (under "everything billing usage") is not synced and must be reconfigured manually after a settings sync automatic production to sandbox settings sync after provisioning only occurs if the sandbox connects to salesforce within 1 hour otherwise, the admin must trigger it manually sandbox to production sync is only available when the sandbox is in active status only the last 20 events are shown in the status messages view at a time, with pagination available for older history for further details, please check the guide here https //docs nue io/nue sandboxes develop test and validate with confidence anrok this feature will be available only after the production release on march 10th, 2026 this feature will be available only after the production release on march 10th, 2026 nue now supports a native integration with anrok as an external tax engine once connected with an anrok api token, 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), anrok product ids as tax codes, and customer/location + tax‑id data tax results are persisted at both the transaction header and line level, and finalized invoices are synced to anrok as permanent transactions for downstream filing and audit why it matters out‑of‑the‑box tax automation for modern saas the anrok integration manages tax compliance risk by delegating rate and rule maintenance to anrok while ensuring nue calls anrok in real time for quotes and orders and uses anrok’s permanent transaction apis on invoice finalization this enables accurate tax across single‑ and multi‑jurisdiction scenarios where anrok operates (us sales tax and global indirect tax) end‑to‑end consistency across quote → order → invoice → credit memo the same anrok calculation and transaction model is used across cpq and billing flows calculations for quotes/orders, finalized invoices, and void/negation handling when invoices are cancelled or refunded this reduces reconciliation issues and “mismatched totals” between sales, billing, and anrok’s tax returns simplified tax configuration and safer operations admins configure anrok once via the integrations overview card, and nue enforces a single active tax engine per tenant product tax setup in nue is reduced to tax mode plus an anrok defined tax code, with all detailed tax categories and rules managed centrally in anrok better seller and finance experience sellers see tax on quotes/orders in real time, including proper handling of tax‑exempt customers via salesforce tax‑exempt flags and non‑us tax ids, so deals don’t stall on manual tax checks finance ops can rely on nue‑driven void vs negation flows to keep anrok’s filings aligned with invoice cancellations and refunds, without logging into anrok to create manual adjustments bug fixes lifecycle manager billing and shipping addresses now correctly populate on change orders previously, change orders created via apis or automated processes (such as auto renewal jobs), the billing address field was not being populated on the new order, even when the related account or billing account had a valid billing address on file since the shipping address is derived from the billing address (or the same as billing address same as billing address setting), this also meant the shipping address was often missing or only partially populated on those change orders this caused downstream issues such as failed tax calculation (for example, with avalara), blocked order activation, and failures when creating orders through automated flows with this fix, billing and shipping addresses are now consistently populated across all change order creation paths, including api based change orders, auto renewal, express checkout, and manual renewals the system now populates both the individual address fields (street, city, state, postal code, country) and the compound billingaddress/shippingaddress fields required by salesforce and downstream tax engines ensures that updated customer or billing account addresses are reflected on new change orders, while preserving safe fallbacks when no current address is available everything billing usage sync to salesforce now runs much faster and more reliably before this fix, usage records uploaded in nue and billed via the scheduler were syncing to salesforce significantly later than the related invoices and invoice line items customers saw invoices and invoice items appear in salesforce almost immediately, but usage records often took close to an hour to sync with this fix, the usage sync behavior has been improved so that usage sync jobs handle tenants with disconnected salesforce integrations gracefully, skipping them with a clear warning instead of generating excessive errors or stalling the entire job once a disconnected salesforce integration is reconnected, the pending usage records for that tenant are picked up and synced on the next scheduled run