@GaneshKumarC17388662   ⚠ This is a GenAI-powered tool. All generated answers require validation against the provided references.

it is indeed possible to convert an Adhoc case into a Case Type and then reuse that Case Type for further case creation in Pega 23. The documentation refers to a feature called "Configure for Reuse" that allows this conversion.

Converting an Adhoc Case to a Case Type

There are two approaches to handling this conversion:

1. Using the "Configure for Reuse" Feature

Pega 23 provides a "Configure for Reuse" option that allows you to transform an ad hoc case into a structured case type. This feature lets developers analyze the adhoc case structure and create a standardized case type based on it. The Case Designer can then be used to visualize and manage the workflow, ensuring the new case type meets business requirements effectively.

2. Manual Conversion Process

If the "Configure for Reuse" option is not available or accessible in your implementation, you can follow these steps to manually convert an adhoc case to a case type:

1. Identify the Adhoc Case - Select the adhoc case that represents a common pattern that should be standardized
2. Analyze the Case Structure - Review the actions, data, and flow associated with the adhoc case to understand what elements need to be included in the new case type
3. Create a New Case Type - Navigate to the Case Types section in App Studio and click 'Create Case Type'
4. Define Stages and Steps - Set up stages and steps that reflect the actions that were part of the adhoc case
5. Configure Data Propagation - If necessary, configure how data will be handled in the new case type
6. Test the New Case Type - Create instances of the new case type to ensure it functions as expected
7. Reuse the Case Type - Once validated, you can reuse this case type for future case creation

Real-World Example

This is particularly useful in scenarios like the one mentioned in the Pega documentation: imagine a banker creating an adhoc case for a high-net-worth client that includes steps like sending a welcome letter, scheduling a follow-up call, and reviewing results. If this becomes a common pattern, converting it to a standard case type would streamline future similar scenarios.

The documentation specifically states: "Because ad hoc Cases are tracked in Pega Platform, if the bank finds that this is a common pattern for high net-worth clients, they should convert the ad hoc Case into a child Case that becomes a standard part of the Case Type for opening an account."