Software Release 19/02/2019
Bookeasy successfully released the below changes into the live production system overnight. Should you require any further information in regards to any of the below features, please reach out to our friendly Bookeasy Support team who will be more than happy to help.
AUTOPOPULATE BUTTON MOVED AND RENAMED TO "QUICK FILL" [#12556]
Back in January, a new button called "AutoPopulate" was introduced to the Bookeasy Staff Console's checkout page in order to help speed up the booking process by pre-filling quick checkout information. Based on feedback received, Bookeasy has re-named the button to "Quick Fill" and has moved the position of this button so that it now sits at the top of the checkout page. Prior to this change, the button's placement was directly above the "Make Booking or Sale" button and prone to inadvertent clicks.
REPORT BUILDER DATETIME FIELD FORMATTING [#12537]
The formatting of DateTime fields in Bookeasy's Report Builder has been improved in order to provide better accuracy when parsing the data to Bookeasy's Reporting API to generate reports. This means that if you use a DateTime field as a filter in your report, you will receive correct results. A DateTime field is a datapoint in Bookeasy that includes both a date and time (e.g. 20/02/2019 15:30:59).
The below fields are affected by the formatting improvement:
|DATA TABLE||DATA COLUMN|
Please note that if using one of the above DateTime fields as a filter in your report, you may need to be specify two separate filters, such as a date greater than or equal to (>=) the date being searched, and also a date less than or equal to (<=) the date being searched. This is because the Report Builder user interface currently allows for a date value only (not a date/time value).
It should be noted that the Reporting API truncates the returns ReturnDate value (i.e. it automatically strips the time out), which means you will be able to just specify a singular date in your report filter without an issue.
DISPLAYING PARTNER CONNECTED PRODUCT [#12319]
Enhancements have been made so that if a LIVN or Rezdy partner connected tour operator is linked to multiple Bookeasy centres, each centre can sell and display select product only. This means that only the products connected will be available for sale by the centre. Prior to this enhancement, if a LIVN or Rezdy partner connected tour operator was linked to multiple Bookeasy centres, then all of the tour operator's products were available to sell with each centre.
YESBOOKIT PARTNER CONNECTION [#12498]
Minor tweaks to Bookeasy's YesBookit partner integration have been made, such as compatibility enhancements for various content formats when importing/connecting new accommodation providers (such as phone number formats). This assists in minimising issues when connecting new YesBookit accommodation providers to Bookeasy.
REFRESHING PARTNER CONNECTED PRODUCTS [#12470]
Improvements have been made so that when a previously connected LIVN or Rezdy partner connected operator's connection is refreshed within Bookeasy, that any prior changes that have been made in Bookeasy to their tour description remain unchanged. Prior to this change, if the connection was refreshed then any changes made to a LIVN/Rezdy tour operator's tour name or tour description would be reset. Due to background services that require the tour name to remain unchanged, Bookeasy has also introduced a change that disables the ability for the tour name to be changed from within the partner connected tour operator's Bookeasy Tours operator console.
Printing the Operator Remittance Advice [#12551]
Resolved a browser issue that prevented page breaks when printing multiple Operator Remittance Advice statements. The fix ensures that each remittance ends in a page break so that the following remittance is printed on a new page.
Itinerary Totals That Don't Match the Total of Bookings Made [#12440]
Corrections have been made to the query used for updating and displaying the Total Cost of an itinerary in the Bookeasy Staff Console. On rare occasions the previous query could lend itself to errors whereby an itinerary's total value might not match the total value of all the bookings on the itinerary, in the event cost adjustments had been made on one of the bookings on an itinerary.