Release Summary - April 20, 2023

ENG-25863

Data Engineering, Enterprise Dashboard:

Enabled Find API Report in the Reports Menu

Find API Report has been enabled in the Report menu, providing key metrics to record the FIND API call counts.

PLAT-3372

Platform>UPS:

Integrated Omnichannel API with common status framework

Omnichannel Order API has been integrated with the common status framework for async reporting of the request status to report:

An overview of a request, including number of orders, success, and failures.

The reason for the failure and order IDs of the failed orders.

ENG-25668

Find:

Creating a timing log for each component in the Search service

With approximately 30 query processors, the Search service has enhanced the processing speed of every Find request by adding timing information for each individual component.

ENG-25578

Data Engineering & Engage:

Dynamic field support for new variables in Dynamic Experience Templates

When a new template is created for a variation, the layout JSON is sent as the payload of an API call to the backend. However, only 5 fields are accepted while any additional fields are disregarded. Consequently, the fields are hard coded.

Dynamic Experience templates now support dynamic field creation for new variables.

ENG-25321

Data Engineering:

Changing the metrics ‘Rec Views’ and ‘Rec Clicks’ to ‘Views’ and ‘Clicks’ respectively in the Real Time Report

Real Time Dashboard metrics have been changed to ‘Views’ and ‘Clicks’ instead of ‘Rec Views’ and ‘Rec Clicks’ to better assist merchandisers in real-time reporting.

ENG-25262

Recommend:

Adding option to Merchandising Rules to remove products already viewed by the user

The user interface has been improved to make it easier for Merchandisers to use the popular products model and filter out items that the user has already viewed. Additionally, there is now an option to experiment with new products in the placement.

ENG-24694

Recommend:

Creating Default Configuration for multiple User Affinity Configuration

When Merchandisers create multiple user affinity configurations and tag them as default, the system may not know if the configurable strategy was linked to the correct user affinity configuration. This is because the configuration was tagged as default and it's unclear whether it best matches the configurable strategy.

To address this issue, Merchandisers can create a 'Default' user affinity configuration. This allows them to edit the value of the default at any time and link it to the configurable strategies that are marked for the default. The name 'Default' cannot be changed or deleted, and a backend API is required to create a configuration with this name that cannot be deleted.

ENG-15967

Find:

Changing Find API response for Status: Warning message even though user is not set

A client encountered an issue while rendering search results on the page based on the value of 'status' returned in the response. If the value of 'status' was 'OK', the products were added to the page. However, if the user was not logged in, Find returned 'status=Warning', which caused an issue for the client.

This issue has now been resolved, and the client can see 'status=OK' in the Find response even when the user is not logged in. Additionally, the search service parameter-related information has been moved from 'Error' to 'Search service debug' to provide more comprehensive information to the client.

ENG-25589

Data Engineering, Enterprise Dashboard:

Find API Count Reporting

Customers can now view the Find API count reporting as part of the portal to track the number of API calls made on a daily basis. The Find API report provides insights on the daily query count for different API methods and enables clients to analyze daily trends.

The following metrics are available in the Find API report:

Total Call Count

Total Raw Call Count

PLAT-3465

Platform>UPS:

Delete support in BuildFTP for Segments, User attributes and User links Feed types

Support has been removed from BuildFTP to enable error-free processing.

The following changes have been made:

BuildFTP will now process user records and remove all content for the specified feed type upon receiving an empty payload for the userID.

This change is applicable to all feed types, including Segments, Columnar Segments, User Attributes, User Links, and both Full & Delta Grouped Links.

ENG-25756

Recommend:

Performance improvement on CategoryBasedReplenishmentModel

The 'CategoryBasedReplenishmentModel' request was taking longer than expected due to the selection of a full product catalog, which includes all products and attributes. Since each product only looks at category membership, this caused unnecessary delays. With the latest update, the request has been modified to build local catalog data that excludes attribute data and runs a single query that only returns category data. This change significantly improves performance.

ENG-25807

Advanced Merchandising, Discover, Find, and Recommend:

Performance improvement on Legacy CatlaogReader

The ‘CatalogReader’ used by Catalog model builds, Discover models, Find models, and Advanced Merchandising has become outdated and inefficient. The latest version significantly improves performance by collecting all the data at once in a product scan, rather than collecting the data from the client-side. This change reduces request completion time.

PLAT-3456

Dashboards, Identity & Access Management:

Model Browser access if the URL is known

Previously, all users could directly access the 'Model Browser' if they knew the URL. However, the 'Model Browser' option should only be accessible to users who have been assigned the 'RR Super User' role or any of the internal roles. This issue has been fixed now.

PLAT-3458

Dashboards, Identity & Access Management:

Unable to see the status for Offline feeds

A client was unable to view the status of Offline feeds. This issue has been fixed now.

ENG-25750

Recommend:

Issue with Brand Filter and Attribute Filter in Recommend

A client faced an issue while creating a Strategy rule and Restriction Rule, where the Brand Filter and Attribute Filter were not displaying the expected results. This issue has been fixed now.