Task Workflow
A Task Workflow is a reified execution of a state machine at the Task and Task List levels. The Task Workflow addresses the following concepts which a user can perceive and interreacted with:
What is the current state of a Task (displayed as status)?
What are other states a Task can transition from or to?
What are the events, manual or automatic, which can trigger a state transition?
What are the dependencies between a state of a Task and a state of an object owns (e.g. a Review) or owned (e.g. a Conversation) by a Task?
What are the dependencies between a state transition of a Task and a state transition of an object owns or owned by the Task?
Note: A Task List is governed by the same Workflow. However, its states and transitions are not important to the users and therefore, obfuscated in the user interface.
The execution of the state machine is always instigated by a user’s action. The cascade effects of the initial transition may be observed at other levels of the Workflows. For example, if a user (manually) sets the state (status) of a Task to Complete, all Open Conversations owned by the Task will also automatically transition to Closed.
%20asStateDiag.png?inst-v=4ef52afe-aa68-4cc9-a76b-41382328f04b)