EmployeeContractDateChangeImpact
What changing the dates of an employee contract would affect. Only the part of the old contract period that the change removes is examined, so services belonging to another contract of the employee never count.
type EmployeeContractDateChangeImpact {
absences: [ContractDateChangeAbsence!]!
addedPastPeriods: [ContractDatePeriod!]!
blocked: Boolean!
blockingAttendances: [ContractDateChangeBlockingAttendance!]!
blockingServices: [ContractDateChangeBlockingService!]!
blockingTours: [ContractDateChangeBlockingTour!]!
earliestPossibleEndDate: Date
employeeName: String!
latestPossibleStartDate: Date
lendings: [ContractDateChangeLending!]!
manualOvertimeEntries: [OvertimeManualChange!]!
openTours: [ContractDateChangeTour!]!
shifts: [ContractDateChangeShift!]!
}
Fields
EmployeeContractDateChangeImpact.absences ● [ContractDateChangeAbsence!]! non-null object
Approved absences outside the new period. They are not changed.
EmployeeContractDateChangeImpact.addedPastPeriods ● [ContractDatePeriod!]! non-null object
The days up to yesterday that the new dates add to the contract, oldest first: before the old start date and after the old end date. Saving the change creates no attendances for them: their attendances must be entered manually. Today and later are left to the daily check in Odoo.
EmployeeContractDateChangeImpact.blocked ● Boolean! non-null scalar
True when confirmed services, completed attendances or tours planned up to today lie outside the new period, so the change cannot be saved.
EmployeeContractDateChangeImpact.blockingAttendances ● [ContractDateChangeBlockingAttendance!]! non-null object
Completed attendances outside the new period that block the change, oldest first.
EmployeeContractDateChangeImpact.blockingServices ● [ContractDateChangeBlockingService!]! non-null object
Confirmed services outside the new period that block the change, one entry per tour, oldest
first. Together with blockingAttendances and blockingTours this lists everything on
earliestPossibleEndDate and latestPossibleStartDate.
EmployeeContractDateChangeImpact.blockingTours ● [ContractDateChangeBlockingTour!]! non-null object
Tours outside the new period that block the change, oldest first. Up to today (PLANNED):
active tours of the employee, as owner or accompanying, and accepted lendings to another park;
they are neither unassigned nor ended, since the employee may already have worked them. From
tomorrow on: accepted lendings that the lending park could not cancel either, because the
requesting park has locked its shift plan or the tour has been started (reason). A day with
confirmed services is reported through those and its tours are not listed here, so a listed
tour on earliestPossibleEndDate or latestPossibleStartDate means blocking tours alone set
that date.
EmployeeContractDateChangeImpact.earliestPossibleEndDate ● Date scalar
Set when confirmed services, completed attendances or blocking tours lie after the new end date: the day of the last of them, which is the earliest end date the contract can have.
EmployeeContractDateChangeImpact.employeeName ● String! non-null scalar
Full name of the employee, for the messages that quote it.
EmployeeContractDateChangeImpact.latestPossibleStartDate ● Date scalar
Set when confirmed services, completed attendances or blocking tours lie before the new start date: the day of the first of them, which is the latest start date the contract can have.
EmployeeContractDateChangeImpact.lendings ● [ContractDateChangeLending!]! non-null object
Lendings of the employee to another park from tomorrow on outside the new period that would be
ended: accepted lendings, whose request is reopened and whose tour becomes unassigned again, and
pending offers, which are withdrawn. An accepted lending up to today is in blockingTours.
EmployeeContractDateChangeImpact.manualOvertimeEntries ● [OvertimeManualChange!]! non-null object
Manual overtime entries (payout, carry-over) outside the new period. They are kept.
EmployeeContractDateChangeImpact.openTours ● [ContractDateChangeTour!]! non-null object
Open tours from tomorrow on outside the new period the employee would be unassigned from, on the
target tour and its active tour. The tours and their services remain, unassigned. A tour of
another park the employee is lent to is listed in lendings instead. Tours up to today are left
unchanged.
EmployeeContractDateChangeImpact.shifts ● [ContractDateChangeShift!]! non-null object
Shifts from tomorrow on outside the new period that would be removed from the live shift plan,
apart from the shifts of the tours in openTours. Shifts up to today and saved shift plans are
not changed.