Release 2401.1 - 01/31/2024

scheduled on wednesday, 01/31/2024 this update introduces nue webhooks to enable event based integrations with other systems it also includes bug fixes to improve stability no man is an island, and neither is nue that’s why we have webhooks to see your work through they augment your work without great complication they let nue give outside apps notification of all of the things that might yet come to pass in the always on tech stack of enterprise saas (i’ll now stop of webhooks the virtues extolling but they offer a change from traditional polling!) you can level up revrec without reservation you now have a way to flag carves allocation if the field’s marked as true, then the carving is nigh but if text fields read “false” then the carves don’t apply if something goes wrong then we’ll troubleshoot quick — but in the meantime we don’t want problems to stick that’s why our new stripe fix is one you should know it mitigates problems in tax billing flow we’ve also fixed issues with invoicing glitchesin stripe so your sales stack can work without hitches \# feature enhancements \# nue platform nue webhooks nue webhooks facilitate communication with external applications webhooks act as triggers to notify outside systems when particular events occur within nue this allows you to build event based integrations that react to changes or activities in nue in real time for detailed instructions on how to register endpoints and trace webhook events, please refer to webhooks docid\ lybcspjuegb68dhoelxnc \# rightrev integration ability to flag a product's carves eligibility we've added a checkbox labeled 'eligible to include in carves allocation' to the revenue recognition section when creating or editing a new product this field is used to indicate the product's carves eligibility true means that the product is subject to carve in/carve out allocation false means that it is subject to the simple deferred/recognized revenue schedule \# stripe integration enhancement to tax transaction error handling we have improved error handling for tax transactions if an invoice for a billing account fails tax commitment, we skip activation for all invoices under that billing account, but invoices for other billing accounts should still be activated on the salesforce side, a new value committed needs to be added to the tax status picklist, which is a restricted picklist, on invoice, credit memo, and debit memo objects please follow the steps below (1) go to setup → object manager → invoice (ruby invoice c) → fields & relationships → tax status (2) add a new value committed (3) follow the same steps for credit memo (ruby creditmemo c) and debit memo (ruby debitmemo c) objects \# bug fixes \# stripe integration invoice has no invoice item in stripe when billing account is different from sales account previously, when the billing account differs from the sales account, invoice items could not be synchronized to stripe we have now resolved this issue cancel order produces an invoice with incorrect tax and total amounts in stripe previously, canceling an order resulted in an invoice with incorrect tax and total amounts in stripe this issue has been resolved in this release