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.

Making requisition fields read only via Page Composer

in Recruiting, Opportunity Marketplace 3 comments

Summary:

Customer uses position management and hiring managers can only create requisitions using a position (all other forms of requisition creation are not available). When the HM creates a requisition, the fields pre-populated by said position are for the most part editable, therefore, can be updated. This means that the integrity of the position (not in the position itself but from an overall position perspective) is changed and therefore, no longer the position that was signed off pre-recruitment.

The only way I have found to manage this requirement is to use Page Composer to make the position fields read only. I wanted to get confirmation on whether this is a protected config aspect when there are quarterly updates made. If they are not protected, this would require a high level of maintenance each quarter. If there are any other alternatives to using page composer, I am all ears!

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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