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
Learn about the new Oracle AI Agent Studio for Fusion Applications: Watch Now

Progress with Redwood: Redwood Resources for Oracle Cloud HCM -  Go Here
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.

Impact of deactivating a candidate selection process (CSP) used in existing job requisitions

edited Aug 11, 2022 4:41AM in Recruiting, Opportunity Marketplace 4 comments

Summary:

We have a requirement to add additional state to a phase in an existing CSP. The only way to achieve the same is to create a new CSP. But we no longer need the old one and want to deactivate the same.

As per Doc ID 1045749.1, there won't be any impact on existing requisitions and candidate can be progressed without any issues.

Provided that there is no provision to update the CSP within the job requisition, we would like to know about such experiences in other implementations

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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