An optional task that users perform while processing a case. This type of flow action does not move a case closer to resolution.
An optional task that users perform while processing a case. This type of flow action does not move a case closer to resolution.
Actual work that is performed by application users and automations that consists of a sequence of tasks and leads to an intended business goal. An example of a case is a process of hiring a particular job candidate, where an HR worker collects necessary documents, a hiring manager conducts a job interview, and an application sends an automated email with onboarding information after the candidate is approved. To create a case, you first build a template of your business process that is a case type, and then apply the template in multiple cases, for example, to review applications from many candidates.
An activity that controls the way that users interact with forms that they need to fill in to complete their tasks. The flow actions associated with a task determine the choices that are available to users as they perform the task. For example, in a damaged goods claim process, the buyer can select to have the goods either reimbursed or replaced.
The act of closing a case by recording in the properties that work is complete.
As a case advances through a flow, information stored in its properties becomes more complete through user input and automatic processing. When the work for a case is complete, the case is marked as "resolved", or "closed".