Administrator Guide > Cases > Case Processes |
A Case Process is a collection of tasks grouped together to perform a business function such as an automobile repossession. Case processes are assigned to case types to include the business functions necessary to resolve a case.
The Case Process topic includes the following attributes and instructions to assist administrators with creating, copying, editing, and deleting case processes:
Administrators can create new processes and manage existing ones by navigating to the System Management > Collections > Case Processes page.
The Case Process page contains a grid that displays a list of all the case processes configured. This grid contains the following details:
Column | Description |
Name | The name of the case process. |
Description | Details about the case process. |
Last Modified | Denotes when the last modification was made to the case process. |
Modified By | Denotes who made the last modification to the case process. |
All case processes share common attributes that are defined while creating, copying, or editing a case process.
The general attributes provide basic information about case processes and are located on the general tab.
General attributes are located on the General Tab:
Attribute | Description | ||
Name | Enter a name for the case process. This is a required field. | ||
Description | Provide details about the purpose and use of the case process. The case process description is visible to administrators from the case processes administration page and end users when they browse case processes to add to a case. | ||
Workday Schedule |
Specify the default calendar to be used when creating new tasks within the Case process. The workday schedule calendar is used to calculate a task's expected start, completion, and due dates, and is also used to calculate the task Escalate Schedule. See Workday Schedules for more information.
|
The tasks attribute is an interactive screen for administrators to build a Case process. There are five task types that can be included in a case process: General, Screen, Execute Code, Workflow, and Execute Rules.
![]() |
For more information about the available task types, please see the Case Tasks topic in this guide. |
The case types attribute allows administrators to assign a case process to case types. If a case type is assigned to the case process, the process is available to be added to the case by a user with appropriate permissions.
Attribute | Description |
Available | Displays a list of all Case Types configured in System Management > Collections > Case Types. Assign a case type by selecting the desired case type(s) from the Available Case Types list and move them to the Assigned Case Types. |
Assigned | Displays a list of the Case Types assigned to the case process. Once the case process is saved, it is assigned to the designated Case Types. |
The Create function allows administrators to create new case processes that can be utilized in case types.
To create a case process navigate to System Management > Collections > Case Processes and click .
Navigate through the tabs and define the case process attributes.
Custom case processes are built on the task tab using the interactive interface to add tasks, create dependencies, and define results. The tasks tab provides the ability to make complex case processes fast and easy.
To build a case process, right-click anywhere within the Tasks tab to display a list of task types available to create and add to a case process. Select a task type from the list.
The Task Editor screen appears. Navigate through the tabs and assign attributes to the task.
![]() |
For more information about tasks and their attributes, see the Task Types topic in this guide. |
When finished assigning attributes click . The new task populates within the Tasks tab.
Once a task is added to a case process, the task may be moved by clicking the task and dragging it to the desired location in the screen.
![]() |
Editing a Task
Deleting a Task
|
When multiple tasks are included in the process, they can be linked to create a dependency.
To link the tasks:
Hover over a task to display the connection points of the task.
Click on a connection point and drag the mouse to the result task that is to be dependent based on the completion of the first task. An arrow link is formed that represents the flow of the process.
The Attended Meeting of Creditors task is dependent on the Meeting of Creditors task and does not start until the Meeting of Creditors is completed.
![]() |
A task can be dependent on multiple tasks. In this case, the task does not start until all dependent tasks have been completed. |
Any task in a process that is not dependent on another task is a startup task, and is available within the task tree when a case is opened. There is no limit as to how many start up tasks can be in a case process.
![]() |
If a delay has been assigned to a startup task it displays as a Waiting to Start task. If there is no delay, the task displays as an In Progress task. For more information on task statuses, please see the Task Statuses topic in the End-User guide. |
Once tasks are linked, a result can be defined by typing the result in the blue text box on the link. The result creates a conditional dependency; therefore, a task is only eligible to be worked if a dependent task is completed with the result defined in the dependency.
![]() |
The results in the blue textbox are results available to the user to select from when completing a task. When a result is selected, the task associated with it becomes In Progress in the case. |
Processes can be configured to allow a single task to have multiple resulting tasks based on the different results. For example, in an Auto Repossession case, if a car is auctioned off, the Auction task may need to result in a deficiency recovery task or a surplus payment task, depending on how much the car sells for. In this situation, a task can link to multiple tasks with a different conditional dependency defined for each result.
![]() |
When configuring the task, an administrator has the option to allow for one or multiple results to be selected. This can drive the process down multiple paths.
|
Example
To illustrate how a case process is configured, please see the below example.
The following depicts an auto repossession case process. The administrator must configure a case process to complete the below tasks:
The tasks attribute of case processes makes building a complex process, such as the above, simple.
Once the defaulted loan has been verified, the next task is to seize the vehicle. Because seizing the vehicle is the only result after confirmation of a default, a conditional dependency is not required.
The administrator configures the process that determines what to do after the vehicle is seized, Retain the Vehicle, Reinstate the Loan, or Sell the Vehicle.
This is accomplished by creating conditional dependencies based on the completion of Seizing the Vehicle. By inserting results into the blue text boxes, an administrator can configure one task to have multiple results to select from while completing the task.
In this example, only one of the results can be selected by the end user when they complete the Seize Vehicle task.
![]() |
Tasks can be configured to allow users to select one or multiple results. There is no limit as to how many dependent tasks can be linked to a single task. |
A task can produce multiple results. If there is no dependency between results, the resulting tasks can be completed simultaneously.
In the Auto Repossession case process, the Reinstate Loan Workflow results in the return of the vehicle to the account holder, and, if necessary, a deficiency recovery workflow.
![]() |
To reduce the number of tasks in a process, a single task can be used as a result for multiple tasks. |
Continuing the auto repossession example, if an institution decides to retain the vehicle as payment or sell the vehicle, the institution needs to return the account holder's personal property that was in the vehicle and potentially recover a deficiency payment.
Only a return personal property task needs to be configured because a deficiency workflow task already exists. The retain vehicle and sell vehicle tasks can be linked to both the return personal property task and the deficiency workflow tasks as shown below.
![]() |
If the vehicle is sold, a surplus workflow may be needed instead of a deficiency workflow.When completing the sell vehicle workflow, users have to select a deficiency or surplus, and to return the personal property. |
When finished entering all the information, click to save the new case process and return to the Case Processes page. The new case process populates in the grid and can be worked by users with the appropriate permissions while working associated Case Types.
![]() |
Useful tips to use while building a case process:
|
The Copy function enables administrators to duplicate the structure of an existing Case Process. The existing Case Process can be used as a base for creating a new Case Process.
Highlight the process that is to be copied and click .
The Copy Case Process screen appears. Navigate through all of the tabs and make any necessary changes to the task process.
When finished entering all information, click to save the new process and return to the Case Processes page. The new process is now listed in the grid and available to be run by users when working a case. Click Cancel to return to the Case Process page without saving the case process.
The Edit function enables administrators to revisit existing case processes and edit the attributes assigned to them.
Highlight the process that is to be edited and click .
The Edit Case Process screen appears. Navigate through all of the tabs and make any necessary changes to the case process.
When finished entering in all information, click to save the process and return to the Cask Processes page. Click Cancel to return without saving.
Highlight the process that is to be deleted and click .
A confirmation message appears.
Click Yes to delete the case process. Click No to return to the Case Processes page without deleting the case process.