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.

Contacts : Self Service

edited Jan 31, 2020 6:30PM in Human Capital Management 1 comment

Summary

Guidance to Employees for Contacts

Content

As we are in the process of implementation, we are struggling with how employees will understand the concept of "Contacts can be an emergency contact, or a beneficiary, or a dependent".  Looking for guidance from existing users on creative ways that you have used, or are we concerned about something that won't really be an issue?

An example we keep going back to from an employee perspective:  If I'm adding an emergency contact, why do you need their date of birth/NID?  

Any thoughts appreciated!

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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