Preferred work location is not saving
Summary
When creating a candidate, the preferred work location does not saveContent
We use User Groups based on location (country) to determine what candidates recruiters have access to. This is primarily to comply with privacy laws. Since moving to Fluid we have noticed that a lot of candidates are being created without the preferred work location, which is the field that is referenced in user groups. Upon researching, we have learned that when recruiters create a candidate profile, the preferred work location is entered at the time of creation but it is not being saved. As a result, these candidates appear in all searches, regardless of the recruiter's home country. Oracle has created