Adding Garnishee Disclosure Filing Types and Auto-Indexing
Based on court feedback, we are creating two new filing types for filers: "Garnishee Disclosure - Indebted" and "Garnishee Disclosure - Not Indebted." These two filing types will automatically index to their corresponding document catalog entry (cms codes DCF62 and DCF63), so clerks no longer need to manually index these forms. Please remember, for all auto-indexing efforts, these still rely on the filer to choose the proper TrueFiling filing type, and courts should always verify that the right code is being applied (and can change it manually whenever necessary).
Did you know? In the month of January, 2025, over 3700 garnishee disclosures were processed by MiFILE courts? All these will now be automatically indexed for you!
Idea Submitted by: 65B District Court - Gratiot County (and voted up by several others)!
Doc Catalog Update: Adding Motion to Set Aside Dismissal
The following entry is being added to MiFILE District Court Catalogs:
DOC Code: MOSAD
Description: Motion to Set Aside Dismissal
OB Doc Type: DC - Motion
CMS Code: MOF52
Confidential: NO
Sealed: NO
Doc File Folder: Legal File
Case Categories: Summary Proceedings, General Civil, Small Claims
Idea Submitted by: 75th District Court - Midland (and voted up by several others)!
Removing Integration Error Sticky Notes after Resolution
Once a document has been completed out of workflow, we will now be removing any integration error sticky notes that were previously applied to the document. That data is still retrievable if needed, but will no longer be visible as a sticky note once the underlying issue has been resolved and the document is stored in the MiFILE DMS.
For reference, these types of sticky notes are red and contain the integration error language that was surfaced in the CMS Integration Life Cycle.
Adding Validation to the Ready for Redaction Queue - MiFILE DMS Only
We are adding a validation to the ready for redaction queue in the case processing life cycle. In this queue, only black or white redactions should be applied to a document, which will then burn into the document upon finalizing the redaction process. If a user attempts to add other notes, such as a dynamic stamp or esignature, they will receive the message shown below in the user interaction window. This update is being made to ensure finalized documents aren't altered beyond the need for redaction.
Technical & Other Updates
JusticeTech Document Catalog Item Search
JIS users now have the ability to search document catalogs by case category to more easily identify what document catalog items have been configured for a given category (e.g., what is currently available for summary proceedings).
This update is not currently available to courts, but will assist the JIS team in maintaining and improving upon each court type's document catalog.
Update Redacted Copy Keywords upon Reindexing of Original Document
When a lead document is recoded or reindexed, if a redacted copy exists, the same keyword updates will be made for that redacted copy as well (such as doc code, CMS code, description, document type, and doc file folder). This ensures that the unredacted and redacted copies of documents are consistent.
Remove Unneeded DAFAP Logic
This is a technical update not visible to end users. We are removing system routing logic related to the generation of DAFAP reports to avoid redundancies and improve performance.
Update to Monitoring Report - DMS Documents Found Outside of Workflow
This is a technical update not visible to end users. Our vendor routinely monitors a "DMS Documents Found Outside of Workflow" report that identifies documents that may have been processed incorrectly. This update will remove from that report pending documents that have been deleted by a court user, as those are not issues that the vendor needs to investigate.