This functionality can cater for both creating, amending or deleting absences. the JSON request can pass on an optional parameter 'Action'. If this action is NOT SET (blank/null) or if it is set to 'I', then this functionality will act as an INSERT. If the action is set to 'M', then this functionality will act as an AMEND. If the action is set to 'D', then this functionality will act as DELETE. Alternatively, it supports PATCH functionality for amending absence related fields.

The 'PostId' can be supplied but is not mandatory. If left blank/null, then the functionality will use the employee's MAIN POST as held in ResourceLink.

The 'AbsenceStart' is a mandatory parameter for both PUT and PATCH.

The 'AbsenceEnd' can also be left blank and if it does, then this is treated as an open-ended absence and is subject to existing business logic surrounding Open Ended Absence functionality. This rule applies for both PUT and PATCH.

The 'AbsenceStartTime' and 'AbsenceEndTime' are optional parameters. If left blank, then functionality will retrieve it from session times as how the core standard functionality works.

The 'AbsenceTypeId' is a mandatory parameter for both PUT and PATCH.

We also introduced the capability to load multiple sets of data or bulk load.

Bulk Data Load

We introduced the concept of HTTP Header (zip-backend-bulk) to support this. The value can either be left blank or Y. If it is blank, then it is assumed that we are processing a single data set. If it is set to 'Y', then we processing a bulk data load.

None of the existing JSON field names will change.
"Bulk" array keyword is to be used for bulk data load.
All business validation rules will remain for single/bulk data load.