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.
End dating the recruiting types
Summary:
We have a requirement where we need to remove some of the existing recruiting types that has already been used for certain requisitions . From the manage common lookups , have tried both the options of disabling those recruiting types and end dating them . By doing this , for new requisitions those values are not showing which is as expected . But the recruiting type is now showing blank for those filled and active requisitions which had used this recruiting type previously. Please advise if anyone had worked on this kind of requirement before and what was the best practice followed.
Content (please ensure you mask any confidential information):
Tagged:
0