In Fusion 5.17 and later, this stage is named Modify Response.
In earlier versions, this stage is named Modify Response with Rules.
Most rules operate on the request, but some rule types, such as banner rules or redirect rules, do their work when the response comes back. The Modify Response stage applies those rules to the response. For example, a banner rule can add a banner URL to the response before returning it to the client.In Fusion 5.17 and later, the Modify Response stage also applies the boost, bury, and suppress settings from the Field Facet and JSON Facets stages.
To use these settings, place the Modify Response stage after both the facet stage and the Solr Query stage.See Rules for additional details about how to configure this set of features.TIPS:
The Apply Rules stage must be enabled as a prerequisite for this stage.
Most use cases don’t require configuration. To show display labels for facet fields, set Facet Field Label Blob ID.
Although this stage is available without a Fusion license, it is only effective after creating rules in Fusion or configuring boost, bury, or suppress in a facet stage.
Stages can be triggered conditionally when a script in the Condition field evaluates to true.
Some examples are shown below.Run this stage only for mobile clients:
params.deviceType === "mobile"
Run this stage when debugging is enabled:
params.debug === "true"
Run this stage when the query includes a specific term:
The first condition checks that the request parameter “fusion-user-name” is present and has the value “SuperUser”.
The second condition checks that the request parameter “isFusionPluginQuery” is not present.
When entering configuration values in the UI, use unescaped characters, such as \t for the tab character. When entering configuration values in the API, use escaped characters, such as \\t for the tab character.
