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.

Mandatory Phases and States in Candidate Selection Process

edited Jul 8, 2021 8:41AM in Recruiting, Opportunity Marketplace 10 comments

Summary

How to make Phases and States mandatory in Candidate Selection Process?

Content

Hi

Is there a way to make a State mandatory in Candidate Selection Process, so that users cannot skip that state before they are allowed to move the status of a candidate to the next states or phase? 

Similarly, is there a way to make a Phase mandatory.

I tried to make a phase (Screening) mandatory by using the delivered configuration field in the task Candidate Selection Process Configuration. But while testing, the Recruiter could move a candidate from the 'New' phase , directly to 'Interview and Selection' phase, skipping the mandatory 'Screening' phase in between.  So, wondering, if I need to remove any privileges for the Recruiter role?  Or are there other ways of achieving the goal of making a Phase and/or State within that Phase mandatory for a user to update?

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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