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 Days

  1. Publishing Date:– the date on which the product is published.

  2. 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:

  1. Online and Mail Subscribers: Transactions will now be generated on MailCutoffDate.

  2. 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):

  1. 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.

  2. 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:

  1. When attempting to create an auto-start for a subscriber with a Marketing term Rate Code.

  2. 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:

  1. What is the default Source Code for Vindicia Auto Payments batch?

  2. 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’.

  1. If BR is set to No: Marketing Terms fields will remain enabled, allowing users to add, modify, or copy Market rate terms as required.

  2. 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:

  1. “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.

  2. 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.txt and payments.txt files 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)

• This release includes schema changes to enhance data management and improve performance across the application. (CM2-11057) (CM2-8767)

Table: FeeTaxTran

• Existing Table: Convert(AdjustFeesTax)

• New Table: FeeTaxTran

Table: FeeCodeInfo

• Existing Table: Convert(FeeCodeInfo)

• New Table: FeeCodeInfo

• FeeCodeInfo is an existing table where the field, IsTaxable, will be added.

Table: TrialSubscription

• Existing Table: Convert(InTrial)

• New Table: TrialSubscription

• A new Table TrialSubscription will be created.

Table: RenewalInfoFee

• Existing Table: Convert(RenewInfo-FeesTax)

• New Table: RenewalInfoFee

• The schema of existing table will be changed to add below fields.

Table: AutoRenewTerm

• Existing Table: ConvertMany(AutoRenewTerm)

• New Table: AutoRenewTerm

• The schema of existing table will be changed to add below fields.

Table: DeliveryScheduleBonusDay

• A new field LabelGroupID needs to be added in the table DeliveryScheduleBonusDay, currently we store it as the second parameter delimited by | in the field DeliveryMethod.

Table: DeliveryScheduleBonusDayAudit

• A new field LabelGroupID will be added in the table DeliveryScheduleBonusDayAudit.

Table: LabelGroupDraw

• New fields will be added in the existing table LabelGroupDraw

Table: RealTimeSync (New)

Table: SingleCopyPublication

• Existing Table: Convert(iServicesRoute)

• New Table: SingleCopyPublication

• The schema of existing table will be changed to add below fields.

Table: UserProfileCR

• The schema of existing table UserProfileCR will be changed to add the fields below. Currently, they are not stored anywhere.

Table: SubscriptionPaymentTran

• The Premium Amount field will be introduced in the existing table SubscriptionPaymentTran.

Table: ChurnExportControl (New)

• This table will be used to store the information of the data being sent to Common Data Platform (CDP) server.

Table: ChurnSubscription (New)

• This table will be used to store the response received from Common Data Platform (CDP) server.

Table: ChurnLevel (New)

• This setup table will be used to display customer satisfaction icon in customer service based on churn range.

Table: ChurnOffer (New)

• This setup table will be used to store the offers required to stop the churn.

Table: SubscriptionPayment

• A new field SplitTransactionID will be introduced in the existing table SubscriptionPayment.

Table: Publication

• A new field PublicationType will be introduced in the existing table Publication

Table: ItemDetail (New)

• A new Table ItemDetail will be created.

Table: Package (New)

• A new Table Package will be created.

Table: PackageProductMix (New)

• A new Table PackageProductMix will be created.

Table: SubscriptionPackage (New)

• A new Table SubscriptionPackage will be created.

Circulation Management (CM)

Customer Service

• Previously, when creating a Temp Stop for Mail subscribers, the Temp Stop Reason codes with “OnlineVacation” set to “Yes” in Reason setup were not displayed in the “Stop Reason” drop-down menu of the customer services screen. Enhancements have been made to NCS Circ and the MicroAPI “AddVacation” to ensure the correct display of Reason Codes based on subscriber type:

  1. Route Subscribers: Both types of Reason Codes, with “Online Vacation” = “Y” or “N,” will be displayed.

  2. Online Subscribers: Reason Codes with “Online Vacation” = “N” will be displayed.

  3. Mail Subscribers: Both types of Reason Codes, with “Online Vacation” = “Y” or “N,” will be displayed.

  (CM2-10694)

• In the Payment Information screen of Customer Services, the character size limit of the Payment Source field has been increased to 20 characters. This change allows for the incorporation of payment source categories such as MPAN ApplePay and DPAN ApplePay for ApplePay transactions made through Payway.

  (CM2-11137)

Route Service

• The maximum allowed character length for the Burt Alt Zone Codes fields has been increased:

  1. Graphical Route Service > Setup > Route Setup Utility

     The “Burt Alt Zone Code 1” and “Code 2” fields in Route Setup Utility now support up to 10 characters, increased from 8.

  2. Character Setup > Distribution > Route > Distribution Point > Specifics > Distrib Point Publication Setup

     The “Burt Alt Zone Code 1” and “Burt Alt Zone Code 2” fields in Distrib Point Publication Setup now support up to 10 characters.

     Note:– These changes apply only to Distribution Point Publication records and do not affect Distribution Point Zip records.

  (CM2-10913)

Tools

• A new utility, PymtAuth_BizRules, has been added to the standard scrub program for the TEST/UPG database. This utility will be included in the crypt purge process and will perform the following tasks after a database refresh:

  1. Update Payment Authorization Business Rules based on values specified in the parameter file (CSV) located in the TEST/UPG database directory.

  2. Update HostName and PhysicalDB Business Rules as needed.

  (CM2-10813)

• Utilities > Import > Demographic Answer The Import Demographic Answers screen has been upgraded to support the import of demographic answers for both Subscription and Account demographics from a flat file.

  The flat file should have the format as follows:

  1. Subscription Demographic Answers: Subscription ID | Answer

  2. Account Demographic Answers: AccountID | Answer

  This utility accepts a range of data types for both Account and Subscription demographics, including:

  1. Integer

  2. Character

  3. Decimal

  4. Logical

  5. Date

  (CM2-10863)

• Utilities > Subscription/Address > Extend Expire Dates The Extend Expire Dates utility has been updated with the addition of a new “Use Import File” option. When this option is selected, the “File Name” field (name of the file to import) will be available.

  Only two types of data should be included in the import file: the SubscriptionID and the number of days to extend, separated by a pipe delimiter (SubscriptionID | Days to extend). Any additional data present in the import file will result in an error.

  Note:– After updating to 2025-0.0, make sure to recreate/resave the input files.

  (CM2-11207)

• A new add-on, ChurnRetention, has been introduced in NCS Circ. This add-on enables users to activate or deactivate churn-related features, such as Churn Extract and Churn Statistics Import, within the application. Add-On Activation:

  To activate the add-on, please contact Naviga Support. Once the password has been received, enter it in: Setup > System > Security > Add-On Activation > ChurnRetention.

  Note:– If the ChurnRetention add-on is deleted, the menu security for churn-related features will remain active, but the corresponding menu items (Churn Extract and Churn Statistics Import) will be disabled in the Graphical User Interface.

  (CM2-11627, CM44#30)

• A new menu option, Churn Extract, has been added under Graphical Utilities > Export. This utility is designed to extract data used to identify customers at risk of churning.

  • The Churn Extract utility includes the following input parameters:

    Field

    What to enter

    Product

    Select the product for which the churn data is required.

    Status to Dump

    Specify the subscriber status: Active, Inactive, or Both.

    Delivery Method

    Specify the delivery method: Print, Digital, or Both.

    Cut-off Date

    Enter the cut-off date.

    The data will be extracted from this date onwards.

    Export File Name

    Specify the file name for the churn export file. The file will be placed in the churn/out subfolder of default exchange directory.

  Note:–

  After deploying this release, create a new subdirectory, ‘churn/out’, within the default exchange directory to store the extracted churn files.

  Path: [defaultdir]/churn/out

  (CM2-11633)

• A new menu option, Churn Statistics Import, has been added under Graphical Utilities > Import. This utility allows users to import churn statistics received from the Common Data Platform (CDP) server. The imported churn data will be displayed on the Customer Service screen, categorized by the subscription churn score range.

  • The Churn Statistics Import utility includes the following input parameters:

    Field

    What to enter

    Read Option

    Specify whether the import should be executed in commit mode (importing churn statistics into Circulation) or in edit mode (reading the file without importing and displaying any errors). It is recommended to first run this option in edit mode to confirm that there are no errors during the import.

    File Name

    Enter the file name for the import.

    The churn statistics will be imported from this file located in the churn/in subfolder of default exchange directory.

  • The Churn Statistics Import utility will import the below fields into Circulation:

    Field

    Description

    BusinessID

    Business ID

    DatabaseID

    Database ID

    ProductID

    Product ID

    SubscriptionID

    Subscription ID

    DeliveryMethod

    Current delivery method of the subscription

    RateType

    Current rate type of the subscription

    PercentOfFullPrice

    Comparison of current rate code to the last rate code in the rate chain

    WeeklyRateAmount

    Weekly rate amount

    IsWasInGrace

    Indicates whether the subscription has ever been in grace

    IsWasAutoRenew

    Indicates whether the subscription has ever been on auto renew

    TotalRelationshipDays

    Total number of days since the last start

    TotalActiveDays

    Total number of active days since the last start up to today

    TimesInGrace

    The number of times the subscription was in grace excluding temporary stop days

    NumOfComplaints

    Total number of complaints since the last start

    NumRateChange

    Total number of rate changes since the last start

    NumRenewals

    Total number of renewals since the last start

    NumPayments

    Total number of payments since the last start

    NumNewStarts

    Total number of new starts

    WeeklyDeliveryDays

    Total number of delivery days per week based on the delivery schedule

    LastTermLengthInDays

    Number of days purchased with the last payment

    ChurnLevel

    Churn level of subscription calculated by the CDP server (e.g.1,2,3, etc.)

    ChurnScore

    Churn score of subscription calculated by the CDP server (ranges between 0.00 and 1.00)

    Note:–

    1. Validation has been implemented for five fields that will be saved in the NCS Circ database: SubscriptionID, ProductID, Delivery Method, Churn Level, and Churn Score.

    2. After deploying this release, create a new subdirectory, “churn/in,” within the default exchange directory to store the churn files for import.

       Path: [defaultdir]/churn/in

  (CM2-11634)

• A new tab, Churn, has been introduced on the Customer Services screen. This tab displays churn information returned from the Common Data Platform (CDP) server, which analyzes circulation data to provide NCS with the Churn Level and Churn Score. The Churn Level represents customer satisfaction on a scale from 1 (lowest) to 5 (highest).

  The Churn Status screen includes the following three fields:

  1. Churn Level: Displays the churn level of the subscription as calculated by the CDP server and feedback.

  2. Churn Score: Displays the churn score of the subscription calculated by the CDP server.

  3. Churn Date: Indicates the date on which the churn data was imported into circulation.

  To visually represent customer satisfaction levels, emojis will be used, corresponding to the following scale:

  • 1: Not Satisfied

  • 2: Slightly Satisfied

  • 3: Satisfied

  • 4: Very Satisfied

  • 5: Extremely Satisfied

  Note:– The Churn Retention table, located to the right of the Churn tab, displays the churn offers available to the customer. Currently, this table is blank and will be populated in a later phase when the feature is fully developed.

  (CM2-11790)

• Utilities > Export > Churn Extract Utilities > Import > Churn Statistics Import

  Menu security has been enabled for the Churn Extract and Churn Statistics Import menu options to regulate access at the user level. The default security value is set to “Not Activated,” which prevents users from accessing these menu items.

  Only users who are part of the Menu Security ID will have access to these options, while users not included in the Menu Security ID will be denied access. For any required assistance, please contact Naviga Support.

  (CM2-11630)

Vindicia

• The CIT/MIT (Cardholder Initiated Transaction/Merchant Initiated Transaction) functionality has been implemented in NCS Circ for Braintree payment processing. A new sciToken parameter has been introduced in the SEND Payment request to Vindicia. This sciToken will now contain the Network Transaction ID (networkTransId) received from Braintree.

  Note:– In cases of multiple autopay declines, the networkTransId will be updated with the most recent value, and only the latest networkTransId will be sent to Vindicia.

  (CM2-10971)

Setup

• Character Setup > Accounting > General Ledger > Bank A new electronic file format, CIBC2, has been introduced for Bank Setup. This format is specifically created for client sites using CIBC Bank.

  (CM2-10699)

• Setup > Rules > Business Rules In the Business Rule Setup screen, a new section called Subscribe has been introduced, along with a set of new Business Rules. These Business Rules have been added at the Business level.

  1. What is the URL to access Subscribe Webhook?

     Default Value: Blank

     Enter the URL to access the Subscribe Webhook.

  2. What is the Media Group code used for Subscribe Webhook?

     Default Value: Blank

     Enter the Media Group Code of the tenant for the Subscribe Webhook.

  3. What is the Media Client code used for Subscribe Webhook?

     Default Value: Blank

     Enter the Media Client Code of the tenant for the Subscribe Webhook.

  4. What is the Client code used for Subscribe Webhook?

     Default Value: Blank

     Enter the Client Code of the tenant for the Subscribe Webhook.

  5. What is the Paper code used for Subscribe Webhook?

     Default Value: Blank

     Enter the Paper Code of the tenant for the Subscribe Webhook. This Business Rule can be set at both the Publication level and the Business level.

  6. What is the Authorization code used for Subscribe Webhook?

     Default Value: Blank

     Enter the JSON Web Token to be used for accessing the Subscribe Webhook.

  7. What is the Source system used for Subscribe Webhook?

     Default Value: Blank

     Enter the consumer or the source system from where the Subscribe Webhook is being accessed.

  8. What is the time interval for which the batch job for Push Notifications should sleep?

     Default Value: 0

     Enter the time interval (in minutes) in which the Webhook endpoint should receive the next batch of notifications or convert records.

     The Webhook will receive push notifications in batches, and based on the value defined in this setting, the notifications will be paused every time after each batch has been sent.

  (CM2-10880) (CM2-11833)

• The DigiCert license, originally valid until May 20, 2024, has been updated. The JAR files have been re-signed with a new certificate, extending the validity until May 20, 2027. (CM2-11301)

• Graphical Setup > System > Security > Menu Security The ‘Menu Security’ option, which was previously accessible through the Character User Interface (CHUI), is now available through the Graphical User Interface (GUI).

  (CM2-11353) (CM2-10372)

Reporting

Extracts

• The occupant_name.txt file in Subscribe Extracts has been updated to include two new fields: Occupant.OtherName and Occupant.OtherNameUsage.

  1. Occupant.OtherName: Provides details of the alternate name for the occupant.

  2. Occupant.OtherNameUsage: Specifies the usage of the alternate name.

  Note:– The new changes are available in Subscribe Extract’s export versions 8 and above. Please contact Naviga Support for this change to be implemented.

  (CM2-11079)

• The non_subs.txt file of Subscribe Extracts has been modified to reduce the total number of columns from 38 to 9 due to its limited use. The updated extract now includes only the following columns:

  1. pub_code

  2. occupant_id

  3. pbs_address_id

  4. occupant_type

  5. first_name

  6. last_name

  7. email

  8. creditstatus

  9. site

  Note:– The new changes are available in Subscribe Extract’s export versions 9 and above. Please contact Naviga Support for this change to be implemented.

  (CM2-11483)

• Character Utilities > Export > Subscribe Extract Previously, the address_master.txt file in Subscribe Extracts contained a row for each address and publication/route ID combination, leading to excessive data duplication. To optimize this, the following changes have been made:

  1. The columns listed below have been removed from address_master.txt and moved into a new file, address_master_detail.txt:

     1. address_id (This column will remain in both files.)

     2. route_id

     3. DistrictID

     4. Redelivery

     5. ProductID

  2. In addition, a new input parameter, “Full Address,” has been introduced on the Subscribe Extract screen.

     1. When set to ‘yes’, the system will export the entire Address table.

     2. When set to ‘no’, the system will export only incremental data, where Address.ModifyDate is greater than or equal to the Export Start date.

  Notes:–

  1. The new changes are available in Subscribe Extract’s export versions 9 and above. Please contact Naviga Support for this change to be implemented.

  2. After updating to 2025-0.0, make sure to recreate/resave any input files.

  (CM2-11511)

Payments

• The Circ application has been integrated with the third-party vendor Enghouse’s Pause and Resume API so that the call recording between the CSR and subscribers now includes an automatic Pause and Resume feature, which the CSR previously handled manually when collecting credit card information or making any other payment-related entry. This functionality pauses call recording when the Payment Hosted Order Page (HOP) is opened and resumes recording immediately once the HOP is closed.

  Note:– To utilize this feature, the customer should make sure that all the open modules have been closed and then reopen only the required modules; otherwise, any existing open modules will return an error.

  (CM2-10593)

• Two new payment vendors, Eigen and ImpressPay (now FluidPay), have been introduced to the NavigaPay suite for payment processing. Changes have been made in NCS Circulation to support these new vendors.

  Note:– While ImpressPay payments are supported in NCS Circulation, the Hosted Order Page integration is currently incompatible due to the existing JX Browser version (v6). An upgrade to JX Browser v7 is underway to enable full support. In the meantime, payment processing through ImpressPay remains fully functional via the Subscribe application.

  (CM2-11324) (CM2-11563)

• The maximum character length for the Credit Card Account Holder Name field has been increased from 30 to 64 characters. Users can now enter or submit up to 64 characters for the Account Holder Name throughout the NCS Circ application. (CM2-11476)

Credit Card Surcharge

• The add-on, CreditCardSurcharge, has been modified to allow a predetermined surcharge to be applied to Subscription Rate Terms. This surcharge will be added to the base rate, with an additional option to apply taxes to the surcharge.

  • Add-On Activation:

    To activate the add-on, please contact Naviga Support. Once the password has been received, enter it in: Setup > System > Security > Add-On Activation > CreditCardSurcharge.

  • Business Rules:

    Two new Business Rules have been added under the Subscriber Payments Section:

    1. Should the CC surcharge be applied on term/grace value only?

       Default value: No.

       This setting determines whether the Credit Card surcharge amount should be calculated against the total payment or just the term/grace value.

       1. If the value is set to Yes and the add-on is activated, the CC surcharge will only be applied to the Term/Grace value.

       2. If the value is set to No, the surcharge amount will be applied to the Total Payment amount.

    2. What is the default percent to use for Cash Discount?

       Default value: 0 (zero percent).

       This setting specifies the default surcharge percentage to be applied to the transaction. For example, to apply a 6% surcharge, enter the value as 6, and for a 5.5% surcharge, enter the value as 5.5.

  (CM2-11282) (CM2-11307)

• A new column, CC Total Amount,’ has been added to the Rate Terms subtab under the Rates tab in Customer Services. This column displays the sum of the Rate Amount and the Credit Card (CC) surcharge. The surcharge is calculated based on the value defined in Business Rule BR2 as referenced below.

  The ‘CC Total Amount’ column will only appear when the following three conditions are met:

  1. ADD ON: CreditCardSurcharge should be activated.

  2. BR1: Should the CC surcharge be applied on term/grace value only? (Subscriber Payments Section). The value should be set to ‘Yes.’

  3. BR2: What is the default percent to use for Cash Discount? (Subscriber Payments Section). The value should be greater than 0.

  (CM2-11308)

• A new field, “CC Payment Amount,” has been added to the ‘Price Quote’ subtab under the ‘Rates’ tab in Customer Services. This column displays the sum of the Payment Amount and the Credit Card (CC) surcharge. The surcharge is calculated based on the value defined in Business Rule BR2 as referenced below.

  The ‘CC Payment Amount’ column will display an amount only under the following conditions:

  1. ADD ON: CreditCardSurcharge should be activated.

  2. BR1: Should the CC surcharge be applied on term/grace value only? (Subscriber Payments Section). The value should be set to ‘Yes.’

  3. BR2: What is the default percent to use for Cash Discount? (Subscriber Payments Section). The value should be greater than 0.

  (CM2-11514)

• When processing payments through the Customer Services screen and the CircAPI with the ImpressPay payment vendor, two new parameters have been introduced to the NavigaPay API’s createVaultTransaction endpoint. These parameters enhance transaction handling by separating tips and donations from taxes and processing fees:

  1. splitAmount: Specifies the amount allocated for tips, donations, or cash adjustments.

  2. adjustmentAmount: Defines adjustments made to the transaction, such as credit card surcharges.

  The API response now includes the following additional parameters:

  1. adjustmentAmount

  2. splitAmount

  3. splitTransactionId

  Notes:–

  1. This functionality is specific to ImpressPay. For other vendors, the payment process will continue to function as it did in previous versions.

  2. The CreditCardSurcharge add-on must be activated to apply credit card surcharge amounts to a transaction.

  (CM2-11345) (CM2-11614)

• Convert Records: The SplitTransactionID received during payment transaction processing will now be stored in the Convert.NewCharacter[1] field for the TransferKey “SplitAmount”.

  (CM2-11616)

• A new field, “CCSurcharge”, has been added to the API response for the following APIs:

  1. CS APIs:

     1. AutoRenew Form Page (autoform1.html)

     2. Single Payment Form Page (payinfo.html)

  2. Micro APIs:

     1. GetRateCodeDetails

     2. GetSubscriptionInfo

  This field will now display the calculated credit card surcharge as part of the API response for these endpoints.

  The ‘CCSurcharge’ field will be returned in the API response only under the following conditions:

  1. ADD ON: CreditCardSurcharge should be activated.

  2. BR1: Should the CC surcharge be applied on term/grace value only? (Subscriber Payments Section). The value should be set to ‘Yes.’

  3. BR2: What is the default percent to use for Cash Discount? (Subscriber Payments Section). The value should be greater than 0.

  (CM2-11453) (CM2-11660)

Naviga Pay

• Payway now supports secure tokenization of merchant tokens (MPAN—Merchant Pay Account Number) for ApplePay transactions, in addition to device tokens (DPAN—Device Personal Account Number).

  • NavigaPay will now return the parameter “isMPAN” to differentiate between DPAN and MPAN transactions:

    1. If the value of “isMPAN” is True, the token will be identified as an MPAN.

    2. If the value is False, it will be considered a DPAN.

  • Convert Records:

    The value of "isMPAN" returned by NavigaPay will now be stored in the New Integer[1] field for the TransferKey "ExtSubPayment" as follows:

    1. If NavigaPay does not return the “isMPAN” parameter, the integer value 0 will be stored in the Convert Record Table.

    2. If NavigaPay returns “isMPAN” with a value of True, the integer value 1 will be stored.

    3. If NavigaPay returns “isMPAN” with a value of False, the integer value 2 will be stored.

  (CM2-10972)

• A new parameter, isFirstRecurringPayment, has been introduced in NCS Circ for requests sent to NavigaPay. This parameter helps in mapping and sending transaction information to Braintree, distinguishing between Cardholder-Initiated Transactions (CIT) and Merchant-Initiated Transactions (MIT). The mapping of Transaction Mode and frequency will now work as follows:

  1. Transaction Mode = Moto/eCommerce and Transaction Frequency = Initial:

     • These are the first payments in a recurring series.

     • Circ Action: isFirstRecurringPayment is set to true.

     • NavigaPay Action: Sends “recurringinitial” to Braintree (CIT).

  2. Transaction Mode = Moto/eCommerce and Transaction Frequency = Recurring:

     • These are subsequent payments in a recurring series.

     • Circ Action: isFirstRecurringPayment is set to false.

     • NavigaPay Action: Sends “recurring” to Braintree (MIT).

  3. Transaction Mode = Moto and Transaction Frequency = Single:

     • These are one-time Moto transactions.

     • Circ Action: isFirstRecurringPayment is set to false.

     • NavigaPay Action: Sends “moto” to Braintree (CIT).

  4. Transaction Mode = eCommerce and Transaction Frequency = Single:

     • These are one-time eCommerce transactions.

     • Circ Action: isFirstRecurringPayment is set to false.

     • NavigaPay Action: Sends “Null” to Braintree (CIT).

  Note:– The isFirstRecurringPayment parameter is generic and will be sent to all vendors from the NCS Circ side. However, NavigaPay will only use this parameter for Braintree transactions.

  (CM2-11042)

• A new “Retryable” flag has been introduced in the Braintree response to indicate whether a transaction is a hard decline (false) or soft decline (true). Now, when a subscriber’s AutoPay payment is declined by Braintree for any reason, the subscriber will now be automatically removed from AutoPay and a Billing Change transaction with remarks will be created on the publishing date for the declined payment.

  If the value returned by the Retryable flag is True (indicating a soft decline), the Billing Change transaction will be created with the remarks “Removes from autopay. Set as suspended. Marked for Vindicia.”

  Notes:–

  1. Only transactions with soft declines will be sent to Vindicia, as it is not necessary to send hard declines.

  2. The Reason Code for the Billing Change can be defined in the Business Rule— What is the default Billing Change Reason Code for Discontinued AutoPay when Credit Card account is closed? (Customer Services section).

  3. The Remarks will contain the Decline Reason Code and its description.

  (CM2-11117)

• When processing the initial Credit Card AutoRenew payment, the transactionFrequency was previously sent as “Initial” to NavigaPay. This value has been updated to “RecurringInitial,” as “Initial” is no longer accepted by payment vendors integrated with NavigaPay. In addition, the isFirstRecurringPayment flag, which was previously sent to NavigaPay for Braintree transactions during Credit Card One-time Payments, has now been removed. (CM2-11576)

Naviga Subscribe Integration

Naviga Subscribe

• When creating a New Start or Restarting a subscription that is either Perm Stopped or Expire Stopped, a push notification will now be sent in the Subscribe application. Additionally, a conversion record will be added to the NCS Circ.

  Note:– The push notification conversion record will only be produced if the Business Rule— What is the URL to access Subscribe Webhook? (Subscribe Section) is not set to blank.

  (CM2-10883)

• Previously, the GetInvoices MicroAPI retrieved the storage path for invoice PDFs (or acknowledgment receipts) from a hardcoded location: .../[defaultdir]/subscribeinvoices. Changes have been made so that the path for fetching the PDF files is now dynamically obtained from the Document Setup (Setup > Miscellaneous > Document).

  (CM2-11211)

• A new Business Rule, What is the public URL to access the invoice PDFs?’ has been added under the CircAPI section, with the default value set to blank. This rule specifies the public URL path for accessing invoice PDFs (e.g., https://www.example.com/renewals/).

  1. The GetInvoices API will now retrieve this public URL path from the Business Rule and append the invoice filename (e.g., Renewal-DM-59917-04222024.pdf) to it.

  2. The full URL returned in the API response will be: https://www.example.com/renewals/Renewal-DM-59917-04222024.pdf.

  (CM2-11382)

MicroAPIs in support of Naviga Subscribe Integration

• MicroAPI GetPaymentDetail Enhancements:

  1. The GetPaymentDetail API now includes three additional output fields:

     1. Premium Amount

     2. Activation Fee

     3. Printed Bill Fee

  2. The API now returns the Payment Transaction details with the Cancel Transaction Number for declined transactions.

  3. When the isAdjustment flag is set to true, a new field, “Description,” is included in the API response. This field displays the web description for the Adjustment Code, providing additional context.

  4. A new parameter, “Payment Type Details,” has been added to the API response. This parameter specifies whether the payment was made through Credit Card or Bank Draft.

  (CM2-10716) (CM2-11179) (CM2-11272)

Application Programming Interface (API)

Circulation (Circ) API

• A new output parameter, “Receive Bonus Day”, has been added to the “FindSubscription” CircAPI response. This parameter indicates whether a subscriber has opted to receive papers on special days that are not part of the normal delivery schedule. (CM2-10351)

• The error message for Error Code 19 was misleading when creating transactions using CircAPIs. Previously, the message incorrectly stated, “PayPalEmail field contained invalid characters that were removed,” even though the transaction was rejected due to invalid characters in the PayPal Email field. The error message has been updated to correctly reflect the issue. It now states, “PayPalEmail field contains invalid characters,” providing a more accurate description of the error.

  (CM2-10730)

• Previously, attempting to permanently stop a Non-Office Pay/Comp subscription using the “Add/Update/Delete/Get Permanent Stop” Circ API with the StopType parameter set to “next billing cycle” resulted in an invalid date error due to missing date logic. Changes have been made in NCS Circ to ensure that the system now correctly uses the next publishing date for the billing cycle when StopType is set to ‘next billing cycle’ in CircAPI to permanently stop the subscription.

  For subscriptions with future start dates, an error message will be displayed, prompting users to “Re-enter a stop date after the current subscription start date of mm/dd/yyyy.”

  (CM2-10989)

• In the FindSubscription CircAPI, the EndGraceDate parameter was being returned in the API response even when the subscriber's End Grace transaction had already been processed. The API has been updated to return the EndGraceDate parameter only if the End Grace Date is greater than the current Start Date. (CM2-11113)

Introduction

Welcome to the NCS Circulation 2025-0.0 release. This major release introduces a wide range of enhancements across various modules of the Circulation Management System, including customer service, route service, accounting, setup, extracts, and payments.

In this release, a new feature, Churn Retention, has been added to identify customers at risk of churning. Additionally, a new “Use Import File” option has been added to the Extend Expire Dates Utility, allowing for file imports. A new “Subscribe” section has also been introduced in the Business Rule setup screen, along with a set of new business rules. The Menu Security feature, previously available only in the Character User Interface (CHUI), is now accessible through the Graphical User Interface (GUI).

Furthermore, the NavigaPay suite has been updated to include two new payment vendors, Eigen and ImpressPay (now FluidPay). The Credit Card Surcharge feature has been modified to allow a predetermined surcharge to be applied to Subscription Rate Terms, with the option to include taxes on the surcharge. The Import Demographic Answers screen has been enhanced to support demographic imports for both Subscription and Account demographics from flat files.

Moreover, Cardholder Initiated Transaction (CIT) and Merchant Initiated Transaction (MIT) functionalities have been added for Braintree payment processing. New fields and file changes have been introduced in Subscribe Extracts, including updates to the occupant_name.txt and address_master.txt files, as well as the addition of an address_master_detail.txt file. A new “Full Address” parameter has also been added to the Subscribe Extract screen.

This major release also includes important bug fixes across various modules of the application.

Minimal Requirements

• If using Naviga Pay for payments, a minimum NavigaPay version of 2.2 is required for 2025-0.0.

• If using Payment Authorization Service, a minimum PAS version of 8.11.61 is required for 2025-0.0.

• A minimum Circulation version of 2020 is required to upgrade to the 2025-0.0 release.

• A minimum of Java 8.201 is required for the 2025-0.0 release upgrade. (PBS43A Interim #110)

  • If the application is accessed through OpenWebStart, we recommend using the Corretto 8 JRE along with it.

  • Download the Corretto 8 JRE file for your operating system from the link:

Installation Notes

• If using PostWare, run all of your postal reports through the current publishing date before applying this patch.

• After upgrading to 2025-0.0, you must recreate/resave any input files for the:

  1. Utilities > Subscription/Address > Extend Expire Dates

  2. Character Utilities > Export > Subscribe Extract