1. Case List Navigation & Case Card Behavior Changes
Discussion focused on usability concerns with the current behavior in the STAC 3 case list.
Clicking the case number or defendant name currently opens the Case Card or Directory Card.
Users reported this workflow becomes cumbersome, especially on smaller laptop screens, courtroom workflows, and high-volume navigation scenarios.
Users moving rapidly between cases were unintentionally opening cards repeatedly instead of simply opening records.
Proposed behavior change: clicking the case number/name will open the case directly, while clicking the icon will open the Case Card or Directory Card.
2. Change Resistance & STAC 3 Adoption
The group acknowledged that workflow changes create resistance even when improvements are beneficial.
Comparison was made to the historic Client STAC → STAC Web transition, where similar frustrations were eventually overcome.
Discussion emphasized long-term gains including faster performance, docked editing windows, right-click functionality, multi-tab workflows, and real-time navigation without losing place.
Demonstration showed how STAC 3 allows docked edit windows while continuing navigation, unlike STAC 2 which consumed the entire screen during editing.
3. Upcoming Enhancements Mentioned
Missing Arrest Sub Type and End Offense Date fields in the wizard were acknowledged and planned for deployment.
Future collaboration topics will include document workflow improvements using variables, discovery code variables, and guided merge workflows.
Goal is to reduce manual editing, user confusion, and excessive navigation.
4. Persistent Filters & Add to List Behavior Discussion
Users raised concerns regarding persistent filters and persistent Add to List mode after logout/login sessions.
Discussion explained STAC is moving toward remembering user preferences and settings until users explicitly change them.
Examples discussed included filters, grid layouts, views, and list mode.
5. Search Box Persistence Across Cases
Users reported the search field clears when switching cases.
Example discussed involved searching document names across multiple cases.
Existing development ticket already created and planned for RC7.
Planned behavior is for search terms to persist while navigating cases, but clear after logout/login.
6. Add to List Complexity & Internal System Challenges
Detailed explanation provided regarding why Add to List functionality became difficult to maintain.
List functionality interacts with queries, filters, saved lists, case updates, dispositions, and dynamic records.
Complex interactions created maintenance issues, performance concerns, and inconsistent behavior.
Discussion emphasized that simpler workflows improve stability, maintainability, and performance.
7. Redaction Module Feedback
Users demonstrated inability to delete redactions directly.
Existing enhancement ticket already open.
Future improvements planned include deleting pages, adding stamps, and supporting multiple redacted versions.
Current STAC 2 limitations only supports a single redacted version.
8. Upload Center Window Position Reset
Users demonstrated that the Upload Center window resets position after each upload.
This creates repetitive workflow annoyance during bulk uploads and image management.
9. PDF Rotation / White Space Issue
Users demonstrated that rotating PDFs introduces additional white space and distorted formatting.
Long-term STAC 3 direction includes native PDF editing without requiring Adobe licenses or third-party software.
10. Embedded Word/Excel & Document Merge Philosophy
Discussion addressed embedded Excel spreadsheets in Word documents used for calculations and public records invoices.
STAC 3 editor is not intended to fully replicate Microsoft Word functionality.
CIP does not want to support macros, embedded Excel logic, or heavily customized Word behavior inside STAC.
Alternative approaches discussed included variables, calculated workflows, and dedicated public records functionality.
11. STAC 3 Editor Benefits Highlighted
Benefits discussed included faster merges, browser-based editing, version history, reduced Word integration issues, and elimination of licensing dependencies.
Large number of historical support calls involved Word merge failures, licensing problems, file association issues, and corrupt templates.
12. Additional Agency Training Offer
CIP offered individual circuit demos, recorded walkthroughs, and focused agency sessions.
Purpose is to assist with user adoption, transition support, and workflow understanding.
Q: What is changing with opening Case or Directory Card behvior?
A: Clicking the case number/name will open the case directly, while clicking the icon will open the Case Card or Directory Card. This change will reduce accidental card openings, improve navigation speed, and assist users working on smaller screens or in court.
Q: Will filters stay active after logout?
A: Currently under discussion. However, the goal is to maintain filters during the logged in session. Once a user logs out or opens a new session in another tab, the filters would be cleared.
Q: Why are users concerned about persistent filters?
A: Users may forget filters are active and mistakenly believe records are missing.
Q: Will search terms remain while switching cases?
A: Yes — planned for RC7.
Q: Will search persist after logout?
A: No — expected to clear after logout/login.
Q: Can I delete redactions currently?
A: Not fully yet — enhancement already ticketed.
Q: What future redaction features are planned?
A: Delete pages, multiple redacted versions, stamps, and expanded editing tools.
Q: Why are PDFs edited directly in STAC now?
A: To reduce dependence on Adobe, third-party licenses, and external tools.
Q: Does STAC 3 support embedded Excel spreadsheets in documents?
A: Not in the same way Microsoft Word does.
Q: Why is CIP moving away from advanced Word functionality?
A: Because macros and embedded logic create support issues, compatibility problems, and long-term maintenance challenges.
Q: What are the benefits of the STAC 3 editor?
A: Faster merges, browser-based editing, version history, no Word dependency, and reduced support issues.
Q: What is CIP’s overall message about STAC 3 right now?
A: The platform is entering a fine-tuning stage focused on workflow polish, user experience improvements, and real-world refinements.