To improve injection efficiency and performance, we are introducing a new approach to event creation, decoupling it from ticket injection. This change eliminates the issue of redundant event information being sent repeatedly without updates in TIXNGO.
What does this mean for you?
We have introduced a new set of API endpoints that allow creating, retrieving, and updating events independently of ticket operations.
...
| Info |
|---|
Once fully integrated with S-360, events will no longer be created during the same API call as ticket injection, boosting injection performance by reducing payload size and simplifying the backend flow. Therefore, until S-360 integration is completed, S-360 tickets injection will behave as of now. |
Improved Back-Office UX
Introduction of the "Create event" screen
If enabled, a new menu entry "Event Creation" will be visible for ADMIN and TIXNGO_SUPPORT back-office users, within "ORGANIZER" section.
...
Once the form filled, click "Create event". The event will be provisioned and you'll be redirected to the "Edit event" screen.
Introduction of individual action buttons to create activation, transfer and design rules
While capitalizing on the new "Edit Event" screen and standardization of tickets rules (activation & transfer as of now), organizers will be now able to create individual rules directly from the back-office.
...
By clicking "New transfer group", a new section will be displayed, allowing organizer to create a new transfer group.
How to activate this feature ?
"Event creation" screen will only be available for non S-360 customers and configured accordingly during the on-boarding.
Limitations
| Warning |
|---|
Due to parallel development stream with S-360 team, individual Event APIs are only available on TIXNGO. Full integration with S-360 to actually separate event creation from ticket injection will be available in next release ZUM V3. |
...