Troubleshooting: Activity with step page call to multivariate circumstance decision table yields incorrect results
Your Pega Platform™ application contains an activity with a step page that calls a multivariate circumstance for a decision table. When calling the decision table, the step page uses the Property-Map-Decision-Tree method, a fairly common usage. The step page is defined with a different class than the primary page. When the decision table attempts to find the circumstance template, the step page is ignored. Hence, the activity’s decision results always resolve to the base class version of the decision tree.
- Create a circumstance template.
- Create circumstance definitions for this template.
- Create a decision table.
- Circumstance the decision table using the circumstance definitions created in Step 2.
- Create an activity using a step page to call the circumstance decision table.
The decision results are not what you expect, since during Rule resolution the system checks for the circumstance template in @baseclass, while the template is present in the PegaSample class. However, the circumstance template is defined on properties present in PegaSample, and not in @baseclass. Pega Platform is loading all the required rules into pr_sys_cache_entry properly, but while looking for RULE-CIRCUMSTANCE-TEMPLATE in pr_sys_cache_entry, it is looking at @baseclass as pxleafclassname.
Decision circumstancing works with the primary page and not with the step page.
Change the activity so that it calls the primary page, not the step page.
All circumstancing works with the primary page, not just Decision rules.
For more information, see Learning about multivariate circumstancing.