Question
Bernafon Hörgeräte GmbH
DE
Last activity: 8 Apr 2024 14:01 EDT
Circumstancing case processing
Hi!
Below is a question from the academy which I'd need some more clarification to the choice of answer given.
Based on the information below, if you execute the Rule when .Dept=Accounting, which version does Pega Platform™ use?
Rule Version Circumstance
01-01-01 None
01-01-01 .Dept=Accounting
01-01-15 None
01-01-25 None, base Rule selected
01-01-30 .Dept=Accounting
01-01-35 None
-
01-01-01, .Dept=Accounting
-
01-01-25, None, base Rule selected
-
01-01-01, None
-
01-01-30, .Dept=Accounting .Please, I'd humbly like to know why 01-01-35 wasn't considered. Thanks
Accepted Solution
Updated: 8 Apr 2024 12:44 EDT
Maantic Inc
IN
Maantic Inc
IN
01-01-30 was not considered because on the page where the rule was running, Pega not able to evaluate the value of property .Dept=Accounting. So it ignored it and selected the next available version 01-01-25, which is the base version so no need to evaluate anything here.
Bernafon Hörgeräte GmbH
DE
The question as mentioned earlier is an Academy quiz question . The Academy chose
01-01-30 .Dept=Accounting as the right answer. My question is why wasn't 01-01-35 None
considered?. 01-01-35 None, being the highest uncircumstanced version with respect to the base
rule version (01-01-25 None, base Rule selected)
Accepted Solution
Updated: 8 Apr 2024 12:44 EDT
Maantic Inc
IN
Ok I think I got a better clarity of the example now.
Whenever a rule has been circumstanced, Pega's rule resolution will check the circumstance condition first in the versions. If its able to find it then it'll consider that version even if the version might not be the highest in the stack. In your case 01-01-35 was the highest available base version, but the page on which the rule was running had the condition .Dept=Accounting present, so it ignored 01-01-35 and chose 01-01-30, which is the highest available circumstanced version.
@ArnoldG16957468
Ok I think I got a better clarity of the example now.
Whenever a rule has been circumstanced, Pega's rule resolution will check the circumstance condition first in the versions. If its able to find it then it'll consider that version even if the version might not be the highest in the stack. In your case 01-01-35 was the highest available base version, but the page on which the rule was running had the condition .Dept=Accounting present, so it ignored 01-01-35 and chose 01-01-30, which is the highest available circumstanced version.