Plan a Board

Before building a status board in WebEOC Nexus, you may want to gather requirements for the board and sketch a design of the layout on paper or a whiteboard. Consider the following requirements outlined on this page before creating a board.

You can build and edit your board in WebEOC Nexus or in DesignStudio. This page contains links to steps performed in both products.

If you import a board into DesignStudio that was not initially built in DesignStudio, the drag and drop features in the Components tray will not work as expected. In this case, you must update the board using Code mode.

You can download the Board Building Worksheet to assist with board planning.

General Requirements

  • What is the board’s name?

  • What’s the purpose of the board?

  • What type of board (standard, tasking, resource tracking, and so forth) am I creating?

  • Is an Input view required? An Input view allows users to enter data. You can build one in WebEOC Nexus or DesignStudio.

  • Is a Delete view required? A Delete view is a type of Input view that contains a confirmation message that allows users to delete a record. You can build one in WebEOC Nexus or DesignStudio.

  • Is a Details View required? A Details view is a type of Display view that displays the individual record details in a separate window. You can build one in WebEOC Nexus or DesignStudio.

  • Is a List View required? A List view is a type of Display view that displays all the board’s records, depending on a user’s permission and filters. You can build one in WebEOC Nexus or DesignStudio.

  • Should board users be able to print any of the views to PDFs?

  • Is a Dashboard view required? You can build one in WebEOC Nexus or DesignStudio Pro.

Input View Requirements

If multiple Input views are needed, consider these requirements for each Input view.

  • What fields will be needed to capture data on the Input View?

    For each field:

    • What is the field’s name and label?

    • What type of field is it, text, textarea, checkbox, radio option, or dropdown list?

      In DesignStudio, you can build a board using components that automate creating fields of many types, such as address, date and time, phone, and more. See Board Components List for details.

    • For dropdown lists, does the list exist in WebEOC Nexus? If not, you must create it.

    • For dropdown lists, if you must create the list, what options must be available in the list?

    • For radio options, what options must be available for selection?

    • Is the field required?

    • Is the field a header to help organize the layout?

    • Should the field be conditionally hidden?

    • If the field should be hidden by a condition, what field and value must be set?

  • Will information posted to this board be data-linked to other boards? If so, which fields will be linked and to which boards and fields will this data be linked?

  • Should a child table be used in this view?

  • Should the view include a map?

  • Will user editing privileges be restricted in this view?

    See Board Access and Permissions below for more information.

  • What options will be applicable to this Input view?

    • If all entries, including updates, are to be displayed on the status board, select the Add Only checkbox for the Input view in the Board Editor. If the Add Only checkbox is not selected, only the last update for a record displays on the status board. Regardless of this selection, all record entries for an incident are recorded in the database, including any updates.

    • To set the data entry display to one record entry for the specified status board per user, select the Lock User Input checkbox for the Input view in the Board Editor. Subsequent entries made by the user are entered as updates through the input view for the board and only the last record entry appears.

    • To set the data entry display to one record entry for the specified status board per position, select the Lock Position Input checkbox for the Input view in the Board Editor. Subsequent entries made by the position are entered as updates through the board's input view and only the last record entry appears.

    • To define whether a view can be assigned to a group, select the Assignable checkbox for the Input view in the Board Editor. By default, a board's view is not assignable. When selected, the view can be assigned in the Groups Manager. This is particularly useful when sharing boards (via import/export or WebEOC Fusion). To disable the view so that it cannot be assigned, clear the checkbox.

Details View Requirements

  • Which fields on the Input view will be available on the Details view?

  • For those fields, should all of the field settings in the Input view be used in the Details view?

  • Will user editing and/or viewing privileges be restricted in this view?

    See Board Access and Permissions below for more information.

  • Should fields be conditionally hidden on this view?

  • Should a child table be associated with this view?

  • Should the view include a map?

List View Requirements

If multiple List views are required, consider these requirements for each List view.

Dashboard View Requirements

  • Which boards should be included in a Dashboard view?

  • Should a map be included in the Dashboard view?

Board Access and Permissions

  • Which feature groups, containing which positions, should be granted access to this board?

  • What permissions, to which Input and Display views, set by Board Permission Tags, should be set for each feature group?

After requirements for the board have been identified, you should be ready to begin building the board.

Related Concepts

Boards Management

Related Tasks

Edit Board Overview

Delete a Board

Board Filters

Import and Export Boards

Import and Export Board Data

Select Display View Settings

Select Input View Settings

Edit a Board in DesignStudio

Create a Board