What is a case solution
Solutions consist of case types, activities, steps, and
other components. A solution is an application that case workers use
to process cases.
The following diagram illustrates the main case artifacts and how they relate to one another.
- Solutions
- A solution consists of one or more related case types that provide the documents, data, business processing, and routing to the case workers. For example, a solution for a human resources department might include a case type for new hires, a case type for retirement, and a case type for employee termination.
- Case types
- Case types define the activities, the necessary document types to support the activity, the activity steps, and the roles that must complete those steps to solve a business problem. The case type also includes properties that are displayed to case workers in views at run time. Case types make up a solution. A case is an instance of a case type.
- Document classes
- Document classes help you to organize and classify the documents that belong to a case. You can provide additional information about the documents by assigning properties to the document class. For example, a document class might be a job application form.
- Rules
- A case type can contain rules. A rule determines the actions to take if particular conditions are met in a case. After you create business rules for your case type, you can use the business rules in an activity to determine process routing or to update case properties.
- Views
- A case type can contain views. A view specifies the properties that are displayed to a case worker for a case type. For each case type, you can specify the properties that are displayed for the case summary and the properties that are searchable. In addition, you can specify the one or more views for the properties that are displayed in the Properties widgets that case workers use to complete cases and work items.
- Activities
- A case contains activities. An activity has one or more steps that must be completed to complete the activity. For example, an activity might be to review new hire applications. A case is not complete until all activities that are marked as required during solution design, as well as all activities that have been started, are completed or manually disabled. Each activity has roles that are associated with it. You can also implement an activity as a business process.
- Steps
- Steps are the actions in a process that must be completed for an activity. For example, a step might be to review a job application form. You assign the steps to roles or workgroups.
- Roles
- A role represents a specific business function. For
example, a role might be an Applicant or Supervisor. You assign users
to roles. You use roles to access a particular activity.
You define roles for the entire solution. You then associate roles with activities.
- Pages
- A page contains the widgets that users of the solution application use to complete an activity. A page consists of a layout, widget configurations, and the flow of events between widgets.
- In-baskets
- Each solution has a personal in-basket that contains steps for activities that are assigned to a specific user. The personal in-basket differs from the role in-basket. The role in-basket contains work items that are assigned to a role, but not to a specific person. Work items in a role in-basket can be accepted by any user to work on.