You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register
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.

Can Offboarding Checklists be restricted based on employee's current location?

edited Sep 12, 2024 4:20AM in Journeys 1 comment

Hello,

We have identified an odd behaviour where an employee's Location A was end dated back in January 1st, 2024.

Thereafter, a new Location B was Assigned to them on January 2nd, 2024.

While the employee resigned from Location B, which was his current location, an offboarding checklist comes into picture where there are multiple tasks that needs to be completed as an Exit formality. Now this Offboarding checklist task was not only assigned to this exited employee's current Location B's Admin but it also got triggered to his previous Location A's Admin which was end-dated.

As per business, the task should have only been triggered to Location B which is the employee's current location. Is there a solution to this?

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!