A standard form that is automatically managed by your application for each case type that you define. A dynamic view displays fields from your data model during different events, such as creation and resolution, in the life cycle of a case.
A standard form that is automatically managed by your application for each case type that you define. A dynamic view displays fields from your data model during different events, such as creation and resolution, in the life cycle of a case.
A view of your data that displays information or collects input from users as they create, update, and resolve cases in your application. Open your case type from the Application Explorer to access the options for configuring a form.
A collection of entities and attributes that describes the objects that are modeled in an application, and their relationship to each other.
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".
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.