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.
Recruiting Interaction Type - why are there 4 standard interactions type that we can't use?
Summary:
As per this documentation : https://docs.oracle.com/en/cloud/saas/talent-management/22d/faimh/recruiting-setup-and-maintenance-tasks.html#s20063037
Considering the following lookup codes : ORA_LIRSC_NOTES / ORA_LIRSC_INMAIL / ORA_EMAIL / ORA_SMS
It is specified not to use this lookup codes : why not simply remove them ? Is there any hidden purpose ?
This is pretty misleading, and a waste of time when implementing.
Content (required):
Setup and maintenance -> Setup: Recruiting and Candidate experience -> Recruiting and Candidate Experience -> Configure Recruiting Interaction Categories
Version (include the version you are using, if applicable):
22C
Tagged:
0