Learn about the new Oracle AI Agent Studio for Fusion Applications: Watch Now
Progress with Redwood: Redwood Resources for Oracle Cloud HCM - Go Here
Progress with Redwood: Redwood Resources for Oracle Cloud HCM - Go Here
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.
Advice on using Last Working Date
Summary:
The Last Working Date is just a date field, therefore does not take into account the terminated person's timezone. What are some best practices for utilising it?
Content (required):
Combined with a field for time we are looking to utilise it to automate the date and time that system access should be revoked. It gets input when someone either resigns or is terminated.
The problem we face is that this date is not contextual to whoever is viewing or inputting the data.
Take this as an example:
- A person's last day is 1st January at 2am GMT. Their line manager in the same timezone inputs exactly that to the date local to them.
Tagged:
0