e-days is pleased to announce the release of e-days version 5.65. For a complete list of improvements and changes please see the list below.
If you have any questions relating to the updates, please contact the support team:
API – Rota endpoint
There is an existing rota endpoint, but it was insufficient because it only assigned the pattern without altering calendar data at all.
The existing endpoint assigns the rota to the user in the table, and any existing records are removed from the table.
We have added an optional date field to the existing rota endpoint. When running the new endpoint, that is the date the rota will be applied from. If no date is supplied, it will choose today’s date.
The new endpoint can be applied to a batch of users:
Calendar day entries are created matching the applied rota from the start date specified on the rota application table for a period running for two years from the current date.
Any user that does not have a record in the table is ignored.
Existing calendar data before the Rota application start date are unchanged.
Any absences that fall on days changed by the rota application are unchanged.
There is no day verification, so you can choose to assign a weekly rota on a non-Monday.
Applying a weekly rota pattern on a Wednesday will skip the first 2 days of the rota pattern. This means that the days in the rota pattern will occur on the correct day of the week in the calendar going forward.
API – Absence duration added to GET absence endpoint
GET absence returns and .
Note: There is no POST or PUT associated with these at this moment.
API documentation has been updated to reflect these changes.