Close popover
Frederi Pochard (POCHF)
Senior System Architect
Pegasystems Inc.
POCHF Member since 2009 20 posts
Posted: May 12, 2017
Last activity: May 15, 2017

About the "Report on descendant class instances" option on Report Definitions


Here is the situation:

Pega 7.22/CELS 7.22

The client needs to create it's own Contact data class (inheriting from PegaCA-Interface-Contact).

Of course, once it's done the DCR must be modified so the InterfaceContactClass property in the Declare_CAApplicationSettings is valued with the name of the customiz Contact data class. And this is done. And the custom class is mapped to its own specific data table.

And the client expected things were going to work that way. Of course it didn't. Because report definitions were defined on the PegaCA-Interface-Contact class without the "Report on descendant class instances" selected.

So all the report definitions must also be "saved-as" and customized in order to activate this option.

Which begs the question: why is it not selected by default? considering this leads to issues and some quick but repetitive customization work on all related report definitions when a client is adding a class inheriting from an OOTB data class?

My answer would be: in order not to systematically add an overhead when this option is not needed. But is that right and is that all?

Or maybe there should be hotfixes in order to switch all/some report definitions to have this option selected by default? So the client only have to create its class and change the DCR?

Any explanations and thoughts welcome.



Low-Code App Development Data Integration
Moderation Team has archived post,
Close popover This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.