Events - 1.52.0

- Given an overpayment has been previously assigned via the 'Allocate Overpayments' feature in Events Host, if a user selects 'View all payments', there will be an option to 'deallocate' the payment as shown below. This will essentially undo the previous action.

Note: Users will not be able to refund allocated payments unless they are deallocated first.

Note: Users will not be able to deallocate deposit allocations without first deallocating prepayments.

This can be configured in Zonal Admin > TimeZones > Edit Estate:

Users are also now able handle time zones during the booking journey via the External API:

- An additional attribute called ‘SiteTimezone’ has been added to the Event endpoint.

- An additional attribute for group ‘Sites’ called ‘Time zone’ has been added to Outlets endpoint.

- All products will now use the term Card Guarantee instead of Pre Authorisation (there is no change to functionality)

- The External API Pre Authorisation fields have been replaced by Card Guarantee fields (Pre Authorisation field requests will still be accepted)

Note: Standard email templates have been updated to 'Card Guarantee', however any bespoke Subject & Body text will need to be updated by Estate Admins.

Example below:

- The highlighted text shows the previous count (200), with the remaining text demonstrating the length of the new Special Request Field. This is valid for all booking journeys that have the Special Request field.

- On the Enquiries Beta page, the first 200 characters of the text are shown in the table and when the user hovers, the full text of 1000 characters is displayed.

- When using the print functionality on the Enquiries Beta page, only the first 200 characters of text are shown.

- Creating a new API Key

- Editing an API Key

- View API Keys

On select, users will be able to assign their required timeframe in the pop-up calendar as shown below. Additionally, a ‘created’ column has been added to the enquiries beta page.

Event ‘Created’ column is also added to the Export CSV file:

and in the print view:

Example Below:

- When setting an Occasion using a Schedule, there is now an enhancement to exclude specific dates, not just dates based on a rule.

- Users should configure their Occasion as per existing functionality. Once the Occasion has been configured, then the Schedule details box should be configured. If Recurrences are being used, then the Start and End Date should be the same – if no Recurrences are being used, then the Start and End Date should reflect the date range of the Occasion.

- To add Exclusions, the Exception type box should be expanded and a choice made: Exception Rules continue to behave as existing functionality. A User can now select “Manual Date Selection”.

- This opens the Manual Exclusions Date Picker, and up to 10 excluded dates can be selected:

- If users require more than 10 dates, or the excluded dates follow a pattern as per this example, users should instead use an exclusion rule.

- Once selected, the Excluded Dates are displayed in a box below the calendar, allowing users to see all selected dates, regardless of the calendar month view.

- Changes should be saved, as per existing functionality.

- Once these Exclusions have been made, the Occasion will be unavailable for booking (Site Hosts can still override this functionality).