Learn about the new Oracle AI Agent Studio for Fusion Applications: Watch Now
Progress with Redwood: Redwood Resources for Oracle Cloud HCM - Go Here
Progress with Redwood: Redwood Resources for Oracle Cloud HCM - Go Here
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.
For more information, please refer to this announcement explaining best practices for getting answers to questions.
Redwood Seniority dates page shows different behavior for Bargaining Unit field
Summary:
when we logged with custom HR Role user for seniority date RUI Page(dev2) and select any employee who is having more than one bargaining unit, then in RUI it shows the latest bargaining unit value as default in the field but when we logged with the same custom HR role user and opens redwood seniority page(in dev5) for the same employee who is having more than one bargaining unit, then in redwood it shows the value populated as per the alphabetical order not the latest one. Even though in both UI we have dropdown to select the LOV is not
Tagged:
0