3591495 - The filter function in the Latest Applicant Workbench is not functioning as intended.

Symptom

The filter function in the Latest Applicant Workbench is not operating as expected. The displayed results do not accurately align with the specified search criteria, leading to inconsistencies in the filtering process. Instead of refining the applicant list based on the selected parameters, the filter returns results that do not match the intended search criteria.

Consider a job requisition with two candidates:

One candidate has the email abc@gmail.com
Another candidate has the email def@gmail.com

Scenario 1: Filtering by the keyword "abc"

The filter correctly returns only abc@gmail.com since it is the only email containing the substring "abc."

Scenario 2: Filtering by the keyword "abc@gmail.com"

The filter unexpectedly returns both abc@gmail.com and def@gmail.com, even though "abc@gmail.com" was specified as the exact search term.

Environment

SAP SuccessFactors Recruiting Management

Reproducing the Issue

1. Login
2. Configure Latest Applicant Workbench filter to use email for filtering candidates.
3. Goto "Recruiting"
4. Click on any job requisition
5. Goto Candidates tab
6. Try filtering candidates with different keywords

Cause

The search is not an exact search for the emails. The system is using the search term and showing the emails that are similar or have

Resolution

This is an expected behavior. This suggests that the filter is matching email addresses based on common substrings, such as "@gmail.com," rather than performing an exact match.

For Scenario 1, where a user searches for "abc," the system will return only candidate with email abc@gmail.com because it is the only email that contains the exact substring "abc."

For Scenario 2, where a user searches for "abc@gmail.com" the system will display both candidates with email abc@gmail.com and def@gmail.com, as both email addresses share the common substring "@gmail.com."

This confirms that the search behavior is designed to retrieve results based on partial matches rather than performing a strict exact search. Given this, the observed behavior is expected and aligns with the intended functionality of the system.