Condition Operators and values

Operators are used wherever PalDock compares one value against another:

• Connections in the Connection Creator
• Modify Field
• Table filters
• Pingtree filters

The set is the same everywhere, with one exception noted below.

Operators

Most operators need one value to compare against. A few need two, and some need none at all.

Comparing

• Equals : the two values are the same
• Not equals : the two values are different
• Is less than : lower than the given value
• Is less than or equals : lower than or equal to it
• Is greater than : higher than the given value
• Is greater than or equals : higher than or equal to it
• Is between : between two boundaries, boundaries excluded. Needs a second value
• Is between (inclusive) : between two boundaries, boundaries included. Needs a second value

Text

• Contains : the text contains the given substring
• Does not contain : the text does not contain it
• Starts with : the text begins with it
• Ends with : the text ends with it
• Regex match : the value matches the given pattern
• Regex not match : the value does not match it

State

• Is true : evaluates to true. No value needed
• Is false : evaluates to false. No value needed
• Is empty : empty string, empty list, or nothing at all. No value needed
• Is not empty : has some value. No value needed

Modify Field only

• Always : always applies. Use it when the change should happen unconditionally, with no condition to write

Field value

The value you compare against is a plain text field, but it also accepts a regular expression. One condition can then cover several cases, so you do not have to build a separate step for each of them.

Compare the two. A single value, in Modify Field:

Source:    this field
Operator:  Equals
Value:     approved
Operation: anything
Output:    anything

Several values at once, using a pattern:

Source:    this field
Operator:  Regex match
Value:     approved|rejected
Operation: anything
Output:    anything

The second one does the work of two steps. With ten possible statuses it does the work of ten, and everything stays visible in one place instead of being spread across the canvas.

Note the operator. Equals compares the text exactly, so approved|rejected would be treated as one long string and would never match anything. Patterns need Regex match.

The Field setting only appears when the Source is set to another field.

Patterns worth knowing

• | for alternatives, as in approved|rejected
• .* for anything, as in app.*
• ^ and $ to anchor to the start and the end, as in ^approved$

Standard regular expressions are supported, so anything you would normally write works here too.

The anchors matter more than they look. Without them, approved also matches not approved, and a rejection quietly travels down the success branch.