Thank you for supporting the Cloud Customer Connect Community in 2024. It's a gift to work with you!

Look back
You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register
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.

Local name field in Oracle Recruit

Summary:

We have a requirement to have the local and global names by the time a candidate is moved to HR. This is needed because we have a process to automatically create AD accounts and emails once a person is created in HR.

Our thought is that if we can have the names similar to how they show up in Core HR in Recruit we can have HR correct the global name and local names prior to moving the person to pending worker.

Content (required):

Is it possible to expose the local name field even if the person has not been created in Core HR?

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!