Create
post
/fscmRestApi/resources/11.13.18.05/shifts
Request
Header Parameters
-
Metadata-Context: string
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".
-
REST-Framework-Version: string
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.
-
Upsert-Mode: string
Contains one of the following values: true or false. If true, the server performs an Upsert operation instead of a Create operation. During an Upsert operation, the server attempts to find an existing resource that matches the payload. If a match is found, the server updates the existing resource instead of creating a new one. If not found or false (default), the server performs a Create operation. Note that the Upsert operation isn't supported for date-effective REST resources.
Supported Media Types
- application/json
Root Schema : schema
Type:
Show Source
object-
CategoryCode: string
Title:
CategoryMaximum Length:30 -
Code: string
Title:
CodeMaximum Length:3 -
Description: string
Title:
DescriptionMaximum Length:2000 -
Duration: number
-
DurationUnit(required): string
Title:
Duration UnitMaximum Length:30 -
HCMScheduleShiftId: integer
(int64)
-
Name(required): string
Title:
NameMaximum Length:240 -
PeriodTypeCode: string
Title:
Period TypeMaximum Length:30 -
shiftDetails: array
shiftDetails
-
ShiftDetailTypeCode: string
Title:
Shift Detail TypeMaximum Length:30 -
ShiftTypeCode(required): string
Title:
TypeMaximum Length:30 -
StartTime: string
Maximum Length:
255
Nested Schema : schema
Type:
Show Source
object-
CoreWorkFlag: boolean
Title:
Core WorkMaximum Length:1Default Value:false -
Day: integer
-
Duration: number
-
DurationUnit: string
Title:
Duration UnitMaximum Length:30 -
MaximumBreakMinutes: integer
-
MinimumBreakMinutes: integer
-
Name: string
Title:
NameMaximum Length:30 -
StartTime: string
Response
Supported Media Types
- application/json
Default Response
The following table describes the default response for this task.
Headers
-
Metadata-Context:
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".
-
REST-Framework-Version:
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.
Root Schema : shifts-item-response
Type:
Show Source
object-
CategoryCode: string
Title:
CategoryMaximum Length:30 -
Code: string
Title:
CodeMaximum Length:3 -
CreatedBy: string
Title:
Created ByRead Only:trueMaximum Length:64 -
CreationDate: string
(date-time)
Title:
Creation DateRead Only:true -
Description: string
Title:
DescriptionMaximum Length:2000 -
Duration: number
-
DurationUnit: string
Title:
Duration UnitMaximum Length:30 -
EndTime: string
Read Only:
trueMaximum Length:255 -
HCMScheduleShiftCode: string
Read Only:
trueMaximum Length:255 -
HCMScheduleShiftId: integer
(int64)
-
HCMScheduleShiftName: string
Read Only:
trueMaximum Length:255 -
LastUpdateDate: string
(date-time)
Title:
Last Updated DateRead Only:true -
LastUpdatedBy: string
Title:
Last Updated ByRead Only:trueMaximum Length:64 -
links: array
Links
Title:
LinksThe link relations associated with the resource instance. -
Name: string
Title:
NameMaximum Length:240 -
PeriodTypeCode: string
Title:
Period TypeMaximum Length:30 -
shiftDetails: array
shiftDetails
-
ShiftDetailTypeCode: string
Title:
Shift Detail TypeMaximum Length:30 -
ShiftId: integer
(int64)
Read Only:
true -
ShiftTypeCode: string
Title:
TypeMaximum Length:30 -
StartTime: string
Maximum Length:
255
Nested Schema : Links
Type:
arrayTitle:
LinksThe link relations associated with the resource instance.
Show Source
Nested Schema : link
Type:
Show Source
object-
href: string
Title:
hyperlink referenceThe URI to the related resource. -
kind: string
Title:
kindAllowed Values:[ "collection", "item", "describe", "other" ]The kind of the related resource. -
name: string
Title:
nameThe name of the link to the related resource. -
properties: object
properties
-
rel: string
Title:
relationAllowed Values:[ "self", "lov", "parent", "canonical", "child", "enclosure", "action", "custom" ]The name of the relation to the resource instance. Example: self.
Nested Schema : properties
Type:
Show Source
object-
changeIndicator: string
Change indicator or the ETag value of the resource instance.
Nested Schema : shifts-shiftDetails-item-response
Type:
Show Source
object-
CoreWorkFlag: boolean
Title:
Core WorkMaximum Length:1Default Value:false -
CreatedBy: string
Title:
Created ByRead Only:trueMaximum Length:64 -
CreationDate: string
(date-time)
Title:
Creation DateRead Only:true -
Day: integer
-
Duration: number
-
DurationUnit: string
Title:
Duration UnitMaximum Length:30 -
LastUpdateDate: string
(date-time)
Title:
Last Updated DateRead Only:true -
LastUpdatedBy: string
Title:
Last Updated ByRead Only:trueMaximum Length:64 -
links: array
Links
Title:
LinksThe link relations associated with the resource instance. -
MaximumBreakMinutes: integer
-
MinimumBreakMinutes: integer
-
Name: string
Title:
NameMaximum Length:30 -
ShiftDetailsId: integer
(int64)
Read Only:
true -
StartTime: string
Nested Schema : Links
Type:
arrayTitle:
LinksThe link relations associated with the resource instance.
Show Source
Links
- shiftDetails
-
Parameters:
- ShiftId:
$request.path.ShiftId
- ShiftId:
Examples
This example describes how to create shifts.
Example cURL Command
Use the following cURL command to submit a request on the REST resource.
curl -u username:password -X POST -H "Content-Type:application/vnd.oracle.adf.resourceitem+json" -d 'request payload' "https://servername/fscmRestApi/resources/version/shifts"
Example Request Body
The following example includes the contents of the request body in JSON format. You replace the request payload in the cURL command with the contents of the Example Request Body. The request payload specifies attribute values that the command will use in the record that it creates.
{
"Name" : "SHIFT-Example",
"Description" : "Shift Example of Post",
"Code" : "",
"StartTime" : "09:00 AM",
"Duration" : 8,
"DurationUnit" : "HOURS",
"CategoryCode" : "WORK_FROM_OFFICE",
"PeriodTypeCode" : "WORK_PERIOD",
"ShiftTypeCode" : "TIME",
"ShiftDetailTypeCode" : "NONE"
}
Example Response Body
The following example includes the contents of the response body in JSON format:
{
"ShiftId" : 300100111082919,
"Name" : "SHIFT-Example",
"Description" : "Shift Example of Post",
"Code" : "",
"StartTime" : "09:00 AM",
"EndTime" : "17:00",
"Duration" : 8,
"DurationUnit" : "HOURS",
"CategoryCode" : "WORK_FROM_OFFICE",
"PeriodTypeCode" : "WORK_PERIOD",
"ShiftTypeCode" : "TIME",
"ShiftDetailTypeCode" : "NONE",
"links" : [ ... ]
}