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.

Validating the Assignment DFF based on the Person type is erroring out in all the scenarios

Summary:

Unable to validate the Assignment DFF based on person type, which is erroring out in both positive and negative scenarios.

Content (required):

We are trying to make the the DFF (LOV) mandatory on Assignment page based on the Person Type (Ex: employee). When Person type is employee, the value in the DFF should not be Null. If it is null it should throw an error and once the value is selected it should allow user to the next region but we are getting the error in both the scenarios. (Attached the Rule screenshot we have created).

Rule type: Object Validation Rule Type

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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