NCS Circ Rapid Release: 2020-6.1

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 and Minimum Supported Configuration

Welcome to the NCS Circulation 2020-6.1 release. This release includes a variety of program changes that address issues from earlier versions.

Transaction Security now correctly applies to the "Writeoff Type" field, ensuring regulation at the user level without affecting other fields. Fiscal Close processes now correctly update the Close Date after each successful run. The issue where the Token Account Updater failed to update the CC Expire Date in the Convert records has been resolved.

The publish token-related issues in graphical and character user interfaces have been resolved. This release also includes changes made to the Conversion Edit Reports.

Minimal Requirements

• If using Naviga Pay for payments, a minimum Naviga Pay version of 2.2 is required for

  2020-6.1.

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

  2020-6.1.

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

Resolved Issues

Circulation Management (CM)

Customer Service

• Previously, Transaction Security applied to the “Writeoff Type” field under the “Grace WriteOff Information” screen in Customer Service also affected the “Source” and “Reason” code fields. This issue has been resolved.

  Now, Transaction Security will only be applied to the “Writeoff Type” field, allowing regulation at the user level without affecting the “Source” and “Reason” code fields.

  

  (CM2-11173, CM43#6460)

Accounting

• Character Accounting > Fiscal Close - Sub > Close Period During the closure of fiscal periods for subscriber activities, the Close Date was not being updated, despite the process running without encountering any errors. This issue has now been resolved, and the fiscal Close Date will be correctly updated after each successful fiscal process run. (CM2-11257, CM43#6550)

Tools

• Previously, the Token Account Updater failed to update the “ExtAutoRenewSub Convert.NewInteger[5]” value with the new Credit Card (CC) Expire Date displayed in Customer Service. Changes have been implemented so that when processing Billing Change transactions, if the CC Expire Date has been updated, the last value of “ExtAutoRenewSub Convert.NewInteger[5]” will be reset to 0. This ensures that the Subscriber Extract assigns the correct CC Expire Date and includes that value in the Extract. (CM2-11061, CM43#6570)

Reporting

• Publish Tokens Related Issues

  1. In the Graphical User Interface, when generating reports such as Daily Draw Worksheet, Bundle Tops, Truck Manifest, and Mail Labels, if the File Name field in the View/Print window contained any tokens (<R>, <RD>, <RM>, etc.), selecting the Save button and then clicking OK triggered the following error messages. This issue has now been resolved.

     • “No w-ViewPrint record is available.”

     • “Error attempting to push runtime parameters onto the stack.”

  2. Character Utilities > System > View/Print > Run > Batch

     When running processes like Daily Draw Worksheet, Mail Labels, Truck Manifest, and Bundle Tops in batch, if the input file for these processes contained a spool file name (saved file) with Publishing Tokens (<G>, <R>, <RD>, <RM>, and <RY>), the tokens were not replaced with their actual values. As a result, the files were created with the tokens in the spool file name instead of their intended values.

     This issue has been resolved, and now these tokens are replaced with their actual values during batch processing.

  (CM2-10609, CM43#6540)

Conversions

• Conversion Edit Reports

  1. Subscription Edit Report

     • A new error message number, 187, has been added to the subscription file. For Digital Subscriptions, if the AddressID does not match the BillAddressID, the conversion will now generate error message 187.

       Short description: “CRITICAL AddressID <> BillingID for online address”.

       Longer description: “If the address associated with AddressID has IsOnline set to yes, then BillAddressID must be the same as AddressID. Errors must be corrected.”

     • The subscription file's error message number, 486, previously marked as CRITICAL, has been changed to a WARNING. Since having the LastPaymentDate later than the StopDate will not result in negative consequences, it is now considered a WARNING instead of a CRITICAL error.

       Description: "Warning: LastPaymentDate > StopDate".

     • The error message number 211 in the subscription file, 'CreditCardExpires is invalid mmyy value,' incorrectly generated an error if the Credit Card Expires were in the past. Having an expired credit card for the last payment is not considered an error.

       Changes have been made so that error message 211 no longer generates an error for expired credit cards for the last payments. This error will still validate whether the provided credit card information is valid and that the expiry date is less than 5 years in the future. This change only affects CreditCardExpires associated with the last payment, not auto-renewals.

  2. Demographic Edit Report

     • The error message number 141 in the demographic file, 'WARNING Subscription demographic not valid for product,' was missing the product ID in the detail report. Changes have been made to include the ProductID for each line in the error file.

  (CM2-10762, CM43#6290)