Patch 1.13.1 adds the following:
- Added a flow property to disable customer account creation and force guest checkout
- Rerouted reports and dashboards to a separate slave database. The reporting data will now be in pseudo-real time with a replication speed between 20ms (default) and 25s (under high load)
- Fixed a performance issue when claiming capacities under high load
- Added the possibility to add a market place logo to a mobile ticket
After deploying time slots in the web shop, box-office and reports; we will also ship the time slot configuration screens to our back-office. In addition we'll also be showing the selected time slot in the admin purchase details screen.
This will allow self-service configuration of time slot events.
We'll be concluding our legacy product migration by shipping the fee administration screens to our new admin section.
Legacy platform deprecation
The legacy platform accessible through the app.yourdomain.com link will become deprecated and obsolete. We will revoke access in the coming months.
Ticket type categories
We'll be adding ticket type categories for non-seated events. These categories will group and categorize your ticket types nicely together in the web shop. They can be used for endless use cases such as up selling, donations, grouping of different entrances and so on.
Capacity based ticket type relations
We'll be adding a new type of ticket type relation which will put a configured ticket type on sale when the capacity of another ticket types has reached a predefined threshold.
We'll add a new checkbox on question level to print the answer of this question on the PDF ticket. Additionally we're adding an event filter to the questions report to make it easier to collect all answer data for one particular event.
Organizer external ID
We're adding a new free text field to the organizer details screen called external id. This can be used in combination with a API or payment integration.
Besides the regular guest checkout, we'll now also offer the customer to create a password protected account to finish his purchase with. Once created he'll be able to use the same account for all his purchases within the same organization.
A flow property is available to enable/disable the guest registration option.
In the future these accounts will be used for more features like: purchase retrieval, discounts, subscriptions, gift cards, ...
The admin financial reports "payout summary" & "payout details" will now report on extra data:
- Distinction between online and offline revenue & refunds
- Clear indication of cancelled issues tickets & revenue
In addition the organizer reports "sale summary" & "sales details" now show:
- + Received ticket revenue
- - Invalidated ticket revenue
Organizer terms and conditions
We're adding a new section in the Design menu of the back-office that covers terms and conditions for organizers. Here it's possible to set additional terms and conditions specifically for the organizer. These will be added to the terms and conditions defined on your platform (if any).