We are excited to announce the release of ConverSight web version 2.0.38.5, packed with a range of new features, enhancements and bug fixes. Here are the key highlights of this release:
New Features
Reports Beta
- Introducing Reports Beta: The Reports Beta feature offers a dedicated interface for creating and viewing periodic data reports, initially presented in a pivot table format with the option to explore alternative visualizations.
AI Workbench
- Manual Configurations in CsApp Updates: Users now possess the flexibility to modify or adjust manual configurations during CsApp updates.
- New CsApp Version 2: Custom components are now effortlessly integrated within CsApp, enhancing its functionality and versatility.
Data Workbench
- Dataset Reconfiguration Options: Users now have the ability to remove tables or columns while reconfiguring datasets. Prior to removal, a warning message will be displayed if the Column, Table or Connector used in any Custom Field.
- Connector Removal Option in Reconfigure Status: Users can now remove connectors in reconfigure status of the dataset.
SME Coaching
- Default Synonym Generation: Single-word column names now have default synonyms generated, matching the column name itself.
Enhancements
Athena
- Improvements to Athena Chat Suggestions: Enhancements have been implemented to refine suggestions within Athena Chat, enriching the user experience and optimizing interaction.
Data Workbench
- Enhanced Dataloading Scheduler Monitoring Screens: Detailed reports can now be thoroughly accessed within Dataset Schedules, offering a more comprehensive view of data insights.
Bug Fixes
Data Workbench
- Recent Activity Error Message Display Fix: Error messages were not appearing in the recent activity section during data loading. This issue has been resolved.
- Warning Message for Removing Connectors or Tables/Columns: Prior to removal, a warning message will be displayed if the Column, Table or Connector used in any Custom Field.
- Float Casting Discrepancy Resolution: Despite casting to float, values in the source database and our platform were different. This issue has been addressed.