Product Information contained within this document, including technical information and functional specifications, is subject to change without notice, and Naviga reserves the right to make any changes to the information in this document at any time without notice. Naviga makes no warranty, representation, or guarantee regarding the suitability of its products and services for any particular purpose.
Welcome to the NCS Circulation 2025-1.0 release. This release introduces enhancements and program changes to resolve beta bugs from previous versions.
In this release, the error that occurred when running Automatic Subscription Payments on Permanently Stopped subscriptions with no balance due has been resolved, along with the issue causing duplicate records in the submaster.txt file during subscription updates while extracts were running. A new business rule has been added to the Integration section to control whether the “Requested Refund?” checkbox defaults to true when creating a Permanent Stop via CircAPI.
Additionally, address matching logic for Canadian addresses has been enhanced by incorporating both Zip Code and Zip Extension fields to improve accuracy. An inconsistency in credit card surcharge calculations between the Customer Service screen and the CS API has also been corrected by ensuring that the Premium Amount is excluded in both cases.
This release resolves a formatting issue by ensuring that the leading zero is included in the Bank Account Information field for Detail (6) records in the CIBC2 Subscriber ACH file. New data elements have also been added to the File Map setup for the Unearned Revenue Report. The system now exports complete Address table details in the address_master_detail.txt file, regardless of whether the Full Address field is set to ‘Yes’ or ‘No.’ The JxBrowser component has been updated to version 7.41.0 to ensure compatibility with a wider range of payment vendors in Hosted Order Page (HOP) implementations.
If using Naviga Pay for payments, a minimum Naviga Pay version of 2.2 is required for 2025-1.0.
If using Payment Authorization Service, a minimum PAS version of 8.11.61 is required for 2025-1.0.
A minimum Circulation version of 2025 is required to upgrade to the 2025-1.0. release.
This release must be applied with Major Release version 2025-0.0. Ensure that the 2025-0.0 release is installed either before or alongside this update to maintain compatibility and optimal functionality.
Character Accounting > Subscriber Payments > Batch Payments The Progress Error message: “Input value: Should be yes/no. (87),” which appeared when running Batch Subscriber Payments for authorized payments, has been resolved. Note: This Progress Error was related to payments processed through Braintree and Payway, which return a Retryable flag. (CM2-11619, CM44#80)
Graphical Setup > System > Security > Menu Security The issue of unwanted messages appearing when modifying the Write Security ID to ‘ALL’ for a Menu Security item has been resolved. (CM2-11876, CM44#130)
The issue of duplicate records appearing in the submaster.txt file of the Subscribe Extract when a subscription was updated while the extracts were running has been resolved. Note: This fix is version-independent. (CM2-11894, CM44#110)
A new Business Rule—’Should Requested Refund default to true when creating a PermStop via CircAPI?’—has been introduced in the Integration Section, with the default value set to ‘Yes’. This setting determines whether the ‘Requested Refund?’ checkbox should be selected in the PermStop transaction on the Customer Service screen when creating a Permanent Stop using the CircAPI.
(CM2-11886, CM44#90)
When using the Get Delivery and Billing Address CircAPI for Canadian addresses, the system incorrectly matched addresses, particularly for digital addresses. This occurred because the system only used the Zip Code field for matching, rather than utilizing both the Zip Code and Zip Extension fields for accurate matching. The address matching logic has now been updated to consider both the Zip Code and Zip Extension fields for accurate matching of Canadian addresses.
Notes:
This change applies only to Canadian addresses. For non-Canadian addresses, the system will continue to match using only the Zip Code, and the Zip Extension will not be included in the matching.
The address response format for Canadian postal codes has been adjusted. The system will now return postal codes with a space (e.g., XXX XXX), instead of using a hyphen, to align with the format stored in the Subscribe database.
(CM2-11917, HM44#20)
In the Total CC Amount column under the Rate Terms subtab of the Customer Service Rates tab, the Credit Card Surcharge was previously calculated without including the Premium Amount. However, the Customer Service (CS) API included the Premium Amount in its surcharge calculation, causing inconsistencies between the Customer Service screen and the CS API. This issue has been resolved. The CS API has been updated to calculate the Credit Card Surcharge without including the Premium Amount, ensuring consistent calculations across the Customer Service screen and the CS API. (CM2-11878, CMO44#20)
The issue with the CIBC2 Subscriber ACH file, where the leading zero was missing in the Bank Account Information field of the Detail (6) record, has been resolved. The ACH file generation logic has been updated to include the leading zero in the Bank Account Information field for all Detail (6) records. (CM2-11887, CM44#100)
Version 7.41.0 of the JxBrowser component, used for Hosted Order Page (HOP) implementations, has been developed for this release. It adds support for various payment vendors, including ImpressPay, Braintree, Authorize.Net, Stripe, Eigen, and others. This update ensures compatibility with a wide range of payment processors in the HOP environment. (CM2-11812, PBS44#20)
Reporting > Management > Unearned Revenue In the File Map setup for the Unearned Revenue Report (Usage = UnearnedRev), three new data elements have been added: ProductID, TotalProductID, and GrandTotalProductID. (CM2-11528, CM44#50)
Previously, when running the Subscribe Extracts with the Full Address field set to ‘No’ and using Subscribe Extract version 9, the system only included incremental data (i.e., records where Address.ModifyDate was greater than or equal to the Export Start Date) in the address_master_detail.txt file. The system has been updated so that the address_master_detail.txt file will now export details of the entire Address table, regardless of whether the Full Address field is set to ‘Yes’ or ‘No’. (CM2-11881, CM44#120)