Published on November 20, 2019 - 10:01am
Last updated December 2, 2019 - 9:24am

Login to like
Question

IsDetectForStaleRuleEnabledValue DSS change

Have an issue that was resolved by modifying the DSS setting as described below:

https://community.pega.com/support/support-articles/rule-access-inconsistency-issue-rule-checkout-and-checkin

I'm wondering why by default this is not enabled, and if there are any possible side effects by enabling this?

***Edited by Moderator Marissa to update SR Details***

Data management
Pega Platform

Group Tags

Related Support Case Number: 
SR-D59531
Correct Answer
SusanLiu
November 20, 2019 - 10:38pm

Pega has added the capability of enabling/disabling the logic to identify rule's staleness via a dynamic system setting : IsDetectForStaleRuleEnabled. Essentially, even if a rule is stale, user will be prompted with the options to overwrite/reload only when this system setting is set to true.

The default value for this system setting will be false so that users are not suffering unintentional performance hit. Users need to set this DASS to true to leverage the stale rule detection feature. 

View correct answer in context

Comments

Keep up to date on this post and subscribe to comments

SusanLiu
Pega
November 20, 2019 - 10:38pm

Pega has added the capability of enabling/disabling the logic to identify rule's staleness via a dynamic system setting : IsDetectForStaleRuleEnabled. Essentially, even if a rule is stale, user will be prompted with the options to overwrite/reload only when this system setting is set to true.

The default value for this system setting will be false so that users are not suffering unintentional performance hit. Users need to set this DASS to true to leverage the stale rule detection feature. 

  • reply