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.

Using Custom Fields Instead of Regulation Fields for Self-ID

edited Mar 16, 2018 8:35PM in Taleo Enterprise 3 comments

Summary

Considering Creating Custom Fields for Self-ID instead of using the Regulation fields provided

Content

Is anyone currently using Custom Fields to collect Self-ID information such as Gender, Ethnicity, Race, and/or Veteran Status?  Our contract with the Federal Government recently ended, and we are working to implement the necessary changes.  As part of this, we are trying to determine the best way to collect Self-ID information post-offer.  Based on legal requirements, it seems that it would be easier for us to create custom fields and then use them to populate the data in Oracle HR.  If anyone is currently doing this, can you please tell us how it's working for you and any challenges you may

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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