Get one calendar shift

get

/fscmRestApi/resources/11.13.18.05/calendarShifts/{calendarShiftsUniqID}

Request

Path Parameters
  • This is the hash key of the attributes which make up the composite key--- CalendarCode, ShiftNumber, ExceptionStartDate and Sequence ---for the Calendar Shifts resource and used to uniquely identify an instance of Calendar Shifts. The client should not generate the hash key value. Instead, the client should query on the Calendar Shifts collection resource with a filter on the primary key values in order to navigate to a specific instance of Calendar Shifts.

    For example: calendarShifts?q=CalendarCode=<value1>;ShiftNumber=<value2>;ExceptionStartDate=<value3>;Sequence=<value4>
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 : calendarShifts-item-response
Type: object
Show Source
  • Title: Calendar
    Read Only: true
    Maximum Length: 240
    Name of the workday calendar.
  • Title: ID
    Read Only: true
    Maximum Length: 255
    Unique identifier for the calendar in the source system.
  • Title: End Time
    Read Only: true
    Time that the shift ends. Shift times can't overlap. Enter time in seconds.
  • Title: Shift Exception End Date
    Read Only: true
    Last date till which any exception in the calendar is valid. This date must be within the calendar start date and end date.
  • Title: Shift Exception Start Date
    Read Only: true
    Start date from which the exception in the calendar is valid. This date must be within the calendar start date and end date.
  • Title: Exception Type Code
    Read Only: true
    Code for the exception type. Valid values are 1 - Available and 2 - Not Available.
  • Title: Exception Type
    Read Only: true
    Maximum Length: 4000
    Name of the exception type. For example, Available, or Not Available.
  • Links
  • Title: Sequence
    Read Only: true
    Sequence number of the date on a calendar.
  • Title: Shift Days Off
    Read Only: true
    Number of consecutive nonworking days.
  • Title: Shift Days On
    Read Only: true
    Number of consecutive working days.
  • Title: Shift Name
    Read Only: true
    Maximum Length: 80
    Name of the calendar shift.
  • Title: Shift Number
    Read Only: true
    Number of the calendar shift.
  • Title: Start Time
    Read Only: true
    Time from which the shift starts. Shift times can't overlap. Enter time in seconds.
Back to Top