Setting Rule Properties

This rule will be used to filter out all the non-search content. As mentioned earlier the web application input adaptor provides the variable URI.

This variable contains just the path part of the request (without the hostname) and is very suitable for this test.

So, click on the If Condition rule. You will see the rules editor change to show the properties for the rule on the left-hand side:

At the very top of the list is always the Label, Rule Class and Description. Label and Description are the short and long descriptions, respectively. The label defaults to the rule name (If Condition in this case). The label is the rule name given in error messages if a problem occurs while starting or executing a rule set. If required, you can change the label to be any short text that you can use to identify the rule.

For each rule, you can also set a description. This should be a short note explaining what the rule is supposed to do in the context of where it is placed.

For now, complete the properties as follows:

You may have noticed that the Value property was entered as “.” . In general values within the rules editor are treated as follows:

Value

Example

Meaning

Number

1234

A decimal number that can be used for calculations.

“Text”

“Hello World!”

Text is always enclosed in double quotes. If not, it will be treated as a variable (see below).

Variable

FROM_ACCOUNT

A variable is a field that contains data. It can be numeric or text.

By convention variables should be typed in UPPER CASE, however, this is not enforced.

Variables may not have commas or double quotes in their name.

Array variable

HEADERS

An array variable is essentially a text variable formatted to contain keyed arrays in a format that is readily recognized by applications and browsers (JSON). There are rules available to convert between JSON and CSV formats too.

CSV

A,B,C

A list of values separated by commas. If the values are strings, double quotes around them are not required (unless they have a comma in them).

Note: Sometimes it can be difficult to know if a property value requires a constant (no quotes required) or a value (quotes, a number or a variable required). To assist you in knowing what to put, property values are light orange input fields, whereas constants are white.

Last updated

General Website Terms & Conditions and Privacy Policy

Terms of UsePrivacy Policy

Contact Us

Get Help

© Copyright TomorrowX 2024 Composable Architecture Platform and Connected Agile are trademarks and servicemarks of TomorrowX .