Question
JCS Lanit - BPM
RU
Last activity: 9 Apr 2019 9:15 EDT
When rule resolution no longer checks @baseclass
In Release Notes for Pega 8.1it is stated that "When rule resolution no longer checks @baseclass". It sounds really frightening. Does anybody knows what it actually means?
We have made a series of experiments and didn't find any unsuals behaviour of rule resolution for When rules applied to @baseclass. To be more specific we have tried the following:
- Calling OOB When rules (for example, Always, Never, has Messages, etc) from @baseclass on a page with an application-level class.
- Calling custom When rules from @baseclass on a page with an application-level class.
- Overriding and then withdrawning When rules from @baseclass in application-level class and using them in a context of an application-level page.
- Calling When rules from a @baseclass on classless pages.
In all cases When rules from @baseclass were successfully resolved and executed.
I have tried posting a SR, but got no result except for recommendation to ask this question here.
Will appreciate any insight about what this release note really means and what problems one will face regarding rule resolution of When rules after upgrading to Pega 8.1.
***Moderator Edit-Vidyaranjan: Updated SR details***
Accepted Solution
Pegasystems Inc.
US
Hi ,
Thanks for highlighting this. I guess the documentation here is a bit confusing and might not truly reflect the change and its effect. We will get this cleaned up in 8.3
I guess the change discussed here is , in cases where the step page context is null or the pxobjclass associated with the step page is empty will will no longer use @baseclass as default to resolve rule.
This is not a common use case and in general should not impact system where we generally have the page context set up correct.
PEG
US
I don't think this is true. Either you've misinterpreted something in the release notes, or the release note was written in such a fashion that the wrong statement is present. Can you provide me with the link to the release note in question?
Accepted Solution
Pegasystems Inc.
US
Hi ,
Thanks for highlighting this. I guess the documentation here is a bit confusing and might not truly reflect the change and its effect. We will get this cleaned up in 8.3
I guess the change discussed here is , in cases where the step page context is null or the pxobjclass associated with the step page is empty will will no longer use @baseclass as default to resolve rule.
This is not a common use case and in general should not impact system where we generally have the page context set up correct.
JCS Lanit - BPM
RU
By the way, I have reviewed a research we've done internally and found out that When rules from @baseclass are successfully resolved on pages with empty pxObjClass. Please refer to a short video I've prepared for you. OOB when rules Always and Never are used for simplicity, but custom When rules from @baseclass we have also checked during our research.
JCS Lanit - BPM
RU
Hello Coher,
Thank you for your reply. The question contains a link to release notes filter (https://community.pega.com/knowledgebase/products/platform/release-notes?q=when&f[0]=version%3A26871) because the release note I am talking about doesn't have a dedicated page.
I have attached a screenshot for your convenience.
Regards,
Alex.
PEG
US
Did you see this response? It seems the change is much more restricted, and actually makes sense. The documentation certainly needs a cleanup, and I will raise a documentation bug. Here is the answer:
Thanks for highlighting this. I guess the documentation here is a bit confusing and might not truly reflect the change and its effect. We will get this cleaned up in 8.3
Did you see this response? It seems the change is much more restricted, and actually makes sense. The documentation certainly needs a cleanup, and I will raise a documentation bug. Here is the answer:
Thanks for highlighting this. I guess the documentation here is a bit confusing and might not truly reflect the change and its effect. We will get this cleaned up in 8.3
I guess the change discussed here is , in cases where the step page context is null or the pxobjclass associated with the step page is empty will will no longer use @baseclass as default to resolve rule.
This is not a common use case and in general should not impact system where we generally have the page context set up correct.