| Info |
|---|
Release date 17-08-2024 |
Changes
Key | Release note |
|---|---|
AXX-2400 | Administrators - Additional fields added to the Reservation and Reservation Item object The following fields are added to the Reservation and ReservationItem objects: -Reservation.lateCancel These fields currently do not have any business logic added and will be used in the Workplace Management baseline in the future for reservation related features. |
Administrators - visitor type added: The Visitor object now also has a VisitorTypeCode field. This field will be used for integration purposes in the future. | |
Administrators - visitor.functionalUpdateTime added: The Visitor object now also has a functionalUpdateTime field. This field will be used for integration purposes in the future. | |
Administrators - visitor.uniqueReference added: The Visitor object now also has a uniqueReference field. This field will be used for integration purposes in the future. | |
Integrations - Updating objects via API: Previously, when updating a field related to an object (e.g. areaId in a request) via the API, it was mandatory to use the DataBaseId value of that object. From now on, the UniqueReference of the object can also be used for this (for objects that have a UniqueReference field). | |
Reservations – Catalog item price: If a reservation is created for a catalog Item (catering/services), the price in the reservation Item is only set based on rates (‘reservablePricing’) linked to the catalog Item reservable object. However, since with the new Workplace Experience integration regarding service & equipment, only fixed prices are currently used for the services (catalog item), the price in a reservation Item is now also set based on the ‘CatalogItem.sellprice’, if rates are not used. Previously the price in the reservation Item would remain '0,00', instead of set based on the catalog item sell price. | |
Recurring reservations - Updating reservations: When changing the reservations based on a reservation schedule, it was necessary to first put the desired reservations into 'change' status and only those reservations were updated based on the schedule. This has been changed. From now on, if the 'update' function ('Create/submit/update reservations) ' is used in a reservation schedule, all open reservations are automatically put to change status (if still allowed by the workflow) and updated and re-submitted based on the changes done in the template (e.g. changed the reserved resources or updated the subject of the reservation) or the recurring schedule (e.g. weekly instead of daily). This makes it easier for users, as it takes a lot less manual actions to update reservations based on a reservation schedule and this also makes sure this functionality is in line with how Outlook and Google calendar recurring reservations work. It is still possible to change a single reservation in a reservation schedule by opening that reservation and changing it. If however the schedule is later updated, any reservation deviating from this schedule will also be put back in line with the schedule, similar to Outlook. | |
Administrators - Additional fields added to the Reservation and Reservation Item object The following fields are added to the Reservation and ReservationItem objects:
These fields currently do not have any business logic added and will be used in the Workplace Management baseline in the future for reservation related features. | |
Administrators - visitor type added: The Visitor object now also has a VisitorTypeCode field. This field will be used for integration purposes in the future. | |
Administrators - visitor.functionalUpdateTime added: The Visitor object now also has a functionalUpdateTime field. This field will be used for integration purposes in the future. | |
Administrators - visitor.uniqueReference added: The Visitor object now also has a uniqueReference field. This field will be used for integration purposes in the future. |
Bugs
Key | Release note |
|---|---|
Exchange integration - Canceling an ongoing reservation: When a recurring reservation is canceled via Outlook that contains a reservation that is currently taking place, that same reservation in Workplace Management was not canceled. This has been fixed. | |
Reloading fields - Auto complete fields: An auto complete field (e.g. a supplier contact field on an asset in which you type the first few characters and suggestions are shown in a drop-down to select from) always saved that field, without saving the other fields on the page, even if a reload on the field (used to auto. save a page if a specific field is changed) or a general save was not done. This was not consistent with the other types of fields and caused issues when this field was used (via a script) to automatically set a certain other field on the page via a reload on this auto. complete field, resulting in the other field not being set to the value determined by the script, due to this semi double save mechanism. This has been fixed. An auto complete field no longer automatically saves the value put in the field, unless the field is set to reload (as that results in a save on the page) or the page is saved in another way ('save' or 'save and return' page function is used, or another field is set that also reloads (and thus saves) the page. |