Flowset Release July 2024

We are pleased to announce the following changes included in the release of our Flowset product dated 23 July 2024

Summary of Release

The option to persist task data beyond the activity in which it was collected was added in the April 2024 release.  This release builds on this persisted task data in two ways

1. When writing the complete ticket audit to a comment, it will now include the duration that the task took to complete
2. The persisted data can be used in later activities to control the behaviour of the workflow.

Activity Durations in Workflow Audits

When the Persist Activity Task Data option is enabled for a workflow definitions, you are able to insert into comments a full audit record of task data collected in each activity performed on the ticket.  In this release, the full audit record will include details of how long the activity took to complete.  It is a record of the timer between when the activity started and when it finished by transitioning to another activity (or finishing the workflow).  See Transition Comments for more details.

Process Persisted Fields

Process Persisted Fields allow task data to be collected in advanced models, but held in such a way that is it accessible to subsequent activities.  This allows a workflow to be designed to gather information early in the process, which can then be used later without having to ask the same question again.  For example, in an employee onboarding process we capture whether someone will be a home worker early on, but may need to use this information later in the process to decide whether they will need a desk allocated.

Process Persisted Fields are available if the Persist Activity Task Data option is enabled for the root level process definition.

See Process Persisted Fields, Process State, Helper and Controlled Fields for details of defining process persisted fields.  See Activity Task Modeling for details of using process persisted fields in task flows.