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.

Confidential Requisitions

in Recruiting, Opportunity Marketplace 6 comments

Summary: How to restrict LOV's in Recruiting Type while creating Requisitions.


Content (required): We have a requirement that some of the Recruiters should only be able to create/view/edit the Confidential Requisitions.

As per some of the previous posts on this topic, we did the following steps.

Create a Recruiting Type called Confidential in ORA_IRC_RECRUITING_TYPE lookup.

Create Job Requisition Security Profile, Secure by Recruiting Type and use it on your Recruiting Data Roles.

Create Recruiting AORs with Recruiting Type as Scope and assign the Relevant AORs to your Recruiters.

Unfortunately, when a Recruiter creates a new requisition, the Recruiting type value shows all LOV's like Professional, Executive, Confidential etc.. The Recruiter is able to select any of these Recruiting type and being the owner of these requisitions, they are able to view all requisitions created by them for any recruiting type.

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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