Improvements

• Incorrect Password Alert
  • Implemented a new feature that displays a user-friendly alert message when an incorrect password is entered during the log-in process, improving the user experience and providing clearer feedback.

Bug Fixes

• Border Line Fix
  • Resolved an issue where a border line was not displaying or was displaying incorrectly, ensuring proper visual separation and alignment.
• Storage Graph Axis Label Fix
  • Corrected a bug related to the axis labels on the storage graph, ensuring they now display accurate and correctly formatted values.
• Usage DBO Label Update
  • Updated the label for the Usage DBO (Data Browser Object) to reflect the correct terminology.
• Addressed several minor UI/UX bugs across the platform.

New Features

• Create Venue v2 Endpoint
  • A new API endpoint was created to allow for the creation of venues using the updated v2 Endpoints architecture. This provides a more robust and scalable way to manage venue data.
• Get Venues v2 Endpoint
  • A new API endpoint was implemented to retrieve venue data using the v2 Endpoints architecture, enabling more efficient data fetching and filtering.
• Add a new system field for Sponsor Category
  • A new field was added to the system to track and categorize sponsors, which will improve data organization and reporting.
• Edit Event Details for Ticket
  • Users can now directly edit Event details from the ticket view, which streamlines the workflow for managing tickets.
• Bulk Update Tickets feature
  • A new feature was introduced that allows for the simultaneous update of multiple tickets, which significantly reduces the time and effort required for administrative tasks.
• Assign Contact to Ticket without CRM requirement
  • The process for assigning a contact to a ticket has been updated. It is no longer a requirement for the contact to already exist in the CRM, which provides more flexibility.

Improvements

• Update v2 Endpoints for Controllers
  • The new v2 endpoints have been updated to ensure they function correctly as controllers, which improves their reliability and integration with other system components.
• Update the order parameter to sort_order for GET requests
  • The parameter used for sorting data in GET requests was changed from order to sort_order for better clarity and consistency across the v2 APIs.
• Separate queries for table data and counts to improve performance
  • The database queries for fetching table data and item total were separated to reduce the load on the server and improve the application's overall performance.
• Prevent reference_code sharing in group tickets
  • The reference_code has been removed from the group ticket flow. This is because the group ticket process uses a different creation query that generates multiple tickets, which makes it challenging to ensure a unique reference_code for each one. If you need to add a unique reference_code to a group of tickets, you can use the Update Ticket API after the group tickets have been created. This will let you assign a unique reference code to each ticket individually.
• Improve the QR code data density
  • We've improved the QR code data density by shortening the data embedded within the QR code. This makes the codes more scannable and reliable, ensuring they can be read more easily by devices.
• Sample Ticket Dynamic Data
  • A dynamic data used for sample tickets was added to be more representative and useful for testing and demonstrations.
• Tax Updates Alignment
  • The tax calculation and display logic for Event Sponsors and Event Expenses has been updated to align with the requirements of the Event Tickets. This change ensures consistent and accurate financial reporting across all event-related transactions.

Breaking Changes

• Renamed Event Venue Area to Event Pricing Division
  • The Event Venue Area table and its related fields have been renamed to Event Pricing Division.
  • We created new migrations for all of these updates to ensure no data is lost in the IIA environment.
  • For existing users, if you're using manual queries for event pricing data, you'll need to update the table and field names to align with the recent changes. Any existing code or integrations relying on the old naming convention will need to be updated.
• Removed Discounts on Events
  • The Discounts tab has been removed from the Events module. All related code and functionality for event-specific discounts have been deleted and will be moved to the Ecommerce module, allowing for global discount management across all services.

Bug Fixes

• We addressed various bugs to improve the module's stability and user experience, fixing issues with form buttons, UI display, data duplication, and a general TypeError.

New Features

• New field processing_fee on quote and orders.
• New field minimum_cart_value on discount.
• Added Payment Status and Shipping Status in Orders custom display fields.
• V2 API Endpoint Controllers.

Improvements

• Rename fields on import for better readability.
• Use product variant when adding a product on an item for a quote or order if Use Product Variant is enabled on the product.
• Order item list improvements.

Bug Fixes

• Missing Quote Company Email, Quote Company Phone Number on the list page of quote.
• Missing Order Company Email, Order Company Phone Number on the list page of order.
• Quote Date not being updated when generating PDF.
• Wrong item name displayed on the PDF.
• Phone number country code is being save along with the Phone number.
• Quote subtotal calculation fixed.
• Display Order Payment Status and Order Shipping Status Fields in custom column.
• Wrong date format of Order Date.
• Sale price not assigned to the order item when adding a variant on an order.
• Fixed 2 Shipping displayed in the display fields and added Discount field.
• Custom field File uploads not added to the created order.
• Custom field select data source multiple not showing the values.
• Wrong total values displayed on order list.

New Features

• API v2 Controllers are now accessible. Please refer to the documentation site for usage instructions.
• Introduced a new view for GraphQL. You can now view, create, edit, and delete your GraphQL queries.

Improvements

• Renamed "API Endpoints" to "Custom API Endpoints" for clarity.
• Custom API Endpoints created in different modules are now displayed.
• Removed the requirement for metadata for Custom API Endpoints to appear in the IIA. Note: Your endpoint must have a .json format to be shown in the IIA.
• Added a delete function for Custom API Endpoints.
• Removed Reports view. Its not functional and not related to Custom API Endpoints.
• Various UI improvements.
• Various improvements to v2 API documentation.

Bug Fixes

• Fixed an issue where the breadcrumb link for the home page was not working.
• Array payloads are now displayed correctly.
• Fixed an issue where all values in the sample request were enclosed in quotes.
• Various bug fixes.

Breaking Changes

• Removed the Archive and Restore functions from Custom API Endpoints. All previously archived endpoints have been restored.
• API Keys have been replaced by Authorization Policies.

New Features

• Ticket Pricing and Grouping
  • Added a new feature to define ticket pricing and grouping, allowing for more flexible event ticket management. This new feature introduces a more flexible and robust system for managing event tickets by redesigning the underlying data structure.
  • Redesigned Data Flow
    • The core of this feature is a conceptual change. The event_venue_area table has been reframed as a "Pricing Division" to better reflect its purpose in the new system. While the table name was not changed to prevent breaking changes, its functionality has been significantly expanded. Users still have the control how many people can avail the tickets.
    • A new "Pricing Division Tiers" table has been added to the database. This table allows for multiple price points to be associated with a single Pricing Division, giving event organizers the ability to offer different ticket prices (e.g., Early Bird, General Admission, VIP) within the same area.
    • To support this new model, several fields were added and deleted from the existing event_venue_area and event_ticket tables. IMPORTANT NOTE: Two new migration files were created to update the database schema, ensuring a smooth transition for existing data.
  • User Interface and Display
    • The ticket form has been updated with new fields and dedicated sections. A new accordion was also added to the drawer form to highlight the price, tax, and total details.
    • With the new fields introduced in the data tables, additional column display options have been added to the Events and Tickets list tables.
    • To ensure all users can see these new fields, a migration was created to reset the current column lists for all accounts. This ensures that the new display options are immediately available and align with the updated data structure.
  • New Integrations
    • We have also introduced 2 new row actions on the Tickets table for managing group tickets:
      • Edit Group
      • Delete Group
    • Additionally, a new feature has been added that allows you to change the type, division, and tier of existing tickets. When these changes are made, the tickets_remaining count is automatically updated across all related tables, including event, division event_venue_area, and event_pricing_tier, ensuring data consistency.
  • V2 API Endpoints
    • New V2 API endpoints for event tickets have been added to the system.
    • The new API-to-controller setup is now complete, ensuring that client-side data retrieval (via API) and server-side rendering (via controller) are handled with optimal efficiency.

Improvements

• Event and Ticket Management
  • Updated the Event's Details and Venue Tabs.
  • Added the ability to clear a field in the dropdown for an event form.
  • Added additional options for Ticket's Confirmation Status.
  • Added new search and filter options for the Tickets List table.
  • Added new fields to the available columns to display in the Tickets List table.
• Data and Integrations
  • Added an event in the event stream when deleting an Event.
  • The email address is now shown in the CRM Contact Fields data source.
  • Purchaser fields are now shown in the Ticket form.

Bug Fixes

• Event and Ticket Data
  • Fixed the issue with the total_tickets_sold field in the Event columns.
  • Corrected the Event's geojson data when editing.
  • Fixed the issue with Custom Fields datetime.
  • Fixed various "Type Error" issues.
• System and UI
  • Fixed the Attendee Company field toggle to a text box when not using a CRM Company.
  • Fixed the Paginated List Delete flow for both bulk and row actions.
  • Removed page and size parameters from the get_filter_options function which prevented some lists being displayed correctly.

Breaking Changes

• Table Updates
  • event_venue_area
    • Added
      • name
    • Removed
      • is_individual_ticket_enabled
      • individual_ticket_price
      • individual_ticket_price_2
      • individual_ticket_price_3
      • is_group_ticket_enabled
      • group_ticket_price
      • group_ticket_price_2
      • group_ticket_price_3
  • event_ticket
    • Added
      • reference_code
      • row
      • seat
      • event_venue_area_uuid
      • event_pricing_tier_uuid
      • price_includes_tax
      • tax_type
      • purchased_by_company_uuid
      • contact_company_phone_number
      • contact_company_phone_country_code
      • contact_company_email
  • event_pricing_tier (NEW)
    • uuid
    • event_uuid
    • event_venue_area_uuid
    • capacity_type
    • name
    • price
    • price_includes_tax
    • tax_type
    • tax
    • availability_start_date
    • availability_end_date

For further information about the Event Tickets object please see the API V2 Documentation at {{your_instance_URL}}/admin/api/events/event-tickets/overview