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.
Worker Assignment Rule gets triggered early in When&Why section of AddPendingWorker flow
Summary:
We have a rule that triggers an error message when step is null in most of our transactions including AddPendingWorker flow. Rule is applied in worker assignment business object but triggers in When&Why section of AddPendingWorker flow. It is expected to only be triggered in the assignment section upon clicking continue.
Steps to replicate:
Pending Workers -> Select any pending worker -> Edit Pending Worker -> Change the effective date in the when&why section -> click continue (Rule is triggered which should not be)
Note that when the effective date is not changed, the issue is not encountered. This is encountered during regression testing for 23D.
Tagged:
0