Release Summary - April 06, 2023
The following key features and improvements, along with bug fixes, have been released in Algonomy products in the release version 23.09 during March 24-April 06, 2023.
Engage
Enabled Segment Creation Based on Visits not Tied to Session Id
Merchandisers can now create segments for first-time shoppers on their eCommerce site. A visitor is considered first-time shopper if they visit the site for ‘n’ number of times within ‘x’ number of days. These visits will not be correlated to external Session IDs.
Jira: ENG-25552
Dashboard
Experience Browser can now be accessed seamlessly
The Experience Browser is now accessible seamlessly through SSO Algonomy login. Previously, after integrating SSO, some navigation issues were noticed in the Omni Channel Personalization Platform. The Experience Browser was disappearing when users navigated to other capabilities of the platform. . The SSO pop-up was also noticed to be appearing more than once when navigated within the Platform. These issues have been fixed.
Jira: ENG-25264
Other Feature Enhancements
The following feature enhancements and upgrades were implemented during March 24-April 06, 2023.
Jira # |
Module/Title |
Summary |
General Availability |
---|---|---|---|
Platform > UPS: Renamed the common status job UUID attribute to ‘jobId’ |
In UPS Attributes API response, the common status job UUID attribute ‘requestId’ has been renamed as ‘jobId’.
|
06-Apr-2023 |
|
Platform > UPS: Implemented an alternate solution to replace the cookie-based authentication mechanism for Experience Browser |
Accessing the Experience Browser menu options such as 'Placement Content' or 'Placement Segment' in Incognito mode causes an endless loop of SSO Login. This issue occurs because the Experience Browser loads on a customer site, and the cookies set by the experience server are treated as third-party cookies by the browser. To access the Experience Browser menu options in Incognito mode, users must disable or allow third-party cookies on their browser. |
06-Apr-2023 |
|
Enterprise Dashboard: Enabled diversify by brand & category options in User purchase history model |
With the new UI enhancement, the options 'Diversify results by category' and 'Diversify results by brand' options are now enabled for the 'User purchase history' model within Configurable strategies. As a digital merchandiser, you can now create a Configurable strategy using user's purchase history and diversify the results by brand or category, so that you can recommend a diverse set of products based on the user's purchase history. |
06-Apr-2023 |
|
Enterprise Dashboard: Modified maximum days under ‘Do not Recommend’ rule to restrict categories already purchased |
The maxim number of purchased days under ‘Filter products already purchased’, has been modified from 90 days to 365 days. As an optimization manager, you can now restrict the categories already purchased in the past 365 days, for your Recommendation restriction rule. |
06-Apr-2023 |
|
Enterprise Dashboard: Updated UI to enable ‘User Attribute’ in Merchandising Rules |
The Merchandising Rules UI has been updated to enable ‘User Attribute’ to boost products if the attributes match. |
06-Apr-2023 |
|
Data Engineering: Enabled Search Performance Metrics in Find Report |
Search Performance Metrics have been enabled for the Find report, providing key metrics to understand search performance and optimize search. |
06-Apr-2023 |
|
Find: Enabled geo search language service support |
A new Default Config set has been added for the new indexingType as place and the find-py-scripts has been tested to ensure compatibility with the new snapshot type. |
06-Apr-2023 |
|
Recommend: Boost products with attributes that match User attributes |
Attributes of users show their preferences which boost the products if the attributes match. |
06-Apr-2023 |
Bug and Support Fixes
The following issues have been fixed during March 24-April 06, 2023.
Jira# |
Title |
Summary |
General Availability |
---|---|---|---|
|
Dashboard: Browser cache needed to be cleared before launching Experience Browser |
Previously, after logging in, the page blocked the pop-up of Experience Browser even if it was allowed, resulting in an error. To fix this, users need to clear their browser cache before launching the Experience Browser. The issue has been fixed now. |
06-Apr-2023 |
Platform > UPS: Error while processing compressed payload in UPS Attributes API |
A client was getting an error while processing compressed payloads in UPS Attributes API. The HTTP Content-Length header check has been removed in the Attributes API so that the compressed payloads can be processed without any errors. The response will now be returned in the format: Copy
|
06-Apr-2023 |
|
Platform > UPS: Site command access issue in BuildFTP server |
Previously, users executing Site upload commands in BuildFTP server received an error message stating "Request is in queue. File processing will begin shortly." This issue has been fixed now. |
06-Apr-2023. |
|
|
Find: Getting 500 error in Find search term request |
A client was getting a 500 error in the Find search term request. It looks like the Solr query was being timed out as there was no result found for the entered query, so the spellcheck came into action. Spellcheck uses all spell fields to get spell corrections and the data in the spell field was too large that's why the spellcheck component took more than Solr socket timeout and hence, the search service gave timeout exception error. This issue has been fixed now. In the response, the search term will be truncated if it exceeds the max token length and spellcheck param will be passed as false to Solr. |
06-Apr-2023 |
Data Engineering: Scheduled MVT Job is not triggering |
An MVT job in DBeaver was not being triggered at the scheduled time. However, the user was able to run the job manually. This issue has been fixed now by changing the schedule time. |
06-Apr-2023 |
|
Low Code Integration: User ID not being set properly |
A client faced an issue with the low code integration where the userId parameter was being sent the same as the sessionId. This occurred because the function that initializes the R3_COMMON variable was sending the same value for both parameters. The issue has been fixed now. |
06-Apr-2023 |
|
Enterprise Dashboard: Unable to access second page in Campaign List |
A client was unable to access the second page in ‘Campaign List.’ This issue has been fixed now. |
06-Apr-2023 |
|
Enterprise Dashboard: Omnichannel Personalization portal’s default page navigating to ‘Service Unavailable 503’ |
During the ThoughtSpot maintenance activity, Omnichannel Personalization portal’s default page navigated to ‘Service Unavailable 503’. This issue has been fixed now. |
06-Apr-2023 |
|
Science: Brand strategies are not using the new Top Seller model |
Brand strategies were not using the new Top Seller model. To address this, current Brand strategies (including new arrivals and oversandshakers) have been converted to use the new Top Seller model. |
06-Apr-2023 |
|
Engage and Enterprise Dashboard: Expired content is showing in the dashboard even after unchecking the ‘Show Expired’ checkbox. |
A client was experiencing an issue with the Omnichannel Personalization dashboard where expired content was still being displayed even after unchecking the ‘Show Expired’ checkbox. This issue has been fixed. |
06-Apr-2023 |