CASES AI – Known Issues, Limitations & Enhancements (Workbench & AI Features)

Document Type: Knowledge Base – Product Overview
Audience: Internal Teams (Product, QA, Support, Implementation)
Last Updated: 2025-05-15
Contributors: Connor Bates, Martin Laycock, Stephen Beaton

The below was captured from the following recording:

Session 3 - Known Issues

TABLE OF CONTENTS

• The below was captured from the following recording:
• 1. Introduction
• 2. Known Issues & Limitations
  • 2.1 Batch Analysis on Canvases
  • 2.2 Table View vs. Card View (Merge Functionality)
  • 2.3 Testimony Matching Errors in Semantic Search
  • 2.4 Uncontrolled Project Save Behavior
  • 2.5 Limited Functionality in Document Page Entity View
• 3. Clarifications on Canvas Behavior
• 4. Recent & Ongoing Enhancements
• 5. Internal QA & Client Support Guidance
• 6. Q&A Tracker Reference
• 7. Summary

1. Introduction

This document outlines current known issues, user-facing limitations, and planned enhancements within the CASES AI Workbench and related AI functionalities. It is intended to assist internal teams in troubleshooting, client communication, and expectation management.

2. Known Issues & Limitations

2.1 Batch Analysis on Canvases

• Issue: Inconsistent behavior during batch document analysis.

• Cause: System may apply references or content from unrelated sources due to semantic matching logic.

• Impact: Users might see references from documents not contextually relevant (e.g., results for “Sally Sanders” pulling references from “Helen Chang”’s transcript).

• Status: Under investigation; improvements to chunking and source precision are planned for release.

2.2 Table View vs. Card View (Merge Functionality)

• Issue: Entity merge functionality is only available in card view.

• Limitation: Users working in table view cannot select and merge records.

• Workaround: Users must switch to card view to access merge controls.

• Enhancement: Logged as a future UI enhancement.

2.3 Testimony Matching Errors in Semantic Search

• Issue: The semantic search may match similar terms (e.g., “testified” vs. “testimony”) across unrelated sections.

• Cause: Loose matching rules in the underlying semantic model.

• Impact: Misleading references and noise in result sources.

• Status: Known issue. Precision filters under review.

2.4 Uncontrolled Project Save Behavior

• Issue: When AI-generated content (e.g., key points, summaries) is saved to a project, there is:

  • No prompt for folder or metadata selection.

  • No confirmation step.

• Behavior: Output is saved using the parent document name and inherits its metadata by default.

• Impact: Lack of granularity and potential confusion over document context.

• Enhancement: Feature request submitted to introduce folder and metadata selection before publishing.

2.5 Limited Functionality in Document Page Entity View

• Issue: From the document page, users cannot:

  • Use the three-dot menu.

  • Add entities to specific worksheets.

• Behavior: Only basic options (e.g., selecting checkboxes, DOCX download) are available.

• Impact: Users may prefer document viewer or transcript viewer, where full options are supported.

• Enhancement: Review and redesign of entity management from static pages under consideration.

3. Clarifications on Canvas Behavior

• Each canvas is associated with a specific set of documents.

• This limits the scope of entity identification and reference matching to only those documents within the selected canvas.

• Helps mitigate unexpected results but requires careful canvas setup by users.

4. Recent & Ongoing Enhancements

5. Internal QA & Client Support Guidance

• Be aware that document context leakage (semantic misalignment) may occur until tighter source control is implemented.

• Inform users that save behavior is automatic and does not allow folder/document renaming at point of save.

• Recommend using Document Viewer or Transcript Viewer for entity management tasks.

• For entity merging, advise users to switch to Card View.

6. Q&A Tracker Reference

• A shared spreadsheet of user questions (collated by James and San) is being maintained.

• Any new questions should be added to this document.

• Answers will be added and periodically reviewed by Product/Support (Connor Bates point of contact).

7. Summary

CASES AI’s Workbench and AI tooling are rapidly evolving, but some limitations currently impact usability and accuracy. Known issues are actively tracked, and enhancement requests have been logged for resolution. This document helps internal stakeholders communicate effectively with clients and prepare for upcoming fixes and feature releases.