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.
For more information, please refer to this announcement explaining best practices for getting answers to questions.
Default Order of Multiple Work Relationships in Response
Summary:
Is there a default order to multiple work relationships provided in a response?
Content (please ensure you mask any confidential information):
Hello Experts,
We are in the midst of several process improvements , including migration to WORKERS REST API. In a couple of processes that currently use EMPLOYEE REST API, the developers were able to rely on a consistent and predictable order to the work relationship and assignment information in the response. I "P" workerType was listed first. With WORKERS, they are not seeing this same end result and it is causing confusion, particularly when pulling all work relationships for an employee.
Tagged:
0