2025.1
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 release is currently in its Beta version.
Subscribe 2025.1 introduces a key feature of Email verification during New Starts using Auth0. The release also includes some minor enhancements and bug fixes.
Release Prerequisites
ENGAGE
2.8.7.2
NCS Circ
2025.0.0 (If using Variable Pricing) 2020-6.3 (if not using Variable Pricing)
Subscribe Extracts
Australian Clients - Extract Version 6 Other Clients - Extract Version 5
Sync Jobs
2025.1
Circ Pro
2023-2.0
DSI (Saxo Circ)
NOT SUPPORTED
Naviga Pay (if using)
2.2
Key Feature - Auth0 Email Verification
With this new enhancement, all users accessing the Subscription Panel to purchase a new subscription will undergo an email verification process managed by Auth0. This verification acts as a vital step before the payment stage, which can reduce the recent rise in carding attempts.
The process works as below:
New Email Address:
If the end-user enters an email address not found in the database, Auth0 creates a new user profile, verifies the email and the user will be allowed to continue with the subscription purchase.
Existing Email Address:
If the email entered by the end-user already exists in the database, it can be either a verified address or an unverified address:
Verified Email address: The user can proceed with the purchase flow.
Unverified Email address: Auth0 prompts the user to complete the email verification process first, before proceeding to the purchase flow.
This enhanced purchase flow ensures that only verified users proceed to the payment step, improving system security and preventing carding attempts.
General Enhancements
Subscription Panel
1. New GIF loader image
A new provision has been added to the Subscription Panel, allowing clients to load a custom GIF image to display to end users if the SP takes longer to fetch and display offers on the page. Currently, a generic spinner is shown. To make the loading experience more engaging, clients can replace this spinner with a GIF image uploaded via the config file. This helps effectively communicate to users that the application is fetching suitable offers for them.
Refer to the GIF given below for your reference:
Implementation Notes:
The Config file must be placed at the Publication level and should contain the following keys in the below specified structure to ensure the loader GIF is visible to end users.
The config.Loader key must include both the ImageName and LoaderText to display the loader image and message.
The loader image must be placed in the
/client/imgfolder of the project structure, following the above-specified naming convention.The loader text is displayed as plain text. HTML formatting (such as color or font size changes) is not supported. The font size and color of the loader message are fixed by design.
2. New Data Layer Variable for GTM Container
A new data layer variable has been introduced for the internal GTM container in SP. This data layer variable can be included in the GTM.js script call from layout.pug for all clients, based on a configuration key. The client's GTM.js will load with the data layer variable if it is defined in the publication-level config.
Note: Changes have been implemented for all client containers.
Implementation Notes:
Add the key
DataLayerinsideconfig.Tracker.GoogleTagManagerwith any string value that maps to the client's data layer variable name.The data layer addition now supports multiple container options, each added within individual container arrays.
API
Saving Encrypted Registration IDs up to 150 characters
Registration records can now store encrypted Customer Registration IDs of up to 150 characters in the database when creating new registrations.
Bug Fixes
SubCon Admin
1. Unlinking registration changing user type
When the CSR unlinked the registration of a subscribed user from a stopped subscription, the ‘Owner’ status of another existing active subscription of the user got changed to ‘Guest’, which was not expected. This issue has been resolved now. After the fix, if the subscribed user has multiple subscriptions, unlinking a registration from a subscription does not affect the status of the remaining subscriptions.
2. Title “Search result” missing from the Event Processor Responses page
The issue of the “Search result” title missing from the Event Processor Responses page (Event Management > Event Processor Responses) has been resolved. After the fix, the title now correctly appears above the search result table.
3. Empty drop-down for REDEEMGIFT event
The ‘Events’ drop-down displayed while clicking the ‘Send Sample’ button on the ‘View all emails’ tab (Event Management > Event Types Emails > Filter by (Event Type Id), Contains (1101) > Search > Edit > View all emails > Send sample > Events) was blank. This issue has been resolved. After the fix, the drop-down now correctly lists the event data as expected.
4. Reason for cancellation/Downgrading not displayed in SubCon Admin
When a subscription was canceled or downgraded through the Self-Service portal, the selected cancellation reason was not reflected in SubCon Admin for the corresponding subscription. This issue has been resolved. Now, when a subscription is canceled or downgraded via the Self-Service portal, the reason is correctly displayed in SubCon Admin for the associated subscription.
5. Spinner display on Email Preferences tab
The issue of a persistent loading spinner appearing when accessing the Email Preferences tab has been resolved. After the fix, if no email preferences are set for a particular newspaper, an appropriate message ("There is no data to display") will be shown upon accessing the Email Preferences tab; otherwise, the corresponding email preferences data will be displayed.
6. Tip Amount not considered during Autopay Sign-up
While signing up for Autopay, if the end user included a tip amount, it was not captured or reflected in the EZpay events and NCS records. This issue has been resolved. After the fix, the tip amount paid during Autopay sign up-is correctly captured and reflected in both the EZpay events and NCS records.
Self Service
1. The unresponsive Cancel button
The Cancel button on the “Manage AutoPay” page was unresponsive while editing the current payment method for an active subscription of an NCS client. Clicking the Cancel button did not close the ‘Edit’ section as expected. This issue has now been resolved. After the fix, clicking the Cancel button properly closes the editing section on the “Manage AutoPay” page.
2. Issue with the Cancel button
The Cancel button on the AutoPay Cancelation (/autopay/signout) page was not working. To address this, it has been replaced with a Go to Dashboard button. When users click this button, they are redirected to the Dashboard page, as indicated. See the image below for your reference.
Implementation Notes:
In CMS, the content "RejectCancel.CancelButtonText" is removed for the AutoPaySignOut, and instead, "ButtonGoDashboard" has been added.
3. Issue in Sharing Subscription
When a subscriber sent an invitation to a recipient's email ID for sharing the subscription, the recipient was unable to log in to the Self-Service portal using the email ID (the one on which the invitation was received). An error message was displayed stating that the email was already registered.
The issue was due to a case mismatch between the email IDs stored in Auth0 and the Subscribe database. This issue has now been resolved. After the fix, the Self-Service portal will ignore case differences between email IDs stored in Auth0 and the Subscribe database. As a result, users can log in successfully regardless of case variations in their registered email addresses.
5. Updating Email with an existing Email ID
Previously, end users were able to update the Email ID field with an existing email ID through the /myprofile page of the Self-Service portal. After this fix, the SUBMIT button on the /myprofile page will be enabled only if there is a change in the existing Display Name or Email ID.
6. Missing Options in the Dashboard
When navigated from the Manage Subscriptions (/selectaccount) page to the Dashboard page, some of the hyperlink options were missing. This issue has been resolved.
After the fix, when navigating to the Dashboard, the papercode in the URL updates based on the selected subscription. The Dashboard options are available as per the configurations in the CMS as expected.
7. Incorrect Phone Number Format on Initial Load
When the Subscriber Update (/update) page was accessed for the first time, the Phone number was displayed in an incorrect format. However, upon refreshing the page, the phone number displayed correctly. This issue has now been resolved.
8. Label alignment issue on Dashboard
The misalignment of the frequency of delivery (day names) labels on the SS Dashboard has been resolved.
API
1. Start call in SubCon Admin updating the House-hold level
The logic that updated the HouseHoldLevelId to the default value set against the ApiKey "DefaultHHSubscriptionLevel" for active subscriptions in the HouseHoldLevels table during a 'Start call' from One CSR Portal been removed. It is now ensured that the HouseHoldLevelId is no longer overridden by default values from the database during Start call from SubCon Admin.
2. Not able to access Autopay Signup page and missing ‘Pay now’ button
Accessing the Set up Autopay (autopay/signup) page from the SS Dashboard resulted in an error message stating, “The subscription was unable to be opened as it is in an invalid status.". On the Payment page, the Pay Now button was absent, preventing users from completing payments. These issues have been resolved.
This issue occurred because the selected subscription did not have a Phone number. After the fix, it is now possible for the end user to sign up for Autopay or make payments even if the Phone number is empty or has a value NULL.
3. Duplicate Subscription creation issue in Kiosk (LTE Starts)
It was observed that while purchasing a new subscription using the Kiosk (LTE Starts), end users could navigate back to the previous page and resubmit the purchase request again. This issue was occurring specifically for future subscriptions where the start date is a future date. This resulted in multiple duplicate subscriptions being created. This issue has now been resolved. After the fix, the user will be restricted from creating duplicate subscriptions for future start dates.
Precondition: To invoke Active Sub-check in the backend for new starts, it is recommended to switch on the SolCon flag ‘No Existing Subscription’ (Offer Groups > Additional Options > Subscription Validation) while creating the SolCon offer group.
4. All Offers not returned
The issue where all offers were not being returned in the API response from SolCon for the /Offers API endpoint — regardless of the source system (such as SubCon Site, Subscription Panel, Direct Sales, SubCon Admin, Engage, In-App, or any other external platform) — has been resolved. After the fix, all valid offers configured in SolCon are returned correctly, irrespective of the source system.
SolCon
1. Error while Saving as New
Clicking the "Save As New" button to create an Offer Group from an existing one triggered a UI validation error without displaying an error message. This issue has been resolved.
After the fix, while creating a new Offer Group from an existing one using the "Save As New" button, the Offer Group name field will be cleared, allowing the user to enter a new, unique name for the group. The entered name will also automatically populate the Offer Group Code field under Additional Options by default.
If the user attempts to save the new Offer Group as a Draft or Publish without a name or with an invalid name, both the name and Offer Group Code fields will be highlighted, and focus will be set to these fields. An error message stating “Name is required” will appear below the Offer Group name field. Additionally, another message, “Offer Group Code is required. By default, the application generates this value based on Offer Group Name.” will display below the Offer Group Code field in Additional Options.
2. Issue with Offer Groups Auto-Selection Across Sales Platforms
While creating a new Sales Team, selecting each Sales Platform caused offer groups from previously selected platforms to be added to the current Sales platform. This issue has been fixed. After the fix, when creating a new Sales Team, the offer groups selected for a specific sales platform will not carry over to others.
3. Unable to create Offer when No Rate code available
Previously, while creating a Comp offer in SolCon, if Rate codes were not available from the Circ system, the Reason code field appeared as a blank drop-down list, preventing users from creating the offer. This issue has been resolved. Now, there is no dependency on the Circ system for Rate codes when creating a SolCon Comp offer. If Rate codes are unavailable, the Reason code field becomes a free text field, allowing users to input the appropriate reason and proceed with offer creation without restrictions.
4. Term Length field goes Editable after Publishing an Offer Group
Whenever a Rate Code is selected, the system fetches the associated Term Length data from Circ and displays it in a drop-down. Previously, after publishing the Offer Group, the Term Length drop-down was changing to an input box, giving users the wrong impression that the Term Length could be edited. This issue has now been addressed. After the fix, the Term Length drop-down remains a drop-down even after publishing the Offer Group, preventing users from editing the Term Length.
5. Unable to edit the existing offer
Previously, while adding new payment methods and saving them as a draft to an existing offer, the checkbox selections of already selected payment methods would disappear from the SolCon UI. This issue has been resolved. After the fix, all selected payment methods are displayed correctly when saving the draft.
Subscription Panel
1. Subscriber’s name displayed twice on subscription confirmation page
The issue of subscriber’s name appearing twice on the subscription confirmation (congratulatory) page has been fixed.
Implementation Notes:
Enable the PaymentInformation Show property in the Confirmation component.
2. Subscriber details captured from the Billing address instead of the Delivery address
During new starts, if a subscriber's billing and delivery addresses differed, Subscribe would capture subscriber details, such as first and last names, from the billing address. This issue has been resolved. Now, during a new purchase, if the delivery and billing addresses differ, Once CSR Portal captures and reflects subscriber details from the delivery address as expected.
3. Issue with ApplePay transaction in FullPage Display
When users selected Apple Pay as their payment method during the new start flow with the Presentation's DisplayType set to FullPage, they were unable to place the order for the new start flow. This issue has been resolved.
After the fix, the flow works as below:
Tax Calculation and Reauthorization: If the user's address requires tax calculation, the system prompts the user with a pop-up message requesting them to click the Pay button once more. This reauthorization is necessary as the total payment now includes both the subscription cost and applicable taxes.
Order Completion: After reauthorization, the user is presented with the Order Summary, where the final payment is processed.
These changes ensure a smoother and more reliable payment experience for users selecting Apple Pay in the FullPage display mode.
4. Reauthorization Message issue of ApplePay V3 Component
The Reauthorization message for the ApplePay payment method was not being retrieved from the 'Errors ReAuthorize' property in the ApplePay V3 component within the CMS, as expected. This issue has now been resolved.
5. Display of Processing Fee for Payment Methods other than Credit Card
The Processing Fee is applicable only to the credit card payment method. Previously, when the credit card Processing Fee was enabled for a client in the support viewer and the Processing Fee CMS settings were toggled ON across all Step V3 components, the processing fee was displayed for all payment methods, which was not intended. This issue has now been resolved. After the fix, the Processing Fee will be displayed only for the credit card payment method, and only if it is enabled for the client and toggled ON in the Step V3 components.
Database
Payment method of NCS clients getting captured as Credit card for all New starts
It was observed that the Payment method of new starts for NCS clients was always getting captured as ‘Credit card’ in the Subscribe database regardless of whichever payment method was used, after the nightly sync process. This issue has been resolved. After the fix, the actual payment methods opted by end-users are correctly captured in the Subscribe database after the nightly sync process.
Last updated
Was this helpful?
