System Rules Lesson Plan

System Rules Lesson Plan

System Rules Lesson Plan


Objective 1-Be able to Understand Custom Fields in Fireworks

• Department Specific Data Collection Fields
• Are Optional for by Default
• Can be made Required based upon Validation Rules
• Multiple Data Collection Formats
  1.  List
  2.  Numeric
  3.  Text
  4.  Checkbox
  5.  Date
  6.  Date/Time
• For Incidents- Located in Incident Settings in the Admin Backoffice
  1.  Create Topic
    1.  Field (Description/Question)
    2.  Data Collection Type
    3.  2- Part Collection
    4.  Order
    5.  Active (Visible or Not)
    6.  Validation Trigger
    7. • Not Required
      1.  Warning
      2.  Error
    8.  Start Date










Objective 2- Be able to Understand Required Fields in Fireworks

• Required Fields are the fields that have Department specific data collection Requirements
• Can be created as an “Error” or a “Warning”
      • Error- Means something must be filled in for that field to complete the report.
      • Warning- Means someone would like something filled in this field, but it can be ignored to complete report.
• Can be created to operate under certain general triggers
• These are in addition to the standard NFIRS Validation


• Certain Trigger Values
• Fire / EMS
      • Fire, all 100
      • Structure Fire: 111-118, 121
      • Residential: check box

      • Passenger Vehicle
      • EMS, all 300
      • MVC only: 322,323,324
      • MVC w/ injuries: 322, 323




Objective 3- Be able to Understand Validation Rules in Fireworks

• Validation Rules allows for custom additional fields to be validated prior to the incident report becoming “Complete” or “Approved”
• It allows a “Not Required” Custom Field to become “Required” base upon department specific requirements.
•
Warning
*Can cause a conflict if not established correctly against Custom Required Fields.




Validation Rules can also be written on Custom Fields
Warning
*Field must have an “empty” ad Default