Release Notes - 2024.12.11

Welcome to the latest One Model product release update. This article provides an overview of the  product innovations and improvements to be delivered on 11 December 2024, the last release of 2024. The next release will be on 8 January 2025 and you can find the 2025 release calendar here. 

One AI  

• One AI Assistant now includes the full Define | Design | Discover | Describe experience from Storyboards, allowing you edit charts and tables without needing to pin to a storyboard first. This enhancement means that in addition to the query structure, you can now modify the visual design, add or configure embedded insights like reference lines and forecasting, and add annotations. This update streamlines workflows, making it easier to prepare, design, and export visualizations. (ref 3604, 3616)
  
  
  
  
• One AI Assistant now supports the GeoMap visualization type, enabling creation and configuration of GeoMaps directly within the assistant. To render a GeoMap, a geographic dimension and the word “map” or “GeoMap” must be included in the prompt (e.g., “Show me headcount by location as a geomap”. Additionally, geospatial location dimensions must be configured and available in advance for the assistant to leverage this feature. (ref 3397)
  
  
  
  
• The Pin To functionality in the One AI Assistant has been updated. The Pin Result to... button is now located directly under the visualization block, making it more contextual to the result and the dialog box now overlays the insight visualization instead of replacing it, preserving the visual context. Additionally, when pinning to an existing storyboard, unshared Storyboards are displayed at the top of the list, aligning the behavior with other components. (ref 21392)
  
  
  
  
• Two new enhancements to Reference Lines provide greater customization and flexibility, facilitating greater data interpretation and decision-making:

1. 1. Percentile Reference Lines: Percentile Reference Lines can now be added to Basic Charts, offering more ways to analyze trends and visualize benchmarks. To add a Percentile Reference Line, select ‘Percentile’ as the Reference Line Type, specify the desired percentile (any value 1-99; e.g. ‘50’), customize the label if desired (labels default to the percentile value if left unchanged; e.g. ‘50th Percentile’), and update the color. Multiple Percentile Reference Lines can be added to a single chart and can coexist with static and average Reference Lines as well. (ref 3531)
      
      
      
      
   2. Blanks in Average Reference Lines: We've added the option to toggle whether blanks are treated as 0s or ignored in the calculation for Average Reference Lines. By default, this setting is toggled off, meaning blanks are excluded from the average calculation. When toggled on, blanks are treated as 0s and included in the calculation. This flexibility allows users to better align average calculations with their specific data context. (ref 3577)
      
      

• To improve the user experience when launching the EDA report, we’ve added a data loading spinner, providing a clear visual indicator that the report is loading. Additionally, a note stating, "Please note that the EDA report may take some time to load," has been included to set user expectations. These changes help reduce confusion during longer load times. (ref 3563)

Admins can now update the visualization type icon for their configured example prompts by changing the visualization type icon directly to the right of the example prompt in the One AI Configuration screen. Available icons include Bar Chart, Line Chart, Table, Kay Value, Pie Chart, and GeoMap, making it easier to align prompts with their intended visualization. (ref 3548)

User Experience Improvements

• We’ve updated the visualisation settings panel to display the Storyboard or Tile style background, ensuring a consistent preview experience. Previously, the background defaulted to white or the Main Contents Background, but now it reflects the intended tile style for improved visual accuracy. (ref 21145)
• We have added an indicator to help users identify which branding settings support gradient colors. Supported settings in 'Admin > Branding > Main Colours, Logo and UI Style' and 'Admin > Branding > Tile Style Templates' are now clearly marked. This makes it easier to apply gradients without trial and error warnings. (ref 21974)
• We have updated the behavior for table totals with no dimension: the custom total section will no longer be rendered in the Design tab for both basic and pivot tables. (ref 22082)
• We have updated the help text of the info icon when updating a chart title. (ref 22393)
• We have removed the role CanImportExportConfigurations as this functionality can only be accessed by One Model Users (ref 19902)
• We have improved the Define Design Discover Describe Panel to introduce horizontal scrolling when on smaller screen sizes (ref 21121)  
  
  

Minor Improvements & Bugs Squashed

• We have fixed an issue where the collapsed One AI Assistant in the header bar caused focus loss due to an invisible overlay, limiting user interactivity in certain areas of the screen. Users can now make selections without needing to retry. (ref 21687)
• We’ve addressed an issue where increasing table pagination caused rows to overflow outside the One AI Assistant container. Scroll bars have been introduced to keep the table contained within the panel. (ref 21663)
• We have improved responsiveness for One AI Assistant and Navigation Bar to ensure they now resize correctly on smaller screens and iPads. This improvement will prevent overlap or cutoff issues with icons. (ref 21719)
• We fixed an issue where Prophet forecasts would not generate if the input data lacked date values. The bug stemmed from the frontend sending empty date arrays that defaulted to the wrong data type, causing a crash. The front end now ensures date arrays are properly populated and typed, restoring full forecasting functionality. (ref 3683)
• We fixed a bug to enable the Metric Editor page to load even when there is missing data. (ref 22013)
• When users tried to access Users Page without permissions they were getting a loading indicator which was misleading as the page never loaded. Instead they will now get a 403 Forbidden error (ref 21905)