Hi,

The PEGA0032 alert is generated if a rule change (update, deletion, or creation) produces many invalid entries in the rules assembly cache.

The threshold applies to the sum of the following three counts:

• Rules removed from the global rules assembly cache
• Rules removed from the personal rules cache (checked-out rules)
• Generated Java classes that were invalidated

Frequent occurrences of this alert indicate that changed rules are invalidating other rules. This condition slows system response because of new rule assembly processing.

Hi,

The PEGA0032 alert is generated if a rule change (update, deletion, or creation) produces many invalid entries in the rules assembly cache.

The threshold applies to the sum of the following three counts:

• Rules removed from the global rules assembly cache
• Rules removed from the personal rules cache (checked-out rules)
• Generated Java classes that were invalidated

Frequent occurrences of this alert indicate that changed rules are invalidating other rules. This condition slows system response because of new rule assembly processing.

Example message text

Change to Rule-Obj-Property:PYPURPOSE caused 14 global entries, 14 personal entries (0 personal only), and 4 classes to be invalidated. Rules invalidated (entry count): activity:getshortcutsxml (4), activity:getworkstyle (5), activity:requestorinitialize (5), activity:populatemyrules (4)

Default prconfig.xml setting

<env name = “alerts/fua/invalidation/threshold" value="10" />

The threshold value is a positive integer identifying the number of invalid entries. The default value is 10.

You can configure threshold accordingly as well.

Kindly notify, if it helps you.