2020.2

l
Not any of the following.
This equates to the logical operator (NOT (... OR ...))
If none of the associated criteria are met, then this group resolves to TRUE.
The top level is always a group. A group can contain one or more Rules and/or Groups.
Rule
A Rule is a logic expression using a single operator or function, and their associated operand
(s). The number and type of operands is dependent upon the operator or function chosen.
Rules can also have different types. The available rule types depend upon the context where
the Rule Editor is used. For instance, within Job Creation, there can be data rules that are
based on record data belonging to a content item, but there will also be "location rules" that
deal with the position of a document within the job.
The Rule types are as follows:
l
Data Rule: This rule operates upon Data entries. Select the Data Field, then select the
logical test and the associated test value(s). The options available will depend upon the
Data Field type (they are "type aware"), but all have at least "is equal to" and "is not equal
to" to another entry as an option.
The data type specific options are as follows:
l
Alphanumeric data field specific selections: Whether the alphanumeric string
"contains", "does not contain", "starts with" or "ends with" another string value.
The "is like" and the "is not like" selections allow the use of "*" wildcards.
The comparison string could be a manually entered string, or it could be another
textual data field. The data field could be from the data model, or it could be a
runtime parameter entered as part of Job Creation. Runtime parameters are
expressed as "params.xxxx", where the xxxx is the name of the runtime parameter.
In the Data Filtering Options rules editor the comparisons are always case sensitive.
In other rule editors there is an option to turn of case sensitivity.
l
Date data field specific selections: Whether the date field is "before", "after", "not
before" or "not after" another date entry, or "is between" two other date entries. The
comparison dates can be a manually entered dates, or date data fields (either from
the data model or runtime parameters).
The date value should be in ISO 8601 format. When entering dates manually it is
best to select the date using the date selection option.
Page 665