STAC 3 Refinement Phase & User Feedback Focus

Wlad explained that STAC 3 has largely reached feature parity with STAC 2, with only a few remaining code/configuration screens still pending conversion. Because of this, CIP is now shifting focus toward usability refinements and workflow optimization based on live agency feedback.

• CIP acknowledged that some STAC 3 features originally appeared beneficial during demos and development but are now proving inefficient or disruptive in daily workflows.

• The collaboration meetings are now intended to focus heavily on workflow refinement, usability concerns, performance improvements, and reducing repetitive navigation friction.

• CIP intends to use community board voting and broader participation to help prioritize future enhancements.

Case List & Case Card Navigation Improvements

Current Problem Identified

• Clicking directly on the case number or defendant name currently opens the Case Card instead of switching directly into the case.

• Users working quickly often unintentionally open the Case Card repeatedly.

• This becomes especially problematic on laptops and during courtroom use.

Planned Fix:

• Clicking the case number will directly open the case.

• Clicking the defendant name will directly open the directory.

• The Case Card functionality will remain available through the icon next to the case number/name.

Dropdown, Code Entry, & Search Workflow Improvements

Discussion About Code-Based Data Entry

• Experienced users who already know event and image codes find autocomplete and search-heavy dropdown behavior disruptive.

• Additional tab stops and magnifying glass buttons slow down keyboard-based workflows.

• CIP plans to preserve search functionality while streamlining keyboard navigation for advanced users.

Automatic Search / Autocomplete Preference Discussion

Current Behavior

• STAC automatically displays matching records as users type case numbers, names, and directory information.

User Concerns

• Some users find real-time suggestions distracting during rapid data entry.

• Long identifiers like Social Security Numbers become difficult to enter cleanly.

Proposed Solution

• CIP is considering making autocomplete behavior a user preference.

Search Behavior & Keyboard Shortcuts

Enter Key Search Functionality

• Rafael demonstrated that pressing Enter automatically triggers searches throughout STAC 3.

• This behavior applies to case searches, directory searches, and search panels.

STAC 3 Performance & Bigger Picture Discussion

Improvements Highlighted

• Faster screen loading

• Dockable/movable windows

• Better multi-screen support

• Enhanced responsiveness and grid functionality

Screen Customization Philosophy & AI Concerns

Customization Discussion

• CIP is working on restoring portions of STAC 2 customization functionality.

• Wlad explained that excessive field repurposing creates problems for future AI functionality and long-term supportability.

Grid Filtering vs Traditional Search

Grid Filtering Benefits

• Multi-column filtering

• Include/exclude logic

• Dynamic filtering

• Contains/does-not-contain searching

User Queries & Search Configuration Discussion

Key Points

• Agencies can rename, reorder, disable, and manage searches and user queries.

• User queries displayed in search screens can only contain the “Logged In User” argument.

Relationship Structure & Reporting Complexity Discussion

Current Relationship Challenges

• Multiple current attorney relationships complicate reports, dashboards, automation, and AI logic.

• CIP recommends maintaining only one “current” attorney relationship per case.

Upload Center Copy/Paste Functionality

• reported missing clipboard buttons in the Upload Center.

• CIP acknowledged the omission and requested a helpdesk ticket.

New Case Template Retrieval Follow-Up

• User asked about the Retrieve Template functionality.

• CIP confirmed the feature remains on the roadmap.

Q&A 

Q: Why is CIP changing the Case Card behavior?

A: Users frequently and unintentionally open the Case Card instead of switching directly into cases. 

Q: Will autocomplete become optional?

A: Potentially. CIP is considering preference-based behavior.

Q: Why doesn’t CIP want unlimited customization anymore?

A: Excessive field repurposing creates support issues and undermines future AI-driven functionality.

Q: Is the “Retrieve Template” feature still planned?

A: Yes. It remains on the development roadmap.