Key case management features in TotalAgility
-
Case definition processes where you define fragments that can share case artifacts.
-
Case fragment processes are linked to the case definition and can directly access case artifacts such as data, roles, and process events.
-
SLA (Service Level Agreement) to manage key performance indicators across a case and fragments that allow process participants to rapidly view when processes are at risk of exceeding targets and allowing them to take corrective action if necessary.
-
Associated (shared) processes to a case.
-
Process events for inter-process synchronization.
-
Dynamically allocate resources to drive resource assignment at runtime based on attributions of the case.
-
Fixed and floating roles within the case.
-
Skins, different flavors of the case fragments based on attributes of the case.
-
External resources used within the execution of the case.
-
Case closure to wrap everything up when the case is completed or terminated.
-
Case states, the states a case can go through.
-
Key case milestones that can influence tasks within fragments.
-
Work types for grouping and finding running jobs. For case management, an additional attribute, Scope indicates whether all fragments use the case data, or have their copy.
-
Metrics
-
Case reference set up after case creation.
It is not always possible to know the case reference when creating the case manually; it can be set up automatically within the process after case creation.
-
Understand the link between fragments versions and case versions. As a fragment has the reliance on the case definition, all fragments and cases must be kept synchronized.
-
View consolidated information at runtime and view all tasks in chronological order regardless of the process they were executed in.
-
Action to take if the case is terminated or completed without all associated processes being complete.