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.

Applying leave from third party application which calls cloud HCM REST API to create leave

Applying leave from third party application which calls cloud HCM REST API to create leave


Content (please ensure you mask any confidential information):

The client is using a self-service employee portal application for the employee’s regular tasks like applying leave, viewing pay slips etc.

Oracle HCM Cloud is the primary application for all the employee data which is the data source.

Use case:

From the employee portal application, the employee is raising a leave request. That leave request is created using REST API in HCM Cloud. But the leave created by name is integration user which is used while calling REST API. But the customer is expecting that leave should be created in the HCM Cloud with logged user in the employee portal. That means user should be authenticated between Employee portal and Oracle automatically and the REST API should be calling using the logged in user credentials via employee portal dynamically. The customer is using Microsoft AD to login Employee portal application.

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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