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
Learn about the new Oracle AI Agent Studio for Fusion Applications: Watch Now

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.

Create api user account

edited Jan 8, 2020 12:29PM in Recruiting, Opportunity Marketplace 3 comments

Summary

What is the best practice to create api user accounts?

Content

Hi,

I worked on eQuest integration in test environment and I hired an employee to create the api user account in order to complete the integration. Then I have also worked on Background Check integration and also in that case I hired an employee to create another api user account. Now I have to perform the integrations on a production environment and I'm asking if it is correct to hire every time fake employees in order to complete the integration associating them to real positions, departments etc.

Could you please clarify if this is the right way to proceed and in which way the api user accounts affect the organization for example in terms of reporting? Is there a best practice on this? Can I give a person ID to the api user accounts if I don't hire them?

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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