What – Numeric and monetary fields were enhanced to support decimal values and thousands separators, ensuring values are displayed using standard currency formatting (for example, $500,000 instead of 500000) across the application UI and printed reports. Monetary fields now consistently display the currency symbol, apply comma separators, and retain formatting in generated PDFs, with validation messaging for large values that exceed supported limits.
Why – This improvement increases data accuracy, readability, and consistency, making financial and numeric information easier to interpret while aligning on-screen values with printed and reported outputs.
How –
Navigate to the relevant investigation or property sections containing numeric or monetary fields.
Enter values using whole numbers or decimals as needed.
The system will automatically format supported monetary fields with $ and comma separators.
Validation messages will appear if entered values exceed allowable limits.
Use Case – A user documenting a large property loss can enter a value such as 500000, and the system will automatically display it as $500,000 on the screen and in the printed report, reducing misinterpretation during review.
What – Updated the printed report layout for Person Involved Statements so statement content is displayed across two rows instead of a single row, separating Date/Time from the statement text to improve readability for long narratives.
Why – Long statements were difficult to review when compressed into a single row, often requiring excessive scrolling or reducing clarity in printed reports.
How –
Open a Fire Investigation record with documented Person Involved Statements.
Use the Print option to generate the report (PDF).
The Statements section will now display Date & Time on the first row and Statement notes on the second row.
Note: Formatting remains consistent even if Date or Time is missing, and statements always render correctly when at least one field contains data.
Use Case – When reviewing a printed report with multiple lengthy witness statements, users can easily read each statement without layout compression, improving clarity during review or sharing.
What – Improved deletion behavior for Not-Started Fire Investigation records so they can be removed from the FI list without impacting associated NFIRS notification data that is still required for other modules.
Why – Previously, Not-Started FI records were difficult to remove and could leave behind visible entries tied to NFIRS notifications, creating confusion and unnecessary cleanup steps.
How –
From the Fire Investigations list, delete a Not-Started FI record.
The FI record and related structure records are removed from the FI database.
Any associated NFIRS notification is automatically hidden from the FI list while remaining intact for other system use.
Note: FI and FD deletion logic remain independent to prevent unintended data impact.
Use Case – A user removes an FI record that was created in error, and it no longer appears in the FI list, while the underlying notification data continues to function as expected elsewhere.
What – Added a warning modal when saving a Fire Investigation record if there is unsaved data in the Persons Involved section, preventing accidental data loss during the save process.
Why – This aligns the save behavior with existing data-loss prevention checks and ensures users are clearly alerted before unsaved personnel information is discarded.
How –
Enter or modify data in the Persons Involved section without saving it.
Click Save on the main Fire Investigation record.
A warning modal appears with options to Save Personnel First, Continue Without Saving, or Cancel.
Note: The Save Person button is now a primary action to emphasize proper data saving.
Use Case – A user updating an investigation attempts to save the record while personnel edits are still pending and is prompted to save or confirm before any data is lost.
What – The Weather Information section now retrieves historical weather data based on the incident’s actual date, time, and location, rather than current conditions at the time of data entry.
Why – Accurate historical weather context is critical for investigations and reporting, ensuring environmental conditions match the time of the incident.
How –
Enter a valid Investigation Date/Time and incident location.
Navigate to Weather Information.
The system retrieves and displays historical weather conditions for that specific date and time.
Note: If the incident date/time is missing or set in the future, weather data retrieval is blocked with a clear message.
Use Case – An investigator reviewing a past incident can rely on historically accurate weather conditions in the report instead of current-day weather.
What – Updated the Fire Investigation CAD Number logic so it pulls from the correct NFIRS notification fields, ensuring accurate incident number mapping throughout the investigation lifecycle.
Why – This ensures consistent and reliable integration between CAD, FD, and FI records, reducing discrepancies in incident identification.
How –
When a Fire Investigation record is created, the system automatically pulls the Investigation Number from the appropriate NFIRS field.
CAD feed refreshes keep the number up to date as the record progresses.
Note: Users can still manually update the Investigation Number if necessary.
Use Case – An FI record consistently displays the correct CAD Incident Number before and after the associated FD record is started, avoiding manual reconciliation.
What – Investigator Qualifications now support multi-select, allowing multiple qualifications to be recorded for each investigator instead of a single selection.
Why – Investigators often hold multiple certifications, and capturing all qualifications improves accuracy and completeness of investigation records and reports.
How –
Navigate to the Investigator Qualifications section.
Select one or more qualifications from the multi-select dropdown.
Use the search option to quickly find specific qualifications.
Note: Printed reports now display all selected qualifications for each investigator.
Use Case – A primary investigator with multiple certifications can have all relevant qualifications documented and reflected in the final investigation report.