Generating a Case Type using Pega GenAI Autopilot

With Autopilot, you can create a Case Type in a Pega Platform application with just a few clicks.

In this example, U+ Bank creates the first Case Type for the new Life Insurance application.

To create a Case Type, you select the Case Type tab from the navigation pane of App Studio.

When you create a Case Type with assistance from Autopilot, the system proposes a list of potential Case Type names based on the name of the application and other application metadata.

In the following figure, Autopilot proposes Case Type names such as Life Insurance application, Policy Underwriting Process, Claims Submission Workflow, and Beneficiary Designation Form:

You can select one of the Autopilot suggestions by clicking a suggested Case Type name, or you can enter a custom Case Type name in the Create Case Type dialog box.

This example uses the Life Insurance Application Case Type from the Autopilot suggestions, as shown in the following figure:

By selecting the Use Autopilot to suggest a Life Cycle and Data Model radio button in the Create Case Type dialog box, Autopilot uses the name of the Case Type and other application metadata to propose a series of Stages and Steps.

The following figure shows the Autopilot suggestion for the Stages and Steps that are associated with the Life Insurance Case Type:

The Stages represent the understanding that Autopilot has about major milestones as a Case progresses from creation to resolution. The Steps represent Autopilot's interpretation of the events that the system or a Case participant must complete to move from one Stage to the next.

The Stages and Steps proposed by Autopilot are based on Pega application development best practices and capitalize on Pega Platform features for workflow Automation, such as approvals and automated notifications.

At this point in the Case Type creation process, you can review and modify the Autopilot recommendations for Stages and Steps to match the workflow defined by your project's stakeholders.

After confirming the Stages and Steps by clicking Next, Autopilot suggests a Data Model for the Case Type. The suggestions save developers the time and effort that they typically require to identify and manually enter the data elements associated with a Case Type.

Autopilot's proposed Data Model includes the pieces of information, or fields, that Autopilot identifies as necessary to resolve a Case. In Pega Platform, each field is a named, reusable UI component. Each field in the proposed Data Model consists of a Name, Type, and ID. The Name of the field identifies the unique data element in the system, and the Type of the field identifies the type of information that is stored in the system for the field. The field ID is Pega Platform's technical reference for the field.

As seen in the following figure, the Data Model associated with the Life Insurance Case Type includes field names such as Policy Number, Insured Name, Insured Age, Policy Details and Claim History: 

The Types assigned to the proposed fields include Text, Date only, Picklist, Currency, Integer, the data relationship field types Embedded Data, and Data reference, among others. For the fields with the data relationship field types of Embedded Data or Data reference, Autopilot now creates the associated data object.

In the same way that Autopilot generates the Stages and Steps of a Case Type, you can edit the Name or Type associated with each field proposed for the Data Model. You can add more fields to create a data structure that aligns with the workflow defined by your project's stakeholders. If necessary, you can even delete the fields proposed by Autopilot.

After you are satisfied with the information associated with the proposed names for the Case Type, Stages and Steps, and the Data Model, you click Submit to create the Life Insurance Case Type in the Life Insurance application. The Autopilot-proposed Case Life Cycle for the Life Insurance Case Type is displayed on the Workflow tab, as shown in the following figure:

The fields associated with the Data Model created by Autopilot is displayed on the Data model tab, as shown in the following figure:

With Autopilot, developers of all skill levels can build the Case Types, Case Life Cycles, and Data Models associated with their application in record time.