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.17.0.X hotfixes are, by default, included in the minor version currently in development, which is 3.17.1, and all subsequent releases.
If you want the fix to be applied, please raise a Salesforce case.
Issues in Share Subscription Flow:
When users shared their subscription with someone and the recipient tried to accept the invite, they encountered an error. This issue has now been resolved.
When CSRs were sending invites using the 'Invite without registration' button, the request was previously failing, and this issue also has been fixed now.
Error while updating Subscriber details
Whenever the user edited the account details, especially the phone number, on the Subscriber/Update page of the SubCon Site, an error message from the Circulation system was displayed saying, “New start failed: Could not update occupant.” This issue was occurring for clients outside the US & has been resolved. After the fix, the user can update account details without encountering an error message.
Auth0 error message not displayed
While attempting to subscribe through the Subscription Panel, if the user entered a password that did not meet Auth0's rules (e.g., a password with fewer than 8 characters), the error messages from Auth0 were not displayed, preventing the user from proceeding with the subscription. This issue has now been resolved.
Following the fix, users will receive appropriate error messages whenever an error occurs during the subscription process.
Error while updating user profile in SubCon Site
When the user tried to select the ‘Update profile’ menu after logging in to the SubCon Site, the system threw an error message: ‘Invalid input’, unless the page was refreshed. This issue has now been resolved. After the fix, the user can select the ‘Update profile’ menu and successfully update their profile data without any error messages.
Title property of 'ApplePay Braintree V3’ component
The Title property of the 'ApplePay Braintree V3’ component has been changed from 'html type' to ‘text type'.
Updating an existing Sales Team with a large data set (such as adding a significant number of offer groups and/or team members) was causing time-out errors. To address this issue, the Sales Teams update functionality has been restructured for performance enhancement.
There are no functional changes. After the refactoring, the performance has significantly improved. 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.
This fix is also merged to 3.16.3.13, 3.17.1 & 3.17.2.
Bug Fixes
Display Name not getting auto-generated
For MG2 Auth clients, when a user attempted to register on the site by providing an email ID and password without entering a display name, the display name was not auto-generated for the newly registered user. This issue has been resolved. After the fix, even if the display name is not provided by the user during registration, it is now auto-generated in the backend.
Errors while updating Display name and email in Self-Service
Previously, when a user tried to edit their Display Name or email ID from the My Profile page the system displayed error messages. These issues have been resolved. After the fix, users can successfully edit the Display Name or email ID from the My Profile page without encountering any error messages.
Implementation Notes:
A new MG2 Control Api setting key SubCon.IgnoreProvider has been introduced. When the value of SubCon.IgnoreProvider is set to true (1), the API does not interact with the Auth system, meaning the identity providers are ignored. When the key value is set to false (0), the API request interacts with the Auth system, which could be MG2 Auth or Auth0, depending on the configuration.
Error while updating address via Self-Service
When the user tried to edit the Billing or Delivery address, the system displayed an error message saying, “Address Second Pass,” and the user was restricted from changing the address. This issue was specific to CircPro clients and has now been resolved.
Subscriber Update issues in Self-Service
The following issues on the Subscriber Update page have been resolved:
The user was unable to update the email ID due to an error message displayed by the system. This issue occurred when the user tried to update the email ID to one that already existed. This problem was caused by an internal validation that restricted the usage of the same email ID in two accounts. After the fix, the user is now able to update an Email ID that is already available in the Subscriber table with a different subscription.
There was another issue specifically observed for users who did not have an email ID saved in NCS Circ. When these users tried to update their details from the Subscriber page, the SUBMIT button was greyed out, preventing them from completing the update. This issue has also been resolved. After the fix, the email field is now optional on the Subscriber Update page. Users can update the subscriber details even if the email field is left blank.
When a user tried to update their phone number by entering a new number after clearing the existing one, the update was successful. However, it was observed that when the user attempted to change the digits of the existing number after the parentheses displayed in the field (area code enclosed in parentheses), the system displayed an error message, preventing the update. This issue has now been resolved.
Error while updating Profile Information in Self-Service
After editing profile information on the My Profile page, users encountered an error message while clicking the SUBMIT button, and the update failed. This issue has been resolved. Following the fix, when a user edits the First Name and/or Last Name, the update is now successful without any errors.
Implementation Notes:
Set the value of MG2Control key SubCon.IgnoreProvider True or False (0 or 1). The default value of the key is True.
Issue in creating a subscription
This issue was specific to CircPro clients. When a user attempted to subscribe with EZPay, the subscription was unsuccessful if the circulation system was CircPro. This was due to a mismatch between the Pac term values set up in the SolCon offer and the Pac terms in the circulation system. This issue has been resolved.
Issue in Restarting subscription from the Subscription Panel
This issue was specific to CircPro clients using the payment vendor Authorize.net. When users attempted to restart subscriptions from the Subscription Panel, it failed. This issue has been resolved. After the fix, the CircPro clients with Authorize.net payment vendor can successfully restart a subscription from the Subscription Panel.
Post login error for recently subscribed users with previously stopped subscriptions
When a user with a previously stopped subscription purchased a new subscription and tried to log in to the self-service portal, they encountered an error message stating 'Max Linked Subscribers.' As a result, the user was unable to verify their account and log in to the site. This issue has now been resolved.
Removal of Special Characters Encoding
The encoding of special characters has been removed due to issues arising when the rate code length exceeded 20 characters in the circulation system after encoding.
This fix is also merged to 3.16.3.13.
Applications Covered:
API, Self-Service, SolCon
Attention - Enhancement
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 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 into 3.16.1.10, 3.16.2.8, 3.16.3.13 & 3.17.0.3 releases.
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.
This fix is also merged into the 3.16.3.14 release.
Redeployed the deprecated /DigitalAccess endpoint
The /DigitalAccess (POST) endpoint was deprecated in Subscribe version 3.17 as part of a major API refactoring. However, to ease the migration, this endpoint has been made available again.
Bug Fixes
Improper Notifications when Linking an Account
When a user linked an SS account with an existing subscription, the success notification displayed HTML tags along with the message text. This issue has been resolved. After the fix, notification messages are displayed correctly with the intended styling (e.g., bold text) and without any visible HTML tags.
Implementation Notes:
The existing property “EnableHtml” in Subcon.config should be set to true → "EnableHtml": true (for converting HTML tags).
Tax not getting included in the payment
If a potential subscriber switched the payment method while making the payment, the tax was getting skipped. The issue has been fixed now.
After the fix, while purchasing a subscription, the Tax is included along with the subscription cost irrespective of the Payment method selected.
Issue with In-App Subscription Purchase
This intermittent issue was specific to Apple's V1 in-app purchase. When users purchased subscriptions through the Apple app via in-app purchase, the corresponding transaction was not reflected in the Subscribe database. Subsequently, the user was unable to access the website. This issue has been resolved. After the fix, the Apple in-app purchases are updated in the Subscribe database correctly and the users can access the websites too.
This fix is also merged into the 3.16.3.13 release.
Error while linking Email ID to subscription
Subscribers for specific clients using dedicated Auth connection per Publication were getting a 'Max Linked Subscribers' error when the same user had subscriptions for more than one publication. The issue has been fixed now.
Reward details not displayed
When the user selected a Reward from the Rewards page, instead of navigating the user to the Membership Rewards page where the user can enter the details to claim the reward, the loader kept on spinning on the Rewards page. This issue has been resolved. After the fix, when the user selects a Reward from the Rewards page, the user is navigated to the Membership Rewards page successfully, and can enter the user details and submit it for claiming the reward.
Non-deduction of Donation amount while signing up for Auto-renew
When a subscriber entered a donation amount during auto-renew sign-up, it was not getting submitted and subscribers were not charged. The issue has been fixed. In addition, the donation is now displayed as part of the one-time payment being made other than the amount for auto-renew sign-up.
User Name not reflected in SubCon Admin after Registration via Engage
Even though the User Registration template in the Engage included First Name and Last Name fields, the user name details entered during user registration were only captured by the Auth0 and were not reflected in SubCon Admin for the corresponding user after a successful registration. This issue has now been resolved.
Error message when subscribing via ApplePay Braintree
When a user attempted to purchase a subscription using ApplePay via Braintree, the transaction failed, 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.
This fix is also merged into the 3.16.3.12 release.
Error in specific cases for Email IDs with special characters
In certain workflows Subscribe uses GET /Users?Email endpoint. It was breaking for email IDs with special characters such as the "+" sign thereby affecting the workflows like Gift subscriptions, Invitations, etc. This issue has been resolved.
Forget Password email not received
Whenever a user clicked on the “Forget Password” link in the Digital tab for an MG2 Auth user, though a success message was displayed, the corresponding email was not actually received by the registered user. This issue has been resolved.
Entitlements API - GET Method not inserting data in Access Log
The GET method implemented for the DigitalAccess endpoint did not insert data into the Access Log. This issue has been resolved.
After the fix, if the GET method is implemented for the DigitalAccess endpoint, user data is inserted successfully into Access logs. Additionally, in the POST API, the parameter accessLevelCode is included in the response to provide entitlement information.
Issues in canceling a subscription
The issue that prevented users from canceling subscriptions due to an error message has now been resolved.
