Two connectors are set up on a workflow task with conditions of:
* *::::::* ''"@typeid@"="12345"'' and*::::::* ''"@typeid@"="45678"'', respectively*
If the workflow is fired against a record associated with typeID 67890, the workflow will never progress to the next task.
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'''
Two connectors are set up on a workflow task with conditions of:
* *::::::* ''"@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.
Two connectors should be set up on a workflow task with the following conditions:
* *::::::* ''"@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:
* *::::::* never not have instructions on ''whether'' to trigger the next workflow task (Rule #1), and*::::::* always have clear instructions on ''which'' task to trigger given a certain set of conditions (Rule #2).*
==Using iCalendar to generate Meeting Requests, Tasks and Contact cards==