Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Dennis Jiang (jiand1)
PEGA
Senior Engineer, Technical Support
Pegasystems Inc.
US
jiand1 Member since 2019 5 posts
PEGA
Posted: Nov 20, 2019
Last activity: Dec 2, 2019
Posted: 20 Nov 2019 10:01 EST
Last activity: 2 Dec 2019 9:24 EST
Closed
Solved

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***

To see attachments, please log in.
Pega Platform
Data Integration
Support Case Exists

Accepted Solution

Posted: 5 years ago
Posted: 20 Nov 2019 22:38 EST
Susan Liu (SusanLiu_GCS)
PEGA
Senior Principal Engineer, Technical Support, Runtime Engine
Pegasystems Inc.
US

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. 

To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice