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 3.16.3.x hotfixes are by default included in the next higher release. However, if a Hotfix branch of 3.16.3 is released after the next higher version, the corresponding Hotfix will be merged into the latest sub-version of the higher release applicable at that time.
Please input a Salesforce case if you want the fix to be applied.
Note: This page covers hotfixes starting from release 3.16.3.11.
Bug Fix
Account linking issue in the Gift redemption workflow
After redeeming a gift, when an existing user clicked on the 'Sign in' button and entered the previously used credentials, they were prompted to verify the account in order to sign in to the SubCon Site. This issue has now been resolved.
Application Covered:
Self Service
Updated on 17 Sep 2024
Removal of Special Characters Encoding
The encoding of special characters has been removed due to issues arising when the rate code length exceeds 20 characters in the circulation system after encoding.
Bug Fix
Error message when subscribing via ApplePay Braintree
The transaction failed when a user attempted to purchase a subscription using ApplePay via Braintree, and an error message was displayed. This issue has now been resolved. After the fix, users can successfully complete their subscription transactions through the Subscription Panel using ApplePay via Braintree, without encountering any error messages.
Application Covered:
API
Attention: Refactor
1. SL Refactor
Updating an existing Sales Team with a large data set (such as adding many offer groups and/or team members) was causing time-out errors. The Sales Teams update functionality has been refactored to address this issue for performance enhancement.
There are no functional changes. It is now possible to successfully update large numbers of offer groups or sales team members within existing Sales Teams without encountering time-out errors. After the refactoring, the performance has significantly improved while updating the sales team.
This fix is also merged into 3.17.0.2, 3.17.1 & 3.17.2 releases.
2. Enhanced Sign-In Mechanism of Landing Application
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, starting with this release, 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.1.10, 3.16.2.8, & 3.17.0.3 releases.
Bug Fixes
1. Issue with In-App Subscription Purchase
This intermittent issue was specific to Apple's in-app purchase. When users purchased subscriptions through the Apple app (V1) via in-app purchase, the corresponding transaction was not reflected in the Subscribe database, and the user was unable to access the website. The issue occurred because Apple was intermittently sending receipt tokens larger than the int32 data type could handle. This has now been resolved. After the fix, Apple V1 in-app purchases are correctly updated in the Subscribe database, and users can access the website without issues.
2. Removal of Special Characters Encoding
The encoding of special characters has been removed due to issues arising when the rate code length exceeds 20 characters in the circulation system after encoding.
This fix is also merged into the release 3.17.0.2.
Applications Covered:
API, SolCon
Attention - Enhancement
1. Merchant Password in the P12 file for Cybersource
Following an urgent update regarding the P12 merchant file for Cybersource keys, Subscribe will now send Password, Filename, and Merchant ID to ensure successful payment transactions with the Cybersource payment gateway. Previously, only the Merchant ID was included in the Cybersource request.
Note that the Merchant ID and Filename values remain the same in the Cybersource request.
Implementation Notes:
A new Api setting key CyberSource.Password has been introduced to get the Cybersource password from MG2 database.
This fix is also merged to 3.17.0.3 release.
Bug Fix
Subscription failure while using Amex Credit card with Apple Pay
When a user tried to pay the subscription amount via Apple Pay with American Express credit card, the transaction failed. This issue has been resolved. After the fix, user can successfully purchase a subscription with American Express credit card via Apple Pay.
This fix is also merged to 3.17.0.4 release.
Application Covered:
API
InApp subscribers not getting website access
Users who successfully purchased subscriptions via In-App Apple Pay and were created in Subscribe did not gain access to the website. This issue was due to the large download_id sent by Apple Pay, which led to incomplete user details being recorded in Subscribe and thus preventing website access.
This issue has been resolved. After the fix, the details of successful In-app Apple Pay subscriptions are now updated correctly in Subscribe, ensuring that subscribers gain valid access to websites as per their subscriptions.
This fix is also merged intothe 3.17.0.4 and 3.17.1.1 releases.
