Thank you for supporting the Cloud Customer Connect Community in 2024. It's a gift to work with you!

Look back
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.

ORC - Clarification on what triggers a change to Last Update Date

Summary:

As a pre-requisite of the Remove Person Information process, we are hoping to identify candidate data over X days old. This is to ensure that the client remains GDPR compliant.

We have found several variables within OTBI. One of these variables is 'Last Update Date'. We are looking for clarification on the events that would trigger an update to the 'Last Update Date' time stamp of a candidate.

The Taleo Implementation Guide is quite thorough and details a series of actions: Career Site Actions, Recruiting Centre Actions, CSP Actions, Candidate File Edits. Unfortunately, there is no similar information provided within the ORC Implementation Guide.

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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