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.

What is the difference between "unposting" and "Suspending" a requisition?

in Recruiting, Opportunity Marketplace 2 comments

Summary:

Recruiters are looking for a way to (temporarily) stop getting applications for certain jobs that attract a lot of applicants. Do you typically unpost reqs (Posting - Edit - Posting Schedule - Do Not Post) or do you Suspend the req ( Actions - Suspend Job Requisition)? And why? What are the downstream ramifications of one option versus the other?

Content (required):

At the moment, we are not utilizing the automatic unpost option (we are considering it), so this question refers specifically to the recruiter changing the requisition status.

Currently, recruiters are unposting requisitions -- which works to temporarily stem the tide -- but given that the Oracle documentation references Suspending requisitions (

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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