Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

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.

Modifying case types

Updated on April 5, 2022

Modify your case types to reflect your unique business needs. For example, you can change a case type name, or delete a case type when you no longer need it.

  • Renaming case types

    Reflect changes to your business requirements by updating the name of a case type.

  • Reclassifying a case type

    Classify an existing case type as a child of another case type to save time and resources.

  • Deleting case types

    Delete a case type and all associated assets in your application to remove the records that you do not need anymore, for example, when the case type no longer meets your business requirements. You can also delete only the associated case instances, such as sample cases that you do not need after you finish development. Removing irrelevant assets saves you time and money through the efficient management of your database space.

  • Previous topic Running multiple instances of the same subprocess with a Split for Each shape
  • Next topic Renaming case types

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

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