What - Added a Field Management tab under Settings for the Daily Log, including a Required Field Management area that allows admins to designate which Daily Log fields are required for submission.
Why - This enhancement gives admins more control over Daily Log data entry by helping ensure important event details are captured before a log can be submitted.
How
Navigate to Settings → Field Management → Required Field Management.
Locate the Daily Log section.
Select the Daily Log fields to mark as required from the dropdown.
Click Save to apply the configuration.
Required fields will display with an asterisk (*) in the Daily Log entry form.
Start Date + Time is always required by default and is not included in the dropdown.
End Date + Time is not required by default but can be selected as a required field.
Supported required fields include Event Type, End Date + Time, Activity Type, Apparatus, Fire Station, Shifts, Users, and Description.
Use Case - An administrator wants to ensure all Daily Log entries include key operational details, such as Event Type, Activity Type, and Apparatus. They can configure those fields as required in Settings → Field Management → Required Field Management, and users will see an asterisk (*) next to those fields when completing Daily Log entries.
Bug Fixes
Events - Required Checklist Items Blocking Event Save
What - Resolved an issue where events with checklists containing required fields could not be saved or updated with participants unless the checklist was fully completed upfront. Required checklist field validation now only occurs when marking an event as Completed.
Why - This fix allows users to create and manage events before checklist items are completed, while still ensuring required checklist information is captured before the event is finalized.
How
Create an event and attach a checklist with required fields.
Add participants and click Save.
Checklist completion is not required when saving the event or adding participants.
Required field validation will only trigger when attempting to mark the event as Completed.
Use Case - A user creates an event that includes a required checklist but needs to add participants before all checklist details are available. They can now save the event and manage participants without completing the checklist first, and required checklist fields will be enforced when the event is marked as Completed.