Register today for Oracle CloudWorld. October 17th - 20th, Las Vegas

Register now

Hillel Cooperman, Senior VP of User Experience Design, has a message for you on Oracle CloudWorld

Watch now
Fluid - Decreasing number of openings doesn't automatically fill the requisition — Cloud Customer Connect
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

Fluid - Decreasing number of openings doesn't automatically fill the requisition

Received Response
40
Views
8
Comments
edited Dec 21, 2020 2:05AM in Taleo Enterprise 8 comments

Content

Hi All -

A user brought this to my attention and I was able to replicate in staging. In legacy recruiting, when a requisition's number of openings is brought down to the number that matches the number hired (i.e., requisition had 9 openings, hired 8 and decreased the number of openings on the requisition to 8), a message pops up saying "once this operation is completed, all openings available for this requisition will have been filled. The system will unpost the requisition. Do you want to save this requisition?"

However in fluid recruiting, a message pops up that the requisition will need to be re-submitted for approval in order to save the new number of openings. This is expected behavior in legacy if a user were decreasing the amount of openings that didn't match the number hired (i.e., requisition had 9 openings, hired 7, decreased number of openings on the requisition to 8). 

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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