<img height="1" width="1" style="display:none;" alt="" src="https://dc.ads.linkedin.com/collect/?pid=287945&amp;fmt=gif">

FlowWright v9.3 Update: Task Scheduling + More

Posted by Dileepa WIjayanayake on Sep 7, 2017 1:35:49 PM

While FlowWright v9.3 packs a lot of new functionality to the product, one of the main enhancements of FlowWright is to its tasks and business intelligence.  FlowWright's main task routing steps  are the task and choice steps.

task step   choice task step

These steps now have extra inputs that are able to provide expirations based on minutes, hours, days and months.  Also options to include weekends or not when computing the expiration date\time.  Given these step inputs and configuration, business intelligence is now able to predict when tasks within a workflow definition will start and end given a starting date time.

Let's look at a simple task example where there are 3 tasks serially.

3 serial task steps workflow definition

Each of the tasks are configured with the following expirations:

Task Name Expiration
Task1 1 day
Task2 2 days
Task3 3 days



Using business intelligence, FlowWright is able to display the start end times of each task for the workflow definition:

definition predictions for 3 serial tasks

As you can see on the above table, BI predicts that this workflow will take 6 days to complete based on the configured values for each of the tasks within the workflow definition.  You can also view when each task will start and end.

Let's take another example where the tasks are in parallel:

3 parallel task workflow definition

The above tasks are configured with the following expirations:

Task Name Expiration
Task1 1 day
Task2 2 days
Task3 3 days

Given that all above tasks are in parallel, business intelligence will show that it takes 3 days to complete this workflow.

start/end projections for 3 parallel tasks using BI

Business intelligence prediction works with any workflow definition that contains tasks or choice task steps.  It also supports sub-workflows to any level, so if a workflow definition has many sub-workflow steps, BI will drill down to all the children (any # of levels deep) and figure out the total time that will take for the definition to execute.

Given the same predictions as shown above for workflow definitions, BI can also display planned vs. actual vs, projected data for any given workflow instance with tasks.  Let's look at a workflow instance that was created using the first workflow definition - 3 tasks in parallel.

Planned vs. actual vs. projected by BI for workflow instances

 As you can see from the above graphic, for the workflow instance, BI is able to display that first 2 tasks were executed, a comparison between the planned vs. the actual start/end date times and also the durations including the delta.  Based on the BI data, this workflow is +5 days ahead of schedule.

No matter how complex the workflow is, FlowWright is able to compute this information in realtime and render to you in realtime.  Our test results show that it takes ~10 seconds to compute ~100, 000 tasks.

New Call-to-action

Dileepa Wijayanayake + FlowWright Team

Topics: task workflow, scheduling, Business Intelligence Process