openShiftItem resource type
Namespace: microsoft.graph
Important
APIs under the /beta
version in Microsoft Graph are subject to change. Use of these APIs in production applications is not supported. To determine whether an API is available in v1.0, use the Version selector.
Represents the details of an open shift.
Inherits from shiftItem.
Properties
Property | Type | Description |
---|---|---|
activities | shiftActivity collection | An incremental part of a shift that can cover details of when and where an employee is during their shift. For example, an assignment, a scheduled break, or lunch. Required. Inherited from shiftItem. |
displayName | String | The shift label of the openShift. Inherited from shiftItem. |
endDateTime | DateTimeOffset | The end date and time for the openShift. Required. The timestamp type represents date and time information using ISO 8601 format and is always in UTC. For example, midnight UTC on Jan 1, 2014 is 2014-01-01T00:00:00Z . Inherited from shiftItem. |
notes | String | The shift notes for the openShift. Inherited from shiftItem. |
openSlotCount | Int32 | Count of the number of slots for the given open shift. |
startDateTime | DateTimeOffset | The start date and time for the openShift. Required. The timestamp type represents date and time information using ISO 8601 format and is always in UTC. For example, midnight UTC on Jan 1, 2014 is 2014-01-01T00:00:00Z . Inherited from shiftItem. |
theme | scheduleEntityTheme | The color of the open shift. Possible values are: white , blue , green , purple , pink , yellow , gray , darkBlue , darkGreen , darkPurple , darkPink , darkYellow , unknownFutureValue . Inherited from shiftItem. |
JSON representation
The following JSON representation shows the resource type.
{
"activities": [{"@odata.type": "microsoft.graph.shiftActivity"}],
"displayName": "String",
"endDateTime": "String (timestamp)",
"notes": "String",
"openSlotCount": "Int32",
"startDateTime": "String (timestamp)",
"theme": "String"
}
意見反應
https://aka.ms/ContentUserFeedback。
即將登場:在 2024 年,我們將逐步淘汰 GitHub 問題作為內容的意見反應機制,並將它取代為新的意見反應系統。 如需詳細資訊,請參閱:提交並檢視相關的意見反應