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.

Support Article

Framework case types not seen as importable in application class



After defining a framework (fw) layer with no case types and an application (app) layer, case types defined for the fw layer are not available for importing into the app layer.

Error Messages

myFWclass framework has no case types to import

Steps to Reproduce


  1. While logged in as [email protected], use application-menu - > new application to make a framework without any cases.

  2. Log in as the admin user for the new framework and use the same menu to define an application on top of the new framework.

  3. Use application-menu - > switch application, to switch back to the framework layer.

  4. Click "cases" in left margin and then use case types - > add a case to define one new case.

  5. Use application-menu - > switch application, to switch back to the application layer and click "cases" in left margin to use case types - > import a case, in an attempt to import the case created at the framework layer.  The issue is that the case is not shown.


Root Cause

If at least one case type is originally specified when the fw is defined, then when the app is defined, the app class' parent class is set to be the fw class. If no case types are specified, the app class's parent class is set to Work-Cover-.


This issue is resolved through the following local change: Manually set app parent class to be the fw class.


Published January 31, 2016 - Updated October 8, 2020

Was this useful?

100% found this useful

Have a question? Get answers now.

Visit the Collaboration 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 Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us