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.

Autoprovision Areas of Responsibility

edited Dec 23, 2024 2:41PM in Human Capital Management 1 comment

Summary:

Currently in Responsive UI we have hundreds of Location Support colleagues that already have AOR assigned. As I'm building and testing the AOR templates in Redwood, I noticed that the autoprovision process is adding an additional AOR to the colleagues that currently already have AOR assigned. Why does the process not skip these colleagues? Does it not recognize that they already have AOR that was assigned in Responsive UI? If not, then how will this affect the colleague's access? Does their access now start over with the new From Date??

For example: A Location Support colleague has already had AOR assigned for their location since 2023 when the autoprovision process runs, it assigns a new AOR. So now there are TWO active lines of AOR present - the original AOR from 2023 and now the one assigned in 2024. Which effective date is being used for the AOR?

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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