Expanded API (Get Shifts in Range & range_end)
With release 18.8 following two improvements have been implemented regarding our API:
- The API request Get Shifts in Range is now returning, besides the already existing company_id, the location_id.
- The parameter range_end can now be used as an optional parameter. When this parameter isn't defined, the current timestamp is being used. Following data types are affected by this change: Time tracking, Absences, Shifts, Records.
Fixed a bug, where it was possible to edit time tracking which has already been confirmed via the mobile app.
Fixed a bug, which caused hosted pages not being displayed properly.
Fixed a bug, which caused problems during the login, when the google login has been used.
Fixed a bug which caused workflow warnings not showing up, when data type "Absence" was used together with the rule "Number of days in period for absence type".
Fixed various smaller bugs which occurred in the roster, when the user switched from specific views to other views or the task calendar.
Fixed a bug, where the tooltip in the roster for applications on shifts was not shown when hovering above the blue dot.
Fixed a bug which caused the actions columns on the absence overview site not being sorted when clicking on the arrows in the column header.
Fixed a bug in the assignment window, where the employee list wasn't displayed properly when an employee had a long name.
Fixed a bug, which caused an endless loading screen, when the input field of a note/tag has been used when editing a shift and the user clicked on an empty spot on the roster to open another shift creation window.
Fixed a bug, which caused a line break when hovering over an employee name in the employee list of the calendar, when the box with the displayed hours was quite big.
Fixed a bug, where it wasn't possible to create a PDF export of payrolls when the location had a lot of employees.