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

Connect-HTTP request query parameters overriden



When used Connect-Http rule, if used same parameter name more than once in Request query parameters, the pyRequestQueryParams only getting the parameter which added lastly.

In Connect-Http rule When set same parameter name more than once, only getting the parameter which added lastly.

But in this case, there is requirement to allow same parameter multiple times in the request.

To achieve this customer modified below activities in his local, after changes done above scenario is working fine. If anytime upgrade happens then conflict may arises so requesting these changes needs to be developed as part of release.

InvokeHTTPConnector (Rule-Connector-Http) - 3rd step java code
Invoke (Rule-Connector-Http)- 5th step java code

Error Messages

Not applicable.

Steps to Reproduce

1) Create a Connect-Http rule and set parameters.
2) Create Activity and set values for parameter which used in Connect-HTTP rule and call Connect-HTTP method.

Root Cause

Existing behaviour of PRPC will not allow with duplicate query parameters in the request URL and it is not a bug from PRPC end. So it will be consider as enhancement to the product.


Pega has raised enhancement request for achieving the changes what user has done in the environment.

Enhancement ID: FDBK-15152

Published May 21, 2016 - 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