Product Enhancements
New Case Fields for Complaint, Preliminary and Investigation
# ID - 1567566
Eight new optional fields are now available across the Complaint, Preliminary, and Investigation applications, allowing you to capture additional case information in structured fields instead of the Chron Log or Action History. The Main tab in all three applications includes Investigation Involving and Primary Relationship with City.
The Complaint Close tab includes a Declined Reason.
The Assistance tab includes Created Date, District of Occurrence, and Created By on the Consensual Monitoring form, and Investigator Badge Number and Sequence Number on the Assistance Request form.
All eight fields are hidden by default and can be enabled through Show/Hide Field Configuration for the applicable application and tab.
Inbound Hotline Email Retained as an Outlook .msg File
#ID 1576970
The Email Hotline Case Fetch job request now attaches the original inbound email to the Complaint Case as an Outlook .msg file instead of generating a .txt summary of the message. The .msg preserves the complete email record, subject, body, sender, recipients, headers, received date and time, HTML formatting, and inline or embedded images, so the message is retained as evidence exactly as it was received. Users can display the .msg on the Attachments tab of the Complaint Case and can download it and view it directly in Microsoft Outlook with no conversion step.
Move Investigation Email Reader Configuration from Connectors to Case Type
#ID 1576968
Email Reader settings for the Complaint case type are now managed directly within the case type configuration instead of as a separate connector record. The default Email Reader entry has been removed from Connectors, Investigation App and then Complaint, and no default connector record is created for new or existing case types. Folder Owner and Initiating Office have also moved from Investigation Configuration to the Email Reader settings, maintaining their existing lookup values, validation, and required or optional behavior. The Email Reader setting is available only for the Complaint case type.
The Email Reader displays your saved configuration, including connection details, folders, field mapping, Folder Owner, Initiating Office, and enabled state. Saved values are retained when you reopen the page.
Existing Email Reader configurations are migrated automatically during upgrade without administrator intervention or interruption to email intake. Field mappings are preserved exactly as configured, and inbound emails continue to create Complaint cases as before.
Email Attachments Nested Beneath the .msg File
# ID 1608925
Files that arrive with an intake email are now stored as child attachments beneath that email's .msg file on the Attachments tab, each keeping its original file name, extension, and native format.
Attachments excluded by the case type's file type configuration, attachments that exceed the configured maximum attachment size, and attachments that cannot be extracted are skipped and recorded in the Job Log, and the remaining files are still attached to the .msg.
Bug Fixes
We’ve made the following security updates in this version of eCase Investigations:
ID | Description |
1606730 | Attachments with special characters in the file name (such as + or #) were not carried over when converting a Complaint case to an Investigation case. eCase now accepts every character that is valid in a Windows file name, so all attachments are copied correctly. |
1631982 | Fixed an issue on the Index (contact) forms where characters typed into the First Name field immediately after leaving Last Name could be dropped or reordered. Name fields now accept typed input reliably, with no change to existing validation or mandatory-field behaviour. |