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.

Stakeholder is not set when the incident is created via REST Api

edited Feb 21, 2024 12:53PM in HCM REST APIs 3 comments

Summary:

The Profile Option ORA_HNS_ALLOW_ACCESS_BY_INCIDENT_REPORTER_AND_LOGGEDIN_USER is set to "Y" but the Reporter is not set as a Stakeholder when creating an incident via REST Api.


Content (please ensure you mask any confidential information):

Hi all,

We are trying to create an Health and Safety Incident using the create incidentKiosk REST Api as per the documentation: https://docs.oracle.com/en/cloud/saas/human-resources/23c/farws/op-incidentkiosks-post.html

The field "EmployeeId" is set with the ID of the Incident Reporter.

The creation is successful and from Standard UI the "Reporter" field of the incident is correctly set.

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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