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

Web Mashup gadget not redirected to corresponding access group



After upgrading to Pega 7.3, Web Mashup gadget does not redirect to the corresponding access group based on the application name.

Error Messages

500 Internal server error

Steps to Reproduce

Consider two applications, Application A and Application B.
  1. Upgrade from Pega 7.2 to Pega 7.3.
  2. Create a portal for Application B.
  3. Run activity A to call the HTML stream containing the gadget code.
  4. Log in to Application A and switch to Application B. Run the portal for Application B.

Root Cause

An issue in the custom application code or rules :

To run on a different application, data-pega-redirectguests ='false' was not set on the gadget DIV.

The data-pega-redirectguests was not specified. This caused the default application to run.


Perform the following local-change:

Set data-pega-redirectguests ='false' on the gadget DIV.

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