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

SAVE AS of any rule type is very slow



SAVE AS of any rule type is very slow.

Error Messages

Not Applicable

Steps to Reproduce

Try Save As on any rule in designer studio.

Root Cause

In pzSetBestAvailableApplicationLayer, Based on a when rule, the smart way of choosing the application will be selected or current application will be set. The when rule will be defaulted to false and the admin need to make it true to default to the current application.

Changing the activity Code-Pega-List.pzRAMapCasesAndDataTypes will resolve the issue. Instead of calling isRuleSetInDependencyPath multiple times, even for same combination of ruleset+class, a local cache is created which calls this api only once per each unique combination of ruleset+class. This will fix the latency issues when changing applications



Apply HFix-30014

Published October 28, 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