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

Autocomplete fails when parameter values contain special chars



Autocomplete (sourced from a report definition) fails when Report Definition parameter values, from a separate control (drop down), contain special characters (such as, apostrophe).

Error Messages

Not Applicable

Steps to Reproduce

In a search window, add autocomplete sourced from a report definition:

The report definition takes filter parameters:

Set the values for the filter parameters in a separate dropdown:

Select a value from the dropdown that contains a special character, like an apostrophe.

Bring up the search window containing the autocomplete.

The autocomplete does not respond.

Root Cause

A defect in Pegasystems’ code or rules. The autocomplete parameters must be sent in POST data instead of Request URL. This is required when a third-party plug-in is used, to protect the web application from cross-site scripting (XSS) attacks by rejecting URLs containing some special characters.


Apply HFix-36984

Suggest Edit

Published September 21, 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