This page containes the description of the hotfixes related to 3.16.1 version
DISCLAIMER
Product Information contained within this document, including technical information and functional specifications, is subject to change without notice. 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.
Please note that all the 3.16.1.X hotfixes are by default included in both the next minor and major versions, which are 3.16.2 and above and 3.17.0, respectively.
If you want the fix to be applied please input a Salesforce case.
Please note that upgrades to this version are no longer available since the Amazon S3 bucket now requires a minimum of TLS 1.2 security protocol, which is not supported by this version.
Note added on June 20th, 2023.
Subscription search against company name is now available in One CSR Portal. The Company field is enough to perform the search. Search is done based on 'contains'
To enable the Company name field please set the SubscriberSearchCompanyNameOption MG2 control setting for a certain client to 1. By default the field is hidden (value = 0).
Both Payment & Customer details are now included in the Payment Token for a new start in Matrix circ system. This fixes the 3.16.1 issue of Customer details being omitted. Matrix version required is 30.00.034.ITSP5.
Unwanted registrations can be deleted by CSR in one go. During the bulk import of registrations from CSV file, the registrations that do not exist in the newly uploaded file will be removed from the database. Please note that The 'Import from CSV' button is only available for Subscription Kind 'Lite'.
Users receiving invitations to corporate subscriptions can now create registrations in Auth0. The button from the invitation will redirect them to the Auth0 modal window showing the Signup tab. When the user enters the relevant credentials, the confirmation is received through email and also displayed in Account Management. To turn this on please set Auth0.App.CanRegister mg2control setting to False.
API, One CSR Portal
Please note that upgrades to this version are no longer available since the Amazon S3 bucket now requires a minimum of TLS 1.2 security protocol, which is not supported by this version.
Note added on June 20th, 2023.
Whenever a subscription/subscriber related API call is made to NCS Circ, the special characters from the following parameters will be discarded before submitting the request with an exception mentioned against each:
First Name: ' - & / .
Last Name: ' - & / .
Cardholder Name: ' - & / # .
House number: / -
Unit number: No Special Chars
Email: @. + - _ ,
When testing email please keep in mind that there is also standard API validation in place:
only one special character is allowed per email
special character cannot be the last one , there should be at least one regular character after the special character
Transfer Links endpoint was enhanced to update the email both in Subscribe database and in NCS Circ
When a user clicks the Login/Register (or any text defined in CMS) button at the Activate page, they are now redirected to the Sign Up tab instead of the Login tab
The logic for the Activate page has been reworked to redirect users referring to the publication code: the Site Code in URL is changed in accordance with the subscription selected. To set this up please go to Support Viewer → APISetting, then updated the Site codes for the SubCon.AllowedPaperCodesByClient API setting
Subscription search via Phone number in One CSR Portal logic was optimised by adding appropriate Indexes in the database table so that it is now able to handle large datasets of up to 7.5M records
The visibility control for AuthPanel buttons SignIn, Register, Custom has been reworked. It can now be managed individually for these buttons via SS Config (HideSigInBox, HideRegisterBox, HideCustomBox, respectively). However, the other properties, like text can be managed from CMS
One CSR Portal, Self-Service, Database
Please note that upgrades to this version are no longer available since the Amazon S3 bucket now requires a minimum of TLS 1.2 security protocol, which is not supported by this version.
Note added on June 20th, 2023.
Fix the login/signup via social media option in Subscription Panel.
The following properties configuration is required in CMS: Subscription Panel --> Presentations --> Page V3 Landing Page --> Step V3 User Information --> User Information --> Switch on 'Google show: ', Facebook show:' and 'Apple show:' properties
The realm Auth0 integration is now configurable via Subscription Panel configuration file to be able to work with SSOR.
To configure the flow to work with SSOR please go to Config --> Systems --> Auth0 within SP and set the 'realm' key value to 'AutomaticMigrationSSOR’. The default 'realm' key value is 'Username-Password-Authentication'.
To prevent potential login failures with subscribers with multiple subscriptions caused by SSOR / Auth0 migration the User Provider configuration setting was created in MG2Control must be set appropriately (e.g. SSOR, Firefly, Gigya, Auth0, etc.)
Logged-in user state not carrying over to MyAccount was fixed by modifying the session recovery logic in SSOR.
VWO script changes
For a certain client the hardcoded VWO smartcode on the checkout pages was outdated. This script has been updated with the details shared by the client.
Delayed Login in Self-Service for Publications using SSOR Authentication
Added on October 16th, 2023.
The issue of publications using SSOR authentication taking too long to load SubCon Sites has been resolved. This delay was primarily because of an additional API call triggered by an internal cookie with an empty value. With the issue resolved, it is now possible to log in to the My Account pages of publications using SSOR authentication without any delays.
This fix is also merged to 3.16.2.5 & 3.16.3.4.
Self-Service, Subscription Panel
Please note that upgrades to this version are no longer available since the Amazon S3 bucket now requires a minimum of TLS 1.2 security protocol, which is not supported by this version.
Note added on June 20th, 2023.
Braintree is sunsetting their API on python platform. Hence, as per Braintree's recommendation, the backend Braintree SDK has been updated to version 4.18.1.
Areas covered: API
The fix was also merged to 2.39.0.1 and 3.16.0.8
Please note that upgrades to this version are no longer available since the Amazon S3 bucket now requires a minimum of TLS 1.2 security protocol, which is not supported by this version.
Note added on June 20th, 2023.
Due to the cross-site validation, Auth0 was deleting the cookie when visiting Self-Service after .com and vice versa. This was fixed by ensuring that the cookie is deleted only when the user actually clicks the Logout button.
Areas covered: Self-Service
The fix was also merged to 3.16.0.9
The issue of registered users getting logged out from the main news site after visiting their My Account page and the issue of users getting logged out from the My Account page after visiting the main news site have been resolved now.
The fix was also merged to 3.16.0.9.
For clients using SSOR authentication, the issue of a logged-in user experiencing a prolonged loading time and the failure to open the dashboard or verified account page on the My Account page has been resolved, and the user can now access the page without the need for a refresh.
The fix was also merged to 3.16.2.3 & 3.16.3
For NCS Clients, the issue of a user on vacation who has paused his subscription with a specific restart date not being able to raise a complaint has been resolved.
Note: Please ensure that the Business Rule within NCS application is set to allow a user to submit a complaint while on vacation.
The fix was also merged to 3.16.2.3.
When attempting to update the payment method using the Google Pay option and saving the offer group, the system was throwing an error message stating “Subscribe with Google SKU codes can be specified only if Subscribe with Google Payment Method selected" for clients on version 3.16.1.X. This issue has been resolved now.
The timeout error occurring in SolCon when selecting specific team members has been resolved.
The fix was also merged to 3.16.2.3.
The error message "Error400:" that was displayed while selecting DefaultOfferGroupId from the 'Available Offer Groups' in the CMS module's Presentation Properties V3 due to the presence of an excessive number of offers on SolCon has now been resolved.
The fix was also merged to 3.16.2.3.
When a user was trying to buy a subscription after getting registered via a third-party authentication system (e.g., a user on a newspaper site clicks on a link ePaper-->Auth0-->Subscription Panel), even after the successful authentication by Auth0, the registration was not created in the Subscribe database. This issue has been resolved now.
The fix was also merged to 3.16.0.12 and 3.16.2.2.
Changes have been made to the Subscription Panel confirmation page such that:
When creating a subscription for a new user, the user will be directed to the website after the subscription has been successfully purchased.
Once an existing user's subscription has been successfully purchased, they must authenticate with Auth0 before being taken to the website.
Auth0 should be set up for the user.
In config.System "AuthCookieDomain" key is mandatory.
The fix was also merged to 3.16.2.3.
Below Special Characters are now allowed in the fields listed below in the Subscription Panel. Users can now enter:
' , - & / . in the First and Last name fields.
All special characters are allowed in the Email field.
' - & / # . in the Card Holder Name field.
# - . / \ in the Address Line 1 field.
. - # in the Address Line 2 field.
When purchasing a subscription, CreateSubscriber failed with the error message “Child Event: CREATESUBSCRIBER failed. Error: FirstName field contained invalid characters that were removed. (19) LastName field contained invalid characters that were removed. (19)" when special character “," was used in the cardholder's name field (First Name and Last Name) on the payment page. This issue has now been resolved.
The issue has occurred since the comma (,) was not one of the earlier permitted special characters ('- & /.) for the name fields. The name fields now allow the usage of special characters: (' , - & / .).
When creating a subscription, AddSubscription failed with the error message "The entered payment information was not accepted" when special characters (&/.,') were used in the Cardholder's name field (First Name and Last Name) on the payment page when using Cybersource gateway. This issue has now been resolved.
The fix was also merged to 3.16.2.3.
Please note that upgrades to this version are no longer available since the Amazon S3 bucket now requires a minimum of TLS 1.2 security protocol, which is not supported by this version.
Note added on June 20th, 2023.
Paypal via Braintree Renewals have been getting declined in circulation. It was identified that the PaypalBAID parameter while purchasing the subscription on EZPay was not being sent accurately to Circ. The issue has been fixed by passing the appropriate parameter from the payment vendor to the circulation system.
Areas covered: Self-Service
This fix was also merged to 3.16.0.10 and 3.16.2.1
Client specific custom configuration for social login has been added to the Subscription Panel config files so that subscribers can authenticate through Auth0 to the client's site using their social media login connections (Facebook, Google, and Apple) based on the respective client's custom configurations. Clients that have not opted for this method of authentication will be able to utilize the default method for subscribers to login to their sites.
Areas covered: Subscription Panel
This fix was also merged to 3.16.2.4
The CMS Content module has been updated to support Transport Layer Security (TLS) version 1.2. The TLS version can now also be configured from the web.config file, and image uploads can now communicate with the AWS S3 bucket using the TLS 1.2 security protocol.
This update has been made as Amazon will no longer support TLS 1.1 for its S3 bucket.
The Hotfix 3.16.1.7 documentation was updated on June 12th, 2023.
Note: If the TLS version is not configured in the web.config file, CMS now uses the TLS 1.2 security protocol by default.
This fix was also merged to 2.39.1, 2.39.1.0, 3.15.3.1, 3.15.2.1, 3.16.0.13, 3.16.2.4, and 3.16.3.
The error “Sorry, the page you requested was not found. See current offers.“ that was displayed when using the input parameter "ofrgp_id" to purchase a subscription in the Subscription Panel has now been resolved. There was an issue with the SolCon GetOffers logic, which has been reworked.
This fix was also merged to 3.16.2.4
The user was not able to add a Division to a published offer in SolCon. An error message was displayed during this update. This issue has been resolved.
This fix was also merged to 3.16.2.4
Previously, in SubCon Site (Self-Service), the GET /Complaints/{subscriptionId}/Problems endpoint was failing because the complaint problem codes retrieved from CircPro were not available in Subsvc, which resulted in an error. This issue has now been resolved.
This fix was also merged to 3.16.2.4
The issue of an increased number of 500 and 404 errors found on clients' servers has been successfully resolved. This was an Authentication system-specific issue. For SSOR clients, even if the user was logged out while navigating to the SubCon site, the logout call was triggered and returned a 500 error. For MG2 Auth clients, the wrong credentials during login were triggering the logout action. After the fix, for SSOR clients, the logout call will be executed with a status 200 and for MG2 Auth clients, there will not be any logout call while entering the bad login credentials.
This fix is also merged to 3.16.2.5 & 3.16.3.0.
In the seamless flow, if the Independent Address component for the payment page has been enabled, users could purchase or subscribe to a subscription with a single click after entering their credit card information. The issue occurs when the credit card details have been validated, the Submit button disappears, and the user is taken directly to the payment options, even if the fields, First and Last names, Phone, and Zip Code, have not been filled. This resulted in the AddSubscription call being triggered with incomplete information, and since the Submit iframe button is from a third-party payment site, it does not validate whether the aforementioned fields have been filled, resulting in no error warnings being displayed.
Changes have been made to allow the submission of incomplete fields if the credit card has already been validated in the seamless flow by introducing a delay time after each keystroke while filling the fields under the independent address component.
A key, "SeamlessInputDelayTime", must be added to the SP Config file with any numerical value. The value indicates the delay time in milliseconds, with the default value set at 1500 milliseconds (1.5 seconds).
For example, after entering the first name, it will wait 1.5 seconds and then call AddSubscription if no additional keystrokes have been detected. When the user starts entering the following fields, such as Last name, phone number, and zip code, the timer is reset after each keystroke, and the AddSubscription call is triggered only after a 1.5-second delay.
This fix is also merged to 3.16.0.14, 3.16.3.1, 3.15.2.4, 3.15.3.5, 3.16.2.5
This release is in its beta version now.
Recently, major browsers have introduced additional security measures and constraints related to third-party cookies, as well as cross-domain data transfer and communication. The latest release of Chrome no longer supports third-party cookies. These were impacting the functioning of the Landing application and user experience negatively. Despite the implementation of workarounds, users were encountering issues in the sign-in flow at times.
Therefore, the sign-in logic for the Landing application has been revised without significantly affecting the existing functionality and behavior. The previous dependency on local storage has been replaced, and a Redis caching approach is now implemented for the users to sign in on the Landing application for accessing consumer applications (SubCon Admin, SolCon & CMS).
Following the new implementation, users can access any consumer application only through the Landing application.
If a user has opened different consumer applications on different tabs in a browser, logging out from one application will force the user to log out from the other opened applications as well. The user will regain access to the application only by signing in through the Landing application.
Page refresh will work as before and have no impact following the redesign.
Multi-Factor Authentication (MFA) with Okta will also work as intended if the feature is turned ON for the specific client.
There is no dependency on third-party cookies related to the Landing application, and the landing works perfectly fine on Safari, Firefox, Chrome, and Edge browsers.
Consumer applications are no longer dependent on Local storage to fetch data.
The CMS Idle Time functionality, which notifies the user if they have been inactive on a CMS page for an extended duration and provides the option to either continue or exit from the page, is working as before.
For a seamless user experience and as a best practice, please do not disable cookies in your browser.
This fix is also merged to 3.16.0.15, 3.16.2.8, 3.16.3.13 & 3.17.0.3 releases.
The document contains the major new features and changes in the minor 3.16.1 release. It also documents known problems and workarounds, if any
DISCLAIMER
Product Information contained within this document, including technical information and functional specifications, is subject to change without notice. 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.
This is a complete document. The last changes were made Oct 11th 2022.
3.16.1 is a minor release hence it does not contains any breaking changes, but mostly enhancements, bug fixes and several small new features. The new features supported are related to corporate subscription and registrations, localization and the Landing app.
Please note that upgrades to this version are no longer available since the Amazon S3 bucket now requires a minimum of TLS 1.2 security protocol, which is not supported by this version.
Note added on June 20th, 2023.
The release notes for the internal stakeholders can be found in Confluence (access required)
Please note that the minor release will include all the hotfixes. The hotfixes documentation can be found at 3.16.0.X hotfixes
The following new features appear in this release
Registration not required to send an Invitation
Until this release, for an invitation to be sent at least one registration linked with the subscription used to be required. Starting from this release an invitation for registration can be sent even without having an existing linked registration.
The visibility of the button is configured by UserAccountSearchDetailsInviteButton APP setting. To enable the feature, set the key to 1. The setting also controls the usual Invite button in the registration grid visibility.
Pre-requisites: N/A
Sign in through Invitation email
The user invited to join a corporate digital subscription can now accept the invitation received via their email and sign in to access the newspaper.
The recommended setup is:
in One CSR Portal go to Event Management tab -> Event Types -> Even Type Emails
select the Invitation Send Event Code and click Edit
in the Update Transaction Email Id window go to the Customer Email tab and select the Subscription Share Invitation option in the Template dropdown
Add the newly created CMS Attribute to the email text and Save
Pre-requisites: N/A
Account Management localization
The following items are now manageable via CMS and hence can be translated to the local language:
The payment gateway setup. Please note that a specific page has to be created for each payment provider (e.g. StripeIframe, SpreedlyIframe etc)
The error message/notification for the unsuccessful payment/invalid payment - a customized page dedicated to every external payment gateway has to be created
getAvailableDatesFailed Page: CancelSubscription
submitPaymentSuccess, submitAutoPay Pages: autopay sign up, manage add tip)
createPaymentMethodFailed and CreditCard.InvalidField Pages: CommonIframe (for Bank Accounts, createPaymentMethodFailed only), StripeIframe, SpreedlyIframe, PeachPaymentIframe, PaywayIframe, BraintreeIframe, CybersourceIframe, AuthorizeNetIframe - Note updated Oct 4th 2022
Payment option's table headers at the AutoPaySignUp page - Note updated Oct 4th 2022:
AutoPaySignUpHeader.Amount
AutoPaySignUpHeader.Term
AutoPaySignUp.NoOptionsText
Days of the week and months in the Date picker, please find the titles of the added fields in CMS, the fields were added to the Layout page:
LongDayName.XXX
ShortDayName.XXX, where the XXX is the name of the day of the week
LongMonthName.YYY, where the YYY is the name of the month
The lookup dropdown options at Verify Account page, please find the titles of the added fields in CMS:
Content: Lastname Segment: PrimarySearchTypeLastNameText
Content: Company Name Segment: PrimarySearchTypeCompanyNameText
Content: Account Number Segment: SearchTypeAccountNumberText
Content: House Number Segment: SearchTypeHouseNumberText
Content: Zip Code and Phone Number # Segment: SearchTypePhoneNumberText
Content: Share subscription Segment: ShareSubscriptionHeaderText
Content: Payment Segment: SaveTimeWithEzPayTitle
Page names in notifications (used to be hardcoded in English
Page: Home Content: Home
Page: MG2Auth Content: MG2Auth
Page: SelectAccount Content: Select Account
Page: VerifyAccount Content: Verify Account
Page: MyProfile Content: My Profile
Page: Feedback Content: Feedback
Page: Preference Content: Preference
Page: Unsubscribe Content: Unsubscribe
Page: Address Content: Address
Page: ForgotPassword Content: Forgot Password
Page: Complaint Content: Complaint
Page: FAQ Content: FAQ
Page: TemporaryStop Content: Temporary Stop
Page: Payment Content: Payment
Page: AutoPaySignUp Content: AutoPay
Page: AutoPayManage Content: AutoPay
Page: AutoPaySignOut Content: AutoPay
Page: AutoPayAddTip Content: AutoPay
Page: EBillSignUp Content: EBill Sign Up
Page: EBillManage Content: EBill Manage
Page: EBillInvoice Content: EBill Invoice
Page: SubscriptionShare Content: Subscription Share
Page: InvitationConfirm Content: Invitation Confirm
Page: Dashboard Content: Dashboard
Page: SubscriptionCancel Content: Subscription Cancel
Page: SubscriptionRestart Content: Subscription Restart
Page: TemporaryStopTransfer Content: Temporary Stop Transfer
Page: TemporaryStopRestart Content: Temporary Stop Restart
Page: SubscriptionUpdate Content: Subscription Update
Page: Activate Content: Activate
Page: Rewards Content: Rewards
Page: StopSaver Content: Stop Saver
Page: Transactions Content: Transactions
Status description of the Subscription
Placeholder content for the following Account Management pages can now be created via CMS: Complaint, Address, Feedback, Verify Account, Share Subscription, Phone number, and Cancel Subscription pages:
Placeholder.ZipCode Pages: Address
Placeholder.SelectOption Pages: Activate, Feedback, VerifyAccount, SubscriptionShare, Address and CommonIframe (recently created for bank account iframe) pages
Placeholder.CCName Pages: BraintreeIframe. Please note that a specific page has to be created for each payment provider
Placeholder.SelectReason Pages: StopSaver, SubscriptionCancel and TemporaryStopTransfer
Placeholder.SelectCategory Pages: Preference
Placeholder.SelectIssue Pages: Complaint
Placeholder.EnterAddress Pages: Address and TemporaryStopTransfer
Placeholder.EnterCity Pages: Address and TemporaryStopTransfer
Placeholder.EnterZipCode Pages: Address and TemporaryStopTransfer
Placeholder.EnterFirstName, Placeholder.EnterLastName, Placeholder.EnterEmail, Placeholder.EnterLocation, Placeholder.EnterComments Pages: Feedback
Password change, Transactions, and Temporary Stop changes (hardcoded message removed) for Transactions and Temporary Stop Transfer pages:
Content: Transactions Segment: Transactions.NoHistoryPaymentsText
Content: There are no Transfers Segment: TemporaryStopTransfer.NoTransfersTe
Content: Enter your email address to create a new password. Segment: ForgotPasswordForm.Description
Pre-requisites: N/A
Subscription Panel localization
The following items are now manageable via CMS and can be translated to the local language:
the error message for the unsuccessful payment/invalid payment; the error generated by the external payment gateway is overridden
Pre-requisites: N/A
Access to Support Viewer via Landing
The user who is authenticated to access the Support Viewer application now can access it via Landing.
Support Viewer being visible on the Home page of the Landing app does not imply that the user has access to the application. If access is needed, it has to be requested from Admin. If the user is not authenticated and tries to access the Support Viewer app, then the Login credentials are deactivated. For the user to be able to access Subscribe applications again the credentials have to be re-activated by the Admin user. Please note that for now Support Viewer is meant for Naviga support only. More functionality is expected in future releases
Pre-requisites: N/A
The following enhancements were introduced to the existing features
Complaints when on Vacation
Pre-requisites: NCS circ, all versions Tested on: NCS Circ 2020-3.0
Initial Auth0 Screen modification for Account Management
When a user wants to subscribe/activate his Digital account, initial authentication is made easy by enabling the Register tab for the users.
If the user already has a digital subscription, then the Login tab would be active by default instead of the Register tab.
Pre-requisites: N/A
Special characters removed from certain parameters
No special characters are supported in the name fields, address 2 fields, or cardholder name fields. All the exceptions are listed below:
First Name: ' - & / .
Last Name: ' - & / .
email: @. + - _ ,
Cardholder Name: ' - & / # .
House number: / -
Unit number: No Special Chars
Pre-requisites: NCS circ, all versions Tested on: NCS Circ 2020-3.0
Payment Terms for Comp Subscribers
As comp (complimentary) subscriptions are meant to provide free access to the content for the employees and other support staff of a Newspaper publication, events are configured in such a format that for Subscription Kind of ‘Comp’ category, are not fired for payment purpose
Pre-requisites: NCS circ, all versions Tested on: NCS Circ 2020-3.0
Restart events order rectified
RESTART PAYMENT event meant for Payment activation for stopped subscriptions used to fire before the occurrence of RESTART SUBSCRIPTION event. The wrong order of firing events is rectified
Pre-requisites: Matrix, all versions Tested on: Matrix 38.0.034.ITSP5
Carrier Collect restriction for Billing method in CMS
Carrier Collect restriction is present in the Hide links for dropdown in the Links section of the Navigation tab
Pre-requisites: N/A
Hardcoded Message about Software Update removed
There used to be a Modal (Message) window for an API with new functionality to notify the user about the new software update. When the system is up and running, the notification serves no purpose so that was removed. Note: The hardcoded message can be configured from CMS for SWUpdate.Text and SWUpdate.Title segments for Layout (Filter by page drop-down) page. Note updated Oct 4th 2022
Pre-requisites: N/A
Close button added in Solicitor Concierge
A close (x) button is added to the top-right corner of the Offer group
Pre-requisites: N/A
American Express card logo removed
On the payment page in Account Management the Card logos for American Express and related card logos were removed (AmericanCardImages setting set to false. Hiding images setting set to false)
Pre-requisites: N/A
The following bugs were fixed in this release
Encoded Subscriber’s Email not accepted
When the user creates a new subscription through Subscription Panel the PurchaseAPI is being called to process a new subscription start. One of these steps is CreateSubscriber in DTI Circulation System. Purchase API was sending an encoded email and DTI API cannot process the same as special characters are not accepted by DTI Circ which caused an error that has been fixed.
Pre-requisites: NCS circ, all versions Tested on: NCS Circ 2020-3.0
Invalid Input for a New Subscription
The PurchaseAPI was not sending proper input for Address and no subscription id was created. As for the new subscription, the system has to generate the Subscription Id by default. This type of subscription is said to be a billed one which means no payment details are required as this is for internal staff of the client or publication.
Pre-requisites: Matrix, all versions Tested on: Matrix 38.0.034.ITSP5
Create Reward returns an unexpected error
An unexpected error was shown when adding a new Reward if there was already at least one Reward. The error message is fixed, a friendly validation message is displayed
Pre-requisites: N/A
Creating a scheduled reward with a start time before the end time
While creating a new reward for a Newspaper client, the Start time later than the End time was acceptable by the system. This behavior is rectified and the system is functioning fine. While creating the reward, if a later date was entered for the start time compared to the end time, the API is giving out an error to notify the user. This is further rectified to give out an appropriate or clear message as “Error! start date can not be greater than or equal to end date”
Pre-requisites: N/A
Error message when a Reward is saved successfully in CMS
While creating the reward, if a later date was entered for start time compared to end time, the API is giving out an error to notify the user. When the error is rectified by entering the correct dates, the Reward details are saved but still, the validation error continues to appear. The only difference it disappears after a few seconds.
Pre-requisites: N/A
The credit card number not encrypted in PurchaseAPI
In Subscriptions API the credit card number is encrypted (does not matter if it is masked) but in Purchase API this functionality was deprecated in 3.16.1 due to being moved to Payments API during its refactor, which is planned for 3.17.0. Still, we need to encrypt the credit card number in the 3.16.X Releases, because otherwise the masked credit card number will not be displayed in the subscription account. In scope of this fix we added credit card number encryption to PurchaseAPI. Note updated Oct 11th 2022
Pre-requisites: N/A
EZPay payment method update resets recurring tip - bug fix
Prior to the fix sometimes when a payment method used for ezpay was updated, the recurring tip was reset. To fix that now TipAmount=null is allowed in case tip amount was not updated during the call. Note updated Oct 11th 2022
Pre-requisites: NCS circ, all versions Tested on: NCS Circ 2020-3.0
Paypal direct integration change to Auth and Capture - bug fix
Paypal Do Express checkout was failing because the API was performing a Sale transaction (TRXTYPE=S). In scope of this fix we updated integration to have Authorize (TRXTYPE=A) and Delayed Capture (TRXTYPE=D) types of transactions Note updated Oct 11th 2022
Pre-requisites: N/A
Stop options not being displayed when scheduling a Permanent Stop in One CSR Portal - bug fix
When trying to schedule a Permanent Stop in One CSR Portal an error message “There are no stop options available for this subscription“ was thrown instead of “Schedule cancellation without refund“ and “Schedule cancellation with refund“. To fix that missing dependencies were added to the component constructor. Note updated Oct 11th 2022
Pre-requisites: N/A
The routable check adds Addresses that do not exist in NCS Circ
New starts were blocked by the Routable check when using addresses that do not exist in NCS circ. The routable check flow was reworked to add Addresses that do not exist in NCS. Note updated Oct 11th 2022
Pre-requisites: NCS circ, all versions Tested on: NCS Circ 2020-3.0
Upgrade/Downgrade not allowed with Temporary stop settings - bug fix was moved to 3.16.2 Note updated Oct 11th 2022.
in CMS please create the new and set the login URL at the attribute value.
Users can and handle the .
Complaints are now supported for paused (status P) subscriptions or subscriptions on vacation (status V). The feature is available both for One CSR Portal and Account management. More info about Complaint functionality can be found . The client can decide(by publication) to expose or hide the complaint option.