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.

Does API User need to have Employee as Person Type?

We are seeing that with eQuest we need a Person in the system. We've placed them in the person type of 'Employee' but are wondering if we can instead use something like 'Non-Worker' so they don't pull into current employee reporting. How are you excluding API Users (persons) from reporting when the person type is Employee? Can a Non-Worker be used for the API User?

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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