Mn Judicial Branch Logo
Find Court
    
   

Home > Court Integration Services >

Release Notifications

Last updated - 12/18/2014

The following are the contents of update notifications that have been sent describing changes to the Courts Integration Services.  As soon as a notification 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 notifications are published please contact the Integration Team and ask to be added to the mailing list.  

 

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 DNR (Department of Natural Resources) 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  Driver Vehicle Services (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 (Criminal History) system that are produced as a result of several batch jobs designed to update older MNCIS data.

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 (National Instant Criminal Background Check System) changes:

  • Juvenile cases with a case type of D16 (Delinquency Felony 16 or over) 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.

 

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 e-Citations using offenses citing rules or ordinances (this indicator does not exist in the 3:5 e-Citation schema). This will result in fewer rejections by court integration and by court staff. The 3:4 Adult e-Citation 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 e-Citation 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 Ody13 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 e-Citations 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 e-Citation 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 e-Citation 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 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 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 e-Citation 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 e-file 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 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 e-file 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 (National Instant Criminal Background Check System) changes:

-          Juvenile cases with a case type of D16 (Delinquency Felony 16 or over) 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

-          E-Filing

-          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.

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:
  1. Pass convictions that are defined by statute as certifiable, regardless of any subsequent action taken to decertify the offense.
  2.  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.

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 e-filed 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.

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 e-Filing schema will be inactivated.

Changes to e-Filing Services

  • An internal change was made to the Initial Release Conditions e-file 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 e-file 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.

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 e-Filing (Complaint, Citation, and Initiate Criminal Case).  The new “municipality specific” ordinances will only be available for e-filing with the new versions of the e-filing schemas that will be available with Release 42.   This change is to reject these new ordinances when older versions are used.

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
    • E-Filing (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.

 

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

 

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 e-filing 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.  

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 e-Filing Services:

  • Occasionally technical errors within MNCIS cause an e-file 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 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 e-file service used in a pilot in Dakota County.  This e-file service will be modified to attach documents to a case event in MNCIS.
  • An internal change has been made to improve response times for e-Filing 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.

 

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 e-Filing 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 E-Files 

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.

 

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 e-filing:

  • 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 e-file 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.
  • An internal change was made to the Add Other Person ID e-file 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 e-filed 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. 

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 e-filing.

  • Some additional internal error logging has been added to capture certain errors associated with the Warrant Status Update e-file service. This is for your information only. No action is required on your part.
  • Occasionally technical errors within MNCIS cause an e-file 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.

 

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.

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 e-file 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 e-file 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 e-file 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

  1. 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 (http://www.mncourts.gov/?page=1368


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.

  1. 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.
  2. Issuing Method is required. If this information is missing, the citation will be rejected.
  3. Identification Method is optional, but if it is included, the value must be one of the enumerated values.
  4. Under conditions listed below, citations submitted with a MandatoryAppearanceIndicator set to false will be treated as mandatory. (Does not apply to juvenile citations.)
    1. PropertyDamageText has a value of Endanger
    2. A careless driving charge and AccidentDamageText contains any value except ‘None’.
    3. A charge for Uninsured Vehicle-Driver Violation (statute 169.793.3) and AccidentDamageText contains Fatal or Substantial Bodily Harm.
    4. 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.  (http://www.mncourts.gov/?page=1368).

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.

 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:
    • e-File Citation Supplemental Document
    • e-File Complaint Supplemental Document
    • e-File Case Document
  • An internal change impacting the Citation Supplemental Document e-File 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.

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 e-file 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.

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 e-filing service.  This change does not require any updates to existing message formats, and should be transparent to users of the citation e-filing service.  This update should not require any system downtime to implement, and is available for testing in Development and QA.   

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 e-Filing 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.   

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.  

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 E-File  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 E-File service, are available for testing in Development and QA.  The change to the Other Agency Person Identifier E-File 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.    

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 e-File service.  
  • A modification to the error processing of the Other Agency Person Identifier e-File 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 e-File service to return a fault message if a non-criminal case is specified. 
  • A modification to the Case Detention Status e-File 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 e-File service to updates that failed with certain system errors. 
  • A modification to the case initiating e-File 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.  

 

Release 23 (8/19/2010)

Subject:               Court Integration Services Release 23

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 e-File Interpreter Status service. 
  • An internal update to the e-File Biometric Status service. 
  • Some internal updates to the e-File Criminal Complaint, e-File Tab-Charge, and e-File 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.  

 

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.  

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 E-File 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.    

Release 20 (02/04/2010)

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

  • Update the E-File 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 e-Files 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 e-File 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.    

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 E-File 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 e-File 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.  

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.

o Do not enter additional locations (NOENTADDLO)

o Do not enter or call victim's place of employment (NOENTREMPL)

o Do not enter victim's residence (ENTVICTRES)

o No contact with known gang members (NOCNTGANGM)

o No contact with Vulnerable Adults (NOCONTVUAD)

o 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 e-Files) 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 e-File 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 e-filing complaints.    This version was only used in Carver and St. Louis Counties. 

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.    

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 

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.

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.

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.

  • E-Filing will be updated to automatically retry on two additional technical system rejections. When e-Files 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.
  • E-Filing and Notification messages are being updated to support both soap version 1.1 and soap version 1.2. Currently all notification messages and e-file 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:
    • E-filing 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 e-Filing 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.

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.
  • E-File 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 (http://www.mncourts.gov/is).   They are:

  • The CourtXML Schema page (http://www.mncourts.gov/?page=1368) 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 (http://www.mncourts.gov/?page=3416)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.

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.

o Case Details

o Case Security

o 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:

o AttorneyAddressAdded

o AttorneyAddressModified

o 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.

o E-Files 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 e-File rejection response messages that are caused by system errors.

o 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.

o 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.

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, available at http://www.mncourts.gov/?page=1365#three.   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.

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:

o SubjectParty requests may now include CaseRespondent elements representing parties who are respondents to family court matters.

o 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:

o SubjectParty and FamilyCaseInititation notification messages may now include CaseRespondent elements representing parties who are respondents to family court matters.

o FamilyCaseInititation notification messages will now be published for all Family case types. Prior versions only include case types categorized as "Parent/Child Relationship" cases.

o 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.

o 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:

o A new type named CaseRespondentType has been added to be used by versions 3:3 of the CaseGet and CaseNotification services.

o A new type named FamilyJudgmentType to be used by versions 3:3 of the CaseGet and CaseNotification services.

o 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 e-Filing: A new security check is being added to prevent a submitter from e-Filing 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.

10. 03/27/2008

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

1) 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.

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:

1) 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.

2) The Rejected ReasonText element has been changed to be repeating to allow for a warrant status update message to be rejected for multiple reasons.

3) 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.

9. 03/13/2008

An update will be applied to the E-Filing 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.

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 e-file/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 e-filed. 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.

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.

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 e-File 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 e-Files 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 E-Filing services in preparation for implementing message correlation. Message correlation will allow subsequent e-File 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 e-Filing. 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. 

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.

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:

a. HearingModified: Published at the time the hearing type is changed.

b. 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.

3. 08/27/2007

 1) A change to how the "Filed" case events are added to cases that resulted from e-Filed 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.

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.

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 e-File deadlock rejection response messages as soap faults.

4) Change to e-Filings to add a Citation e-Filed (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.