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.

Why are working hours, salary and certain other fields not standard for the requisition?

edited Feb 5, 2021 5:30PM in Recruiting, Opportunity Marketplace 6 comments

Summary

Inability to add the OOTB fields for working hours, salary onto the requisition is

Content

We are struggling to understand why we are unable to add certain standard fields like working hours and salary into the requisition. With these fields being only available in offer, the user raising the offer would need to know these values to hand as we can not bring them in from the requisition. This is going to create extra time for each offer to find the values which is not going to work for our central team.

On our current ATS we collect these fields from the manager at the point they raise the requisition, then these will feed into the offer and therefore into the contract, which to us seems the most logical process.

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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