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

openWorkByURL opening in new thread post upgrade



'OpenWorkByURL' is used for custom bulk processing functionality.

After upgrading from PRPC 6 to Pega 7, openWorkByURL javascript method runs the activity in a new thread hence breaking the existing functionality.

User requires a way in which openWorkByURL can be called in the same thread or get an equivalent alternative method that can be called from javascript.

Error Messages

Not Applicable

Steps to Reproduce

Run an activity using openWorkByURL and compare the thread of new activity with original thread.

Root Cause

An issue in the custom application code or rules: Logic for bulk processing.
openWorkByURL has been changed to align with the current design requirements.

User is using ListView with customized logic which is not working in all the scenarios.


Here’s the explanation for the reported behavior:

For openWorkByURL scenario, use requestor level declared pages to share data across threads.

For Listview, recommendation is to use Report definitions. As customization is involved, use default Listviews which is working in Out-of-the-box (OOTB) scenarios.

Published March 28, 2018 - 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