Skip to main content

Cannot load a mashup from a non-default access group

Suggest edit
Updated on November 15, 2021

Ensure that you can successfully load a mashup from an access group that is not the default access group for an application.

Condition

In Pega Platform 8.2.x and earlier, the mashup does not load on the web page when the mashup is loaded from an access group that is not the default access group for the application.

Cause

By default, a case or harness can be loaded in a mashup from the operator’s default access group for a given application. In Pega Platform 8.3 and later releases, mashup URLs are qualified by the application name, which indicates which engine runs the mashup in a given application context. In releases earlier than 8.3, priority is given to the access group hash in the URL, instead of the application name.

Solution

  • For mashups generated before release 8.3, if you want to load a case or harness in a mashup from a non-default access group for an application, set the attribute data-pega-redirect-guests to false. Then, add the attribute to other attributes in the mashup code.

  • Previous topic Cannot load a mashup asynchronously based on an event or a flag
  • Next topic Cannot embed a mashup in a Pega application
Did you find this content helpful? YesNo

0% found this useful

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us