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: AI Resources for Oracle Cloud HCM – Go Here

Progress with Redwood: Redwood Resources for Oracle Cloud HCM -  Go Here

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!