MiFILE Updates and Information

MiFILE Release 2.2.13

Written by Brandon Cleveland | Feb 5, 2025 1:47:27 PM
 Release to PROD Date: 2/6/2025
 

 

New View Only Queues for Jurists! - MiFILE DMS Courts Only 
This enhancement is for our jurists using the MiFILE DMS! Up to this point, jurists have only had access to a jurist "sign" queue in the case processing life cycle. Many users have requested a dedicated space to send documents to a jurist for review, but not necessarily signature. Comingling these two types of activity has caused confusion and led to finalized documents erroneously being signed (causing floating signature issues). 

Judges, magistrates, and referees will now have their own respective "View Only" queues. This queue is to be used to receive finalized documents that the jurist needs to review - but not sign/annotate (although adding sticky notes is just fine).
 

 

With this update, the Jurist Sign queue can then be limited to its original intent--a place to send unindexed documents that need to be signed by the jurist. 

We are also adding logic to the system to make sure the right documents end up in the right queue. We do not want finalized documents landing in the sign queue, and we do not want unindexed documents landing in the view only queue. If a user tries to send a document to the wrong queue, the system will reroute it to the appropriate queue. 
 
Improved Routing Options for Hearing Jackets - MiFILE DMS Courts Only 
MiFILE DMS courts have expressed a desire for more flexibility in how hearing jackets can move through the judicial hearing life cycle. This update will help improve workflow by allowing for the following: 
 
  • You can now route to the Hearing Docket queue from the Prep for Hearing, Jurist Hearing Review, Pre Complete, and Bench queues!
  • You can now route to the Hearing Complete queue directly from the Hearing Docket queue - no need to move through the Bench Queue first!

New Reporting Dashboard - eSignatures Not Burned into Completed Documents - MiFILE DMS Courts Only 
OnBase Administrators now have access to the "eSignatures Not Burned into Completed Documents" report, which is accessible from Reporting Dashboards. This report will show you a list of all documents where a user placed an esignature on a finalized document. These "floating signatures" have not been burned into the document, and would not be visible to a party/public user if viewed. 
 
Reports are available in the Ribbon of the Home Tab here: 
 
 
Courts should regularly review this report to ensure documents are being signed before being completed. From the report, you can double-click on any document, and remove the floating note(s). Doing so will then remove the document from the report when it is run again. Please note however that courts still need to properly address and correct any issues that may be the result of improperly applying these notes. 
 
New Update Bar Number Task in the CMS Integrations Review Queue 
We are adding an "Update Bar Number" task to the Review Queue in the CMS Integration Life Cycle. This task will allow an OnBase user to correct an invalid bar number that is associated to a subsequent filing. Please note that this task is only for subsequent filings. Invalid bar numbers associated to a case initiation bundle will still be corrected on the case initiation eform. 
 

Technical Updates 

Workview Object Import Script Update - All Hosted Courts 
Technical update to workview object import scripts. No impact to OnBase users. 
 
Monitoring Report Update 
Technical update to a monitoring report used by our vendor to identify issues with notes & annotations that need to be addressed by the vendor rather than the court. 
 
Hearing Jacket Minor Fix - MiFILE DMS Courts Only 
If a user creates a Hearing Jacket from the Forms Tab of the Home Ribbon, the system will now require all necessary minimum data before saving the form and sending it to the Prep for Hearing queue. 
 
Remove URL Encoding for UPOP Links - All Hosted Courts 
Technical update not visible to end users. 
 
Filing Processing - Backend Processing Improvements 
We are adding System Locked Bundle Queues so that backend processing isn't delayed due to a document being locked by an end user. These additional queues will also assist with investigating issues as they arise. 
 
Fix: Configuration Workbook Import Update - Copy for Case Processing 
Technical update not visible to end users.