• the next version will be published Monday 1/26 (STAC + STAC 3).
• This release is expected to correct many of the smaller issues previously discussed.
• Some agencies intentionally waited for this release instead of upgrading to RC2.
  
• The Upload Center and Linked Folders that require the new STAC tool will be available in this version. However, it is going to be rolled out per Agency and we will start with the hosted agencies. 

• Next week:
  CIP will hold a large group meeting with all agencies / both STAC 2 and STAC 3 users.
• Purpose: review the new release and discuss impacts because the release includes changes for STAC 2 and STAC 3
• Following week: regular STAC 3 Collaboration Meeting resumes.

• Wlad encouraged agencies to complete upgrades between now and the next regular collab.
• CIP offered to assist with upgrade issues.

• Reported misdemeanor diversion payments entered in STAC 3 were not appearing on their diversion report.
• STAC 2 entries were appearing correctly.
• Question raised: Do STAC 3 tables update overnight?

• STAC 2 and STAC 3 share the same database
• Data is real time
• There are no overnight updates for report tables (for normal data entry)

• reviewed the case record and found the payment was not actually added as a payment record.
• In STAC 3:
• Diversion record entry exists
• Payments must be added using Right-Click → Add Payment
• Once payment is entered correctly, reporting works as expected.

• noted this “Right-click add associated info” concept applies to other areas where users add supplemental/complementary data, such as:
• Diversion payments
• Score sheet variables/manual actions (depending on feature)

• Asked whether Directory Compressions now run overnight in STAC 3.

• Confirmed: Yes — Directory Compression runs overnight in STAC 3.
• Reason: Performance optimization.
• Compression triggers massive updates throughout the database
• Running immediately (real time) can slow down system performance significantly

• CIP understands the tradeoff: users often expect immediate updates.
• Team is still evaluating better ways to improve performance while meeting workflow expectations.

• Request: Allow users to unrelate an officer from an agency directly from the officer’s directory card.
• Goal: avoid needing to:
• open directory record
• go to Relationships tab
• right-click/remove relationship

• a user request: Right-click → Print Note (single note).

• reviewed likely expected behavior:
• If printing is needed, a report is the most consistent/controllable method.
• Printing one note without context might not be useful unless formatting includes headers/case context.

• CIP suggested this is best handled via a tab report that prints:
• selected note(s)
• with appropriate case headers/metadata

• Asked about creating brand-new notifications in STAC 3 (division chief wants to send notifications to staff).

• l asked for details: What kind of notification is he trying to send?
• emphasized:
• Many internal tasks should be handled as a Request workflow rather than ad-hoc notifications.
• They want to avoid building another “communication channel” in STAC that duplicates existing tools (Requests, Teams, etc.).

• Reported a scenario where a “View Case” field/link was not wrapping and forced users to resize the case card.
• She could not reproduce live and needs to confirm where the issue occurs (possibly a specific notification type).

• Submit a ticket once the exact location/notification type is confirmed.

• Question re-raised: notification currently links to the “original” case, can it also link to the new case?

• CIP recommends this was previously discussed and remains not recommended due to confusion risk.
• CIP considers the notification purpose to be a “heads-up” alert; users can locate the new case via:
• search
• caseload User queries
• directory lookup

• asked if the Directory → Cases tab could support:
• multi-select cases
• right-click → Open selected

• Cleanup scenario: a directory was entered incorrectly (example: Starbucks entered as “Other” instead of “Business”)
• uses the directory case list to identify impacted cases and correct relationships.

• recommended avoiding directory case list navigation for bulk fixes.
• Instead:
• go to Cases
• run a Query filtered by Directory
• optionally filter by Relationship Type
• then fix relationships directly from the case results list

• Described 2 problems when editing directory entries:

1. After selecting a new Directory Type (keyboard selection), the field loses focus, forcing the user to click back into it.
2. Changing a directory type from Other → Business does not automatically update Directory Category as expected (STAC 2 behavior).

• Confirmed this appears to be an issue and requested a ticket.
• Requested ticket submission so the team can track progress and follow up.
  
• These issues will be corrected in RC-3

• requested an “Open in new tab” option in the Images tab.
• requested a ticket so it can be tracked.

• death certificates
• certified convictions
• documents relevant to a person (not only one case)

• Users upload to case images, then must:
• download the file
• go to directory
• re-upload it as directory image

• raised duplication and long-term organization concerns:
• duplicate records in different locations
• risk of one being deleted while the other remains
• confusing file lifecycle management

• CIP agreed to review further and asked for a ticket.
• noted configuration options may exist (purge behavior by image type), but CIP acknowledged the workflow concern and agreed it’s worth discussing across agencies.

•  reported users again asked for wrapping in the Name column on case lists (especially while in court) so they can shrink columns but still see full names.

• CIP believes there may already be a ticket, but asked user to submit another if needed so it can be added to backlog.

• Encouraged all agencies to use/engage with the Help Desk Community section for:
• shared workflow ideas
• suggested best practices
• discussion topics needing broader input
• Noted postings recently and had little/no engagement.

• reported that in STAC 3, assigning a signature image produces:
• File not found
• error when right-clicking to set signature

• confirmed this is a known issue in older versions and was corrected in RC-2.
• User was not running the newest version (not RC2).

• explained:
• Profile image and Signature image must be separate records
• The system blocks trying to mark a profile image as a signature
• the error messaging may be misleading and needs improvement.

• can set the signature using STAC 2 until STAC 3 update is installed.

Questions & Answers