The following are the contents of update notices that have been sent describing changes to Court Integration Services.  As soon as a notice is published (usually a month before the updates are implemented) it will be posted here.   If you would like to receive email messages when these update notices are published, please contact the Integration Team and ask to be added to the mailing list.

• Court Integration Services Release 94
• Court Integration Services Release 93
• Court Integration Services Release 92
• Court Integration Services Release 91
• Court Integration Services Release 90
• Link to all prior Releases beginning with Release 1

Court Integration Services Release 94

Environment(s): Production

Effective Date/Time: Thursday, December 18, 2024 at noon
To: Integration Group Contacts
Purpose: Notify Court Integration Services consumers of an upcoming update.
Details: The following updates will be applied to Integration Services:
 

Point-to-Point Data Passes

 

Examiner Resource Application (ERA)

A new case event will be added to apply to Criminal cases for the ERA integration pass. 
Order for Neuroleptic Exam (ONE)
 

Integrated eFiling

 

Batch Citation Processing

Internal changes to court's batch citation processing will accelerate processing of citations into Odyssey to better match BCA submissions to the court. Parking citations will continue to not process immediately during the morning court workday hours but will be processed after peak times.
 

Judicial Branch Internal Changes

 

ServiceNow Dashboard

The ServiceNow dashboard has been updated to accommodate a name change for the Level 1 group.
 

Employee Access Request Automation

The group "All Treatment Court Coordinators" has been added to the Supervision Access request.
 

Non-Prod Odyssey Configuration and Access Requests Automation

This new automation has been added to process requests for non-production Odyssey desktop configuration.

Birthright Roles Automation
This new automation has been added to process new account requests and provide them with group membership based on their team assignment.
 

Internal Technical Changes

 

SoapServices Web Service Endpoint Retirement

This change will disable an old unused Web Services endpoint. In the past this endpoint was accessed using URLs ending with /soapservices/courtsis_02/courtsis.ashx.

return to top

Court Integration Services Release 93

 
Environment(s): Production
Effective Date/Time: Thursday, October 31, 2024 at noon
To: Integration Group Contacts
Purpose: Notify Court Integration Services consumers of an upcoming update.
Details: The following updates will be applied to Integration Services:
 

General Services

Case Get

Migrated the service for CaseGet to the current development architecture.   There were no functional changes.
 

Point-to-Point Data Passes

Minnesota Attorney Registration System (MARS)

The MARS to Minnesota Court Information System (MNCIS) attorney integration has been updated to concatenate the 4^th line of the address into the 3^rd line of the address on new attorneys added.
 

Other Integration Services

 

Sentencing Order 

Adjusted Sentencing Order process to bypass cases that do not have case numbers.
Corrected the signature line placement on the Sentencing Order. 

return to top

Court Integration Services Release 92

 
Environment(s): Production
Effective Date/Time: Wednesday, September 11, 2024 at noon
To: Integration Group Contacts
Purpose: Notify Court Integration Services consumers of an upcoming update.
Details: The following updates will be applied to Integration Services:
 

General Services

 

Civil Commitment Notification

A new MNCIS case event will now trigger this case notification:
• Order Appointing Forensic Navigator (ORAPFORNAV)
 

Court Decision Notification

A minor change was made to prevent failures when the Reimbursement component is entered on a juvenile judgment.
CaseNotification/CourtDecisionNotification/JuvenileJudgment/Reimbursement/ObligorPayor
 

Charge Disposition Notifications and Case Get Query Results

New disposition codes will be added to MNCIS effective January 1, 2025:

• PROBV - Stay under 609.1056 Military Veteran
• PROBCS - Stay under 152.18 Controlled Substance
• PROBNS - Stay under 609.3751 Nonpayment of Support
• FGNA - Found guilty No adjudication

The following dispositions will have an obsolete date and status added to them at that time:

• PROB - Statutory stay of adjudication
• NOADJUD - No adjudication-lesser offense

The MNCIS simple type files for ChargeDispositionTextType are updated in the non-production files and available for testing.
 

Point-to-Point Data Passes

 

MyMnConservator (MMC)

Migrated the services for MMC to the current development architecture.   There were no functional changes.

DVS Transaction Logging

Migrated this service to our current development architecture.
 

NICS - National Instant Criminal Background Check System 

The new charge disposition codes noted above are included in NICS processing when appropriate.
 

Document Integrations

 

File Stamping Fix 

PDF file stamping fix for document added directly to MNCIS to prevent errors when they are processed in Task Manager.
 

Internal System Changes

 

IBM MQ

Migrate to the current IBM MQ client library.
 

ECF Court Record Service Logging

Stop logging full output messages for this service to cut down on log space requirements.
 

ECF Filing Review Logs

Implement a purge of log entries older than 6 years.

return to top

Court Integration Services Release 91

 
Environment(s): Production
Effective Date/Time: Friday, June 28, 2024 at noon
To: Integration Group Contacts
Purpose: Notify Court Integration Services consumers of an upcoming update.
Details: The following updates will be applied to Integration Services:
 

Point-To-Point Data Passes

 

My MN Conservator (MMC) 

Refined phone logic to handle when the current phone number is also invalid.
 

BCA Protection Order Pass Change 

Change the process that sends messages to the BCA to use the .Net component HttpClient rather than WebRequest to perform message sends.  This is an internal change that does not affect the messages being sent.
 

General Services

 

Case Notification Service

Change to the way warrants are loaded for parties on the published case to improve publishing performance.   This is an internal change and does not affect the messages being published.
 

ECF Filing Review Service

Subsequent Filing, internal changes:

• Refined error processing to better handle issues with partner receiver services.
• Updated the parameters for the maximum eFS message size.

Integration Access Rights 

• Developed a new access right to support court review-event processing.
• Internal updates to reflect source-system code changes.

Automation

 

Senior Judge ServiceNow Automation

Use 2 working days prior rather than 2 days prior when calculating the processing date and time for changes.
 

HR Center

The process for providing supervisor access to the HR Center has been updated to use Active Directory groups.
The previous processes have been decommissioned.
 

Internal Changes

 

CourtXML SimpleTypes

Migrate the process that produces CourtXML SimpleType schemas and companion files to our current development architecture.
 

Migrate services using .Net 6 to .Net 8

Migrate all services developed with our current architecture from .Net 6 to .Net 8.   This is an internal change and does not affect the functionality of the services.
 

MCRO Watermark Flatten Document Option

Add a new option to the watermark service for MCRO to request that a document is flattened before the watermark and signature are added.   This is to correct an issue with certain documents that prevents them from receiving digital signatures.
 

Positive Pay

Discontinue a file exchange of positive pay files for Wright County. 

return to top

Court Integration Services Release 90

Environment(s): Production
Effective Date/Time: Tuesday, April 30, 2024 at noon
To: Integration Group Contacts
Purpose: Notify Court Integration Services consumers of an upcoming update.
Details: The following updates will be applied to Integration Services:
 

Point-To-Point Data Passes

 

My MN Conservator (MMC)

Change MNCIS case events for two MMC reports

Account Examination: 
Changed from 'Inventory or Account Review Report' to 'CARP Review Report'.

Account Examination Judicial Review Necessary:
Changed from 'Inventory or Account Review Report-Judicial Review' to 'CARP Review Report - Judicial Review Necessary'.

Add new review event to MNCIS for additional MMC reports
"Level 4 Judicial Review Complete [R]" will be added to MNCIS when MMC submits the following:
     CAAP Audit Report - Judicial Review Necessary
     CARP Review Report - Judicial Review Necessary

Send multiple party phone numbers
'Letters' and 'Party Update' messages were enhanced to send more than one phone number/type to MMC, when applicable.

New 'Judicial Review Complete' integration
A new integration from MNCIS to MMC was developed to notify MMC when a 'Completed' date is entered for "Level 4 Judicial Review Complete [R]" events.
 

My MN Guardian (MMG)

New 'Guardian Waived' integration

A new integration from MNCIS to MMG was developed to notify MMG when an "Order Waiving Use of MMG" case event is added to a Guardianship/Conservatorship case.

A new edit failure was developed to support this integration and will be set if the event is added without the associated party.

New criteria for re-sending "letters" to MMG
"Letters" information will now be re-sent to MMG when a qualifying "letters" case event is updated in MNCIS with different event "Date" or the "Issued to" parties change.
 

Statute and Offence Code Maintenance (SOCM)

The backend integration processes that provide query and export access to statutes from the BCA have been migrated to our current development toolset.
 

BCA Vehicle Make Processing

The backend integration processes that process vehicle make codes from the BCA have been migrated to our current development toolset.
 

Other Integration Services

 

Sentencing Order

Corrects the placement of the date, judge name, and signature on the Sentencing Order when necessary.
 
return to top

Court Integration Services Release 89

 
Environment(s): Production
Effective Date/Time: Thursday, February 29, 2024 at noon
To: Integration Group Contacts
Purpose: Notify Court Integration Services consumers of an upcoming update.
Details: The following updates will be applied to Integration Services:
 

Point-To-Point Data Passes

MyMNConservator (MMC)

Internal updates were made to correct the name applied to Amended Annual Account documents submitted from MMC.
 

Background Check Reminder App (BCRA)

MNCIS to BCRA integrations were developed to support the process of notifying guardians and conservators of approaching background check requirements.
 

Harassment Restraining Orders (HRO)

Removed Protection Order edit failure 86 as it is no longer valid due to a fix in document annotation logic. 
 

Extreme Risk Protection Orders (ERPO)

New Case Event for the Bureau of Criminal Apprehension Service Notification is added that will not set case security review flags needed with other types of protection orders.
Schema is modified to indicate conditions are optional.
 

ServiceNow

Exiting Senior Judge Automation

Removal of processing for Citrix.
 

File Exchanges

MN Court Information System to Swift 
Month-end file transform was updated to use revised voucher type for Branch files.
 

Internal Changes

Message Processing Logs

Changes to what is logged as messages are processed for various services to reduce disk space requirements.
 

Document Get Audit Report

Change to how the audit report is produced to accommodate changes made to message processing logs.

return to top

Court Integration Services Release 88

 
Environment(s): Production
Effective Date/Time: Tuesday, December 15, 2023 at noon
To: Integration Group Contacts
Purpose: Notify Court Integration Services consumers of an upcoming update.
Details: The following updates will be applied to Integration Services:
 

Custom Integrations

 

Protection Orders (OFP, HRO, and ERPO)

Extreme Risk Protection Orders 

Changes are implemented for Protection Orders in MNCIS in preparation for automating the sending of Extreme Risk Protection Orders (ERPO) to the BCA and NCIC ERPO File.
 
The existing Order for Protection (OFP) and Harassment Restraining Order (HRO) integration will remain essentially the same but will now include Extreme Risk Protection Orders (ERPO). The ERPO pass will include the document images associated with the ERPO.
 
New legislation for Extreme Risk Protection Orders (ERPO) is effective January 1, 2024. 

New case type, EPO-Extreme Risk Protection Order

New schema with BCA
                OFP and HRO remain unchanged.
                New ERPO selection.

MNCIS Custom Edits
                Language modified for custom edits that apply to all protection orders.
                Custom edits modified if behavior is different between the different types of protection orders.
                New custom edits are introduced for ERPO.

MNCIS Edit Failures – updated to include ERPO.

Reports - MNCIS reports will be modified by local courts to include ERPO similar to HRO and OFP.

Validation – Current data validation processes between agencies are modified to include ERPO.

 

Digital Exhibit Management

The internal service was enhanced to support new court processing requirements.
 
return to top

Court Integration Services Release 87

 
Environment(s): Production
Effective Date/Time: Tuesday, October 31, 2023 at noon
To: Integration Group Contacts
Purpose: Notify Court Integration Services consumers of an upcoming update.
Details: The following updates will be applied to Integration Services:
 

Integration Access Rights

Case Security

Internal changes were made to better handle data shared across products.
 

Custom Integration

Supervision/Treatment Case Cross Reference 

Enhanced the integration to add the Cross Reference number to supervision/treatment cases linked with new charges. 
 

Internal Changes

Document Signing

A new option for digitally signing documents has been added for use by services that process and sign documents.
 

Odyssey Document Handling

A process change for a small set of documents added to Odyssey to accurately display number of pages. 
 

Access Request Automation

A new automation has been created to process access requests for the supervision security group.

return to top

Court Integration Services Release 86

 
Environment(s): Production
Effective Date/Time: Thursday, August 31, 2023 at noon
To: Integration Group Contacts
Purpose: Notify Court Integration Services consumers of an upcoming update.
Details: The following updates will be applied to Integration Services:
 

Point-to-Point Data Passes

Remote Hearings

Internal changes made to the MNCIS-to-Zoom integration to comply with Zoom security requirements.

Judge Maintenance (GJUDGE) pass
Migrated the services for MNCIS, MACS and Judge File to our current development architecture.   There were no functional changes.
 

Integrated eFiling

 

eFS Integrations

Services were updated to better handle eFS filer names containing apostrophes.
 

Batch Citation Processing

Internal changes to court's batch citation processing. These internal changes will accelerate processing of complaints and petitions within the MNCIS workflows. Citations marked as In Custody will still process immediately for accelerated court hearings. Parking citations will no longer be processed immediately if submitted during peak timeframes. All other citations will process during peak court work hours but at a slower pace to not impede higher priority filings. 
 

Citation NameGet Processing

Vehicle registered-owner lookup service has been refined to better handle variations in redesigned WI source data.
 

Automation

ServiceNow Exiting Employee Automation

Processing change to minimize the manual work required when the automation fails because of insufficient access to an OU.
 

ServiceNow Employee Access Request Automation

Added Artificial Intelligence (AI) Exception Form Request processing.
 

Sentencing Order (EP296)

The Sentencing Order process was updated to bypass Odyssey publishing, prevent duplicate orders from being attached to the same event, remove the outstanding failure when users delete the event before the order could be attached, and to make the order digitally accessible.
Additionally, the print margins were updated to resolve an issue with text being obscured at the page breaks.

return to top

Court Integration Services Release 85

 
Environment(s): Production
Effective Date/Time: Friday, June 30, 2023 at noon
To: Integration Group Contacts
Purpose: Notify Court Integration Services consumers of an upcoming update.
Details: The following updates will be applied to Integration Services:
 

Integrated eFiling

 

Extradition Cases

Extradition court files were impacted by recent legislative changes. eComplaints citing extradition statutes may once again be eFiled via BCA eCharging effective May 26, 2023. 
 

Point-to-Point Data Passes

 

MyMNGuardian (MMG)

Messages sent from MNCIS to MMG when a qualifying letters event is added now include suffix (Jr., Sr., II, etc.) for the party's current known name.
 

Secretary of State pass

Updated to support 2023 legislative changes.
 

Minnesota Attorney Registration System (MARS) pass

Migrated the services for LDMS, CLE and the public website to our current development architecture.   There were no functional changes.
 

File Exchanges

A new file exchange of positive pay files for Wright County. 

return to top

Court Integration Services Release 84

Environment(s): Production
Effective Date/Time: Friday, April 28, 2023 at noon
To: Integration Group Contacts
Purpose: Notify Court Integration Services consumers of an upcoming update.
Details: The following updates will be applied to Integration Services:
 

Internal Changes

 

Database Access Enhancement

An internal change has been made to improve the performance of database access for services.
 

HR Center Get Supervisors from MMB Data

Updating the Get Supervisors program to access a new SharePoint 2019 site (instead of SharePoint 2017).
 

HR Center Sync Permissions

Updating the Sync Permissions program to access a new SharePoint 2019 site (instead of SharePoint 2017).
 

Decommission CPC Call Log Archive Process

The CPC Call Log Archive process is no longer needed. The Integrations program and database resources can be decommissioned.
 

Hearing Officer SharePoint List Item Deletion 

New process to delete items that exceed retention policy which will prevent Hearing Officer SharePoint list from exceeding record limit.
 

Point-to-Point Data Passes

 

Minnesota Attorney Registration System (MARS) foreign address update. 

MARS updated their foreign address field to consume all address fields. 
A change will be made to handle how the Minnesota Court Information System (MNCIS) and Minnesota Appellate Court Management System (MACS) receive an Attorney's foreign address from MARS. 
 
return to top

Court Integration Services Release 83

 
Environment(s): Production
Effective Date/Time: Tuesday, February 28, 2023 at noon
To: Integration Group Contacts
Purpose: Notify Court Integration Services consumers of an upcoming update.
Details: The following updates will be applied to Integration Services:
 

Integrated e-Filing

 

Add Case Cross Reference Number - PRISM Case Number

A new Case Cross Reference Number enumeration reflects addition to MNCIS for future integration with MN DHS (Department of Human Services) and their PRISM (Child support enforcement and collection) system.
 

Add Case Events - PRISM Case Opened and PRISM Case Closed

New MNCIS Case Events are added to integrations to accommodate MN DHS PRISM. These Case Events will set and unset the MNCIS IV-D case flag consistently to synchronize MNCIS to PRISM.
 

Add Case Flag - Fingerprints Required by Statute

Internal changes to accommodate a future MNCIS automation. In the near future, MNCIS functionality will be deployed to set this case flag consistently across all appropriate cases in MNCIS. The current reliance on eFilers to submit when Fingerprints are Required on a court file is removed.
Note: This will have no impact to the current process for agencies to notify the court when Fingerprints have been Taken or when a Booking has been submitted to the BCA Criminal History.
 

Add Person Contact Information

A fix to allow for phone numbers with leading zeroes in their 4-digit line number part.
 

ECF Document Filing 

A fix for an issue causing requests routed directly to MNCIS to fail due to a change made for requests routed to EFS.
 

Get Firm Service Contacts 

A fix to handle larger message size from EFS.
 

Internal Changes

 

CPC Archive Process Changes

Added new "HOAScheduled" column to the archive process.
 

Hearing Officer SharePoint List Item Deletion

New process to delete items that exceed retention policy which will prevent Hearing Officer SharePoint list from exceeding record limit.

return to top

Court Integration Services Release 82

 
Environment(s): Production
Effective Date/Time: Thursday, January 5th, 2023 at noon
To: Integration Group Contacts
Purpose: Notify Court Integration Services consumers of an upcoming update.
Details: The following updates will be applied to Integration Services:
 

Notifications

Civil Commitment Notification 

Three new MNCIS case events now trigger this case notification: 

• Finding of Incompetency and Order
• Finding of Incompetency and Order - D16
• Finding of Incompetency and Order - Juvenile

Notifications pushed through Web Services/HTTP 

The user-agent http header has been added to pushed notification messages using web services/http. This will prevent rejections when network security software requires that header. This does not affect notification messages that are pulled or that are received using MQ Series.

Query Services

Document Get 

A recently introduced bug was fixed.

 

Integrated eFiling

eFS - eFile to eFS

Attach and Detach Service Contacts 
The Attach/Detach Service Contact service will now return a formatted error when user credentials are not submitted.
 

Attorney Assignment

An internal change is implemented to prevent an errant partner application from causing duplicate entries in MNCIS.

 

Point-to-Point Data Passes

My MN Guardian (MMG)

Additional triggering MNCIS case events were added to the MNCIS-to-MMG messages for discharging guardians and termination of guardianship.
 

NICS - National Instant Record Background Check System

Additional triggering MNCIS case events were added to the NICS pass.
Minor modification to prevent unnecessary updates to a NICS entry due to court processing procedures.
 

Examiner Resource Application (ERA)

One case event will be added to the integration from MNCIS to ERA to provide examiners an accurate method to bill for those services. 
Order Regarding Request for Rule 20 Extension (ORR20EXT).
 

Minnesota Attorney Registration System (MARS)

Additional Attorney Standing code to improve accuracy.

 

Integration Access Rights

Document Security

An internal document-processing service was updated to better handle unexpected document storage locations.
 
return to top

Court Integration Services Release 81

Environment(s): Production
Effective Date/Time: Monday, October 31^st, 2022 at noon
To: Integration Group Contacts
Purpose: Notify Court Integration Services consumers of an upcoming update.
Details: The following updates will be applied to Integration Services:
 

Integrated eFiling Services

Person Contact 
Service was enhanced to add more descriptive MNCIS-user Created/Updated audit trail information. 
 
Court Case Event 
Service was enhanced to add more descriptive MNCIS-user Created/Updated audit trail information. 
 
Person Demographic
Service was enhanced to add more descriptive MNCIS-user Created/Updated audit trail information. 

 

Point to Point Services

Digital Exhibit Management 
A new service was developed to assist internal court processing.

 

Query Services

DocumentGet 
Refined document-query responses to be more timely and descriptive when the requested document exceeds the size limit of the service.

return to top

Court Integration Services Release 80
 

Environment(s): Production
Effective Date/Time: Wednesday, August 31^st, 2022 at noon
To: Integration Group Contacts
Purpose: Notify Court Integration Services consumers of an upcoming update.
Details: The following updates will be applied to Integration Services:

Integrated eFiling
 
eFS - eFile to eFS
 

Supplemental Filing Service

• Service has been updated to better handle unexpected characters in the document name (BinaryDescriptionText)
  • XPATH: CoreFilingMessage/FilingLeadDocument/DocumentRendition/DocumentRenditionMetadata/DocumentAttachment/BinaryDescriptionText
• Internal updates were made to better handle variations in filing.

Service Information Query

• The query service has been updated to better handle cases that have large numbers of parties and/or service contacts.

 

Internal Changes

Framework update

return to top

Court Integration Services Release 79

 
Environment(s): Production
Effective Date/Time: Thursday, June 30^th, 2022 at noon
To: Integration Group Contacts
Purpose: Notify Court Integration Services consumers of an upcoming update.
Details: The following updates will be applied to Integration Services:
 

Integrated eFiling

Schema - Juvenile eCitation 
A new Juvenile eCitation schema version 3:5 is available. 

New:

• Third Violation Indicator is now available and optional

Change:

• Offense Location Text is now optional

These changes conform the juvenile schema consistent to the adult citation schema. These were identified in the current Hennepin pilot. No changes are required for current vendor systems submitting to HJIP (Hennepin Justice Integration Program). This is in preparation for a future statewide project with the BCA (Bureau of Criminal Apprehension).
 
eFS - Supplemental Filing Service 
A fix was made to send appropriate failed status to the submitter in one specific situation.
 

Point to Point Services

IRMA - Interpreter Resource Management Application
Internal update to prevent integration failures to the Interpreter Resource Management Application that may cause hearing reschedules or cancels to get missed by the integration. 
 
Internal Document Processing
File Stamping - Citation Data Summary and Supplemental Complaint Document
 
The process for adding file stamps to these documents has been updated to use our current method for adding file stamps.
 
return to top

Court Integration Services Release 78

Environment(s): Production
Effective Date/Time: Friday, April 29, 2022 at noon
To: Integration Group Contacts
Purpose: Notify Court Integration Services consumers of an upcoming update.
Details: The following updates will be applied to Integration Services:
 

Query Services

CaseGet 
A fix was made to ChargeDispositions to better handle amended dispositions and ensure only the current disposition is returned in the reply.
 
Integration Access Rights
Document Security
A new service was developed to assist internal court processing.
 

Notifications

Case Notifications
A change was made to allow messages to publish when unexpected MN Court Information System party records are used as case parties.
 

Point to Point Services

Minnesota Court Records Online (MCRO)
Internal changes are being made to error handling for the service used by MCRO to add watermarks to documents.

return to top

Court Integration Services Release 77

Environment(s): Production
Effective Date/Time: Monday, February 28^th, 2022 at noon
To: Integration Group Contacts
Purpose: Notify Court Integration Services consumers of an upcoming update.
Details: The following updates will be applied to Integration Services:
 

Integrated eFiling

Juvenile ePetitions

• Internal processing changes in preparation for pilot.

Custom Integrations

Interpreter Edit Failure Update

• A new edit failure was created to identify when court users add a completed date to the request for interpreter case event.

General

Integration API Reference Service

• A new internal document service was developed to support future projects.

 return to top

Court Integration Services Release 76

 
Environment(s): Production
Effective Date/Time: Monday, January 3, 2022 at noon
To: Integration Group Contacts
Purpose: Notify Court Integration Services consumers of an upcoming update.
Details: The following updates will be applied to Integration Services:
 

Integration Access Rights

Internal changes were made to support future projects.
 

Point to Point Services

MCRO
A new service is being implemented in support of online access to documents using MCRO (Minnesota Court Records Online).
 

User Interfaces

IB Messenger
A fix was applied to the IB Messenger (Edit Failures) user interface to prevent errors from occurring if large amounts of text are added to the additional information field when requests for assistance are submitted to the Service Desk.
 

General

Some internal updates to services to bring them up to current versions of our development tools.

return to top

Court Integration Services Release 75

 
Environment(s): Production
Effective Date/Time: Friday, October 29, 2021 at noon
To: Integration Group Contacts
Purpose: Notify Court Integration Services consumers of an upcoming update.
Details: The following updates will be applied to Integration Services:

Point-to-Point

Remote Hearings 

• MNCIS to Zoom integration now handles instances where meetings are deleted in Zoom prior to MNCIS Court Session updates.

Integrated eFiling

eFS Integrations 

• Services now return a response when the filer’s eFS account has not been approved in eFS. 

MNCIS eFilings

• Additional retry processes are deployed to handle system failures within Odyssey to prevent citations and complaints from rejecting to e-filers.

Schema - New Complaint and Petition Document PDF

• A new schema version (3.2) is published for the service used to move BCA eCharging complaint and petition PDF documents to MNCIS.
• The new schema allows submission of the PDF at the time of case initiation to reduce delays. 
• ComplaintSupplementalDocumentAdd_3_2.xsd

 return to top

Court Integration Services Release 74

Environment(s): Production
Effective Date/Time: Thursday, August 31, 2021 at noon
To: Integration Group Contacts
Purpose: Notify Court Integration Services consumers of an upcoming update.
Details: The following updates will be applied to Integration Services:
 

Query Services

CaseGet 

• Responses will now successfully publish for legacy cases where the Financial Details have been requested and unexpected/non-standard financial adjustments exist on the case.
• CourtXML change to allow email addresses that include underscores and hyphens.

 

Point-to-Point

Remote Hearings 

• Integration Statistics are updated to include MNCIS-to-Zoom usage.

 

Integrated eFiling

Attorney Assignment 

• Service was enhanced to add more descriptive MNCIS-user Created/Updated audit trail information. 

 Party Contact Information 

• CourtXML change to allow email addresses that include underscores and hyphens.

 

Case Notifications

CourtXML 

• Messages will now successfully publish for cases with charges that have $1,000 (or more) entered for the Wildlife Restitution Amount.
• Change to allow email addresses that include underscores and hyphens.

 return to top

Court Integration Services Release 73

Environment(s): Production
Effective Date/Time: Thursday, June 17, 2021 at noon
To: Integration Group Contacts
Purpose: Notify Court Integration Services consumers of an upcoming update.
Details: The following updates will be applied to Integration Services:
 
Note:  Please see the information at the end of this notice regarding a change to how these releases are scheduled.
 

Integrated eFiling

Appellate Court Opinions from the (Minnesota Appellate Courts Case Management System (MACS) to the Minnesota Court Information System (MNCIS)
Appellate Opinions: Precedential and Nonprecedential will be separated into specific MNCIS case events.
 
Citation Name Get Processing 
The vehicle registered-owner lookup service is updated to prevent internal errors by better handling incomplete and/or inconsistent source-system data.
 

Point-to-Point Data Passes

Harassment Restraining Orders (HRO)

• An internal edit failure notification process is implemented to notify court staff when annotated documents need to be updated and sent to the MN Bureau of Criminal Apprehension (BCA).
• An internal fix to the query validation process is implemented.

MyMnConservator (MMC) 
To better support the design of MMC, the messages sent from MNCIS to MMC when a qualifying letters event is entered now include the current known name for the parties rather than the primary names on the case.

Remote Hearings 
A new edit failure was created to capture court session updates that interrupt the MNCIS to Zoom Integration: Zoom Integration Court Session Comment manually changed.
 
BCA Protection Orders Pass
A fix to the Protection Order Query to prevent errors from occurring for certain documents.
 

Notifications

Case Notifications
Appeal Notification 
The Appeal Notification will continue to trigger for Appellate Court Opinions added to MNCIS. These are now differentiated based on Case Event type.

• Appellate Court Opinion - Precedential
• Appellate Court Opinion - Nonprecedential

These updates are currently available for testing in our Development and Quality Assurance (QA) environments.  These updates should not require any system downtime to implement in production. 

Integration Services Release Schedule Change
We will be changing the schedule of Integration Services releases from occurring every quarter to occurring every 2 months.  This release will be the last quarterly release.   Our next release will be applied to production at the end of August.  Releases, starting with the August release, will have the following characteristics:

• Occur every 2 months.
• The release date will generally be on the last working day of the release month.  If there are scheduling conflicts it will be changed to a date as near as possible to that date.
• Notice will be sent out 3 weeks prior to the release date.
• Releases will be applied to our QA environment 3 weeks prior to the release date.
• Releases will be applied to production over the noon hour on the release date (same as the current process).

Please let us know if you have any questions.

return to top

Court Integration Services Release 72

Environment(s): Production
Effective Date/Time: Thursday, March 18, 2021 at noon
To: Integration Group Contacts
Purpose: Notify Court Integration Services consumers of an upcoming update.
Details: The following updates will be applied to Integration Services:
 

Integrated eFiling

Professional Party Assignments
An internal change will be made for better handling of mass submissions from partners.
 

Point-to-Point Data Passes

Harassment Restraining Orders (HRO)
An internal edit failure notification process will be implemented to notify court staff when newer documents may need to be sent to the BCA.
 
MyMNGuardian (MMG)
An enhancement was made to send a new message from MNCIS to MMG indicating the entire guardianship is terminated.
 
Remote Hearings
Internal services were developed to provide additional options when scheduling remote hearings.
 
Interpreter Resource Management Application (IRMA)
Internal update to prevent failures when trying to send inactive parties to IRMA with hearing attendance.
 
Examiner Resource Application (ERA)
One case event will be added to the integration from MNCIS to ERA to provide examiners an accurate method to bill for those services.

• Sexually Dangerous Personality Report (RPSEXDANG)

IB Messenger
The process for resolving edit failures has been modified to allow for the submission of ServiceNow tickets directly from the IB Messenger application without having to log-in to ServiceNow.
 

Notifications

Case Notifications
Charge: The Charge Notification has been updated to correct an issue with publishing a certain variation of charges being deleted from a case in MNCIS.
 
return to top

Court Integration Services Release 71

Environment(s): Production
Effective Date/Time: Thursday, December 10, 2020 at noon
To: Integration Group Contacts
Purpose: Notify Court Integration Services consumers of an upcoming update.
Details: The following updates will be applied to Integration Services:
 

Point-to-Point Data Passes

MyMNGuardian (MMG)

• Information presented in the Integration Manager was enhanced for party updates from MMG to MNCIS in order to assist in troubleshooting.

 Secretary of State pass

• Logic was refined to reduce instances where redundant/duplicate messages may be sent to the Secretary of State.

 eFinance Invoice Import

• A new custom service has been created to import invoices received from vendors into the eFinance application.

 ERA

• The following case event will be removed from the MNCIS to ERA integrations as it is not intended to be used for recording court-appointed examiner reports.
  • Examiner's Report in Support of Petition for Commitment              (RPEXAMSUPP)

Integrated eFiling

Citation NameGet Processing

• Registered-owner vehicle lookup service has been updated to use redesigned source data.  This change will increase accuracy of owner information for leased vehicles and vehicles with WI plates.

 Appellate Document e-File

• Documents received from the Appellate Court will start receiving file stamps again.

 

Notifications

Case Notifications
Warrant case notification

• A technical change was made to correct an internal issue.  There is no impact to the messages or to partners.

return to top

Court Integration Services Release 70

Court Integration Services Release 70
Environment(s): Production
Effective Date/Time: Thursday, September 17, 2020 at noon
To: Integration Group Contacts
Purpose: Notify Court Integration Services consumers of an upcoming update.
Details: The following updates will be applied
 

CourtXML

Simple Types
 

• Technical updates were made to refine the values in some simple type files.

Point-to-Point

Certificates of Conviction, Driver License Notice, DVS File Extract (Internal)
 

• Technical updates were made in response to Department of Vehicle Services (DVS) changes related to the new MnDrive system.

MyMnConservator (MMC)
 

• In response to the August 1, 2020 legislative changes services were updated to include the new case-party connection type: Person Subject To Conservatorship (PUC).
  • Note: this change moved to Production on 8/1/2020.

MyMnGuardian (MMG)
 

• In response to the August 1, 2020 legislative changes services were updated to include the new case-party connection type: Person Subject To Guardianship (PUG)
  • Note: this change moved to Production on 8/1/2020.

Examiner Resource Application (ERA)
 

• Six case events will be added to the integration from MNCIS to ERA to provide examiners an accurate method to bill for those services.
  • Rule 20.01 Felony                         (RU20.01FEL)
  • Rule 20.01 Gross Misdemeanor (RU20.01GMD)
  • Rule 20.01 Misdemeanor            (RU20.01MSD)
  • Rule 20.02 Felony                         (RU20.02FEL)
  • Rule 20.02 Gross Misdemeanor (RU20.02GMD)
  • Rule 20.02 Misdemeanor            (RU20.02MSD)

Hearing Officer Appointment List (SharePoint) 
 

• The existing process that loads the 2nd District Hearing Officer appointments into SharePoint has been replaced. The appointment information will now be updated throughout the day but the overall functionality of the site will not change.

IMS Package Inventory (SharePoint) 
 

• The packages/features/updates that have been installed via Tyler's IMS process will be available in a SharePoint list. The information will be loaded from the Justice database daily.

4th District Felony Trial (SharePoint) 
 

• The existing process that retrieves the list of trials for the 4th District Felony Trial SharePoint site has been replaced. Users of the 4th District Felony Trial SharePoint site will experience no noticeable difference.

HR Center (SharePoint) 
 

• The existing process that retrieves the list of Supervisors from the MMB data has been replaced. Users of the HR Center will experience no noticeable difference.

eFS Query Services

Firm Payment Account Query
 

• Service was updated to better handle instances where the EFS account has no payment accounts configured.

Integrated E-Filing

Hearing EFiles 
 

• Currently, attempts to schedule into a hearing session not configured by the local court as 'Same Time' fail, but no response message is returned to the partner. Partners will now receive a response with an error message of "Submitted Hearing Session is not available for scheduling by justice partner systems".

Case Notifications

Public Defender Notification
 

• An additional case event will now trigger the Public Defender notification. The additional case event is:
  • Order Granting Public Defender-Juvenile (ORPDJ)

return to top

Court Integration Services Release 69

Environment(s): Production
Effective Date/Time: Thursday, June 18, 2020 at noon
To: Integration Group Contacts
Purpose: Notify Court Integration Services consumers of an upcoming update.
Details: The following updates will be applied
 

CourtXML

Vehicle Makes (VehicleMakeText)
MNCIS is updated to use National Crime Information Center (NCIC) vehicle make values.
This change allows more detailed and accurate information regarding vehicle makes to be stored in MNCIS and helps align vehicle-make information in MNCIS with information used by other criminal justice partners.
This impacts both inbound and outbound integration services:

• Citations
  • CitationVehicleInType
• Complaints
  • ComplaintVehicleType
  • InitiateCriminalCaseVehicleType
• Case Notifications
  • CaseNotificationVehicleType
• Bond Notifications
  • BondNotificationVehicleType
• CaseGet
  • CaseGetVehicleType
• Simple type and companion file
  • VehicleMakeTextType.xsd
  • VehicleMakeTextType.xml

Important Note: As of the June 2020 release, vehicle makes submitted in efiles must reflect the updated values found in the VehicleMakeTextType Simple Type in order to file a case in MNCIS.  Notifications and query responses will contain NCIC vehicle makes.

 

E-Filing

File stamps will no longer be added to documents filed into MNCIS from the Appellate Court (MACS).
 
 

Point-to-Point Data Passes

CPC Call Log Archive (SharePoint)

• The existing process to archive CPC Call Log SharePoint items has been replaced. The new process will move items from the Call Log SharePoint site to the archive database daily. A new SharePoint list, form, and report are also included in this project.

CPC Call Log Destruction

• A new process has been created to automatically document and delete CPC Call Log items from the archive database once they exceed the retention policy. The process will document and delete eligible archive items each day. A new report is included in this project.

Domestic Abuse No Contact Orders to BCA (DANCO)

•  There were rare situations where deleting an interim DANCO would not trigger a pass to the BCA. These situations should now trigger successfully.

Harassment Restraining Order (HRO)

• A technical change was made to the document pass to the BCA.

MyMNGuardian (MMG)

• A technical change was made to improve efficiency of the MMG document submission process.
• A fix was made to the message sent from MNCIS to MMG indicating paper reports were filed.  This change corrects the guardians included in the message when multiple guardians are associated with the applicable review events.
• A change was made to the party-update message sent from MNCIS to MMG when the change was made by MMG.  Party updates received from MMG will no longer be sent back to MMG.
• A change was made to handle amended Affidavit of Service documents sent from MMG to MNCIS.  Amended Affidavits of Service will be identified and review events will not be updated or created in response to receiving an amended Affidavit of Service.
• Edit Failures – two new edit failures were added to handle documents filed through eFS where MNCIS configuration cannot be enforced:
  • Orders discharging the guardian that are missing the associated party (guardian).
  • Letters of guardianship that are missing the associated party (guardian).

National Instant Criminal Background Check System (NICS)

• A technical change was made to the pass to NICS.

return to top

Court Integration Services Release 68

Environment(s): Production
Effective Date/Time: Thursday, March 19, 2020 at noon
To: Integration Group Contacts
Purpose: Notify Court Integration Services consumers of an upcoming update.
Details: The following updates will be applied
 
Minnesota eFile & eServe (eFS) Integration Services
Our eFS integration services have completed pilot testing and are now available as part of our Service Catalog. We have two primary services and several ancillary services. The two primary services are:

Subsequent Filing: Developed to provide partners with a system-to-system method to file and/or serve documents through eFS.

Attach and Detach Service Contacts: Developed to provide partners with a system-to-system method to attach and detach service contacts to cases in eFS.

Enhancements included with this release:

• Previously, our eFS integration services would be unable to distinguish between two case numbers which only differed by leading zeros and hyphen placement (e.g. 99-CR-18-345 and 99-CR-01-8345), resulting in an Ambiguous Case Number error being returned. The eFS integration services will now be able to distinguish between these case numbers.
• Previously, our eFS integration services would time out when the submitted eFS account had been locked out (usually due to too many login attempts with an incorrect password). They will now return Error Code 79 in this situations, “eFS Account Locked. Please reset password through eFS website.”
• The Attach Service Contact service will now return Error Code 80 when appropriate, “Service Contact already attached to party”.
• The Subsequent Filing service is now able to return two new Errors when appropriate: Error Code 77, “Invalid or Inactive PaymentID”, and Error Code 78, “PaymentID provided belongs to another firm”.

 

Query Services

Document Get
Previously, there would be situations where an Error Code 3 would be incorrectly returned for "Proposed Order or Document" case events. (Error Code 3 is that a case event has more than one associated document). These false errors should no longer occur.
Previously, there would be situations where a Document Get request would time-out when the case could not be found. Partners should now more consistently get Error Code 2 in these situations (CaseTrackingID not found).
Previously, in non-production environments only a fraction of documents that were returned in a Filing List Response message were actually able to be retrieved in a Document Query message. All should now be able to be retrieved.

 

Integrated eFiling

Hearing E-Files
The Hearing E-File services will now return a SOAP Fault of “Case Not Found.” when a case matching the provided Court File Number cannot be found.

Attorney Assignment
A fix was added to E-filing Attorney assignment to handle uncommon suffixes.

Response Message Processing
An internal validation check has been implemented to prevent response messages that were produced in a non-production environment from being published to a partners production application. 
 

Point-to-Point Data Passes

MyMnConservator (MMC)
An internal change was made to better handle situations where Account hearings are scheduled or held on cases that are not in MMC.

 MyMnGuardian (MMG)
To better support the design of MMG, the messages sent from MNCIS to MMG when a qualifying letters event is entered now include the current known name for the parties rather than the primary names on the case.

 

CourtXML

Vehicle Makes (VehicleMakeText)
Effective June of 2020, MNCIS will be updated to use National Crime Information Center (NCIC) vehicle make values.
This change will allow more detailed and accurate information regarding vehicle makes to be stored in MNCIS and will help align vehicle-make information in MNCIS with information used by other criminal justice partners.
This impacts both inbound and outbound integration services:

• Citations
  • CitationVehicleInType
• Complaints
  • ComplaintVehicleType
  • InitiateCriminalCaseVehicleType
• Case Notifications
  • CaseNotificationVehicleType
• Bond Notifications
  • BondNotificationVehicleType
• CaseGet
  • CaseGetVehicleType
• Simple type and companion file
  • VehicleMakeTextType.xsd
  • VehicleMakeTextType.xml

 
Important Note: This change will be part of the June 2020 Integration Release, but is available now for testing in our DEV environment.  It will not be available for testing in our QA environment until mid-May 2020.
 
As of the June 2020 release, vehicle makes submitted in efiles must reflect the updated values found in the VehicleMakeTextType Simple Type in order to file a case in MNCIS.  Notifications and query responses will contain NCIC vehicle makes.

return to top

Court Integration Services Release 67

Environment(s): Production
Effective Date/Time: Thursday, December 5, 2019 at noon
To: Integration Group Contacts
Purpose: Notify Court Integration Services consumers of an upcoming update.
Details: The following updates will be applied to Integration Services:
 

DVS Certificates of Conviction Data Pass

• Enhancements were made to include a new CDLHolderFlag element in the pass.  The additional data, based on the MNCIS case flag (CDL Holder), will assist DVS in processing convictions.
• Conviction messages will now be sent to DVS when non-conviction dispositions are modified to Convicted.  This change will increase efficiency and timeliness in reporting convictions.

DVS DL Suspensions/Reinstatement Data Pass

DL messages will now be sent to DVS when non-triggering case events are modified to triggering case events.  This change will increase efficiency and timeliness in reporting DL suspensions/reinstatements/No Proof of Insurance.
 

MyMnConservator (MMC)

A fix was made to Edit 47 (Letters of conservatorship event linked to an inactive conservator or a non-conservator party) to correctly handle instances where multiple parties are associated with a qualifying letters case event and the parties do not all have a conservator connection.

This means an edit failure will no longer be produced when the conservator and guardian on the case event are different parties.
 

MyMnGuardian (MMG)

A fix was made to Edit 69 (Letters of Guardianship event linked to an inactive guardian or a non-guardian party) to correctly handle instances where multiple parties are associated with a qualifying letters case event and the parties do not all have a guardian connection.

This means an edit failure will no longer be produced when the guardian and conservator on the case event are different parties.
 

Protection Orders (OFP and HRO)

Changes are implemented for Protection Orders in MNCIS in preparation for automating the sending of Harassment Restraining Orders (HRO) to the BCA and NCIC. The Order for Protection (OFP) integration will remain essentially the same but will now include HROs. The HRO pass will include the document images associated with the HRO.

• BCA Schemas
  • New schemas introduced for HRO processing which includes document images.
• MNCIS Custom Edits
  • Language modified for custom edits that apply to both OFP and HRO.
  • New custom edits are introduced for both OFP and HRO.
• MNCIS Edit Failures
  • Current OFP messages expanded to include HRO.
• Reports
  • MNCIS reports will be modified by local courts to include HRO similar to OFP.
  • Data Quality reports will be modified to include all PO types.
  • DSS custom reporting changed to include all PO types.
• Validation
  • Current data validation processes between agencies are modified to include HRO in similar manner as OFP.

Notifications

Case Notifications

Probation Order
Previously, the CaseEventDate for a “Discharge from Probation or Monitoring” case event would often be the end of the probation or monitoring period, rather than the date the Discharge event was added to the case. As of November 1st, the CaseEventDate for “Discharge from Probation or Monitoring” events is always the date the Discharge event is added to the case, which is often approximately 6 months after the end of probation or monitoring. Minn. Stat. § 609.135, subd. 2(f) (requiring that "defendant shall be discharged six months after the term of the stay expires").

Charge
The Charge Notification has been updated to include an additional variation of charges being deleted from a case in MNCIS.
 

EFS Integrations

Our services which integrate with eFS are still in pilot and only available on a limited basis. Any expansion of these services will be announced in a future release.

ECF Filing Review Service

• Creation of a User Authentication service to authenticate an eFS user and return a Password Hash which can then be used by the partner agency in lieu of that user's eFS Password for the remainder of the day.
• Updated the Subsequent Filing service to accept the Password Hash returned by the new User Authentication Service.

ECF Court Record Service

• Updated services to accept the Password Hash returned by the new User Authentication service.
• Renumbered error messages to provide consistency across eFS Integration Services.
• The Service Information Query Service no longer requires eFS credentials.

return to top

Court Integration Services Release 66

Environment(s): Production
Effective Date/Time: Thursday, September 19, 2019 at noon
To: Integration Group Contacts
Purpose: Notify Court Integration Services consumers of an upcoming update.
Details: The following updates will be applied to Integration Services:
 

Queries

Case Get
When using an Agency Control Number or Citation Number as selection criteria in a Case Get request, an Agency ORI is required. We have heard from our partners that they are sometimes provided one of these numbers without knowing which agency it belongs to. For these situations, the Case Get service will now allow for a value of "All" to be submitted as the Agency ORI. Note, this may result in multiple cases being returned, so it is recommended to still use a specific Agency ORI value when possible.

Document Get
The Document Get query service has been updated to:

• Fix an internal issue that prevents partners from retrieving documents in certain situations.
• Better handle errors when there are problems with multiple documents on a case.

Notifications

Case Notifications

Probation Order & Probation Report 

• The Probation Order notification has been expanded to include the following case events: 'Probation Violation Warrant,' 'Probation Violation Summons,' and 'Probation Violation Order for Detention.'
• The Probation Report notification has been expanded to include the following case events: 'Probation Violation Report' and 'Proposed Probation Violation Summons or Warrant.'

• Impact:
  • Increased access to information.  This change provides notification to subscribers when Courts enter these case events in MNCIS.  Partners may choose to consume this information or filter these out.
  • Increased message volume (depending on individual partner subscriptions and local practices for using these case events).

Integrated E-Filing

Hearing EFiles 

• Currently, when a partner tries to schedule a hearing to an obsolete hearing type, they will get an error message of "No Matching Court Session for the parameters provided." Partners will now receive a more specific error message of "Submitted Hearing Type is obsolete".
• Currently, attempts to reset a hearing to a calendar at a different node fail, but no response message is returned to the partner. Partners will now receive a response with an error message of "Cannot reset a hearing to a calendar at a different node."
• Currently, partners incorrectly get the error "Setting is already continued" when trying to reset or cancel a setting which was created by another setting being rescheduled. These EFiles should now succeed.
• Currently, attempts to cancel or reset a hearing which does not belong to the indicated case could fail with no response message being returned to the partner. Partners will now receive a response with an error message of "Hearing is for a different case".
• Partners will now receive the more specific error message of "Setting not found on indicated hearing" when the provided SettingID is not found on the hearing indicated by the provided HearingKey.

Citation NameGet Processing
The vehicle registered-owner lookup service is updated to:

• Better handle inconsistencies in source-system data.  This change addresses incomplete address information.
• Prevent internal errors:
  • On subsequent lookups when a case created as a result of a parking citation has been deleted in MNCIS.
  • When non-MN source systems experience outages.

Juvenile eCitation and ePetition
Parent Guardian Relationship Types

• The schema enumerations list for relationship types is expanded from: Father, Mother, and Other. The new accepted values are: Father, Mother, Step Father, Step Mother, Grandparent, Relative, Guardian, Foster Parent, Other.
• This is to synchronize the values used successfully by Hennepin Justice Integration Program with State Court Integration.
• eCitation vendors already using the values in the HJIP schema will not need to make any changes.

Impact:
The following schema versions will be updated:

• JuvenileCitationDocument_3_4
• JuvenilePetitionDocument_3_4

Note: Juvenile eCitations are currently only deployed in a pilot in Hennepin County. Juvenile ePetitions will be deployed statewide with BCA eCharging in the future.
 

Point-to-Point Data Passes

MARS to MNCIS
In order to prevent duplicate records from being created, there will now be a short delay before attorney updates are added to MNCIS.

MyMNGuardian
MyMNGuardian (MMG) is the Judicial Branch's new guardian application that will be rolled out later this fall.  New integration services have been developed to allow an internal exchange of information and documents between MMG and MNCIS regarding Guardianship cases and the parties on those cases.  This exchange of information will increase efficiency for court staff and guardians.

Statute Service
Services were updated to utilize a newer version of the BCA's Statute Service (v.7).

GJudge to MNCIS
The integration between GJudge and MNCIS is being updated to use a consistent format when populating the internal description field.

DANCO pass to BCA
Additional logic is being put into place to reduce the number of instances in which court staff need to take additional actions for a DANCO update to pass to the BCA.

return to top

Court Integration Services Release 65

Environment(s): Production
Effective Date/Time: Thursday, June 20, 2019 at noon
To: Integration Group Contacts
Purpose: Notify Court Integration Services consumers of an upcoming update.
Details: The following updates will be applied to Integration Services:
 

Integrated eFiling

General
Internal processing improvements to reduce the likelihood that submitted eFiles will timeout.
 

Integration Access Rights

Minnesota Court Information System (MNCIS) data:

Party Address [PartyAddressType]

Partner accounts are updated to exclude confidential addresses.  Addresses marked as confidential in MNCIS are not publicly accessible.  Internal changes were made in previous releases to support this restriction.

Messages on Case Notification schema version 3:8, Case Get version 3:8, and Bond Notification version 3:5 include a confidential address indicator.  This indicator is set to "true" for confidential addresses, but the address itself is not included.  Messages publishing on earlier schema versions will not include the confidential address or the indicator.
 

Notifications

Case Notification Charge Type
Charge/OffenseLocationText: special characters that prevent case notifications from publishing are being removed.

Hearing Trial Setting Notification
Hearing notifications are updated to handle the new hearing-result types being added to MNCIS in the near future.  The new hearing-result types are more descriptive versions of the current result type of "Held" but the published message structure and content are the same.  Future schemas may be updated to reflect the new result types.

Transport Order
Transport Order notification is updated to include two new MNCIS case events: 'Order to Transport-D16' and 'Order to Transport-Juvenile'. These were added to MNCIS on April 1, 2019. These new case events are now included in addition to the existing 'Order to Transport' case event.
 

Queries

Case Get

Case Get Charge Type
Charge/OffenseLocationText: special characters that prevent responses from publishing are being removed.

Case Get Citation Document Type
Incident/OffenseLocationText: special characters that prevent responses from publishing are being removed.

Hearing Trial Setting
Case Get replies are updated to handle the new hearing result types being added to MNCIS in the near future.  The new hearing result types are more descriptive versions of the current result type of "Held" but message structure and content are the same.  Future schemas may be updated to reflect the new result types.
 

Custom Integrations

MyMnConservator (MMC)
The new service developed to notify MMC of Account Hearings is updated to handle the new hearing-result types being added to MNCIS in the near future.  The new hearing-result types are more descriptive versions of the current result type of "Held" but published message structure and content are the same.

Order for Protection (OFP) 
Case Event of 'Service Message Rejection Notification' added when service is attempted by the MN Bureau of Criminal Apprehension, but fails due to bad data.

Person Contact Information Logic Update 
Logic update on the Person Contact Information eFile to stop overriding existing Email and phone numbers with the same Email and phone number on eFile submissions (making it look "updated" on the party record in MNCIS, when it was not).

Person Demographics Logic Update 
Logic update to the party demographic eFile to allow an existing self-reported race value of "Unavailable" to be overridden with another race value.

Photo Get (Domestic Abuse No Contact Orders)
The Photo Get service now retrieves photos for parties with special characters in their surname.
 

Edit Failures

Charge Disposition
The Criminal Disposition edit failures are updated to handle an occasional internal data issue that had been preventing some edits from clearing after the appropriate resolutions steps were taken.

Interpreter
A new edit failure will trigger when more than one language is requested on the same event.  This will occur when 2+ parties are selected and they do not all speak the same language.

return to top

Court Integration Services Release 64

Environment(s): Production
Effective Date/Time: Thursday, March 21, 2019 at noon
To: Integration Group Contacts
Purpose: Notify Court Integration Services consumers of an upcoming update.
Details: The following updates will be applied to Integration Services:

Schemas
Criminal Complaint and Petition Supplemental Document
Added a new document enumeration to the existing service: Petition. This will allow BCA eCharging to submit the PDF version of a juvenile petition to the associated MNCIS juvenile court file in the same manner adult complaint PDFs are currently submitted upon case initiation in MNCIS. This is part of a joint project between the BCA and the court. The final project will deploy at a later date.

Juvenile ePetitions
Added a new eFile service and schema to support submission of juvenile ePetitions. This will be used by BCA eCharging to initiate court files in juvenile court. Prosecutors will submit new court files initiated by a juvenile petition in a similar manner to how adult complaints are currently submitted to the court. This is for a joint project between the BCA and the court. The final project will deploy at a later date.
Case types:
 

• Delinquency
• Delinquency-Felony
• Extradition-Juvenile
• Juvenile Petty Offense
• Juvenile Traffic

Validations:
 

• Age validations will be in place similar to adult citations, juvenile citations, and adult complaints.
• Case type determination: Extradition-Juvenile and Delinquency-Felony will be programmatically determined by the court.
• Current validations enforced on adult complaints will be enforced when applicable (e.g. eFile requirements, offense codes, simple type enumerations).
• Current validations enforced on juvenile eCitations (Hennepin pilot) will be enforced when applicable (e.g. parent/guardian).

Impact:
The following schema versions will be used to support the eFiling of Juvenile Petitions:
 

• JuvenilePetitionDocument_3_4 (NEW - similar to adult complaint use of CriminalComplaintDocument_3_4)
  • CourtXML_3_2 (also used for adult complaints)
• ComplaintSupplementalDocumentAdd_3_1 (already in use by BCA eCharging for adult complaints)
  • CourtXML_3 (already in use by BCA for adult complaint documents)

 CourtXML

• The "ParentGuardianCustodian" subject-party definition was expanded to include parties connected to cases as 'Legal Custodians.'  This impacts case notifications and CaseGet responses.

Queries
DocumentGet
 

• Refined document-query responses to be more timely and descriptive when a document does not exist.  The issue where documents do not exist is typically limited to non-Production MNCIS environments.
• Increased flexibility of request-message validations.  The service now allows the submission of either the Electronic Court Filing (ecf) or the NIEM Core (nc) schema element for EntityOrganization/EntityPerson.

 Case Search By Party
 

• The Case Search By Party service has a default Case Match Limit of 1,000 cases. When the number of matching cases exceeds this limit, the service will now return the newest matching cases.

CaseGet
 

• CaseGet responses now include parties connected to cases as 'Legal Custodians' in the SubjectParties "ParentGuardianCustodian" element.

Notifications
CaseNotifications
 

• The SubjectPartyNotification now includes parties connected to cases as 'Legal Custodians' in the "ParentGuardianCustodian" element.

E-Files
 E-File Processing Improvements
 

• An internal change was made to our E-File processing methods to help prevent errors previously caused when a space was included at the beginning or end of a name. Only impacts E-Files which initiate criminal cases.

 ECF Filing Review Service
 

• Additional changes to support the ability to eFile and eServe documents into eFS for pre-existing court cases.
  • The ability to eFile and eServe documents is still in pilot and only available on a limited basis. Any expansion of this service will be announced in a future release.

Custom Integrations
 DVS Certificates of Conviction and DL Suspensions/Reinstatements
 

• An internal change was made to use an automated DVS service to update integration account credentials.  There is no impact to the functionality of either data pass.

MyMnConservator (MMC)
 

• A new service was developed to notify MMC when an Account Hearing (ACT) is scheduled or updated in MNCIS.
• An enhancement was made to allow MMC to submit the 'CARP Account Summary' document to MNCIS.

Integration Access Rights
MNCIS data:
 

• Party address [PartyAddressType]: Addresses marked as confidential in MNCIS are not publicly accessible.  Internal changes were made to support this restriction.  Partner accounts will be updated in the June 2019 Integration release to exclude confidential addresses.  Confidential address indicators are available in Case Notification version 3:8, CaseGet version 3:8, and Bond Notification version 3:5.

MNCIS documents:
 

• Beginning December 1, 2018 certain partners are allowed access to certain confidential documents on non-Child Protection/non-Paternity family cases.  A new integration access right was developed to support this access.
• A new integration access right was developed to support providing the 'Application for Public Defender' document to the State Board of Public Defense.

 Service Related
 

• Party Telephone Number: An internal change was made to support setting the 'Invalid' indicator on telephone numbers when they are added to MNCIS.

return to top
 

Court Integration Services Release 63

Environment(s): Production
Effective Date/Time: Thursday, December 13, 2018 at noon
To: Integration Group Contacts
Purpose: Notify Court Integration Services consumers of an upcoming update.
Details: The following updates will be applied to Integration Services:

New Schema Versions
A new base version of Court Extensible Markup Language XML 3 (CourtXML 3) was created to accommodate enhancements and to correct known issues.
This new base schema is: CourtXML_3_3.xsd. These changes impact the Case Notifications, Case Get, and Bond Notification services.  

Changes

• Hearings
  • HearingTrialType: Added optional HearingCommentText element
• Party related
  • CaseRespondentType: Added optional PersonBirthDate and PartyDeathDate elements
  • Added new CaseDecendentType
  • PartyAddressType: Added required confidentialIndicator attribute
  • PartyAddressBaseType: Changed choice indicator from required to optional (to prepare for a future project).
• Citations
  • CitationReferenceType: Added Citee container that includes partyKey and citee involvement type elements
• Conditions
  • ConditionType: Added optional ConditionLocation and optional ConditionAmount elements
• Judgments
  • Added new complex type: ProbateJudgmentType
• Global Elements and Annotations
  • Replaced select complex types with global elements and updated annotations
  • Updated CaseTitle global element to include datatype and min/max length

Other changes 
Case Notifications

• New notifications:
  • ProbationReport (case-event based)
  • CivilCommitment (case-event based)
  • CaseInitiationProbateNotification
  • CourtDecisions\Probate Judgment
• Changes:
  • Public Defender Order: Removed Warrant
  • Probation Order: Added optional ChargeReference element to CaseNotificationProbationOrderEventType
  • SubjectParty: Added new CaseDecedent
  • Charges: Added optional WildlifeRestitutionAmount element to CaseNotificationChargeType
  • Court Decisions: Removed sentenceEventKey attribute from CaseNotificationtSentenceDispositionType and CaseNotificationSentenceAdjudicationType

Case Get

• CaseInformation\CourtDecisions: Added new ProbateJudgment
• CaseInformation\SubjectParties: Added new CaseDecedent
• CaseInformation\CourtDecision\AdultSentence: Removed sentenceEventKey attribute
• CaseInformation\CourtDecision\AdultDelinquencyDisposition: Removed sentenceEventKey attribute
• Added optional WildlifeRestitutionAmount element:
  • CaseInformation\Charge
  • CaseInformation\ChargeDispositions\ChargeDisposition\Charge
  • CaseInformation\ChargeDispositions\ChargeAdjudication\Charge
  • CaseInformation\CourtDecisions\AdultSentence\Charges\ChargeDisposition\Charge
  • CaseInformation\CourtDecisions\DelinquencyDisposition\Charges\ChargeAdjudication\Charge
  • CaseInformation\Bond\Charge

Bond Notifications

• Charges: Added optional WildlifeRestitutionAmount element to BondNotificationChargeType

Impact: 
As a result of these changes, the following new schema versions will be implemented with Release 63:

• CaseNotification_3_8.xsd
• CaseGet_3_8.xsd
• BondNotification_3_5.xsd

Prior active versions of schemas will remain active and unchanged. They can be used after the new versions are in production.  
 
CaseGet and Case Notifications
'AllCountsDisposed' indicator (within CaseHeaderType) is updated to handle all variations of amended dispositions.  This fixes the issue where the indicator was not accurate in certain scenarios.

Citations

• A fix to eCitations is implemented to prevent invalid messages from disrupting the court's citation processing service. This will prevent certain delays in citation processing.
• Additional retry processes will be deployed to handle new system failures within Odyssey to prevent citations from rejecting to e-filers.
• Case Get responses are updated to handle unexpected citee height entries. A future release will prevent the erroneous incoming data from populating MNCIS.
• Citee address information will be fixed for one version of addresses. The fix will allow complete update of citation citee address information on both the party and citee tabs. Currently, only the party tab is complete.
• A new case event and related citation data document will be added to cases initiated by citation. The document will include data currently only visible on the Citation tab of Odyssey Assistant. This new document will allow consistent visibility of citation information across all court applications. This is preparation for a new project and a final implementation date will be set later.

eFiles
Warrant Status eFile Service:
Previously, the Update Warrant Status Service was not always checking to ensure that the submitted Current Warrant Status Date and Type were accurate. After this fix, those checks should now always be performed.
 ECF Filing Review Service:
The ECF Filing Review Service is being expanded to provide court partners with an integration service able to eFile and eServe documents into eFS for pre-existing court cases.
This expanded functionality is currently available on a limited basis (pilot-partner agencies only). Any expansion of the service will be announced in a future release.

Custom Integrations
DANCO pass to BCA
Two new edit failures, 70 and 71, are being added to help in situations where the Domestic Abuse No Contact Order previously passed to the BCA but has since expired.
Interpreter Edit Failure Updates
Updated edit failure logic to prevent edit failures from occurring on case events copied over from transferred cases.
Updated logic on Edit Failure #66 (Missing Party Language) to NOT apply on deleted parties.


return to top

Court Integration Services Release 62

Environment(s): Production
Effective Date/Time: Thursday, September 20, 2018 at noon
To: Integration Group Contacts
Purpose: Notify Court Integration Services consumers of an upcoming update.
Details: The following updates will be applied to Integration Services:

​Integrated eFiling
HJIP - Juvenile SILS Integration
Changes needed to assist the Fourth District in a Technology Grant project are enabled.  HJIP will be submitting additional SILS Case Cross Reference Numbers and Identifiers when their project deploys later this year. Once HJIP converts and deploys their project, Hennepin's juvenile court files will contain the same types of cross reference numbers seen on their adult cases in MNCIS since 2007. 
Batch Citation Processing Improvements
Changes to our batch citation processing method to help citations enter MNCIS more quickly.
Document File Stamp Format Change
A new statewide file stamp is being implemented to reflect the MN Judicial Branch's goal of oneCourtMN and facilitate centralization efforts. The new stamp does not include a district or county name.

Edit Failures
Request for Interpreter - No Hearing Match  
This edit failure will trigger when a Request for Interpreter case event's due date does not align with an existing hearing date.  This edit failure enforces the current CAP rules and prepares court staff for the upcoming IRMA integration.
Request for Interpreter - Missing Party Language
This edit failure will trigger when any party selected on a Request for Interpreter case event is missing a primary language.  This edit failure enforces the current CAP rules and prepares court staff for the upcoming IRMA integration.
Cancel Interpreter/​Modified Interpreter Hearing Date - Unrelated to Request for Interpreter event
This edit failure will trigger when a Cancel Interpreter or Modified Interpreter Hearing Date case event is NOT related to a Request for Interpreter case event.  This edit failure enforces the current CAP rules and prepares court staff for the upcoming IRMA integration.

Custom Integrations 
DVS Certificate of Conviction Data Pass

• Due to legislative changes, updates were made to send additional certifiable convictions on boats, snowmobiles, and all-terrain vehicles.
• Technical  changes were made to support DVS' transition to their new driver system (scheduled to occur October 1, 2018).

BCA NICS Pass
The NICS pass to the BCA will trigger on the new disposition value of "Acquitted, cognitive impairment" (scheduled to start on September 1, 2018)

return to top

Court Integration Services Release 61

Environment(s): Production
Effective Date/Time: Thursday, June 21, 2018 at noon
To: Integration Group Contacts
Purpose: Notify Court Integration Services consumers of an upcoming update.
Details: The following updates will be applied to Integration Services:

​Queries
Document Get
A monthly report was developed to return all documents received through the new document query service (DocumentGet) in order to support internal audit processes.  The availability of DocumentGet remains limited to pilot-partner agencies only.
Case Search By Party
Case Search By Party will now return up to 1,000 matched cases. (The old limit was 100 cases) 

Notifications
Case Notifications
Public Defender Order Notification
The Public Defender Order notification now correctly handles deleted bonds.  This fixes the issues related to deleted bonds where messages either did not publish or published and included deleted bonds.

Integrated eFiling
Biometric Collection Status
The Fingerprints Required by Statute case flag will remain on a case if a Fingerprints Taken case flag is submitted.
Court Record Service
 Two new integrated efiling services (AttachServiceContact and DetachServiceContact) were developed to provide partners with a system-to-system method to attach and detach service contacts to cases in eFile and eServe. AttachServiceContact and DetachServiceContact will initially only be available on a limited basis (pilot-partner agencies only); the service is not yet available upon request. Any expansion of the service will be announced in a future release.
Warrant Status Error
Updated WarrantStatus_3.1 Efile error message to indicate either the status or date of the current warrant is incorrect.  The previous error message indicated just the date was incorrect.
PersonDemographics_3_1
Updating Efile program to reference schema with Enumerations and require a unique EFile ID.

Custom Integrations
DANCO pass to BCA
Minor internal tweaks are being made to the Domestic Abuse No Contact Order pass to the BCA which should result in fewer DANCO sentence conditions needing to be repassed by court staff.
OFP pass to BCA
Minor internal change to prevent multiple service/hearing messages to be sent to the BCA.
 
return to top
 

Court Integration Services Release 60

Environment(s): Production
Effective Date/Time: Thursday, March 15, 2018 at noon
To: Integration Group Contacts
Purpose: Notify Court Integration Services consumers of an upcoming update.
Details: The following updates will be applied to Integration Services:

Integrated eFiling
Document eFile Validation
Document submissions will be validated to reduce the chance of multiple copies of a document ending up in Odyssey. When an appellate, citation, or complaint document is submitted, it will be validated to see if the eFile was previously submitted. If the subsequent submission is a duplicate, the message will be rejected rather than accepting. The rejection message will indicate whether the previous submission was already accepted or already rejected.
Expand Attorney Assignment to Non-Criminal (Chips cases)
The court is expanding the Attorney Assignment efile to schema to include non-criminal (CHIPS) cases.  This will require having partykey or partyid at the time of the attorney assignment.  The new version of the efile schema, Version 3.2, has been released.  Version 3.1 will continue to be available as well.
 
Notifications
Case Notifications
Public Defender Notification
An additional case event will now trigger the Public Defender notification. The additional case event is:
 - Order Denying Public Defender (ORDENYPD)
This case notification will continue to publish statewide as it always has when the case events, Order Granting Public Defender and Public Defender Discharged, are updated on any case.
Agencies subscribed to this service will notice an increase in volume and reasons for the messages.
Hearing Trial Setting Notification
The actual court reporter now publishes correctly when different than the scheduled court reporter.
Commercial and Hazardous Material Vehicles 
Notifications and CaseGet query responses: the Commercial Vehicle Indicator and Hazardous Materials Indicator now  populate within the case information: Case/Charge/Vehicle.
Charge Disposition Notification
New Criminal Disposition edit failures were developed to prepare for the retirement of the BCA Criminal History Pass edits.  The new edit failures focus on control number, controlling agency, and defendant date of birth.  The new edit failures will not be activated in the Integration Messenger until the current Computerized Criminal History system (CCH) pass is disabled.
Document Notifications
A new document notification is available to provide Sentencing Order images.
 
 Custom Integrations
MyMnConservator (MMC)
Internal enhancements:

• MMC requests for MNCIS information were separated from MMC requests to update MNCIS.  This change should improve service to the MMC application.
• Changes were made to the processing of MMC requests that update MNCIS party information.

return to top
 

Court Integration Services Release 59

Environment(s): Production
Effective Date/Time: Tuesday, December 19, 2017 at noon
To: Integration Group Contacts
Purpose: Notify Court Integration Services consumers of an upcoming update.
Details: The following updates will be applied to Integration Services:

Integrated eFiling 
Citation NameGet Processing
The vehicle registered owner lookup service is updated to:

• Better handle inconsistencies in source-system data.  This change corrects the issue of partial names for some registered owners of leased vehicles.
• Prevent internal errors when non-MN source systems experience outages.
• Include Administrative Rules (under current offense eligibility criteria) and offenses in the Fish & Wildlife Parking offense group (new eligibility criterion).

Note: these updates are in Production (as of 10/30/2017, 9:00PM).
 
Notifications
Case Notifications - No Contact Order 
There was a rare situation where removing a No Contact interim condition in a certain way would prevent a notification from being published. This should no longer happen.

Case Notifications - Public Defender Notification
Published warrant information will be reduced in new PD notifications. All warrants will continue to publish in the Notification Header but all status details of all warrants will no longer be included in the separate warrant node. When a party has extensive warrants, this was causing messages to fail to publish.
 
Custom Integrations
Domestic Abuse No Contact Order (DANCO) - pass to BCA
There was a rare situation where removing a DANCO interim condition in a certain way would prevent a message from being sent to the BCA. This should no longer happen.

OFP Service - Inactivations
This is a minor issue the integration team recently identified.  When an order is both served and expired at the same time in MNCIS - only the service was sent and the expiration was not sent.  Integration fixed the service so both actions are sent to the BCA.

Secretary of State pass
Edit failure 64 has been created to catch when an inadvertent case event in a criminal case attempts to update the voting rights of a juvenile.
 
Schemas
Court XML Schemas
Changes are only to annotations for purposes of clarification and in response to partner questions.  There are no design changes and no impact on the messages partners receive.

Updated annotations on:

• Driver's License Number [PersonDriverLicenseID]
• Phone Number [PartyTelephoneNumber]
• Email Address [PartyEmail]
• Scars/Marks/Tattoos [PersonPhysicalFeature]
• Caution Flags [Cautions]
• Victim and Witness [Victim, Witness, and PartyCaseAssociationText, where applicable]

Affected Base and Query Schemas:

• CourtXML_3_2.xsd
• CaseGet_3_7.xsd
• CaseSearchByParty_3_2.xsd

Updated annotation on:

• Reporting Agency Control Number [ReportingAgencyControlNumber]
  • Citation/Incident/ReportingAgencyControlNumber
  • Charge/Report/ReportingAgencyControlNumber

Affected eFile Schemas:

• CitationDocument_3_6.xsd
• JuvenileCitationDocument_3_4.xsd
• InitiateCriminalCase_3_4.xsd
• CriminalComplaintDocument_3_4.xsd
• TabChargeDocument

 return to top

Court Integration Services Release 58

Environment(s): Production
Effective Date/Time: Thursday, September 28, 2017 at noon
To: Integration Group Contacts
Purpose: Notify Court Integration Services consumers of an upcoming update.
Details: The following updates will be applied to Integration Services:

Integrated eFiling
Appellate Document Add – Case Security Changes
A new process based on MNCIS settings will be used for determining the document security when adding Appellate Documents. Case Flags will no longer be added to Confidential or Sealed cases. Cases having Criminal Sexual Conduct Statutes will no longer be an exception for security on incoming documents.

Citation Document Add Security
A new process based on MNCIS settings will be used for determining the document security when adding Citation Documents.

Citation Name Get Processing
Several changes were made to improve internal processing.

Citation Routing in Ramsey County
In custody eCitations for Ramsey County will now be sent directly into MNCIS as they are for the rest of the state. The validation check for the In Custody indicator for Ramsey County eCitations will no longer be enforced. This is preparation for retirement of legacy Ramsey systems. This change should not be noticeable to citation submitters. 

Complaint Document Add – Case Security Changes
A new process based on MNCIS settings will be used for determining the document security when adding Complaint Documents. Case Flags will no longer be added to cases having Criminal Sexual Conduct statues. Cases having Criminal Sexual Conduct Statutes will no longer be an exception for security on incoming documents.

Import Self-Reported Race and Ethnicity
A new service was created to populate the self-reported race and ethnicity values on the MNCIS party record. This service will initially be used by the Second District to allow check-in kiosks to replace the current paper process.

Juvenile Citation Routing in Hennepin County
An internal Odyssey and Integration processing change will be implemented to allow for separation of juvenile and adult court eCitations. This is preparation for statewide deploy of juvenile eCitations. This change should not be noticeable to submitting eCitation partners or Hennepin County Juvenile Court.

Notifications
Case Notifications and Queries
Case Flag - Fingerprints Needed. The MNCIS description currently published when a case flag, 'Fingerprints Needed', exists on a case is changing to 'Fingerprints Required by Statute'.  The codeword will remain the same: FINGERN.

Case Notifications
A change was made to prevent internal failures when criminal cases are undeleted or unexpunged.

Document Notifications
Documents will no longer publish when more than one non-obsolete document is linked to the associated case event.

Queries
Document Query Service
A new query service (DocumentGet) was developed to provide partners with a system-to-system method to obtain documents from MNCIS.
DocumentGet will be available on a limited basis (pilot-partner agencies only); the service will not be available upon request.  Any expansion of the service will be announced in a future release.

Integration Access Rights
Case Security
Internal improvements to how non-standard case security groups are handled.

Integration Access Rights
A fix was made to the document access rights that provide access to confidential documents on adult criminal cases.

Custom Integrations
OFP Edit Failure #63 Fix
A change in edit failure #63 for court staff to prevent incorrect edit failure generation on non-DMA cases.

Tax Court Petition Document Notification
A new document notification allowing Tax Court to receive the Tax Petition (PEPROPTAX) from MNCIS into their new Case Management system (C-Track).  IMPORTANT: The CURRENT process for processing Tax Petitions with the Tax Court should continue until notified otherwise.

Schemas
Case Initiation eFiling Schema Changes
The draft schemas published in Release 57 are now available for partners to test eFiling into the MNCIS Development and QA environments.
These updates are currently available for testing in our Dev and QA environments.  These updates should not require any system downtime to implement in production.  Please let me know if you have any questions.

return to top
 

Court Integration Services Release 57

Environment(s): Production
Effective Date/Time: Thursday, June 22, 2017 at noon
To: Integration Group Contacts
Purpose: Notify Court Integration Services consumers of an upcoming update.
Details: The following updates will be applied to Integration Services:

Integrated eFiling
Adding New Process for a Corrections Document - PSI (E-Filing)
A new process will be available for the electronic filing of the Correction's Probation Document, 'Presentence Investigation Report'. The new Integrated eFiling process will work in parallel with the current EFS process to allow for an easier transition. The default document security will be based on the MNCIS defaults.

Inbound Corrections Document Security (E-Filing) 
There is an internal improvement on assigning default document security for Correction's documents: 'Probation Violation Report' and 'Proposed Probation Violation Summons/Warrant'. The default document security is now based on the document security setting configured within MNCIS.

Inbound Documents on Converted Cases (E-Filing)
There is a change in the process when documents are added to MNCIS converted cases. Previously, converted cases that were showing as 'duplicates' in MNCIS were unable to be found when adding documents through the eFiling process. This prevented cases from receiving 'document' updates. Now these cases are able to take documents.

eCitations

• Law Enforcement Observed Race - This information is collected by some law enforcement agencies and submitted to the court but not consistently.  Because the submission of race data by law enforcement on citations is no longer required by any court rule, and because the Law Enforcement Observed Race data is not utilized for data collection or reporting, or any outbound integration messages, the data will no longer populate the Odyssey Citation record.  There is no impact or change to the current processes for recording Observed Race or Self-Reported Race on party records.  Integration eFilers do not need to make any changes. Appear by Date - Odyssey is now configured for all counties to compute this date automatically. Inbound Appear by Dates will no longer be processed, and the validations for Appear by Date have been removed.

eFile System Rejection Reprocessing
Improved internal eFile system processing of eFiles to Odyssey. Added specific rejection messages that will be tried for reprocessing. This will result in a reduction in error messages to eFilers due to Odyssey system interruptions.

ProfessionalPartyAssignment Enumeration -
Adding Examiner as an enumeration for the ProfessionalPartyAssignment eFile service.  This is for the future pysch/interpreter project.
 
Notifications
Case Notifications
The civil "Forfeiture" case notification topic has been expanded to include 'Conciliation – Forfeiture' cases.  Partners subscribing to "Forfeiture" notifications will now receive messages for Forfeiture and Conciliation-Forfeiture cases.

Document Notifications
Changes were made to which Electronic Court Filing (ECF) schema elements are used for the document version ID and confidential document indicator.

Hearing Trial Setting Notifications
Hearing Notifications will no longer mix scheduled end times with actual start times. No HearingDatetimeEnd element will be returned when the actual start time is known but the actual end time is unknown.

Queries
Case Search By Party
In an effort to improve performance and functionality, an internal rework of the Case Search By Party service has been completed.
Primary enhancement:

• The 100 case limit will now be enforced after all Access Rights and Request Restrictions have been applied.

Bug fixes:

• Restrictions based on Party Case Association and Party Base Case Association will now be accurately applied for parties with multiple connections to a case.
• Inactive Person FBI ID Numbers will no longer be returned with the Current Known Indicator set to true.
• Person Prefix Names (e.g. Dr.) will now be returned more consistently.
• The format of the PersonFullName element has been updated to match Case Get and Case Notifications (i.e. Last Suffix, Prefix First Middle).

Integration Access Rights
Integration Access Rights

• Court rules and Supreme Court orders now allow certain partners access to confidential commitment (probate/mental health) cases, confidential harassment restraining order (civil) cases, and certain confidential documents on those cases.  New integration access rights were developed to support this access.
• Internal updates were made to the following: the right that controls access to Public documents; and the Commitment case notification subscription topic.

 
Custom Integrations
Court Staff Edit Failure Notifications
Added additional features for edit failure notification subscriptions:

• Ability to subscribe at District, County, or Node level.
• Ability to choose when to receive the notification.
• Reminder email if an edit failure remains outstanding after one week.

MyMnConservator (MMC)
Enhancements were made to handle the following:

• MNCIS connection type "Professional Emergency Conservator" [PEC].
• Submission of the 'Account Exam Report - Judicial Review Necessary' from MMC to MNCIS.

Internal improvements:

• Document security (MMC to MNCIS) is now based exclusively on MNCIS configuration.
• Party-update process (MNCIS to MMC) better handles updates to parties associated with a large volume of cases.

OFP Edit Failure - Case Party Connections 
New edit failure created to notify court staff when an invalid case party connection is selected on an OFP case.  The edit failure will clear when case party connection is corrected.

OFP Delete Status - Validation Query 
Updated the OFP validation logic to identify deleted OFP's as "DELETED" rather than referring to the status field value on the OFP.  No impact to court staff.
 
Schemas
New eFiling Schemas
New draft versions of eFiling schemas are now published and available online. These will be available for testing in the fall of 2017 and available in production before December 31, 2017.
New Schema Versions:

• CitationDocument_3_6.xsd (BCA eCharging and Hennepin County/HJIP)
• JuvenileCitationDocument_3_4.xsd (Hennepin County currently and future BCA eCharging)
• InitiateCriminalCase_3_4.xsd (Ramsey County only)
• CriminalComplaintDocument_3_4.xsd (BCA eCharging)
• TabChargeDocument (Hennepin County/HJIP only)

Note: the previous versions of these eFiling schema used CourtXML_3_1.xsd and the new versions will use CourtXML_3_2.xsd.  CourtXML_3_2.xsd is currently available in production and used by our latest notification and query schemas.

• Appear By Date: this is being removed since MNCIS/Odyssey now computes this date for all counties in Minnesota.
  • Citations
• CDL - Commercial DL Indicator: this is a new optional element. It will be required when an offense included in the eFiling is certifiable to the Department of Public Safety (similar to when offenses require vehicle information). If a driver holds a CDL at time of the incident, then the indicator would be set to 'True'.
  • Citations
  • Juvenile Citations
  • Complaints
  • Initiate Criminal Case
  • Tab Charges
• Fingerprints Needed Indicator: this is currently in the eComplaint schema and is now added to citations. The same logic for submission on a complaint will now apply to citations. If an eFiling includes at least one offense where fingerprints are required before inclusion of a court disposition in criminal history, this would be set to 'True'.
  • Citations
  • Juvenile Citations
• Wildlife Restitution Amount: this is a new optional element. It allows for submission of a wildlife restitution dollar amount request to the court. The offense Simple Type companion files for charging statutes, local ordinances, and administrative rules will include notation if wildlife restitution is allowed on an offense.
  • Citations
  • Juvenile Citations
  • Complaints
  • Initiate Criminal Case
  • Tab Charges

return to top

Court Integration Services Release 56

Environment(s): Production
Effective Date/Time: Thursday, March 23, 2017 at noon
To: Integration Group Contacts
Purpose: Notify Court Integration Services consumers of an upcoming update.
Details: The following updates will be applied to Integration Services:
Integrated eFiling

Case Type Determination - Extraditions
A new statute passed by the legislature is incorporated with this case type determination when eComplaints are submitted.

Citation Name Get Processing
The vehicle registered owner lookup service is updated to better handle instances where there are system delays.

Document Add – Document Security
Citation Images eFiled will have their document security set to Public 1 (PUB1) instead of Public 2 (PUB2). Police Reports will have their document security set to Confidential Agency (CONFA) instead of Confidential 1 (CONF1).

eCitations
Incident Officer Comments - This information will populate the Odyssey Citation record rather than using a case event. This was previously included and communicated with Integration Release 52 but was delayed waiting for refinements from Tyler Technologies.

Juvenile eCitations - currently a pilot project in Hennepin Juvenile Court
Parent/Guardian Details - This information will populate the Odyssey Citation record rather than using a case event. This was previously included and communicated with Integration Release 52 but was delayed waiting for refinements from Tyler Technologies.

Processes for FTP
Removed all internal jobs, access rights, and processes used previously when citations could be sent directly to the court via FTP. All agencies are now submitting eCitations via the Bureau of Criminal Apprehension eCharging (BCA) or Hennepin Justice Integration Program (HJIP).

Schedule Hearing eFile Conversion to API
An internal change for the Schedule Hearing service to use APIs. This is an ongoing effort to retire old E-File technology. This will be seamless without any change to court staff or submitters. Currently, only Hennepin County and Ramsey County use this service.
Notifications

Document Notifications
A new service was developed to provide specific documents related to certain business processes. 
The initial document notification provides warrant documents.  Additional document notifications will be developed in the future.

Wildlife Restitution
A new court decision field for entering Wildlife Restitution was introduced with Odyssey 2014.3. The code word will now publish consistently for notifications and queries.
Queries

Converted Case Numbers
This will allow users to drop preceding zeros for case numbers on TCIS converted cases, e.g. '21-K4-92-000021' may be submitted as '21K49221'.
Integration Access Rights

Case Security
Internal improvements to how non-standard case security groups are handled.
Outbound Integrations

MyMnConservator (MMC)
The MNCIS-to-MMC service is updated to send MMC the correct phone number (based on type).

Orders for Protection (OFP)  
Edit failure 62 (case party info has been updated, repass to BCA is required) is improved. Court staff will receive this prompt less often since scope is limited by filtering on relevant party type connections.

Secretary of State Voting Rights Pass (SOS)
Internal change to migrate to current software version.
These updates are currently available for testing in our Dev and QA environments.  These updates should not require any system downtime to implement in production.  Please let me know if you have any questions.

return to top

Court Integration Services Release 55

Environment(s): Production
Effective Date/Time: Tuesday, December 20, 2016 at noon
To: Integration Group Contacts
Purpose: Notify Court Integration Services consumers of an upcoming update.
Details: The following updates will be applied to Integration Services:

CourtXML
Party Address
A change was made so that the party address ‘undeliverable’ attribute will populate correctly (PartyAddress/@undeliverableIndicator).  This change is associated with a new version of MNCIS (version 2014.3) expected in January 2017.

Integrated eFiling
Attorney Assignment eFile
There was a rare situation in MNCIS where an attorney would be assigned as the lead attorney for a party multiple times. This situation should no longer cause problems for the Attorney Assignment eFile service.

Complaint Document Security - Case Flags
Internal change to no longer set a Case Flag of Review Complaint Classification in MNCIS when Document Security Classification is changed from PUB1 to PUB2.  The complaint document will still have a PUB2 classification when certain statutes exist on the case.

Tab Charges (eTabCharges are only submitted by the Hennepin County Sheriff's Jail) 
Internal change for handling of statutes to match Hennepin County's business practice.  A defect was introduced when Local Ordinances were codified statewide that negatively impacted the use of statutes on this eFiling type. This will restore previous functionality for Hennepin County's Adult Criminal Court. 

E-Filing Warrant Status

• Updated the error message ('system error') to be more descriptive when a warrant status is submitted with a date prior to the initial warrant issued date.
• A new validation was added that requires the current warrant status date to be correct in order to add the new warrant status. Prior to this only the warrant number had to be correct to add the new status.

Notifications
Case Notification performance
Internal changes being made to help improve the timeliness of Case Notifications.  

Charge Disposition notifications
ChargeDisposition notifications are now produced when any charge information changes after disposition.  This fixes the issue where notifications were not produced when certain charge information changed after disposition.

Party Merge notifications
Internal changes being made to include Party Merge notifications within our new Party Notification framework.

Queries
CaseGet Requests
CaseGet is updated to correctly process requests containing a mix of control numbers.

Integration Access Rights
Initial Release Conditions eFile Service
Integration access rights controlling the use of this service are now being enforced.

Public Paternity Cases
Beginning October 1, 2016, court rule changes allow Paternity cases where there is post-adjudication activity to be publicly accessible.  See Minn. R. Pub. Access 4, subd. 1(n).  Impact: once public, Paternity cases are available to more integration partners.

Outbound Integrations 
Domestic Abuse No Contact Order (DANCO) – pass to BCA

• Edit failure 59 will trigger more consistently in situations where there are multiple active DANCO sentence conditions with different end dates.
• There was a rare situation where performing certain modifications to an active DANCO interim condition while also editing the comment on the condition could result in a message not being sent to the BCA when one was anticipated. This should no longer happen.

NICS - National Instant Criminal Background Check System - pass to FBI

• Internal Integration changes to accommodate the FBI's enhanced 'New NICS'.
• Improved handling of NewNICS exception messages.
• Improved process to pull Crime of Violence statutes from the BCA Statute Service.
• Improved handling of Juvenile diversion cases.
• Improved handling of Chemical Commitment cases.

OFP - Order for Protection - pass to BCA
Edit failure 62 has been created to help remind court staff to repass an OFP to the BCA when case level data (Case Name, Observed Race, or Observed Ethnicity) is updated.
These updates are currently available for testing in our Dev and QA environments.  These updates should not require any system downtime to implement in production.  Please let me know if you have any questions.

return to top
 

Court Integration Services Release 54

Environment(s): Production
Effective Date/Time: Thursday, September 22, 2016, at noon
To: Integration Group Contacts
Purpose: Notify Court Integration Services consumers of an upcoming update.
Details: The following updates will be applied to Integration Services:

eCitations/Duplicates

• Duplicate Citation check is being added at the point it is received by the Court Integration Broker.  If a citation already exists in Odyssey, then the new eCitation will be rejected immediately as a validation error. Some of these have previously been caught after court staff have expended effort in the acceptance process.
• Improved responses for Ramsey County eCitations. Some duplicate citation response messages have not succeeded in updating Bureau of Criminal Apprehension (BCA) eCharging.  This will now be more consistent.

eCitations/NameGet
The vehicle registered-owner lookup service is updated to better handle instances where the defendant is replaced prior to the completion of the lookup process.

eFiling
An internal change to the eFiling service for complaints, tab-charges, hearings, and single citations that prevents their processing from being delayed due to batches of citations.

Case Notifications/Court Decision Notifications
Notifications will now correctly publish when a judgment is amended, the amendment is deleted, and then the judgment is amended again.

Case Notifications/Custody Release Notification 
New case events will now trigger the Custody Release notification.  The new case events are:

1. Bail to Stand as Previously Ordered (BAILSTANDS)
2. Hold for Commit/Transport Order (HOLDCOMMIT)

• This case notification will continue to publish statewide as it always has when the case event, Release Ordered, is updated on any case.
• Agencies subscribed to this service will notice an increase in volume and reasons for messages.

Case Notifications/Probation Order Notification
The Probation Order notification has been expanded to include 'Discharge Probation - not all counts' case events.
     Impact:

1. Increased access to information.  This change provides notifications to subscribers when Courts enter 'Discharge Probation - not all counts' case events in the MN Court Information System (MNCIS).  Partners may choose to consume this information or filter these out.
2. Increased message volume (depending on individual partner subscriptions and local practices for using this case event).

Discharge from Probation or Monitoring
The description of the 'Discharge from Probation' (code DISCHPROB) case event changed to 'Discharge from Probation or Monitoring.'  The code (DISCHPROB) did not change. 
This case event is included in the following integration services:

1. Case Notifications – Probation Order notification
2. BCA Criminal History (CCH) data pass
3. CaseGet responses, when CourtCaseEvents are selected (and the case contains the event)

Questions or concerns regarding this change should be directed to Kelle Schleis, Court Operations Analyst, Court Services Division, kelle.schleis@courts.state.mn.us

CaseGet
A fix was made to process all financial transaction types within the FinancialDetail (3:7 schema).

MyMnConservator (MMC)
A new integration was developed to update MNCIS when CAAP audits are declined in MMC.

OFP Email Notification
Changing verbiage of the Order for Protection (OFP) petitioner email notification when either just a guardian or just a minor is served on an OFP.  The email will more clearly identify who was actually served.

Integration Access Rights
An amendment to the Rules of Juvenile Protection Procedure will make Children in Need of Protection or Services (CHIPS) Truancy and CHIPS Runaway cases publicly accessible on a go-forward basis, beginning October 1, 2016.  Impact: once public, Truancy and Runaway cases will be available to more integration partners.

These updates are currently available for testing in our Development (Dev) environment and will be available in Quality Assurance (QA) on Thursday, August 25.  These updates should not require any system downtime to implement in production.  

return to top
 

Court Integration Services Release 53

Environment(s): Production
Effective Date/Time: Thursday, June 23, 2016, at noon 
To: Integration Group Contacts
Purpose: Notify Court Integration Services consumers of an upcoming update.
Details: The following updates will be applied to Integration Services: 

eCitations 
Internal changes are being made to batch citation processing to improve performance. Partners should see a reduction in the number of rejected eCitation eFiles due to court system outages.  Partners do not need to make any changes to accommodate this change.

• Final internal changes to remove all remaining Violations Bureau Electronic System (ViBES) processes due to its decommissioning. Partners should not notice any impact.

Access Rights 
The following data is not available through Court Integration Services accounts:
 

• Driver's License Numbers [PersonDriverLicenseID]:  Driver's license data is not displayed, pursuant to Judicial Branch policy.  Agencies may contact the Department of Public Safety/Driver and Vehicle Services (DPS/DVS) for driver's license information.
• Phone Numbers [PartyTelephoneNumber]:  Telephone numbers are not remotely accessible, pursuant to Minn. R. Pub. Access 8, subd. 2(b)(3).
• Email Addresses [PartyEmail]:  Email addresses are not remotely accessible, pursuant to Minn. R. Pub. Access 8, subd. 2(b)(3) and Judicial Branch policy.
• Scars/Marks/Tattoos [PersonPhysicalFeature]:  The information is not publicly accessible, pursuant to Minn. R. Pub. Access 4, subd. 1(a)(3), 1(b) and 1(f).
• Caution Flags [Cautions]: The information is not publicly accessible, pursuant to Minn. R. Pub. Access 4, subd. 1(a)(3), 1(b) and 1(f).
• Victim and Witness Information [Victim, Witness, PartyCaseAssociationText]: Victim and witness information is not remotely accessible, pursuant to Minn. R. Pub. Access 8, subd. 2(b)(5).

Any questions about the availability of the data described above may be sent to MGAAccessSupport@courts.state.mn.us.

Name Get 
The vehicle registered-owner lookup service is updated to better handle out-of-range dates of birth on owners of leased vehicles.

Court Decision - Judgment Information
Court Decision Notifications 
 

• Will now return a CourtDecisionModified notification containing the active judgment when a judgment amendment is deleted from a family case.
• Will now return the accurate JudgmentEventType, JudgmentEventDate, and IssuingJudge for family cases that have had a judgment amendment deleted.

Case Get 
 

• Will now return the correct judgment information on cases where a judgment amendment has been deleted.

Domestic Abuse No-Contact (DANCO) Pass fix 
 

• Prevent the service from attempting to access deleted case events when pulling photos from Odyssey.
• Prevent a failure that occurs when attempting to access a photo for a case event that has no documents.

These changes are available for testing in both our Dev and QA environments and should not require any system downtime to implement in production.

return to top
br />

Court Integration Services Release 52

Environment(s): Production
Effective Date/Time: Thursday, March 24, 2016 at noon 
To: Integration Group Contacts
Purpose: Notify Court Integration Services consumers of an upcoming update.
Details: The following updates will be applied to Integration Services: 

New Schema Versions
A new base version of Court Extensible Markup Language XML 3 (CourtXML 3) was created to accommodate enhancements in the court case management system and to correct known issues. This new base schema is: CourtXML_3_2.xsd. These changes impact the Case Notifications, Case Get, Case Search By Party, and Bond Notification services.  

Changes  
 

• Warrants: bond information on the warrant has been expanded to allow repeating bond types and to allow repeating split bonds.
• Family and Juvenile judgments: expanded to allow repeating Custody Subjects, Visitation Subjects, and Support elements (family only).
• Party:
  • Expanded to allow 20 character address street numbers and repeating email addresses.
  • Removed unused elements: PersonComplexionText from PersonPhysicalDetailsType and GroupCommentText from GroupType.
  • Updated annotations on: PersonRace, PersonEthnicity, PersonSSNID.
  • Expanded PartyBaseType to allow repeating PartyCaseAssociationText elements.
  • Expanded CasePartyRelatationType to allow repeating PartyCaseAssociationText elements.
• Court Decision:
  • Removed the unused DispositionCostElement from DispositionComponentType.
  • Expanded the DispositionComponentType to allow repeating Disposition Durational Elements.
  • DispositionDurationalElement:
    • Renamed StartDateTime to StartDate and changed element to contain only the date.
    • Added a new optional StartTime element.
    • Renamed EndDateTime to EndDate and changed element to contain only the date.
    • Added new optional EndTime element.
  • Added or updated annotations for DispositionComponentValues, sentenceDelinquencyDispositionKey, sentenceEventKey, and judgmentKey.
  • JudgmentAwardType:
    • Added new ChildSupportJudgmentIndicator
    • Removed Dates container element.
• Court Case Events:
  • Renamed CaseEventDateTime to CaseEventDate and changed element to contain only the date.
  • Added a new optional CaseEventTime element.
• Court Case Header Group
  • Changed CaseFileDateTime to CaseFileDate and changed element to contain only the date.
• Case Assignment
  • Renamed AssignedCourt to CaseLocationText
• Miscellaneous:
  • CommentType: Increased field maximum length to 8000 characters (previously 7000).
  • Replaced select complex types with global elements and updated annotations.

Other changes:  

Case Notifications

• Court Decisions: Changed Charges and ChargeDisposition elements to be optional within CaseNotificationSentenceDispositionType and CaseNotificationSentenceAdjudicationType to allow messages to publish in the rare instances this information is not available.
• Case Details: Updated the annotation for Prior Court File Number.
• CaseInformation\CourtCaseEvent: Added optional Amount element
• Added a new Case Notification: Appeal Notification which is not functional at this time. This is a placeholder for a notification service to notify agencies when events related to appeals are added to MNCIS.
• SubjectPartyNotification:
  • Expanded to allow repeating PartyRemovalInformation elements.
  • Added a required PartyCaseAssociationText element to the PartyRemovalInformation element.

Case Get  
 

• CaseInformation\CitationDocument\Citation\IssuingMethodText: Added attributes and simple type files for new code table. Current description text values remain as enforced in the eCitation schema. When new eCitation schemas are published the new code values will also become available in those schema.
• CaseInformation\CitationDocument\Citation\Incident\OfficerCommentText: field maximum length is now 8000 characters (previously 7000).
• Changed PersonPhysicalDetails within Citee from local elements to use PersonPhysicalDetailsType.
• Added new FinancialDetail feature to CaseGetRequest\CaseOptions and CaseGetReply\CaseRequest\CaseInformation. This functionality will provide detailed information on financial transactions assessed on cases. Currently only available for Restitution.

Impact: 
As a result of these changes, the following new schema versions will be implemented with Release 52:  
 

• CaseNotification_3_7.xsd
• CaseGet_3_7.xsd
• BondNotification_3_4.xsd
• CaseSearchByParty_3_2.xsd
• Simple Type change - new IssuingMethodTextType.xml and .xsd files

Prior active versions of schemas will remain active and unchanged. They can be used after the new versions are in production.  

Document Security 

Additional security validations will be applied to incoming documents (submitters of documents will not see an impact). 

eCitations 

The following changes will be made to internal eCitation processing. eCitation filing schemas remain unchanged. These changes should not require any changes for submitting agencies.  
 

• Offense Desciption Truncation 
  When an e-Citation is submitted with an agency modified statute Offense Description, the offense description will be truncated to 93 characters if speed and speed zone are also submitted. Since Odyssey adds the speed information to the offense description this has been causing some errors when the final description exceeds the 100 character limit in the database. Truncating the description will prevent Odyssey from rejecting the eCitation. Submitting agencies are encouraged to shorten their descriptions on speeding offenses. The additional information may be also included in Officer Comments instead.
• Officer Comments 
  OfficerCommentText - this information previously populated a case event but will now populate the Citation record in Odyssey.
• IssuingMethodText - this information previously populated a case event but will now populate the Citation record in Odyssey. New eCitation filing schema will be published later in 2016 to allow submission of codes as shown in the new associated simple type companion file instead of only allowing description text.
• Parent/Guardian Information (Juvenile eCitations - currently only in Hennepin County) - this information previously populated a case event but will now populate the Citation record in Odyssey. The case event will no longer be used for Parent/Guardian information. The event will still be used when school information is submitted.

Professional Party Assignment Service  
 

• Has been updated to utilize better performing application program interface (API) services available from the MNCIS vendor.
• If a person was previously associated with a case, but their connection(s) to the case have since been removed, they may now be re-added to the case using this service.
• If a person has multiple active connections to a case, they may no longer be removed from the case using this service.

Case Notifications 
 

• Court Decision Notifications
  • Will now correctly handle situations where a court user simultaneously deletes multiple court decision amendments and/or court decisions.
• Case Details Notifications
  • Will now produce a notification when a case number is modified outside of a reassignment and will provide the prior court file number when possible.
• Schema Validation Errors
  • Charge Offense Descriptions where the length exceeds the maximum due to trailing spaces and/or line breaks will now publish.
• Subject Party Notifications
  • Added a new NotificationEvent of SubjectPartyModified, which will be triggered when a party's connection to the case is altered but they are still attached to the case with the same type of Subject Party that they were previously.

Bond Notifications

• Bond Notifications will now publish additional information (when available) on vehicle, plea, and bond-subject address.

Name Get

• Changes were made to the vehicle registered-owner lookup service to handle several new exceptions.

Other Changes

• Edit Failures: expanded edit failures to include active DANCOs at the Courts that may be missing at the BCA due to processing steps taken.

These changes are available for testing in both our Dev and QA environments and will not require any system downtime to implement in production.

return to top
 

Court Integration Services Release 51

Environment(s): Production
Effective Date/Time: Thursday, December 17, 2015, at noon 
To: Integration Group Contacts
Purpose: Notify Court Integration Services consumers of an upcoming update.
Details: The following updates will be applied to Integration Services: 

Case Notification Services
Court Decision Notifications will no longer try (and fail) to return information for deleted Writs of Execution.

Court Decision Notifications will no longer include information from deleted decision amendments.

No Contact Order Notifications will now correctly trigger when a sentence is modified to delete a No Contact Order condition, while keeping other conditions on the sentence.

Other Agency Cross Reference Notifications will now successfully trigger for cases that have incorrectly been assigned a case cross reference number multiple times.

Case Detail Notifications will no longer be triggered by scofflaw updates.

Warrant Notifications have been updated as follows:

• Warrant Modified messages will only be published on active warrants.
• Messages will exclude charges that have been removed from the warrant.
• Warrant Inactivated messages will no longer have a chance of failing because the warrant was inactivated and then deleted in quick succession.

Probation Order Notification has been expanded to include 'Discharge From Probation' events.
Impact:

1. Increased access to information.  This change will provide notification to subscribers when Courts enter 'Discharge From Probation' case events in MNCIS.  Partners may choose to consume this information or filter out these events.
2. Increased message volume.  The number of 'Discharge From Probation' events recorded in MNCIS could potentially double the current volume of Probation Order case notifications (depending on individual partner subscriptions).

eFiling
Juvenile eCitations will now accept additional vehicle makes (currently only used in Hennepin County).
 
Point to Point Passes
For the Order for Protection pass to the BCA, logic has been updated to correctly trigger edit failure #54 (OFP left in a correcting status).
 
Simple Types 
The Case Cross Reference Number simple type is being updated to include MyCourtMN Filing ID and the National Instant Criminal Background Check System (NICS) Record Identifier.
 
Access Rights
Some integration accounts have been updated to conform with the Rules of Public Access to the Records of the Minnesota Judicial Branch and Supreme Court orders.
 
These changes are available for testing in both our Dev and QA environments and will not require any system downtime to implement in production.

return to top
 

Court Integration Services Release 50

Environment(s): Production
Effective Date/Time: Thursday, September 24, 2015, at noon 
To: Integration Group Contacts
Purpose: Notify Court Integration Services consumers of an upcoming update.
Details: The following updates will be applied to Integration Services: 

Service Catalog Services

• For all eFile services that can include documents, an error message will be returned to the submitter when a document is found to be corrupt.
• For the warrant status update eFile service an error message will be returned to the submitter when the update time is before the current warrant status time.
• The Attorney Assignment eFile Service has been updated so it now functions in situations where an attorney had previously been assigned multiple times to the same party.
• For the Person Other ID eFile service an error message will be returned to the submitter when the specified party is Read-Only within MNCIS.
• For the case notification service certain types of hearing settings were not always publishing when the setting time was modified. This has now been fixed.
• Internal changes have been made to the Case Get service to improve performance. Also, an edit has been added to reject individual requests that include more than 20 cases to prevent performance issues caused by requests containing large numbers of cases.

NICS
Some cases previously ineligible to be sent to NICS due to court rules will now be sent to NICS.

DANCO – Domestic Abuse No Contact Orders 
A change has been made to the service that receives rejection messages to improve troubleshooting and support processing.

Judge Maintenance 
The Judge Maintenance to MNCIS integration has been updated to current programming standards and to prevent incidental loss of MNCIS configuration outside the scope of this integration.

Statute Service 
New services were developed for an internal Court application to provide statute information from the BCA's Statute Service. Functionality includes a query service and two message services (daily statute updates and weekly notification of the full statute set).

These changes are available for testing in both our Dev and QA environments and will not require any system downtime to implement in production.

return to top
 

Court Integration Services Release 49

Environment(s): Production
Effective Date/Time: Thursday, June 25, 2015, at noon
To: Integration Group Contacts
Purpose: Notify Court Integration Services consumers of an upcoming update.
Details: The following updates will be applied to Integration Services:
 

• An internal change to how broker services process simple type companion files to improve performance. There should be no impact to integration partners with this change.
• Legislative changes passed into law with the recent 2015 Session will require some internal processing changes for document handling. There should be no impact to our integration partners with these changes.
• A new service has been developed to support real time electronic transmission of Driver's License Suspensions and Reinstatements and notifications of No Proof of Insurance violations to the Department of Public Safety.

return to top
 

Court Integration Services Release 48

Environment(s): Production
Effective Date/Time: Thursday, March 26, 2015, at noon
To: Integration Group Contacts
Purpose: Notify Court Integration Services consumers of an upcoming update.
Details: The following updates will be applied to Integration Services:

Ramsey County Citation Routing
Ramsey County eCitations will require the submitter to include the In Custody indicator. This is in preparation for ViBES retirement. If the citation is filed for Ramsey County and the information is missing, the eCitation will be rejected. If the In Custody indicator is set to 'false', it will be routed for handling in ViBES. When ViBES is retired in Ramsey, these will be directed to MNCIS. If In Custody indicator is set 'true', it will be routed for special court handling by Ramsey staff before filing in MNCIS. This indicator remains optional in all other counties and its use is dictated by local practice.

Citations

• An internal change has been made to the security processing done by citation service to require that the submitter has the correct rights to file citations by court rather than just the right to file citations.
• In preparation for the retirement of the ViBES system in Hennepin and Ramsey County, some changes have been made in the processing of citations. Name lookup on parking citations will be moved from VIBES to Court integration broker. The parking citation, submitted for Hennepin or Ramsey will still be processed by VIBES until the respective court stops using VIBES.
• Processing of names and dates of birth is moved before the adult court validation rules to allow better processing of juvenile owners of vehicles.
• Simple Type Statutes and Ordinances include more offenses with a Traffic group to allow better processing for the adult court validation rules on parking offenses.

BCA Disposition Pass
A fix was made to the BCA Disposition pass to correct instances where the fine amount from the Sentence was not always being passed to the CCH system.

CaseGet and CaseSearchByParty
An internal change has been made to improve performance.

CaseNotification Schema Validation Error
An internal change has been made to prevent a schema validation error.

eFiling
An internal change has been made to automatically retry eFiles that were rejected to do some specific system errors. This change impacts criminal complaints, tab charge, citation, hearing and professional party assignment e-files.

File Stamping
A change has been made to the process that the integration broker uses to add file stamps to eFiled documents to keep from invalidating any digital signatures that were included prior to filing them. This change impacts criminal complaint documents received from eCharging and also documents received from the Appellate Courts Case Management System (MACS).

Fix Logic for determining the plea for a charge
An internal change has been made in the process for the logic in determining the plea for a charge where the incorrect plea would be passed under certain circumstances.

return to top

 

Court Integration Services Release 47

Environment(s): Production
Effective Date/Time: Thursday, December 18, 2014, at noon
To: Integration Group Contacts
Purpose: Notify Court Integration Services consumers of an upcoming update.
Details: The following updates will be applied to Integration Services:

• A change was made to the disposition data pass to the Department of Natural Resources (DNR) to exclude local ordinances when determining which dispositions and sentences should pass to the DNR.
• The courts created a process to pull specific information on the requests made to the DVS system and the responses received from the DVS system.  An example of the information requested from DVS is the driver’s photo for the DANCO verification process. This information about requests and responses will be logged into a database, which will be used by the State Court Administration Audit Group.
• Some internal changes have been made to the service that accesses DVS To retrieve DANCO photos.  These changes address some minor issues and will be transparent to court users.
• A change was made to the BCA Disposition pass to modify the messages sent to the CCH system that are produced as a result of several batch jobs designed to update older MNCIS data.

return to top

 

Court Integration Services Release 46

Environment(s): Production
Effective Date/Time: Thursday, November 6, 2014, at noon
To: Integration Group Contacts
Purpose: Notify Court Integration Services consumers of an upcoming update.
Details: The following updates will be applied to Integration Services:
NICS changes:

• Juvenile cases with a case type of Delinquency Felony 16 or over (D16) will pass to NICS upon disposition if there are charges deemed a Crime of Violence.
• Mental Health cases with a disposition of Committed - Psychopathic Person will be passed. This disposition is no longer used by the court but some historical cases have this disposition.
• Minor modifications to the NICS pass to prevent unnecessary canceling and re-passing of cases due to court processing procedures.

Note: This change to the NICS pass was originally part of release 45 but was pulled out because it was not ready when that release went to production. 

An internal change to the mechanism used by the integration broker to make updates to MNCIS. This change is being made to prevent some errors that have occurred, and did not change how services work or how they are used.

An enhancement to the VIBES Web Service. This Web Service is only used in Hennepin and Ramsey.

• A new option is being added to the query that pulls statutes and ordinances to allow the caller to request by Offense ID.

return to top

 

Court Integration Services Release 45

Environment(s): Production
Effective Date/Time: Thursday, September 25, 2014, at noon
To: Integration Group Contacts
Purpose: Notify Court Integration Services consumers of an upcoming update.
Details: The following updates will be applied to Integration Services:

The 3:4 Adult e-Citation schema will now process most e-Citations with the new case type, AGC - Adult Citation, rather than CRM (Mandatory) or VIB (Non-Mandatory). This case type deployed in Odyssey for manual entry in July 2014. Previous integration logic to determine or validate case type will be removed and Odyssey will determine case type (CRM or VIB). The MandatoryAppearanceIndicator will only be used for eCitations using offenses citing rules or ordinances (this indicator does not exist in the 3:5 eCitation schema). This will result in fewer rejections by court integration and by court staff. The 3:4 Adult eCitation schema will retire permanently in January 2015.

Adult Citation Validations - citations submitted to adult court will be validated against additional rules to determine if they are to be filed in Juvenile Court instead. If the citation needs to be filed in Juvenile Court, the citation will be automatically rejected with a message to file with Juvenile Court. Previously these were manually rejected by court staff or manually re-routed in ViBES counties. The rejection message is the same as the one produced currently if an eCitation is filed and the citee is under the age of 16.

Simple Type Offense File changes:

• The StatutuoryChargingOffenseType, RuleChargingOffenseType, and OrdinanceOffenseCategoryType companion files will now be populated by the corresponding MNCIS Offense Type that was introduced with Odyssey 13 and deployed in July 2014. Some offenses may move based on the new classification within MNCIS.
• All three offense files will now include the DefaultSeverityLevelText. This is the configured default level of offense (Felony, Gross Misdemeanor, Misdemeanor, or Petty Misdemeanor) for each offense in MNCIS. MNCIS will use this at case initiation on eCitations for both validating adult citations and for potential rejection of citations that need to be filed in Juvenile Court.
• All three offense files will now include a Group on appropriate offenses: the new group concept is introduced for use with the Adult Court Validation rules. An eCitation with a 16- or 17-year-old citee may be handled in Adult Court if all offenses are petty misdemeanor and are in a group of either "Traffic" or "Water". An eCitation with a DWI offense and a 16- or 17-year-old citee may also be handled in adult court as long as one offense is Driving While Intoxicated (DWI) and the others are in the "Traffic" or "Water" group regardless of severity level.
• StatutoryChargingOffenseType file will now include the Crime of Violence flag on appropriate offenses. This will match the MN Justice Information Services (MNJIS) Statute Service and will be used by the court to determine if a juvenile case may be submitted to NICS.
• AllowEndanger will now appear on some offenses. Odyssey uses this information to determine and/or correct the level of offense on a charge. This will be used by court integration to validate offenses similar to how Odyssey does when an eCitation is filed. Court integration will use this specifically for adult citations with a citee that is 16- or 17-years-old to determine whether the e-citation may be filed in adult court.

Occasionally technical errors within MNCIS cause an eFile service to fail. These failures can often be resolved by having the service automatically retry the eFile. Changes have been made to expand the retry process to include an additional technical error. This is for your information only. No action is required on your part.

An internal change was made to the Attorney Assignment eFile service to use utilize API services available from the MNCIS vendor. This is for your information only. There has been no change to the message schema. In conjunction with this change an updated version of the technical consumer documentation will be posted to the public web site.

NICS changes:

• Juvenile cases with a case type of D16 will pass to NICS upon disposition if there are charges deemed a Crime of Violence.
• Mental Health cases with a disposition of Committed - Psychopathic Person will be passed. This disposition is no longer used by the court but some historical cases have this disposition.
• Minor modifications to the NICS pass to prevent unnecessary canceling and re-passing of cases due to court processing procedures.

A change was made to several services to incorporate a new MNCIS case type: Extradition (Juvenile). The Extradition (Juvenile) case type will be available in Production MNCIS sometime after September 25, 2014.

An internal change has been made to the following services to reduce the amount of system memory they use. This does not change in any way how the services are used.

• Case Notification
• Bond Notification
• eFiling
• Batch Citations

These changes are available for testing in both the development and QA environments.

These changes will not require any system downtime to implement.

return to top
 

Court Integration Services Release 44

Environment(s): Production
Effective Date/Time: Thursday June 26, 2014 at noon
To: Integration Group Contacts
Purpose: Notify Court Integration Services consumers of an upcoming update.
Details: The following updates will be applied to Integration Services:

Changes to Point-to-Point Data Passes

• Driver Vehicle Services (DVS) Pass
• Two changes have been made.  The DVS pass has been updated to:
  • Pass convictions that are defined by statute as certifiable, regardless of any subsequent action taken to decertify the offense.
  •  Automatically pass convictions of certain offenses based on offense and citee.  Previously these convictions required manual updates by Court staff.

Internal Changes
A modification has been made to an internal service based on a fix to an internal Odyssey (MNCIS) component.  The result is that all street suffix types on a party address can now be added to MNCIS.  This change currently affects the MMC (MyMnConservator) to MNCIS integrations.

MACS/MNCIS Document Add Service – Document Security Changes     
A change is being made to an internal court integration between MNCIS and the Appellate Court system related to document security.

Corrections Document Add Service
A new service has been developed,  which will allow Corrections partners to submit Probation Violation Reports and Proposed Probation Violation Orders via an integration as part of a pilot.  We plan to expand this service to other corrections documents in the future.

These changes are available for testing in both our Dev and QA environments.

return to top
 

Court Integration Services Release 43

Environment(s): Production
Effective Date/Time: Thursday April 24, 2014 at noon
To: Integration Group Contacts
Purpose: Notify Court Integration Services consumers of an upcoming update.
Details: The following updates will be applied to Integration Services:

A new service has been developed to support the centralized processing of Hennepin and Ramsey County parking citations.  The new service identifies the registered vehicle owner in cases where the owner/driver is not present and the parking citation is issued to the vehicle.

The new service will result in some changes to the submission of eFiled parking citations.  Further detail regarding the use and requirements of this service will be provided by Kris Wilkens from the Court’s Business Practices Unit. 

This service does not impact VIBES citation processing.

These changes are will be available in Dev on Friday March 28th.   They will be available in QA on Friday April 4th.

return to top

Court Integration Services Release 42

Environment(s): Production
Effective Date/Time: Thursday April 3, 2014 at noon
To: Integration Group Contacts
Purpose: Notify Court Integration Services consumers of an upcoming update.
Details: The following updates will be applied to Integration Services:

New Schema Versions
A new base version of CourtXML 3 was created to allow for a more standardized/global structure for representing charges. This new base schema is: CourtXML_3_1.xsd.   These changes impact the Case Notifications, Case Get and Criminal e-filing services.    This does not impact e-filing through Odyssey E-file and Serve.

Major changes:

• The Charge structure in CourtXML 3:1 has been flattened out, and the four separate sub-structures that made up ChargeStatuteOrdinanceRule have been eliminated, with many elements becoming direct child elements of Charge. This change allows for offenses of any type (statute, ordinance or rule) to be represented in the same way.
• In CourtXML 3:1 the unique MN-specific identifier associated with an offense has been made more global with the element named OffenseID. Offense ID replaces the use of the more granular StatuteID, OrdinanceCategoryID and RuleID that are used in CourtXML 3:0.

Other changes:

• Arrest/ArrestingOfficial/BadgeNumber was renamed Arrest/ArrestingOfficial/OfficerBadgeNumber.
• Arrest/ArrestingOfficial/Name was renamed Arrest/ArrestingOfficial/OfficerNameText.
• Report/ReportingOfficial/BadgeNumber was renamed Report/ReportingOfficial/OfficerBadgeNumber.
• Report/ReportingOfficial/Name was renamed Report/ReportingOfficial/OfficerNameText.
• Vehicle data has been expanded to include additional elements, such as vehicle type, and vehicle text, in addition to vehicle plate information.
• The HazardousVehicleIndicator has been renamed to HazardousMaterialsIndicator.

Impact:
As a result of the change to the Charge structure, the following new schema versions for Case Notifications, Bond Notifications and Case Get will be implemented with Release 42:

• CaseNotification_3_6.xsd
• CaseGet_3_6.xsd
• BondNotification_3_3.xsd

Due to the change in the Charge structure, the following new schema versions for criminal e-filing will also be implemented:

• CitationDocument_3_5.xsd
  • MandatoryAppearanceIndicator – removed since case type will be determined by MNCIS
  • OffenseDescriptionText (replaces ChargeDescriptionText) – optional for statutes; not allowed for ordinances or rules
  • Third Violation Indicator – allowed on appropriate statutes
• CriminalComplaintDocument_3_3.xsd
  • Criminal Complaint Document
  • Tab Charge Document
• InitiateCriminalCase_3_3.xsd  (used  by Ramsey County only)
• JuvenileCitationDocument_3_3.xsd

Prior active versions of schemas will remain active and can be used after the new versions are in production.  At some point an additional notification will go out that will let you know when older version of the Citation eFiling schema will be inactivated.

Changes to e-Filing Services

• An internal change was made to the Initial Release Conditions eFile service as a result of a vendor change in Odyssey Release 13.  The change will not result in any changes to the submission of e-files.  This is for your information only.
• When a MNCIS case is initiated through BCA eCharging, the final complaint document image will be attached to MNCIS.  The BCA eCharging  system will need to make a corresponding change.  The date of the change at the BCA is yet to be determined.
• The adult criminal complaint eFile service is modified to set the Extradition case type when appropriate.

Changes to Simple Type Schemas and Companion Files

• The Simple Type Offense companion files will include additional information:
  • Statutory Offenses (StatutoryChargingOffenseType.xml)
    • Offense Owner
    • Third Violation
  • Rules (RuleChargingOffenseType.xml)
    • Offense Owne
  • Ordinances (OrdinanceOffenseCategoryType.xml)
    • Offense Owner
    • Cite
• The following Simple Type schema files are being discontinued and will no longer be published.   For each of these there is another more complete file  that will continue to be published.
  • OrdinanceOffenseCategoryTypeIn.xsd
  • RuleChargingOffenseTypeIn.xsd
  • StatutoryChargingOffenseTypeIn.xsd
  • StatutorySupplementalOffenseTypeIn.xsd

These changes are currently available in the development environment and will be available in QA on March 10th.

return to top
 

Court Integration Services Release 41

Environment(s): Production
Effective Date/Time: Thursday December 5, 2013 at noon
To: Integration Group Contacts
Purpose: Notify Court Integration Services consumers of an upcoming update.
Details: The following updates will be applied to Integration Services:

This release of integration services is in preparation of the upcoming release of Odyssey 2013.   These changes are to prepare for the new “municipality specific” ordinances that will be configured after Odyssey 2013 is in production.

• The process for building simple type schemas for Ordinances and Rules is being modified so that it will include these new ordinances.
• An internal change is being made to Criminal eFiling (Complaint, Citation, and Initiate Criminal Case).  The new “municipality specific” ordinances will only be available for eFiling with the new versions of the eFiling schemas that will be available with Release 42.   This change is to reject these new ordinances when older versions are used.

return to top
 

Court Integration Services Release 40

Environment(s): Production
Effective Date/Time: Thursday October 31, 2013 at noon
To: Integration Group Contacts
Purpose: Notify Court Integration Services consumers of an upcoming update.
Details: The following updates will be applied to Integration Services

Service Catalog Services

• The following services are being updated to our current development software.   Along with this update an internal change is being made that reduces the amount of memory each service requires to run on our integration broker servers.    This change is being made because of some issues we have had recently where our servers were running low on memory.   This update does not change how any of these services work, and will be transparent to consumers.
  • CaseGet
  • CaseSearchByParty
  • CaseNotification
  • BondNotification
  • eFiling (not including batch citations)
• Citation filing processing (both batch and single citations) changes:
  • If a Pay or Appear Date is submitted on an e-Citation, this date will be validated to prevent a date in the past from being submitted.
  • A service fix is being applied to prevent rejections of e-Citations with specific offenses that no longer require a mandatory court appearance.

These changes are currently available in the Development environment and will be in QA on Friday (10/4).  Implementing these changes in production will not require any system downtime.

return to top
 

Court Integration Services Release 39

Environment(s): Production
Effective Date/Time: Thursday September 19, 2013 at noon
To: Integration Group Contacts
Purpose: Notify Court Integration Services consumers of an upcoming update.
Details: The following updates will be applied to Integration Services: 
 

Service Catalog Services

Integration Services Access
This release of integration services includes some changes related to an eCourtMN initiative to better support court rule and compliance standards regarding access to confidential cases. These changes should be transparent with the following exceptions:

• Integration services partners that have access to adult criminal cases will not receive case notifications or query results (using ‘Case Get’ or ‘Case Search by Party’) for a case if the case is made confidential.
• As a result of a legal policy decision integration service partners with access to confidential cases will no longer receive social security numbers as part of that access. A Supreme Court order is required for access to social security numbers.

Internal Court Integration Services

MyMnConservator (MMC) is the Court’s conservator account-filing and auditing system that is replacing the existing CAMPER system.

New services have been developed that will allow an internal exchange of information and documents between MMC and MNCIS regarding Guardianship/Conservatorship cases and the parties to those cases.  This exchange of information will increase efficiency and data quality for court staff, conservators, and the Conservator Account Auditing Program (CAAP) staff. 

The Service Catalog services are available for testing in both our Development and QA environments.  Implementing these changes in production will not require any system downtime.

return to top
 

Court Integration Services Release 38

Environment(s): Production
Effective Date/Time:     Thursday May 30, 2013 at noon
To: Integration Group Contacts
Purpose: Notify Court Integration Services consumers of an upcoming update.
Details: The following updates will be applied to Integration Services:

New Services:
This release of integration services is in preparation for the upcoming pro se eFiling pilot in Hennepin County for OFP (Order for Protection) and HRO (Harassment Restraining Order) initial filings.

These changes will not impact any other integration services.

Changes to the VIBES Web Service:
A new version (#5) of the web service is being implemented that includes an additional field from the VIBES database.    All prior version will continue to function, and will be unaffected.

Hennepin and Ramsey Counties are the only users of this service.

Implementing these changes will not require any system downtime.

return to top
 

Court Integration Services Release 37

Environment(s): Production
Effective Date/Time:     Thursday March 28, 2013 at noon
To: Integration Group Contacts
Purpose: Notify Court Integration Services consumers of an upcoming update.
Details: The following updates will be applied to Integration Services:

Changes to Case Notification services:

• A change has been made to Charge Disposition notifications such that when amendments to dispositions are deleted, the notification will reflect the current disposition for the charge in the case notification.  This change is to address inconsistencies in how deleted information is handled within messages.
• A change has been made to the Hearing Trial Setting Notifications.  The HearingDatetimeEnd element will now reflect the end time of scheduled hearings on calendars that are set up for interval time periods.  Interval hearings are calendars with hearings scheduled for set time periods, for example every 15 minutes.  Previously the end date was not produced for interval hearings.  This does not impact hearings on other calendars not set up for interval time periods.   This change is to correct inconsistent end dates being produced for scheduled hearings that have specific end times.
• An intermediate  change was made to truncate business names that exceed 80 characters to prevent failures with case notification and query service results; this is an intermediate change until such time as CourtXML schemas can be changed to reflect the business name size that the MNCIS application now allows.

Changes to eFiling Services:

• Occasionally technical errors within MNCIS cause an eFile service to fail. These failures can often be resolved by having the service automatically retry the eFile. Changes have been made to expand the retry process to include an additional technical error. This is for your information only. No action is required on your part.
• A change has been made to the supplemental citation document add eFile service used in a pilot in Dakota County.  This eFile service will be modified to attach documents to a case event in MNCIS.
• An internal change has been made to improve response times for eFiling requests received through Web Services.

Change to the Case Search by Party service:

• An internal fix has been made to the retry logic used by this service to try to better respond to internal server issues.   This fix does not have any impact on how the service is used or its message format.

Changes to Point-to-Point Data Passes:

• For the data pass to the DNR, two additional vehicle types (Off-road motorcycle and Off-road recreational vehicle) have been added to the selection criteria for 169A* and 171* statutes.
• An internal change was made to the functionality for retriggering certain messages to the Secretary of State.
• A fix is being implemented for the BCA Disposition Pass to correct an error that occurs during message processing in certain circumstances.  This is for your information only. No action is required.

These changes are currently available for testing in  Development and will be in the QA environment on Friday March 1.   Implementing these changes in production will not require any system downtime.

return to top
 

Court Integration Services Release 36

Environment(s): Production
Effective Date/Time: Thursday December 20, 2012 at noon
To: Integration Group Contacts
Purpose: Notify Court Integration Services consumers of an upcoming update.
Details: The following updates will be applied to Integration Services:
 

Service Catalog Services

Changes to Case Notification services:

•  A change has been made to Charge notifications and Charge Disposition notifications  such that when amendments to pleas are deleted, the notification will reflect the current plea for the charge in the case notifications.  This change is to address inconsistencies in how deleted information is handled within messages.

Changes to eFiling Services:

• A new vehicle make type has been added to the simple type companion file. The code of ‘other’ vehicle make has been added for administrative use only and is not available for general use.   If a citation is submitted with this vehicle make, it will be rejected.   This is for your information only.
• Charges that include the ‘Pending Statute’ structure will no longer be allowed on e-Citations or e-Complaints.  E-Citations or e-Complaints submitted with this pending structure will be rejected.  All charges will now require a valid statute, ordinance or rule.
• An internal change was made to error handling for the UpdateBiometricCollectionStatus e-file service. The change will not result in any changes to the submission of eFiles

Point-To-Point Data Passes:

• Internal changes will be made to the BCA Disposition Pass to clarify certain messages.  This is for your information only. No action is required.

These changes are available for testing in both our Development and QA environments.  Implementing these changes in production will not require any system downtime.

return to top

Court Integration Services Release 35

Environment(s): Production
Effective Date/Time:     Thursday September 20, 2012 at noon
To: Integration Group Contacts
Purpose: Notify Court Integration Services consumers of an upcoming update.
Details: The following updates will be applied to Integration Services:
 

Service Catalog Services

Changes to Case Notification services:

• Warrant notifications now include a Warrant Deleted Notification. This notification is produced when a previously active warrant that has been inactivated is deleted.
• Bond notifications now include a Bond Deleted Notification. This notification is produced when a bond is deleted
• A fix to address the rare occasions when a message published from MNCIS without the UserID of the court user that made the update, resulting in a failure. A fix has been implemented such that the attribute ‘update user account’ will have a value of ‘MNCIS’ if the published message is missing the actual value of the user account that made the update.
• Fix to Case Details notification when a related case was deleted in conjunction with some other action that triggers a  notification. This scenario caused an error to occur, preventing the notification from being produced. This has been fixed so that the delete of a related case number from a case does not impede the Case Details notification from being produced.
• Fixes were made to Agency Notes Notifications, Transport Notifications, and Probation Order Notifications to address the scenario where parties were related to a case event and then removed.  A fix was made to not provide the party in these case notifications after the party was removed.

Changes to eFiling:

• A new version of the Other Agency Cross Reference service has been developed. The new version is 3:2 and uses schema CaseCrossReference_3_2.xsd.  This version allows a single cross reference number to be added to multiple cases.  It was developed at the request of the Court of Appeals.  This is for your information only. No action is required on your part unless you choose to use 3:2. Version 3:1 will continue to be available.
• A new version of the Other Agency Note service has been developed. The new version is 3:2 and uses schema OtherAgencyNote_3_2.xsd. It allows a note to be added to multiple cases.  The new version was developed at the request of the Court of Appeals. This is for your information only. No action is required on your part unless you choose to use 3:2. Version 3:1 will continue to be available
• Occasionally technical errors within MNCIS cause an eFile service to fail. These failures can often be resolved by having the service automatically retry the eFile. Changes have been made to expand the retry process. This is for your information only. No action is required on your part.
• An internal change was made to the Add Other Person ID eFile service as a result of a vendor change in  Odyssey Release 12. This is for your information only. No action is required on your part.
• A new version of the Add Case Document service has been developed for use by the Court of Appeals.
• A MNCIS change to document security required a change to the document add services that allow documents to be eFiled to a case by a Hennepin County Court imaging application.

Point-To-Point Data Passes:

• The MARS to MNCIS attorney integration has been changed to use API calls to update MNCIS. This is for your information only. No action is required on your part.
• The FBI made a change to the format of messages sent from MNCIS to the National Criminal Background Check System (NICS). This required an internal change to the NICS service. This is for your information only. No action is required on your part.
• At the request of the Bureau of Criminal Apprehension (BCA), the BCA Disposition Pass has been modified to not pass probation agency when the probation agency code is ADMPROAGY (Administrative Process).  This is for your information only.  No action is required on your part.
• A change will be made to the interface between MARS (Attorney Registration) and MBCLE (Minnesota Board of Continuing Legal Education).   This interface passes attorney information from MARS to MBCLE.   After the update MBCLE will be consuming some additional fields.  This is for your information only.  No action is required on your part.

These changes are available for testing in both our Development and QA environments.  Implementing these changes in production will not require any system downtime.

return to top

Court Integration Services Release 34 (06/28/2012)

Environment(s): Production
Effective Date/Time:     Thursday June 28, 2012 at noon
To: Integration Group Contacts
Purpose: Notify Court Integration Services consumers of an upcoming update.
Details: The following updates will be applied to Integration Services:

Service Catalog Services

1)      A fix to the Case Notification service for Juvenile Judgments.

• When an update was made to a juvenile judgment where the related amended judgment had been previously deleted, an error occurred which prevented the notification from being produced. This has been fixed.

2)      New CaseGet and CaseNotification schema versions incorporating new warrant bond fields.

• Recent configuration changes in MNCIS have added three new fields to warrants. These fields allow the court to specify a ‘split’ bond. Typically this is used when the court assigns a bond amount and allows a cash bail alternative.

Revised Case Get and Case Notification schemas are being published.  The new versions and associated service changes use the new fields when warrants are returned in the results.

The new schema versions are:

• CaseNotification_3_5.xsd
• CaseGet_3_5.xsd

The SplitBond element is contained within warrant and includes:

• SplitBondAssociation
• SplitBondAmount
• SplitBondTypeText

Integration Services users are not required to use the revised schemas.  If older versions of the schema are used, the split bond elements will not be included in results.

3)      A fix to the Case Notification service for Warrant Notifications.

• When there is one or more active warrants on a case, the entry of certain case events (warrant quashed, warrant recalled, etc.) inactivates all of the warrants and generates a warrant notification. A problem was discovered that affected cases where multiple active warrants existed. The warrant notification was only reporting that one warrant was inactivated.  That has been fixed so that when multiple warrants are inactivated by a case event, a warrant notification is generated for each warrant inactivated by the case event.

4)      Some internal changes to eFiling.

• Some additional internal error logging has been added to capture certain errors associated with the Warrant Status Update eFile service. This is for your information only. No action is required on your part.
• Occasionally technical errors within MNCIS cause an eFile service to fail. These failures can often be resolved by having the service automatically retry the e-file. Changes have been made to expand the retry process. This is for your information only. No action is required on your part.

Point to Point Passes

1)      BCA DANCO (Domestic Abuse No Contact Order)  Pass

• The DANCO service has been changed to optionally include law enforcement observed race and law enforcement observed ethnicity for the Order Subject (Defendant) in the message that is sent to the BCA, in response to Supreme Court order ADM10-8050.
• The DANCO service has been changed to require less data in the message that is sent to the BCA when the message type is ‘OrderDeleted’.

2)      Driver Vehicle Services (DVS)  Pass

• A change to the functionality of the DVS pass will allow the passing of specific disposition amendment scenarios. Training for users will be provided by Court Services in the near future.

These changes are available for testing in both our Development and QA environments.  Implementing these changes in production will not require any system downtime.

return to top

Court Integration Services Release 33 (04/26/2012)

Environment(s): Production
Effective Date/Time: Thursday April 26, 2012 at noon
To: Integration Group Contacts
Purpose: Notify Court Integration Services consumers of an upcoming update.
Details: The following updates will be applied to Integration Services:


Service Catalog Services
A Supreme Court order has made changes to the default subject party types for Paternity and Support case types.  Prior to May 1st, 2012 the default subject party types on those two case types are Plaintiff and Defendant. Starting May 1st, 2012 the default subject parties will be Petitioner and Respondent.

Case Get and Case Notification services have been changed to use the appropriate subject party types.

An issue that affected these two services has also been fixed.  In some instances, the services were only reporting one subject party when two subject parties existed on a case.

Point to Point Passes
BCA NICS Pass

• A fix is being implemented with the BCA NICS (National Instant Criminal Background Check System) to correct an issue caused by amended judgments.

Other Services
VIBES Web Service change.

• The VIBES Web Service is currently only used by Hennepin County and Ramsey County.
• This change will implement a new version of the schema that includes an additional data element which will be used only in Hennepin County at this time.
• The prior version of the schema will be unaffected and will continue to be active.

Implementing these changes in production will not require any system downtime.

return to top

Court Integration Services Release 32 (02/16/2012)

Environment(s): Production
Effective Date/Time:     Thursday February 16, 2012 at noon
To: Integration Group Contacts and E-citation Group and Vendor Contacts
Purpose: Notify Court Integration Services consumers of an upcoming update.
Details: The following updates will be applied to Integration Services:

• An internal change is being made to the Warrant Status Update eFile service *. There is no change to the message schema or functionality for this service.
• A new validation check is being added to the Juvenile Citation eFile service. If the age of the citee as of the date of the offense is less than 10 years old, the citation will be rejected.
• New schema versions will be published for Criminal Complaints and Tab Charges, and for the Initiate Criminal Case message used in Ramsey County.  Processing changes have also been made.   Please review the section below labeled Complaint/Tab-Charge/Initiate Criminal Case Schema Changes for details on these changes.
• New schema versions will be  published for adult and juvenile citations.  Changes have also been made to how citations are processed.  These changes apply to batch and single eFiled citations.  Please review the section below labeled Adult and Juvenile Citation Schema Changes for details on these changes.

These changes are available for testing in both Development and QA.  

* The Warrant Status Update eFile service will be available for testing in Development and QA on 1/18/12

Implementing these changes in production will not require any system downtime.
 

Complaint/Tab-Charge/Initiate Criminal Case Schema Changes

New Schema Versions

• CriminalComplaint_3_2.xsd
• InitiateCriminalCase_3_2.xsd

Changes include:
A Vehicle element has been added within Charge.  The vehicle element contains the following child elements:

• VehicleTypeText
• VehicleMakeText
• VehicleModelText
• VehicleYear
• VehicleColorText
• VehicleLicensePlate
• CommericalVehicleIndicator
• HazardousmaterialsIndicator
• VehicleID

The Vehicle element is optional. If it is included in a submission, VehicleLicensePlate/PlateState and PlateNumber are required. All other elements within vehicle are optional.

Note: VehicleLicensePlate was previously included as a child element of charge. It is now contained within Vehicle.

Processing Change

• Minnesota Offense Code (MOC) is required on all Felony and Gross Misdemeanor level charges. If this condition is not met, the complaint will be rejected with a schema validation error.

There is no specific date that partners will be required to begin using the new schema versions.  The 3:1 versions of these schemas are currently not scheduled to be inactivated and will remain available for use.  However, any new development should apply only to the most recent versions. See the Integration Services website for the support status of each schema version (CourtXML Schema).
 

Adult and Juvenile Citation Schema Changes

New Schema Versions

• CitationDocument_3_4.xsd
• JuvenileCitationDocument_3_2.xsd.

Changes include:

New child elements have been added to the vehicle element:

• VehicleID (VIN)
• VehicleYear

The HazardousVehicleIndicator has been changed to HazardousMaterialsIndicator.

Within Vehicle, the following elements are now required:

• VehicleType
• VehicleMake
• VehicleLicensePlate
• CommericalVehicleIndicator
• HazardousMaterialsIndicator.

A new required element has been added:

IssuingMethodText.  Valid values are enumerated within the schema.                

A new optional element has been added:

IdentificationMethodText. Valid values are enumerated within the schema.

Processing Changes

Changes have been made to citation processing. Except where noted, these changes apply to adult and juvenile citations:

Vehicle information is conditionally required. If a citation includes a charge that requires vehicle information, the citation will be rejected if it does not contain all of the required vehicle elements.  A previously published update to the Statutory ChargingOffenseType simpletype file included a VehicleRequired associated value. All statutes that require vehicle information include this value.

• Minnesota Offense Codes (MOC) are required on all Felony and Gross Misdemeanor level charges. If this condition is not met, the citation will be rejected with a schema validation error.
• Issuing Method is required. If this information is missing, the citation will be rejected.
• Identification Method is optional, but if it is included, the value must be one of the enumerated values.
• Under conditions listed below, citations submitted with a MandatoryAppearanceIndicator set to false will be treated as mandatory. (Does not apply to juvenile citations.)
  • PropertyDamageText has a value of Endanger
  • A careless driving charge and AccidentDamageText contains any value except ‘None’.
  • A charge for Uninsured Vehicle-Driver Violation (statute 169.793.3) and AccidentDamageText contains Fatal or Substantial Bodily Harm.
  • If the citee was under age 16 on the date of offense, the citation will be rejected. (Does not apply to juvenile citations.)

The new schema versions and processing changes are scheduled to be moved to production on February 16, 2012. July 1, 2012 is the target date when their use will be required. Older versions of the schema will be deactivated on that date. See the Integration Services website for the support status of each schema version.  (CourtXML Schema).

return to top

Court Integration Services Release 31 (12/20/2011)

Environment(s): Production and QA 
Effective Date/Time:  12/20/11 
To:  Integration Group Contacts
Purpose: Notify Court Integration Services consumers of an upcoming update.
Details: The following update will be applied to Integration Services

This is a special integration release to support the implementation of batch e-citations for the MN State Patrol – St. Cloud district.

The changes being made are to accommodate the special circumstance of citations that occur in the Benton County part of the City of St. Cloud, the Benton County part of the City of Sartell, or the Sherburne County part of the City of St Cloud, but for which the court case will be created in Stearns County.

return to top

Court Integration Services Release 30 (12/01/2011)

Environment(s): Production and QA.
Effective Date/Time: Thursday December 1, 2011 at noon
To: Integration Group Contacts
Purpose: Notify Court Integration Services consumers of an upcoming update.
Details: The following updates will be applied to Integration Services:

• An internal change to the services that store document images (TIFFs and PDFs) in MNCIS.   Currently when one of these documents is stored in MNCIS the number of pages shown for that document is zero.   This change will associate the correct page count with the document.   The impacted services are:
  • eFile Citation Supplemental Document
  • eFile Complaint Supplemental Document
  • eFile Case Document
• An internal change impacting the Citation Supplemental Document eFile service.  This change will cause the service to use court specific MNCIS document types when storing documents.  This is being done to allow security for these documents to be configured at a more granular level.
• An internal change to the Warrant Status Update service.   This service rejects warrant status updates with status dates that are in the future.    To allow for discrepancies in system times this service currently allows for status dates that are around 90 seconds in the future.   This will be increased to around 5 minutes.
• The ordinance simple type schema (OrdinanceOffenseCategoryType.xsd) and related companion file (OrdinanceOffenseCategoryType.xml) will be updated to include some new “County” ordinances.   A separate business communication will be distributed to explain the use of county ordinances. In addition, a new “AssociatedValue” element called “RepealDate” will be added to this simple type.
• The Statute simple type companion file (StatutoryChargingOffenseType.xml) will be updated to only include the associated value “RequiredAdditionalDataElement” when it is configured state-wide.  Currently there is an issue where there is unique configuration at a single court that appears in this file as if it is the configuration for all courts.

These changes are available for testing in Development and will be available in QA on Wednesday November 2.  

These updates did not require any schema changes, and implementing them in production will not require any system downtime.

return to top

Court Integration Services Release 29 (09/15/2011)

Environment(s): Production
Effective Date/Time:     Thursday September 15, 2011 at noon
To:  Integration Group Contacts
Purpose: Notify Court Integration Services consumers of an upcoming update.
Details: The following updates will be applied to Integration Services:

• A new e-file service for Juvenile Citations (citations citing criminal charges) will be implemented.  Juvenile citations can be submitted singly (similar to criminal complaints), or via batch. Juvenile eFile citation processing uses a separate message schema, but processing is similar to adult citation processing.
• A fix will be implemented to address a schema validation error that occurs when a juvenile judgment is amended. This bug was introduced in the last Integration Services Release while fixing a schema validation error that occurred when deleting an amended  juvenile judgment and an original judgment in the same transaction.

Due to the pending implementation of the Odyssey 2011 release to Production,  these changes will not be available for testing in QA.  The changes will be available for testing in Development on Wednesday August 17.   Also, the Court Integration Services website will be updated with information on Juvenile Citations on Wednesday August 17.

Implementing these changes in production will not require any system downtime.

return to top

Court Integration Services Release 28 (07/21/2011)

Environment(s): Production
Effective Date/Time: Thursday July 21, 2011 at noon
To: Integration Group Contacts
Purpose: Notify Court Integration Services consumers of an upcoming update.
Details: The following updates will be applied to Integration Services:

With release 2011, our court case management software vendor is delivering a fix that will address a MNCIS problem with vehicle license plate information.  This vendor fix is necessitating an internal change to the citation eFiling service.  This change does not require any updates to existing message formats, and should be transparent to users of the citation eFiling service.  This update should not require any system downtime to implement, and is available for testing in Development and QA. 

return to top

Court Integration Services Release 27 (07/07/2011)

Environment(s): Production
Effective Date/Time: Thursday July 7, 2011 at noon
To: Integration Group Contacts
Purpose: Notify Court Integration Services consumers of an upcoming update.
Details: The following updates will be applied to Integration Services:

• The Case Get service will no longer return Court Case Events that are ‘non-docketable’.  Court Case Events and their respective Comments are marked as ‘non-docketable’ when they are not intended to be part of the Register of Actions for the case.  Reasons for this practice vary;  such as when the Event and Comment relate to an activity that is not traditionally included on the Register of Actions, such as clerk notes and case reviews.  This modification to the Case Get service will apply to both public and confidential  MNCIS case types.   It is necessary to make the  Case Get service consistent with the provision of case information to government subscribers through MNCIS Odyssey Login Accounts (which do not provide access to ‘non-docketable’ Case Events and their respective Comments).
• A new service named Add Complaint Supplemental Document will be implemented.  This service is used in conjunction with eFiling of criminal complaints to add the image of the complaint to its associated case within the courts case management system.  The image of the complaint can either be in PDF or TIFF format.    Please see the courts integration services website for more information on this service.
• A fix will be implemented for the Family and Juvenile Judgment Court Decision notification services.   The fix corrects an issue that occurred when Judgments were amended and then the amendment and judgment were deleted.   When this occurred the delete of the original judgment was not published.

All updates are available for testing in Development and QA.    These updates did not require any updates to existing message formats and should be transparent to consumers of the updated services.  These updates should not require any system downtime to implement.

return to top

Court Integration Services Release 26 (05/05/2011)

Environment(s): Production
Effective Date/Time: Thursday May 5, 2011 at noon
To: Integration Group Contacts
Purpose: Notify Court Integration Services consumers of an upcoming update.
Details: The following updates will be applied to Integration Services:

• An internal modification to the CaseGet and CaseSearchByParty services to better track, and reduce the number of,  technical error responses due to system issues with servers and/or databases.
• An internal fix to the batch citation processing to better handle the error when a batch of citations is submitted with an invalid schemaVersion value.
• An internal modification to criminal complaint e-file processing to accommodate an upcoming change that will be included in the next release of Odyssey.  This change has to do with how error responses are returned for complaints that were submitted with an invalid prosecuting attorney bar number.   The result of the change is that the service will work the same as it does today after the new release of Odyssey is installed.

All updates are available for testing in Development and QA.    These updates did not require any updates to existing message formats and should be transparent to consumers of the updated services.  These updates should not require any system downtime to implement.

return to top

Court Integration Services Release 25 (03/10/2011)

Environment(s): Production
Effective Date/Time: Thursday March 10, 2011 at noon
To: Integration Group Contacts
Purpose: Notify Court Integration Services consumers of an upcoming update.
Details: The following updates will be applied to Integration Services:

• A modification to the process that validates incoming batches of citations.  Prior to this change when a batch included a citation that was not formatted properly, causing schema validation to fail, the whole batch would be rejected.   After this change all citations will be validated individually and if a batch contains some valid citations and some invalid citations only the invalid citations will be rejected with the valid citations continuing on to MNCIS.
• A modification to the process that performs schema validation processing for CourtXML messages to improve performance and to prevent intermittent validation errors that occur when MNCIS codes are modified.   Inbound and Outbound CourtXML messages will now be validated against a CourtXML schema that uses simple type schemas without enumerations.   All codes are still validated by either Integration Broker or MNCIS Processing but will not be validated by the schema.
• An internal correction to the component that retrieves documents from MNCIS to prevent an error that occurs if a document does not have a description associated with it.
• An internal change to the Other Agency Person Identifier eFile  Service.   This does not have any impact on how this service is used or on its message formats.

All updates, other than the internal change to the Other Agency Person Identifier eFile service, are available for testing in Development and QA.  The change to the Other Agency Person Identifier eFile service will be available in Development and QA on Wednesday February 23.  These updates did not require any updates to existing message formats and should not require any system downtime to implement.    

return to top

Court Integration Services Release 24 (10/28/2010)

Environment(s): Production and QA
Effective Date/Time: Thursday October 28 at noon for Production and Wednesday September 29 for QA.
To: Integration Group Contacts
Purpose: Notify Court Integration Services consumers of an upcoming update.
Details: The following updates will be applied to Integration Services:

• An internal change to the Other Agency Case Cross Reference eFile service.
• A modification to the error processing of the Other Agency Person Identifier eFile service. If duplicate ID values are submitted they will now be rejected with a fault message. In the past the service returned a successful response.
• A modification to the Biometric Collection Status eFile service to return a fault message if a non-criminal case is specified.
• A modification to the Case Detention Status eFile service to return a fault message if a non-criminal case is specified.
• Implementation of a new performance enhancement feature provided by the MNCIS vendor that prevents non-published case event updates from impacting the performance of publishing.
• A modification to Warrant Status Update eFile service to updates that failed with certain system errors.
• A modification to the case initiating eFile services (Complaints, Tab-Charges, Initiate Criminal Case and Citations) to prevent duplicate events from being added to MNCIS if their response messages are recycled due to system errors.

All updates are available for testing in Development and will be available in QA on Wednesday September 29.  These updates did not require any updates to existing message formats and should not require any system downtime to implement.

return to top

Court Integration Services Release 23 (8/19/2010)

Subject: Court Integration Services Release 23
Environment(s): Production and QA 
Effective Date/Time:  Thursday August 19 at noon for Production and Thursday July 22 for QA. 
To: Integration Group Contacts
Purpose: Notify Court Integration Services consumers of an upcoming update.
Details: The following updates will be applied to Integration Services:

• An internal update to the eFile Interpreter Status service.
• An internal update to the eFile Biometric Status service.
• Some internal updates to the eFile Criminal Complaint, eFile Tab-Charge, and eFile InitiateCriminalCase services.
  • Correction to processing done when a Prosecuting Attorney Bar number is included with a Criminal Complaint and a technical error occurs when validating the bar number. This fix will properly distinguish between this technical error and when the bar number is truly invalid.
  • An update to how the MNCIS "Send Notice" field is set for the defendant. With this update this field will be set to False rather than True.
• An update to the CourtXML_3 schema including a new complex type named FamilyJudgmentType2. This new type is a copy of the original FamilyJudgmentType with the following changes:
  • The Award element is now repeating to account for judgments with multiple awards.
  • For the Support/SupportAward element the child elements MethodTypeText and MethodFrequenceText are now optional.
  • The element Dates/Inactive/InactiveReason is now optional.
• A new version 3:4 of the Case Notification message will be made available in production. This change includes some fixes to the Judgment element (see the prior bullet for the CourtXML_3 change) and some new elements were added to the NotificationAdminHeader element including:
  • CaseStatus including the Status, Date and a Comment.
  • ProSeIndicator within the PartyIdentifier element.
  • CriminalDefendantAdditionalInformation for defendants on criminal cases including:
    • Other names
    • Other birth dates
    • Physical Details
    • Addresses
  • Warrant information within the PartyIdentifier element containing the warrant number, type and status for active warrants associated with the party.
• A new version 3:4 of the Case Get message will be made available in production.
  • Fixes to the Judgment element (see the prior bullet for the CourtXML_3 change).
  • Fixes to some of the IncludeAttorney indicators in the request message. The type of these elements has been corrected to be xs:boolean. Prior version of the schemas did not have a type for these element.

All updates are available for testing in Development and will be available in QA on Thursday July 22.  These updates did not require any updates to existing messages and should not require any system downtime to implement.

return to top

Court Integration Services Release 22 (5/27/2010)

Environment(s): Production and QA
Effective Date/Time: Thursday May 27 at noon for Production and Thursday April 22 for QA.
To: Integration Group Contacts
Purpose: Notify Court Integration Services consumers of an upcoming update.
Details: The following updates will be applied to Integration Services:

• Modifications to Batch Citation processing to do the following:
  • A fix to correct a response message validation error caused when some of the processing steps ran longer than expected causing them to overlap with subsequent steps. This correction will allow these steps to overlap as well as allow batch citations to update MNCIS with the Citation Filed, and Officer Notes case events at the time the citation is accepted rather than waiting until the next nightly batch run.
  • A modification to the processing to have error responses, caused by invalid batches, returned immediately if the transport used to submit the batch was either MQ Series or Web Services rather than waiting for the next batch run.
  • A modification to VIBES batch processing, for submitters using either MQ Series or Web Services, to have batches transmitted immediately to VIBES for processing when received by the courts broker, and response messages be returned immediately rather than only during the nightly batch run.
  • A fix to better handle the processing of responses when duplicate batches are submitted.

Note:  we are looking into making changes that would allow the transmission of responses back to submitters using FTP to be done in a timelier manner in a future release.

• A fix to the case get service to correct a problem preventing charges from being included in reply message that could occur when a user is updating the case at the same time that the case get service is retrieving that case from MNCIS.
• A modification to the case get service to add some additional logging that should help us to diagnose some service outages that we have experienced over the past couple of months.
• A fix to the CourtCaseHeaderGroup/CaseTitle element to correct a case notification message validation error caused by court cases not having a case title. This is usually a situation that occurs for only a short period of time on a given case while certain updates are being made to it.
• A modification to the Juvenile and Family Judgment CourtDecision notification to prepare for the upcoming MNCIS release 2009SP2. This change allows the notification to work the same with both releases.
• A fix to the criminal CourtDecision notification to process messages correctly in the event that a charge gets expunged. Prior to this change a schema validation error would occur if the expunged charge was associated to an amended sentence.
• New filtering options will be added to allow case notification subscriptions for family cases to be restricted to subsets of family case types. [Note: a court partner agency must submit an initial request form or a change request form, and have the proper authorization, in order to implement these or any other subscription options.] Previously, the filtering options for subscribing to notifications on family case types were as follows:
  • All family case types
  • CHIPS - Truancy
  • CHIPS - Runaway

New categories will allow for additional subscription filtering options in the family case line of business. These are the subscription case categories available with this release:

• Civil Domestic Violence
• Divorce
• Guardianship (Family) - this category includes cases filed for the purpose of having the court award the care, control and maintenance of someone or something to one of the parties to the case, and cases where the transfer of permanent legal custody is granted and the juvenile court ends its supervision
• Parent/Child Relationship - this category includes the full range of CHIPS (child in need of protective services) case types, as well as termination of parental rights cases
• CHIPS - Truancy
• CHIPS - Runaway
• Support - this category includes actions brought for the collection of child support
• Adoption
• Paternity
• Other Family - this category includes family court matters that do not fit into any of the other family case types

Documentation will be available on the State Court integration web site which will provide more information on case notification subscription options.

All updates are available for testing in Development  and will be available in QA on Thursday April 22.  These updates did not require any schema changes and should not require any system downtime to implement.

return to top

Court Integration Services Release 21 (03/25/2010)

Environment(s): Production
Effective Date/Time: Thursday March 25 at noon.
Details: The following updates will be applied to integration services:

• A fix to an issue with the Departure flags in the AdultSentence and DelinquencyDisposition elements. This impacts the CaseGet and CaseNotification services. The current set of codes used for DispositionCompoentValues/FieldName could not accurately represent the values that can be specified for departure within MNCIS. They could not represent instances when there was both a dispositional departure and a durational departure. The existing codes (UpwardDeparture, DownwardDeparture, DispositionalDeparture, and DurationalDeparture) will be made obsolete and the following set of new codes will be used to represent departure data:
  • DispositionalDepartureUpward
  • DispositionalDepartureDownward
  • DurationalDepartureUpward
  • DurationalDepartureDownward
• An update to the PersonPhysicalDetails and ChildPhysicalDetails elements to fix an issue with the formatting of Race data. This impacts the CaseGet and CaseNotification services.
• A new service will be made available that allows law enforcement agencies to submit documents (in PDF or TIFF format) to the court and have them attached to the case associated with the citation within MNCIS. The types of documents that can be submitted are: Citation Image, Victim Notification Request, Driver Record (45), Vehicle Record (28), and Police Report. This new service is currently being piloted in Dakota County and statewide implementation is dependent upon expansion of the document imaging functionality within MNCIS/Odyssey.
• An internal update to the Other Agency Note and Case Defendant Status eFile services. There is no change to how these services are used.
• An internal update to the CaseNotification service to fix some validation errors that can be caused by users making multiple updates to a sentence within a short period of time when there is a publishing backlog.

Other than the final 2 bullets these updates are now available for testing in Development.   All updates will be available in both Development and QA on March 4.  These updates did not require any schema changes and should not require any system downtime to implement. 

return to top

Court Integration Services Release 20 (02/04/2010)

On Thursday February 4 at noon the following updates will be applied to Integration Services in production:

• Update the eFile Criminal Complaint submission processing to make use of the Prosecutor element to assign an attorney as the prosecutor on the newly filed case. This element has always been in the Criminal Complaint schema but had remained unused until now. This is also being done for the Initiate Criminal Case message that is currently only used in Ramsey County.
• Implement a new version (3:3) of the CitationDocument schema. The following changes were incorporated into this new version:
  • The ProsecutingAgencyORI element is now required. This will require that the prosecuting agency be specified on all citation submissions.
  • Two new groups of elements have been added to the citation submission. One is used to indicate the parking space for parking offenses and the other is to indicate the expiration month and year of the vehicle license plate.
• This new schema is used for both single citation eFiles and for batch citation submissions.   With this new version we are setting the inactivation date for the prior versions of the schema (3:1 and 3:2) to be July 30, 2010.   These schemas are being inactivated because they do not require the Prosecutor ORI element which is required by MNCIS for Auto Assess processing of fines and fees.    Versions 3:1 and 3:2 will continue to work until July 30.  After July 30, 2010 citations submitted at versions 3:1 and 3:2 will be rejected.    Version 3:3 of this schema is available for review on the CourtXML page of our Integration Services website.
• The minimum required to begin using the new version of the schema is the following 2 changes:
  • Change the value in the schemaVersion attribute of the message body's root element to be "3:3".
  • Include the ProsecutingAgencyORI element.
•  The Warrant Status Update eFile service has been corrected to report "Warrant Not Found" rather than "Case Not Found" when the specified warrant number does not exist within MNCIS.
•  A fix is being applied to the Case Search by Party service to make it return some additional identifiers that were being skipped by the service. These identifiers were always included in the schema but were never implemented by the service. They include:
  • PersonFBIID. The FBI identifier assigned to the matching party.
  • PersonOtherID. This is an ID value that is assigned to the party usually by an outside agency.
  • Group. This value identifies one or more groups that the party has been assigned to. Family is an example of a type of group.

Other than the first bullet (Prosecutor Assignment) these updates are available for testing in the Development and will be available in QA on January 7.  Other than the new citation document schema this update did not require any schema changes and should not require any system downtime to implement.

return to top

Court Integration Services Release 19 (12/03/2009)

On Thursday December 3 at noon the following updates will be applied to Integration Services in production:

• Update the CaseGet service to the .Net Framework version 3.5 and Visual Studio 2008.
• Update the CaseSearchByParty service to the .Net Framework version 3.5 and Visual Studio 2008. Also fix an error that caused a soap fault to be returned if 2 or more case type restriction values are specified, both the code and text values are included on the case type restriction and 2 of them have the same text value.
• Update the eFile Response publishing service to the .Net Framework version 3.5 and Visual Studio 2008. Also fix the issue associated with Ticket 148334 (MNCIS Defect 5335) that prevented response messages for certain WarrantStatusUpdate eFile submissions from being published.

These updates are available for testing in both the Development and QA environments.  They did not require any schema changes and should not require any system downtime to implement.

return to top

Court Integration Services Release 18 (10/15/2009 and 10/16/2009)

On Thursday October 15 the following updates will be applied to Integration Services in production:

• No Contact Order Notification change. This case notification message has been updated to include the following additional condition types. This change includes an update to the ConditionNoContactType simple type schema and companion file to include these new conditions.
  • Do not enter additional locations (NOENTADDLO)
  • Do not enter or call victim's place of employment (NOENTREMPL)
  • Do not enter victim's residence (ENTVICTRES)
  • No contact with known gang members (NOCNTGANGM)
  • No contact with Vulnerable Adults (NOCONTVUAD)
  • No unsupervised contact with child in certain circumstances (NOCNTCHILD)
• The StatutorySupplementalOffenseType simple type schema and companion files have been updated to include ordinances to accommodate a recent configuration change that allows ordinances to be used as additional statutes on charges.
• The ExtendedPartyConnectionType simple type companion file has been updated to include the associated party base connection (BaseConnectionTextType) for each extended connection.

Updated simple type schemas and companion files will be available around 6:30 am on October 15 and the change to the No Contact Order Notification will occur at noon on October 15.   These updates did not require any schema changes and should not require any system downtime to implement.  

These updates have already been applied to the development environment and are currently being tested.

On Friday October 16 we will move our production broker over to a new set of clustered servers.   We are contacting technical staff for all Integration Services consumers in separate correspondences to coordinate with them any changes that are required to accommodate these new servers.    The changes that are being made include:

• For consumers that connect to Integration Services via MQ Series Server channels, new channels will be defined between the new broker queue manager and your queue manager.
• For consumers that connect to Integration Services via MQ Series Client the configuration of the client application configuration will have been changed to connect to the queue manager on the new broker.
• For consumers that connect to Integration Services via MQ Series (Either Client or Server) any references to the old queue manager (MSCJB02P) will need to be changed to the new queue manager name (MSCJB01P)
• For consumers who submit messages (such as case gets and eFiles) to our broker through HTTP we will update our network to route messages to the new broker servers using the same URL that is currently being used. This is all done internally and does not require the consumer to make any changes.
• For consumers who receive messages (such as notification messages and eFile responses) the IP address 156.98.54.34 and 156.98.54.35 will have to be allowed into their firewall in the same way that the current IP 156.99.86.15 was allowed in.

On April 1st 2010 we will be retiring our original version of eFiling complaints.    This version was only used in Carver and St. Louis Counties.

return to top

Court Integration Services Release 17 (08/06/2009)

On Thursday August 6 at noon the following updates will be applied to Integration Services in production.   These changes include:

• Some fixes to the transforms that produce CourtXML elements. These fixes are to correct the following:
  • An error that caused Court Decision Case Notification messages that resulted in a single charge being included multiple times when dispositions associated with that sentence have been amended.
  • A validation error with Family Judgment and Juvenile Judgment elements (within both Case Notifications and Case Gets) caused by a monetary award that that did not have a type specified.
  • A validation error with the Charge Disposition Case Notification message that could occur when a plea and disposition are deleted at approximately the same time depending on the current publishing backlog and the amount of time between updates.
• A fix to the process that produces e-File response messages such that when MQ Series messaging is used the MessageID from the original submission message is used as the response message's CorrelationID. The CorrelationID value was incorrectly being set to the MessageID value from an intermediate message.
• An internal change to the processes that produce notification messages to help the Integration Team in knowing when validation errors occur, and to aid in troubleshooting them.
• A modification to the batch citations processing to better handle input batches that are not well-formed xml documents. Currently when these batches are received no further processing is done with them. This fix will cause a response to be produced and returned to the submitter indicating that there was an error with the batch.
• A fix to the Court Decision notifications for Family case types. With the most recent patch to Odyssey we are now able to publish deleted judgments. Prior to this patch and fix none were produced. The following two notification events will now be included with the Court Decision notification when these deletes occur:
  • CourtDecisionDeleted - if the judgment is deleted
  • CourtDecisionAmendmentDeleted - if an amendment to a judgment is deleted

These updates have already been applied to the development environment.

These updates did not require any schema changes and should not require any system downtime to implement.

return to top

MNCIS Change (06/01/2009)

On June 1st a change will be implemented in MNCIS that will cause the Level of Sentence to be included in CourtXML messages that contain criminal court decisions.  The level of sentence element has always been in the CourtXML schema though it has been empty up to this point.   This does not require changes to any Integration Services or any updated schemas.  The attached file is a fact sheet describing what the level of sentence is. 

In Court XML, Level of Sentence is represented by the SentenceChargeSeverityLevel element.  This element is returned with CourtDecisionNotifications and CaseGets that include CourtDecisions.  Both AdultSentences and DelinquencyDispositions can include the Level of Sentence.

Level of Sentence Fact Sheet

return to top

Network Change (06/05/2009)

In the near future the Judicial Branch will be changing the IP address for https://is.courts.state.mn.us.   This is the address that is used to access production query and submission services when using http.  This change has no impact on Notification services or on consumers that use MQ Series to access services.  We update our internal DNS and send a request for OET to update the "courts" DNS name space record for that host. These changes should be transparent to your application unless you used your own internal DNS to resolve is.courts.state.mn.us to the IP address (this should not be common)  or use host files to reference the name to the IP address(if this is the case, the new IP is 156.98.54.40). There are agencies that I am sure block outbound traffic from their servers and they should request immediately that outbound traffic to 156.98.54.40 be allowed from services that are accessing Courts web integration services because the IP address for the host IS will be updated at midnight on Thursday June 4th.  The new IP address is up and available to any of you who use host files, otherwise it will be updated as the DNS tables timeout after midnight on the 4th.  Friday, June 5th, will be the first day it is in effect.    Both the old and new IP address will be available until June 12th.  After that date only the new IP address will work.

If you are a consumer of a Notification service or a consumer using MQ Series to access services we will be contacting you over the next few weeks to make similar changes.

return to top

Court Integration Services Release 16 (05/07/2009)

On Thursday May 7 at noon the following update will be applied to Integration Services in production:

A fix to the CaseSearchByParty service will be implemented.  This service was producing incorrect error messages when certain input was specified.   These included entering more than 20 characters for StateID, OtherID and FBIID searches,  and Name/DOB searches  with years earlier than 1753.  The fix will allow these searches to be successfully processed and produce better error messages when applicable.  This fix does not require any schema changes.  

This update has already been applied to the development environment.

This update is not expected to cause any service down time. Please let me know if you have any questions.

return to top

Court Integration Services Release 15 (04/09/2009)

On Thursday April 9 at noon the following updates will be applied to Integration Services in production.   None of these updates result in any schema or message changes or result in any immediate changes to how any service works.   They are some internal changes that will be put in place to improve service reliability and flexibility in some areas.

• eFiling will be updated to automatically retry on two additional technical system rejections. When eFiles are rejected because of a purely system error (such as a database blocking problem) the integration broker automatically retries them assuming the condition that caused the error may have cleared up and to prevent the rejection from having to be returned to the submitter.
• eFiling and Notification messages are being updated to support both soap version 1.1 and soap version 1.2. Currently all notification messages and eFile response messages are published using soap version 1.2. After this change notification messages can be configured to publish using either version, and e-file response messages will be returned using the same version as their corresponding submission message. Notification messages will continue to publish using soap version 1.2 unless you ask the integration team to reconfigure your subscription to use the other version. Query services, such as CaseGet, have always supported both versions. This has no impact on the version of CourtXML that is used.
• A fix to the CaseNotification service is being implemented to eliminate some schema validation errors that can occur with the CourtDecision and ChargeDisposition notification messages when dispositions are deleted immediately following some other update to either the associated sentence, charge, plea or to the disposition itself. This fix is an internal change to handle these deletes properly and does not require any schema change.
• Processes running on the integration broker that add case events back into MNCIS are being updated to use a more reliable method to do so. The integration broker usually adds case events to MNCIS as a result of some other action that it performs, such as receiving an e-filed case or sending a message to a business partner as the results of a point-to-point integration. This change involved the following processes:
  • eFiling of citations, batch citations and criminal case initiations. Note: complaints and tab-charges have been using this new method since release 14.
  • BCA Criminal History
  • DPS Certifications
  • DNR Dispositions
• The eFile Case Event Notification service (Currently only used by Ramsey County) has been modified to have eFiling produce its messages rather than publishing.  This cuts down the trips through the publisher for this service from 2 to one which will speed up the production of these messages.
• The process for producing the CommunityOfOffense simple type comanion file has been updated to exclude courts from communities for which they are hidden and not available for use at.
• The process for producing the HearingTrialCancelReason simple type companion file has been updated to exclude some cancel reasons that are not available within the application.

These updates have already been applied to the development environment.

These updates are not expected to cause any service down time.    Please let me know if you have any questions on any of them.

Note: this was initially scheduled for 04/02/09 but was pushed forward a week due to a scheduling conflict.

return to top

Court Integration Services Release 14 (01/23/2009 and 02/05/2009)

As a part of this release there will be 2 separate updates.   One update will be applied at the same time as the new release of Odyssey.   The 2nd part will be applied 2 weeks following that date.

January 23rd after hours (during the Odyssey Release 2008 migration downtime) **

• Fix an internal error with ‘CourtDecisionModified' notifications that was reported in Service Desk ticket 133060 from Ramsey County. A deleted sentence condition was being published in the scenario where a sentence condition is being deleted in the same transaction where a sentence condition is being added. This does not require any schema change.
• An internal change is being made to accommodate a change to the Odyssey Internal XML interface relating to case events and interim conditions. This will not result in any schema or message changes. This will not be fully ready to test in dev until December 29. The following areas are affected by this change:
  • Case Gets of Interim Conditions
  • Interim Condition Order Notifications
  • No-Contact Order Notifications
  • Case Gets of Case Events
• A change is being made to the events that trigger the Interim Conditions Order Notification. This change does not require an update to the schema. The events for this notification, along with any changes, are listed below:
  • InterimConditionsAdded - trigger this notification when a condition set is added. The published message will reflect the current state of the condition set.
    • This is unchanged from today.
  • InterimConditionsModified - trigger this notification when an existing condition set is modified (e.g. conditions are added to or removed from the set; the judge or order date is updated; condition set comments are added, updated or removed; individual conditions are updated (location, comments, amount); or the expiration date is removed, or added/update with a future date). The published message will reflect the current state of the condition set.
    • This is a change from today. Today when an individual condition is deleted from a set, an InterimConditionsDeleted message is being produced. The published message reflects the current state of the condition set, but this has been misinterpreted. Some consumers thought that the message was specifying what conditions are being deleted from the set.
  • InterimConditionsDeleted - trigger this notification when the condition set is deleted. The published message will reflect the condition set that has been deleted.
    • This is a change from today. Today, when a condition set is deleted, an InterimConditionsExpired message is being produced. This is due to limitations with the current release of Odyssey - Tyler is addressing this in the new release.
  • InterimConditionsExpired - trigger this notification when the expiration date on a condition set is being set to the current date. The published message will reflect the current state of the condition set.
    • This is a no change from today (other than condition sets that are deleted will be represented as InterimConditionsDeleted notification events, rather than InterimConditionsExpired.
• The element SentenceChargeSeverityLevel, in adult sentences and juvenile delinquency dispositions, will begin to be populated with the severity level for the sentence. Prior to this it was omitted from messages. This impacts all versions 3:# of CaseGet and CaseNotification messages that include an AdultSentence or DelinquencyDisposition element, though it does not result in any schema changes because the schemas already contain this element.

February 5th at noon **

• An update is being made to the CourtXML_3 base schema to fix a problem found with phone numbers that end in 4 zeroes. The SubscriberID element is being changed to have an integer data type rather than a positive-integer data type. This will impact all 3:# schemas that include telephone numbers. The internal schema version for this version is 18.
• eFile and Batch Citation Response messages that contain errors because of missing required blood alcohol parameters will now have a new ReasonText value that states the error more clearly. Prior to this fix the value for ReasonText when this error occurred was "DPSGroup/Status is a required field.". After the fix the ReasonText value will be "An offense is missing required blood alcohol parameters".
• An internal change is being made to the CaseGet service. This change will allow it to process requests that include multiple cases more efficiently. When multiple cases are specified they will be processed in parallel rather than one at a time. This does not change the message format or how the service is used.
• An internal change is being made to how warrants are published by the case notification and case get services. This change will improve performance when cases are being published that have multiple warrants. This does not require a schema change.
• An internal change is being made to the Case Search by Party service. This change fixes a problem that occurs when multiple court locations have been specified and one of the requested locations is subordinate to another. This does not require a schema change.
• The value for the soap header wsa:Action, within Criminal Complaint and Tab Charge response messages will be changing. Prior to this change response messages for both Complaints and Tab Charges had the same value (http://www.courts.state.mn.us/IS/02/SubmitComplaintTabChargeResponse). This change will provide each response message type with a unique wsa:Action value which will make it easier for receiving services to route them to document specific processes. The new values are listed below:
  • Complaints: http://www.courts.state.mn.us/IS/02/SubmitCriminalComplaintDocumentResponse
  • Tab Charges: http://www.courts.state.mn.us/IS/02/SubmitTabChargeDocumentResponse
• A fix is being made to the HearingTrialSetting element that is included in case notification and case get reply messages. Prior to this when a hearing was cancelled the comments entered as a part of cancelling the hearing were not always included. This fix does not require a schema change.
• The property damage type code of "NO" (No property damage) is being removed from the PropertyDamageType simple type. This code is already obsolete and has never been used in Minnesota. It is being removed to eliminate some confusion that it caused on the Property Damage element.

Also we would like to direct you to some updates that have recently been made to the Courts Integration Services website.    
They are:

• The CourtXML Schema page has been updated to show status information pertaining to versions of schemas. Also included is information about our support policies for schema versions that have been superseded by newer versions.
• A new page has been added that shows the history of all integration services update notifications that are published describing changes to integration services (such as this one). When an update notification is being sent it will also be added to this page. Each prior release has been given a sequential number which is how this release was given the number 14.

** These dates depend on the Odyssey 2008 release being applied as planned on the evening of January 23.

return to top
 

Court Integration Services Release 13 (09/11/2008)

An updated CourtXML_3 schema (internal schemaVersion 17) is being published with a change to the measureUnitText attributes of both the PersonWeightMeasure and PersonHeightMeasure elements. The measureUnitText attribute for weight has been assigned an enumeration value of "Pounds". The measureUnitText attribute for height has been assigned an enumeration value of "Inches". These were always the only values that were accepted or published in these attributes and errors would have occurred if other values were provided. This updated schema has been posted on the IS Website.

The following case notification types have been expanded to publish for all case types. No schema changes were required.

• Case Details
• Case Security
• Interim Conditions Order

The subject party (case) notification will be updated to produce notification messages when changes are made to attorney addresses with respect to cases they are assigned to. 3 new notification events will be added:

• AttorneyAddressAdded
• AttorneyAddressModified
• AttorneyAddressRemoved

The following internal infrastructure changes are being made to improve the performance and reliability of service. These changes do not have any impact on how the services are used.

• eFiles that are rejected due to system problems, such as database blocking or network errors, will be automatically retried. This is to cut down on the number of eFile rejection response messages that are caused by system errors.
• The CaseGet service is being updated to process requests that include multiple cases more efficiently. When multiple cases are specified they will be processed in parallel rather than one at a time.
• All query services (CaseGet , CaseSearchByParty) have been updated to use the replica database rather than the primary Odyssey database to process their requests. This should cut down on the load on the primary database (used by Odyssey users) and should eliminate the need to have these services shut down during the week for regular system maintenance. Note: This will not be fully implemented until the next major release of Odyssey is installed in production around the end of this year.

These changes are not expected to cause any service down.    Please let me know if you have any questions on these changes.

return to top
 

Court Integration Services Release 12 (08/14/2008)

 Effective with this release, Social Security Numbers will no longer be included in any Case Get or Case Search by Party response, or in Case Notification messages for public case types such as adult criminal cases and juvenile delinquency (over 16) cases unless a specific request is made to include SSN.   This change may have minimal impact on the data you receive because Social Security Numbers are not often provided to court staff or entered into MNCIS.  

If there is a business need to receive SSN for public case types, please use our Change Request Form to request it.   Section 3 of the Change Request Form deals with this particular type of request for SSN.   A court order will be required for receiving SSN on public cases,  so please limit your request to receive this data for your county or district.   If your agency is currently authorized to receive confidential case types, such as juvenile delinquency (under 16) or juvenile petty offenses, SSN will continue to be included in existing messaging, to the extent that it is available in our case records. 

This change is not expected to cause any service down time and does not involve any schema changes.  Please let me know if you have any questions on this change.

return to top
 

Court Integration Services Release 11 (06/26/2008)

New CaseGet schema version: A new version 3:3 (internal schemaVersion 1) case get schema will be published that supports all case types within the Family case category. Versions 3:1 and 3:2 will remain active and no retirement dates have been set for them at this time. The following changes have been implemented with this schema version:

• SubjectParty requests may now include CaseRespondent elements representing parties who are respondents to family court matters.
• CourtDecision requests for Family cases may now include FamilyJudgment elements. The FamilyJudgment element applies to all Family cases that are not considered "Parent/Child Relationship" case types. Parent/Child Relationship case types are already included in previous versions as Juvenile Judgments.

New CaseNotification schema version: A new version 3:3 (internal schemaVersion 1) case notification schema will be published that supports all case types within the Family case category. Versions 3:1 and 3:2 will remain active and no retirement dates have been set for them at this time. The following changes have been implemented with this schema version:

• SubjectParty and FamilyCaseInititation notification messages may now include CaseRespondent elements representing parties who are respondents to family court matters.
• FamilyCaseInititation notification messages will now be published for all Family case types. Prior versions only include case types categorized as "Parent/Child Relationship" cases.
• CourtDecision notification messages will now be published for all Family case types. For Family cases that are not "Parent/Child Relationship" cases a new FamilyJudgment element will be included with this notification. Parent/Child Relationship case types are already included in previous versions published as Juvenile Judgments.
• A new notification type named OtherAgencyCrossReferenceNotification has been added to publish changes to other agency numbers on cases.

New CourtXML_3 schema published: An updated version of the schema CourtXML_3 will be published. The internal schemaVersion value for this version is 16. This update is being done to support the new 3:3 versoins of the CaseGet and CaseNotification services and do not impact any existing messages. This update includes the following changes:

• A new type named CaseRespondentType has been added to be used by versions 3:3 of the CaseGet and CaseNotification services.
• A new type named FamilyJudgmentType to be used by versions 3:3 of the CaseGet and CaseNotification services.
• The following new SimpleType schemas are now referenced in support of the FamilyJudgment changes:
  •  JudgmentInactiveReasonTextType.xsd
  • PropertyTextType.xsd
  • JudgmentAwardSatisfactionTypeTextType.xsd
  • JudgmentAwardSatisfactionDocumentTypeTextType.xsd
  • JudgmentAwardSatisfactionCostsTypeTextType.xsd
  • JudgmentSupportTypeTextType.xsd

New SubjectParty notification events: The subject party notification will have 3 additional events. These events will be used to notify consumers when address changes have been made for subject parties on cases. The new events are: SubjectPartyCaseAddressAdded, SubjectPartyCaseAddressModified and SubjectPartyCaseAddressDeleted. These new events will be available with versions 3:1, 3:2 and 3:3 of the case notification service.

Fix to the SubjectParty notification: MNCIS provides the ability to replace one party on a case with another party which did not previously trigger the subject party notification. The normal practice is to remove the party and then add a new party which does trigger the subject party notification. This fix will cause the replace function to also trigger this notification.

Update to ParrentGuardianCustodian subject party element. This element within case gets and case notifications will now also be produced for tribal representatives. This change impacts versions 3:1, 3:2 and 3:3 of case gets and case notifications.

Fix to the Warrant notification: MNCIS allows warrants to be added on cases for an attorney. Prior to this fix a validation error would occur because the warrant message would not contain a warrant subject. With this change the warrant will be properly formatted with the attorney as the warrant subject in cases where the warrant is for the attorney.

New CaseDetails notification event: An additional event will be added to the CaseDetails notification message to inform consumers when case flags have been modified. Prior to this change events existed to inform consumers that flags have been added and deleted. This new event (CaseFlagModified) will indicate that an existing flag has been modified. Currently the comment on the case flag is the only field that can trigger this event. This new event will be available with versions 3:1, 3:2 and 3:3 of the case notification service.

Update to the InterimConditions notification: The interim conditions (case) notification has been modified to no longer publish the event InterimConditionsExpired when the expiration date has been modified with a future date since the conditions are not yet expired. Consumers will have to look at the expiration date to determine if and when a condition will expire. This change affects versions 3:1, 3:2 and 3:3 of the case notification service.

Fix to the No contact order notification: This notification previously could have been published when changes were made to conditions other than the "No Contact" condition. This change will restrict publishing of this notification only to be caused by changes that are associated with the "No Contact" condition.

Change to eFiling: A new security check is being added to prevent a submitter from eFiling updates to cases that they do not have access to. For example, unless a submitter is explicitly given access to sealed cases they would not be able to submit an attorney assignment on a sealed case. 

Other than the new OtherAgencyCrossReferenceNotification case notification message all changes are available for testing in the development environment.   An update will be sent out when this message is ready for testing.

Updated and new schemas are available for download on the integration services website.   While the update may take up to 60 minutes to fully implement is not expected to cause any service downtime.   Please let me know if you have any questions on any of these changes.

return to top
 

Court Integration Services Release 10 (03/27/2008)

An updated version of the CourtXML_3 schema will be published that includes the following changes:

• The complex type NoContactOrderType, used by the NoContactOrder case notification message, has been changed to include 3 optional attributes that are used to link the no contact order back to the Interim Conditions Order, or the Sentence, that triggered the NoContactOrder notification. They are (orderEventKey, sentenceEventKey and sentenceDelinquencyDispositionKey). This type has also been changed to include 2 additional comment fields. These are OrderCommentText and ConditionCommentText which will contain comments that may have been entered that pertain to the Order or to the individual condition that is being published with the NoContactOrder notification. These changes impact the CaseNotificaiton service version 3:2.
• The complex type InterimConditionsOrderType has been modified to include an additional comment element named OrderCommentText which will contain the comment entered for the interim conditions order if one exists. This affects the CaseGet service versions 3:1 and 3:2 for the InterimConditions option, and the CaseNotification service versions 3:1 and 3:2 for the InterimConditions notification.

The element UpdateWarrantStatusResponse within the schema for the WarrantStatusUpdate service, version 3:1, is being modified with the following changes:

• An attribute named "code" is being added to both the PendingCourtReview and Rejected ResonText elements that will contain a code that is associated with the specific reason text value that is contained in the message.
• The Rejected ReasonText element has been changed to be repeating to allow for a warrant status update message to be rejected for multiple reasons.
• Note: these two changes will eventually be made to all eFile response messages.

The WarrantStatusUpdate service is being modified to return a WarrantNotFound soap fault rather than a CaseNotFound soap fault when updates are submitted for warrant numbers that do are not found within MNCIS.

An update to the XML Web Service will be implemented that incorporates the schema changes noted above.

The update process may take up to 30 minutes, though the changes are not expected to cause any service down time.   Updated schemas have been posted on the IS website for review and updated services can be tested in the development environment.   Please let me know if you have any questions on any of these changes.

return to top
 

Court Integration Services Release 9 (03/13/2008)

An update will be applied to the eFiling response publishing program to fix a problem with some system errors being returned as CourtXML Response messages rather than SOAP Faults.   This fix is associated to Remedy Ticket # 50474.

return to top
 

Court Integration Services Release 8 (02/28/2008)

1) New messages used to reset and cancel hearings. Two new pairs of submit and response messages have been added to the schema ScheduleHearing_3_1.xsd. These messages are used to reset scheduled hearings to new dates, and to cancel scheduled hearings. The existing messages that are used to schedule hearings are unchanged.

2) New service to set Interpreter Required flag. A new service will be made available to allow partner agencies to notify the court that an interpreter is required or not required for a given court case.

3) New service to set the biometric collection flag. A new service will be made available to allow partner agencies to notify the court when it is necessary, or no longer necessary, to collect biometric information on a case defendant.

4) New service to notify the court of the custody status of a defendant. A new service will be made available to allow partner agencies to notify the court of the custody status of a defendant on a case.

5) Warrant notifications for Probate and Civil case types will be published. We will begin publishing warrant notifications for warrants on Civil and Probate case types. Prior to this they were only published for Criminal and Family case types. Depending on your subscription you may begin receiving them on the 28th. Please let me know if you are not sure about what your case notification subscription is configured to include.

6) Hearing notifications for Probate and Civil case types will be published. We will begin publishing hearing notifications for hearings on Civil and Probate case types. Prior to this they were only published for Criminal and Family case types. Depending on your subscription you may begin receiving them on the 28th. Please let me know if you are not sure about what your case notification subscription is configured to include.

7) Message Correlation will be available. This is a new feature of eFile/submission messages that will allow a message to be associated to a message that has been sent earlier. The purpose for message correlation is to allow for submission of subsequent messages prior to having received the response messages for prior messages. An example of this is scheduling a hearing on a case that will be created for a complaint you have just eFiled. You may not have received the case number associated with the case created as a result of the complaint, which is needed by the schedule hearing message. Rather than sending the schedule hearing message with the case number you have an option to include the eFileID of the complaint message instead. The eFileID of the complaint submission is included in the schedule hearing message's CorrelationeFileID element. The service will use the CorrelationEFileID to determine which case the hearing should be scheduled on. This change does not require a schema change.

8) Additional option for receiving notification and response messages. A new option will be available for how notification and response messages are delivered. Currently all notification and response messages are "pushed" to an address that is specified by the receiver. This address equates either to a web service hosted on the receivers web server, or to an MQSeries queue hosted on the receiver's MQSeries server. The new option allows the receiver to "pull" these messages. Periodically the receiver will make a web service request to see if any messages are available to be pulled and pull them if there are any. This option is most appropriate for smaller offices with lower volumes of messages, and in situations where some delay in message delivery is not an issue. Additional global elements have been added to all submission and notification schemas to support this. These new elements are not required to be used and do not affect any existing messages.

9) Update to pro se flag on participants without attorneys. Prior to this update if parties on a case had no designation as to whether they have an attorney or not, they were identified as being "Pro se". After this change they will only be identified as being "Pro se" if within MNCIS an update is made that signifies this. If they are specified as being "Pro se" and do not have an attorney identified for them within MNCIS they will not have a "RepresentedBy" element. This change affects the CaseGet and CaseNotification services though it does not require a schema change.

10) An update to 3:2 case notification schema to include a new "Custody Order" notification. New outbound case notification when the court orders a defendant released from custody on a particular case. This notification is based on custody status of an individual on a case but may not reflect the overall custody status of that person.

11) An update to 3:2 case notification schema's SubjectPartyNotification element. In order to accommodate a MNCIS user removing more than one attorney from a party within one transaction the "AttorneyRemovalInformation" element has been changed to be repeating.

12) An update to the base CourtXML version 3 schema will be published. This schema has been updated to include new elements used by the Custody Order notification.

13) An update to the web service that is used to access integration services will be published. The web service that is used to access integration services is being updated to include methods for accessing all integration services. Prior to this only selected services were available through the web. Also a second web services option is going to be available. The current web service provides only generic WSDL support and requires a separate WSDL file in order to define the XML elements that are included in the service. The new service incorporates the CourtXML schema into its WSDL so that the WSDL and the service are both available from the same endpoint. Both types of web service will continue to be available and either can be used. This change does not affect any existing use of the web services. 

The update process may take up to 30 minutes though the changes are not expected to cause any service down time.   New and updated schemas have been posted on the IS website for review and updated services can be tested in the development environment.   We are currently working on documentation for all of the new services.   Please let me know if you have any questions on any of them.

return to top
 

Court Integration Services Release 7 (01/28/2008)

1) An updated CourtXML base schema (CourtXML_3.xsd) will be put in place. This update includes the following change:

The data type for AddressZipCode, within nonstandard US addresses, has been changed from integer (xs:int) to be a string (xs:string) with a pattern that enforces the zip code format ((\d{5}|\d{9})).   The AddressZipCode within standard US addresses had already been changed to use this format and the change was missed within nonstandard addresses.   The reason for this change is to accommodate zip code values that begin with zero.   Values such as 05123 would be invalid integers and would result in validation errors even though they are valid zip code.  This change does not result in any required changes to messages.

2) An updated version 3:1 CitationDocument schema (CitationDocument_3_1.xsd) will be put in place. This update includes the following change: 

The element SubmittingAgencyNameText was changed to have a minimum length of 1.   This is a required element in the schema and if citations are submitted with this element containing an empty value an error occurs.   This change allows the schema to enforce this requirement and prevent errors that result when it is empty.

A new element named InCustodyIndicator has been added to the Citee element to allow the submitter to note that the person that is receiving the citation is in custody.   This is an optional element and if omitted it is assumed that the person receiving the citation is not in custody.  This schema change does not require any changes to messages being submitted unless you have a need to use the new element.

3) A new Fees sentence component will be added to criminal court decisions. Sentence components show up in CourtXML as SentenceDispositionDetail elements within AdultSentence and DelinquencyDisposition elements. This new component will not result in any schema changes, though there will be one additional value (Fees) in the DispositionSentenceType enumeration to denote when this component is used, and many new values in the DispositionComponentValueType enumeration for all of the fee schedules that can be chosen as a part of this component. This new component will not be configured for use in all courts. Currently it is being tested in Hennepin County for use on adult criminal cases beginning in January or February of next year.  

4) The fix to the Case Search by Party service corrects a problem caused when name searches were used and those names included spaces.   When this occurred matches were not found.  An example name including spaces is "St. Michel".     Also with this fix, searches using business names are now available.   Prior to this fix all requests specifying business names resulted in an error stating that business names were not supported yet.

These updates can be tested now in the development environment.  

Updated schemas have been posted on the IS Website.

These updates are not expected to require any downtime.    The entire update process may take close to an ½ hour,  though it only requires that services are stopped and restarted which only takes a few seconds for each service.  Please let me know if you have any questions regarding this update.

return to top
 

Court Integration Services Release 6 (12/13/2007)

1) An updated CourtXML base schema (CourtXML_3.xsd) will be put in place. This update includes the following:

• a. Added minimum length of 1 to CourtFileNumber/ID, StatuteOrdinanceRuleCiteType and ChargeDescriptionTextType. These items were causing database updates to fail when they are required but contain no data. This change allows the schema to enforce the rule instead of the database. This will affect existing eFile messages that use these elements, though the effect will only be seen on messages that would have been rejected anyways.
• b. Made BondTypeText (within WarrantBondType) and WarrantConditionTextType (within WarrantConditionType) nillable. This allows eFiles that include these elements to specify either the code attribute or the element text value. This will not affect any existing messages.
• c. Added a new complex type BondOutType2 which replaces BondOutType in new versions of the Case Get and Bond Notification services. Current versions of these services are unchanged and still use the BondOutType complex type. The new bond format replaces BondCompanyText with SuretyBondGuarantorText to accommodate individuals as well as companies as the entity that is guaranteeing the bond.
• d. Added a new complex type CitationDocumentOutType. This complex type will be used by the new version (3:2) of the case get service.

2) Version 3:2 of the Case Get service will be implemented. The schema for this version has been posted on the IS website. This new version provides some additional options over what is provided in version 3:1. They include:

• a. Additional selection criteria for specifying which case, or cases, to be returned.
  • i. Citation number
  • ii. Control Number (Reporting and Arresting)
  • iii. Other Agency Number (Case Cross Reference number in Odyssey)
• b. Case information returned by the service uses the complex type BondOutType2 for bond information if requested.
• c. Added an option for requesting information on the citation that initiated the case.

3) Version 3:2 of the Case Notification service will be implemented. The schema for this version has been posted on the IS website. This new version contains the following changes from the 3:1 version:

• a. Added new notification types
  • i. Probation Order
  • ii. Note to Agency
  • iii. Transport
  • iv. Protection Order
• b. Added arresting and reporting control numbers to the notification header for criminal cases.

4) Version 3:2 of the Bond Notification service will be implemented. The schema for this version has been posted on the IS website. This new version contains the following changes from the 3:1 version:

• a. Modified to use the new complex type BondOutType2.

5) Updated eFiling services in preparation for implementing message correlation. Message correlation will allow subsequent eFile messages to be sent without the need to wait for responses to preceding associated messages. Correlation is not expected to be fully implemented until early next year.

6) Fix to a date processing routine used in eFiling. This fix corrects a problem that occurs when DateTime values include a timezone.

These updates can be tested in the development environment.   

For the new version 3:2 services, existing requests and subscriptions will not be automatically switched over from the old version to the new one.  The old versions will continue to work as they did in the past (unless noted otherwise above).   Currently no retirement date has been set for the 3:1 versions of these services.   To begin using the new versions of these services you need to do the following:

1) For the Case Get version 3:2 service you need to update your request message to conform to the schema CaseGet_3_2.xsd and make changes to your application to accommodate the format of the version 3:2 reply message.

2) For Case Notifications and Bond Notifications please let me know when you would like your subscriptions updated to the 3:2 versions.

You can switch over to using the new versions any time in Development, and any time after December 15 in QA and Production. 

return to top
 

Court Integration Services Release 5 (10/18/2007)

1) The timeout setting for case get and case search by party requests is being increased to cut down on the number of timeout errors that are returned by these services. The timeout setting is being increased to 5 minutes.
2) A fix is being applied to the hearing case notification service. This fix corrects a problem that occurs if a court user both edits the hearing type and resets the hearing within one save. When this occurred the notification message only indicated that the hearing had been modified and didn't indicate that the hearing was reset. After the fix the notification message generated when this occurs will include both a HearingModified and a SettingReset events.

return to top
 

Court Integration Services Release 4 (10/01/2007)

 Hearing Notification Fix:   It has been discovered that some specific changes that court users can perform on hearings scheduled on MNCIS calendars didn't trigger hearing notification messages.   The steps the MNCIS users are taking are not common business practice for making changes to hearings, and they do not occur often.  These include changing the hearing type or editing the start time without rescheduling the hearing, and changing the interpreter required indicator and changing the interpreter language.

After this update is applied the Hearing notification service will start publishing messages when these updates occur.   This change does not require a change to the schema but does include 2 new notification event types:

• HearingModified: Published at the time the hearing type is changed.
• SettingModified: Published at the time that the time is changed, or the interpreter indicator or language is changed.

This fix will affect all versions of the case notification service.

return to top
 

Court Integration Services Release 3 (08/27/2007)

1) A change to how the "Filed" case events are added to cases that resulted from eFiled Complaints, Tab-Charges and Citations to prevent the condition where a rejection response message is returned even though a case was created (issue 3986).

2) A fix to the Bond Notification service to properly handle the condition when a case is linked to more than one bond within one save.

3) A fix to the Subject Party Case Notification to properly handle the condition where one attorney is removed and another is added to a case party within one save.

return to top
 

Court Integration Services Release 2 (08/15/2007)

On Monday August 13 at 5 p.m. we will be promoting a fix to Integration Services into Production and QA.   This fix is to correct a problem identified by the Hennepin County Jail where they could not process the results of a case get reply for a specific case.    The error that is being corrected caused the charge description for certain charges to contain invalid data.

return to top
 

Court Integration Services Release 1 (08/03/2007)

1) Change to add the defendant name to hearing reset and cancel emails sent to court staff.

2) Fix to the formatting of telephone numbers to prevent validation errors when they include alpha characters.

3) Change to send eFile deadlock rejection response messages as soap faults.

4) Change to eFilings to add a Citation eFiled (IBCIT) case event to the MNCIS case created from the citation.

5) Fix to the case search by party service to prevent multiple parties from being returned when using the search by "partyKey".

6) Fix to the Warrant notification to suppress notification messages when the only update made is a change to a timestamp when printing the warrant.

7) Fix to the Charge notification to have notifications sent when GOC and Offense Dates/Times are modified.

 

All updates are available for testing in Development and will be available in QA on Thursday July 22.  These updates did not require any updates to existing messages and should not require any system downtime to implement.

return to top

Return to Court Integration Services