About Case Entities
- Updated on 02 Mar 2019
- 1 minute to read
A Case is a less structured User Defined Type . where the number of outcomes isn’t as determined as it normally would be in a flow based process.
Cases are usually based on real or existing data which is then evaluated by roles & recorded while moving through the process.
When a user first opens Decisions they are able to see a Cases folder within the studio folder tree. When a Case Entity is being created, the System creates a sub-folder under the Cases folder. In this sub-folder instances can be created for the Case Type Extension . Each Case Type can have its own specific States defined by the Designer . Therefore, each instance of the Case Type Extension goes through its own life cycle of changing defined States . On each State change Assignments can be created for an Account or Group in Decisions .
With all this in mind, Case Entities may be used in dynamic workflow processes where the entity state change can enable or disable actions on the entity.
Rules, forms and workflows can be implemented to seamlessly coordinate cases with other Decisions components.
When to Use a Case?
Cases are best used when there is an expected set of states or stages that the process should follow. Ideally in scenarios where there is unstructured data and the outcome of the process is not consistent.
Cases are often utilized where the process is repeatable but the outcomes are variable as opposed to workflow based systems where a strict path is followed. An example would be a medical professional examining a patient, there is a process of inquiry, booking appointment, running through patient questionnaire and then assessment - a process like this is a perfect use example of cases.