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.

Need Guidance on Implementing Seniority Date Validation

Dear Team,

We’re currently working on a business-critical requirement and need your expert guidance. Below is the summary of the scenario and the corrections needed:

  1. Seniority date exceeding the hire date:

Issue: In some records, the seniority date is later than the hire date.
Required Correction: The seniority date must always be less than or equal to the hire date.

2. Blank seniority date:


Issue: In certain cases, the seniority date field is left blank.
Required Correction: The seniority date field should be mandatory and must not be left blank.


We’d like to know if there’s a feasible way to implement validations for these scenarios in the Test Environment before rolling them out to production.

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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