2025-0.0 - Resolved Issues
Circulation Management (CM)
Customer Service
The issue with Delivery Placement Change Transactions not being processed if a single RouteDeliveryPlacement record was end-dated or if the start or end dates overlapped with another Delivery Placement Change setup has been resolved. (CM2-10702)
When creating a Move transaction, the Delivery Placement ID was incorrectly defaulted, even if no Delivery Placement ID was set in the Router setup or at the Old Address. This issue has been resolved, and the Delivery Placement ID will no longer be incorrectly defaulted during Move transactions when not specified. (CM2-10704)
The issue that allowed users to delete a Bank Draft payment from the Customer Service screen before Batch Payments were processed has been resolved. The Delete button will now be disabled until the Batch Payments have been processed. Additionally, the issue that allowed users to modify a Bank Draft payment from the Customer Service screen before Batch Payments were processed has also been resolved. (CM2-10866) (CM2-10890)
The issue of escalation emails incorrectly displaying the number of formal complaints raised has now been resolved. The logic for calculating the number of complaints has been modified as follows, and escalation emails will now accurately reflect the number of formal complaints based on the specified review period, ensuring that only relevant complaints within the defined time period are included:
Number of Complaints Count = Publishing Date − Review DaysPublishing Date:– the date on which the product is published.
Review Days:– the time period, in days, during which a complaint should be escalated; this period is defined in the Publication Setup > Specifics > Complaint Escalation.
For example, if the Publishing Date is the 30th of a month and Review Days has been set to 3, then the number of complaints will be calculated from 30 − 3 = 27. In this example, the escalation email will only include complaints that have been raised between the dates of the 27th to the 29th.
Note:– The above logic applies only if the complaint date falls within the range of review days.
(CM2-10868)
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)
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)
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)
Previously, when a payment was made to auto-start a subscription, the system used the previous label group even if it ended, and the subscription was starting after the label group’s end date. Changes have now been made such that if the label group publication or label group delivery schedule has been end-dated for Mail or Online subscribers, an error message will now be logged in the process log and the transaction will fail to process.
(CM2-10886)
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)
When creating a Payment Cancel transaction for a 12-month payment ending on a leap year date, the error message “Day in month is invalid. (81)” was displayed. This issue occurred due to the “same day of month” logic used to move the current expiration date back by 12 months. The logic has been updated to validate the new expiration date. If the new expiration date is invalid, it will now be adjusted to a valid date. The error message will no longer be displayed.
(CM2-11112)
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)
Route Service
Route Service > Setup > Route Setup Utility On the Route Setup Utility screen, Resource Texts have been added to the fields “Burt Alt Zone Code 1” and “Code 2” so that clients can change their labels by adding Resource Translations.
(CM2-10774)
Previously, the process identifier (PID) assigned to the Route Delivery List Report was limited to six digits (999999). With the transition to AL2023 (Amazon Linux), which supports PIDs of up to seven digits, this limitation caused issues as the process could not launch and reports were not generated.
Changes have now been made to increase the PID size for the Route Delivery List Report to seven digits, ensuring that reports are generated correctly. (CM2-10805)
Route Service > Draw Mgmt > Draw Adjustments > Adjust for a Week The issue where the user interface incorrectly disabled entry for certain days of the week, even if it was a publication date, when making draw adjustments for publications that do not publish daily (7 days a week), has been resolved. The system will now correctly allow adjustments on publication dates, regardless of the publication frequency.
(CM2-10970)
Accounting
Accounting > Subscriber > Renewal Notices When running Renewal Notices, subscribers with multiple Routes of different Route Types (e.g., Motor, Home Delivery, etc.) were not being selected for renewal, and no errors were logged in the process log. This issue has now been resolved, ensuring that all eligible subscribers are correctly considered for renewals.
(CM2-113)
Subscriber Renewals Export File (Detailed Export 2):
Previously, when running Renewal Notices, the Subscriber Renewals Export File (Detailed Export 2) exported “?????????” in the E1 Value of Adjustment and Payment Amount fields if the values were large (greater than $10,000).
This issue has now been resolved, ensuring that large values are correctly exported without errors in the specified fields.
Additionally, the issue of “?????????” appearing in the F1 Value of the Transportation Cost field for negative values has also been resolved. Negative values are now exported correctly.
(CM2-10364) (CM2-10839)
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)
When running Renewal Notices, invoices or renewal notices were previously printed without including Rate Term information if the Rate Term setup did not have ‘Always’ selected in the ‘Show on Renewals’ and ‘Show on Invoices’ fields. This issue has now been resolved. Renewal Notices will now only be generated when valid Rate Terms are correctly configured in the Rate Term setup. (CM2-11566)
Previously, running Account Accruals without closing past or same-day Account Billings did not display an error, allowing the Accruals to proceed incorrectly. Now, if an unclosed Account Billing exists either in the past or on the same date as the Accruals run, an error message, “Billing is scheduled for MM/DD/YYYY but has not been completed. Billing must be completed if scheduled before Accruals are run for a date greater than or equal to the Billing Date”, will be displayed. This update ensures that billing is completed before running Accruals for the specified date.
(CM2-10349)
Accounting > Subscriber Payments > Payment Processing The error “Mismatched parameter types pass to procedure findgrace. (3230)” occurred in the Payment Processing logs under the following circumstances:
When attempting to create an auto-start for a subscriber with a Marketing term Rate Code.
When processing a payment for a subscriber with a future start date and a Marketing term Rate Code.
These issues have been resolved. The error no longer appears in the Payment Processing logs under these conditions, ensuring seamless processing for auto-starts and payments involving Marketing term Rate Codes.
(CM2-11019)
Accounting > Subscriber > Auto Notice Export When running the Auto Renew Notice Export with the "Print Rate Change Only" checkbox selected, the export was incorrectly excluding eligible subscriptions. This issue occurred when exporting notice information for subscribers whose next Auto Renew payment amount differed from their previous Auto Renew payment. The issue has now been resolved, and the Auto Renew Notice Export correctly includes all eligible subscriptions.
(CM2-11249)
Tools
Graphical Utilities > System > Process Log Report Character Utilities > System >Process Log Report
The Process Log Report was not generated when running from the Graphical User Interface (GUI). In the Character User Interface (CHUI), the report failed to generate when an input file was saved, selected through the Find option, and then processed. This issue occurred when the database contained a large number of UserProfile records and the report was requested for All Users, leading to a Progress error: “-s stack exceeded.”
The issue has been resolved. The Process Log Report now generates successfully without displaying Progress errors, even when running for All Users.
(CM2-10339)
Character Utilities > Import > Billing Change When running the Billing Change Import, the Rate Code of a subscription was incorrectly updated in the Billing Change transaction, even if the FileMap did not include Rate Code information. This occurred because the import process retrieved Rate Code details from the StartSubscription table instead of the Subscription table.
The issue has been resolved by ensuring that Rate Code details are now fetched from the Subscription table. This change prevents unintended updates to the Rate Code in Billing Change transactions.
(CM2-10413)
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)
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)
The ListMatch utility previously failed to add records from a Customer Data System (CDS) 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)
Vindicia
Two new Business Rules have been introduced in the ‘Pymt Auth - Vindicia’ section to replace the earlier hardcoded Source and Reason codes used when processing batches of Vindicia payments in the Batch Payment Screen:
What is the default Source Code for Vindicia Auto Payments batch?
What is the default Reason Code for Vindicia Auto Payments batch?
(CM2-11451)
The Vindicia Retain functionality has been updated to populate the “Transaction ID” field on the Payment Information screen for the SubscriptionPayment record in Customer Services. This “Transaction ID” field will now be populated with the NameValuePair (NVP) value of the PaymentProcessorTransactionId received in the FetchBill response when running the Vindicia Get Payments functionality.
(CM2-11547)
Publishing
Publishing > Distribution > Prev Delivery Labels When running Previous Delivery Labels, the system printed an incorrect TruckID from end-dated TruckDropDistribPoint records. This issue occurred because the same TruckSequenceID had outdated TruckDropDistribPoint data with a TruckID different from the current TruckID.
The issue has been resolved. The system now correctly prints the TruckID from the end-dated TruckDropDistribPoint record when generating Previous Delivery Labels.
(CM2-8852)
Mail and Online subscribers with Bonus Day Transactions were incorrectly excluded from the Publishing Run processes, including the Press Room Report, Mail Labels, PO Report, and End Publication Run (AAM Reporting). This issue has been resolved, and Mail and Online subscribers with Bonus Day Transactions are now included in all Publishing Run processes.
(CM2-11030)
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)
Subscriber Activity Import (SAI)
Graphical Reporting > Subscriber > Sub. Activity Import (GUI) Character Utilities > Import > Subscriber Activity (CHUI)
SAI previously allowed the creation of new starts with a backdated Start Date. This issue occurred when there were publications with multiple editions, and final transaction processing was completed for one edition while another edition remained open. The issue has been resolved. Backdated starts will no longer be created through SAI, preventing conflicts with publication editions and ensuring correct processing of new starts.
(CM2-10756)
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-11826)
Setup
A new Business Rule (BR)— “Should Market Terms setup be disabled to be added, modified or copied on Subscriber Rating?” has been introduced in the ‘Customer Services’ section, with the default value set to ‘No’.
If BR is set to No: Marketing Terms fields will remain enabled, allowing users to add, modify, or copy Market rate terms as required.
If BR is set to Yes: Marketing Terms fields cannot be modified, and a popup message will display: “Marketing Term setup is no longer supported. Please contact Naviga IT support for assistance.”
(CM2-10587)
Graphical Setup > Rules > Business Rules In the Business Rules Setup screen, pressing the F2 button previously did not display the available options for certain Business Rules when attempting to modify their settings. This issue has now been resolved, and the F2 button correctly displays all available options for the associated Business Rules.
(CM2-10624)
Setup > Accounting > Renewal Campaign Campaign offers were still being applied to subscriptions when payments were made after the Campaign ended, as long as the payment matched the offer amount. Now, if the Campaign ends before the payment date, the Campaign offer will no longer be applied to the subscription.
(CM2-10760)
Character Setup > Accounting > General Ledger > Sub Payment Adjust The field “Is Taxable” was shown in the Sub Adjust Code Setup screen even though Subscriber Payments with Subscriber Adjustment codes will not be taxed. This issue has been resolved, and the “Is Taxable” field has been removed from the Subscriber Adjustment Code Setup.
(CM2-10780)
Character Setup > Accounting > General Ledger > Sub Payment Adjust > Specifics > Sub Payment Adjust Info When creating a Sub Adjust code with the same ID as a Reason Code record, ReasonCodeInfo records were incorrectly displayed on the SubAdjustCodeInfo screen. This led to errors when attempting to modify SubAdjustCodeInfo records, displaying the message, ‘Sub Adjust Code Info record not found.’
The dependency between SubAdjustCodeInfo and ReasonCodeInfo records has now been removed. This update ensures that ReasonCodeInfo records are no longer displayed on the SubAdjustCodeInfo screen when creating a Sub Adjust code with the same ID as a Reason Code record.
(CM2-11293)
To support payment processing with the payment vendor “Eigen” through NavigaPay, the existing add-on, Eigen, has been renamed “RTEigen.” Activation:– To activate the add-on, please contact Naviga Support. Once the password has been received, enter it in Character Setup > System > Security > Add-On Activation > RTEigen.
(CM2-11402)
Previously, when running processes such as Account Direct Debit using the CIBC2 Electronic File, the File Creation Date and Value Date in the payment file were displayed in the incorrect 'YYDDMM' format instead of 'YYMMDD' in the Header and Batch Header Records. Additionally, the Receiver Bank Institution ID was not displayed in the required four-digit format. These issues have now been resolved, ensuring the file is generated correctly. Additionally, the naming convention for Bank Draft-related files has been updated to the following format:
File Naming Convention:
[Client defined].[CIBC file type].[flag].[extension][Client defined]: Existing file name.[CIBC file type]: "C0800" (hardcoded for CIBC2 file type).[flag]: Indicates whether the file is for Production ("P") or Test ("T").[extension]: ".dat"Example:
directdeposit.C0800.P.dat
(CM2-11656)
Self Service Portals (CMO)
iServices
When creating a new subscription through iServices (zipcampaign.html), users encountered a blank page after entering address and occupant details. This issue has been resolved. Users can now successfully create new subscriptions through the iServices campaign without encountering a blank page. (CM2-11038)
Payments
Naviga Pay
Previously, NCS Circ did not send the custom fields, notes2 and notes3, to NavigaPay for Bank Draft payments when using the payment vendor Payway. This issue has been resolved, and both custom fields will now be sent to NavigaPay for Bank Draft payments. (CM2-10873)
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) (CM2-11829)
Reporting
Reporting > Route > Complaint The default behavior for Redeliver Instructions in the Complaint Report has been modified for complaints created through the CS API or Subscription Link:
“Mail to subscriber” will now be the default in the Redeliver Instructions only when the Resolution option is set to “m” (Mail paper to the caller) and the Deliver Complaint field is set to No in the Complaint Code Setup.
The Redeliver Instructions will remain blank if the Resolution option is anything other than “m” (Mail paper to the caller) or if the Deliver Complaint field is set to Yes in the Complaint Code Setup.
(CM2-8842)
When running Bundle Tops for future start messages, the system was generating duplicate messages for subscriptions if Final Transaction Processing was run, followed by Undo Final Transaction Processing, and then Final Transaction Processing was run again. The issue occurred because duplicate messages were not updated with a bundle print date, leading to them appearing on the bundle top report even after the start had been processed. This issue has been resolved. Messages will now appear only once in the Bundle Top report, eliminating duplicates and ensuring accurate reporting.
(CM2-11009)
Extracts
The intermittent Progress errors that occurred in the
auto_renew.txtandpayments.txtfiles when running Subscribe Extracts on servers using NCS 2020-6.1 version have been resolved. (CM2-11578)
Naviga Subscribe Integration
MicroAPIs in support of Naviga Subscribe Integration
When changing a subscriber’s delivery method from Mail to Online using the Micro API, AddDeliveryScheduleChg, the error “Invalid Label Group” was displayed. This occurred because the subscriber was associated with a Label Group not valid for Online delivery, and the system was incorrectly attempting to use this Label Group. This issue has been resolved. The system now correctly assigns a valid Label Group for Online delivery, preventing the “Invalid Label Group” error from occurring during the delivery method change through the MicroAPI.
(CM2-10297)
Application Programming Interface (API)
Customer Service (CS) API
Users encountered error code 412 when submitting a complaint through the Interactive Voice Response (IVR) system. This issue occurred when the Complaint Code’s “Valid When?” setting was set to “Always,” and the Delivery Deadline Override was enabled for a route. This issue has been resolved. Users can now submit complaints through IVR regardless of the Delivery Deadline Override setting for a route. The resolution applies to Complaint Code’s “Valid When?” setting set to ‘Before,’ ‘After,’ and ‘Always,’ based on when the complaint is submitted.
(CM2-11254)
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)
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-10759)
Last updated
