Workflow Examples

There are a few properties on the workflow activity and a few of the workflow path that work together to create a number of different options. The easiest way to understand how these properties interact together is through some examples.

Escalation Example:

In this example, the Analyze and Sort activity is activated. Notice that there are three identities responsible for this activity - Change Specialist I and the Creator . Let's say that these identities complete their tasks and vote as follows:

Change Specialist I - Test Data (95%)
Creator - Reject Data (10%)

In this case, since none of the paths are marked as override or default, and since none of the paths have received a 100% vote, the decision is escalated to the identity specified in the Escalate To property, in our case the Creator. If there is no identity specified there, then the activity is escalated to the workflow Process Owner.

Override Example

Let's take the same example we have above, but now, let's say that the Reject Data path is marked as Override.

As soon as the Override path receives even one vote, no matter how small the percentage of the total vote weight that vote brings, the override path is executed. So, in this case, even though the Reject Data path receives just 10%, the Reject Data activity is activated.

Default Path Example

In this example, we are again working with the Analyze and Sort activity, however, there are no longer any Override exit paths from this activity. Now, we have the Test Data path marked as the Default Path.

Here again, the Change Analyst 1 votes Test Data, which gives it only 95%, and the Creator votes Reject Data, which receives 10%. If none of the paths are marked as Default or Override, this issue would be escalated. However, since we do have a Default Path, the default is chosen instead. So, in this case, the activity Test Data would become active next.

Required Example

In this example we are again working with the Analyze and Sort activity. Notice however that now there are 3 Identities responsible for completing it - the Change Specialist I, the Creator, and the Inspectors. Notice that the Creator is marked as Required. This means that even if there is 100% vote weight on any one path, the Required identity must vote.

Let's assume that none of the paths are marked as Override or Default, and that the voting so far yields:

Data Analysis - Test Data (95 %)

Testing and Quality - Test Data (95%)

This would give the Test Data path 190%, which is enough for that path to be selected. However, since the Creator has not yet voted, the activity does nothing and awaits that last input. If the Creator votes Reject Data, the Test Data activity is activated next. However, if the Reject Data was marked as Override, then that one last vote would change the whole picture and Reject Data would be activated instead.

Wait For All Votes Example

If the Wait For All Votes option is checked on the Activity, then no action will be taken until all the votes are in, even if there is 100% gathered on any particular path, or even if a vote is cast for an Override path.

In the above example, all 3 identities have to vote before the exit path is activated. Let's say that the Reject Data path is marked as Override. Then, the votes come in as follows:

Change Specialist I - Test Data (95%)

Creator - Reject (10%)

At this point the result is very clear. The Reject Data path will be selected. However, Aras Innovator will wait until the Inspector group votes, and then the Reject Data activity will be activated.