FAS 20.1 Upgrade Notes – Rezolve Ai Support Portal

Introduction

FAS 20.1 is compatible with the previous release.

FAS, Insights and CRU 20.1 introduce A/B testing capabilities for result modifications.

A/B testing for Result Modifications

FAS 20.1 allows for A/B testing on Rankings, requiring both CRU and our new Fredhopper Insights. Access Insights via a link in the Merchandising Studio to track the results of the tests.

The A/B tests are available on their own page in the Merchandising Studio and can be used to split traffic among multiple ranking rules, as well as campaigns. The A/B tests can be edited and published just like other triggered entities. They will also appear on the Result Modifications page, so their priority can be set relative to other modifications.

Once a winning option has been identified, you can convert the test to a standalone modification. It is also possible to test a modification against its underlying rankings (that's it not having modifications).

Known Limitations

It is not possible to choose the modification applied on Preview Pages in a prepublished environment - all variants for an A/B test will be applied simultaneously.

Changes in the response

A new section in the response schema (under /page/universes/universe) shows result modifications. If some of them are a part of A/B tests, they will have an additional property, groupId, which points to the A/B test entity.

This change is so that FAS has a consistent approach and reveals the A/B test id (groupId) for all A/B tested rules.

Here's an example:

<result-modifications>
  <result-modification id="7462cd71-6025-4146-9c8a-03c81c39bd46" groupId="7292df82-8da8-49d6-a586-fce944c9e7cc"/>
  <result-modification id="2cd9ffec-9df0-4545-9406-d9bbbf8096f8"/>
</result-modifications>

This section is placed directly on the Universe level, not in Universe/ItemsSection/Results, because even responses without items (ItemSection is not present) can contain blocking result modifications.

The result modifications are also mentioned in the bizlog line, as before. There is a subtle difference between this section and the bizlog line (see the table below):

Parameter	result-modifications section	bizlog: modificationapplied	bizlog: fh_modification
Description	Mentions ids of all modifications applied to the page, including empty ones. Also mentions groupIs of A/B tested modifications.	Mentions ids of all modifications applied to the page, excluding empty ones. Does not mention groupIds of A/B tested modifications.	Mentions all result modification id passed to the response. Does not mention groupIds of A/B tested modifications.
groupId	yes, for A/B tested modifications	no	no
empty modifications	yes	no	yes
triggered, but not applied move modifications	no	no	yes

Changes in default system settings (system.xml)

Login attempts rate limiter

For security reasons, we support number of login attempts per second limit. The parameter used for this is renamed in this release, from login_attempt_rate_limiter_per_second to login-attempt-rate-limiter-per-second. All clients on version 19.3 that used this parameter must have it renamed in business.xml to keep the functionality it provides.

	<node name="com">
		<map />
		<node name="fredhopper">
			<map />
                        <node name="bm">
				<map>
					<!-- Zero or positive number. In case of zero, the feature is disabled -->
					<entry key="login-attempt-rate-limiter-per-second" value="0" />
				</map>
			</node>

		</node>
         </node>

Remote rank calculation method

Alternative experimental algorithm for calculating entities' rank (ordering), for example, campaigns and facets, available behind a feature toggle. It is turned off by default.

Possible parameter values are

ABSOLUTE_POSITION (the default for the release; no change from the current behaviour) and
RELATIVE_POSITION

	<node name="com">
		<map />
		<node name="fredhopper">
			<map />
                        <node name="features">
				<map>
                                        <!--
                                                Possible values are "ABSOLUTE_POSITION" or "RELATIVE_POSITION"
                                         -->
                                        <entry key="remote-rank-calculation-method" value="ABSOLUTE_POSITION" />
				</map>
			</node>

		</node>
         </node>

Migration

Migrating from FAS 19.3 to 20.1 requires no specific migration steps.