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

Performance issues on Directed Web Access(DWA) screen in Chrome



UI generated by Pega in an external assignment using Direct Web Access (DWA) is fast in IE, but lags when clicking radio buttons, check boxes, etc in Chrome.

Error Messages

No error. There is a performance hit. 15 second lag in Chrome
is observed as compared to IE

Steps to Reproduce

1. Click on URL generated by DWA. This will load up a Pega UI screen.

2. On the screen, click Radio Buttons/Checkboxes in IE.

3. Repeat the same test in Chrome and compare the time lag.

Root Cause

The root cause of this problem is a defect in Pegasystems’ code/rules.
The pega.util.Dom.getElementsByName API in (pega_yui_extensions.js) is programmed to use XPath query for non-IE browsers which is causing performance impact in case of Chrome.

The fix was to use getElementsByName DOM API if the root of the search is the document object else fallback to XPath query in case a DOM element is specified as root of the search.


This issue is resolved by hotfix item, Hfix-9730

Published March 12, 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