Value conditions for screen flow connections

The allowable values for screen flow connections are specified below. These conditions are validated at compile for correctness.

For booleans:

[true|false|yes|no|y|n|unknown|uncertain]

For example, true

For dates:

[(>|>=|=|<=|<|<>|!)yyyy-MM-dd]

For example, >= 2005-06-12

For date-times:

[(>|>=|=|<=|<|<>|!)yyyy-MM-dd hh:mm:ss]

For example, 2010-03-26 22:04:12

For time of days:

[(>|>=|=|<=|<|<>|!)hh:mm:ss]

For example, 19:00:00

For numbers:

[(>|>=|=|<=|<|<>|!)any number]

For example, = 50000

For text comparisons:

[(=|!|<>|not)"any text"]

For example, the text value is case specific.

NOTES:

! means not equal to (the equivalent of <>)
You can join comparisons together using 'and'. This allows you to test ranges, for example:
>1000 and <=2000
>2006-06-30 AND <=2007-07-30
You can also join comparisons together using 'or'. For example,
<1000 or uncertain
"unemployed" or "student"
This is necessary because you can't have two connections from a decision shape to the same shape.
When using both 'and' and 'or' there are no parenthesis, so conditions are evaluated using an order of operations similar to addition/multiplication in maths. In this case, 'AND' has a higher precedence than 'OR', for example:
"A and B or C and D" is evaluated as "(A and B) or (B and C)"
"A or B and C" is evaluated as "A or (B and C)"
The priority of OR versus AND means that you can always replace two separate connections with a single connection using the word OR.