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 with extended "i" characters in Turkish



Turkish User has inconsistent behavior with Autocomplete lookup on the extended "i" characters in Turkish.

In Turkish Alphabets, the combination of Capital Letter and Small Letter changes -- Turkish Alphabet having 4 I's---2 Latin I (that is.,LATIN CAPITAL I WITHOUT DOT [ I ], LATIN SMALL i WITH DOT [ i ]) and two Additional Turkish I's (that is, TURKISH CAPITAL I WITH DOT [ İ ] , TURKISH SMALL I WITHOUT DOT [ ı ]).

And the combination of Capital-Small letter is I,ı(that is, LATIN CAPITAL I WITHOUT DOT [ I ],  TURKISH SMALL I WITHOUT DOT [ ı ]) and İ,i(that is, TURKISH CAPITAL I WITH DOT [ İ ], LATIN SMALL i WITH DOT [ i ])

Error Messages

Not applicable

Steps to Reproduce

  1. Include Autocomplete populating from declare page list. The declare page populates from a Rule Obj-Browse in an activity. 
  2. Include Autocomplete can also be populated from property local list, but their is no change in behavior. User is using Turkish locale.

Root Cause

Currently this is the limitation for the autocomplete as the highlighting of the results are happening on the basis of regular expression and it is not specific to the locale. So need to make changes to highlight based on lowercase conversion and traversing the original string to look for matches.



Apply HFix-30399 to resolve the concern. Also follow the below changes along with the hotfix :
  • Turkish Locale(tr_TR) must need to be set to Locale.
  • As the Hotfix includes Rule-Utility-Function(RUF) change, so after installing the Hotfix need to regenerate the functions and re-save the section is must required. 
Suggest Edit

Published December 26, 2016 - 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