Task Models

Tasks are a broad concept because various field data types and guidance messages represent them. Tasks themselves are contained within an Activity.

An Activity can be thought of as what needs to get done, while Tasks are often the detail of how the Activity gets done.

Flowset supports two levels of configuration of workflows. Task Sets are the original level, offering a simple, straightforward list of Tasks, however, with a level of conditional display for further qualification purposes that constitutes what gets done within an Activity.

The choice to use Task Models (Advanced) should be based on the need and sophistication.  Task Models are perfect for Pathways | Decision Trees within an Activity where branching logic is needed.

Here are some examples:

A decision tree that guides agents through a network of Tasks

Flowset Agent Guid.png


Different pathways through the same Activity depending on data


A characteristic of Task Models is that they contain decision points that present Tasks dependent data, making them much more flexible and reduce the number of unique Activities needed.


The alternative to Task Models is Task Sets, which present lists of Tasks within an Activity

When creating a new workflow, you'll be offered the choice of either model:

  • Standard, which equates to Task Sets
  • Advanced, which equates to Task Models



Note: It's not possible to switch models once initially selected.





Was this article helpful?
0 out of 0 found this helpful



Please sign in to leave a comment.