STAC 3 Collaboration Meeting Summary 2/11/26

STAC 3 Collaboration Meeting Summary 2/11/26

1. Upgrade Status & Deployment Coordination

After-Hours Upgrade Clarification

  • Hosted agencies do not need to update during business hours.
  • CIP performs upgrades after hours.
  • Upgrade requests must be submitted through the Helpdesk portal using the Classification=Release Update specifying:
    • Test vs Production
    • Restore requirements (if applicable)
  • Agencies are expected to:
    • Upgrade Test first
    • Validate
    • Then proceed to Production (typically next day)

2. Session Timeout & Login Error

  • Users receiving timeout/login errors after session expiration.
  • Error message unclear (possible 400/500).

Resolution

  • Session timeout controlled under:
  • Setup → Configuration → Security Options → Maximum Session Lifetime
  • Default: 30 minutes
  • Maximum: 720 minutes
  • Thomas to submit screenshot of error for review.

 

3. List Management – “Remove from List” Behavior Change

  • In STAC 2, users could remove items from any result list.
  • In STAC 3, “Remove from List” requires “Add to List” toggle to be enabled.

CIP Explanation

  • By design.
  • In STAC 2, every search implicitly created a server-side list, increasing memory usage.
  • STAC 3 treats:
    • Searches
    • Saved Lists
      As separate structures for performance efficiency.
  • Users must now intentionally create/manage lists.
  • No change planned at this time.

4. Document Merge & Error Display Issue

  • When rejecting a merged document:
    • STAC 2 shows full error message.
    • STAC 3 shows small corner notification; unreadable.

Status

  • Occurring in RC3 without latest patch.
  • Ticket requested.
  • CIP to investigate error rendering logic.

5. Charge Language Display

  • Display full charge language in case entry (as relied upon in STAC 2).

Discussion

  • Current implementation uses a static field.
  • Concern: charge language stored separately from official statute document language.
  • Risk: language drift if not updated in both places.
  • Ticket to be submitted.
  • CIP may explore displaying document-based language instead of static text.

6. Charge Sequence Editing – Major Discussion

Current STAC 3 Behavior

  • Users must create a new sequence when modifying a charge.
  • No option to “edit without new sequence” for standard users.
  • Administrative override function not yet implemented (but planned).

Agency Concerns

Agencies (SA12, SA19, SA14, SA5, etc.) raised:

  • Frequent clerical charge entry errors.
  • Placeholder charges used while awaiting statute updates.
  • Generic charges replaced with correct statute.
  • Need to correct sequence 0 without creating artificial history.
  • Data Transparency errors when incorrect sequence 0 reported.

CIP Position

advocated for:

  • Maintaining charge history for audit integrity.
  • Preventing silent edits that could:
    • Conflict with previously merged documents
    • Create discovery inconsistencies
    • Remove audit trail

Key argument:

History protects the office. Silent edits can create document inconsistency issues.

  • Administrative function will be implemented to allow corrections without new sequence.
  • Standard users will continue to create new sequences.
  • CIP to review:
    • Data Transparency reporting logic
    • Whether sequence 0 or latest Original sequence should be reported
    • Disposition filtering for incorrect charges

Further discussion to occur in follow-up session.

7. Image Viewing & PDF Concatenation

Ability to:

  • Select multiple images
  • Open as single PDF for review (without saving concatenated file)

STAC 3 already supports:

  • Print (temporary concatenation in browser)
  • Carousel preview navigation
  • Mixed file-type preview (Word, PDF, images)

Key Clarification

  • STAC 2 generated a persistent file when concatenating.
  • STAC 3 performs server-side temporary rendering.
  • Carousel preview does not generate stored file.

Potential Enhancement

  • Carousel limited to selected images only (currently entire folder).
  • Ticket suggested.

8. Subpoena Merge – Multiple Date Selection

STAC 2:

  • Allows date selection screen in subpoena merge that is applied to all relationships. 

STAC 3:

  • Defaults to most recent date.
  • Requires manual editing per recipient with no reference to future dates

Status

  • Known issue.
  • Ticket already exists.
  • CIP to review.

9. DOC vs DOCX Templates

Difference in handling .DOC vs .DOCX templates?

Answer

  • Both supported.
  • DOCX preferred:
    • Smaller size
    • More secure (non-binary format)
    • Better performance
  • Merging now server-side (faster than STAC 2).

Agencies encouraged to migrate to DOCX.

10. Case Wizard – Default Field Focus

New Case Wizard cursor does not land on first logical field (Open Date / Received Date).

CIP Response

  • Should always land on first visible field.
  • Agreed this is basic UI expectation.
  • To be adjusted.

11. User Adoption & STAC 3 Usage Metrics

  • Some agencies show minimal STAC 3 user logins.
  • Primarily administrators accessing system.

Circuit Concerns

  • User familiarity with STAC 2.
  • Users revert when encountering errors.
  • Reports not fully stable in some circuits.
  • Feature parity concerns.

CIP Position

  • STAC 3 core functionality is largely stable.
  • Broader usage helps surface real-world issues.
  • Not forcing STAC 2 shutdown yet.

offered to provide usage metrics to agencies.

Q&A Summary

Q: Do hosted agencies need to perform STAC upgrades during business hours?

A: No. CIP performs hosted upgrades after hours. Agencies should:

  • Submit upgrade requests through the portal.
  • Specify Test vs Production.
  • Upgrade Test first, validate, then proceed to Production.

Q: Do STAC 2 and STAC 3 need to be on the same version?

A: Yes. STAC 2 and STAC 3 must remain version-aligned to avoid functionality inconsistencies.

 

Q: Why are some agencies experiencing login or timeout errors?

A: Session timeout is controlled in:

Setup → Configuration → Security Options → Maximum Session Lifetime

  • Default: 30 minutes
  • Maximum: 720 minutes
    If error persists, submit a screenshot via ticket for review.

 

Q: Why can’t I remove items from a search result list like I could in STAC 2?

A: In STAC 3, users can still use the “Remove from List” option, but the List toggle needs to be enabled. 

Why this changed:

  • In STAC 2, every search created a hidden server-side list.
  • This increased memory usage.
  • STAC 3 separates searches from intentional saved lists for performance optimization.

No change planned at this time.

 

Q: Why does STAC 3 show merge errors in a small corner notification instead of a full message like STAC 2?

A: This is not expected behavior.
If occurring in RC3 without the latest patch, submit a ticket. CIP will review error rendering logic.

 

Q: Why must users create a new charge sequence when correcting a charge in STAC 3?

A: STAC 3 enforces sequence creation to preserve audit integrity and protect document consistency.

Silent edits can:

  • Conflict with merged documents
  • Create discovery inconsistencies
  • Remove audit history

 

Q: What if the charge error is purely clerical?

A: Agencies raised valid concerns about:

  • Placeholder charges
  • Statute corrections
  • Data Transparency errors when sequence 0 is incorrect

Resolution direction:

  • Administrative override function will be implemented.
  • Standard users must still create new sequences.
  • CIP reviewing Data Transparency logic (sequence 0 vs most recent vs disposed filtering).

Q: Can we select multiple images and open them as one PDF without permanently concatenating them?

A: Yes, partially.

STAC 3:

  • Uses temporary server-side rendering.
  • “Print” function concatenates for preview only.
  • Carousel allows multi-file navigation.
  • No permanent file is created unless user downloads.

 

Q: Can carousel preview be limited to selected images only?

A: Currently it previews the entire folder.
Enhancement request suggested – submit ticket.

 

Q: Why does STAC 3 default to the most recent subpoena date instead of allowing dropdown selection like STAC 2?

A: Known issue.
Ticket already exists. CIP reviewing workflow.

 

Q: Should agencies use DOC or DOCX templates?

A: DOCX is preferred.

Reasons:

  • Smaller file size
  • More secure (non-binary format)
  • Better server-side merge performance

Both are supported.

 

Q: Why doesn’t the Case Wizard cursor default to the first logical field?

A: It should.
This is basic UI expectation and will be reviewed.