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.
Autocomplete: Unable to nullify Assignment DFFs for certain Assignment Actions & Transaction State
Summary:
We need to nullify 4 flex fields at assignment level when creating Change Assignment transactions with action as ‘Transfer’ and ‘Leave’.
These fields should only be nullified upon initiating the transaction by the manager. Later the manager fills in the data in the 4 flex fields before submitting the transaction. This transaction now goes for approval to a group in HR Services.
However if HR Services are trying to ‘Edit’ the transaction from the approval notification, the fields are getting nullified again (losing the data that was filled in by the manager), even though it is configured in the autocomplete rule that transaction state should not be any of the following:
Tagged:
0