mifile

MiFILE Release 2.2.18

Brandon Cleveland 16 April, 2025

Release to PROD Date: 4/17/2025

Display Routing Destination on Bundle eForms

You can now see the routing destination in a bundle eform prior to clicking the Done task. This is applicable when you choose the route radio button in the unity indexer. Whatever destination you choose will then display in the status column of the bundle eform as, for example, "Route: Judge Review." This gives users a visual validation of the selection they made just prior to finalizing their bundle.

Here is what it looks like: select route in the unity indexer and choose the judge and route option as always.

After you save the unity indexer, your selected route option will appear in the status column (which used to just read "pending route"):

Idea Submitted by: 54B District Court (East Lansing) - and voted up by many others!

Simplified CMS Integration Error Limit

We are simplifying the logic that prompts your CMS integrations to automatically pause. Previously, if you had a total of 30 items "stuck" in a variety of queues within the CMS Integration Life Cycle, your integrations would pause. This required you to monitor multiple queues (some of which you had no control over), and you had to do some mental math. With this release, once your Review queue hits 30 items--independent of any other queues--your integrations will automatically pause.

Your integrations will also automatically pause if your exception queue hits 30 items (also independent of any other queue), but that queue is monitored by our vendor and requires no direct action on your part.

Bug Fix: Inability to Associate Parties to Documents

A bug was reported by courts where OnBase was not returning parties on a case, making it impossible to associate parties to documents when required. The issue had to do with a race condition between our case feed processor and receiving response messages from the CMS. This update resolves that race condition and should prevent this scenario from occurring in the future.

DOCUMENT CATALOG UPDATES

Circuit Document Catalog Update: Adding Domestic Relations Judgment Information (FOC 100)

Based on court feedback, we are adding the FOC 100 form (Domestic Relations Judgment Information) to the circuit document catalog. This form is regularly submitted to the court, and needs to be routed off to the FOC office, but not filed in the court file. The logic applied to this catalog item will be the same as that of the "Verified Statement." Details on the configuration are outlined below:

OnBase Description: Domestic Relations Judgment Information

OnBase Doc Code: FOC100

OnBase Doc Type: CC - Not Filed

CMS Code: FOC100

Case Categories: Domestic Relations, Miscellaneous Family

Confidential: YES

Don't Send to CMS: YES

Idea Submitted By: Ottawa Circuit Court

District Document Catalog Update: Adding "Bench Warrant Filed" an "Bench Warrant Issued"

Based on court feedback, we are adding district document catalog items for "Bench Warrant Filed" and "Bench Warrant Issued." Details on each item's configuration is provided below:

OnBase Description: Bench Warrant Filed

OnBase Doc Code: MC229F

OnBase Doc Type: DC - Warrant

CMS Code: BWF

Case Categories: All

OnBase Description: Bench Warrant Issued

OnBase Doc Code: MC229I

OnBase Doc Type: DC - Warrant

CMS Code: BWI

Case Categories: All

Idea Submitted by: 17th District Court (Redford)

District Document Catalog Update: Adding "Request (general)"

Based on user feedback, we are adding a "Request (general)" document catalog item to the district court document catalog.

OnBase Description: Request (general)

OnBase Doc Code: REQGEN

OnBase Doc Type: DC - Request

CMS Code: EDF

Case Categories: All

Idea Submitted By: 75th District Court (Midland)

MiFILE Release 2.2.18

MiFILE Release 2.2.17

MiFILE Release 2.2.19

Similar Blog Posts

MiFILE Release 2.2.12

MiFILE Release 2.2.19

MiFILE Release 2.2.17