Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Skimming not working properly

SA-17492

Summary



Developer is trying to perform a minor version skimming and could see that only 2 rules are getting moved to the skimmed version, but the actual rule count is 946.
 

Error Messages



NO Error Messages

Steps to Reproduce



1. Login to PRPC 7.1.8
2. Launch Refactor Ruleset and select Skim a Ruleset.
3. Select any Ruleset.
4. Provide new ruleset version.
5. Then Skim.
 

Root Cause



A defect in Pegasystems code or rules. The skimming logic is using a prepared statement to fetch the records to be skimmed. The same .pyPreparedValues page is used to pass the prepared statement parameters for a set of queries executed in a for loop.

When prconfig/security/showSQLInListPage is set to false, .pyPreparedValues page is removed from clipboard before executing the query. So, when the first query is executed, this page is removed and for subsequent queries the prepared values are not correctly set. So, only Rule-Obj-Property types are skimmed and rest is ignored.

Resolution



Perform the following local-change:

Set showSQLInListPage to true, so that .pyPreparedValues page is not cleared from memory.

Published January 31, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

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

Pega Community 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
Contact us