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.
How to restrict based on previous Backout status
Summary:
Hello All,
I'm currently working on restricting the custom BIP notification based on below scenario.
If an employee benefits is backed out and reprocessed again, the notification should not trigger to benefits team - which means the data should not be availble in the data set. But the issue is once the reprocessed is done the status is changing to STARTED again, so how to restrict based on previous VOIDD or BACKOUT status. In other words, if an employee has VOIDD or BACKOUT status in any of their history transaction, then the employee data should not be fetching even if their status changed to STARTED again.
Tagged:
0