Create a Power Unit

post

/drivers/{driverGid}/powerUnits

Request

Path Parameters
Supported Media Types
Request Body - application/vnd.oracle.resource+json;type=collection ()
Root Schema : schema
Type: object
Show Source
Nested Schema : items
Type: array
Show Source
Nested Schema : schema
Type: object
Show Source
  • The GID for the calendar that determines the day and times when the power unit can be used with the driver. For example, if you select a calendar for Monday through Friday, 8 a.m.-8 p.m., that power unit would be used with that driver Monday through Friday, 8 a.m.-8 p.m.. On a different driver you could then select a time of Monday through Friday, 8 p.m. -8 a.m., as well as on any time on Saturday and Sunday, and assign the same power unit to a different driver. Only calendars with an activity of Driver Work will be considered for overlap when other drivers share the same power unit. Validation checks against other calendars for duplicate assignments when you save. By establishing power unit availability to multiple drivers through the use of a calendar, you are defining "slip seating".
  • Database domain where this data is stored.
  • effectiveDate
    The effective date for this Driver and Power Unit union.
  • expirationDate
    The expiration date for this Driver and Power Unit union.
  • links
    Read Only: true
  • The power unit assigned to the driver.
  • Primary key of the table.
Nested Schema : effectiveDate
The effective date for this Driver and Power Unit union.
Match All
Show Source
Nested Schema : expirationDate
The expiration date for this Driver and Power Unit union.
Match All
Show Source
Nested Schema : links
Type: array
Read Only: true
Show Source
Nested Schema : dateTimeType
Type: object
Show Source
Request Body - application/vnd.oracle.resource+json;type=singular ()
Root Schema : schema
Type: object
Show Source
  • The GID for the calendar that determines the day and times when the power unit can be used with the driver. For example, if you select a calendar for Monday through Friday, 8 a.m.-8 p.m., that power unit would be used with that driver Monday through Friday, 8 a.m.-8 p.m.. On a different driver you could then select a time of Monday through Friday, 8 p.m. -8 a.m., as well as on any time on Saturday and Sunday, and assign the same power unit to a different driver. Only calendars with an activity of Driver Work will be considered for overlap when other drivers share the same power unit. Validation checks against other calendars for duplicate assignments when you save. By establishing power unit availability to multiple drivers through the use of a calendar, you are defining "slip seating".
  • Database domain where this data is stored.
  • effectiveDate
    The effective date for this Driver and Power Unit union.
  • expirationDate
    The expiration date for this Driver and Power Unit union.
  • links
    Read Only: true
  • The power unit assigned to the driver.
  • Primary key of the table.
Nested Schema : effectiveDate
The effective date for this Driver and Power Unit union.
Match All
Show Source
Nested Schema : expirationDate
The expiration date for this Driver and Power Unit union.
Match All
Show Source
Nested Schema : links
Type: array
Read Only: true
Show Source
Nested Schema : dateTimeType
Type: object
Show Source
Back to Top

Response

Supported Media Types

Default Response

Default Response.
Body ()
Root Schema : schema
Type: object
Show Source
  • The GID for the calendar that determines the day and times when the power unit can be used with the driver. For example, if you select a calendar for Monday through Friday, 8 a.m.-8 p.m., that power unit would be used with that driver Monday through Friday, 8 a.m.-8 p.m.. On a different driver you could then select a time of Monday through Friday, 8 p.m. -8 a.m., as well as on any time on Saturday and Sunday, and assign the same power unit to a different driver. Only calendars with an activity of Driver Work will be considered for overlap when other drivers share the same power unit. Validation checks against other calendars for duplicate assignments when you save. By establishing power unit availability to multiple drivers through the use of a calendar, you are defining "slip seating".
  • Database domain where this data is stored.
  • effectiveDate
    The effective date for this Driver and Power Unit union.
  • expirationDate
    The expiration date for this Driver and Power Unit union.
  • links
    Read Only: true
  • The power unit assigned to the driver.
  • Primary key of the table.
Nested Schema : effectiveDate
The effective date for this Driver and Power Unit union.
Match All
Show Source
Nested Schema : expirationDate
The expiration date for this Driver and Power Unit union.
Match All
Show Source
Nested Schema : links
Type: array
Read Only: true
Show Source
Nested Schema : dateTimeType
Type: object
Show Source
Back to Top