Question
Pegasystems Inc.
JP
Last activity: 17 Jul 2017 16:44 EDT
Why the Properties come from directly inherited parent class does not show up in the Application Explorer
We have an application like below using PRPC 7.1.17.
MyApp:01-01
Built on application:
PegaRULES:07-01
Application RuleSets:
1.MyAppUIRuleset:01-01 (contains rules related to user interface: flows, flowactions, sections etc.)
2.MyAppBizRuleset:01-01 (contains rules related to business logic: properties, declare expression, map value, decision table etc.)
For the shake of clear separation between rules handling User Interface and the rules handling business logic, the development team made the below decision.
All properties which is only being used for the presentation purpose should be defined in MyAppUIRuleset and Applies to the class which associated with MyAppUIRuleset.
By following this architectural decision, developers defined two classes, MyCo-UI-Data-Product directly inherit MyCo-Biz-Data-Product.
The application functions just fine, however the UI developers faces a problem with the Application Explorer of the Designer Studio:
Properties come from directly inherited parent class does not show up in the Application Explorer.
We have tried the [Explorer inheritance -> Directed] option from the drop down menu of Application Explorer, and it didn't work.
We have an application like below using PRPC 7.1.17.
MyApp:01-01
Built on application:
PegaRULES:07-01
Application RuleSets:
1.MyAppUIRuleset:01-01 (contains rules related to user interface: flows, flowactions, sections etc.)
2.MyAppBizRuleset:01-01 (contains rules related to business logic: properties, declare expression, map value, decision table etc.)
For the shake of clear separation between rules handling User Interface and the rules handling business logic, the development team made the below decision.
All properties which is only being used for the presentation purpose should be defined in MyAppUIRuleset and Applies to the class which associated with MyAppUIRuleset.
By following this architectural decision, developers defined two classes, MyCo-UI-Data-Product directly inherit MyCo-Biz-Data-Product.
The application functions just fine, however the UI developers faces a problem with the Application Explorer of the Designer Studio:
Properties come from directly inherited parent class does not show up in the Application Explorer.
We have tried the [Explorer inheritance -> Directed] option from the drop down menu of Application Explorer, and it didn't work.
***Updated by moderator: Marissa to close post***
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
Accepted Solution
Pegasystems Inc.
GB
Hi Chunzhi,
I think that the behavior that you are describing is working as designed. The Explorer Inheritance setting is used to determine which classes to show in the tree, and not which rules appear under which classes.
https://community.pega.com/sites/default/files/help_v717/procomhelpmain.htm
To give an example I configured something similar. 2 Data classes, one called ParentData and one called ChildData. ChildData is configured to directly inherrit from ParentData.
With Pattern Inheritance I do not see the ChildData class in the App Explorer tree when looking at the ParentData class, but with Directed enabled I do see it (see the screen shot below).
Hi Chunzhi,
I think that the behavior that you are describing is working as designed. The Explorer Inheritance setting is used to determine which classes to show in the tree, and not which rules appear under which classes.
https://community.pega.com/sites/default/files/help_v717/procomhelpmain.htm
To give an example I configured something similar. 2 Data classes, one called ParentData and one called ChildData. ChildData is configured to directly inherrit from ParentData.
With Pattern Inheritance I do not see the ChildData class in the App Explorer tree when looking at the ParentData class, but with Directed enabled I do see it (see the screen shot below).
I guess what your users are expecting to see is the ParentText1 property showing up under the Property group for the ChildData class. I believe that this would be an enhancement to the product (e.g. an additional show inherrited rules option). It may be a little confusing to have ParentText1 show up under the ChildData class if it is not really defined there. In the second screen shot below it would then appear twice, once under ParentData - Property and once under ChildData - Property. I guess it could appear greyed out or something to indicate that it is not really part of that class.
Pegasystems Inc.
JP
Hi Marc,
Thanks for your reply.
Show inherited properties is going to be a very useful feature in our situation, because most of the business entity related properties are defined under the parent class, only a few properties defined under the child class to handle presentation layer UI/UX issues.
Pegasystems Inc.
GB
One way you can view this is to use the Record Viewer like this.
- Right click on the Property group and select View
- Check the include inherited box, and filter the Applies to class to the ones you want to see.
