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.
Welcome to the NCS Circulation 2020-5.1 release. This release includes a variety of program changes that address issues from earlier versions.
With this release, changes have been made in the autopay payment authorization to remove a subscriber from the autopay if the payment is declined by Payway vendor, and new fields have been introduced in the Subscribe Extracts Rate_Codes file.
The issues with the PeopleSoft interface in the Route Service, the rejection of emails sent from iServices in Gmail, the GetTax CircAPI not retrieving the tax details for hybrid delivery methods, and the Subscribe Extract's runtime performance have been resolved.
If using Naviga Pay for payments, a minimum Naviga Pay version of 2.2 is required for
2020-5.1.
If using Payment Authorization Service, a minimum PAS version of 8.11.61 is required for
2020-5.1.
A minimum Circulation version of 2020 is required to upgrade to the 2020-5.1 release.
To access the newly added fields in the extract files, Subscribe Extract version of 7 is required. Please contact Naviga Support for this change to be implemented.
Setting the Business Rule— “To which system should account credit balances be interfaced? (Account Finance section)” value to Peoplesoft4 disabled the Bank Draft fields in Account Services, which resulted in users being unable to update the Bank Draft information. This issue with the Peoplesoft interface has now been resolved, and the Bank Draft details can now be updated. (CM2-10140, CM43#5310)
Previously, when sending emails from iServices to subscribers with multiple email addresses, the email was generated with multiple To fields (one for each email address) instead of a single To field containing all email addresses separated by a comma (,). This caused Gmail to reject the emails with the error message— “This message is not RFC 5322 compliant. There are multiple To headers. 550-5.7.1 To reduce the amount of spam sent to Gmail, this message has been 550-5.7.1 blocked.” This issue has been resolved, and emails will now only be sent to the subscriber's primary email address. (CM2-10340, CM43#5620 - CMO43#670)
The runtime performance of the Subscribe Extract, Auto_Renew, has now been improved. (CM2-10054, CM43#5220 - CM43#5260)
The Progress Error "Value x too large to fit in INTEGER." in the auto_renew.txt file of Subscriber Extracts has been resolved.
Note: This error will now be displayed in the debugger file instead of the extract file.
The Progress Error "Starting position for SUBSTRING, OVERLAY, etc. must be 1 or greater." in the payment.txt file of Subscriber Extracts with export version 5 and above has been resolved.
(CM2-11012, CM43#5495)
The issue with the MicroAPI "GetDeliveryType" returning an incorrect value for the IsRoutable flag has been resolved. (CM2-10996, CM43#6310)
The GetTax CircAPI failed to retrieve tax for subscriptions using Hybrid delivery methods since it only supported Route, Mail, and Online delivery methods. This issue has now been resolved, such that when Hybrid is entered as a delivery method, the API considers it a Route delivery method for retrieving tax information. (CM2-10210, HM43#740)
A new "Retryable" flag has been introduced in the Payway 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 Payway 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." Note:
Only transactions with soft declines will be sent to Vindicia, as it is not necessary to send hard declines.
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).
The Remarks will contain the Decline Reason Code and its description.
(CM2-9819, CM43#4980)
The rate_codes.txt file of Subscribe Extracts now includes two additional fields, “Rate Type” and “Next Rate Code,” so that clients can use the rate codes in determining which offers will be displayed for users as part of the Stop Saver flow. Note: The new changes are available in Subscribe Extract’s export versions 7 and above. Please contact Naviga Support for this change to be implemented. (CM2-10193, CM43#5490)