Skip to main content

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Creating a case type

Suggest edit Updated on April 5, 2022

Save time when processing similar business operations by defining case types that are the templates for work in your application. By creating case types, you automate business processes and support the different paths that case workers can follow to resolve a case.

You can structure case types in a hierarchy to define parent-child relationships and share information among cases. To resolve a parent case, first resolve all of its child cases.

For example, you can define the following case types: Accident Claim, Vehicle Damage, and Bodily Injury.

A customer service representative (CSR) creates an Accident Claim case each time a customer reports an automobile accident. After your application verifies the customer's driving license and vehicle identification number, the system creates a Vehicle Damage case that is linked to the Accident Claim case.

The CSR decides whether the application needs a Bodily Injury case, based on information from the customer and the search results for similar cases. When other CSRs process the Vehicle Damage and Bodily Injury cases, the CSR enters funds payable and updated policy premium in the Accident Claim case.

A case manager then receives a notification that the Accident Claim is ready for review.

  • Creating a top-level case type

    Improve work processing in your application by creating top-level case types that visualize business processes. When you visualize a business process, you can conveniently divide the process into phases, and then track and manage work with greater ease.

  • Creating a child case type

    Create child case types to ensure that users of your application address all elements of a complex business process before resolving the case. When you supplement your business processes with child case types, you create dependencies that these case types represent.

  • Creating a case type rule form in Dev Studio

    Provide advanced options for your business processes by creating case types through a case type rule form. For example, you can select an application layer in which to store your case type, or define multiple options at once, for example, for the people that your case type involves, processes that can support your case type, or dependencies with other case types.

Did you find this content helpful? YesNo

100% found this useful

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us