Changelog

Follow up on the latest improvements and updates.

RSS

Default Inventory Control
: Elastic inventory is now set as the default method.
Room Blocks Enhancements
: We now send Release Date (aka cut off) date field to room blocks and block details when pushing data.
Rate Calculation Fix:
Resolved an issue where invalid rates were applied to room blocks beyond the first day.
We've fixed the issue where clicking on an organization merge field edit icon in the document page, resulted in a redirect to a 404 page. Now it appropriately redirects you to the Organization general settings page as expected.
image

fixed

Groups & GRC

PMS

Opera PMS Release Date

We have resolved an issue where the Group’s Release Date was being assigned the Group’s Arrival Date if the Group was edited.
Any affected Groups will need to be edited with the correct Release Date re-selected.

fixed

Organization Settings

Delete Account Types

We have fixed the issue with being unable to Account Types, now the deletion works as expected
Zapier actions have been updated to support creating/updating Contact custom fields
image
We've updated the filter for archived items:
  • Previously, both archived and unarchived items were visible when selecting "Include Archived."
  • Now, the filter is named "Archived" and only archived items are shown when filter is set to True.
image
Additionally, Archived items are now hidden when selecting a Menu Item within a Space.
image
Admins can now control whether new Groups sync with Opera by default. Existing Opera Integrations are set to 'yes' by default to maintain current behaviour.
image
Changing the setting to
no
means the
Create on PMS
option will not be selected by default. This is useful if you have a lot of lead status Groups that you
do not
want to be synced with Opera.
image
We have fixed a bug where Read Only Users were not able to update their Password or Profile Logo in their Personal Settings.
Read Only Users are now able to edit their current password to our new requirements for the rollout of our exciting security updates!
Batch event cloning now supports cloning Events to a different Booking.
image
Please note
: All cloned Events will now default to the Lead status, regardless of the original Event's status (e.g., Definite). This update separates conflict checking from the cloning process. Cloning Events as Lead status ensures there are no conflicts during the initial cloning. It's possible to later edit the status, and any conflicts will be displayed and can be addressed.

improved

Bookings & Events

Include notes when cloning a Booking

Now when cloning Booking, there is an option to clone the notes as well.
image
Load More