Creating a Hide Workflow within NERIS

Creating a Hide Workflow within NERIS

Purpose Statement

  1. The purpose of this article is to demonstrate how to create a Hide Workflow for fire reports. This workflow enables agencies to streamline fire documentation by automatically hiding certain fields based on predefined conditions. This increases documentation efficiency and ensures users only see relevant information.

Background Information

What is a Hide Workflow?
  1. A Hide Workflow allows users to hide specific fields or sections within the documentation process when certain conditions are met. This is configured within the Incident Documentation module in First Due.

Why use a Hide Workflow?
  1. Using a Hide Workflow helps:
    • Minimize visual clutter by displaying only relevant fields.
    • Ensure compliance with agency-specific documentation preferences.
    • Improve user efficiency and reduce data entry errors.

Use Case Example:

  1. If your agency does not require the “Response Zone” field for incidents categorized as "No Emergency - Cancelled," a Hide Workflow can automatically hide that field when that incident type is selected.

Video


Step-by-Step Guide


1. Navigate to Fire Incident Setup
  • Go to the Incident Documentation module.
  • Select Fire Incident Setup, then click Workflows.


Lets navigate to the Fire Incident Setup within the Incident Documentation module and select on Workflows.



2. Add a New Workflow
  • Click the + Add New button.





3. Select a Field
  • Choose a field by either searching or scrolling.
Note: If the field is not selectable, a workflow already exists for it. You must edit the existing workflow.



When creating a new workflow choose a field to add a workflow by either searching or scrolling to find the appropriate field.



4. Choose "Hide Workflow"
  • After selecting a field, click on Hide Workflow.
  • Select the + (plus) icon to begin creating the workflow.


Once the field is chosen select Hide Workflow then select the plus icon to begin.



5. Enter a Workflow Description
  • Provide a description. This appears in the workflow menu for easy reference.


It is required to give a Description of this workflow.



6. Add Conditions or Groups
  • Choose between:
    • Add Condition – Define a specific rule that triggers the field to be hidden.
    • Add Group – Define multiple conditions that are evaluated together using AND/OR logic.


Choose if you wish to Add a Group of conditions or Add Conditions to begin assigning conditions and parameters for the field.



7. Configure Conditions
  • For each Add Condition, set:
    • The triggering field (e.g., Primary Incident Type).
    • The condition logic (e.g., is equal to).
    • The value or parameter (e.g., No Emergency - Cancelled).
  • Use AND or OR to combine conditions:
    • AND: All conditions must be met.
    • OR: Any condition can trigger the workflow.


Each time you select Add Condition you will be able to set the rule or rules to trigger the workflow.



8. Configure Groups (if used)
  • When using Add Group, define a set of conditions.
  • Apply AND/OR logic to group conditions.


When selecting the Add Group button enter a set of conditions (rules) that must be met based on the logic defined either by all (And) or any (Or) in order to trigger the workflow.



9. Define the "When" Condition
  • Use the dropdown or search bar to select the field that triggers the condition.


When is the field you want to base the condition on, using the dropdown or search bar to filter the list then select on a field.



10. Select Condition Logic
  • Choose a logical operator such as “equal,” “not empty,” etc.


Choose a condition in which parameters can be met in your workflow.



11. Choose Parameters
  • Select the parameter(s) that complete your rule (e.g., specific incident types).


Choose the parameter or parameters pending on condition set to complete the workflow rule.



12. If you choose to Remove Conditions or Groups
  • Click the trash can icon to delete conditions or groups.


To remove Conditions or Groups select on the trash can icon.



13. Confirm Deletions
  • A warning modal will appear. Click Confirm to delete the selected item.


After selecting the trash can icon a warning modal will populate select Confirm to delete.



14. Save the Workflow
  • When finished, click Save.


When all conditions and or groups are complete select Save.



15. Test the Workflow
  • Open an incident report.
  • Select the incident type that matches the condition (e.g., “No Emergency - Cancelled”).


From within an incident report you are now able to see if the field will hide when conditions are met.



16. Verify Field Visibility
  • Confirm that the targeted field (e.g., Response Zone) is hidden when the conditions are met.


The condition has been met and the Response zone is hidden.


Best Practices

  • Do: Use clear and descriptive workflow names for future reference.
  • Do: Test workflows after creation to verify functionality.
  • Don't: Stack too many unrelated conditions within a single group.
  • Avoid: Overcomplicating logic with nested groups unless necessary.

Troubleshooting & FAQs

Q: Why can’t I select a specific field when adding a new workflow?
A: The field already has an existing workflow. You’ll need to edit that workflow.

Q: My workflow is not hiding the field as expected. What should I check?
  • Ensure the logic (AND/OR) is correctly configured.
  • Verify all condition parameters match exactly.
  • Double-check the incident report scenario to confirm it meets the conditions.
Q: Can I remove workflows later?
A: Yes. You can delete workflows by selecting the trash can icon and confirming the removal.

Additional Sections

User Roles & Permissions
  1. Only users with administrative permissions in the Incident Documentation module can create or edit workflows.



    • Related Articles

    • Creating a Default Value Workflow within NERIS

      Purpose Statement The purpose of this article is to demonstrate how to create a Default Value Workflow. This feature is designed to improve data consistency and reduce manual input by automatically populating fields with predefined values during ...

    • Creating an Error Validation Workflow within NERIS

      Purpose Statement The purpose of this article is to demonstrate how to create an Error Validation Workflow for fire reports. This workflow helps ensure that required data is completed accurately before a report can be submitted. Background ...

    • Navigating the NERIS Workflows

      Purpose The purpose of this article is to provide users with clear guidance on how to navigate and view system-defined NERIS Workflows within the Fire Incident Setup section of the First Due platform. Video Background Information NERIS Workflows are ...

    • Managing and Editing Existing Workflows within NERIS

      Purpose The purpose of this article is to guide users through locating, editing, or deleting existing workflows within the Fire Incident Setup area of the First Due platform. This ensures agencies can efficiently maintain and update documentation ...

    • NERIS - Fire Incident Documentation

      Timeline We’re excited to share important updates on First Due’s transition to the NERIS data standard. We're committed to helping your agency make a seamless transition. Below is a breakdown of what to expect in the coming months, including key ...