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.
Is it ok to keep ACR enabled after redwood pages are enabled
Summary:
We currently have a few ACRs that default Job Requisition DFFs and 2 delivered Job Requisition fields based on position DFF values. The 25B Common What's New Document says "In 25B, defaulting and validation is not supported from Position and Assignment objects while creating or editing job requisition."
Other Oracle Documentation states that ACR's need to be disabled when transitioning to redwood.
Content (please ensure you mask any confidential information):
In our unit testing the existing ACR's are working as expected on the redwood Job Requisition page. Would it be ok to keep this enabled since the use case is not supported in VBS?
Tagged:
0