Overview
Use Business Rules in the Rules Editor
General | Condition | Action |
In the General column, only the Name field is required. Other fields are optional:
| Conditions are triggers that activate the rule when they match the current date and time, query, or field values. See Rule conditions for more information. | A rule can take different types of actions when the specified conditions are met. See Action types for more information. You can also create custom actions. |
black-friday-sale
..csv
file containing your rules.Create Custom Rule Actions with the API
Component | Name |
---|---|
Query pipeline | custom-rule-pipeline |
Custom rule type | custom-rule-type |
Rule | custom-rule-action |
custom-rule-pipeline
, that is used to complete the rule action.
custom-rule-type
, that uses your query pipeline. Here are some important parameters to include in your POST
request.
schema</code
, define the values required from the user to create a rule that uses the custom rule type.id
value must be unique across all apps in Fusion (global namespace).custom-rule-type
custom-rule-pipeline
My Custom Rule
1st-rule-parameter
string
Manufacturer
description
value is shown in the field’s tooltip in the Rules Editor.https://EXAMPLE_COMPANY.b.lucidworks.cloud/api/apps/myFusionApp/custom-rule-types
. Custom rule types are also available in the Rules Editor:
custom-rule-action
, that uses your custom rule, custom-rule-type
. If you are creating the rule using the Query Rewrite API, the following image depicts which parameters are shared between the custom rule type and the rule:
id
value is used for the rule’s type
and custom_type
fields. Remember to assign values to the custom rule properties, custom_param1
and custom_param2
.
123456
, with the Query Rewrite API: https://EXAMPLE_COMPANY.b.lucidworks.cloud/api/apps/myFusionApp/query-rewrite/instances/123456
Use the Query Elevation Component
id
field. Ensure id
is entered in the “FIELD NAME” option.COLLECTION_NAME_query_rewrite
collection and matches them against the query. Matching rules that perform query rewriting are applied at this stage, while matching rules that perform response rewriting are applied by the Modify Response with Rules stage later in the pipeline.rule_ss
.