Connectors Conditions and Rules

If you have more than one output connector from a step, you must either add conditions to all the connectors except the one you want to use as a default connector, or you must start parallel branch for the non-default connectors. There is always should be a default connector to make sure the process doesn't get stuck.

The system will evaluate all conditional connectors first (and you can sequence how you want them evaluated) and if none match then it does the default connector. If a conditional one is executed the default one doesn’t (unless the conditional is also parallel, in which case it might still run the default connector)

6 Comments

Harry

I am trying to create a conditional connector of type "Flow Step Status." I fill in all menu items in the "Flow Step Status Config" area except 'filter'. When I try to save there is an error: "You should create at least one condition." In the conditions section it says "* Here you must provide a conditions to search a data source records for the process version."

Work-Relay Administrator

Harry - you need to select conditions to identify which datasource record you want the Flow Step Status to check. Since Flow Step Status can check objects other than the context object datasource, you need to narrow down the record or records you want to check the Step status on by providing the appropriate conditions.

Andrew

I am trying to create a parallel connector that will execute if a decision is not received within x amount of hours. I have a manual step which proceeds to a decision step. Where do I put the additional step to 'check' if a response isnt received then follow that path. Should this be off the original manual step with conditions like if Decision process is pending or in progress?

Work-Relay Administrator

If "A" is your Manual step, which is followed by Decision step "B", then you can start a parallel branch after A and put a System step "S" there. On this System step, put a Before step rule, that will activate this step after the wait period. Ex. if the wait period is 3 days, the expression may look like
{$System.Date} < {$Cursor.StartDate} + 3
On this System step, you may have before step action(s) that will do what you need. System step will activate anyway - no matter decision step was completed or not - so when completing the Decision step, you may update some variable in the process, and on those before step actions of a System Step, define condition to look at whether Decision step (B) was completed or not.

Andrew

Thank you. So for a delay in minutes the syntax is?

{$System.Date} < {$Cursor.StartDate} + MINUTES(3)

Work-Relay Administrator

I think the correct option is
{$System.DateTime} < {$Cursor.StartDate} + MINUTES(3)

Add your comment

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.