Absence
Namespace: CCPEntities
Summary
When working with absences we make a difference in Ill/Available records and Holiday/other records. They are handled and interpreted differently:Ill/Available records:
- CCPEntities.AbsenceType.Ill and CCPEntities.AbsenceType.Available are two seperate records. Once someone is reported Ill, the person will remain Ill until he is reported Available.
- Both Ill and Available records are valid throughout the entire day.This means that only the date-part of the From field is used, not the time-part.
- The field Until is not being used.
- If, for example, someone is reported Ill at 09:00, the report will also apply to trips that were planned earlier that same day or trips that are busy at the time of the report. CCPEntities.Trips that are already performed that day remain obviously unaffected (If the CCPEntities.Traveler was reported Ill too late, the Traveler would have been reported CCPEntities.MovementStatus.NoShow by the Driver.)
- If, for example, someone is reported Available at 16:00, the Traveler will already be expected available on the remaining trips that day.It that case it might be advisable to report the Traveler Available the next day by filling in a From-date of the next day
- If multiple Ill and Available reports are made the same day, the From field will not suffice to determine their order (as it contains only the date-part). The field RegistrationTime will be leading in this particular case.
- AbsenceScopeNames like CCPEntities.AbsenceScope.OnlyTo, CCPEntities.AbsenceScope.OnlyReturn or CCPEntities.AbsenceScope.Both are not applicable for Ill/Available records, because these records are always valid for the entire day.
- CCPEntities.AbsenceType.Holiday and CCPEntities.AbsenceType.Other are always one record each day. So if a CCPEntities.Traveler is on a holiday from 15-01-2015 until 20-01-2015, six Absence-records are added.
- Of the field Until only the time-part will be used.
- A Holiday/Other-record can be valid in the following ways:
- The entire day: The time-part of the From field is 0:00, the Until field is either null or its time-part has the value 0:00.
- A part of the day: the time-part of either the field From or the field field Until has a value different from 0:00.
- During trips towards/from a location: AbsenceScopeName will contain CCPEntities.AbsenceScope.OnlyTo or CCPEntities.AbsenceScope.OnlyReturn.
Syncable
This object is syncableProperties
| Name | Type | FixedLength | MaxLength/Range | Identity | Summary | Value | |
|---|---|---|---|---|---|---|---|
|
|
AbsenceId* | Edm.Int32 | False | true | |||
| From* | Edm.DateTime | False | |||||
| Until | Edm.DateTime | False | |||||
| CreationDateTime* | Edm.DateTime | False | The date/time when the entity was created in CCP | UTC timezone | |||
| RegistrationDateTime* | Edm.DateTime | False | The registration date/time of the entity | ||||
| LastUpdatedUsername | Edm.String | False | 50 | The username of the user that did the last update on the entity | |||
| CreatorUsername | Edm.String | False | 50 | The username of the user that created the entity | |||
| LastUpdated | Edm.DateTime | False |
A timestamp of the last update of the entity in CCP. Check this property in order to know if you are in sync with CCP. |
A timestamp in UTC. | |||
| Deleted* | Edm.Boolean | False | Indicates whether this CCPEntities.Interfaces.ITracable is logically deleted. |
|
|||
| Remark | Edm.String | False | 150 | ||||
| AbsenceTypeName* | AbsenceType | False | 50 | ||||
| AbsenceScopeName | AbsenceScope | False | 50 | ||||
| TravelerId* | Edm.Int32 | False |
Navigation Properties
| Name | Type | Multiplicity | Summary | |
|---|---|---|---|---|
| Traveler | Traveler | 0..1 |
Additional Information
Notable information when adding a recordChecks if the user has sufficient rights to add/change/delete a record and performs the desired operation.