Skip to main content


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

Importing a case type

Updated on November 22, 2021

To reduce the complexity of your application, share templates for business processes between your applications by importing case types.

For example, when you have multiple applications to deal with different kinds of loan requests, you can share the template for the loan request review process.
Before you begin: Add an application that contains case types that you want to reuse to your built-on applications stack. Ensure that the application is on top of the stack. For more information, see Adding built-on applications.
  1. Define a build-on application from which you want to import the case types:
    1. In the navigation pane of Dev Studio, click App.
    2. Under the name of your application work pool, click SysAdminClass.
    3. In the Class inheritance section, in the Parent class (Directed) field, enter the work pool of your built-on application.
    4. Click Save.
  2. In the navigation pane of App Studio, click Case types.
  3. In the Case types panel, click OptionsImport case types.
  4. Review the list of top-level case types that you add to your application.

    Case types with the same name as an existing case type in your application do not appear in this list.

  5. Optional: To exclude a case type from the import process, clear the check box next to the name of that case type.
  6. Click Submit.
Result: The case type and its child case types now exist in your application. Supporting rules, such as the starting flow for a case type, continue to reside in the built-on application. You can leave them there, or create specialized versions in your application.

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