Our use case is to add a category(property) to the custom rule form and categorize each and every custom rule. In our project , we have around 500 custom rules and we have a separate portal to maintain those 500 + rules.

We have report definition under Data-Rule-Summary that fetch these rules and renders on the portal and if user click a rule, it goes to pr4_rule and open that custom rule and display. So we would like to add these additional column to the pr4_rule_vw table, so that we can use the existing report definition to fetch the data.

My question is that , if there is a custom rule type in the product and it allows customer to use it, then these tables should be extendable. ( might be with some restriction ).

Is there a reason why Pega restrict the client/customers  from extending these tables and keep the data population code within the engine and not exposing to customer or client?. or if the code is within engine, is there any recommended approach?

Thanks,

Nagarajan Kadhiresan