Changes

Note: because the sequence in which the system accesses each connector is not configurable it is important that the conditions are mutually exclusive. For example, if you have 3 connectors for different paths based on a particular value the conditions could be:

You can also use MySQL syntax to perform calculations within the Condition:

This condition will be true only on the 1st of the month. This could be used with a Recurring Workflow that loops daily if you wish to send out a summary e-mail on the 1st of every month.

Three connectors are set up on a workflow task with conditions of:

* ''"@typeid@"="12345"'',

* ''"@typeid@"="45678"'' and

* ''"@typeid@"="67890"'', respectively

Alternatively, connectors with the following conditions could be set up:

* ''"@typeid@"="12345"''

* ''"@typeid@"!="12345"'' (not equal to "12345"), and

* ''"@typeid@" NOT IN ("12345","45678")'', respectively

'''2. Each condition must be mutually exclusive from every other'''

* ''"@typeid@" in ("12345","45678") AND "@statusid@" in ("888","999")'' and

* ''"@statusid@" in ("888","999")''

The issue here is that both statements [[Boolean Operators|evaluate]] as '''true''' if the statuses on the record triggering the workflow have a statusID of 888 or 999.

* ''"@typeid@" in ("12345","45678") AND "@statusid@" in ("888","999")'' and

* ''"@typeid@" not in ("12345","45678") AND "@statusid@" in ("888","999")''

This configuration satisfies Rule #2, in that the conditions are now mutually exclusive. However, a third connector must be included, with the following condition, which connects to the "Complete" task, in order to satisfy Rule #1 above:

* ''"@statusid@" not in ("888","999")''

With these three connectors configured, the workflow will: