Skip to content

29 October 2024

On Tuesday 29 October, a new version of the application was released. In this release, a large number of issues has been resolved.

Resolved issues that apply to all users

The following issues that affected all users have been resolved.

  • Creating a booking in the past is now possible. Previously, only domain admins could do so, but from now on, all users can register a booking that took place in the past. However, once created, modification and cancellation are restricted to device managers only. If you need to modify or cancel your past booking, contact the manager of the device.
  • Accounts will be automatically archived after not logging in for 365 days (see note below).

Resolved issues that are only relevant to domain admins

The following issues that only affected domain admins have been resolved.

  • Admin users can now modify their default costplace again
  • A costplace may now figure both as default costplace and as additional costplace.
  • When using the impersonate functionality, the default costplace of that user is now pre-selected as costplace.
  • The costplace and departments where not correctly saved when creating a booking, leading to missing data in reports. New bookings will have the correct data stored in the database; we are still trying to retrieve missing data from past bookings.
  • Devices belonging to more than one category were shown double in the reports (one record per category, leading to incorrect totals). These records have been merged to one record per booking.
  • Devices marked as 'red' (inactive, visible, but not bookable) can now be booked by admin users again (see note below).

Notes regarding the automatic archiving of user accounts

  1. From Tuesday 5 November on, we will start archiving all non-activated users (that is, users who have logged in but have not been added to a device group yet) that have been created more than 50 days ago (i.e., before 16 September 2024). Generally, this concerns users that used their SurfConext credentials to log into the application without actually having any intend of using it. Therefore, these users will not receive a notification of this archive action. If a user still wants to use the application, s/he can contact the manager of the device s/he wants to book, and this manager can reactivate the user's account again. This archiving job will run daily and affects all non-activated users that have not logged in for 50 days.
  2. From the same day on, we will re-enable account archiving for activated users that have not logged in for more than 365 days. This means that the first accounts will we archived on 29 May 2025. This archiving job will run daily as well.

Note regarding the default and additional costplaces

Since this release, you can enter the entire list of costplace of a user among the additional costplaces, and use default costplace to indicate which of those costplaces is the default to use. Previously, this was not possible. When a user had three costplaces (e.g., costplaces A, B and C), and costplace A was default, B and C were additional, switching the default costplace would imply both changing the default costplace (from A to B) and changing the additional costplaces (remove B, add A). From this release on, admins that regularly switch from default costplace, can set A, B and C as additional costplace, and simply switch the default costplace from A to B if applicable. The application will accept the same costplace figuring both in default costplace and additional costplaces.