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.

Required for Saving VS Required for Approval

edited Apr 29, 2020 9:30PM in Taleo Enterprise 3 comments

Summary

Change setting from "Required for Saving" to "Required for Approval" but it doesn't work.

Content

We have a User-defined Field that was set up as "Required for Saving". Recently we made the change to have it "Required for Approval". As a result, in the Diagnostic panel, it moved from the "Fields to Create" to "Fields to Request Approval", which is correct. However, when we create a requisition and save it with no value for this field, we can't. The error message says that this field mus be filled before the requisition can be saved. See below picture.

I'm wondering if anyone encountered the same issue before or help me figure out the reason.

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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