1. Score Sheet Import Behavior

• In STAC 2:
• Importing a score sheet:
• Retains current case values (judge, offense date, primary charge)
• Pulls prior case charges as additional offenses
• In STAC 3:
• Import behaves like full duplication
• Imports:
• Old judge
• Old offense date
• Old charges

• Increased manual work:
• Users must update multiple fields after import
• Significant inefficiency in:
• Smaller circuits
• High repeat-defendant workflows

CIP Explanation

• Current behavior is by design
• “Import” in STAC 3 = duplicate score sheet

 Not a template-style import like STAC 2

If behavior changes:

• Must determine:
• What data is retained (current case)
• What data is imported (prior case)
• Risk of:
• Duplicate charges
• Incorrect offense mapping

 Status

• Under review by CIP
• Not planned for next release
• Future redesign likely

2. Copy/Paste Behavior Change (Upcoming Release)

 Change Announced

• Paste will be DISABLED when editing records
• Paste will ONLY be available when:
  Creating new records

 Applies To

• Events
• Relationships
• Addresses
• All forms/screens

 Current behavior causes:

• Data inconsistencies
• Validation conflicts
• Overwriting of key fields

 CIP Position

 Better to:

• Create new record
• Preserve history
• Maintain data integrity
  
  

 3. Copy/Paste Session Limitation (Clarification)

1.  Copy/paste works ONLY within same session/tab

Example

• Case opened via report link → new tab
• Paste option will NOT carry over

Explanation

• Each tab = separate session
• Clipboard is session-based

4. Microsoft Authentication (Azure / Entra Integration)

• STAC supports:
• Microsoft login (SSO-style)
• Traditional username/password

Requirements

• User must:
• Be marked as External Authentication
• Have matching email in:
• STAC
• Microsoft 365

Key Setup Components

• Client ID
• Tenant ID
• Secret (expires – must track)

Critical Requirements

• Must run under:
   HTTPS
   Will NOT work under HTTP

Behavior

• First login:
• Microsoft authentication screen
• After login:
• Token returned → seamless access

Flexibility

Can mix:

• Authentication method (Microsoft)
• Email provider (SMTP / Google / Microsoft)

5. Microsoft Email Provider – Key Limitations

1. “From Name” Limitation

• Microsoft Graph:
• Does NOT allow custom “From Name”

• Email shows:
• Microsoft account name
• NOT:
• Agency name from STAC

Status

• Reported to Microsoft
• Not a STAC-controlled behavior

2. Calendar Sync Issue (Provider Change)

• Calendar events use:
• Provider-generated hash

When switching providers:

• Old hash ≠ new provider
• Cancel/update emails fail 

Impact

• Temporary calendar inconsistencies
• Resolves over time as new events are created

6. Portal / Authentication Troubleshooting Insight

Common Issue Identified

• Login failures due to:
• Mismatched email between:
• STAC user record
• Microsoft account

Resolution

 Ensure emails match exactly

7. Case Entry – Missing Offense End Date

• STAC 3 does NOT include:
• Offense End Date field (present in STAC 2)

Workaround

 Use Required Events

• Configure event to:
• Capture end date
• Populate charge data

Status

• Under review
• No immediate change planned

8. Class Field Placement in New case Wizard

• STAC 2:
• Field appears early in workflow
• STAC 3:
• Located on Details tab (later screen)

 Request

• Move to earlier step

 CIP Response

• Will NOT move to page 1
• Future plan:
• Configurable required fields by case type

9. Required Events – Reopen Scenario Limitations

 Issue

• Reopen scenarios vary:
• VOP Arrest
• NTA VOP
• Motion reopen
• Cannot:
• Dynamically require events based on reopen type

 Current Limitation

• Required events only tied to:
• Case type (not scenario/type)

 Status

• Enhancement acknowledged
• No near-term solution

10. Field Visibility / UI Customization Request

 Issue

• Users entering unnecessary data
• Need ability to:
• Hide fields during case entry

 Current State

 Not supported

 Future Direction

 Planned after:

• System structure stabilizes
• Full UI finalized

Q&A

Score Sheets

Q: Why does score sheet import bring over old case data?
A: Because STAC 3 import functions as a full duplication, not a template-based import like STAC 2.

Q: Will this behavior change?
A: Under review, but no changes expected in the immediate next release.

Copy / Paste

Q: Can I paste data into an existing record?
A: No (upcoming change). Paste will only be allowed when creating new records.

Q: Why is paste being removed for edits?
A: To prevent overwriting data, validation issues, and inconsistent records.

Q: Why doesn’t paste work between tabs?
A: Copy/paste is session-based. Each tab is a separate session.

Microsoft Authentication

Q: What is required for Microsoft login?
A:

• External authentication enabled
• Matching email in STAC and Microsoft

Q: Can we use Microsoft login and SMTP email?
A: Yes. Authentication and email providers can be different.

Q: Does Microsoft authentication require HTTPS?
A: Yes. It will not work over HTTP.

Microsoft Email

Q: Why is the agency name not showing in emails?
A: Microsoft Graph overrides the “From Name” with the account name.

Q: Is this a STAC issue?
A: No. This is a Microsoft limitation.

Calendar Issues

Q: Why are calendar cancellations failing after switching providers?
A: Because provider hash values change, and old events cannot be matched.

Case Entry / Fields

Q: What happened to Offense End Date?
A: Not included in STAC 3. Use required events as a workaround.

Q: Can we move fields like “Class” earlier in the wizard?
A: Not currently. Future customization may allow this.

Q: Can we require different events based on reopen type?
A: No. Required events are currently only tied to case type.

Customization

Q: Can we hide fields during case entry?
A: Not currently. Planned for future enhancement.