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

Mashup: Custom parameters sent in lower case

SA-43114

Summary



Mashup issue with custom parameter names defined as DIV attributes using syntax like PegaA_<ParamName> results in a URL generated with paramname=<value>.

The parameters are passed in lower case when user uses Internet Explorer running in Edge mode.

The custom Mashup parameters are passed with mixed case when using older Quirks mode.

Parameter names within PRPC activity processing and so on are case sensitive.


Error Messages


None, parameters are simply sent in lower case instead of mixed case.


Steps to Reproduce



Mashup using custom parameters defined as PegaA_<ParamName> using mixed case.


Root Cause



To process custom parameters defined as DIV attributes user is simply looping through the DIV attribute array.

When using Internet Explorer in Edge mode the HTML standards have changed and DIV attribute names are normalized to lower case.

When building the URL for the Mashup iFrame the parameter names added are in lower case because that is how the browser is providing the names to us. One can remove the "PegaA_".

The same is true for Chrome, Firefox, Safari browsers.

Resolution



Here's the explanation for the behavior:

Do not use PegaA_<ParamName>. Instead put parameters inside PegaA_Params or for later releases of PRPC "data-pega-action-param-parameters". This will maintain the mixed case of parameter names when generating the URL for the Mashup iFrame.

Suggest Edit

Published December 15, 2017 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

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

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