User details are not returned when creating a new HR case and entering the first 3 characters of the employee's nameIssue As per the HR case creation configuration, the minimum input length defined is '3', but while creating the new HR case and entering employee details under "Search for Employee" with the 3 characters, the user details are not returned. For example, when searching with the keyword 'mal', the desired behavior is for the user 'Malika' to appear.CauseWith the current configuration, this is working as expected. The system property "glide.ts.max_wildcard_expansion" is set to 500 by default. This is the maximum number of matches for a wildcard term that are allowed as unambiguous; "mal" is being detected as a "common word". This can be confirmed in the following table: https://instance_name.service-now.com/ts_word_list.do Continuing our example, there would be more than 500 matches for the issue to occur. The user's information is not returned because it would exceed the value of 500, which is allowed as unambiguous. Profiles that show the desired behavior and return the employee's name, will have less than 500 matches.ResolutionTo achieve the desired behavior with scenarios like the one in the description, do one of the following: Increase the limit on the "glide.ts.max_wildcard_expansion" system propertyFilter more specifically (i.e. type more characters).