In order to provide you with more detailed information on our updates we have broken the Release Notes down by module. 

---

New Features

1. What:  This feature enables users to create default and error workflows for the Operation, People Involved, and Investigation (Arson and Suspect) sections within an incident report.
   
2. Why:  This allows you to define and apply their own business rules in real time.
   
1. Default Workflow Implementation: Default values are automatically set when predefined conditions are met across the Operation, People Involved, and Investigation (Arson and Suspect) sections.
   
2. Error Workflow Implementation: Validation messages are triggered when error conditions occur within the same sections of and incident report, ensuring proper feedback to users.
   
3. How:  
   
1. Define default or error workflow on Fire Incident Setup/Workflows for specific field within Operation, People Involved, and Investigation (Arson and Suspect) sections. 
   
2. Users input data into fields within Operation, People Involved, and Investigation (Arson and Suspect) sections. If a predefined condition is met, the field automatically populates with a default value in case of default workflow but if it is and error workflow the field should be highlighted and an error message related is shown on the form. The error message provides guidance on how to correct the input.
   
3. As long as Error Workflow exist, the report won't be completed.
   

1. What:  This feature allows you to create hidden workflows for fields in an incident report that are not required by the NFIRS standard.
   
2. Why:  This allows you to define and apply your own business rules in real time.
   
3. How:  
   
1. Define the hidden workflow based on the specific rules of the fire incident in Fire Incident Setup/Workflows for a specific field within the incident report. (Fields that may be required by NFIRS cannot be hidden.)
   
2. As soon as the condition for hiding the field is met, it is hidden. At this point, if the field has errors due to WF, it is cleared so that the object and section are not affected. The hide workflow takes precedence over the error and default workflows.
   

1. What:  This feature allows users to create 2nd level conditions inside workflows for fields in an incident report.
2. Why:  This allows you to define and apply your own business rules in real time.
3. How:  
   
1. Define the any workflow (hide, default, error) based on the specific rules of the fire incident in Fire Incident Setup/Workflows for a specific field within the incident report.
   
2. Define multiple conditions, grouping them using different operators. Ensure at least two or more rules exist between groups. Save and test to confirm conditions trigger expected.
   

---

Enhancements

1. What:  The ability to move custom questions to a new section or sub-section while preserving data after moving the field to a new location.
   
2. Why:  This enhances the configurability of custom questions within Incident Reports, allowing you to move them within predefined sections.
3. How:  Navigate to the Field Management within the Fire Incident Setup and select a Custom Question to manage, now choose a new location from the section dropdown then select save. 
   

​

1. What:  The ability to access/edit the apparatus details from the Fire Incident List when the report is in the Not Started status.
   
2. Why:  Allows you to complete your apparatus information without having to wait for the report to be started.
   
3. How:  From the Fire Incident list now the apparatus icon will be enabled when a report is in the Not Started status, by selecting on the icon will bring you to the apparatus details modal to begin your documentation.
   

​

1. What:  This feature enhances the CREWSENSE integration by implementing an improved method for assigning the Officer in Charge (OIC) based on firefighter rank.
2. Why:  Instead of defaulting to the first arriving unit, this new logic prioritizes the highest-ranked available firefighter within the responding units.
3. How:
   

1. Rank Setup:

   • Admins assign numerical values to ranks under Agency Setup > Rank List.

2. Enable the Setting:

   • Navigate to NFIRS Setup.

   • Locate the setting: "Enable OIC based on Personnel Rank."

   • If enabled, First Arriving OIC is disabled automatically.

3. Incident Processing:

   • System identifies all personnel in responding units.

   • Filters out personnel from EMS units if "Exclude EMS from OIC Logic" is enabled.

   • Selects the firefighter with the highest priority rank (lowest numerical value).

   • If multiple personnel share the same priority, the system selects one randomly.

4. OIC Assignment and Display:

   • The assigned OIC is displayed for "Not Started" records.

   • OIC is sortable within the records list.
     

4.  Documenting the same apparatus multiple times.

1. What:  This feature introduces the ability to document the same apparatus multiple times as long as the times do not overlap.
2. Why:  There are cases where a unit is called to assist on an incident and then later recalled to the same scene. This limitation prevents accurate documentation of such occurrences.
3. How:  
   

1. Navigate to Fire Incident Setup → Response → Resources.

2. Enable Allow Documentation of Apparatus Multiple Times.

   • This will automatically enable and disable the Apparatus Assignment Override setting.

3. When adding a second instance of an apparatus:

   • Ensure times do not overlap.

   • Ensure times are within the incident timeframe.

4. The apparatus selection form will display instances as [Apparatus Name] / [Dispatch DateTime].

5. When exporting data (CAD, Payroll Summary):

   • Only the first instance of the apparatus will be included in CAD downloads.

   • Payroll summary should handle personnel correctly even if an individual appears on multiple instances of the same apparatus.