RMS Product Release Notes
2025 Second Release
The information in this document is provided for planning purposes only. The software described in this document is furnished under a license agreement or non-disclosure agreement. Executive Information Services reserves the right to change specifications without notice.
US GOVERNMENT RESTRICTED RIGHTS: Use, duplication or disclosure by the United States Government is subject to restrictions as set forth under DFARS 252.227-7013 or in FARS 52.227-19 Commercial Computer Software - Restricted Rights.
Correspondence regarding this publication should be directed to:
Executive Information Services1396 NE 20th Avenue, Suite 100Ocala, FL 34470support@goeis.net(208) 580-0400
Contents
Summary PAGEREF _Toc192055770 \h 4
Document Convention PAGEREF _Toc192055771 \h 4
Deployment PAGEREF _Toc192055772 \h 4
RMS Release Notes PAGEREF _Toc192055773 \h 5
RMS Entry PAGEREF _Toc192055774 \h 5
Seal Indicator PAGEREF _Toc192055775 \h 5
Seal Indicator Header PAGEREF _Toc192055776 \h 5
Accident Approval PAGEREF _Toc192055777 \h 6
Accident Approval Access PAGEREF _Toc192055778 \h 6
Warrant Module PAGEREF _Toc192055779 \h 6
Import Templates PAGEREF _Toc192055780 \h 6
AM Message Prefill PAGEREF _Toc192055781 \h 8
Media PAGEREF _Toc192055782 \h 10
Security Object PAGEREF _Toc192055783 \h 10
MCR PAGEREF _Toc192055784 \h 10
MCR ID Type PAGEREF _Toc192055785 \h 10
MCR Address Update PAGEREF _Toc192055786 \h 11
CFS Detail PAGEREF _Toc192055787 \h 11
Printing Error PAGEREF _Toc192055788 \h 11
Arrest Screen PAGEREF _Toc192055789 \h 12
Case Offenses PAGEREF _Toc192055790 \h 12
Trespass Module PAGEREF _Toc192055791 \h 12
Write Level PAGEREF _Toc192055792 \h 12
Citation Module PAGEREF _Toc192055793 \h 12
Write Level PAGEREF _Toc192055794 \h 12
Protection Order Module PAGEREF _Toc192055795 \h 12
Adding Alias PAGEREF _Toc192055796 \h 12
RMS Query PAGEREF _Toc192055797 \h 13
Search Supplement Purpose Codes PAGEREF _Toc192055798 \h 13
Search Supplement-Specific UDF Fields PAGEREF _Toc192055799 \h 13
User Groups PAGEREF _Toc192055800 \h 14
CFS Detail PAGEREF _Toc192055801 \h 15
Phone Number Cut-Off PAGEREF _Toc192055802 \h 15
California IBR PAGEREF _Toc192055803 \h 15
Multi-Agency Support for XML Submissions PAGEREF _Toc192055804 \h 15
XML Submission Upload Progress Report PAGEREF _Toc192055805 \h 16
DELETE Incidents from Repository PAGEREF _Toc192055806 \h 17
Upload Fails PAGEREF _Toc192055807 \h 17
Combining Drugs Within the Same Weight Class PAGEREF _Toc192055808 \h 17
Clearance Date PAGEREF _Toc192055809 \h 18
Property Segment PAGEREF _Toc192055810 \h 18
Drug; Loss Type PAGEREF _Toc192055811 \h 18
Base Case Error PAGEREF _Toc192055812 \h 18
LEOKA ORI PAGEREF _Toc192055813 \h 18
2024 Was Added to the Dropdown for Zero, And DV PAGEREF _Toc192055814 \h 18
Florida IBR PAGEREF _Toc192055815 \h 18
Data Collection PAGEREF _Toc192055816 \h 18
Upload Unfounded Cases PAGEREF _Toc192055817 \h 19
Group B Arrests PAGEREF _Toc192055818 \h 19
Added 2024 to the Year Dropdown PAGEREF _Toc192055819 \h 19
Victim/Offender Relationships PAGEREF _Toc192055820 \h 19
Idaho IBR PAGEREF _Toc192055821 \h 19
Added 2024 PAGEREF _Toc192055822 \h 19
Louisiana IBR PAGEREF _Toc192055823 \h 19
Renumber Property Entry Numbers PAGEREF _Toc192055824 \h 19
Society Victims PAGEREF _Toc192055825 \h 19
Added 2024 PAGEREF _Toc192055826 \h 20
South Carolina IBR PAGEREF _Toc192055827 \h 20
Collecting Prior Reports PAGEREF _Toc192055828 \h 20
Added 2024 to the year dropdown PAGEREF _Toc192055829 \h 20
Victim Involvement PAGEREF _Toc192055830 \h 20
Texas IBR PAGEREF _Toc192055831 \h 20
Texas-Specific Segment PAGEREF _Toc192055832 \h 20
Delete Segments PAGEREF _Toc192055833 \h 20
Relationship Issues PAGEREF _Toc192055834 \h 20
2024 Added to Dropdown PAGEREF _Toc192055835 \h 21
Virginia IBR PAGEREF _Toc192055836 \h 21
Single Flat File PAGEREF _Toc192055837 \h 21
New Values to Tables PAGEREF _Toc192055838 \h 22
Values to Tables PAGEREF _Toc192055839 \h 22
Validation Rules PAGEREF _Toc192055840 \h 22
Drug with Loss type 1 PAGEREF _Toc192055841 \h 22
Offender Sequence Number PAGEREF _Toc192055842 \h 22
Victim/Offender PAGEREF _Toc192055843 \h 22
Unknown Offender PAGEREF _Toc192055844 \h 22
Offender Relationships PAGEREF _Toc192055845 \h 23
LEOKA Victim Offender/Arrestee Relationships PAGEREF _Toc192055846 \h 23
Group B Arrests PAGEREF _Toc192055847 \h 23
Washington IBR PAGEREF _Toc192055848 \h 23
Report Incident Based on IBR Offense PAGEREF _Toc192055849 \h 23
Added 2024 to Dropdown PAGEREF _Toc192055850 \h 23
Renumber Offenders PAGEREF _Toc192055851 \h 23
RMS Manager PAGEREF _Toc192055852 \h 24
Restore Narrative PAGEREF _Toc192055853 \h 24
Change Case Number PAGEREF _Toc192055854 \h 25
AAC Manager PAGEREF _Toc192055855 \h 26
Wild Card PAGEREF _Toc192055856 \h 26
State Interface PAGEREF _Toc192055857 \h 26
MV Mask PAGEREF _Toc192055858 \h 26
SLEDS EW and EM PAGEREF _Toc192055859 \h 26
MIS Service PAGEREF _Toc192055860 \h 26
Allow MNI Match with no Middle PAGEREF _Toc192055861 \h 26
Summary
This document provides an overview of the impactful changes to EIS Public Safety Software products in the highly anticipated second edition release for 2024. This comprehensive update includes all EIS products, such as RMS, JMS, and CAD, emphasizing the significant enhancements made to the RMS product.
Each release is designed to address corrections and introduce powerful enhancements that elevate the functionality and efficiency of our systems. This document meticulously categorizes the key products and modules, offering an in-depth exploration of their features and capabilities.
Given the highly configurable nature of EIS systems, please be aware that your agency's actual interface and functionality may vary slightly from the descriptions provided. Embrace these advancements to enhance your agency's performance and service delivery.
Document Convention
We have included a quick visual indicator to describe each item as either a product feature enhancement or a fix to an existing element. Items are not presented in any specific order within the document.
The NEW Icon indicates a new feature added to the application.
The UPDATE Icon indicates an update to a feature or function currently deployed.
The FIX-IT icon indicates a correction or a modification to an existing deployed function.
Deployment
EIS is committed to delivering updates twice yearly, ensuring our services meet your needs continuously. The timing of these deployments is strategically determined based on contractual obligations, the specific modules being deployed, agency discretion, and any unique challenges or requirements your agency may face.
To make the process even more convenient, EIS now offers a self-scheduling option. To take control of your update schedule, visit EISServicePackUpdates and follow the easy prompts.
Should you have any questions or wish to discuss the deployment process further, please don’t hesitate to contact your account manager or EIS Customer Support at 208-580-0400. We're here to support you every step of the way!
RMS Release Notes
The following changes are incorporated in the January 2025 RMS Law Management Service pack, which includes 2024 hotfixes. For this update, you will need .NET framework 4.6.2 or higher.
RMS Entry
Seal Indicator
ADDED
Seal Indicator Header
When a name record or case narrative is sealed, a prominent indicator label will be featured in the header, effectively notifying users of the sealed document’s presence. This innovative feature significantly enhances transparency and security across essential modules, including Incident, Citation, Warrant, Protection Order, and Field Interview (FI). Furthermore, this feature is fully configurable, empowering users to decide whether to display it or not. For further information and assistance, we encourage you to contact support.
When a case is both restricted and sealed, you will find the sealed indicator prominently displayed below the restricted indicator, ensuring clarity and enhancing your understanding of the case status.
The query search result grid for each module will now feature a dedicated column that clearly indicates when a name or the incident narrative has been sealed. This enhancement not only improves transparency but also ensures that critical information is easily identifiable, reinforcing our commitment to effective data management.
This indicator is designated for each supplement individually, emphasizing its importance. If the base case features a sealed name record or narrative, only that base case will reflect the indicator. However, if a name is added to a supplement and subsequently sealed, the original supplement, along with any other supplements that include the existing record, will also prominently display the sealed indicator. This ensures clarity and consistency across all related documents.
Accident Approval
ADDED
Accident Approval Access
If a user possesses ACCIDENT APPROVAL access in Security Manager and has Add/Edit privileges, they can confidently enter and modify the Approved Date and PIN directly on the main Accident screen, enhancing efficiency and accuracy in managing accident approvals.
Warrant Module
ADDED
Import Templates
THIS IS AN OPTIONAL MODULE. PLEASE CONTACT SALES FOR MORE INFORMATION
EIS is excited to introduce a powerful new feature that enables users to effortlessly populate the miscellaneous data field within the warrant’s module using standardized text templates. We are implementing a streamlined template import function on the warrants screen, offering an intuitive user interface that grants easy access to a diverse array of text template options designed specifically for the warrants module. These templates will be expertly managed within the established RMS Management tool, ensuring efficiency and consistency in your operations. Embrace this opportunity to enhance your workflow and improve data accuracy!
When a template is imported into the Comments field on the Warrant screen, it’s important to note that any special formatting—such as font color and size—will be lost, as this field only supports plain text. To ensure seamless integration, the Comments field from the Warrants face page will automatically transfer into the MIS – Miscellaneous text field on the EW – Entry Warrants mask. This transfer occurs when you select the appropriate option from the ORLEDS Menu on the Subject Screen. Embracing this process will enhance clarity and maintain consistency in your documentation.
ADDED
AM Message Prefill
THIS IS AN OPTIONAL MODULE. PLEASE CONTACT SALES FOR MORE INFORMATION
EIS has developed a customized data function designed to generate a formatted collection of text data from the displayed warrant record. This compilation will be represented as a single text string and displayed in the message window. This function aims to share the details of the warrant with an external agency using the ORLEDS AM messaging communication method. This innovation enhances the flow of information and strengthens collaboration with external partners.
The Warrants Entry screen will feature an AM button to create the AM mask for entry and submission.
When the button is selected for the existing
warrant on the screen that the AM Mask will be
displayed with the following data items
automatically populated.
The mapping of the data is as follows:
Media
ADDED
Security Object
RMS has a new feature to improve security and make it easier for users. Media will not appear in the tree view or the right-click menu for users without access permissions. You can choose to turn this feature on or off. For more details, please get in touch with support.
MCR
CORRECTED
MCR ID Type
Resolved an issue on the MCR page that prevented proper validation of ID entry fields during the save process. This fix enhances data accuracy and ensures a smoother user experience.
CORRECTED
MCR Address Update
We have implemented a powerful configuration to update the most current home address in the MCR Module. When this configuration is activated, it ensures that the most recently entered address in the Address History screen is automatically set as the MNI Home address. Additionally, the Current/Home checkbox will intuitively change the address type indicator to "HOME." This streamlined process means that once you save your changes, the updated location will be sent to MNI as the official address associated with the name, ensuring accuracy and efficiency in data management.
CFS Detail
CORRECTED
Printing Error
The printing error in the CFS Detail Report has been successfully resolved, ensuring accuracy and reliability in our documentation.
Arrest Screen
UPDATED
Case Offenses
RMS enhanced the arrest charges screen to automatically import all offense data rather than just the offense description and level. This improvement significantly reduces redundancy and streamlines the process, saving valuable time and effort by eliminating the need for repetitive manual data entry. This change will boost efficiency and enhance overall accuracy in record keeping.
Trespass Module
CORRECTED
Write Level
The Trespass module properly utilizes the write level, ensuring only authorized users can edit. This enhancement improves security and standardizes access protocols across all modules, resulting in a more seamless and reliable user experience.
Citation Module
CORRECTED
Write Level
The Citation module properly utilizes the write level, ensuring only authorized users can edit. This enhancement improves security and standardizes access protocols across all modules, resulting in a more seamless and reliable user experience.
Protection Order Module
CORRECTED
Adding Alias
An important enhancement has been made in the Protection Order module. Now, when importing a name using MNI, if the name has existing aliases, the AKA tree node will be added as soon as the user saves the name, eliminating the wait and ensuring a smoother experience.
RMS Query
ADDED
Search Supplement Purpose Codes
The Incident Query form in RMS Query has been enhanced to include the ability to search by supplement purpose directly on the Details search screen. A new Purpose column has been integrated into the search results grid, providing clear visibility into the supplement purpose. This improvement streamlines your search process and ensures you can access relevant information more efficiently.
ADDED
Search Supplement-Specific UDF Fields
The Incident Query form in RMS Query now features an enhanced section for searching specifically tailored User Defined Fields (UDFs) within the Details search screen. When Incident Supplements are equipped with their unique set of UDF fields, a dedicated section will become available, empowering users to search using these specialized fields effortlessly. This improvement simplifies the query process and ensures more precise and relevant results, significantly enhancing your user experience.
ADDED
User Groups
If you've integrated User Groups into your crime codes within RMS Manager's Crime Code Maintenance, you can now leverage this enhancement in RMS Query. Experience the power of our newly added User Group search option in the Incident Detail search, which will make your investigations more efficient and tailored to your needs.
Add User Group search to Incident Detail search.
RMS Manager, the 3 fields can be configured as you see in the screenshot below in Crime Code Maintenance.
CFS Detail
CORRECTED
Phone Number Cut-Off
EIS successfully addressed the issue on the CFS Detail screen, which was cutting off the phone number. Extending the field by three characters ensures that all contact information is obvious and accessible, enhancing user experience and communication efficiency.
California IBR
The following items comprise user interface additions and corrections within the RMS, specific to the California IBR Confirmation.
ADDED
Multi-Agency Support for XML Submissions
We have enhanced our system to support multi-agency credentials, ensuring a seamless submission process. When uploading incidents, domestic violence reports, or zero reports, credentials are efficiently retrieved from the database based on the specified agency in the submission windows. This improvement streamlines operations and fosters collaboration across agencies for more effective reporting and response. Contact Customer Support for more information.
ADDED
XML Submission Upload Progress Report
EIS is excited to announce the addition of a new report that provides immediate feedback on your XML Submission upload status as soon as the process is complete. This enhancement ensures that you stay informed and confident about your submission, making your experience smoother and more efficient.
This report compellingly showcases the instances of upload attempts, promptly notifying users of their progress and ensuring they remain informed at every step of the process. NOTE: The UPLOAD STATUS only indicates that the web service received the incident, not whether or not it was validated correctly.
The new reports will be added as a row where the submission_type is UPLOAD. The latest reports will be shown in the Submission History form with a Run Type of UPLOAD:
The report can then be displayed by selecting the row and clicking Case List at the bottom. This report will only be contained in uploads attempted after this release.
ADDED
DELETE Incidents from Repository
RMS has a new feature that allows users to delete selected reports from the repository efficiently. With the ability to enter a specified list of reports, you can confidently take charge of your data management. Rest assured, only reports associated with the selected agency will be removed, guaranteeing accuracy and security in the process. This tool seamlessly handles deletions for reports uploaded in XML and flat file formats, making it a robust and user-friendly solution. Take decisive control of your repository today!
This screen is accessed via the Utility dropdown menu.
CORRECTED
Upload Fails
We have resolved an error that hindered uploads, guaranteeing a smooth and dependable user experience moving forward.
CORRECTED
Combining Drugs Within the Same Weight Class
The writer will correctly combine drugs that belong to the same weight class.
CORRECTED
Clearance Date
The issue concerning the blank clearance date when entering "N" has been successfully resolved, ensuring a smoother and more efficient experience moving forward.
CORRECTED
Property Segment
Fixed the following issue related to recovered property:
Resolved an issue that hindered the submission process from accurately marking future recovered items as reported.
Resolved an issue where the writer incorrectly overwrote the recovery date for existing items, ensuring accurate recovery timelines for future items.
Resolved an issue where the writer miscalculated recovered values when combining items of the same type, enhancing accuracy and reliability.
CORRECTED
Drug; Loss Type
The writer no longer produces a ‘none’ substance element for a drug, ensuring data accuracy.
CORRECTED
Base Case Error
Successfully addressed and resolved the base case errors, ensuring a robust and reliable outcome.
CORRECTED
LEOKA ORI
When documenting a LEOKA victim, the entry will be excluded if the LEOKA agency's ORI is identical to the reporting agencies. This update enhances the functionality of the XML and flat file writers, ensuring more accurate and efficient reporting.
CORRECTED
2024 Was Added to the Dropdown for Zero, And DV
2024 has been added to the Zero and DV Reporting dropdown menu.
Florida IBR
The following items comprise user interface corrections within the RMS, specific to the Florida IBR Confirmation.
CORRECTED
Data Collection
Improved report collection and validation, enhancing reliability.
CORRECTED
Upload Unfounded Cases
Resolved an issue preventing the deletion of uploaded unfounded cases, enhancing process efficiency.
CORRECTED
Group B Arrests
If a report includes arrests, the submission application automatically removes any prior Group B arrests before uploading the new report to ensure accurate records.
CORRECTED
Added 2024 to the Year Dropdown
Added 2024 to year dropdowns
CORRECTED
Victim/Offender Relationships
Resolved an issue that prevented recording victim and subject relationships for 64A and 64B offenses.
Idaho IBR
The following items comprise user interface corrections within the RMS specific to the Idaho IBR Confirmation.
CORRECTED
Added 2024
Added 2024 to the year dropdowns
Louisiana IBR
The following items are comprised of user interface corrections included within the RMS, specific to the Louisiana IBR Confirmation
CORRECTED
Renumber Property Entry Numbers
The writer will implement a renumbering system for property RMS entry numbers to enhance clarity and eliminate potential confusion. This proactive approach will prevent duplicate sequence numbers in cases involving vehicles and standard property items.
CORRECTED
Society Victims
Newly created society victims are recorded correctly, ensuring that every case is now documented correctly and effectively.
CORRECTED
Added 2024
Added 2024 to the year dropdowns.
South Carolina IBR
The following items comprise user interface corrections within the RMS, specific to the South Carolina IBR Confirmation.
CORRECTED
Collecting Prior Reports
When collecting prior reports, the application will now check the `ibr_start_date` for each agency. If a valid date is found, it will collect cases with an `ibr_status` of "U" (update) dating back to that date. If the date is invalid, the application will revert to its standard operation, which only gathers cases from the past year. Cases with an `ibr_status` of "N" or blank will remain limited to a one-year retrieval period. This enhancement will streamline our reporting process and improve data collection efficiency.
CORRECTED
Added 2024 to the year dropdown
Added 2024 to year dropdowns.
CORRECTED
Victim Involvement
A warning dialog box will appear when changing a name linked to VICTIM involvement to a different, unmapped involvement. This dialog box states that the change may interfere with current IBR validations; however, the screen will save the changes.
Texas IBR
The following items comprise user interface corrections within the RMS, specific to the Texas IBR Confirmation.
CORRECTED
Texas-Specific Segment
The Texas-specific segment now includes the necessary padding of blank spaces for optimal formatting.
CORRECTED
Delete Segments
The deleted segments are being recorded correctly for Group B reports.
CORRECTED
Relationship Issues
The relationships between offenders and victims for offense code 120 are being accurately recorded.
CORRECTED
2024 Added to Dropdown
Added 2024 to year dropdowns
Virginia IBR
The following items comprise user interface additions and corrections within the RMS, specific to the Virginia IBR Confirmation.
ADDED
Single Flat File
We have implemented a new feature that enables users to create a submission file for specific reports. Access this option under the "Single Flat File" section within the UTILITY dropdown at the application's top. This feature is specifically designed to submit reports that cannot be submitted through regular channels due to their significant deviation from the standard IBR date range. Use it accordingly.
The output file name contains the agency ORI, the report number and the reporting month/year defaulted to the current month/year. Example file name: FL013042VAERIC9.24J
ADDED
New Values to Tables
Added fentanyl drug type to DRUG-TYPE
Added gunshot wound to IBR-INJURY.
Added new relationship codes XR, FP, FC, and CO.
UPDATED
Values to Tables
Renamed Anti-Mormon to Anti-Church of Jesus Christ. The code is still 28.
Removed validation related to rule 560, which states that at least 1 offender must be of a different sex for an 11A offense.
UPDATED
Validation Rules
Subject/victim relationships are now optional for crimes against property, except for 120, which still requires it. Reworded the relevant error codes and removed error 459.
Removed the following offense codes which are no longer reportable: 90A, 90E, 90H
CORRECTION
Drug with Loss type 1
Resolved the issue that hindered the accurate recording of drug items with a loss type 1.
CORRECTION
Offender Sequence Number
The offender's sequence number has been renumbered to ensure all sequence numbers remain within the two-digit limit.
CORRECTION
Victim/Offender
The writer will not include victim/offender relationships unless the offender involvement type is accurately mapped to OFFENDER.
CORRECTED
Unknown Offender
When documenting a victim segment for an unknown offender, you must use 00 as the first offender number in the related data element.
Resolved the issue of unnecessary blank spaces in the victim segment when documenting unknown offender relationships, ensuring clearer reports.
Effectively resolved an issue that prevented the writer from accurately noting the unknown offender's relationship to the victim, enhancing the reliability of future reports.
CORRECTED
Offender Relationships
Relationships are no longer omitted for all offenders and are being recorded correctly.
CORRECTED
LEOKA Victim Offender/Arrestee Relationships
Renumbering the sequence numbers of offenders in the LEOKA victim-offender/arrestee relationship section is now functioning correctly.
For VA-specific LEOKA/offender relations, the writer will always use "O" instead of "A" to accurately match the offender number.
CORRECTED
Group B Arrests
In incident reports with arrests, the writer will remove segments related to any previously uploaded Group B arrests when adding a Group A offense to ensure clarity and accuracy.
Washington IBR
The following items are comprised of user interface additions and corrections included within the RMS, specific to the Washington IBR Confirmation
ADDED
Report Incident Based on IBR Offense
EIS is excited to introduce a configuration that allows users to customize IBR data collection. Instead of relying solely on Case Type, you can now report IBR data based on reportable IBR offenses. This improvement enhances reporting accuracy and supports better decision-making. For assistance implementing this feature, please contact our customer support at 208-580-0400. Unlock the potential of your data today!
CORRECTED
Added 2024 to Dropdown
Added 2024 to the Year dropdowns.
CORRECTED
Renumber Offenders
The submission application will renumber offenders in the victim/offender relationship section.
RMS Manager
ADDED
Restore Narrative
Sometimes, users may inadvertently delete a case report with an important narrative. RMS is proud to introduce a powerful new feature to enhance our service and safeguard your valuable information. With the restore narrative option in RMS Manager, you can easily retrieve and reinstate previously saved narratives. This ensures that your critical data is never permanently lost and provides peace of mind as you manage your case reports.
Users must add a security object to their login to enable the Report Narrative module on the menu. ‘CASENARRATIVEREPLACE’ in Security Management.
Unlock the full potential of your saved narrative by following these clear and compelling step-by-step instructions for restoration.
Open RMS Manager
Click on Restore Narrative
Close out RMS Entry
Enter the Current Case/Report Number “Tab”
If there is a Supplement Report Number, “Tab” Again.
At this point you will see an audit log. Update indicates every time the narrative was saved. Delete indicates when the report was deleted.
Double-click each line item to decide which narrative to restore to the report. NOTE: The incident report must have been recreated and saved before you try to restore the narrative.
Replace Narrative into the report.
CORRECTION
Change Case Number
The numbering of the new supplement names does not overlap and appears in the correct sequential order.
AAC Manager
ADDED
Wild Card
Add Wild Card Search to Personnel, Login, First Name, and Last Name
State Interface
ADDED
MV Mask
MV Mask—Add an additional OCA to the MANDATORY section and the NIC and additional LIC and VIN to the Record Identifiers section. The data will populate the OCA, LIC, and VIN sections instead of the Vehicle Information sections.
Correction
SLEDS EW and EM
Improved the output formatting for the SLEDS EW and EM outbound messages for clearer communication.
MIS Service
ADDED
Allow MNI Match with no Middle
We have implemented a powerful new app configuration that enhances our matching capabilities by allowing matching options based solely on First Name, Last Name, and Date of Birth. This strategic adjustment ensures that if these three critical elements align, the system will still recognize it as a valid match even when the Middle Name is missing from one or both records. This improvement is designed to prevent the unnecessary creation of multiple MNI records when only the name and date of birth correspond. Importantly, if a Middle Name is present in both records, it must match strictly for the records to be considered a true match. This streamlining not only increases efficiency but also enhances the accuracy of our data management. Contact Support for Configuration.
Source: RMS Release Notes 2025.docx