Events - 1.36.0

Stop Same Day Enquiries - Zonal ID 396204

Administrators can set a restriction to the number of days in advance they are willing to accept enquiries, by Estate, Company and Site. This will allow customer to prevent enquiries being made at short notice that sites may not be able to accept / reject in time.

This enhancement brings feature parity with Reservations setting Enquiry Days Stop in Options > Options.

Guest Portal: Prevent Booking amendments after the booking date - Zonal ID 399871

Guest still have access to a booking through the guest portal after the expiry of a booking date, but they can no longer make any amendments, including:

• Manage an event

• Add, remove, or update attendees

• Cancel the booking

• Pay for the booking

• Choose meals

• Message the host

Guest Portal: Messaging to be appropriate when not Braintree Integrated - Zonal ID 402152

When a site is using Secure Trading or Worldpay, a relevant notice is now presented on the guest portal to inform guests that only the organiser can pay an amount due.

Guest Portal - Organiser

• The event overview payment section now displays a message to advise the organiser they need to pay the entire deposit

• The "Pay Now" button has been renamed to "Pay Total Now"

Guest Portal - Attendee

• All payment messages have been removed and a new messages to advise the attendee "All payments are made through the organiser of your event"

Turn Time Synchronisation between Events and Tables - Update from Events - Zonal ID 405142

In this next phase of addressing the synchronisation of the Turn Time between Events and Tables, the update journeys from the Events host app, Guest Portal and External API have been addressed. On updating an event from within any of the products, the turn time will be respected based on a hierarchical order and synchronised between Events and Tables.

If a booking is made in Events, the hierarchy is:

• First the turn time as set against the selected Occasion if any,

  • Then any turn time as configured in Manage Tables

  • Finally, the default turn time will be used

If booking is made in Tables, then the hierarchy is:

• Manually selected turn time in Tables

  • Turn Time as set against the selected Occasion

  • Turn time configured in manage tables

  • Finally default turn time

   

 

Events Admin
Update admin to determine the advance booking days to accept enquiries

 

Events Guest Portal
Guest Portal: Should not be able to made any amends after the booking date
Guest Portal - Messaging to be appropriate when not Braintree Integrated
Turn Times - Events and Tables to respect the valid turn time of an Event on UPDATE at Guest Portal and Events External API

 

Events Host App
Turn Times - Events and Tables to respect the valid turn time of an Event on UPDATE at Events Host App

 

 

Zonal ID	Description
422536	Events - keyboard opens over the message box during the guest booking process

 

 

Description
Apply Mediator Pattern to OccasionsController
Apply Mediator Pattern to TagsController
Apply Mediator Pattern to ReservationsImportController
Apply Mediator Pattern to SiteCapacityController
Apply Mediator Pattern to SessionsController
Apply Mediator Pattern to TransactionsController
Apply Mediator Pattern to SiteEventsController
Apply Mediator Pattern to UpsellsController
Remove CorrelationId logs from being sent to Graylog
Implement Nettitude logging in Events
Add Health checks to Reservations
Nettitude: Request Body Should Be Only Logged For Security Endpoints