Open topic with navigation
The Promotion Agentstore component retrieves rules in the same way that the IDOL Server Agentstore component retrieves categories and agents. You must set up your rules correctly to ensure that your HPE QMS rules return for relevant queries.
When Promotion Agentstore matches query text against rules, it uses the following matching order:
Indexfields in the rules (for example
QMSAGENTBOOLfield of the rule.
QMSFIELDTEXTfield in the rule (if this field exists).
Promotion Agentstore checks the Boolean restriction only if the rule content matches the query.
To ensure that rules match query text, the
DRECONTENT field (or another index field) must contain terms that match the Boolean expression. For example, you could add each term from the Boolean expression to the
In some cases, it is not possible to include every term that might match your Boolean expression to the
DRECONTENT field, for example because the expression contains Wildcards. In this case, you can configure an
AlwaysMatchType field and add this field to your QMS rules.
When a rule contains an
AlwaysMatchType field, Promotion Agentstore bypasses the first matching step, and checks the Boolean and FieldText restrictions for the rule.
For more information about
AlwaysMatchType fields in AgentBoolean queries, refer to the IDOL Server Administration Guide.
In boost rules, you must configure and use an
AlwaysMatchType field. HPE QMS uses this value to retrieve these rules, and you do not need to add extra terms.
In whitelist and blacklist rules, you do not need to set
DRECONTENT, because HPE QMS retrieves the lists directly by using the document reference.
You can optimize the performance of matching rules in the same ways that you optimize AgentBoolean agents and categories in IDOL Server. For more information, refer to the IDOL Server Administration Guide.