⚡NCS Circ Rapid Release: 2025-2.2
This release is currently in Beta.
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.
✨Introduction
Welcome to the NCS Circulation 2025-2.2 release. This rapid release introduces key enhancements and program changes across Payments, Customer Service, Accounting, Reporting, and APIs.
This release introduces an enhancement in Naviga Pay with new mapping logic to ensure accurate payment categorization based on PaymentType and PaymentSource. This update improves consistency and prevents data transformation errors.
The release also includes resolved issues across Subscriber Activity Import, Batch Payments, Payment Authorisation handling, and Delivery Method exports, while improving performance in the ImpressPay Hosted Order Page (HOP). Additionally, the ActiveMQ JAR has been upgraded to address security vulnerabilities.
🖥️Minimal Requirements
If using Naviga Pay for payments, a minimum Naviga Pay version of 2.2 is required for 2025-2.2.
If using Payment Authorization Service, a minimum PAS version of 8.11.61 is required for 2025-2.2.
A minimum Circulation version of 2025 is required to upgrade to the 2025-2.2. release.
🛠️Resolved Issues
👥Customer Service
An issue that caused the error message “No w-AutoPayRate terms record” to appear in the Customer Service screen when opening a Combo Subscription with Active or Stopped status has been resolved.
(CM2-12592, CM44#950)
📊Accounting
Accounting > Subscriber Payments > Batch Payments
When adding an adjustment-only payment to a subscription through the Batch Payment screen and clicking OK, the system displayed the following error: “custservice/payment/discount Shared frame layouts do not match for frame AutoRenewFrame. (683).” In addition, the Payment Transaction was incorrectly created with a zero Adjustment Amount.
This issue has been resolved. The error no longer appears when submitting adjustment-only payments from the Batch Payment screen, and the system now correctly creates the Payment Transaction on the specified subscription ID, including both the payment and adjustment amounts.
(CM2-12357, CM44#760)
📥Subscriber Activity Import (SAI)
Graphical Reporting > Subscriber > Sub. Activity Import Character Utilities > Import > Subscriber Activity
Previously, when running the Subscriber Activity Import on a Progress database configured with the DMY (day-month-year) date format, the error message appeared: “The month of a date must be from 1 to 12. This record was rejected. (2578).” This occurred even when the File and File Map were set to MDY or DMY.
This issue has been resolved. The import process now correctly supports all standard date formats (DMY, MDY, and YMD), and the error no longer appears.
(CM2-11948, CM44#560)
🏦 Payments
The Hosted Order Page (HOP) of ImpressPay encountered performance issues during payment processing. While payments were vaulted, authorization failed, and in some cases, the HOP froze after processing more than 20 payments.
This occurred because a new Chromium instance was created for each HOP, and the instances remained active after payment submission, eventually exhausting system resources and causing the process to hang. This issue has been resolved.
(CM2-12148, PBS44#50)
The statement descriptors sent to Naviga Pay have been updated to support all subscription Rate Types (Normal, Reduced, and Promotional), which were previously limited to only Reduced and Promotional.
They are now correctly applied for all Rate Types, based on the following Business Rules in the Pymt Auth – General section:
When using Naviga Pay, what statement descriptor should be used for one-time payments?
When using Naviga Pay, what statement descriptor should be used for auto payments?
(CM2-12446, CM44#610)
Validation has been added to the Routing/Bank Number and Account Number fields when entering Bank Draft details in the Payment or AutoRenew sections for non-Naviga payments. The system no longer accepts all-zero values in these fields, ensuring accurate financial data entry.
Note: This validation applies only to the following modules*:*
Customer Service
Accounting
Route Service
(CM2-12448, CM44#620)
Validation has been added to the Routing/Bank Number and Account Number fields when submitting Bank Draft details through the CircAPI, Customer Service API (Single Payment and AutoRenew Payment), and AddPaymentProfile Micro API for non-Naviga payments. The APIs no longer accepts all-zero values in these fields, ensuring accurate financial data entry.
Note: This validation applies only to the following CircAPI endpoints:
Create Subscription
Create Subscription By Campaign
Create Payment
Create Billing Change
Create Billing Change By Campaign
(CM2-12538, CMO44#70 – HM44#120 – CM44#770)
The issue with the Payment Authorization Message not being defined for the payment vendor CyberSource SA integrated with NCS Circ has been resolved.
Previously, only the Decline Response Code was displayed to the customer, without the corresponding Error Description returned from the vendor.
A fix program has now been implemented to create these Payment Authorization Messages, ensuring both the Decline Response Code and the Description are displayed correctly.
(CM2-12578, CM44#920)
📑Extracts
The Standard Conversion Extracts for subscriptions have been updated to correct an issue where Online subscribers were exported with Home Delivery or Carrier as the Delivery Method, and Mail subscribers were exported with Carrier. This occurred when Delivery Method changes were made on the same date.
The issue has now been resolved, and the extracts correctly reflect the updated Delivery Method.
(CM2-12338, CM44#550)
🌐Customer Service (CS) API
When creating a Single Payment through the CSAPI on the Single Payment Terms Info page (payinfo.html), the error “No qualifying payment terms available for Daily Messenger (Error Code: 202)” occurred for Mixed Delivery publications (those using both Route and Mail Delivery Methods).
This issue occurred after Final Transaction Processing was run and the publications were in Transactions Processed status, but End Publication Run had not yet been started.
This has been resolved. Valid payment terms are now correctly retrieved and displayed during Single Payment processing through the CSAPI.
(CM2-12428, CM44#590 – HM44#110)
⚙️Setup
The ActiveMQ JAR has been upgraded from version 5.8.0 to 5.16.8 to address a known vulnerability identified on the Corretto Citrix box used to access the NCS Circ Graphical application.
(CM2-12447, PBS44#60)
The Application Launcher for NCS Circ 2025 has been updated to replace the application name “Newscycle Solutions” with “Naviga.” The associated icons have also been updated to display the official Naviga logo.
(CM2-12559, PBS44#70)
🚀Enhancements
🏦Payments
A new mapping logic has been implemented in NavigaPay to ensure accurate categorisation of payments. The system now maps PaymentType values based on PaymentSource, ensuring consistency and preventing data transformation errors.
The following rules are applied when mapping payment records received from Naviga Subscribe:
If PaymentType is CreditCard and PaymentSource is ‘ApplePay’, ‘Apple Pay’, ‘ApplePay Mpan’, or ‘ApplePayMpan’, it is mapped to applepay.
If PaymentType is CreditCard and PaymentSource is ‘GooglePay’ or ‘Google Pay’, it is mapped to googlepay.
If PaymentType is CreditCard and PaymentSource is blank, it remains CreditCard.
If PaymentType is CreditCard and PaymentSource is PayPal, it is mapped to paypal.
If PaymentType is PayPal, it is mapped to paypal without modification.
If PaymentType is Bank Draft, it is mapped to ach.
Disclaimer:
This feature is introduced with Naviga Subscribe version 2025-4.0. To take advantage of this functionality, ensure that your system is running version 2025-4.0 or later, as earlier versions do not support it.
(CM2-12185, CM44#510 – HM44#90)
Last updated