Horizon Changelog

Click Follow to be notified when we update this changelog.

Horizon Release Notes 2.66.0

Features and Improvements

Fixed

• The ReplicateDeletes setting was set to false for the tables tblSessions and tblPricesAll to prevent delete operations from being replicated.

New

• Horizon now supports importing data files via SFTP and accepts both XLS and XLSX formats.
• The Import dashboard is now available to Horizon Super users who log in through CIM.

Group Booking

Group Booking Order

Company

Group Booking Type

Group Booking Sub Type

Group Booking Venue

Third Party Venue

Horizon Release Notes 2.65.0

Features and Improvements

Fixed

• The "Stream" navigation items now display correctly within their respective category.

New

• The following fields were added to the Cinema_Screen view in Horizon.
  Screen HO Code
  Screen HO Number
• A new dashboard named "React Surveys" has been added. There is a new feature wherein clients will be asked to respond to a survey after an order/watching a movie. This 'React surveys' dashboard displays the survey results. It includes measures and KPIs such as 

  Click through rate
  Completion rate
  Film ratings graph
  Intent to watch graph
   

• The consumer now handles the logic to compare the LastReplicationMessageSequenceNumber with the LastReceivedMessageSequenceNumber, enabling it to request missing messages or trigger a full table reupload when necessary for Database Restoration Move Sequence mismatch validation.
  
   
• Super/Admin users can now view, edit, and manage all dashboards and tenant-specific objects in Horizon, including private items, with full permissions to change access and ownership.
  
   
• Admins can now set Horizon’s starter dashboards (owned by VISTA) to Private and assign viewer access to selected users, helping restrict visibility where KPIs differ or sensitive data is involved. This is available via the existing Change Permissions menu.
  
   
• Web Payments Module (WPM) has been added as a Horizon source through the tblWebPaymentHistory table. The same table from Vista Connect source already exists in Horizon.
  
  A new feature flag, replicate WebPaymentModuleData, has been introduced to control the source of data replication for tblWebPaymentHistory. When set to false (default), the table is replicated from Vista Connect, otherwise, the table is replicated from the Web Payment Module.
  
  Prerequisites:
  To support data replication from WPM, customer needs to
  1. Upgrade the Horizon producer to 2.65 or higher
  2. Have the WPM v3.1.0 or higher
      

Producer only changes

• In Horizon Producer, WPM source databases now utilize managed identity access for improved security by eliminating the need for passwords in connection strings.
• Excessive log generation has been fixed, preventing logs from consuming excessive storage space.
• A fix has been implemented to resolve an issue where the sp_flush_CT_internal_table_on_demand stored procedure was failing to execute due to insufficient permissions. The calling stored procedure has now been updated to execute as a db_owner, ensuring it runs successfully with the required privileges.

Data Model Changes

• The following views have been added to the data model, to provide session pricing data from Vista Connect.
  • Session Ticket Price Link
  • Ticket Price
  Pre-requisites
  • Customers must have Vista Connect version 5.0.8.x or above to access these views.
  • This feature requires the setting CONSISTENTPRICECARDCODE to be set in Vista (visWebLoader.ini), to ensure consistent price card codes are returned.
    
    

  Table	Previous version name	Current version name	Type	Action
  Session Ticket Price Link		Session Ticket Price Link	Table	New
  Session Ticket Price Link		Head Office Id	Column	New
  Session Ticket Price Link		Record Type	Column	New
  Session Ticket Price Link		Session Id	Column	New
  Session Ticket Price Link		Session Ticket Price Link Id	Column	New
  Session Ticket Price Link		Site Id	Column	New
  Session Ticket Price Link		Source Database Id	Column	New
  Session Ticket Price Link		Source Type Id	Column	New
  Session Ticket Price Link		Ticket Price Group Code	Column	New
  Ticket Price		Ticket Price	Table	New
  Ticket Price		Area Category Id	Column	New
  Ticket Price		Head Office Id	Column	New
  Ticket Price		Record Type	Column	New
  Ticket Price		Site Id	Column	New
  Ticket Price		Source Database Id	Column	New
  Ticket Price		Source Type Id	Column	New
  Ticket Price		Ticket IsAvailableOnKiosk	Column	New
  Ticket Price		Ticket IsChild	Column	New
  Ticket Price		Ticket IsComp	Column	New
  Ticket Price		Ticket IsPackage	Column	New
  Ticket Price		Ticket IsRedemption	Column	New
  Ticket Price		Ticket Price Gross	Column	New
  Ticket Price		Ticket Price Group Code	Column	New
  Ticket Price		Ticket Price Id	Column	New
  Ticket Price		Ticket Price IsDynamicPricing	Column	New
  Ticket Price		Ticket Price Net	Column	New
  Ticket Price		Ticket Price Sort Primary	Column	New
  Ticket Price		Ticket Price Sort Secondary	Column	New
  Ticket Price		Ticket Price Surcharge Gross	Column	New
  Ticket Price		Ticket Price Surcharge Net	Column	New
  Ticket Price		Ticket Price Tax 1	Column	New
  Ticket Price		Ticket Price Tax 2	Column	New
  Ticket Price		Ticket Price Tax 3	Column	New
  Ticket Price		Ticket Price Tax 4	Column	New
  Ticket Price		Ticket Type Id	Column	New
  Ticket Price		Ticket Type Name Alternative	Column	New
  Ticket Price		Ticket Type Name	Column	New

• The following views were added to Horizon.
  Survey
  Survey Page
  Survey Question
  Survey Response
  
  Survey Question Response
   
  Pre-requisites
  Customers must have Vista Connect version 6.9.0 or above to access these views.

  Table	Previous version name	Current version name	Type	Action
  Survey		Survey	Table	New
  Survey		Head Office Id	Column	New
  Survey		Record Type	Column	New
  Survey		Site Id	Column	New
  Survey		Source Database Id	Column	New
  Survey		Source Type Id	Column	New
  Survey		Survey Code	Column	New
  Survey		Survey Creation Date Time UTC	Column	New
  Survey		Survey Id	Column	New
  Survey		Survey Title	Column	New
  Survey Page		Survey Page	Table	New
  Survey Page		Head Office Id	Column	New
  Survey Page		Record Type	Column	New
  Survey Page		Source Database Id	Column	New
  Survey Page		Source Type Id	Column	New
  Survey Page		Survey Id	Column	New
  Survey Page		Survey Page Code	Column	New
  Survey Page		Survey Page Display Priority	Column	New
  Survey Page		Survey Page Id	Column	New
  Survey Question		Survey Question	Table	New
  Survey Question		Head Office Id	Column	New
  Survey Question		Record Type	Column	New
  Survey Question		Source Database Id	Column	New
  Survey Question		Source Type Id	Column	New
  Survey Question		Survey Page Id	Column	New
  Survey Question		Survey Question Code	Column	New
  Survey Question		Survey Question Display Priority	Column	New
  Survey Question		Survey Question Id	Column	New
  Survey Question		Survey Question Max Rating Scale	Column	New
  Survey Question		Survey Question Min Rating Scale	Column	New
  Survey Question		Survey Question Number Of Films	Column	New
  Survey Question		Survey Question Response Type	Column	New
  Survey Question		Survey Question	Column	New
  Survey Question Response		Survey Question Response	Table	New
  Survey Question Response		Film Id	Column	New
  Survey Question Response		Head Office Id	Column	New
  Survey Question Response		Record Type	Column	New
  Survey Question Response		Source Database Id	Column	New
  Survey Question Response		Source Type Id	Column	New
  Survey Question Response		Survey Question Id	Column	New
  Survey Question Response		Survey Question Response Code	Column	New
  Survey Question Response		Survey Question Response Id	Column	New
  Survey Question Response		Survey Question Response Last Responded Date Time UTC	Column	New
  Survey Question Response		Survey Question Response Rating Scale Response	Column	New
  Survey Question Response		Survey Question Response Sequence Number	Column	New
  Survey Question Response		Survey Question Response YesNoUnsure Response	Column	New
  Survey Question Response		Survey Response Id	Column	New
  Survey Response		Survey Response	Table	New
  Survey Response		Head Office Id	Column	New
  Survey Response		Record Type	Column	New
  Survey Response		Source Database Id	Column	New
  Survey Response		Source Type Id	Column	New
  Survey Response		Survey Id	Column	New
  Survey Response		Survey Response Code	Column	New
  Survey Response		Survey Response Creation Date Time UTC	Column	New
  Survey Response		Survey Response Expiry Date Time UTC	Column	New
  Survey Response		Survey Response Id	Column	New
  Survey Response		Survey Response Loyalty Membership Id	Column	New
  Survey Response		Survey Response Status	Column	New

Horizon Release Notes 2.64.0

Features and Improvements

Fixed

• In the Dashboard, the third-party data source is now displayed as online by default to avoid confusion caused by its previous permanent offline status.
• We have now separated dashboard admin permissions by introducing a new role called "Horizon_Discover_Can_Manage_All_Objects" and a corresponding AAD group name
• In the previous version of Horizon,  the property MinReplicationIntervalInSecondsForOccasionallyChangingTables was set for the below two tables  which caused these tables to be updated hourly. In this release, that property is removed for these two tables. Now the tables are replicated in every 10 seconds.

• Upon creating a new dashboard in Horizon, selecting a data source and hitting the Create button now correctly navigates to the dashboard editor for immediate editing.

• Replication of Delete Permanently Removed for following Loyalty and VGC tables.

New

• In this release, we’ve enhanced the performance of the following dashboards to ensure faster load times and a smoother user experience

Producer only changes

• Feature: Optimise Change Tracking
  Horizon producers utilise SQL Server Change Tracking to detect changes in the source database. By default, the Change Tracking retention period is set to 30 days, after which tracking data is automatically cleaned up. This can be problematic for databases with storage constraints.
  
  With this release, we are introducing support for manual Change Tracking cleanup. This feature can only be enabled on SQL Server versions later than 2014. Once enabled, the retention period can be set as low as 1 day. Horizon producers can then automatically trigger cleanup after confirming that all tracked changes have been successfully sent to Horizon. This provides better control over storage and improves data management efficiency.

• Improvement: Detect on producer side when the source DB is restored when the producer is running
  If the replicated DB is restored while the producer is running, the producer now detects it immediately, stops replication, and re-initiates a handshake to prevent downstream issues.

Horizon Release Notes 2.63.0

Features and Improvements

Fix

• The last updated field in the transaction and transaction payment tables is now updating correctly with new values. The missing historical values have been populated with the current date and time.‘LastModifiedHorizonUtc’ Field in cognetic_data_transaction and cognetic_data_transactionPaymenttype tables
   
• Improved security for caching Discover Query by validating cache keys during cache misses. This ensures that the correct permissions are used when retrieving and storing data, preventing users from accessing incorrect information due to mismatches between cached permissions and those in the database.

New

• Ability to Import data from external sources and to create data sources for dashboard usage.
• Discover API has been improved to add more functionality to manage user access to Discover Objects.

Horizon Release Notes 2.62.0

Features and Improvements

• No changes.

Horizon Release Notes 2.61.0

Features and Improvements

Fix

• Further performance enhancements have been made to the calculation of post-sale ticket value adjustments in Horizon. This is ongoing, and additional improvements to the performance of this process will be made in future releases.

Data Model Changes

New

• Price Book Detail was added to Horizon’s Cinema data model, allowing analysis of Item pricing at Sites across different dates and times.
• Views have been added and updated to provide detailed information of Client Orders from Vouchers & Gift Cards, including orders made through the client portal.
• Voucher Client Order History and its child views provide a history of changes to an order and communications with the client.
• Voucher Delivery Method and Voucher Payment Method provide details of how the order was paid for and sent to the client, respectively.
• Voucher Stock Order can be used to link client orders with any stock creation transactions, such as ordering new physical vouchers or generating new electronic vouchers.

Version 2.60.0

Overview

This release of Horizon contains a number of new views and fields in the data model, along with bug fixes and performance enhancements.

Features and Improvements

Further performance enhancements were made to the calculation of Adjusted Box Office values, as configured in Post Sale Ticket Value Adjustments in Head Office. Performance of these calculations continues to be monitored, and further enhancements will be made as required.

Data model changes

Loyalty Balance Type Earning Override was added, allowing points earning configuration to be analyzed.

Voucher Client Order Detail has been added to allow the contents of client orders to be reported.

Where tickets are scanned as patrons enter and/or leave the cinema, the Session Entry Status view allows reporting on the current entry status of each ticket.

Site Daily Status contains the status of each date at each Site, as determined by the open and close of day process in CashDesk.

• Note that Daily Cash Journal data, generated at cinema at the same time the day is closed, may not be immediately available in Horizon when the day is closed. DCJ data in Horizon is replicated from Head Office, so this will only be available in Horizon after a successful HO Upload has completed after the day is closed.

Voucher Stock records were incorrectly mapped to Client Orders. This incorrect mapping column was removed and a new field, Client Order Detail Id, was added, allowing the vouchers to be correctly linked to the client orders.

Version 2.59.0

Overview

This release of Horizon adds some additional Loyalty views to the data model.

Features and Improvements

• When Site-level security is enabled, users are no longer able to select a Head Office where they have no permitted Sites when loading a dashboard.

Data model changes

• Where an item is configured to be received with another Item when making Purchase Orders, the “Received with Item Id” field in the Item view contains the ID of the second Item.
• Loyalty Cinema Types, Format Class and Sales Channels were added to the model.

Version 2.58.0

Overview

This release of Horizon adds fields to help with integrations that read from the Loyalty views.

Data model changes

• Last Modified Datetime columns have been added to several Loyalty views, to allow incremental changes to be more easily identified.

Version 2.57.0

Overview

This release of Horizon has enhancements to Site-level security, along with the addition of Holdover Sheet, stock balance and POS operator logs to the data model.

Features and Improvements

• Improvements have been made to Horizon’s handling of Site-level security, which allows restriction of which Sites’ data each user has access to. The behavior is unchanged, but performance should be improved.
• A new version of the analysis schema, analysis_en_norls, has been added to allow queries to be written over the full data set, ignoring Site-level security settings. This schema allows SQL users to create queries to power circuit-wide dashboards for all users, even if they are restricted to a subset of Sites for other dashboards. It also allows more performant queries to be written in environments that have Site-level security enabled – additional information on this and other tips for writing performant queries in Horizon can be found here.
• The current member count KPI on the Loyalty Memberships dashboard was displaying incorrectly for Horizon environments with multiple Head Offices. This has been corrected.

Data model changes

• Holdover Sheet data from Film Programming is now available in Horizon. This includes the Holdover Sheet header table, the film bookings assigned to each holdover sheet, and Planning Policy information used to instruct cinema managers on the number and timing of sessions.
  NOTE: Replication of Holdover Sheet data is not enabled by default for all customers. If you have Film Programming and want to enable this data in Horizon, contact your Vista representative.
• A Stock Balance view has been added, which contains close of day stock balance for Items at each Cinema.
  NOTE: This data is taken from Head Office, so HO uploads of concession transactions must be enabled at Cinema for it to be available in Horizon.
• POS User Logs have been added to Horizon, allowing for actions taken by POS operators to be reported on.
• POS Session Payment Groups have been added to Horizon, showing the expected and cashed-up value of each payment group in a POS Session. This allows for detailed reporting of cashier variances.
• Calculation of the Session Time Block that is assigned to a session was not properly excluding inactive or deleted time blocks. This has been fixed, and all sessions should only be assigned to valid time blocks.

Version 2.56.0

Overview

This update to Horizon adds new Loyalty fields and views for better membership reporting.

Data model changes

• The Loyalty Member Group view was added, allowing reporting of recognition earning and use by different subsets of members.
• Fields were added to various Loyalty views, as listed in the table below.

Version 2.55.0

Overview

This release of Horizon adds a number of views and fields to the data model to meet custom reporting requirements.

Data model changes

• Cinema Screen Attribute Link view has been added, connecting Cinema Screen records with the Attributes assigned to them.
• Screen Capacity value has been added to the Cinema Screen view. Note that this value is taken from the Head Office definition of the screen, so is only available if the Head Office and Cinema records are correctly linked.
• Sales Tax Id has been added to the Item view, containing the default sales tax applied to each Item in Head Office, or at Cinema if the Item record was created there.
• Item Class Code has been added to the Item Class views, containing the identity of the records in Head Office, or at Cinema for Item Classes created there.