Conditions, or triggers, define the environment necessary for the rule action to fire. Any combination of conditions (date, field value, query, and query profile) can be defined for a rule.
Multiple conditions of the same type are met with AND logic. If a rule has multiple conditions and at least one of the conditions is not met, the rule will not fire. Multiple conditions of different types, however, are met with OR logic. The rule is triggered when one or more conditions of different types are met.
For more information, see Business Rules Conditions Reference.
Descriptions
Condition types
Dates
Set a date and time range for the rule. If the current date and time are outside of this range, the rule will not fire. The Rules Editor includes a calendar selector for ease-of-use.
Field value
Set field values, or filters, that trigger the rule. This corresponds with the fq parameter used in a request: search?q=red&fq=type:shoes. For example, a Field Value rule can trigger if the user has faceted for the product type shoes.
Query
Set query terms that trigger the rule. Query terms can match as keywords, phrase, or text. This corresponds with the q parameter used in a request: search?q=red&fq=type:shoes.
Query profile
Specify one or more query profiles that will trigger the rule.
For example, this can be used to create rules that apply to a query profile used for testing specific user groups. Once testing validates the rules, the Query profile condition is removed so the rules fire for all query profiles.
FAQ
If no conditions are set for a rule, Fusion will automatically assign a Query condition with no matching search terms. This effectively means the rule will always fire, even when no query is made. For example, you can create a block list rule to prevent a list of documents from appearing in results under any conditions without actually removing the documents from your datasource.