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.
500 Internal server error
Steps to Reproduce
Consider two applications, Application A and Application B.
- Upgrade from Pega 7.2 to Pega 7.3.
- Create a portal for Application B.
- Run activity A to call the HTML stream containing the gadget code.
- Log in to Application A and switch to Application B. Run the portal for Application B.
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.