Who is this article for?

Users and admins who want to learn more about the changes introduced in the latest release.

No elevated access or permissions are required.

Galileo 1.4 introduces powerful enhancements to data retrieval by enabling selective fetching of records based on creation or modification dates. This means you can now retrieve only the data that has changed within a specific time range—eliminating the need to reload entire datasets.

Key benefits

• Improved Performance: Load only what’s necessary—minimizing processing time and resource usage.
• Better Scalability: Efficiently manage growing datasets without compromising speed or reliability.
• Enhanced Efficiency: New views and indexes significantly reduce wait times for data access.
• Accurate Updates: Streamlined ETL processes ensure complete and consistent data with no gaps.

Technical changes

We've made several behind-the-scenes enhancements to improve your Galileo experience. These improvements work together to deliver faster response times, better system reliability, and enhanced data accuracy for all users

• Delta Change Implementation
  • Add created_date and modified_date fields to the dwanalytics and dwreporting schemas to Reporting, Audits, Documents and Risk.
  • See "Views & New Fields" section for details
• New Views
  • Introduced dwanalytics_report_form_section_field view for enhanced reporting capabilities in the form section.
  • Added dwanalytics_version_view to easily check your current Galileo version
• Performance Optimisations:
  • Enhanced database memory allocation for faster query processing and improved multi-user performance
  • Implemented read replica technology to support more concurrent users without performance impact
  • Added strategic database indexes across Reporting, Audits, Documents, and Risk-related tables for faster data searches and more efficient.
• Data Reliability:
  • Improved ETL processing to ensure data completeness - the system now only updates progress markers when operations are completed successfully, preventing potential data gaps
  • Enhanced data integrity controls to prevent duplicate entries
• Maintenance:
  • Deprecated certain Reporting, Audits and Documents views to optimize overall system performance (see "Deprecated Views" section for details)

Deprecated views

To ensure optimal performance and the best user experience, we recommend updating your reports and queries to use our enhanced replacement views.

What you need to do: Replace the deprecated views in your existing reports with the recommended alternatives listed below. For example, if you're currently using dwanalytics.audit_fact, please update to either dwanalytics.audit_fact_non_workflow or dwanalytics.audit_fact_workflow depending on your specific needs.

Recommended replacements

Fixes