If updating the bundle from any version prior to 2025.02.20.1, administrators must make the updates to the bundle preferences during the update process specified in the 2025.02.20.1 release notes.
If updating the bundle from 2025.02.20.1 or later, no additional steps need to be taken.
New Features/Improvements (7)
Enhancement to Optimize Contract Pricing (ZB-3019)
Enhancement to optimize the Execute Rating process specifically in scenarios when a Subscription Item leveraged a Contract Pricing record which included an extremely high number of Contract Pricing Details.
Enhancement to Accommodate NetSuite Change to Script Deployment Audiences (ZB-3010)
Enhancement to accommodate NetSuite’s update to Script Deployment records, which now separates Audiences by ‘Internal Roles’ and ‘External Roles’. This ensures scripts previously set to ‘All Roles’ continue to function as expected, with no change to existing functionality.
Enhancement to Create Transactions Search (ZB-3007)
Enhancement to the search used in the Create Transactions process to optimize the retrieval of Charges and their related fields to source data to generate the Transaction. No change to billing logic was made as part of this update.
Enhancement to Charge Consolidation Backup File Functionality (ZB-2991)
Previously, when leveraging the Charge Consolidation feature, the ‘backup’ file of projected Charges only included Charges in periods in which consolidation occurred. If a particular period did not have any Charges to consolidate, no file was generated.
This enhancement will ensure that a Consolidated Charge File is generated in all periods if Charge Consolidation is in use on the corresponding Rate Plan.
Ability to Lock ZAB Billing Profile Record (ZB-2978)
A new feature to lock the ZAB Billing Profile record has been introduced to add controls and auditability for administrators. It is recommended that all Billing Profiles be locked once testing phases have concluded, before they are utilized on Subscriptions in Production. Unlocking and editing Billing Profile records once they are actively in use may result in unintended impacts to future Transactions.
For System Administrators as well as any users listed as ZAB Administrators on the ZAB Preferences record, a new ‘Lock’ button will appear at the top of the Billing Profile.
When pressed, the entire record will be locked so that no edits may be made, including adding, changing, or deleting Billing Profile Combine or Separate Groups.
In order to proceed with making changes to the Billing Profile, a user with the appropriate permissions must first ‘Unlock’ on the record and click through a warning pop-up. Any changes to the lock status can be audited via the field called ‘Is Locked’ in the System Notes.
Enhancement to Approve Revenue Orders Suitelet (ZB-2895)
Resolves an extraneous search executed when loading the Approve Revenue Orders suitelet to improve efficiency. This was non-impacting and therefore removed.
Enhancement to ZAB API to Return Record Links (ZB-2149)
Enhancement to the ZAB API to allow users to optionally include a parameter to include a link to the record in the response file. To include the link, add the parameter include_links = True to a GET request.
Product Maintenance & Fixes (3)
Issue Filtering Approve Subscription Suitelet (ZB-3012)
Resolves an error occurring when leveraging the ‘Approve Subscriptions’ feature and filtering by ‘Subscription’. This ensures that all filters and results are displayed appropriately.
Issue Leveraging Ad Hoc Rate Plan and Charge Schedule with 'Days' Interval (ZB-3005)
Resolves an issue occurring when leveraging a Subscription Item with an Ad Hoc Rate Plan and a Charge Schedule with a ‘Days’ interval. Previously, Charges were generated with the Charge Period Start and End Dates incorrectly set to the Ad Hoc Data date instead of using the Charge Schedule's settings.
Issue Leveraging Handlebars zab_round Function (ZB-2855)
Previously, when certain company and user number format preference combinations were used in conjunction with the handlebars zab_round function, the rounded number displayed incorrectly when periods and commas were not evaluated appropriately. This has been resolved so that all number formats are compatible with handlebars rounding functionality.