Circumstance VS Performance

I heard circumstance based activity rules with big implementations creates performance issues.

is that rite? If yes why it so?


**Moderation Team has archived 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.


Keep up to date on this post and subscribe to comments

October 22, 2013 - 4:32am

As per Rule Resolution when Pega encounters a rule with circumstance it loads the base rule and its circumstance versions into cache, irrespective of whether the base version is being called or the circumstanced version. Hence too many rules with circumstances can fill up the Rule Cache size and thus leading to performance issues.

July 16, 2014 - 3:51am


I already sent a circumtanced rule to the production but now i want to remove it.how can i achived ?any one have any suggetion?

July 21, 2014 - 3:35am


To prevent the circumstanced rule from being considered for rule resolution, you can "Save As" the base rule to the highiest ruleset version, and click on the "Availibilty" button and select the "Base Rule" checkbox. This will result in all previous circumstanced versions of the rule being disregarded for rule resolution.

July 27, 2014 - 6:17am

I agree with Afzals comment. But I would recommend one more thing to withdraw the circumstances rule so that it does not create confusion going further.