NCS Circ Rapid Release: 2020-4.2

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-4.2 release. This release includes a variety of program changes that address issues from earlier versions, as well as a new Business Rule for standardizing the dates parameter in the APIs.

In this version of NCS Circulation, the input parameters of the CreateDayPassByCampaign and BillingChange CircAPIs have been updated, and program changes have been made to the Automatic Subscription Payments.

Minimal Requirements

• If using Naviga Pay for payments, a minimum Naviga Pay version of 2.2 is required for 2020-4.2.

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

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

Resolved Issues

Circulation Management (CM)

Tools

• Utilities > System > View/Print

  When running the Trial Account Billing batch using the View/Print Utility, if the batch contained an entry for Trial Billing followed by another entry for anything, the message “** FIND FIRST/LAST failed for table w-ViewPrint. (565)” was displayed on the screen, and other programs were unable to run after running the Trial Account Billing.

  This issue has now been resolved in (CM2-9583, CM43#4640).

Naviga Subscribe Integration

MicroAPIs in support of Naviga Subscribe Integration

• The Label Group is set incorrectly in the AddMoveTranDelSchedChg MicroAPI, although it is correctly set when the move is entered manually in CM. This has been resolved now. (CM2-9739, CM43#4920) (CM2-9835, CM43#4875)

Payments

• Accounting > Subscriber payments > Auto Payments

  When creating a Billing Change to update the credit card details in the Auto Renew Subscription record, the following changes have now been implemented:

  1. If the Card Holder Name field is left blank, the Account Holder Name will reflect the existing Card Holder Name.

  2. If the Card Holder Name field is changed, the Account Holder Name will be updated in the credit card details to reflect the new cardholder’s name.

  (CM2-9361, CM43#4560)

Application Programming Interface (API)

• The CircAPI BillingChange has been modified so that if no change is to be made to the Tip Amount, providing a null, blank, or any character value will retain the existing Recurring Tip Amount. Note: The Recurring Tip Amount will only be changed if an integer/decimal value is provided.

  (CM2-9642, HM43#355 - HM43#680)

Enhancements

Application Programming Interface (API)

• A new Business Rule— “What is the default format for date type input and output parameters received and sent in Circ and Micro APIs?” has been introduced in the CircAPI section, with the default value set to “mdy” (i.e., mm/dd/yyyy).

  Note:

  1. In the CircAPI, the response will show the date in the format that has been specified in this BR.

  2. The input parameter fields in MicroAPIs and CircAPIs only accept the date format that is specified in the BR.

  

  (CM2-9636, CM43#4770 - HM43#660)

• The CreateDayPassByCampaign CircAPI has been modified so that the “Source Code” parameter, which used to be mandatory (*), is now optional.

  Note: If the Source Code is not passed in the CircAPI, the value will be taken from the Source Code value defined in the respective Campaign Code.

  

  (CM2-9743, HM43#690) (CM2-9835, HM43#575)