Get an incident

get

/hcmRestApi/resources/11.13.18.05/incidentKiosks/{IncidentId}

Request

Path Parameters
Query Parameters
  • This parameter specifies dependencies which are fields that are set before and rolled back after generating the response. Generally they are used to preview the effects of an attribute change. The fields specified in this parameter are always set in the resource instance in question. When a child resource collection is requested and the parameter is set, the fields will be set in the parent resource instance before generating the resource collection payload. The value of this query parameter is a set of dependency fields. Example: dependency=ProductId=2

    Format: <attr1>=<val1>,<attr2>=<value2>
  • When this parameter is provided, the specified children are included in the resource payload (instead of just a link). The value of this query parameter is "all" or "". More than one child can be specified using comma as a separator. Example: ?expand=Employees,Localizations. Nested children can also be provided following the format "Child.NestedChild" (Example: ?expand=Employees.Managers). If a nested child is provided (Example: Employees.Managers), the missing children will be processed implicitly. For example, "?expand=Employees.Managers" is the same as "?expand=Employees,Employees.Managers" (which will expand Employees and Managers).
  • This parameter filters the resource fields. Only the specified fields are returned, which means that if no fields are specified, no fields are returned (useful to get only the links). If an indirect child resource is provided (Example: Employees.Managers), the missing children will be processed implicitly. For example, "?fields=Employees.Managers:Empname" is the same as "?fields=;Employees:;Employees.Managers:Empname" (which will only return the "Empname" field for Managers). the value of this query parameter is a list of resource fields. The attribute can be a direct (Example: Employees) or indirect (Example: Employees.Managers) child. It cannot be combined with expand query parameter. If both are provided, only fields will be considered.

    Format: ?fields=Attribute1,Attribute2

    Format for fields in child resource: ?fields=Accessor1:Attribute1,Attribute2
  • This parameter can be used to show only certain links while accessing a singular resource or a resource collection. The parameter value format is a comma-separated list of : <link_relation>

    Example:
    self,canonical
  • The resource item payload will be filtered in order to contain only data (no links section, for example).
Header Parameters
  • If the REST API supports runtime customizations, the shape of the service may change during runtime. The REST client may isolate itself from these changes or choose to interact with the latest version of the API by specifying this header. For example: Metadata-Context:sandbox="TrackEmployeeFeature".
  • The protocol version between a REST client and service. If the client does not specify this header in the request the server will pick a default version for the API.

There's no request body for this operation.

Back to Top

Response

Supported Media Types

Default Response

The following table describes the default response for this task.
Headers
  • If the REST API supports runtime customizations, the shape of the service may change during runtime. The REST client may isolate itself from these changes or choose to interact with the latest version of the API by specifying this header. For example: Metadata-Context:sandbox="TrackEmployeeFeature".
  • The protocol version between a REST client and service. If the client does not specify this header in the request the server will pick a default version for the API.
Body ()
Root Schema : incidentKiosks-item-response
Type: object
Show Source
  • Title: Employee
    Employee ID of the person who reported the incident. If the reporter is Non Employee, Employee ID should be null. This attribute is required if the reporter is an employee. Valid values are defined in the list PersonLovPVO.
  • HnsIncidentsDFF
  • Title: Date and Time
    Date the incident occurred captured by the incident reporter. This attribute is required.
  • Title: Description
    Complete description of the incident captured by the incident reporter.
  • Incident Detail Kiosks
    Title: Incident Detail Kiosks
    The incidentDetailKiosk is a child resource of incidentKiosks. It provides information about incident events. This resource allows a simple GET and POST operation on incidents events.
  • Title: Incident ID
    Unique identifier of the incident. System-generated primary key.
  • Title: Immediate Actions
    Description of any immediate actions undertaken after the incident was captured by the incident reporter.
  • Date and time when the notified person was informed about the incident.
  • Title: Incident Source
    Maximum Length: 30
    Unique identifier for the incident source. Valid values are defined in the list HcmCommonSharedAM_HnsIncidentSource. This attribute is required.
  • Title: Summary
    Maximum Length: 1000
    Summary information of the incident captured by the reporter. This attribute is required.
  • Title: Incident Type
    Maximum Length: 30
    Unique identifier for the incident type. Valid values are defined in the list HcmCommonSharedAM_HnsIncidentType. The default value is Health and Safety Incident.
  • Links
  • Title: Location ID
    Onsite location where the incident happened. If the incident happened offsite, the Location ID should be null. This attribute is required if the location is ORA_ONSITE. Valid values are defined in the list LocationLovPVO.
  • Title: Location Type
    Maximum Length: 30
    Default Value: ORA_ON_SITE
    Type of location where the incident occurred, captured by the reporter such as ORA_ONSITE or ORA_OFFSITE. Valid values are defined in the list HcmCommonSharedAM_HnsLocation. This attribute is required.
  • Employee ID of the person who is notified about the incident. This attribute is required if the notified person is an employee. Valid values are defined in the list PersonLovPVO.
  • Title: Incident Reporter
    Maximum Length: 30
    Default Value: ORA_EMPLOYEE
    Selection made by the incident reporter to categorize the incident reporter as either an employee or a non-employee. Valid values are defined in the list HcmCommonSharedAM_HnsPerson. This attribute is required.
  • Title: Address Line 1
    Maximum Length: 255
    Address line 1 of the incident captured by the reporter. If the incident happened onsite, then the value should be null. This attribute is required if the location is ORA_OFFSITE.
  • Title: Address Line 2
    Maximum Length: 255
    Address line 2 of the incident captured by the reporter. If the incident happened onsite, then the value should be null.
  • Title: Area Code
    Maximum Length: 30
    Area code for the reporter's phone. If the reporter is an employee, then the value should be null.
  • Title: City
    Maximum Length: 100
    City where the incident was captured by the reporter. If the incident happened onsite, then the value should be null. This attribute is required if the location is ORA_OFFSITE.
  • Title: Country
    Maximum Length: 100
    Country where the incident occurred, captured by the incident reporter. If the incident happened onsite, then the value should be null. This attribute is required if the Location is ORA_OFFSITE.
  • Title: Country Code
    Maximum Length: 30
    Country code for the reporter's phone. Valid values are defined in the list PhoneCountryCodePVO. If the reporter is an employee, then the value should be null. PhoneCountryCodePVO.
  • Title: Email
    Maximum Length: 250
    Email ID of the person who reported the incident. If the reporter is an employee, then the value should be null. Either ReptrPhoneNo or ReptrEmail is required if the reporter is a non employee.
  • Title: Name
    Maximum Length: 200
    Full name of the person who reported the incident. If the reporter is an employee, then the value should be null. This attribute is required if the reporter is a non employee.
  • Title: Phone
    Maximum Length: 18
    Phone number of the person who reported the incident. If the reporter is an employee, then the value should be null. Either ReptrPhoneNo or ReptrEmail is required if the reporter is a non employee.
  • Title: Specific Location
    Maximum Length: 255
    Detailed information on the location of the incident captured by the reporter. This attribute is required.
  • Title: State
    Maximum Length: 100
    State where the incident was captured by the reporter. If the incident happened onsite, then the value should be null. This attribute is required if the location is ORA_OFFSITE.
  • Title: Postal Code
    Maximum Length: 100
    Postal code of the incident captured by the reporter. If the incident happened onsite, then the value should be null.
  • Maximum Length: 30
    Default Value: ORA_NO_EFFECT
    Severity level of the incident.
  • Title: Target Completion Date
    Date and time by when the incident needs to be completed. Prepopulated using the Target Date setup value.
Nested Schema : HnsIncidentsDFF
Type: array
Show Source
Nested Schema : Incident Detail Kiosks
Type: array
Title: Incident Detail Kiosks
The incidentDetailKiosk is a child resource of incidentKiosks. It provides information about incident events. This resource allows a simple GET and POST operation on incidents events.
Show Source
Nested Schema : incidentKiosks-HnsIncidentsDFF-item-response
Type: object
Show Source
Nested Schema : incidentKiosks-IncidentDetailKiosk-item-response
Type: object
Show Source
Back to Top

Examples

The following example shows how to retrieve a health and safety incident by submitting a GET request on the REST resource using cURL.

curl -i -u "<username>:<password>" -H "Content-Type: application/vnd.oracle.adf.resourceitem+json" -X GET  https://<host>:<port>/hcmCoreApi/resources/11.13.18.05/incidentKiosks/{incidentID}

Example of Response Header

The following is an example of the response header.

HTTP/1.1 200 OK
Content-Type : application/vnd.oracle.adf.resourceitem+json

Example of Response Body

The following example shows the contents of the response body in JSON format.

{
    "EmployeeId": 300100172372584,
    "IncidentDate": "2018-11-01T11:06:06.352+00:00",
    "IncidentId": 300100172522925,
    "IncidentSummary": "UPG EADI 1901 Adding Results",
    "LocationTypeCode": "ORA_ON_SITE",
    "ReporterTypeCode": "ORA_EMPLOYEE",
    "ReptrCity": null,
    "ReptrCountry": null,
    "ReptrEmail": null,
    "ReptrAddrLine1": null,
    "ReptrName": null,
    "ReptrPhoneNo": null,
    "ReptrSpecificLocation": "UPG EADI 1901 Adding Results",
    "TargetCompletionDate": "2018-12-31T11:06:06.346+00:00",
    "ReptrAddrLine2": null,
    "ReptrZipCode": null,
    "ReptrState": null,
    "LocationId": 3030,
    "ReptrCountryCodeNum": null,
    "ReptrAreaCode": null,
    "IncidentSourceCode": "ORA_INTERNAL",
    "links": [
        {
          ...}
   ]
}
Back to Top