Get Started with Redwood for Oracle Cloud HCM Begin Now
To ensure that questions get required attention from community members and are NOT left unanswered, it’s important for the author to indicate (by selecting “Yes” or “No” when prompted) whether the question was answered. (newly added) Please note that it is also important to respond to EACH comment your question receives. Your Yes or No response ensures an accurate status for your question.
For more information, please refer to this announcement explaining best practices for getting answers to questions.
For more information, please refer to this announcement explaining best practices for getting answers to questions.
Best Practice for Avoiding Duplicate Candidate Records
Summary
We are looking for best practices or ways other TBE users are avoiding the creation of duplicate candidate records.Content
Because TBE's primary key is a candidate's email address, our candidates end up with multiple records. After submitting a ticket we learned this is the intended functionality and we would need to load an enhancement request if wanted to have a new key field added. Other than adding more verbiage to our careers page to help candidates and then merging records once duplicates are created we are looking for best practices or ways other TBE users are avoiding duplicate records. Any and all ideas would be greatly appreciated.
Tagged:
0