NCS Circ Rapid Release: 2020-6.4
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 2020-6.4 release. This rapid release introduces enhancements and program changes to address issues from previous versions.
This release adds support for selecting multiple Product IDs in the GMA/SAM Export. The NCS Conversion File Exports now allows multiple company selection, generates a consolidated file, and includes a new LabelGroupID field. Additionally, payment declines from previous subscriptions are no longer counted for New Start auto-renewal subscriptions. In Subscriber Activity Import (SAI), address matching for Canadian addresses has been improved by incorporating the Zip Extension in the validation process.
This release also resolves issues related to Renewal Notices, Subscriber Lockbox Processing, Bonus Day Setup, ListMatch Utility, and CircAPI.
Minimal Requirements
If using Naviga Pay for payments, a minimum Naviga Pay version of 2.2 is required for 2020-6.4.
If using Payment Authorization Service, a minimum PAS version of 8.11.61 is required for 2020-6.4.
A minimum Circulation version of 2020 is required to upgrade to the 2020-6.4 release.
Installation Notes
After upgrading to 2020-6.4, you must recreate/resave any input files for the:
Route Services > Utilities > Export > GMA/SAM Export
Resolved Issues
Customer Service
When adding a Move transaction for a combo subscription, the MoveOut/MoveIn transactions for the combo’s non-primary subscriptions were missing ComboSubscriptionID, but the MoveOut/MoveIn transactions for the primary subscription were created correctly. This issue has now been resolved. (CM2-10875, CM43#6250)
Previously, when creating a billing change to update a subscriber’s bank draft AutoPay information (such as BankNumber, AccountNumber, or both), the updated information was not saved, and the AutoRenew transaction record was incorrectly removed during processing. This issue occurred because the logic compared masked values in the AutoRenewTran and AutoRenewSubscription data instead of the unencrypted values. The logic has been updated to compare unencrypted values instead of masked values. This change ensures that the updated bank draft information is correctly saved and prevents the AutoRenew transaction record from being removed during Billing Change processing. (CM2-10876, CM43#6130)
Previously, when Perm Stop was processed for a subscription, the Billing Change Transactions that had been suspended for Vindicia were not marked as processed, resulting in an error— “Error Billing Change Subscription transaction XYZ for subscription XXXXXXXXX: No active route or mail subscriptions exist. (995)”. Changes have been made such that when a record sent to Vindicia has been permanently stopped and Vindicia rejects the payment, the Billing Change Transaction created after the Payment decline will be deleted and a Note will be added. (CM2-10877, CM43#6280)
Previously, when a subscriber failed to pay for their unplanned Premium Days and a payment was made with a negative non-cash Adjustment, the Premium Amount balance displayed a negative value after processing the payment batch. This issue has been resolved. Now, when a subscriber does not make the payment towards the unplanned Premium Days, the wallet will display the Premium Amount as zero instead of a negative value. (CM2-10910, CM43#6600 – CMO43#760)
When the payment decline threshold was reached for online subscribers, the transaction date for Billing Change transactions was incorrectly generated using RouteCutoffDate. The logic has been updated to generate transaction dates based on the appropriate cutoff dates for different subscriber types:
Online and Mail Subscribers: Transactions will now be generated on MailCutoffDate.
Route Subscribers: Transactions will continue to be created on RouteCutoffDate.
(CM2-11150, CM43#6420)
Route Service
Route Services > Utilities > Export > GMA/SAM Export The GMA/SAM Export utility has been updated to support the selection of multiple Product IDs.
Note:– After updating to 2020-6.4, make sure to recreate/resave the input files.
(CM2-12043, CM43#7230)
Accounting
When running Renewal Notices, the Transportation Cost was missing in the export file. This issue occurred when the CarrierRuleDistribPoint had a specific AAM zone, which caused the transportation cost program to fail in finding a rule rate link. However, when an asterisk was present in the AAM Zone field, the rate was successfully identified. This issue has now been resolved, and the Transportation Cost is no longer missing in the renewal notices.
(CM2-11554, CM43#7070)
Previously, when running Subscriber Lockbox Processing for Mail Subscribers with a negative Adjustment Amount, some transactions resulted in errors, causing a blank Rate Code in the Subscription Payment Transaction.
This issue occurred due to the subscriber’s old Delivery Method, which caused errors in locating the required distribution point publication or route publication. The issue was inconsistent, affecting only some subscribers in a given file. This issue has now been resolved.
(CM2-12002, CM43#7220)
Tools
Utilities > Subscription/Address > Bonus Day Setup The issue with Bonus Day transactions were not being created for any type of subscriber when the asterisk (*) was selected as the Delivery Method in the Bonus Day Setup has now been resolved.
(CM2-10579, CM43#5900)
Utilities > Subscription/Address > Bonus Day Setup When the Bonus Day was set up for Mail Delivery Method with the “Include Opt Out Subs” checkbox set to Yes, and a Mail subscription was created with the “Accept Bonus Days” checkbox set to No on the Customer Service screen, the Bonus Day transaction was not created.
This issue has been resolved. Bonus Day transactions for Mail subscriptions will now be created correctly.
(CM2-10810, CM43#6050)
The ListMatch utility previously failed to add records from a CDS (Customer Data System) file if the Street Address matched, but the Zip Extension (Zip+4) was different. This issue occurred because the Zip Extension was not being considered in the matching process.
This issue has now been resolved. The utility now correctly considers the Zip Extension (Zip+4) when matching records, ensuring that records with the same Street Address but different Zip Extensions are correctly added. (CM2-11334, LM43#20)
Publishing
Publishing > Tran Processing Authorized PayPal credit card payments in suspended batches were not being processed when running the Transaction Processing. This issue has been resolved.
The Business Rule— “Should authorized real-time credit card payments in suspended batches be processed? (Pymt Auth - Subscrib Section)” has been updated to include PayPal credit card payments made through the Braintree payment gateway. Authorized PayPal payments will now be processed correctly, even in suspended batches.
(CM2-11156, CM43#6440)
Subscriber Activity Import (SAI)
Graphical Reporting > Subscriber > Sub. Activity Import (GUI) Character Utilities > Import > Subscriber Activity (CHUI)
When using SAI to create a Canadian address, the system was incorrectly matching addresses in the database, particularly for digital addresses. This issue occurred because the matching process previously relied only on the Zip Code field instead of utilizing both the Zip Code and Zip Extension fields for accurate matching. This issue has now been resolved.
Note:– This change is only applicable to Canadian addresses; for non-Canadian addresses, the system will continue to match only on Zip Code, and the Zip Extension will not be included in the matching.
(CM2-11607, CM43#7090)
Naviga Pay
When an Auto-Renew subscription reached the maximum number of payment declines set by the Business Rule “ How many auto renew declines without an accepted auto renew can a subscriber have before being removed from auto renew?” (Subscriber Payments section), it was removed from auto-renewal. However, if a New Start was created with a Start Date later than the previous subscription, the payment decline count still included declines from the previous subscription. Changes have been made to ensure that declines occurring prior to a New Start with auto-renewal are no longer included in the decline count. Only payment declines occurring after the New Start will be considered for the decline count.
Note:– This change applies only if the Start Date of the New Start subscription is different from that of the previous subscription.
(CM2-11596, CM43#7060)
Reporting
The NCS Conversion File Exports prompt now supports multiple Company ID selection, which was previously limited to a single company.
When multiple companies are selected, the system generates a single extract file using an updated naming convention (e.g., DTIAddress-ALL.txt).
When a single company is selected, the system behaviour remains consistent with previous versions.
Error handling has been implemented to ensure validation for invalid or missing selections.
Additionally, a new field, LabelGroupID, has been added to the Subscriber file of NCS Conversion Extracts. This field is populated from MailSubscription.LabelGroupID. For the Route delivery method, this field will remain blank.
Note: NCS Conversion Extracts are for Naviga Support use only.
(CM2-12112, CM43#7250)
When running the NCS Conversion File Exports, the record counter displayed an error: “Value 1000000 cannot be displayed using >>>,>>9. (74).” This issue occurred when the record counter exceeded six digits. The record counter format has now been updated to “>>>,>>>,>>9”, allowing it to accommodate up to nine digits without errors.
(CM2-12211, CM43#7260)
Circulation (Circ) API
When creating a payment transaction using CircAPI for a Mail Subscription with a start date of 01-01-1990 and an unspecified end date (“?”), the error message “No transaction available, check error log” was displayed. This occurred because the Publication data was not being correctly fetched from the Publication database table in this scenario.
The issue has been resolved, and the error will no longer appear when creating payment transactions for Mail Subscriptions with the specified start and end dates. (CM2-10616, CM43#5840)
In the Add an Address/Occupant (AddAddrOcc) CircAPI, the default behavior for the following fields has been updated:
MailAccessible
RouteAccessible
CleanseAdd
If these fields are not provided or left blank, the system will now default them to “Yes” instead of the previous default value, “No.”
(CM2-12003, HM43#1050)
Last updated
