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

Benefit Set autocomplete search is case sensitive



Auto-complete is case sensitive when selecting Benefit Set in Product Template screen.

Error Messages

Not Applicable

Steps to Reproduce

1. Log in to Product Composer System (PCS) with appropriate credentials.
2. Select Create Product Template from the menu.
3. In the Benefit Set autocomplete fields, search for a benefit set by changing the case of the search characters.

Root Cause

It is an expected behavior.


Here’s the explanation for the reported behavior:
The benefit sets are very limited when compared to other entities like benefit, and so on. An expert search has to be performed rather than a simple search in autocomplete. This is the reason for the case sensitivity of benefit set autocomplete.
To remove the case sensitivity, remove the filter titled “G” from ListOfBenefitSets report definition, and save the rule in a custom implementation ruleset. As an alternative, keep that G filter, but open the gear icon and select Ignore case as shown below. This will return all the benefit sets irrespective of the casing.

Suggest Edit

Published March 3, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

100% found this useful

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