Changelog: August 2024

API

Added

• [B2B feature] Added new RecentlyPurchasedFacet which can return hits on whether products in the result set was recently purchased by the user, user's company, or user's parent company.
• Added ResultSettings to the ProductQuery, so that you can be selective about which properties you want returned for your ProductResultDetails and VariantResultDetails. This can enable you to make large data access queries towards the Relewise API faster by minimizing the returned payload size. It defaults to the previous behaviour of returning all properties if this is not set.
• Added new ProductInCartFilter which enables the scenario where you want to include or exclude products currently in the user's cart from a request.
• Added new DataObject condition: ObjectValueIsSubsetOfCondition, which can be used to determine if a list of values on an entity in Relewise is a subset of the entries provided in the condition.
• Search Analytics: Added new Dataset setting to exclude zero hits from being tracked if a Redirect was found. The default behavior is that search results, even though empty, will not count as a zero hit if redirects was found.

Changed

• All IntegerFacets have been marked obsolete. Instead, you should use the DoubleFacet counterparts.
• Click Through Rate (CTR) minimum threshold has been increased; we now require more clicks before taking CTR into consideration.
• We now use sliding cursor expiration upon consuming paged results in ProductQuery via 'NextPageToken'. This ensures predictable retrieval of elements when traversing pages even when CRUD operations are taking place at the same time as results are being retrieved.

Fixed

• Search Analytics: Fixed a bug that caused single searches to not be counted towards analytics.
• Search Analytics: Fixed a bug where zero hits would only count 1 per day per term instead of all actual hits.
• Wrapping the search query in 'OR' or 'AND' filters no longer produces different results.

---

My Relewise

Added

• A "Content Delivery" section has been added to the left-side navigation. This section provides insights into consumption through our Content Delivery features, such as email campaigns that include recommendations.
• Added a counter of how many languages and currencies have been used in a given period (as defined by the date selector at the top of the screen in MyRelewise).
• Added support for SAML-based Enterprise SSO (single sign-on). For more information, click here.
• Single Sign On: It's now possible to remove the provider, and return to using email and password the old school way.
• Using the "Forgot Password" feature when being an SSO user will now send an email to reset password as for any other regular user.

Changed

• Merchandising: Rules are now enabled by default when they are created, instead of when saving the first time. This makes it easier to ensure that rules are active when you want them to be.
• We now ask for a user's current password when updating the password in MyRelewise.

Fixed

• Fixed an issue where modals would sometimes randomly scroll to top on click.
• Fixed an issue where the search parameter for the link to the Relewise Demo Shop was not encoded, which would cause the dataset data to not be included correctly in the redirect.
• Search Analytics: Fixed a visual bug in Search Analytics that would display the wrong Delta percentage in the list overview.

---

Integration

Added

• Java SDK: Added generation of Java Documentation when using the SDK.
• JS SDK: Added Get Content Facet Helper & Get Product Category Facet Helper.
• JS SDK: Added support for popularity multiplier selectors.
• JS SDK: Added support for setting search constraints.
• JS SDK: Added support for the ObjectValueIsSubsetOf condition.
• JS SDK: Added the option to facet on recently purchased products.
• JS SDK: Added the option to filter on products that are in the user's cart.

Changed

• Improved error message from faulty requests to the API - useful for server-side implementations without access to the network tab.
• Java SDK: Made Clients public so that they could be used outside test projects.
• JS SDK: Explicitly set caching to 'no-cache' for fetch used in the relewise.client.
• Shopify Integration: We now use GraphQL to fetch products.

Fixed

• Demo Shop: Fixed an issue where it was possible to reach an error state where the header would not be able to load because of a missing user in context.
• Demo Shop: Fixed an issue where the share query parameter was not encoded while generating a share link. This would cause issues when sharing a dataset with special characters in its values.
• JS SDK: Removed dependency on cross-fetch. This fixes an issue where using the SDK client side in nextjs 14 would cause an error.
• Umbraco Integration: Handled export error for "varies by culture"-Document Types when dealing with non-string values.

---

Documentation

Added

• Added a page detailing the Search Result Modifier functionality, with usecase suggestions. Available here.
• Added documentation for single sign-on (SSO) functionality in MyRelewise, allowing you to link your MyRelewise login to your SSO provider of choice. Available here.
• Added documentation for social logins, allowing you to login to MyRelewise via a Google or Microsoft account. Available here.
• Added documentation for the Commercetools integration. Available here.
• Added pages detailing our Service Level Agreements, Quotas, and Support Agreements for using Relewise. These can be found under the heading Policies in the navigation.

Changed

• Updated the documentation with specifications for the use of Pin rules in Merchandising. Available here.

Fixed

• Fixed a number of broken breadcrumbs across the Documentation site.