Administrator Guide v8.0

WebEOC
Administrator Guide
Version 8.0
2015 Intermedix Corporation. All rights reserved.

This document contains confidential or proprietary information of Intermedix Corporation, and distribution should be limited to authorized persons only.
Be aware that any disclosure, copying, distribution, or unauthorized and/or commercial use is strictly prohibited. While every precaution has been taken
in the preparation of this document, Intermedix Corporation assumes no responsibility for errors or omissions. Neither is any liability assumed for
damages resulting from the use of the information contained herein.
WebEOC and ESi are registered trademarks of ESi Acquisition, Inc.

MapTac and WebEOC Fusion are trademarks of ESi Acquisition, Inc.
Twitter and Tweet are the registered marks of Twitter, Inc.
Microsoft, Windows, and Internet Explorer are registered trademarks of Microsoft Corporation.
Mozilla and Firefox are registered trademarks of Mozilla Foundation.
Chrome and Android are registered trademarks of Google Inc.
Safari, iPhone, and iPad are registered trademarks of Apple Inc.
BlackBerry is a registered trademark of RIM.
All other trademarks are the property of their respective companies.
Address any questions, comments, or suggestions to:

support@intermedix.com
888-971-2250
6451 N. Federal Highway, Suite 1000
Fort Lauderdale, FL 3330
www.intermedix.com
Table of Contents
Welcome....................................................................................................................................................... 1
Background ............................................................................................................................................... 1
Overview .................................................................................................................................................... 2
Getting Started ............................................................................................................................................ 4
WebEOC Home Page ............................................................................................................................... 4
Control Panel Overview ............................................................................................................................. 5
Navigating WebEOC ................................................................................................................................. 7
Admin Manager Overview ......................................................................................................................... 8
Help and Client Hub ................................................................................................................................ 11
Standard Plugins ..................................................................................................................................... 11
Additional Add-ons .................................................................................................................................. 13
Status Boards .......................................................................................................................................... 13
Users .......................................................................................................................................................... 15
The Users Manager ................................................................................................................................. 15
The Positions Manager............................................................................................................................ 27
The Groups Manager .............................................................................................................................. 36
The Sessions Manager............................................................................................................................ 48
Incidents..................................................................................................................................................... 52
The Incidents Manager ............................................................................................................................ 52
The Archives Manager ............................................................................................................................ 60
The Master Views Manager .................................................................................................................... 63
The Reporter Manager ............................................................................................................................ 68
The Simulator Manager ........................................................................................................................... 80
Processes .................................................................................................................................................. 91
The Boards Manager ............................................................................................................................... 91
The Agency Template Manager ............................................................................................................ 134
Table of Contents
The Dual Commit Manager ................................................................................................................... 139
The Links Manager ................................................................................................................................ 154
The Lists Manager ................................................................................................................................. 156
The Menus Manager ............................................................................................................................. 167
System...................................................................................................................................................... 172
The Admin Profiles Manager ................................................................................................................. 172
The Audit Log Manager ......................................................................................................................... 176
The General Manager ........................................................................................................................... 179
HTML Conventions ................................................................................................................................. 187
Board Components ................................................................................................................................ 187
Edit View Window .................................................................................................................................. 188
Supported HTML Tags for Input Views ................................................................................................. 189
WebEOC-specific Tags ......................................................................................................................... 192
Multi-tiered Lists .................................................................................................................................... 218
Chart and Data Tags ............................................................................................................................. 218
Glossary ................................................................................................................................................... 222
Index ......................................................................................................................................................... 226
ii
Welcome
WebEOC Professional is Crisis Information Management Software (CIMS) that was developed over a
decade ago to meet the needs of emergency management agencies (EMAs) at the federal, State, and
local levels.
Today, WebEOC is used by government agencies, such as the U.S. Departments of Agriculture,
Defense, Energy, Homeland Security (CDP, FEMA, ICE, TSA, and USCG), Health and Human Services,
EPA, and NASA. It is also used by corporations, public utilities, universities, and more.
Although WebEOC and its product suite provide specialized tools for managing crisis information and
emergency response, it can also be used to manage any and all events, agencies, organizations, and
more.
WebEOC includes a default set of boards and plugins that enable any agency to begin using it almost
immediately. An agency can use any or all of the boards as-is, or build an unlimited number of boards
and forms tailored to local requirements. Within the context of WebEOC, a board is an electronic display
that allows you to transmit and share information in real-time with other WebEOC users. WebEOC boards
are the equivalent of large, chronological, or topical paper-based boards that, for years, dominated every
EOC and command center around the world.
Background
Initially introduced in 1997, WebEOC was the first web-based, commercial-off-the-shelf CIMS system
used for emergency management. WebEOC is designed to make crisis information universally available
to authorized users everywhere. It is a tool that can be configured based on local requirements, while
giving agencies the ability to link to a wide assortment of different systems.
As a web-based product, WebEOC ushered in the era of virtual EOCs, making it possible to monitor and
manage an emergency response from anywhere in the world.
WebEOC can be used during the planning, mitigation, response, and recovery phases of any emergency.
It can also be used by agencies during day-to-day activities to manage routine, non-emergency
operations.
Welcome
WebEOCs design is based on the following tenets of emergency information management systems.
CIMS should:
Be affordable.
Be user-friendly.
Be easy to maintain by existing EMA staff with access to the vendors technical support.
Be easy to configure and tailor to the conditions of the agency.
Allow for remote access by authorized users located outside the local area network (LAN).
Comply with the provisions for the National Incident Management System (NIMS).
Comply with the provisions for the Incident Command System (ICS).
Support users who implement both the ICS and Emergency Support Functions (ESF) structure.
Integrate with other systems, such as mapping, and other CIMS and telephonic alert notification
systems.
Integrate public health into emergency management.
Operate within a variety of network configurations.
Have a wide range of features consistent with the four phases of emergency management.
Have help desk support on a 24-hour basis.
As a tool, WebEOC can be configured locally and tailored to almost any process. The default status
boards that come with WebEOC are summarized in this User Help and detailed in the WebEOC User
Help. These status boards can be implemented as-is or they can be modified locally. Status boards can
also be built using standard tools within WebEOC or external HTML editors.
Overview
This User Help provides detailed instructions on setting up and managing groups, positions, users,
incidents, links, lists, master views, and menus. It explains how to assign and restrict user privileges and
how to build checklists, status boards, exercise simulations, and reports. It also covers plugins, such as
Checklists, File Library, Messages, and MapTac. Board building and HTML skills are also covered.
Administrator Guide
Intended Audience
The Help is written for WebEOC administrators and is not intended for the average user. WebEOC users
and administrators should refer to the WebEOC User Help for detailed user instructions. However, users
can be assigned administrative rights and privileges. In these cases, users with administrative privileges
may need to refer to this User Help.
Basic Features
WebEOC is designed to make crisis information available to authorized users everywhere. More
importantly, it is a tool that can be customized based on local requirements while giving agencies the
ability to link to a wide assortment of different systems. WebEOC can be used during the planning,
mitigation, response, and recovery phases of any emergency. It can also be used by agencies to manage
day-to-day activities or routine, non-emergency events.
WebEOC includes a default set of status boards and plugins that enable any agency to begin using
WebEOC almost immediately. An agency can use any or all of the boards as-is or build an unlimited
number of status boards and forms tailored to local requirements. Within the context of WebEOC, a status
board is an electronic display that allows you to transmit and share information in real-time with other
WebEOC users. WebEOC status boards are the equivalent of large, chronological, or topical paperbased boards that, for years, dominated every EOC and command center around the world.
Time Conventions
WebEOC stamps all entries with a time and date. It also tracks and displays who entered the information.
Entries appear in status boards in the order in which they are entered into the system. For example, a
telephonic report is received at 10:00 p.m., and it is entered into WebEOC at 10:01 p.m. The system time
is 10:01 p.m.
Agencies can determine whether to show system times as part of the displayed entry. During setup,
administrators can add additional time fields to status boards that can be user-modified; these times could
represent a time the incident occurred, actual time of receipt, and so forth. These additional time fields, if
used, are separate from the unalterable system time. Normally, agencies enter a time of receipt and time
of occurrence in the narrative description.
Getting Started
Read the following topics to learn about:
WebEOC Home Page
Control Panel
Admin Manager
Status boards
Standard plugins
Additional plugins
If you need additional information, check the Help and Client Hub topic.
WebEOC Home Page

When you log in to WebEOC, or change positions, you are taken directly to the Home page. The Home
page displays agency information, as well as system-wide messages and notifications so that you and
other users are immediately informed of critical information. You can return to the Home page at any time
by clicking the Home tab
at the top of the page.
The position and incident you logged in to appear in fields at the top of the page. Clicking the field opens
a drop-down menu from which you can choose another position or incident.
Open the control panel by clicking the control panel icon
Open the User Help at any time by clicking the Help icon
in the upper left corner of the Home page.

.
Click the Logout link beside your username in the information bar to exit WebEOC.
Administrator Guide
Control Panel Overview

The control panel is the information hub in WebEOC. It contains boards, menus, tools, plugins, and links.
Users see only the items to which they have been granted access.
The features that are available are determined by the version of WebEOC and the plugins that you have
installed.
Following is an example of a control panel.
Open the control panel by clicking the control panel icon
in the upper left corner of the Home page.
Within the control panel sections, options are listed alphabetically. The control panel, components, and
functions are described in detail in the WebEOC User Help.
A star icon
preceding a board name alerts users when new data has been posted to that board. Once
the status board has been opened, the star disappears until new information has been added or existing
information has been updated.
Getting Started
Clicking the name of a board, menu, or plugin opens it in a new tab within the existing window. Clicking
the window arrow
to the right of the name opens the board or item in a new window. Clicking the name
of a link automatically opens that item in a new window.
Menus are located on the control panel in the Menus section. The arrow symbol preceding the menu
name indicates the menu contains items. Items contained in the menus follow the same convention and
behavior as status boards. A star icon
preceding a menu item alerts users when a change has been
made. Once the item containing new data has been opened, the star disappears until new information
has been added or existing information has been updated.
Multiple status boards and/or multiple copies of a status board, plugin, or link may be opened.
Click the name of the menu or the arrow
to the left of its name. The section expands to show you the
available options.
Administrator Guide
Menus can contain status boards, plugins, links, or other menus. When a menu item is selected, it
opens in a new window.
Navigating WebEOC
Clicking an items name in the control panel opens that board, tool, menu, or plugin, in a new window.
The tab for the board or option that is currently in focus is dark blue.
If you have a board tab in focus and changes are made to another board or item that you have open, the
system notifies you by placing the star icon
in the tab header and changing the updated tabs color to
light blue.
When you have many tabs open, you can quickly move from one to another by using the menu on the
right side of the tab bar. Open the menu and click the correct option. That tab comes into focus.
You can also scroll through the open tabs when they expand beyond the visible area by clicking the arrow
icons
to the left and right of the tabs.
Getting Started
To close a status board, menu window, plugin, or link, click the close option in its tab, or in the window.
Note: WebEOC remembers your current view for each position. That is, when you log in the same tabs
are open as when you last logged out or changed positions.
Admin Manager Overview

The gear icon
provides access to the Admin window. Clicking it opens a new window containing
WebEOC administration features.

When this option is selected, the Admin window opens in a new tab in your browser.
Features and functions are now grouped into tabs and subtabs. Tabs provide better context for the
functions found within each. For example, as you work in the Groups subtab, at a glance you can see that
Users, Positions, and Sessions are also managed from the Users tab.
Administrator Guide
Subtabs appear in a logical order. The tasks that are most common appear first. For example, tasks
related to managing Users are more commonly used than those available for Sessions.
Each component manager is described in detail in a dedicated topic of this User Help. The following lists
provide a summary of each admin manager grouped by tabs.
The Home tab displays system-wide messages, and server and support information.
The Users tab contains the following managers:
Users: Configure user accounts and assign credentials that enable users to access WebEOC.
Credentials include usernames and passwords.
Positions: Assign users to positions in WebEOC and create and manage position access codes
(PACs) for self-registration by users.
Groups: Create groups and establish access privileges to boards, links, menus, and plugins;
these appear as links in a users control panel.
Sessions: View a list of users currently logged in to WebEOC and, when appropriate, terminate
user login sessions.
The Incidents tab contains the following managers:
Incidents: Create and manage incidents to track and relay information specific to the incident.
Filter your active and inactive incident data for reporting and viewing purposes. Convert inactive
incidents to active incidents.
Master Views: View all incidents that have been added to that view. Multiple incidents can be
added to a master view. Use the Master View Manager to create new, edit existing, or delete
unwanted master views.
Reporter: Create pre-formatted or ad hoc reports that can then be added as links to the control
panel.
Simulator: Create and manually or automatically post scenario injects to the appropriate status
boards during a drill or exercise.
The Process tab contains the following managers:
Boards: Design, create, and maintain an unlimited number of boards and forms.
Getting Started
Agency Template: Define agency-specific system options. Select an agency name, logos, and
system-wide message. You can also add a policy message to the WebEOC Login window. Board
Template options exist for older boards using the agency template styles.
Dashboards: Design, create, configure and maintain your WebEOC dashboards and define user
views if you have WebEOC Enterprise or have purchased the Dashboards add-on.
Dual Commit: Set up and configure remote WebEOC servers to which data from the local
WebEOC server can be posted.
Links: Set up and configure hyperlinks to URLs, other systems, or files.
Lists: Create and manage lists of items that users can select when updating certain fields on
status boards and forms.
Menus: Group boards, links, plugins, or other menus in any combination under a single link
(menu) on the control panel.
The System tab contains the following managers:
Admin Profiles: Establish a predefined set of specific administrator privileges that can be applied
as a template to a group of users. You can add, edit, or delete admin profiles.
Audit Log: You can view user login information, clear the log, and use the search feature to
search for specific events. The log tracks, records, and displays (in a predefined format) events
that have occurred in the WebEOC system.
General: Access security options, email servers, and more.
WebEOC Fusion: Set up and manage your WebEOC Fusion connection(s).
Other: Other plugins and add-ons for WebEOC appear in this area.
The Plugins tab contains the following managers:
Checklists: Automate procedures and checklists for use within WebEOC during the course of an
incident. Add checklists, assign groups to checklists, and attach files to checklists.
File Library: Manage folders and assign permissions.
MapTac: Create and edit maps, and make maps, markers, and tabs available to users who are
using the MapTac plugin.
10
Administrator Guide
Help and Client Hub

Help
Access the WebEOC User Help by clicking the Help icon
. The User Help opens in a new browser
window. You can view specific instructions or information on all WebEOC features and standard plugins,
as well as detailed instructions about the Admin managers. As with most User Help, you can select a
specific topic or task, use an index to search on a keyword, or search all topics to find the information or
instructions you need.
WebEOC Client Hub

The WebEOC Client Hub is a powerful community site where you can find WebEOC documentation and
support options.
Intermedix regularly adds to and maintains the content on the Hub, and actively monitors posts.
In the Hub, you can find the following and more:
People - Access resource information on user groups, as well as profiles of team members and
Client Service Managers (CSMs).
Product Suite - Get the latest information, downloads, and documentation for our entire
WebEOC Product Suite, including add-ons, all in one place.
Knowledge Base - Access Best Practices, the Community Board Swap, Techie Tips, and other
official announcements.
Documentation - Download the latest documentation, including manuals, Quick Reference

Guides (QRGs), and Product Announcements.
Community - Search our Community forum for information on your toughest challenges, and
post solutions and strategies to help your fellow administrators.
Standard Plugins
The following plugins are included in a standard installation of WebEOC. Refer to the WebEOC User Help
for detailed instructions on using plugins.
11
Getting Started
Plugin
Description
Enter incident-specific checklists that users can complete. You can identify steps as
main steps or sub-steps and can order and re-order these steps using arrow
Checklists
buttons. Steps and sub-steps can be marked as Complete, Open, Previously

Accomplished, or Not Applicable. When running a checklist, remarks can be
added to a step and displayed or hidden as desired.
File Library
Upload and share documents and files with other users through WebEOC.
An authorized user can upload an image file of a map, dispersion model, digital
MapTac
photo, and so forth, from any map, GIS source, or digital camera. Users can apply
markers, labels, shapes, and/or polygons, and share the map with other authorized
users.
Messages
NWS
Weather
Alerts
Users can communicate with other users using an internal messaging tool and
externally via email.
Users can view and link to the National Weather Service watches, warnings, and
advisories.
Agencies can generate pre-formatted or custom reports based on individual status
boards. They can also generate a comprehensive incident report consisting of
Reporter
individual or all status boards in an agencys WebEOC system. Because WebEOC

uses Microsoft SQL Server for the database, customers can use Access, Crystal,
or other tools to generate reports.
Search Tool
Sessions
Users can search for information across all their boards.

See which users are logged in and view their username, position, assigned incident,
name, and log-in date and time.
A training official or an exercise controller can build, edit, and control delivery of
exercise scenario injects into WebEOC status boards manually or automatically in
Simulator
real-time. With Simulator, you can manage your Master Scenario Events List
(MSEL). Injects can be started, stopped, reset, added, or deleted as necessary to
meet training or exercise objectives. You can also import injects from or export
injects to an MS Excel Spreadsheet.
12
Administrator Guide
Additional Add-ons
WebEOC offers many add-ons that you can purchase to extend the functionality of the system. See the
WebEOC Client Hub for additional information.
Status Boards
The WebEOC User Help explains how to use WebEOC status boards. The following table summarizes a
typical set of status boards. This set of boards is available with the Core, Professional, and Enterprise
versions of WebEOC.
Board
After Action Review
Checklist
Damage Assessment
Description
Document comments and recommendations after an event, and track
resolution of items.
Create, edit, and view a chronological list of specific items users have
completed during an incident.
Track detailed information on the cumulative dollar loss due to damage
to private and public properties.
Document actions and major incidents taken by the personnel in the
Event Reporting
EOC. Event Reporting consists of the Activity Log and Significant Events
views.
File Library
Press Release
Resource
Request/Task
Assignments
Road Closures
Schedule
Shelters
13
Upload, organize, and share documents and files.

Post press releases that have been published. Users can post a
description with the attached press release.
Enter and track requests or tasks, and post updates on the status of
tasks and requests.
Document and track specific details on road closures to include status,
location, damage, and suggested detours.
Enter pertinent events and view visual cues as they progress through
their cycle. Also referred to as a Battle-Rhythm.
Track the status of shelters to include status, occupancy, and points of
contact.
Getting Started
Sign In/Out
Situation Report
Track and show everyone who is currently on shift and provides details
about how to contact them.
Publish a summary report based on one of two common methodologies:
ICS or ESF.
14
Users
This section provides information about how to manage users within the system.
The Users Manager

The Users Manager allows administrators to create and edit basic user settings, such as usernames,
passwords, permissions, email addresses, and more.
Read the following sections to learn about:
User positions
Position Access Code (PAC)
Roles
Reports
Positions
Each user account must be assigned to a position, each position must be assigned to a group, and each
group must be assigned to an incident. Without a position, a user cannot log in to WebEOC. Without a
group, a user does not have permission to any incidents, and without being assigned to an incident, a
user does not have permission to any boards, plugins, and so forth.
Position assignments made in the Users Manager are automatically applied to the Positions Manager.
Likewise, changes made in the Positions Manager are automatically applied to the Users Manager.
15
Users
Position Access Code

If you, as the WebEOC administrator, provide an individual with a position name, position access code
(PAC), and your agencys WebEOC URL, that individual can set up their own user account. Enable this
option in the Security section of the General Manager. If users set up their own accounts, provide them
with the instructions from this section of the Help.
Roles
Users have basic access to WebEOC.
WebEOC administrators have full access to the system. Granting users WebEOC administrator privileges
through the Users Manager automatically enables them to perform all administrative functions in
WebEOC.
Users cannot grant themselves WebEOC administrator permissions. User accounts configured as
administrators must be created by a WebEOC administrator.
For more details on administrative roles, refer to Account Types.
Reports
You can build the following user reports from the Users Manager:
User Activity
User Position
Administrative Access
Usage
16
Administrator Guide
Configuring the Users Window
The Actions button in the Users window allows you to choose which columns of additional information
fields are displayed in the Users window.
To configure columns:
1. In the Users list, click the Actions button, then click Configure Columns to choose the columns of
data to display.
2. Select the columns to display.

3. Click Save.
17
Users
Planning a New User Account

Before creating a user account, determine the users information and permission requirements. Answer
the following questions before creating a user account:
What is an appropriate user name and password for the user account?
What position or positions will the user be assigned to? Does the position already exist?
Will the user be a WebEOC administrator? If so, do they need access to all administrator areas
or only particular ones?
Will the user need to be able to send emails?
Will this account only be used by the WebEOC API?
Account Types
Be sure to determine the appropriate type of account for a new user. Account types offer different
permissions and define the actions the user can perform in the system.
User - This is the most common type of account; it does not have administrator permissions.
Full Administrator - This account gives the user full access to the system and administrative
tasks and allows them to create and modify any type of user account.
Partial Administrator - This type of account offers partial administrative permissions. Partial
administrators are assigned one or more admin profiles that grant limited access to specific
administrative functions.
Note: This option is available only if admin profiles have been defined.
Sub-administrator - Full administrators can assign the sub-administrator role to users in order to
distribute some of the user management workload. The full administrator assigns the users and
positions that the sub-administrator can manage. The sub-administrator can manage assigned
accounts and run a limited number of reports for this subset of users and positions.
18
Administrator Guide
Sub-administrators can also create additional user accounts as needed and assign and modify
position assignments.
Note: The sub-administrator account type is available in WebEOC Enterprise only.
Service - This is an account type that is designed for use with Dual Commit, WebEOC Fusion,
or the API. This account cannot be used to log in to WebEOC.
Service as Administrator - In addition to having the same properties as the Service account,
this account also allows users to perform the administrative API functions.
Single-user or Multi-user Accounts

Important: This feature is included only in earlier versions of WebEOC and might not be available in your
system.
WebEOC user accounts can be configured as either single- or multi-user. Multi-user accounts allow more
than one user to be simultaneously logged in with the same username and password. Single-user
accounts allow only one person to be logged in at any given time. If a user attempts to log in to a singleuser account, another user sees an error message on their control panel and is automatically logged out
of the account.
If you are ever logged out of the system by another user, contact your WebEOC administrator for
assistance.
You can configure an account as single- or multi-user when you create a new account or edit an existing
account.
Creating a User Account

The Create User window allows you to create user accounts in WebEOC.
Note: Partial Administrator rights and permissions are assigned via an Admin Profile.
To create a new user account:
1. In the Admin window, click the Users tab, then click Users.
19
Users
2. In the Users window, click the Create User button.
3. In the Create User window, enter the user's Username. This is a required field.
4. Enter the user's primary email address in the Primary Email field. This is a recommended field.
5. Enter the user's secondary email address in the Secondary Email field. Use the add icon
to add
the address to the list. Repeat this step if you want to add more email addresses to this account.
Tip: To remove an email address from the list, select the email address, then click the remove icon
.
6. Enter the user's Password, and enter it again in the Confirm Password field.
Note: Passwords are case sensitive, are limited to 50 characters, and can contain virtually any
character, including special characters such as a space, #, &, $. System-wide password
requirement settings can be configured from the System General Manager settings.
7. Optionally, select the Change password at next login? check box to ensure that the user changes
their password the next time they log in.
Tip: This feature is useful if an administrator has set an initial password for a user or has reset a
users password.
20
Administrator Guide
8. Click the Account Type.
Tip: The options visible in this list depend on whether you have full administrator permissions. The
Sub-Administrator account type is available only in WebEOC Enterprise. Refer also to Account
Types.
9. If appropriate, specify account administration settings in the System Access section:
Note: This section is visible when you select Partial Administrator from the Account Type list. It
is also visible if you are using WebEOC Enterprise and you select User or Sub-Administrator as
the account type.
For a Partial Administrator, assign one or more Admin Profiles.
For a Sub-Administrator, assign the users and positions this user can manage.
10. Select Disabled for User Update to disable the update between the Additional User Information
page displayed during the login process and the data stored in the Edit User page.
Tip: If you do not select the Disable User Update option, all updates the user makes during the
login process are saved to the user's account profile.
11. If multiple users are likely to use this account simultaneously, or log into an account on multiple
devices simultaneously, select Enabled for Multiple User Login.
Tip: The Multiple User Login option may not be available in your WebEOC system.
12. Select Enabled for Inactivity Logout to make a user session expire after 20 minutes of inactivity.
By default, this setting is enabled.
13. Optionally, specify the user's background color. Click in the User Color field to use the palette to
select the color or enter a color code.
Tip: Background colors can help users distinguish between usernames that are displayed on a
status board.
14. In the Personal Information section, complete the fields as applicable.
Note: Information in this section auto-fills the Additional Login Information window during the login
process. You can change information that is displayed by default. Enter the user's first and last
name in the Name field.
15. If applicable, attach a file to the user's account. Click the Choose File button to locate the file on
your computer.
21
Users
16. To assign a position to the user account:
a. In the System Access section, if it is not already selected, click the Positions tab.
b. Click Add Position.
c. Select one or more positions.
d. Click Add.
17. To view mobile devices that have been configured to access WebEOC, in the System Access
section, click the IMX Connect tab.
18. Click Save.
Editing an Existing User Account

The Users window contains a search feature that allows you to search for a user using either the first or
last name in the Filter field.
Note: A sub-administrator can manage a limited number of users and positions, as specified by the full
administrator. For more information, refer to Account Types.
To edit an existing user account:
2. Click the user name of the user's account you want to modify.
3. Make your changes in the Edit User window.
Tip: Refer to Creating a User Account for more detailed instructions.
4. Your changes can include the following:
a. If appropriate, change the Account Type.
22
Administrator Guide
Tip: The options visible in this list depend on whether you have full administrator permissions. The
Sub-Administrator account type is available only in WebEOC Enterprise. Refer also to Account
Types.
b. If appropriate, specify account administration settings in the System Access section:
For a Partial Administrator, assign one or more Admin Profiles.
For a Sub-Administrator, assign the users and positions this administrator can manage.
c. To delete a secondary email address, select the email address you want to delete, click the
remove icon
, then click OK to confirm the action..
d. To remove an assigned position, select the position in the Positions tab in the System Access
section, then click the Remove button.
Note: If you make position changes in the Users Manager, those changes are automatically
applied to the Positions Manager.
5. Click Save.
Deleting a User Account

Deleting a user account removes the user from the Positions Manager.
Note: The WebEOC Administrator account cannot be deleted from the system.
To delete a user:
2. In the Users window, click the trash can icon
3. In the confirmation window, click OK.
23
next to the user account you want to delete.
Users
Locking a User Account

Important: Only a WebEOC administrator or a user with appropriate admin profile permissions can lock
or unlock a user account.
In the General Manager section, the administrator can set a limit to the number of unsuccessful login
attempts. If a user exceeds the number of log in attempts allowed, their user account is automatically
locked and a lock icon appears in the Users window.
To manually lock a user account:
2. Click the user account you want to lock.
3. In the Login Information section, select the Account Disabled check box.
4. Click Save.
Unlocking a User Account

Important: Only a WebEOC administrator or a user with appropriate admin profile permissions can lock
or unlock a user account.
In the General Manager section, the administrator can set a limit to the number of unsuccessful login
attempts. If a user exceeds the number of log in attempts allowed, their user account is automatically
locked and a lock icon appears in the Users window.
To manually unlock a user account:
24
Administrator Guide
2. Click
Unlock User next to the user account that has been locked.
3. Click OK.
Viewing the User Activity Report

The User Activity Report lists users and user account details, including each user's username, real name,
primary email address, last attempted login date and time, and last successful login date and time. This
report can assist you in managing user accounts. From this report you can quickly determine whether
each user account has an associated email address, which is required for system emailing capabilities.
Note: Only users with access to the Users Manager can access this report.
To view the User Activity Report:
2. In the Users window, click the Actions button, then click one of the following options:
User Activity Report - View to open the report in a new window. Opening the report in a new
window allows you to print it as a PDF.
25
User Activity Report - Export CSV to export it to a CSV (comma-separated value) file.
Users
Viewing the Administrative Access Report

The Administrative Access Report shows you which users have full or partial administrative access and
the admin managers they have access to. Only users with access to the Users Manager can access this
report.
To view the Administrative Access Report:
Administrative Access Report - View to open the report in a new window. Opening the report
in a new window allows you to print it as a PDF.
Administrative Access Report - Export CSV to export it to a CSV (comma-separated value)

file.
Viewing the User Position Report

The User Position Report lists every user and the positions they are assigned to.
To view the User Activity Report:
User Position Report - View to open the report in a new window. Opening the report in a new
26
Administrator Guide
User Position Report - Export CSV to export it to a CSV (comma-separated value) file.
Viewing the Usage Report

The Usage Report includes a number of statistics, including the number of non-service accounts and the
number of unique logins by year and month.
This report is generated as a PDF file.
To view the Usage Report:
2. In the Users window, click the Actions button, then click Usage Report.
The Positions Manager

In an emergency response organization, users traditionally serve specific positions, such as public
information officer (PIO), logistics chief, or safety officer. In WebEOC, organizations can create an
27
Users
unlimited number of positions for users to fill. Multiple users can hold a single position in WebEOC and a
user can be assigned to multiple positions.
When an agency implements the positions feature, the users account is set up with the users proper
name. The users account is assigned to a position or positions, which defines the users role in the
response organization. If a user can be assigned to multiple positions, the user is prompted to select the
specific position during login.
Positions and position access codes (PACs) allow new users to self-register and create user accounts for
themselves the first time they access WebEOC. This reduces the burden on administrator for managing
user accounts on an ongoing basis.
See also the information on self-registration and security features located in the General Manager.
Every position must be assigned to a group. A positions group assignments determine the boards, links,
menus, and plugins that appear in the users control panel. Positions assigned to multiple groups have
the least restrictive permissions from each.
Position Access Codes

A Position Access Code (PAC) serves as a layer of password protection for a position, separate from the
password the user creates for their user account. The WebEOC administrator can generate the PAC as a
way of controlling who can register for a position.
PACs serve the following purposes:
Implementing PACs reduces the burden on administrators during an emergency. After users are
given their position name, PAC, and the URL to their WebEOC, they are able to register
themselves rather than burdening the administrator with that task. Administrators are then able to
28
Administrator Guide
focus on more substantive issues during the emergency. When possible, administrators should
define positions and have users register their accounts before an emergency.
PACs prevent users from registering for unauthorized positions. Before users can self-register for
a position in WebEOC, they must have the PAC for that specific position.
PACs add individual accountability. When a user logs in to WebEOC, they log in to a specific
position. This allows administrators, through the Audit Log, to track the actions of multiple users
that have filled one position during an emergency. Administrators are able to track individuals and
positions independently.
PACs and User Self-registration

PACs are only used when the WebEOC administrator enables the Allow Self-registration feature in the
General Manager.
PACs are randomly generated by WebEOC. The following are examples of PACs.
Wx9%z{B7
2d+WK4i%
L&c34eD{
PACs can be created or changed on a position-by-position basis or for all positions simultaneously.
Generating a PAC for a Single Position

To generate a PAC for a specific position:
1. In the Admin window, click the Users tab, then click Positions.
2. In the Positions window, click the position for which you want to generate a PAC.
29
Users
3. Click the Generate PAC button. The PAC appears in the PAC field, overwriting any PAC that was
previously in the field.
4. Click Save.
Generating PACs for All Positions Simultaneously

Note that, when you generate PACs for all positions simultaneously, existing PACs are also updated.
To generate PACs for all existing positions simultaneously:
2. In the Positions window, click the Actions drop-down list button.
3. Click Generate PACs.
4. In the confirmation window, click OK. The Positions window fills with PACs for each position.
Creating a New Position

To create a new position:
30
Administrator Guide
2. In the Positions window, click the Create Position button.
3. In the Create Position window, enter a Name for the new position. This is a required field.
4. In the Comments field, enter additional information about this position.

5. To assign a background color to the position name, click inside the Color field. When the color
palette appears, use the crosshair icon to select the color. This color is applied wherever the position
field is displayed on a board.
Tip: You can also enter a color code in the field.
6. To generate a position access code (PAC) for this position, click the Generate PAC button.
7. To assign the position to a group or groups:
a. If it is not already selected, click the Groups tab in the System Access section.
b. Click Add Group.
31
Users
c. Select one or more group names in the list.
d. Click Add.
8. To remove a group:
a. If it is not already selected, click the Groups tab in the System Access section.
b. Select one or more group names you want to remove.
Tip: To select all of the groups, select the check box beside the Name column title.
c. Click Remove.
Note: A positions group assignments control their level of access permissions for boards, menus,
and plugins.
9. To assign a user or users to the position:
a. Click the Users tab in the System Access section.
b. Click Add User.
c. Select one or more user names in the list.
d. Click Add.
10. To remove a user or users from the position:
a. Click the Users tab in the System Access section.
b. Select one or more user names you want to remove.
c. Click Remove.
11. Click Save.
Note: Changes made to user assignments in the Positions Manager are automatically applied to
parameters set in the Users Manager.
Editing an Existing Position

To edit an existing position:
32
Administrator Guide
2. In the Positions window, click the name of the position you want to edit.
3. In the Edit Position window, make your changes.
Note: For additional information on fields located in the Edit Position page, see the Creating a New
Position topic.
4. Click Save.
Note: Changes made to user assignments in the Positions Manager are automatically applied to
the Users Manager.
Deleting a Position
Note: Before deleting a position, make sure all users currently assigned to the position have been
reassigned to another position. Otherwise, they may not have access to WebEOC components from their
control panel.
To delete a position:
1.
33
In the Admin window, click the Users tab, then click Positions.
Users
2. In the Positions window, click the trash can icon
next to the name of the position you want to
delete.
3.
In the confirmation window, click OK.
Note: Changes made to user assignments in the Positions Manager are automatically applied to the
Users Manager.
Viewing the Position Matrix Report

The Position Matrix Report lists the positions in your organization, the boards those positions have
access to, the level of access to each board, and the positions access to menus, links, plugins, incidents,
file library folders, checklists, MapTac maps, and process permissions. Only users with access to the
Positions Manager can access this report.
To view the Position Matrix report:
2. In the Positions window, click the Actions button, then click one of the following options:
Position Matrix Report - View to open the report in a new window. Opening the report in a new
Position Matrix Report - Export CSV to export it to a CSV (comma-separated value) file.
34
Administrator Guide
Viewing the Individual Position Report

The Individual Position Report lists the boards, the level of access to each board, and the access to
menus, links, plugins, incidents, file library folders, checklists, MapTac maps, and process permissions for
a selected position. Only users with access to the Positions Manager can access this report.
To view the Individual Position Report:
2. In the Positions window, click the position you want to view the report for.
Individual Position Report - View to open the report in a new window. Opening the report in a
new window allows you to print it as a PDF.
Individual Position Report - Export CSV to export it to a CSV (comma-separated value) file.
Viewing the PAC Report

The PAC Report provides a quick list of positions and their associated PACs. Only users with access to
the Positions Manager can access this report.
35
Users
To view the PAC Report:
PAC Report - View to open the report in a new window. Opening the report in a new window
allows you to print it as a PDF.
PAC Report - Export CSV to export it to a CSV (comma-separated value) file.
The Groups Manager

In WebEOC, group profiles provide a quick and easy method of assigning access privileges to incidents,
boards, plugins, links, and menus.
These group permissions are normally based on the duties performed, positions assumed, and
information required during the course of an incident. Each user in WebEOC is assigned to a position that
can then be assigned to a group. Because group privileges also determine the options displayed in the
36
Administrator Guide
control panel (such as boards, links, menus, and plugins), even single-user positions must be assigned to
a group.
In addition to defining the contents of the control panel, a group profile provides an additional method to
set up, apply, and manage user permissions, which are then applied to the positions assigned to the
group. When a position is assigned to two or more groups with differing permissions, the users assigned
to that position inherit the combined, least restrictive set of privileges.
Organizational groups allow system administrators to establish a local process for creating, reviewing,
assigning, and tracking mission and task requests in WebEOC. Members of these internal organizational
groups can be assigned process permissions that give them task assignment and/or requesting
capabilities. Since administrators can place limits on whom the user can task, what the user can do, and
what they can view, setting up organizational groups can eliminate structural miscommunication and
duplication of tasks.
Permissions for a user are also determined by the administrator profiles to which they belong. Users
assigned to multiple groups and administrator profiles have the least restrictive permissions from each. If
a user needs some administrative privileges, but not all, specific administrative permissions can be
configured for the user through the Admin Profiles Manager.
Planning a Group
Before creating a new group, determine the groups information and permission requirements. Answer the
following questions before creating a new group:
Is there an existing group or set of groups with the proper permissions that would meet the needs
of the users? Does a new group need to be created?
Which positions will be assigned to the group?

Which incidents will the group need to be granted access to?
Are process permissions to be assigned to the group?
Which boards, links, menus, and plugins will the group need to access? These items will appear
on the users control panel.
37
For each component to which the group is granted access, what privileges will they require?
Users
Creating a New Group

The Create Group window allows you to create a group and add positions, incidents, boards, plugins,
links, and menus to the group. The group name is the only required field/option.
You can save the group at any point during the group setup process.
Note the following about this process:
To remove any item you selected from the group, click it in the list, then click the Remove button.
To select all items in a list, select the select all check box at the top of the list.
38
Administrator Guide
The Input and Display drop-down lists contain the views configured in the Boards Manager.
Changes made in the Boards Manager automatically appear in the Groups Manager.
The Input and Display drop-down lists contain only those views that were marked as
"assignable" in the Boards Manager.
The links available for selection were created in the Links Manager.
The menus available for selection were created in the Menus Manager.
Certain fields that appear in this workflow have default values that were set up elsewhere in the
application. For example, the Label field's default value for a board was set up in the Boards
Manager; the Label field's default value for a link was originally set up in the Links Manager; and
the Label field's default value for a menu was set up in the Menus Manager. You can change
these values.
Boards can be configured to allow access based on board permission tags. These tags are
created in the board views and appear in the Board Permission Tags tab when you add a board.
Typical board permission tags are edit and delete permissions, though these can also be used to
control access to any component in the view.
To create a group:
1. In the Admin window, click the Users tab, then click Groups.
2. In the Groups window, click the Create Group button.
3. Enter a Name for the group.

4. In the Comments field, enter a description or additional information about this group.
Note: It is important to note whether there are any system dependencies on the naming or
existence of the group.
5. Select the Organizational Group check box if process permissions will be used.
6. Assign positions to the group:
39
Users
a. In the Settings section, if it is not already selected, click the Positions tab, then click Add
Position.
b. Assign one or more positions to the group by selecting the positions in the list.
c. Click the Add button.
7. Assign one or more incidents to the group:

a. In the Settings section, click the Incidents tab, then click Add Incident.
b. Select one or more incidents in the list.
c. Click the Add button.
8. Assign boards to appear in the control panel for the group:
a. In the Settings section, click the Boards tab, then click Add Board.
b. Click the board in the Board drop-down list.
c. To change the Label to an alias to be displayed on the control panel, delete the text and type a
new name for the board.
40
Administrator Guide
d. If applicable, click the input view in the Input drop-down list. Most often, input views are
assigned using board permissions and the boards input view is left as None.
e. Select the display view in the Display drop-down list.
Note: If the board contains filters and board permission tags, filters and tags appear under tabs in
the Add Board window.
f.
Click the View Filters tab.
g. Select the filter or filters.

Tip: If you select multiple filters, only those entries meeting all of the criteria selected appear in the
view.
h. Click the Board Permission Tags tab.
i.
Select a check box for every appropriate permission tag.
j.
Click Save.
k. Repeat these steps for each board you want users in this group to be able to access.
9. Add plugins to the control panel for the group:
a. In the Settings section, click the Plugins tab, then click Add Plugin.
b. Click the plugin in the Plugin drop-down list.
c. To change the Label to an alias to be displayed on the control panel, delete the text, and type a
new name for the plugin.
Tip: The Label field's default value is the plugin's name.
d. If applicable, assign Permissions.
Tip: Permissions do not apply to all plugins.
e. Click Save.
10. Add links to appear in the control panel for the group:
a. In the Settings section, click the Links tab, then click Add Link.
b. Click the link in the Link drop-down list.
41
Users
new name for the link.
d. Click Save.
11. Add menus to appear in the control panel for the group:
a. In the Settings section, click the Menus tab, then click Add Menu.
b. Click the menu in the Menu drop-down list.
new name for the menu.
d. Click Save.
12. Click Save.
Note: To update the control panel, a user must log out and then log back in to WebEOC, or use the
Ctrl+R keyboard keys.
Editing an Existing Group

To edit an existing group:
2. In the Groups window, click the name of the group you want to edit.
3. Edit the group settings as needed, then click Save.
42
Administrator Guide
Tip: To remove an incident, board, subscription board, plugin, link, or menu from the group, click
the relevant tab in the Settings section, select the item(s), then click the Remove button.
Note: For additional information on fields located in the Edit Group page, see the Adding a New
Group topic.
Deleting a Group
Before you delete a group, make sure the positions in the group are assigned to another group. Users in
positions not assigned to a group can log in to WebEOC but cannot access boards, menus, links, or
plugins.
To delete a group:
2. In the Groups window, click the trash can icon
next to the group you want to delete.
Assigning Process Permissions

By selecting the Organizational Group check box when adding or editing a group, you are enabling
process permissions. You should then assign process permission to the group.
The Process Permissions window contains process permission categories created by clicking the
Manage Process Permissions button. Refer to Adding a Process Permission for detailed instructions on
adding a category.
43
Users
To assign process permissions for an existing group:
1. Click the Users tab, then click Groups.
2. In the Groups window, click Enabled beside the group you want to assign permissions to.
Note: Only groups that have the Organizational Group check box selected can be assigned
process permissions. The Organizational Group check box is located in the Edit Group window.
3. To assign process permissions:
a. Click Add Group under the applicable Process Permission section.
b. Select one or more group names in the list.
c. Click Add.
4. Click Save.
Creating a Process Permission

Administrators can manage as many processes as they need to support their organization. With the
Manage Process Permission feature, administrators can add, edit, or delete any process for a group.
Situation reporting, making requests, or assigning tasks are only a few examples of the many processes
that can be managed through WebEOC process permissions.
To add a process permission:
2. In the Groups window, click the Actions button, then click Manage Process Permissions.
44
Administrator Guide
3. Click the Create Process Permission button in the Process Permissions window.
4. In the New Process Permission window, enter the name in the Process Permission Name field.
5. In the Comments field, enter a description or additional information about this process permission.
6. Click Save.
Editing a Process Permission

To edit a process permission:
2. In the Groups window, click the Actions button, then select Manage Process Permissions.
45
Users
3. In the Process Permissions window, click the name of the process permission.
4. Edit the Process Permission Name or Comments fields as applicable.
5. Click Save.
Deleting a Process Permission

To delete a process permission:
46
Administrator Guide
3. In the Process Permissions window, click the trash can icon
next to the process permission you
would like to delete.
4.
In the confirmation window, click OK.
Viewing the Process Permissions Report

The Process Permissions Report lists all groups in your organization and the process permission
assignments configured for them.
To view the Process Permissions report:
2. In the Groups window, click the Actions button, then select one of the following options:
Process Permissions Report - View to open the report in a new window. Opening the report in
a new window allows you to print it as a PDF.
47
Process Permissions Report - Export CSV to export it to a CSV (comma-separated value) file.
Users
Viewing the Process Permissions Boards Report

The Process Permissions Boards Report provides details about the process permissions that are
currently in use, which can aid you in making appropriate decisions about board and view maintenance.
The report lists the board name and the process permission group associated with each. You can
generate a PDF file or a Microsoft Excel spreadsheet.
This report is available from the Process Permissions page of the Groups Manager.
To view the Process Permissions Boards report:
3. In the Process Permissions window, click the Actions button, then click one of the following options:
Process Permissions Board Report - View to open the report in a new window. Opening the
report in a new window allows you to print it as a PDF.
Process Permissions Boards Report - Export CSV to export it to a CSV (comma-separated

value) file.
The Sessions Manager

A session is the period of time in which a user is logged in to WebEOC. Users authorized to access the
Sessions Manager can see which users are currently logged in to WebEOC and terminate an individual
user or all users.
48
Administrator Guide
The Sessions List identifies the user account, the position, the incident the user is currently logged in to,
the users name (if applicable), and the date and time the user logged in to the system. In addition:
User logins are added to and removed from the Sessions window as they log in and out of the
system.
Additional detailed information for the user may be available if the Require Additional Login
Information check box is selected in the General Manager.
Users who are involuntarily logged out through the Sessions Manager receive an advisory message in
the WebEOC window and must log back in to continue using WebEOC.
Viewing Session Information

To view session information:
1. In the Admin window, click the Users tab, then click Sessions.
2. In the Sessions window, click the user record you want to view.
3. In the Session Information window, click Back to Sessions to return to the Sessions window.
49
Users
Terminating a Login Session

To terminate a users log in session:
2. Click the trash can icon
next to the user session you want to terminate.

Users who are involuntarily logged out through the Sessions Manager receive an advisory message in
the WebEOC window and must log back in to continue using WebEOC.
Terminating All Login Sessions Simultaneously

Important: Terminating ALL user login sessions ends every users WebEOC session. This process
should only be used in extreme cases.
To terminate all user login sessions simultaneously:
2. Click the Actions button, then select End All Sessions.
50
Administrator Guide
Note: When terminating all login sessions, the Sessions window is purged, with the exception of the
session performing the operation. Users who are involuntarily logged out through the Sessions Manager
receive an advisory message in the WebEOC window and must log back in to continue using WebEOC.
51
Incidents
This section describes how to manage incidents within your WebEOC system.
The Incidents Manager

WebEOC is an incident-based information management system, capable of managing multiple incidents
simultaneously yet independently. This is critical for organizations that function in an oversight or
regulatory role and that, by the very nature of their business, must manage and/or track multiple
incidents, or that has an industry structure involving multiple operating site locations.
You can set up an incident or edit an existing incident through the Incidents Manager in the Admin
window. It is maintained as an active incident until you change it to inactive by clearing the Active check
box.
52
Administrator Guide
At the start of an incident, users create the incident in the system and assign applicable groups. During
log in, the Incident drop-down list is filtered based on the group permissions of the selected position.
Users can begin posting information after selecting the incident and successfully logging in to the system.
With WebEOC, agencies and users can track individual incidents or include multiple incidents in a
common master view. This master view feature is discussed in detail in The Master Views Manager.
Users with access to the Incidents Manager have the ability to run comprehensive incident reports to
include all boards or any combination of boards. All data fields for each board selected are included in the
report.
WebEOC is automatically configured with a Setup incident feature that appears in the Incident dropdown list. Authorized users can use this option to access and set up configurations for any admin
manager and configure and manage static data in a board. The Setup incident feature is not available
from the Incidents Manager list and, therefore, cannot be deleted from the system.
Setup Incident Overview

Accessing the "Setup" incident cannot be done using the Incidents manager. WebEOC Administrators
and users with admin profile permission can access this incident when logging in to WebEOC. Setup is
an option listed in the Incident field.
Use the setup feature to perform administrative and configuration functions in WebEOC. Setup is also
used to configure pre-canned information that is duplicated in a static status board for each subsequently
created incident.
Data linking is not available in the input view in the user interface when logged in to Setup. Also, you
cannot run drills or exercises through Setup. Use the Simulator Manager to create and run drills or
exercises.
53
Incidents
Static Entries in Setup

When administrators are logged in to the Setup incident, pre-canned or static entries can be added or
updated using the applicable input view. Following are two examples where static entries are used:
An agency that routinely adds a set of entries for any incident can configure the status board as
static (through the Boards Manager) and add the entries to the specified status board using
Setup. Whenever a new incident occurs, the pre-canned entries automatically appear on the
board. If any of the entries need to be changed, the static entries can be updated in a similar way
to any other board entry.
As an example, pre-canned entries can be used in a shelter board listing the shelter name, its
capacity, or other available features. During an annual review, if a change occurs, you can edit or
delete the static entry to keep your pre-canned shelter board information current.
Creating a New Incident

Use the Incidents Manager to quickly create an incident.
The new incident's date is automatically set to the current date and time. You can change this
information.
You can set the incident to appear as the default when users are logging in to WebEOC. The user can
select a different incident if they are a member of a group assigned to that incident. The last incident
selected as the default, by the administrator, overrides the previously set default.
In order for users to access an incident, a WebEOC administrator must assign it to their group or groups.
To create a new incident:
1. In the Admin window, click the Incidents tab, then click Incidents.
2. In the Active Incidents window, click the Create Incident button.
54
Administrator Guide
3. Enter a Name for the incident.
4. If you want, change the date, delete the text, and enter a new date using this format: mm/dd/yyyy
hh:mm:ss (month, day, year, hour, minutes, and seconds).
Note: The format is based on the locale settings for international compatibility.
Tip: If you use an invalid format or leave the Date field blank, you cannot save the incident and an
error message appears in red next to the Date field.
5. By default, the incident is created as an active incident. If you want to change it to an inactive
incident, clear the Active check box.
6. If you want the incident to appear as the default when users are logging in to WebEOC, select the
Default check box.
7. Select one or more groups to assign to the incident in the Groups list:
a. In the Groups section, click Add Group.
b. Click one or more groups from the list.
Tip: To select all the groups, select the select all check box in the Name column heading.
c. Click Add.
55
Incidents
8. Select a master view in the Master Views section:
a. In the Master Views section, click Add Master View.
b. Click one or more views from the list.
Tip: To select all the views, select the select all check box in the Name column heading.
c. Click Add.
9. Click Save.
Editing an Incident
As the scale, nature, or cause of an incident becomes apparent, it might be necessary to edit the incident
in WebEOC.
If there are no master views set up in your instance, the Master Views section does not appear in the Edit
Incident window.
To edit an incident:
2. Click the name of the incident you want to edit.

3. In the Edit Incident window, make your changes.
4. Click Save.
Deleting an Incident
Important: If you delete an incident, all information associated with the incident is deleted from the
system and cannot be retrieved. Therefore, if an incident contains useful data, consider making it inactive
rather than deleting it.
56
Administrator Guide
To delete an incident:
2. Select the trash can icon
next to the incident you want to delete.
Note: You cannot delete an incident you are currently logged in to. You must first log out of
WebEOC and log back in to a different incident.
Viewing the Incident Activity Report

The Incident Activity Report lists the users who have logged in to a specific incident, their position, their
last successful login date/time, and their last logout date/time. This report generates in PDF or CSV
(comma-separated values) formats and can assist you in managing access to incidents.
Note: Only users with access to the Incidents Manager can view this report.
To view the Incident Activity Report:
2. In the Active Incidents window, click the incident for the report.
57
Incidents
3. Click Actions, then click one of the following options:
Incident Activity Report - View to open the report in a new window. Opening the report in a
Incident Activity Report - Export CSV to export it to a CSV file.
Viewing the Incidents Report

The Incidents Report lists each active incident's name and start date and time, and indicates whether it is
mapped to a regional incident.
Note: Regional incidents are only applicable when connecting to other WebEOC systems using WebEOC
Fusion.
This report generates in PDF or CSV (comma-separated values) formats.
Note: Only users with access to the Incidents Manager can view this report.
To view the Incidents Report:
58
Administrator Guide
2. In the Active Incidents window, click the Actions button, then click one of the following options:
Incidents Report - View to open the report in a new window. Opening the report in a new
Incidents Report - Export CSV to export it to a CSV (comma-separated value) file.
Running an Incident Report

To run a report on an incident:
2. Click Run Report next to the desired incident.
3. To include boards in the report, click Add Board.

4. Select one or more boards in the list, then click Add.
59
Incidents
Tip: To select all the boards, select the select all check box in the Name column heading.
Note: Only the selected boards that contain data appear in the report.
5. Click Run. The report opens in a new window.
Note: If no data displays in the report, no data exists in the selected boards.
6. Click Print PDF to generate a hardcopy.
The Archives Manager

The Archives Manager allows you to store, query, and view archived incident data. When archived data is
retrieved, board and plugin data are viewed in their original display format.
Note: You will find the Archives option under the Incidents tab only if you have archived incidents from
previous releases.
Refer to The Incidents Manager for detailed instructions on archiving an incident.

Archived board data can be turned into a simulation. This feature provides the following capabilities.
An archived incident can be replayed as though it were occurring in real-time. This valuable tool
can aid in post-incident critique and evaluation activities.
60
Administrator Guide
Once simulated, an incident can be added to an organizations suite of exercise scenarios for
training and evaluation purposes. You can also edit and run it using the Simulator Manager.
When the archived incident is simulated, board data is automatically imported and added to the list of
simulations in the Simulations Manager.
Note: MapTac, File Library, and NWS Alerts plugins are not saved when an incident is archived. You
should consider generating hard copies as necessary to meet record retention requirements for this
specific information.
Viewing an Archived Incident

Archived data can be viewed through two admin managers: Archives and Reporter.
If you want to view status board information in its original format, use the Archives Manager.
When using the Reporter Manager, you must create a custom report.
Use this manager when you need greater filtering capabilities than are present in the Archives Manager,
must sort archived data, or want the information presented in a report format. Refer to The Reporter
Manager for detailed instructions.
Note: The date displayed in the Archives window is the date that was configured when the incident was
added to the Incidents Manager.
Viewing Board Data for an Archived Incident

To view board data for an archived incident:
1. In the Admin window, click the Incidents tab, then click Archives.
2. Click the name of the archived incident that you want to view.
3. To query and display historical data for a board, click the name of the board from the Boards list.
4. In the Select Archived View window, click View in the drop-down list, then click Next.
5. In the Archived Board window, enter your search criteria.
In regard to search criteria:
61
The more criteria you enter, the narrower your search and results.
To view all data, leave all query fields blank.
Partial searches can be performed on a field.
Incidents
You can use the following formats when including date and/or time criteria in the search:
US Date formats: mm/dd/yyyy (for example, 05/27/2014) or [Month] [Day], [Year] (for example,
May 27, 2014)
International Date formats: yyyy/mm/dd (for example, 2014/05/27) or [Year] [Month] [Day], (for
example, 2014 May 27)
Time formats: hh:mm:ss (for example, 21:35) or hh:mm:ss AM/PM (for example, 8:00:15 AM,
8:00:15 PM)
Note: You can use 12- or 24-hour time format. You can enter AM/PM designation as lower or
upper case.
6. Click the Query button to execute the search. Data matching the criteria specified in the query
opens in a separate window; it appears in the original view format for the board or plugin.
Viewing Plugin Data for an Archived Incident

Archived plugin data can only be viewed for the Checklists and Messages plugins.
To view plugin data for an archived incident:
2. Click the name of the archived incident that you want to view.
3. Click Checklists or Messages in the Plugins section.
4. If you chose Checklists, open Checklists and click the list you want. It appears in the Checklists
window.
5. If you chose Messages, all of the messages for the archived incident appear in the Messages
window.
6. To generate a hardcopy, right-click in the display window and use the print option in your browser.
Note: You can print complex boards or extensive data sets using the Reporter Manager, specifying,
filtering, and sorting the data fields.
Simulating an Archive
When an archive has been simulated, it is possible that boards and field data may not transfer intact. This
error can occur when a board has since been deleted from the system or field names in a board have
62
Administrator Guide
been changed or deleted. For detailed instructions on running a simulation, refer to The Simulator
Manager topic.
To simulate an archive:
2. Click the create simulation icon
next to the name of the incident.

4. In the Incidents tab, click Simulator to confirm that the simulation was created in the Simulator
Manager.
The newly created simulation has the same name as the archived incident and is appended with
(Imported). The simulation can now be edited as required.
Deleting an Archive
Deleting an archive permanently removes the incident and all associated information from the system.
To delete an archive:
next to the name of the archived incident you want to delete.
3. In the delete confirmation window, click OK.
The Master Views Manager

In WebEOC, organizations can track individual incidents or combine multiple incidents in a common
master view. Once configured by an administrator in the Master Views Manager, a user logged in to the
master view can view the data from all sub-incidents together, or can filter the information to a single
63
Incidents
incident, as needed. The ability to view the master view, along with its sub-incidents, is available only to
those users with the appropriate group permissions for each incident that makes up the master view.
The option to track multiple incidents simultaneously yet separately, or rolled up into master views, means
that a local EOC can track their own ongoing emergency while a district EOC combines several local
incidents into a master view. At the same time, the State EOC could have a master view of all regional
incidents. Each tiers information can have a different level of detail based on the information
requirements for each organization.
Users select which incident or master view to participate in when logging in to WebEOC. Master views
are not themselves incidents; instead they are a view of information from selected incidents.
Logging in to a Master View

Master views and assigned sub-incidents are easily identified when logging in to WebEOC. Following are
details about accessing master views:
Master views and incidents that have not been assigned to a master view appear left-justified in
the Incident drop-down list in the Login window.
64
Administrator Guide
Sub-incidents assigned to master views are grouped together immediately under the master view
in the Incident list. They are preceded by three short dashes.
If an incident is assigned to more than one master view, it appears under each master view to
which it is assigned.
A master view with no assigned sub-incidents does not appear in the Login window.
Creating a Master View

To create a new master view:
1. In the Admin window, click the Incidents tab, then click Master Views.
2. In the Master Views window, click the Create Master View button.
3. Enter a Name for the master view. This is a required field.
4. The Date is automatically set to the current date and time. If you want to change the date, delete the
text and enter a new date, formatted: mm/dd/yyyy hh:mm:ss (month, day, year, hour, minutes, and
seconds).
Note: The format is based on the locale settings for international compatibility.
65
Incidents
5. In the Incidents section, click Add Incident and click the incidents from the Incidents list that you
want to assign to the master view. Any changes you make to incident assignments in the Master
Views Manager automatically update in the Incidents Manager.
Tip: To select all the incidents, select the select all check box in the Name column heading.
6. Click Add.
7. Click Save.
Editing a Master View

To edit a master view, follow the steps below.
2. Click the name of the master view you want to edit.
3. Make your changes in the Edit Master View window.
4. Click Save.
Deleting a Master View

Deleting a master view does not delete the incidents associated with it.
66
Administrator Guide
To delete a master view:
next to the name of the master view to be deleted.
Managing a Master View

When status board entries from multiple incidents are viewed collectively in a master view, a filter appears
in the upper left corner of each board using the <incidentname/> tag.
To display entries for an individual incident in the master view, select the incident from the filter dropdown list. The board refreshes and displays only the entries related to the selected incident.
Note: You can design or modify a board to display the name of the incident next to each entry. In the
Board Editor, include the system field named Incident in the board view. A board configured in this
fashion and displayed through a master view enables users to easily relate each entry to its respective
incident. Refer to Boards Manager for information on modifying boards.
Information is entered, updated, and managed from a master view in much the same way as users do
when logged into an individual incident. Like board master views, the input view contains an Incident
drop-down list. Select the incident from the drop-down list and complete the data or settings. Information
is posted and recorded to the incident you select from the list.
67
Incidents
When updating board entries in a master view, the Incident drop-down list does not appear in the input
view. The incident is determined when the entry is initially entered.
The Reporter Manager

In addition to real-time access to emergency information, WebEOC provides extensive data retrieval and
reporting capabilities. Agencies can generate an unlimited number of preformatted or ad hoc reports
based on individual status boards. Preformatted reports can be added as a link to the control panel.
Use the Reporter Manager when:
You want the information presented in a report format.
You want to display all updates to records in a status board.
You need to sort archived data.
Note: Archiving is only available in previous releases of WebEOC.

An unlimited number of user-defined reports can be developed for both default and customized status
boards.
Two types of board reports are available:
The Standard Report is built using standard Reporter Manager tools.
The Custom Report is built using HTML and can be developed in an external editor, such as
Adobe Dreamweaver, and then pasted into the Reporter Manager.
You can generate a multi-board incident report through the Incidents Manager.
68
Administrator Guide
Creating a Standard Board Report

When creating a standard board report, you can decide whether all updates are included. If you select
Yes in the Show Updates drop-down list, the report includes all updates that have been made to an
entry. If you select No, the report includes only the last update made to an entry.
The list of Available Fields is based on the board specified for the report. Sorting using fields that have
been configured as a [TEXTAREA] in the Boards Manager are not supported and, if configured, are not
executed.
To create a standard board report:
1. In the Admin window, click the Incidents tab, then click Reporter.
2. Click Create Report.

3. Enter a name for the report in the Name field. This field is required.
69
Incidents
4. Click the Board/Table in the drop-down list. This field is required.
5. In the Show Updates drop-down list, click either Yes or No.
6. In the Custom drop-down list, click No.
7. Click Next. The Report window opens, where you can add the data fields to include in the report.
8. Click the Available Fields drop-down list and click a field.
Note: The Available Fields list is populated from the board you selected in the previous window.
9. Click the add icon
to add the field to the list. Repeat this step if you want to add more fields to the
list.
Tip: To remove a field from the list, select the field, then click the remove icon
10. Repeat steps 8-9 for each data field you want included in the report.
11. If appropriate, change the order of the fields by clicking a field, then clicking the Up or
Down arrows.
70
Administrator Guide
12. When you have finished selecting and ordering the data fields, click Next. The Sort section enables
you to establish the parameters on which entries are sorted and appear in the report.
Tip: You can configure single or multiple parameters for the sort protocol.
13. In the Available Fields drop-down list, click the field.
Note: If this is an existing report and the board/board table was changed, you must remove and/or
add data fields corresponding to the currently selected board.
14. Click either ASC for ascending or DESC for descending in the drop-down list.
list.
16. Repeat steps 13-15 for each rule added. As each rule is configured, it is added to the Displayed
Fields pane.
17. Click Next. The Filter window opens, where you can create a single query using one or more criteria
to filter board entries included in the final report. The last filter configuration for an existing report
appears in the Filter window.
18. Open the Boolean drop-down list and click AND or OR.
Note: See the Query Options topic for Boolean descriptions.
71
Incidents
19. Open Field and click the appropriate field.
Note: If this is an existing report, and the board/board table was changed, you must remove and/or
add the corresponding data fields to the currently selected board.
20. Click one of the following in the Operation list: =, <, >, <>, or LIKE.
21. Enter a value in the Value field and click the add icon
. The query appears in the Criteria pane.
22. To configure multiple filter parameters, repeat steps 18 - 21.

Tip: If you do not specify a Boolean operator, AND is automatically appended to the second and
subsequent parameters.
Tip: To delete a filter parameter, select it in the Criteria pane and click the remove icon
23. When you are done, click Finish.

24. To create a link for the report, click Create Link next to the report in the Reports window.
The link appears in the Links Manager.
72
Administrator Guide
After you create the report, if you want users to be able to access it, add the report link to the appropriate
group or menu, as applicable.
Query Options
If all board entries are to be included in the report, leave the Criteria pane blank. You can configure a
combination of criteria using simple query statements. Queries are constructed based on the parameters
(Boolean and Operation) selected.
The following table describes each query parameter:
Symbol
AND
OR
LIKE
=
<
>
<>
73
Query Option
AND is used in multi-query statements to specify that entries must meet all parameters
linked by AND in order to be included in the report.
OR is used in multi-query statements to specify that entries meeting any parameter
linked by OR are to be included in the report.
Result includes matches containing the parameter entered in the Value field. This is
comparable to a contains query. The wildcard (%) can be used with a LIKE query.
Result includes entries that exactly match the parameter entered in the Value field.
Result includes matches that are less than the parameter entered in the Value field
(numerically or alphabetically).
Result includes matches that are greater than the parameter entered in the Value field
Result excludes those entries matching the parameter entered in the Value field.
Incidents
Running a Board Report

To run a report using the Reporter Manager:
2. Click Run Report next to the report you want to generate.

3. If you are running a report for:
An archived incident, the system automatically generates and displays the report in a report
preview window. Skip to step 7.
Note: Archiving is only available in systems updated from previous releases of WebEOC.
All other incidents, continue to step 4.
4. In the Run Report window, select either Active or Inactive for the type of incident.
5. Click the incident in the Incident drop-down list.
6. Click Run.
7. When the report opens, you can print it by clicking the Print PDF link.
Adding a Custom (HTML) Report

Custom board reports developed in an external HTML editor or WebEOCs board builder can be imported
directly into the Reporter Manager. The Reporter Manager employs HTML tags and several special tags
to display data. A user must know HTML standards to fully understand the functionality of the special
HTML tags supported for the Reporter Manager. Refer to Supported HTML Tags for Input Views for more
information on tags.
74
Administrator Guide
You can decide whether all updates are included in the report. If you click Yes in the Show Updates field,
the report includes all updates that have been made to an entry. If you click No, the report includes only
the last update made to an entry.
The list of Available Fields is based on the board specified for the report. Sort criteria using fields that
have been configured as a [TEXTAREA] in the boards manager are not supported and, if configured, are
not executed.
To add a custom report:
2. Click Create Report.
3. Enter a name for the report in the Report Name field. This field is required.
4. Click the Board/Table in the drop-down list. This field is required.
5. In the Show Updates drop-down list, click either Yes or No.
6. In the Custom drop-down list, click Yes.
7. Click Next.
75
Incidents
8. Enter or cut-and-paste the HTML into the field, then click Next.
9. Open the Available Fields drop-down list and click a field.

Note: The Available Fields list is populated from the board you selected in the previous window.
list.
Tip: To remove a field from the list, click the field, then click the remove icon
11. If appropriate, change the order the fields by clicking a field, then clicking the Up or Down arrows.
12. When you have finished selecting and ordering the data fields, click Next. The Sort section enables
you to establish the parameters on which entries are sorted and appear in the report.
76
Administrator Guide
Tip: You can configure single or multiple parameters for the sort protocol.
13. In the Available Fields drop-down list, click the field.

Note: If this is an existing report and the board/board table was changed, you must remove and/or
add data fields corresponding to the currently selected board.
14. Click either ASC for ascending or DESC for descending from the drop-down list.
list.
16. Repeat steps 13-15 for each rule added. As each rule is configured, it is added to the Displayed
Fields pane.
17. Click Next. The Filter window opens, where you can create a single query using one or more criteria
to filter board entries included in the final report. The last filter configuration for an existing report
appears in the Filter window.
18. Open the Boolean drop-down list and click AND or OR.
Note: See the Query Options topic for Boolean descriptions.
77
Incidents
19. Open Field and click the appropriate field.
Note: If this is an existing report, and the board/board table was changed, you must remove and/or
add the corresponding data fields to the currently selected board.
20. Click one of the following in the Operation list: =, <, >, <>, or LIKE.
21. Enter a value in the Value field and click the add icon
. The query appears in the Criteria pane.
22. To configure multiple filter parameters, repeat steps 18 - 21.

Tip: If you do not specify a Boolean operator, AND is automatically appended to the second and
subsequent parameters.
Tip: To delete a filter parameter, click it in the Criteria pane and click the remove icon
23. When you are done, click Finish.
78
Administrator Guide
24. To create a link for the report, click Create Link next to the report in the Reports window.
The link appears in the Links Manager.
After you create the report, if you want users to be able to access it, add the report link to the appropriate
group or menu, as applicable.
Deleting a Board Report

To delete a board report:
79
Incidents
next to the report you want to delete.

Note: After you have deleted a report in the Reporter Manager, you must delete the report from the Links
Manager (if a link was created). Refer to The Links Manager for more information.
The Simulator Manager

Simulator is a tool organizations can use to construct scenarios that can be added to WebEOC and run
as needed for initial and recurring training, drills, and exercises. It can simulate inputs that would normally
be generated by an entire team of emergency responders, while minimizing the number of support
personnel needed for role-play activities.
With the Simulator Manager, authorized users can:
Develop system-generated inputs that are automatically injected at specified intervals based on
ETime.
Develop contingency inputs for which ETimes cannot be determined but may be input later as the
exercise unfolds.
Modify scenario inputs, if the edit occurs before the item appears on the designated status board.
Disable an entry from being posted.
Delay inject of a scheduled entry.
Selectively remove entries already posted to status boards.
Pause the simulation, as required, and then restart when the training, drill, or exercise resumes.
Import and/or export simulation data in XML-formatted text files.

80
Administrator Guide
Generate hard copies of the timeline and injects.
ETimes.
Offset days and times.
ETimes
ETimes are calculated based on the elapsed Simulator run-time. ETimes are calculated and entered into
the Simulations Manager in hours, minutes, and seconds. Before creating a simulation, users may want
to draft board entries or inject numbers and ETimes to be used in the scenario. If developed in an
external application, scenario designers can cut-and-paste entry details from the external file while editing
the simulation.
Offset Day and Time

Simulated entries can display either the actual date and time posted or an offset date and time. Offset
days and minutes can be entered as positive values that are added to the post date and time or negative
values that are subtracted from the post date and time.
To specify the actual post date and time, leave the date and time fields blank. When the ETime for the
entry is reached, Simulator posts the entry and the current date and time appear on the board. For
example, an entry is added to a simulation with an ETime of 00:15:00 (15 minutes) and the date and time
fields are blank. Simulator is started at 10:00 hours on 05/12/2007. At E + 15 minutes (that is, 15 minutes
has elapsed), the entry is posted to the board with a post date of 05/12/2007 and post time of 10:15.
Entries whose date and time are not the same as the current date and time are configured with an offset
value in plus (+) or minus (-) days and/or minutes. These values are added to or subtracted from the
calculated ETime. For example, a simulated entry posts at E + 2 hours (02:00:00), but the time displayed
on the board should reflect an entry time of one hour (60 minutes) earlier than the current time.
When configuring this type of entry, enter an ETime of 02:00:00 (two hours). To offset the date and time,
leave the date blank and set the time at -60 minutes. When you leave the date blank, the current date is
used. Simulator is started at 09:32 on 5/12/2004. When the ETime 02:00:00 is reached (at 11:32), the
entry is posted to the designated board with a date of 05/12/2004 (the current date) and a time of 10:32
(the current time minus 60 minutes offset time).
81
Incidents
Creating a Simulation
To create a new simulation:
1. In the Admin window, click the Incidents tab, then click Simulator.
2. Click Create Simulation.

3. Enter a name for the simulation in the Name field. This field is required.
4. Click Save.
5. Click the board name in the drop-down list, and click the Add button to add an inject to that board.
82
Administrator Guide
6. In the Simulation Event window, indicate the time using one of the following methods:
Enter the ETime using the format hh:mm:ss (for example, 01:15:30).
If the entry is to be manually injected at an indeterminate time, maintain the default ETime of
00:00:00.
Tip: It is not necessary to enter a leading zero for single digit entries.
Note: The ETime is the amount of time that is expected to lapse from the Simulator start time to
the time the entry is auto-posted to the status board. When the ETime for the entry is reached,
Simulator posts the entry and the current date and time appear on the board.
7. Enter an Inject # (identifier), if applicable.
8. If appropriate, enter a short summary in the Synopsis field.
Note: This synopsis, in conjunction with an Inject # (if applicable), appears in the Events list in
both the Edit Simulation and Simulation Run windows. These two pieces of information can
facilitate locating a specific entry in the Simulation Run window.
9. Open the User drop-down list and click the appropriate option.
10. Open the Position drop-down list and click the appropriate option.
Note: Some boards contain date and time fields. These fields have [Offset Days] or [Offset
Hours] next to them.
11. If the board you are configuring does not include an offset day or time, skip to step 12.
Otherwise, configure the offsets:
a. Enter a positive or negative number in each appropriate field marked [Offset Days].
83
Incidents
b. Enter a positive or negative number in each appropriate field marked [Offset Hours].
Note: For more information on offsets, refer to The Simulator Manager: Offset Day and Time.
12. Complete the remaining data fields in the Simulation Event window as applicable.
Note: Since each board contains a unique set of data field, the list of data fields varies.
13. Click Save.
14. For each additional inject to your simulation, repeat steps 5 -13.
15. After you have added all of the injects to the boards selected for your simulation, click Save.
Editing an Existing Simulation

To edit an existing simulation:
2. In the Simulator window, click the name of the simulation you want to edit.
84
Administrator Guide
3. In the Edit Simulation window, click the name of the inject that you want to edit.
4. In the Edit Simulation window, edit the data fields that need to be revised.
5. Click Save.
6. For each subsequent inject that needs editing, repeat steps 3 - 5.
7. To add more injects to your simulation, click the board name in the drop-down list.
8. Click Add.
9. In the Edit Simulation window, enter the data in the appropriate fields.
Note: For more information on offsets, refer to The Simulator Manager: Offset Day and Time.
10. Click Save.
85
Incidents
Deleting a Simulation
To delete a simulation:
2. Select the trash can icon
next to the simulation you want to delete.
Printing a Simulation
To print a simulation:
2. In the Simulator window, click the name of the simulation you want to print.
3. In the Edit Simulation window, click Print. The simulation details appear in a new window.
4. Right-click in the window and use your browser options to print the simulation.
86
Administrator Guide
Running a Simulation
You cannot use the Setup incident feature to run a simulation. Instead, log in to an incident created for
the drill or exercise before starting Simulator. Users, groups, and positions are assigned in the same way
as for an actual incident.
To run a simulation:
2. Click Run Simulation next to the simulation you want to run.

The simulation control window uses DVD-like controls, complete with buttons and digital elapsed time
display. The buttons on the control are, from left to right: Rewind, Pause, Reset, Play, and Forward.
The Rewind button sets the Simulator clock back to one second before the last ETime and
removes the entries matching that ETime from the related boards.
87
The Pause button stops the clock without setting it to zero.
Incidents
The Reset button stops the simulation, resets the clock to 00:00:00, and removes all entries that
have been posted up to that point.
If you click reset, the Reset the Simulation window appears advising you that this action
removes all posted entries from status boards. Click the OK button to reset the clock and
remove posted entries.
Note: Entries with 00:00:00 ETimes that were manually injected must be individually removed by
clicking the Enable button.
The Play button starts the clock.
The Fast Forward button advances the clock to the next scheduled ETime and posts the entry or
entries configured with the specified ETime.
Configured entries for the simulation are displayed in the list box and are ordered by ETime.
Entries with ETimes of 00:00:00 do not auto-post to their respective boards. The administrator
running the simulator must manually inject these entries by clicking the Add button next to them.
Tip: Contingency messages and injects with indeterminate post times are excellent candidates for
00:00:00 ETime configuration.
Each line entry displays the ETime, Inject #, Board name, Synopsis, and two action buttons
with the default settings of Add (or Remove) and Disable (or Enable).
Button settings associated with each entry line indicate the operation that is applied to the entry
when the button is next clicked. As button settings are changed, the entry status and display color
(white, blue, or red) corresponding to that entry also change. If the Add and Disable buttons are
available, the entry may be injected (either manually or automatically) or disabled (unavailable for
posting). When the Add button is clicked or the entry is automatically posted, the Remove button
is made available and the Disable button is made unavailable. When the Disable button is
clicked, the Enable button is made available and the Add button is made unavailable.
When the simulation is initially loaded, all line entries are displayed in white. The default button
settings of Add and Disable indicate they are available for posting (that is, they have not been
injected). As the simulator runs and ETimes are reached, or as entries are manually injected,
individual entry lines change colors and the associated buttons change, indicating actions that
can be taken.
88
Administrator Guide
Before posting to a status board, users can modify associated details through the Edit Simulation
window. After a post has been uploaded to its status board, entry updates can only be
accomplished through the input view.
For the user, entries can be added, updated, sorted, and filtered as any other entry.
Do not data-link entries posted through the Simulator Manager. This can cause unpredictable
results when posts are removed from a board.
The simulation automatically pauses once all non-zero ETimes for the simulation have occurred.
At the conclusion of the simulation, event information can be archived intact with all injects, as
well as entries posted by players, or deleted per your organizations policies and procedures.
Note: To save all the posted entries with the injects, close the Simulation Run window by clicking
the red X in the upper right hand corner. Do not use the Control Reset button. The reset button
removes all the posted entries from the status boards.
Exporting a Simulation
You can export a simulation and share it with other agencies.
To export a simulation:
2. Click Export Simulation next to the simulation you want to export.

3. Open or save the file, as appropriate.
Importing a Simulation
You can share simulations among WebEOC agencies. It is possible that boards and field data may not
import intact. This could occur if the board does not exist in your system, or if the imported board data
fields are not the same as the board in your system.
89
Incidents
To import a simulation:
2. Click Actions, then Import.
3. Click the Choose File button.

4. Locate and select the file you want to upload and click Open.
Tip: The file should have a SIM file extension (for example, HazMat Spill.sim).
5. Click the Import button to upload the file to the Simulator window. The simulation and the date and
time it was imported are added to the list and appended with (Imported).
90
Processes
This section describes how to manage processes within the system.
The Boards Manager

A status board is a display used to transmit and share crisis information in real-time. Although pre-built
status boards are included in WebEOC, the Boards Manager allows you to create status boards, modify
existing status boards, and delete boards that are no longer needed.
Using the Board Editor, administrators can:
Create, add, and customize input and display views
Set up data linking between boards
Add email functionality to a board
Add IMX Connect mobile app functionality to a board
Set control panel notifications when data is added to a board
Configure status board display filters
Perform HTML editing
91
Processes
Board designers with advanced knowledge of HTML and WebEOC conventions can customize boards to
meet the specific requirements of their organization. WebEOC has a built-in HTML editor that features
line numbers, syntax highlighting, formatting, and contextual auto-complete functionality. HTML can also
be developed in an external HTML editing tool and added to WebEOC using the Board Editor. See HTML
Options for more information.
Planning a Status Board

Before building a status board in WebEOC, you may want to sketch a design of the layout on paper or a
whiteboard. Consider the following points before creating or modifying a board.
Whats the purpose of the board?
What should be the name of the board?
What type of board (standard, tasking, resource tracking, etc.) am I creating?
What information will be recorded on the board?
What fields will be needed to capture data? What should I name and label the fields? What types
of fields will I need (i.e., system field or custom field, text, drop-down list, etc.)? Are any of the
fields required to be completed before posting a record to its status board? If so, which ones?
If a list is necessary, does it currently exist? If not, the list must be built.
Is a header row or a footer row required?
Is the board add only, or will users be allowed to update?
What options will be applicable to this board?

Will user editing and/or viewing privileges be restricted?
Will filters be helpful with viewing restrictions?
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?
After requirements for the board have been identified, you should be ready to begin building the board.
92
Administrator Guide
HTML Options
Designers with advanced knowledge of HTML and WebEOC conventions can customize boards to meet
the specific requirements of their organization. WebEOC has a built-in HTML editor that features line
numbers, syntax highlighting, formatting, and contextual auto-complete functions.
The HTML editor in the Board Editor provides the following capabilities and features:
Add HTML developed in an external HTML editing tool to WebEOC using the HTML editor.
Edit HTML directly in the HTML editor.
Switch between Design View, Advanced Code Editor, and Plain Code Editor displays.
Change the name and table used for a view.
Open multiple input views, display views, and tables and use the tab feature at the top of the Edit
View window to quickly switch between the views you have open and the complete list of board
views.
Search for text within the code in either the Advanced Code Editor or Plain Code Editor. You
can open the Find window by pressing CTRL+F. Enter your search text and then use the
Previous and Next options to scroll through the search matches.
You can use the CTRL+S keyboard shortcut to save your work in either the Advanced Code
Editor or Plain Code Editor.
93
Processes
Table Options
Form
Select the Form check box to allow the board to behave like a form. This enables the update-only
function. A form-like board displays only the last update made to the board per incident. The ICS and ESF
Situation Reports that come standard with WebEOC are examples of form boards. All updates to a form
board are saved in the database for auditing purposes.
Note: Use of this option in conjunction with others, such as Global, means that there might be more than
one entry per incident, but only one entry is displayed at a time.
Static
Select the Static check box if this status board will be used to store pre-canned information that is
automatically posted and used in all incidents.
For example, an agency that routinely completes a set of tasks for any incident can configure the status
board as Static, add the commitments to the specified status board through Setup, and have the
precanned entries automatically copied to the board. Static entries can be updated and processed as in
any other board entry.
A Delete button is enabled in the input view for authorized users logged in to Setup. They can remove
unwanted precanned entries by displaying the data item in the input view for the board, and clicking
Delete.
Note: Entries added to Static status boards through the Setup incident are automatically duplicated
(posted) in those boards for each subsequently created incident. Once the board has been built, the
administrator can log in using Setup and add the pre-canned data items to the static board.
94
Administrator Guide
Incident Independent
Select the Incident Independent check box anytime the data entered to the status board is more
permanent than the incident itself. This option allows data to remain in the board even after the
associated incident is archived.
A scenario where the incident-independent feature is useful is the Shelters board, which tracks status and
related details on an ongoing basis. When configured as Incident Independent, all data entered across
all incidents continues to be maintained in the board when an incident is archived.
Searchable
The Searchable check box is selected by default, enabling data on this board to be included in search
results when using the WebEOC Search Tool. The Searchable column in the Boards list window shows
which boards have this option enabled or disabled.
Edit Board Overview

Read the following sections to learn about the following:
Include feature
Plugins
Board editor tools, including board and data import and export
HTML Options to learn about using the HTML editors to create a board
Refer to the Data Manager section in this topic if you use:

WebEOC Enterprise, or
WebEOC Professional and have a Data Manager license.
Include
The Include section provides a list of plugins or interfaces installed on the WebEOC server that can be
integrated into a status board by incorporating specialized fields into the design of the board. Refer to the
plugin or interface documentation for detailed instructions to implement this specialized functionality.
95
Processes
Plugins
The Plugins section provides a list of WebEOC plugins that allow you to build boards that integrate with
the plugin fields and data. Refer to the plugin documentation for detailed instructions for implementing this
specialized functionality.
Tools
Board Editor
The Board Editor provides all the tools needed for creating and editing input and display views and
adding enhanced functionality to a status board. The editor also allows you to directly edit the HTML for a
board and make changes to board tables when needed.
Edit Data Links
Data can be pushed from one status board to other boards by establishing data links and properly
mapping the boards' fields. One-way and two-way data linking can be established. This will only be
enabled from the Edit Board window when a single input view exists.
Import and Export Boards
You can import new boards into WebEOC or export board files for sharing using the Import/Export Board
features.
Notes: The system supports importing and exporting data links that are internal to the board as well as
those that are external to other boards. Both the system export and import of a board must be done on
WebEOC 7.7 or later.
Advanced filtering using groups is only supported when boards are published over WebEOC Fusion and
both the publisher and the subscribers are on WebEOC 7.7 or later.
WebEOC 8.0 uses a new CSS when creating new board views. This CSS is only supported for boards
published over WebEOC Fusion when both the publisher and the subscribers are on WebEOC 8.0 or
later.
Import and Export Data
You can import and export board data using the Import/Export Data functions.
Note: More advanced board data import and export functions are available if you are a WebEOC
Enterprise (7.7 or later) administrator or are using WebEOC Professional (7.7 or later) and have a license
for the Data Manager add-on. See Board Data for more information.
96
Administrator Guide
Individual Board Assignment Report
The Individual Board Assignment report contains data for a specific board. You can view the report in
PDF format, or export it in CVS (comma-separated value) format. You can save or print the PDF file. Only
users with access to the Boards Manager can access this report. Refer to the Viewing the Individual
Board Assignment Report topic for additional information.
Manage Resources
Use the Manage Resources feature to upload files that can be referenced within status boards; those files
are exported and imported with the board.
For example, if you have a logo or custom function in your board, those files can be stored here. When
you export a board to share it, the logo and custom function are exported with the board file.
Data Manager
For WebEOC Enterprise clients, advanced Data Manager functions are fully integrated with WebEOC and
available in version 7.7 or later. These enhanced features replace previous versions of data management
functions, such as importing and exporting board data.
These advanced Data Manager functions are also available to WebEOC Professional clients as an addon.
All other WebEOC clients continue to have access to the administrator data import and export features
that existed prior to version 7.7.
This section provides an overview of the Data Manager functions that are available with WebEOC 7.7.
For more information and detailed instructions on using these advanced features, refer to the Board Data
Manager Administration quick reference guide.
Parent and Child Data
Data Manager allows you to import and export both parent and child data. These processes recognize
and retain the relationships between parent and child data in different tables.
Import
An import template is available for each board from its Import/Export Board Data page. If a board has
more than one table, the template contains a worksheet for each.
97
Processes
Note: You can import data from a comma-separated value (extension .csv) or Microsoft Excel (extension
.xlsx) spreadsheet.
During the import process, the system attempts to match fields in the import file with fields in the
associated board table. The Import Map page allows you to see how the system mapped the fields. You
can accept this mapping or change it. You can also map fields that were not automatically mapped.
The Import Map page shows sample records from the import file. It provides enough data to ascertain
how fields are mapped so that you can make any appropriate changes.
The Import Map page also includes the following options:
Option
Table Name
Description
Select the table you want to map the input fields to.
For boards with only one table, you do not need to make a selection.
Select the field by which you want to match records in the import file with
those that exist in your system. If you select an option, the import process
attempts to match a record in the import file with a record in your system.
Unique Fields
Important: If a match exists, the system overwrites the existing data with the
data from the import file.
If a match does not exist, the data is added as a new record. This allows you
to use a single import file to both add and update records.
Select this check box when you know that some drop-down fields (columns)
Automatically
contain values that are not already defined in your system lists. When
Create Missing
selected, the system automatically adds these values to the field's list of valid
List Items
values. If you do not select this check box, any new values will not be retained
once the record is saved.
The Import Preview page shows all records in the import file.
This page also indicates when a field or record is not valid. For example, if alphabetic characters appear
in a field that is restricted to numbers, a warning icon appears in both the tab header and record row.
You can cancel the process, correct the issue, and retry the import, or simply proceed. Records
containing invalid data are not imported.
Export
When you export a board's data, the export file contains a worksheet for each table in the board.
98
Administrator Guide
Creating a New Board

To create a board:
1. In the Admin window, click the Process tab, then click Boards.
2. Click Create Board.
3. In the Board Name field, enter a name for the board. This is a required field.
4. Click Save. The Edit Board window opens.
99
Processes
5. Click Board Editor in the Edit section.
6. Click one of the following view links:
Click Create Input View in the Input Views section to create an input view. See Adding and
Editing an Input View.
Click Create Display View in the Display Views section to create a display view. See Adding and
Editing a Display View.
7. In the Settings section, select the settings for the view:
See Selecting Input View Settings for a detailed procedure for this step.
See Selecting Display View Settings for a detailed procedure for this step.
8. Click Save.
Deleting a Board
Before deleting a board, ensure that the data will no longer be needed. You may want to consider
exporting a copy of both the board file and the board data.
To delete a board:
2. In the Boards window, click the trash can icon
next to the board you want to delete.

100
Administrator Guide
About Views
In WebEOC, users enter information that is viewed in a pre-defined format. Users input information
through a data entry window. The resulting output is displayed in the view.
In the Boards Manager, the terms input view and display view simply mean the data entry window
(input view) and the window to view data (display view).
The ability to create multiple input and display views allows an organization to record sensitive
information while at the same time restricting unauthorized access to some or all the data entered. For
example, the input view for a Victims status board may include a field to record victim names. Two display
views are added: one view is intended for hospital use only and includes victim names, and a second
display view used by media personnel hides the sensitive information. The display view that includes
victim names would be assigned to a Hospital group, while the view that excludes victim names would be
assigned to a Media group, ensuring sensitive information is restricted on a need-to-know basis.
WebEOC allows you to create boards that have single or multiple input and display views based on a
single table or multiple tables. These tables correspond to a table in the underlying SQL Server database.
This allows an agency to record and filter sensitive information while at the same time restricting
unauthorized access. It also provides an easy method of implementing processes through WebEOC.
Input View
Following is an example of an input view.
101
Processes
Display View
Following is an example of a display view.
View History
Each time a view is saved, a version is stored and added to the list in the History section.
Each version of a view can be viewed or restored.
With each save, a copy (version) of the view is stored along with a record of the date/time,
comments, errors, and the user who modified the view.
Restoring a view makes it the current/active view and replaces the existing view code.
When a user restores a view, a new history record with an updated timestamp is created.
To access the history of a view:
2. Click the name of the appropriate board. The Edit Board window opens.
3. Click Board Editor.
4. Click a view.
5. Scroll to the bottom of the window. The View History window displays a complete list of versions of
the view.
102
Administrator Guide
To restore a version:
1. Click the date of the version in the History section.
2. Click Restore.
3. Click Save.
Creating and Editing an Input View

The Board Editor window allows you to visually design and edit data entry (input) views that users can
use to enter data.
Note: This procedure follows Creating a New Board. See Creating a New Board.
To create a board input view:
1. Click Create Input View in the Board Editor window.
2. Enter or change the input view Name.
3. Select a table from the Table drop-down list, or click Create Table to automatically generate a table.
4. In the HTML section, use the Design View editor to make changes to the view.
103
Processes
For help using the Advanced and Plain Code Editors, see HTML Options.
The Design View of the HTML section includes four components.
Cell formatting tools
Undo and Redo buttons
Field types and properties editing
Design pane. Use this pane to create the input view design, assign cell and formatting
properties, and view a visual representation of the input view.
5. In the Design View, begin constructing the input view layout by selecting one of the baseline cells
label and field and applying the Split Horizontal, Split Vertical, or Merge button. You must have a
cell selected in order to apply the operation.
a. To create a horizontal cell, select a cell and click the Split Horizontal button. to split the single
cell into two horizontal cells.
b. To create a vertical cell, select a cell and click the Split Vertical button to split the cell into two
vertical cells.
c. To merge cells into a single cell, hold down the CTRL key, click adjoining cells to form a
rectangle, and click the Merge button.
Note: Merging cells deletes some of the merged content of the selected cells as part of the
process.
6. Continue to split and merge cells until you get the layout you want.
104
Administrator Guide
Once you have the layout constructed, you are ready to assign the field type and properties to each
cell.
7. If the cell is to be used as a label in the input view:

a. Select the cell.
b. Enter a name for the label in the cell content's text field.
c. Click Apply. The label appears in the Label cell.
8. If the cell is to be used as a data field in the input view:
a. Select the cell.
b. Select the appropriate field type (for example, Text, Textarea, Dropdown, or Checkbox).
c. Select the cell with the field that was created to display additional field options.
d. Enter a unique name for the field (this will be used in the database) in the field properties
section.
Note: Ensure all field name declarations are unique so that you can easily identify them when
building your display view.
e. Define the field Size and Value, if needed.
f.
Click Apply.
Tip: It is a good practice to periodically save the view as you are working on it. Saving allows you
to revert back to a previous version at any time using the History feature.
105
Processes
g. Select the cell.
h. Click a field type, and set any additional cell properties required. The type of field selected
determines the field properties that are available.
i.
Text - Displays a single line of text. You need to set additional cell values for the text field.
ii. Textarea - Displays multiple lines of text. A scroll bar is available to view inputs that exceed
the row count set for the field. You need to set additional cell values for the Textarea field.
iii. Dropdown - Presents a selection (drop-down) list of items. You need to set additional cell
values and specify the list to be used.
iv. Checkbox - Allows a user to mark a selection or selections. You need to set the value for
the check box (for example, Yes).
9. When you have configured the cell label and field, edit the appearance by using the cell formatting
tools. You may also choose not to alter the default appearance as a standard format is already
applied.
a. Select the cell.
Tip: If you wish to apply changes to multiple cells, hold the CTRL button and select the applicable
cells.
b. To change the background color of a selected cell, click the Background Color field, enter a
hexadecimal color code or choose the color from the palette, and click Apply.
c. To change the text color of the selected cell, click the Font Color field, enter a hexadecimal
color code or choose the color from the palette, and click Apply.
d. To set the font for the text, open the Font drop-down list and click the font name.
e. To set the size for the text, open the Size drop-down list and click the point size for all selected
cells.
f.
Set the style for the text by clicking (B) Bold, (I) Italic, or (U) Underlined for the selected cell.
g. Click Left Justify, Center Justify, or Right Justify to set the text horizontal alignment.
h. Set the vertical alignment for the text in the cell by clicking Top, Middle, Bottom, or Default in
the Vertical Align drop-down list.
106
Administrator Guide
Note: The Default alignment setting relates to the alignment specified through the HTML written in
an external editor and imported to a board. The default setting in this case can be overridden by
clicking Top, Middle, or Bottom in the Board Editor window.
i.
To set the width of the cell, enter a number with a unit in the Width field, and click Apply.
Note: Valid units include the percent symbol (%), inches (in), centimeters (cm), or pixels (px).
4. Click Save.
Tip: Refer to WebEOC-specific Tags for detailed information about tags that can be added to
enhance functionality in the view.
Selecting Input View Settings

To select input view settings:
1. In the Board Editor, if it is not already selected, click the Options tab:
a. Select the Add Only check box if all entries, including updates, are to be displayed on the
status board. If the Add Only check box 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.
b. Select the Lock User Input check box to set the data entry display to one record entry for the
specified status board per user. Subsequent entries made by the user are entered as updates
through the input view for the board and only the last record entry appears.
c. Select the Lock Position Input check box to set the data entry display to one record entry for
the specified status board per position. Subsequent entries made by the position are entered as
updates through the board's input view and only the last record entry appears.
107
Processes
d. Select the Assignable check box to define whether a view can be assigned to a group. By
default, it 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 check box.
2. In the Settings section, click the Dual Commit tab to configure a board to use the Dual Commit
feature. For more information, refer to Dual Commit Target Servers.
a. Click Add Server to add servers.

3. In the Settings section, click the Notifications tab to configure notifications on status boards.
a. Select the Email check box and enter the email addresses of all recipients to whom an email is
automatically sent as each new or updated entry is posted to the board. An email server must
be configured to enable the email function. Refer to The General Manager section for detailed
instructions on setting up your email server. When configured for emails, the subject and
content are created from a status board entry. Multiple email addresses can be entered,
separated by a comma. You can also use an email distribution list.
Tip: Separate email addresses with a comma character only. Do not enter spaces in the Email text
field.
108
Administrator Guide
b. Select the Control Panel Notification check box and enter a notifications message to enable
all users who have permission to the board to receive control panel message notifications.
c. Select the IMX Connect Enabled check box to send messages to IMX Connect apps (iOS or
Android), and enter the message subject into the field on the right. This text is added to the
beginning of the message subject when the message is sent. After WebEOC users install and
configure the IMX Connect app on their devices, they can begin to receive notifications. These
push notifications are delivered to the recipients' devices even when the app is closed.
Notifications from a board can be sent to positions or groups. When you send a message, all
users in the selected position or group receive it.
d. Select the board's view from the list. Only the fields included in this view are visible to users
when they receive the push notification message or open the board from IMX Connect.
Note: Users can receive notifications from boards that do not appear on their control panel.
However, to view the board in WebEOC, the user needs permission to access the board's view.
4. Click Save.
Creating and Editing a Display View

The Board Editor window allows you to visually design and edit board display views that users can use to
view data.
To create a board display view:
1. Click Create Display View in the Board Editor window.
2. Enter or change the input view Name.
3. Click a table in the Table drop-down list.

4. In the HTML section, use the Design View editor to edit the view.
109
Processes
5.
For help using the Advanced and Plain Code Editors, see HTML Options.
The display Design View Editor window includes four primary components:
Cell formatting tools
Undo and Redo buttons
Cell types and properties editing
Design pane: Use this pane to create the display view design, assign cell and formatting
properties, and view a visual representation of the view.
110
Administrator Guide
6. In the design pane, begin constructing the display view layout by selecting one of the baseline cells
and clicking the Split Horizontal, Split Vertical, or Merge button. You must have a cell selected in
order to apply the operation.
a. To create a horizontal cell, select a cell and click the Split Horizontal button to split the single
cell into two horizontal cells.
b. To create a vertical cell, select a cell and click the Split Vertical button to split the cell into two
vertical cells.
c. To merge cells into a single cell, hold down the CTRL key, click adjoining cells to form a
rectangle, and click the Merge button.
Note: Merging cells deletes some merged content of the selected cells as part of the process.
d. Display views may be designed to use fixed header and footer rows, similar to a spreadsheet.
To increase or decrease the number of header or footer rows, use the Header Rows and
Footer Rows plus (+) and minus (-) buttons located just above the Design pane. If no header
or footer rows will be used, set the values to 0 (zero).
7. Continue to split and merge cells until you get the layout you want.
8. If the cell is to be used as a label in the display view:
a. Select the cell.
b. Enter a name for the label in the cell content's text field.
c. Click Apply. The label appears in the cell.
9. If the cell is to be used to display information in the display view:
a. Select the cell.
111
Processes
b. Select the field for which data will be displayed in the cell from the Field drop-down list.
c. Click Apply.
d. Repeat these steps for each data field.
10. When you have configured the cell label and field, edit the appearance by using the cell formatting
tools. You may also choose not to alter the default appearance as a standard format is already
applied.
a. Select the field.
b. To change the background color of a selected cell, click the Background Color field, enter a
hexadecimal color code or choose the color from the palette, and click Apply.
c. To change the text color of the selected cell, click the Font Color button, enter a hexadecimal
color code or color from the palette, and click Apply.
d. To set the font for the text, open the Font drop-down list and click the font name.
e. To set the size for the text, open the Size drop-down list and click the point size for all selected
cells.
f.
Set the style for the text by clicking (B) Bold, (I) Italic, or (U) Underlined for the selected cell.
g. Click Left Justify, Center Justify, or Right Justify to set the horizontal text alignment.
112
Administrator Guide
h. Set the vertical alignment by clicking Top, Middle, Bottom, or Default in the Vertical Align
drop-down list.
Note: The Default alignment setting relates to the alignment specified through the HTML written in
an external editor and imported to a board. The default setting in this case can be overridden by
clicking Top, Middle, or Bottom in the Board Editor window.
i.
To set the width of the cell, enter a number with a unit in the Width field, and click Apply.
Note: Valid units include the percent symbol (%), inches (in), centimeters (cm), or pixels (px).
11. Click Save.
Deleting a View
To delete a view:
1. In the Board Editor window, click the trash can icon
next to the input view you want to delete.
Selecting Display View Settings

To select display view settings:
1. In the Board Editor window, click the Options tab:
a. Select the Global check box when information posted to the view is to be displayed from all
active incidents. For example, assume the Significant Events board is configured as Global.
Anytime an EOC is managing two separate incidents (for example, Hostage Situation and
113
Processes
HazMat Spill) and data is posted to the Significant Events board, users logged into either
incident see all data related to both incidents. This setting is specific to the selected view.
b. Select the Lock User View option if you want the user to only see entries they add to that
status board, not entries added by other users.
c. Select the Lock Position View option if you want the user to only see entries added by the
position they are currently filling.
d. Select the Assignable check box to define whether a view can be assigned to a group. By
default, it is selected, which means 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 check box.
2. Click Save.
Board Filters
WebEOC allows you to build data filters so that you can filter for the exact information you want to show
in the board. Filters can range from simple to quite complex.
Applied By Default
When you indicate a filter is applied by default, the board automatically shows only those records that
meet the filter's criteria.
Note: Filters are exported and imported with the board.
Statements
114
Administrator Guide
You can use any combination of AND and OR statements in your filters. An:
AND statement filters for records that meet all stated criteria.
OR statement yields records that match at least one criterion or set of criteria.
You can add groups of criteria, and you can build a hierarchy by adding groups within groups.
Example 1:
For a simple filter, you do not need to use the groups feature.
Your filter can consist of a single criterion, or you can include several. In the latter case, you also need to
specify the relationship between the criteria by choosing ANY or ALL.
You specify that you want to see records with a high priority by adding that criterion. The criteria section
shows: priority = 'high'.
You then add that you want to see records with the status of closed. The section shows: status = 'closed'.
You choose ALL. The operand AND appears between the two criteria.
As a result, this example filters the road closures board to show only those records that have a status of
closed and are listed as high priority.
Example 2:
Using groups helps you quickly build more complex filters. In this example, you set the board to show all
road closures that have the status of closed and further filter the list to show only those that have a
priority of high or medium.
To do so, build two groups and set the relationship within each group and for the filter as a whole.
In this example:
The first group you include is an AND statement. It specifies that you want to see records that
have a status of closed AND a high priority.
The second group is also an AND statement. It filters for records that have a status of closed
AND have been assigned a medium priority.
115
Selecting ANY at the top of the hierarchy indicates an OR statement.
Processes
The filter yields records that meet the first group of criteria or the second group. With this filter applied,
your Road Closures board shows only records that have a status of Closed and that have a high or
medium priority assigned.
Note: Advanced filtering using groups is only supported when boards are published over WebEOC
Fusion and both the publisher and the subscribers are on WebEOC 7.7 or later.
Operands
The following table shows the operands that are available to you as you specify search criteria.
Operand
Query Option
in
Value must be in the list.

Result includes matches containing the parameter entered in the value field. This is
like
comparable to a "contains" query. You can use the wildcard (%) with a "like" query.
Result includes entries that exactly match the parameter entered in the value field.
Result includes matches that are less than the parameter entered in the value field
<
Result includes matches that are greater than the parameter entered in the value field
>
<>
Result excludes those entries matching the parameter entered in the value field.
Adding and Editing a Board Filter

Board filters can be configured using standard board builder tools. Filters are designed using Boolean
logic and may be selectively applied or removed through the use of buttons in the board display.
The following procedures provide instructions for:
Accessing a board's filters
Adding a filter
Editing a filter
For details on building filters, refer to Board Filters.

To access filters:
116
Administrator Guide
2. Locate the board and click its name.
3. In the Edit Board window, click Board Editor.

4. In the Board Editor window, click a display view in the Display Views section.
To add a filter:
1. In the Filters section, click Create Filter.
2. In the Edit Filter window, enter the filter's Name.

3. To turn the filter on by default, select the Applied check box.
4. Click Save. The information is saved and the Filter Criteria section opens in the page.
5. Build your filter criteria:

a. Select ANY or ALL from the drop-down list.
b. Click Add Criterion.
117
Processes
c. Select a field from the drop-down list.
d. Select an operand from the next drop-down list. The content of this list is determined by the
type configured for the field you selected.
e. Enter a value in the text box,
-orSelect the check box immediately following the operand and then select a value from the dropdown list. The content of this list is determined by the field type and operation selected.
6. If you want to add a group of criteria, click Add Group. A box opens where you can add criteria to a
group.
7. Repeat steps 5 and 6 to add criteria to this group and to add more groups.
8. Click Save.
To edit a filter:
1. In the Filters section, click the name of the filter.
2. If appropriate, change the filter's Name.
3. Select or clear the Applied check box to turn the filter on or off by default.
4. Refer to steps 5 - 6 of the add filter procedure to add criteria and groups to the filter.
5. To delete criteria, click the trash can icon
next to the criterion.
6. To delete a group, click Remove Group.

Tip: You can remove a group only after you remove all of its criteria.
7. Click Save.
118
Administrator Guide
Deleting a Board Filter

To delete a board filter:
2. Locate the board and click its name.
3. In the Edit Board window, click Board Editor.
4. In the Board Editor window, click a display view in the Display Views section.
5. In the Filters section, click the trash can icon
next to the filter you want to delete.
Importing a Board
To import a board:
2. In the Boards window, click Create Board.
119
Processes
3. Enter the name of the board in the Board Name field.
4. Click Save. In the Edit Board window, click the Import/Export Board button.
5. In the Import/Export Board window, click the Choose File button.
6. Locate the file, select it, and click Open. The File field displays the path to your file.
7. Click the Import button. The Edit Board window re-opens.
8. Make any adjustments to the options and click Save. The board you just imported appears in the
Boards window.
Exporting a Board
To export a board:
120
Administrator Guide
2. Click the board name you want to share.

3. In the Edit Board window, click the Import/Export Board button.
4. In the Export section, click the Export button.
5. Save the board to your computer. The saved board appears as a WEB (.web extension) file.
121
Processes
Data Linking
Data linking streamlines the process of posting data to multiple status boards by enabling you to send
information from one status board to another. It also ensures information integrity across multiple boards.
One-way and two-way data linking are supported in WebEOC. By default, data linking is set to One-way
Data Linking.
Data Link
Scenario
One-way
Board A is linked to Board B. Updates to data linked fields in Board A update Board
data linking
B, but updates to data-linked fields in Board B do not update in Board A.
Two-way
Board A is linked to Board B. Updates to data linked fields in Board A update Board
data linking
B, and updates to data-linked fields in Board B update the linked entry in Board A.
Changes made to a data-linked entry are replicated on each board to which that data item has been
linked.
Rules for linking data between boards are built and stored in the Board Editor utility of the Boards
Manager. A board can be linked to one or multiple boards or not linked at all.
One data link template is added for each board to which it will link. The WebEOC administrator maps the
fields in the source board to specified fields in the target boards.
For each data link template that is set up, a Data Link check box is added to the input view of the source
board.
Creating and Editing a Data Link

To add a new data link:
2. Click the appropriate board in the Boards window.
3. In the Edit Board window, click Edit Data Links.
Note: If the board has multiple input views, the Edit Data Links button is disabled (grayed out) and
data links must be managed from the input view Board Editor window.
122
Administrator Guide
4. In the Data Links window, click Create Data Link.
5. In the New Data Link window, enter the Name of the data link. This is a required field.
6. If appropriate, select the Enable 2-Way Data Linking check box.

Tip: To maintain one-way data linking for this rule, do not select this check box.
7. Click the target input view in the Destination View drop-down list.
You can map the fields in the source board to available fields in the destination view you selected. The
fields that are available to data-link from a source board to any text-type field in a destination board are
considered Field Mappings.
123
Processes
Field Mapping
Automatic
If your destination field names match the source field names, select Mapped Fields to automatically
select them.
Custom
In some cases, you may want to map a field that has a different name on the destination board than it had
on the originating board.
To map a custom field:
1. For each field in Field Mappings, select the field to which the data will be mapped.
2. If you do not want to map a field, use the default selection (None) in the drop-down list.
3. Click Save.
Deleting a Data Link

To delete a data link:
2. Click the appropriate board in the Boards window.
3. In the Edit Board window, click Edit Data Links.
Note: If the board has multiple input views, the Edit Data Links button is disabled (grayed out) and
data links must be managed from the Input View section of the Board Editor window.
4. In the Data Links window, click the trash can icon
next to the data link you want to delete.
124
Administrator Guide
Importing Board Data

Data management functions, such as importing and exporting board data, are available from the board's
Edit Board page.
Notes:
If the board has multiple tables, the Import/Export Data button is disabled (greyed out) and
importing/exporting can be accessed from the Actions drop-down list in the Tables section in the Board
Editor window.
For WebEOC Enterprise clients, advanced Data Manager functions are fully integrated with WebEOC in
version 7.7 or later. These enhanced features replace previous versions of these data management
functions. They are also available to WebEOC Professional clients as add-ons. For more information,
refer to the Board Data Manager Administration quick reference guide. All other WebEOC clients continue
to have access to the standard administrator data import and export features.
To import board data:
2. Click the name of the board where you want the data to appear.
3. In the Edit Board window, click Import/Export Data.
125
Processes
4. Click Choose File to locate the board data you want to import.
5. Click Import.
Exporting Board Data

Data management functions, such as importing and exporting board data, are available from the board's
Edit Board page.
Note: For WebEOC Enterprise clients, advanced Data Manager functions are fully integrated with
WebEOC in version 7.7 or later. These enhanced features replace previous versions of these data
management functions. They are also available to WebEOC Professional clients as add-ons. For more
information, refer to the Board Data Manager Administration quick reference guide. All other WebEOC
clients continue to have access to the standard administrator data import and export features.
126
Administrator Guide
To export board data:
2. Click the name of the appropriate board.

3. Click the Import/Export Data button in the Tools section. The Import/Export Board Data page
opens.
4. Select the appropriate format.
5. Click Export.
6. Click Save As in the File Download window.
7. Navigate to the location where you want to save the file, enter a File Name, and click Save.
Sending a Board to the Target Server

In order to share a board with another agency, you must send the board file to them. We recommend
creating a zipped file and emailing the board. It is necessary to create a zipped file because some email
servers may strip out board code they deem malicious, corrupting the board file.
After the agency receives the board, it must be unzipped and then imported on the target server. Refer to
Importing a Board for detailed instructions.
To set a board with input views to Dual Commit:
2. Click the name of the board you want to share.
127
Processes
4. In the Input Views section, click the name of the input.
5. In the Settings section, click Dual Commit.
6. Click Add Server.

7. Click the server in the Server drop-down list.
8. Select the Auto check box if you want all posts to be dual-committed by default. Leave this box
cleared if you want users to selectively decide which entries to Dual Commit.
9. Click Save.
10. Repeat steps 5-9 for each input view.
11. When you are finished, click Save.
Configuring a Board for Email

Notification-type boards can be configured to notify users outside of WebEOC. When configured for
emails, the subject and content are created from a status board entry.
An email server must be configured to enable the email function. Refer to Configuring Your SMTP
Service to Send Emails section for detailed instructions on setting up your email server.
Multiple email options can be applied to a field. For example, a single field can be part of both the
Subject and Body of the email.
To configure a board for email:
2. Click the name of the board intended for email configuration.
4. Click the name of the input view to be configured.
128
Administrator Guide
5. Scroll down and click the Notifications tab.
6. Select the Email check box.
7. Enter the email addresses of all recipients to whom an email is automatically sent as each new or
updated entry is posted to the board. Multiple email address can be entered, separated by a comma.
You can also use an email distribution list.
Tip: Separate email addresses with a comma character only. Do not enter spaces the Email text
field.
8. Click Save.
9. Click the View List tab at the top of the window.
10. Click the input view you just changed.
11. For each field to be used to enter ad hoc email addresses in the Data Entry window:
Note: Separate multiple email addresses or distribution lists with a comma.
b. Select the Recipient check box.
c. Click Apply.
12. For each field to be included in the subject line of the mail:
b. Select the Subject check box.
c. Click Apply.
129
Processes
13. For each field to be included as part of the email message:
b. Select the Message check box.
c. Click Apply.
d. Click Save.
Note: If multiple fields are configured as Subject or Message, specified fields are respectively
concatenated (combined together) to form the Subject or Message portion of the email, as applicable.
Sending Notifications
To configure notifications:
5. In the Settings section, click the Notifications tab to configure notifications on status boards.
a. Select the Email check box and enter the email addresses of all recipients to whom an email is
automatically sent as each new or updated entry is posted to the board. An email server must
be configured to enable the email function. Refer to the General Manager section for detailed
instructions on setting up your email server. When configured for emails, the subject and
130
Administrator Guide
content are created from a status board entry. Multiple email address can be entered,
separated by a comma. You can also use an email distribution list.
Tip: Separate email addresses with a comma character only. Do not enter spaces the Email text
field.
b. Select the Control Panel Notification check box and enter a notifications message to enable
all users that have permission to the board to receive a control panel message alerting them of
the change.
c. Select the IMX Connect Enabled check box to send messages to IMX Connect apps (iOS or
Android) and enter the message subject into the field on the right. This text is added to the
beginning of the message subject when the message is sent. After WebEOC users install the
IMX Connect app on their devices and log in, they begin to receive notifications. These push
notifications are delivered to the recipients' devices even when the app is closed. Notifications
from a board can be sent to positions or groups. When you send a message, all users in the
selected position or group receive it.
d. Click the board's view in the list. Only the fields included in this view are visible to users when
they receive the message or open the board from IMX Connect.
Note: Users can receive notifications from boards that do not appear on their control panel.
However, to view the board in WebEOC, the user needs permission to access the board's view.
Configuring a Board to Display Control Panel Messages

Status boards in WebEOC can be configured to generate a pop-up message on the control panel as new
entries or updates are posted. The advisory can be sent to any users currently logged into WebEOC. This
is a useful feature that can be added to select boards to alert users that a new or updated entry has been
posted. For example, this capability could be added to a mission task board to alert users of a new task.
To add the pop-up messages capability to a board:
2. Click the name of the appropriate board.
4. Click the name of the input view that you want to configure.
131
Processes
5. In the Settings section, click the Notifications tab and select the Control Panel Notification check
box.
6. In the text field, enter the message text you want to appear in the pop-up on the control panel.
7. Click Save.
8. Click the input view you just changed.
9. Configure each field that you want to designate as a Receiver of the control panel notification:
a. Select the field you want to designate as a Receiver field.
b. Select the Receiver check box.
c. Click Apply.
Note: The Receiver can be a WebEOC user. It is customary to designate a drop-down field that
contains the built-in users list so that users do not have to enter the user's name. If the pop-up
advisory is to be sent to multiple users, you must add the appropriate number of fields.
10. Configure each field that is to be included in the text portion of the Notification:
a. Select the field you want to designate as a notification field.
b. Select the Notification check box.
c. Click Apply.
Note: If multiple fields are configured as Notification, specified fields are concatenated (combined
together) to form the pop-up advisory on the control panel.
11. Click Save.
132
Administrator Guide
Viewing the Board Assignment Report

The Board Assignment Report displays the groups and menus all of the boards have been assigned to.
The report opens in PDF format in a new window. You can save or print the PDF file. Only users with
access to the Boards Manager can access this report.
To view the Board Assignment Report:
2. In the Boards window, click the Actions button, then select one of the following options:
Board Assignment Report - View to open the report in a new window. Opening the report in a
Board Assignment Report - Export CSV to export it to a CSV (comma-separated value) file.
Note: If you use the Filter function and then run the report, the report will only include the boards
from the filtered results.
Viewing the Individual Board Assignment Report

If you want a report that only contains data for a specific board, you can access the Individual Board
Assignment Report. The report opens in PDF format in a new window. You can save or print the PDF file.
Refer also to Board Manager for more information.
133
Processes
To view the Individual Board Assignment Report:
2. In the Boards window, click the board name.

3. In the Edit Board window, click one of the following options in the Reports section:
Individual Board Assignment - View to open the report in a new window. Opening the report in
a new window allows you to print it as a PDF.
Individual Board Assignment - Export to CSV to export it to a CSV (comma-separated value)

file.
The Agency Template Manager

The Agency Template Manager allows you to define agency specific settings in WebEOC. You can apply
your agencys name and logo. You can also add a login policy message that appears when a user logs
into the system and a system-wide message that appears in the Notifications section of the home page
for all users.
134
Administrator Guide
Note: Board colors and fonts can be managed from this area when using agency template code in
boards. Views created in the board builder do not use this code. Instead, they apply a uniform user
interface standard. When exporting boards that use the agency template, the theme is not exported.
Agency Tag
Your agencys name is displayed on the Homepage tab. It can also be display in boards by using the
<agencyinfo /> tag. If you do not apply the tag to your board, your agencys name does not appear
in the board.
The defined primary logo appears on the Homepage tab. This tag is also included in the default board
set. The primary logo and secondary logo can be displayed in a board by using the <agencyinfo />
tag. If you do not apply the tag to your board, your logos do not appear.
Use the System-wide Message field to communicate critical information to system users. This message
is displayed on the Homepage tab and can also be displayed in boards by using the <agencyinfo/>
tag. If you do not apply the tag to your board, the system-wide message does not appear.
Refer to the Web-EOC-specific Tags topic for detailed information on these tags.
135
Processes
Policy Message
The text you enter in the Login Policy Message field appears on a separate window that is presented to
the user prior to reaching the WebEOC Login window.
Users must click Accept in order to continue logging in to WebEOC. This is useful if your agency has a
policy or terms statement that users must accept. It is also useful to indicate whether the system is a
production or training environment when multiple environments exist. Below is an example of what this
feature looks like during the login process.
Tip: Text can be copied form a Microsoft Word document into the Login Policy Message field.
Formatting is retained.
System-wide Message
The text you enter in the System-window Message field appears in the Notifications section in the home
page. Text can be copied from a Microsoft Word document into this field. Formatting is retained.
136
Administrator Guide
Configuring the Agency Template

To configure the agency template:
1. In the Admin window, click the Process tab, then click Agency Template.
2. In the Agency Template window, enter a name in the Agency Name field.
3. Click the Browse or Choose File button next to the Primary Logo field to upload your agencys
logo.
Tip: The recommended logo size is 60x60 pixels; however, this is not a requirement.
4. Click the Browse or Choose File button next to the Secondary Logo field to upload an additional
logo.
5. In the Login Policy Message field, enter your agencys login policy message and use the tools in
the formatting toolbar to format the message.
6. In the System-wide Message field, enter your system-wide message. Use the tools in the
formatting toolbar to format the message.
7. Click Save.
137
Processes
Configuring Board Colors and Fonts

In some WebEOC version 7 boards, the agency template code is used in boards to centrally configure
colors and fonts. WebEOC version 8 boards do not use this approach. Version 8 boards use a new
standard user interface that maintains consistency between boards and among WebEOC systems. Board
colors and fonts are configured in the Agency Template Manager.
To configure the agency template board colors and fonts:

1. In the Admin window, click the Process tab, then click Agency Template.
2. In the Agency Template window, click the Actions button, then click Configure Board Options.
138
Administrator Guide
3. In the Colors section, assign a color to the background of your boards, board headers, table
headers, and table rows by entering a color code or clicking inside the field and using the color
picker window.
4. In the Colors, Board Header, Table Header, and Table Entry sections, select a font family, font size,
font style, and font color.
5.
Click Save.
The Dual Commit Manager

Dual Commit and remote boards are tools for agencies that need to communicate with other agencies
outside their firewall. Dual Commit allows users to avoid the confusion of having to log directly into two or
more WebEOC systems, thus facilitating information sharing among agencies using WebEOC (for
example, between counties and state EOCs or like agencies).
Dual Commit allows agencies to automatically or selectively decide which board entries to post to an
outside server, keeping sensitive information within your organization. It is similar to logging into another
server and posting information, but through a WebEOC administrative configuration, the client can post
information to more than one server without having to log out of the local server and onto the remote
servers. This allows for a convenient data sharing solution among multiple WebEOC agencies.
139
Processes
Individual status boards can be set to either auto or manually Dual Commit. If the Auto check box is not
selected for the board, then each individual entry must be manually pushed to the remote server at the
discretion of the user.
The Dual Commit Manager allows you to maintain a list of servers available for Dual Commit. This list is
updatable, allowing servers to be added, modified, and deleted as needed.
In order to successfully execute the Dual Commit operation, an identical copy of each status board
designated for Dual Commit must reside on each source and each target.
Each time a new board is added and configured for Dual Commit, the board must be added to the target
servers. This can be accomplished using the Import/Export Board tool in the Boards Manager. Once the
new board is added to the target server, remember to set applicable group permissions on the target
server as well.
If changes are made to a Dual Commit board, identical changes must be made on the target servers,
either manually or by copying the HTML of the input and display views for the board to each target server
using the Board Editor.
Alternatively, the Import/Export Board tool may be used. If this utility is used to update a board on a target
server, import the updated board, and then reset group permissions for the board.
The Test Connection button in the Dual Commit Manager executes an automated test between the local
server and the target server to verify configuration parameters during setup.
Prerequisites
You must meet the following requirements in order to implement the Dual Commit and Remote Boards
features.
1. You must have a licensed copy of WebEOC 7.0 or higher.
Note: Dual Commit may not be possible between different versions of WebEOC.
2. The Dual Commit target or remote board WebEOC server must be accessible by the WebEOC
server executing Dual Commit or Remote Board functions. This network access must support
TCP/IP. In addition:
If SSL is implemented, access over port 443 is required.
If SSL is not implemented, access over port 80 is required.
140
Administrator Guide
3. Status boards configured as Dual Commit on the local server must also be available on the target
server. In addition:
When a new board is added or an existing board is modified on the local server, the same
changes must be performed on the target server.
Board names and field names on the target server must be identical to the board names and field
names configured for the board on the local server.
4. A user account, password, and position name must be established on the target server and your
local server to implement the Dual Commit and Remote Board features in WebEOC.
These user accounts should only be used for Dual Commit purposes. We recommend that you
distinguish the accounts from normal user accounts by selecting the Dual Commit User check box
in the Edit User window. This removes the user accounts from the users list, meaning the account
does not appear in the user name selection list wherever utilized in WebEOC (such as input views,
display views, and so forth).
The user account must also have Multiple User Login enabled so multi-user access conflicts do not
occur when executing these features.
Dual Commit Target Servers

Before you add a Dual Commit server, you must obtain the following:
The username, password, and position name of the user account on the target server (the server
you want to log in to).
The URL of the target server.
The URL is a DNS name, a host name, or an IP address along with the directory where WebEOC is
located. The following are several examples of typical URLs.
http://www.webeoc.com/eoc8/
http://webeocserver/eoc8/
http://10.25.35.1/eoc8/
Note: You must add the forward slash (/) at the end of the URL for it to be valid.
141
Processes
Adding a Dual Commit Target Server

To add a Dual Commit target server:
1. In the Admin window, click the Process tab, then click Dual Commit.
3. In the Create Dual Commit Server window, enter the Name of the target server. This is a required
field.
Note: You can enter any name for the server.

4. Enter the URL of the target server.
142
Administrator Guide
5. In the Organization field, type EOC Professional.
Tip: Be sure to include the space.
Note: Agencies that target a WebEOC system hosted on an ASP server should contact the
WebEOC Customer Support for the appropriate organization information.
6. Enter the Username and Password of the Dual Commit user account on the target server.
7. Re-enter the password in the Confirm Password field.
8. Enter the Position of the Dual Commit user account.
9. Click Save.
10. From the Dual Commit window, click the Name of the server.
If you have entered any information incorrectly, the system displays an error. Example errors:
The remote name could not be resolved: sevr
Invalid URL
Invalid Organization Name
Invalid Username or Password
User account on target server is not set to Multiple User Login
You are not a member of a position
If you receive the You are not a member of a position error, the position configured for the user account
may not have the proper permissions on the target server. Contact the administrator of the target server.
The successful connection message indicates your settings are correct and the settings are automatically
saved.
After you have added the target server, you need to set up the queuing option for incoming Dual Commit
entries. Refer to Incident Mapping for more information.
Editing a Dual Commit Target Server

To edit a Dual Commit target server:
143
Processes
2. In the Servers list, click the name of the server you want to edit.
3. In the Edit Dual Commit Server window, make your changes.

4. Click Test Connection to execute an automated test of the server configuration.
Take the appropriate action based on your results:
If you receive the You are not a member of a position error, contact the administrator of the
target server.
If you receive any other error, contact the Support Center.
The successful connection message indicates your settings are correct and are automatically
saved. No further action is required.
Deleting a Dual Commit Target Server

To delete a Dual Commit target server from WebEOC:
next to the server you want to delete.
144
Administrator Guide
Adding Dual Commit Functionality to a Board

In order to push data to a target server, the board on your server (host server) must be configured to
use Dual Commit.
Dual Commit allows you to share a board with another agency. Sharing a board requires the following
three processes:
Export the board
Send the board to the target server
Configure the board on the host server to use Dual Commit
Refer to the Boards Manager topics for more information on creating, importing, and exporting boards.
Sending a Board to the Target Server

In order to share a board with another agency, you must send the board file to them. We recommend
creating a zipped file and emailing the board. It is necessary to create a zipped file because some email
servers may strip out board code they deem malicious, corrupting the board file.
After the agency receives the board, it must be unzipped and then imported on the target server. Refer to
Importing a Board for detailed instructions.
To set a board with input views to Dual Commit:
145
Processes
5. In the Settings section, click Dual Commit.

7. Click the server in the Server drop-down list.
8. Select the Auto check box if you want all posts to be dual-committed by default. Leave this box
cleared if you want users to selectively decide which entries to Dual Commit.
9. Click Save.
10. Repeat steps 5-9 for each input view.
11. When you are finished, click Save.
Incident Mapping
Before data can be shared using Dual Commit, the way in which incidents are handled and synchronized
must be configured on the target server. The target server can either automatically create a matching ad
hoc incident for incoming Dual Commit entries or queue incoming entries until manually mapped to an
existing incident. After an incident has been mapped, all queued dual commit entries automatically post to
the mapped incident.
To set the incoming queuing option:
2. In the Dual Commit window, click the Actions button, then select Incoming Dual Commit Options.
146
Administrator Guide
The Edit Incoming Dual Commit Options window opens.
3. Do one of the following:
To create a new incident on the target system with the same name as the host server, select
Queue all incoming dual commits until the incoming incident... .
Note: If you select this option when using remote boards, other WebEOC systems are not able to
post messages or see those boards until their incidents have been mapped.
To create a new incident on the target server with the same name as the incident on the sending
server, select Create incident if it does not exist... . Messages are posted under the newly
created incident.
4. Click Save.
Mapping Queued Messages

If you have opted to queue incoming messages, you now need to map the messages to a specific
incident. Queued messages generate a popup message on the control panel advising that new Dual
Commit entries have been received.
147
Processes
Note: Once assigned, the incident you have chosen cannot be changed or undone. Click Cancel in the
Map this Incident? window to select a different local incident. A list of mapped incidents can be viewed by
selecting the View Mapped Incidents button. This is a view-only window; mappings cannot be changed.
To map queued messages to an incident:
2. In the Dual Commit window, click the Actions button, then select Incoming Dual Commit Options.
3. Click a local incident in the list.

4. When the Map this Incident? window opens, click OK.
Remote Boards
Dual Commit can be configured to allow access directly from your control panel to boards residing on
other WebEOC servers. Rather than maintaining copies of the board and posting data directly to every
WebEOC server, a single board on one server can be accessed by multiple WebEOC instances. Users
can view, sort, filter, add, and update entries as they normally would.
Using remote boards allows all WebEOC instances to view the same set of data from the same board.
Everyone has all the information available to them and a common operational picture is maintained.
Data is stored on the server that is hosting the remote boards. If connectivity to that server is lost, data
contained in the remote boards hosted on that server cannot be viewed, except by those users directly
connected to the server, until connectivity is restored.
Board permissions set at the host server define the highest permission set that can be assigned at the
local level. Users granted higher permissions at the local server are not able to execute boards tasks for
which permissions have not been granted at the host server.
Using Remote Boards with Dual Commit

If you implement Dual Commit, you can use remote boards to allow users access directly from their
control panel to boards residing in another WebEOC system. Entries may be viewed, sorted, filtered,
148
Administrator Guide
added, and updated as though they reside on the local server. Refer to Remote Boards for more
information.
Using Remote Boards

On the control panel, remote boards are grouped in the Dual Commit section under a single link named
Remote Boards. Clicking this link shows a list of the boards the user can access.
Remote boards are used just like local boards on a users control panel. Users can add, update, view,
sort, and filter data as determined by the permissions allowed at the board owner and local server levels.
Remote boards differ from local boards in that board displays do not refresh as data is added. Remote
boards refresh on a timed interval, which can take up to 60 seconds. Users who are logged in to a system
directly viewing the same status board will see data refresh as it is added.
Important: It is strongly recommended that this be emphasized during local training.
Closing the Remote Boards window automatically closes all remote boards that are currently open. If
necessary, the Menu window can be minimized when not in use.
Remote Board Setup and Configuration

Certain setup configurations must be completed on both the host server and the local server. Because
the server acting as host must be made available across the Internet, it is strongly recommended that the
steps outlined for the host server in the following section be taken to secure the implementation.
The Dual Commit Server

Complete the following on the Dual Commit (host) server.
Follow these steps to secure the implementation:
1. Implement SSL. WebEOC should be accessed over the Internet using https.
2. In the General Manager, set the following security parameters. See the table below for
recommended settings and values.
Parameter
Recommended Setting
Enforce strong passwords
enabled
Password age (expiration)
180 days
149
Processes
Minimum password length
8 character minimum
Account lockout threshold
3 attempts
Account lockout duration
30 minutes
3. Determine the board permissions to be granted to the local server. These permissions cannot be
overridden at the local level.
a. Identify (or add) the board or boards to be shared.
b. Identify the exact input and display view names for the boards.
c. Determine board permissions to be granted to the local user. These permissions cannot be
overridden by permissions set at the local level.
d. Determine whether the board is to be Global or Incident Independent.
i.
If set to Global, all entries posted to the board through any active incident on the host
server are displayed and remain displayed until the incident through which it was posted is
archived.
ii. Data posted to a board configured as Incident Independent is not removed when the
incident through which it was posted is archived, nor is board data archived.
iii. If the board is not configured for either Global or Incident Independent, multiple incidents
can be rolled up to a master view.
4. Set up user accounts in the Users Manager for use with the remote board feature. The user name is
posted if displayed in the remote board. In the Edit User window, select the Multiple User Login
and Dual Commit User options.
5. Add the user account created in the previous step to a position, and assign that position to a group.
Set permissions (Read, Read/Write, or Read/Write/Delete) for each board that the remote users
have access to.
6. Record the information determined and/or created in the preceding steps. You must provide the
following information to the administrator of the local server to complete the remote board
configuration:
a. URL of the host server.
150
Administrator Guide
b. Username, password, and position name for the account to be used for the remote board
feature.
c. Exact name of the board or boards.
d. Exact name of both the input view and display view for the board to which users have access.
e. Permissions assigned for each board in the group profile.
The Local Server

Before you begin, you must have the URL of the host server and user account and board information.
You must also determine which groups on the local server are to have access to the remote boards.
To create a Dual Commit server for the remote board function:
1
In the Admin window, click the Process tab, then click Dual Commit.
Click Add Server.
In the Create Dual Commit Server window, enter the server Name.
Enter the URL of the host server.
Enter the organization name provided by the administrator of the host server in the Organization
field.
Note: If WebEOC is installed locally, the organization name is EOC Professional. If your WebEOC
is hosted by Intermedix, contact the Support Center for the appropriate organization information.
7. Enter the username provided to you by the administrator of the host server in the Username field.
8. Enter the password provided to you by the administrator of the host server in the Password field.
9. Re-enter the password in the Confirm Password field.
10. Enter the Position of the user account provided to you by the administrator of the host server.
11. Click Save.
12. In the Dual Commit Server List, click the Dual Commit server you just created.
13. In the Edit Dual Commit Server window, click the Test Connection button to verify communication
with the host server. Login Successful should appear in the Admin window.
151
Processes
14. Click the Back button.
Now that you have created and tested your new Dual Commit server, you must add the remote boards to
it and assign group permissions to them.
1. In the Dual Commit window, click Manage Remote Boards next to the server you just created.
2. In the Remote Boards List window, click Add Remote Board.
3. In the Edit Remote Board window, do the following.

a. Enter the Name of the board.
Note: This name must match the name of the board on the host server.
152
Administrator Guide
b. Enter the exact name of the input view in the Input View field.
c. Enter the exact name of the display view in the Display View field.
d. Click a group in the list that you want to assign to the list item.
e. To modify the permissions, click Edit beside the permissions, and select a new permission in
the Available Groups window.
f.
Click Save.
g. Repeat these steps for each remote board.

4. To assign the remote board permission to a group, click Groups in the Users tab of the Admin
window. This adds the Remote Boards plugin to the control panel of users assigned to the group.
5. In the Groups window, click the name of the group.
6. In the Settings section, click the Plugins option.
153
Processes
7. Click Remote Boards in the list.
8. Click Save.
The Links Manager

WebEOC allows you to create links to URLs (Internet or intranet) and other applications, systems, or
databases.
These links can appear in the control panel or within menus and provide direct access to a web page,
directory, or file. The page or file opens in a separate browser window.
Creating a Link
To create a link:
1. In the Admin window, click the Process tab, then click Links.
2. Click the Create Link button.
154
Administrator Guide
3. Enter a name for the link in the Link Name field.
Note: The Link Name should be a proper name or meaningful phrase, not an address. This is the
label that appears on the users control panel.
4. Enter the URL address for the link.
Note: The address can include a domain name or IP address as well as directory or file names. Be
sure to follow URL conventions, such as specifying the protocol https:// and using the forward
slash (/) to separate directory names rather than the back slash (\).
5. Click the Open URL button to test the link.
6. Click Save.
Note: After you add the new link, you need to set access privileges to the link. Access privileges
are configured in the Groups Manager.
Editing a Link
To edit a link:
2. In the Links window, click the name of the link you want to edit.
155
Processes
3. In the Edit Link window, make your changes.
4. Click Save.
Deleting a Link
To delete a link:
next to the link you want to delete.
3. In the confirmation window, click OK. The link is removed from any assigned groups and the users
control panel the next time they log in to WebEOC.
The Lists Manager

Lists allow you to create pre-defined sets of choices from which to select when entering data in status
boards.
156
Administrator Guide
Lists make data entry easier for the user and reduce typographical errors and inconsistent naming
schemes. Lists can also be used to filter a status board display to show only those entries related to a
specific list item.
Multi-tiered lists can be created allowing you to define up to two levels. For example, you could create a
list of States. Each State could have a sub-list containing counties. Each county list could contain a list of
cities. After you build a multi-tiered list, you can add it to a board in the Board Editor. Refer to Multi-tiered
Lists for more information on adding a multi-tiered list to a board.
Lists can also be used to implement processes by assigning group permissions to any item or sub-item in
a list. For example, if you want only the controller to set a task status as Closed, you can assign
permissions to a specific group or groups. In this scenario, the Closed status would be made available to
the authorized positions in the group configured in the Lists Manager.
Colors can be assigned to items in the list. When the color is selected, it is saved with the list item. Using
color codes in a board display helps users interpret data (such as status) more quickly and determine the
importance of the data.
Other lists in WebEOCUsers, Incidents, and Positionsare created and maintained through their
respective Admin manager.
The following conditions should be considered when creating, modifying, or replacing lists:
157
Add Other to each list as a catch all category.
Add a blank item as the first list option unless the default value should be something different.
Take advantage of the alphabetize feature to present list items to users in a logical order.
Processes
If the List Name is changed, the information currently posted on any board using that field is not
affected, but the board will no longer use the list unless the board is modified through the Board
Editor to reference the new list name.
If a list used in a board is deleted, the information currently posted on any board implementing
that field is not affected, but the list field will be empty if the user creates or edits records.
If a new list is created to replace the deleted list, that field must be updated in the board or
boards through the Boards Editor.
Creating a List
To create a list:
1. In the Admin window, click the Process tab, then click Lists.
2. Click the Create List button.

3. Enter a Name for the list.
158
Administrator Guide
4. In the Comments field, enter a description or additional information for this list.
5. Click Save.
6. Click Create Item in the List Items section.
Tip: If you already have the list, you can import it. Refer to Importing a List for more information.
7. Enter a name for the item in the Item Name field.
8. If desired, assign a color to the item by clicking inside the Color field. Use the cross hair icon to
select the color.
Tip: You can also enter a color code in the Color field.
159
Processes
9. If the list item is reserved for use by a specific group of users with access to the list, select the Apply
Permissions check box. If you want the list item to be available to all users with list access, do not
select the check box.
10. If you selected the Permissions check box, apply the permissions by doing the following:
a. Click Add Group in the Group Permissions section.
c. Click Add.
11. Click Save.
12. Repeat these steps to build your list.
Adding Sub-lists
After you create a list item, you can add a sub-list to it. You can even add a sub-list to your sub-list. For
example, if you created a list called Georgia and added every county in the state of Georgia as a list item,
you could create a sub-list for every city in every county. After you have added the cities, you can add
subdivisions within those cities.
To create a sub-list:
1. Click the list in the Lists window.
160
Administrator Guide
2. In the Edit List window, click Add Sub-list next to a list item.
3. In the Edit List window, click Create Item to add items to your sub-list.
select the color.
c. Click Add.
8. Click Save.
9. Repeat steps 3-8 to build your list.
161
Processes
After you build your sub-list, you can build a sub-list for that list as follows:
1. In the Edit List window, click Add Sub-list next to the list item you want to add a sub-list to.
2. Click Create Item to add items to your sub-list.

select the color.
162
Administrator Guide
c. Click Add.
7. Click Save.
8. Repeat steps 3-7 to build your list.
9. Click Save.
Editing a List and List Items

To edit a list and the associated list items:
2. In the Lists window, click the name of the list you want to edit.
3. In the Edit List window, do one or more of the following:
163
To rename the list, enter a new name in the Name field.
Processes
In the Comments field, change the description or insert additional information if applicable.
To change a list item name, click the name of the list item.
To edit a sub-list item, click Edit Sub-List next to the sub-list you want to edit.
To organize the items alphabetically, click Actions, then click Alphabetize.
To view all items in the list, including sub-list items, click Actions, then click View List Report.
To move an item up or down, click the Move up or down arrows.
To delete an item, click the trash can icon .

Note: Deleting an item also deletes any sub-lists of that item.
Note: Refer also to Importing a List or Exporting a List.
4. Click Save.
Deleting a List
To delete a list:
next to the name of the list you want to delete.

Note: If a list is being used by a board, this will be shown in the confirmation window. If it is deleted, the
board no longer has any list items visible when you edit a record.
Importing a List
If you already have a list, you can import it into WebEOC. The file must be a comma-separated value
(CSV) file.
164
Administrator Guide
To import a CSV file:
2. In the Lists window, click the name of the list you want to upload to.
3. In the Edit List window, click the Actions button, then click Import/Export.
4. In the Import/Export List window, click the Choose File button.
165
Processes
5. Locate your file, and click Open. The File field is populated with the location of your file.
6. Click Import. The Edit List window appears. The List Items section is populated from your file.
Note: Sub-list items can also be imported; however, they must be imported separately from the
main list.
Exporting a List
You can also export lists from WebEOC and share them with other agencies.
To export a list from WebEOC:
2. In the Lists window, click the name of the list you want to export.
3. In the Edit List window, click the Actions button, then click Import/Export.
4. In the Import/Export List window, click the Export button.
5. When the File Download window appears, click Save.

6. Select a location and save the file.
166
Administrator Guide
The Menus Manager

You can use the Menus Manager to group and display boards, plugins, links, and other menus under a
single item on the control panel. When a user selects the menu name, assigned items expand below it.
When the menu is selected again, the list of items collapses and is no longer visible.
As each board, link, plugin, or menu is added to the menu, access permissions must be assigned to each
in the same way as group permissions are assigned. Users assigned to a group that has access to the
menu inherit the permissions established for the menu.
For example, a menu called Resources includes the Resources board (Edit permissions), File Library
(View Only) and MapTac (Edit Markers). This menu is added to the Logistics group. Any user who is a
member of that group has the same access to the Resources menu with the permissions assigned
during menu setup.
Menus are located on the control panel in the Menus section. Click the name of the menu or the arrow
to the left of its name to expand a menu item. The section expands to show you the available options.
167
Processes
A star icon
preceding a board item alerts users when there is data that has not been viewed. Once the
board containing new data has been opened, the star disappears until new information has been added
or existing information has been updated.
Creating a Menu
To create a menu:
1. In the Admin window, click the Process tab, then click Menus.
2. Click the Create Menu button.
3. Enter a Name for the menu.
168
Administrator Guide
4. In the Boards tab, click Add Board.
a. Click the board in the Board drop-down list.

b. To change the Label to an alias to be displayed on the control panel, delete the text and type a
new name for the board.
c. In the Input drop-down list, click the appropriate input view.
d. In the Display drop-down list, click the appropriate display view.
e. In the View Filters tab, select the check box next to any filters you want to appear.
f.
In the Board Permission Tags tab, click the permissions in the list.
g. Click Save.
5. Click the Plugins tab to assign plugins to this menu.
a. Click Add Plugin.
b. Click a plugin in the Plugin drop-down list.
c. Rename the plugin, if appropriate, in the Label field.
d. If applicable, click a permission in the Permission drop-down list.
e. Click Save.
6. Click the Links tab.
a. Click Add Link.
b. Click a link in the Link drop-down list.
c. Rename the link, if appropriate, in the Label field.
d. Click Save.
169
Processes
7. Click the Menus tab.
a. Click Add Menu.
b. Click a menu in the Menu drop-down list.
c. Rename the menu, if appropriate, in the Label field.
8. Click Save.
Note: After you add a new menu, you need to set access privileges to it using the Groups Manager.
Editing a Menu
To edit a menu:
2. In the Menus window, click the name of the menu you want to edit.
3. In the Edit Menu window, make your changes.
170
Administrator Guide
4. Click Save.
Deleting a Menu
To delete a menu:
next to the menu you want to delete.

Note: When a menu is deleted, it is also removed from any assigned groups in the Groups Manager.
171
System
This section describes various system configurations and functions.
The Admin Profiles Manager

Use the Admin Profiles Manager to control access to specific administrator functions in WebEOC.
You can configure and assign permissions to specific users with the account type of partial administrator.
Partial administrators can perform only those administrative functions that you enable, allowing nonsystem administrators in an organization some degree of administrator privileges, when required, in order
to help administrators fulfill their job duties.
You can grant system permissions based on the need and permission level required. For example, a
profile can allow a user to manage lists for their agency by assigning an admin profile, while another
profile includes a different set of administrator permissions, such as building boards and checklists.
Similarly, as members of the controller organization, User A is responsible for building drill scenarios
while User B conducts emergency management training. While job responsibilities require both to have
access to the Simulator Manager, specific permissions based on need can be assigned allowing User A
full permissions to edit, delete, and run simulations, while User B is only allowed to run the simulator. In
turn, User A can assign permissions to other users that are equal to or less than their own. User B can
only assign Run permissions to another user.
Users that are designated WebEOC administrators through the Users Manager have full system access
and configuration authority, regardless of permissions assigned through the Admin Profiles Manager.
172
Administrator Guide
Planning an Admin Profile

Before adding an admin profile, consider the following points in determining specific permissions.
Determine the permissions that should be enabled for each user with that profile, such as edit,
delete, clear, run, unlock, and more.
Is there an existing admin profile with the proper permissions that meets the needs of the user, or
does a new admin profile need to be created?
When creating and editing an admin profile, consider the following points.
If you want the partial administrator to be able to access the profile, they must be added as a
user to the admin profile.
If you are assigning the user from the Edit Admin Profile page, you can only add users with an
account type of partial administrator.
An admin profile partial administrator can exercise their assigned permissions to any profile to
which they belong, regardless of who created the profile.
You can assign the same or more restrictive privileges to users assigned to the profile; users
cannot elevate their assigned permissions within the admin profile.
In order for the Admin icon
Belonging to an admin profile gives that user access to the admin managers to which they have
to appear, a user must belong to at least one admin profile.
been granted rights. It does not give them access to the Admin Profiles Manager.
In addition, note the following about full and partial administrators:
The List permission is automatically selected for most admin managers and cannot be removed.
To remove an admin manager from the profile, select the admin manager in the list and click
Remove.
Users assigned WebEOC full administrator privileges through the Users Manager have full
configuration permissions in the Admin Profiles Manager. This overrides any permissions set in
the Admin Profiles Manager.
Partial administrators have access to only the admin managers and permissions to which they
have been assigned.
173
System
Partial administrators cannot elevate their permissions to another profile.
A partial administrator sees only those permissions that they have been assigned. If their user
account has been assigned WebEOC full administrator privileges, they can enable and/or disable
all permissions for all admin managers.
Creating an Admin Profile

For details on profiles, administrators, and partial administrators, refer to Admin Profiles Manager.
To create a new admin profile:
1. In the Admin window, click the System tab, then click Admin Profiles.
2. Click the Create Admin Profile button.
3. Enter a Name for the profile.
174
Administrator Guide
4. Assign a user or users to the admin profile by clicking Add Partial Administrator.
Note: Only users with a partial administrator account type configured in the User Manager are
displayed.
5. Select the user from the list, then click Add.
6. Assign admin managers and set their permissions by clicking Add Admin Manager in the Admin
Manager section.
a. Click in the Admin Manager drop-down list.

b. Select the Permissions.
c. Click Save.
7. Click Save.
Editing an Admin Profile

To edit an admin profile:
175
System
2. In the Admin Profiles window, click the name of the profile you want to edit.
3. Make your changes in the Edit Admin Profile window.
4. Click Save.
Deleting an Admin Profile

To delete an admin profile:
next to the profile you want to delete.
The Audit Log Manager

The Audit Log tracks, records, and displays administrative events that have occurred in the WebEOC
system.
176
Administrator Guide
This information allows you to monitor, assess, and troubleshoot system activities. You can search the
Audit Log based on user, message, position, incident, and date range, or a combination of these criteria.
Examples of entries that are recorded in the Audit Log include successful and/or failed logins, forced
logouts, account lockouts, and add/delete/update actions performed in an admin window. The date/time,
user, position, and a brief synopsis of the action are provided and displayed in descending chronological
order.
The Audit Log can be purged to permanently delete all information.
You can obtain data entry and entry update actions in a status board by generating a report through the
Reporter Manager.
Viewing and Sorting the Audit Log

By default, the audit log is sorted in descending, chronological order. You can change the sort order by
clicking the desired column heading (Date, User, Position, Incident, or Message).
You can also select the numbers in the bottom banner of the Audit Log window to quickly navigate
through the list.
Searching the Audit Log

To search and display specific audit log events:
177
System
1. In the Admin window, click the System tab, then click Audit Log.
2. In the Audit Log window, enter search criteria in one or more of the following fields:
Tip: Partial searches can be performed on a field.
a. Enter the name of the User you want to find log entries for.
b. In the Message field, enter text that is contained within the event description.
c. Enter the Position you want to search for.
d. Enter the name of the Incident that the user was logged in to when the action was executed.
e. Specify a Date Range. Enter the from date in the first field, and the to date in the second field.
US date format:
mm/dd/yyyy (for example, 05/27/2010)
International date format:
dd/mm/yyyy (for example, 27/05/2010)
178
Administrator Guide
3. Click Apply. Audit log events matching the values specified in your search appear in the page.
Tip: To remove search filters, select the Clear button. All fields are clear. The entry list is reset to
display the entire audit log.
Clearing the Audit Log

Warning: Clearing the audit log permanently removes all events in the log from the WebEOC database.
This event information cannot be retrieved once it is cleared.
To clear the audit log:
1. In the Admin window, click the System tab, then click Audit Log.
2. In the Audit Log window, click the Actions button, then select Clear Log.
The General Manager

The General Manager allows you to configure several system options and set a number of security
policies for WebEOC. Options configured in the General Manager are applied to all WebEOC user
accounts.
179
System
Accessing the General Manager

To access the General Manager:
1. In the Admin window, click the System tab, then click General.
2. In the General Settings window, configure the required settings. For details, refer to:
Email Configuration Options
Security Options
Miscellaneous Options
Additional Sub-Administrators
3. When you are done, click Save.
General Manager Miscellaneous Options

By default, WebEOC is set to use the Design HTML editor. Other options included the Advanced HTML
editor, which offers syntax highlighting and auto-completion as well as the Plain Text editor.
Administrators can set the default for all HTML editing to any of these three editors.
If the Require Additional Login Information check box is selected, you can set additional options that
users are required to provide during the login process. These details could be name, location, email
address, phone number, and/or comments. When enabled, data entered during login can be accessed in
180
Administrator Guide
the Sessions Plugin and Sessions Manager and viewed for the duration of the users session. A WebEOC
board can also be configured to automatically capture this data to reduce data entry time.
General Manager Security Options

The Security Options section in the General Manager enables you to configure WebEOC in a manner that
matches your organizations security guidelines.
In addition to the security features outlined in this section, it is strongly recommended that you implement
a Secure Socket Layer (SSL). This ensures data is encrypted during the data transfer. See your system
administrator or hosting provider to set up this feature.
181
System
You should also consider enabling Windows authentication. This allows you to identify and validate the
identity of users accessing WebEOC. See your system administrator or hosting provider to set up this
feature.
Allow Self-registration
This feature enables users to self-register and set up their own user accounts in WebEOC. When you
activate this feature, the New User? Click here to create an account link appears in the WebEOC Login
window.
When self-registration is activated, the Forgot Username/Password? link is enabled. This can be used
to email a user their username if they have forgotten it or send them a link to change their password if
they have forgotten that.
Note: If you enable the self-registration feature, you must provide your users with a position name and a
position access code (PAC). PACs are configured in the Positions Manager.
182
Administrator Guide
Allow Users to Edit Their Accounts

Administrators can allow WebEOC users to edit and maintain their own user accounts.
If this feature is not enabled, the account name appears as static information on the information bar and
all changes to user accounts must be performed by a system administrator. When enabled, the user
account name appears as a link in the information bar.
Clicking the link opens the User Account edit window. Users can update their own account information
such as their password and email addresseasing the burden on administrators. Users can also add
data to the Additional Information section. This feature does not allow users to change their assigned
permissions or access privileges.
183
System
Security Options
The following table lists and describes security options that you can set, as appropriate for your
organization:
Option
Description
If enabled, user passwords must meet the requirements for a strong password. It
Enforce Strong
must contain at least one upper case letter, at least one lower case letter, and at
Passwords
least one number.

We recommend enabling this feature.
Sets the number of days a password will be valid before it expires. When the
Password Age
number of days is exceeded, the user is required to change it at their next attempt
to log in. When set to zero (0), passwords do not expire.
We recommend setting the password age to 180 days.
Minimum
Password Length
Requires a specified character length for user passwords. Setting the character
length to zero (0) removes the character count requirement.
We recommend setting the password length to a minimum of 8 characters.
Determines the number of unique new passwords that have to be associated with a
Enforce
user account before an old password can be reused. If enabled, user passwords
Password History
cannot be reused for the specified number of times configured in the Password
History field.
If the Enforce Password History setting is enabled, this sets the number of
unique passwords a user must exhaust before they are allowed to repeat a
Password History
particular password.
For example, if Password History is set to 3, the first password may not be reused
until three unique passwords have been used.
Sets the number of failed login attempts allowed before an account is locked.
Account Lockout
Threshold*
Setting the threshold to zero (0) allows an unlimited number of login attempts.
As the administrator, you can log in to WebEOC to manually unlock a user
account.
We recommend setting this to 3.
After the lockout threshold is exceeded and the account is locked, this option sets
the amount of time that must elapse before the system processes another login
Account Lockout
attempt.
Duration
Setting the duration to zero (0) minutes locks the account until it is manually
unlocked by an administrator.
We recommend setting this to 30 minutes.
184
Administrator Guide
Sets the number of days an account can be inactive before it is locked.
Inactivity Lockout
If a user exceeds the inactive time period, the user cannot log in. If left blank or set
Threshold
to zero (0), the user account remains active until the administrator manually
disables or deletes the account.
Ensures the total disk space allotted for data files uploaded into the WebEOC
Enforce
database is limited to a specific number of megabytes. This includes files and
Maximum File
attachments added through the File Library, MapTac, Messages, and status
Storage Size
boards.
We recommend you enable this feature.
If enforcing a maximum file storage size is enabled, set the maximum storage disk
Max File Storage
space in megabytes that can be used to store uploaded files in the WebEOC
Capacity
database.
We recommend setting the maximum storage capacity to 500 megabytes.
*The built-in WebEOC administrator account cannot be locked regardless of the threshold value.
General Manager Email Configuration Options
In order to send emails externally using WebEOC, you must:
Enter a valid email address,
Enter the IP address of the email server, and
Configure the SMTP service. You only have to configure an SMTP service if your email server
does not have an SMTP service already installed.
185
System
To configure your email server to send emails, enter the host name or IP address of your email server.
The host name looks similar to: companyname-exch.com.
The IP address looks similar to: 195.55.55.55.
After you configure the email server and the SMTP service, you can send emails via the Messages tool
and any board that has been configured to send emails.
Any external email that is sent from a board within WebEOC is addressed from the users (primary or
secondary) email account configured in the Users Manager. Users are able to send external emails from
a board to any email account. An email sent from the Messages tool is addressed from the senderthat
is, the user account used to log in to WebEOC.
Note: A user account must have an email address configured in order to send emails.
The Use SMTP Credentials check box enables you to provide a username and password to the SMTP
settings, allowing for authenticated email sending.
General Manager Additional Sub-Administrators Options

The Additional Sub-Administrator section enables you to increase the number of sub-administrators
allowed in your WebEOC system.
Important: This feature is available only in WebEOC Enterprise.
The WebEOC Enterprise license typically allows you to have 10 sub-administrators. Your agency can
increase this number by purchasing a license that removes the restriction. For more information, contact
WebEOC Customer Support.
186
HTML Conventions
WebEOC Administrators can use a number of features to tailor boards and views to their organization's
specific needs. This section describes HTML conventions you can use to accomplish these tasks.
Note: Board customization is available in WebEOC Professional and Enterprise only.
Board components
Edit View window
Tags:
Supported HTML tags for Input Views
WebEOC-specific tags
Multi-tiered lists
Chart and data tags
Board Components
Every board has two types of views: input and display. Data is entered and updated in the input view and
displayed in the display view. The data resides in one or more tables created specifically for that board
based on the input fields defined in the input forms HTML.
Input View
Following is an example of an input view.
187
HTML Conventions
Display View
Following is an example of a display view.
Edit View Window

Board code changes are entered in the HTML section of the Board Editor window. If you are using an
external HTML editor, this is the area where you can paste in your copied code.
To access the HTML section of the Board Editor window:
2. Click the name of the board.
4. In the Board Editor window, click the name of an input or display view.
188
Administrator Guide
5. In the HTML section, click the Advanced Code Editor tab to display the HTML editor, which includes
syntax highlighting and auto-completion features. Click the Plain Code Editor tab to use the plaintext editor.
Supported HTML Tags for Input Views

WebEOC allows you to use all HTML tags; however, the following tags should be used for input views
only.
<input>
<select>
<textarea>
By default, the <input> and <select> tags are represented in the SQL Server database with a
variable character field (nvarchar) limit of 500 characters. Text fields that hold an unlimited amount of
data are <textarea> fields.
The underlying database field types can be overridden by the fieldtype attribute. In addition, field length
for nvarchar fields can be overridden using the fieldlength attribute. If the fieldtype is set to datetime, then
the format attribute can be used to format the output of the field.
Refer to the SQL Server documentation on the convert function for more information on available
datetime formats.
Refer also to WebEOC-specific Tags topic for information on the board resouce attribute, which you can
use with a number of HTML tags.
<input>
The <input> tag is used to create data entry elements. An input field varies depending on the type of
attribute you assign to it. An input field can be a text field, a check box, a radio button, a button, and
more.
You can use the following values for the type attribute of the input tag:
189
text: Creates a text field (<input type="text" />).
checkbox: Creates a check box (<input type="checkbox" />).
radio: Creates a radio button (<input type="radio" />).
HTML Conventions
hidden: Hides the input field (<input type="hidden" />).
You have the option to update a parent record from the child input record. To do this, include the table
attribute in the <input> tag. Specify the parent table as the attribute's value. This use of the table
attribute works only within an input field where the type="text".
Text input fields can have one of the following predefined values. These predefined values cause the field
type to be datetime:
_currentdate: Causes the field to be the current date. The format is 101 (mm/dd/yyyy).
_currenttime: Causes the field be the current time. The format is 108 (hh:mm:ss).
_currentdatetime: Causes the field to be both the current date and time. The format is 100
(mm/dd/yyyy hh:mm:ss).
_number: Causes the field to be 0 and the field type to be int (integer). The format is 0 (int).
For example, the code <input type="text" value="_currentdate" /> causes the field
type to be the current date.
The code below specifies you want a text field and you want it to be named location.
<input type="text" name="location" />
<select>
The <select> tag is used to create a list of selections, typically a drop-down list. The <select> tag
can be populated with lists contained in WebEOC. The lists are entered using the Lists manager. To
populate a <select> tag with a WebEOC list, use a list attribute on the <select> tag to set the
name of the list. Refer to the following example:
<select name="FieldName" list="ListName">

</select >
When using hard-coded <select> lists with <option> tags, each <option> tag must contain a
value attribute where the value matches the text between the opening and closing <option> tag.
Otherwise, the selected list value will be saved to the WebEOC database as an empty string.
190
Administrator Guide
<select name="FieldName">
<option value="Yes">Yes</option>
<option value="No">No</option>
</select>
WebEOC allows for a select element to display the entire list of EOC users or positions. The syntax for
this <select> tag is shown below.
For users:
<select name="FieldName" list="Users">

</select>
For positions:
<select name="FieldName" list="Positions">

</select>
processpermission and processgroup Attributes

WebEOC extends the select element with a few WebEOC-specific attributes to display a partial or
complete list of EOC users or positions.
The list attribute allows displaying the entire list of EOC users or positions:
For users:
<select name="FieldName" list="Users">

</select>
For positions:
<select name="FieldName" list="Positions">

</select>
191
HTML Conventions
A list of all groups and positions for a process permission can be displayed by using two attributes. The
processpermission attribute specifies the name of the process permission, and the processgroup attribute
specifies the group or position.
<select name="FieldName" processpermission="Requesting"

processgroup="groups">
</select>
To see all positions for the "Requesting" process permission:
<select name="FieldName" processpermission="Requesting"

processgroup="positions">
</select>
<textarea>
The <textarea> tag defines a multi-line text input control. It can hold an unlimited number of
characters, and the text renders in a fixed-width font. The size of a <textarea> tag can be specified by
the cols (columns) and rows attributes.
<textarea name="FieldName" rows="6" cols="100"/>

</textarea>
WebEOC-specific Tags
WebEOC uses the following special tags and related attributes. These are listed in alphabetical order.
Click a link to move to that section of the list.
A
192
Administrator Guide
<agencyinfo>
The <agencyinfo> tag displays the information you created in the Agency Template manager. The
agency name, primary logo, secondary logo, and activation message can be displayed in a board by
assigning those values to the type attribute. These items are rendered as text.
name
Assigning a value of name to the type attribute places your agencys name in a board in WebEOC.
<agencyinfo type="name"/>
primarylogo
Assigning a value of primarylogo to the type attribute places your agencys primary logo in a board in
WebEOC.
<agencyinfo type="primarylogo"/>
secondary logo
Assigning a value of secondarylogo to the type attribute places your agencys secondary logo in a board
in WebEOC.
<agencyinfo type="secondarylogo"/>
activationmsg
Assigning a value of activationmsg to the type attribute displays the System-wide Message (created in the
Agency Template manager) in a board in WebEOC.
<agencyinfo type="activationmessage"/>
<attachment>
The <attachment> tag displays a download link for downloading file attachments.
<attachment name=fileid>html</attachment>
The name attribute holds the fileid. The table attribute is used for <attachment> tags defined within
a <relatedlists> tag.
193
HTML Conventions
<attribute>
The <attribute> tag is used to add field values within attributes while maintaining valid XML.
Following is an example of invalid XML.
<a href="<eocfield name="url" />">A link</a>

Note: The <href> attribute means hyperlink.
Instead use the <attribute> tag to add the href attribute to the anchor tag.
<a>
<attribute name="href">
<expression name="href">url</expression>
</attribute>
A link
</a>
The <attribute> tag can also contain other tags, such as <if> tags for conditional processing.
<boardname>
The <boardname> tag displays the name of the board to the users. If you change the board name in
the admin interface, it is updated anywhere the <boardname /> tag is used. It is usually located within
the display view of a board. You can use it within a <viewlink> tag to dynamically name the text within
the <viewlink>.
<boardpermission>
The <boardpermission> tag allows administrators to apply permissions within the view of a board.
Use this tag to set group permissions for actions, such as adding or updating a record. Only users who
belong to groups that are granted that permission can perform the action.
For example, an "edit" permission can be applied to an Edit button in the board by placing the
viewlink button tag inside the boardpermission tag. Only groups that are assigned the board
194
Administrator Guide
permission can access the viewlink within the boardpermission tag and have the ability to edit
the record.
A board's boardpermission tags appear as permission options within the group administration page.
An option must be selected for that group to have permission to use that feature.
This tag uses the name attribute. The value is the name that appears as a permission option in the group
administration page.
<boardpermission name="Edit">
<viewlink name="Input" type="button"/>Edit</viewlink>
</boardpermission>
The board permission tag also has a sub-tag called <notapplied> that renders its contents when the
board permission has not been applied. In the example, below, a Delete button would display when a
user has been granted this board permission. However, if the user has not been granted the permission,
the button will not render. Instead, the text that was specified for <notapplied> will be displayed.
<boardpermission name="delete">
<viewlink name="delete" type="button"/>Delete</viewlink>
<notapplied>
You do not have permission to delete.
<notapplied>
</boardpermission>
boardresource
The boardresource attribute allows items to be shared among views within a single board or system
wide.
The attribute is used on specific HTML tags to point to the location of a resource for that board. When
used, the standard resource attribute is ignored. Therefore, when you include boardresource, do not
include the standard attribute.
195
HTML Conventions
The following table lists the tags that support using the boardresource attribute and the standard
attribute it takes the place of.
Tag
Standard Attribute
<link>
href
<script>
src
<img>
src
<a>
href
<embed>
src
<object>
data
<iframe>
src
As an example, you have an image file and a script that you want to include with the board. Following are
examples of the tags to include:
<img boardresource=../images/company/myimagefile.png/>
<script type="text/javascript" boardresource=myscriptfile.js/>
Note: It is a best practice to always include the type attribute in <script> tags. This allows you to include
any type of scripting language file, as long as you specify its type in the tag.
<calendar>
The <calendar> is used to place an interactive calendar on a status board. The calendar has day,
week, month, and year views that users can navigate through. Users can also create appointments that
are tied to a WebEOC record in a WebEOC table identified in the <calendar> tag.
Related fields include the following:
appointmentnamefield - Field to be used as the appointment name on the calendar.
appointmenttypefield - Field to be used for the appointment type on the calendar.
starttimefield - Field to be used for the appointment start time on the calendar.
endtimefield - Field to be used for the appointment end time on the calendar.
commentsfield - Field to be used for the appointment comments on the calendar.
196
Administrator Guide
displayview - Display view to be shown when the user clicks an appointment.
Following is the syntax for the <calendar> tag:
<tr>
<td>Name:<input type="text" name="name" /></td>
</tr>
<tr>
<td>Type of Appointment<input type="text" name="type"/></td>
</tr>
<tr>
<td>Start Time<input type="text" name="starttime"/><span
style="cursor:pointer;"
onclick="OpenBoardDateTimePicker(event,'starttime','true');">
<img src="../lib/cal.gif" width="16" height="16" border="0" alt="Pick
a date"></img>
</span>
</td>
</tr>
<tr>
<td>End Time<input type="text" name="endtime"/><span
style="cursor:pointer;"
onclick="OpenBoardDateTimePicker(event,'endtime','true');">
<img src="../lib/cal.gif" width="16" height="16" border="0" alt="Pick
a date"></img>
197
HTML Conventions
</span>
</td>
</tr>
<tr>
<td>Comments: <textarea name="comments" id="" cols="30"
rows="10"></textarea></td>
</tr>
To create a calendar on the display view:
<calendar width="500px" height="500px" appointmentnamefield="name"

appointmenttypefield="type" commentsfield="comments"
endtimefield="endtime" starttimefield="starttime" displayview="Test"/>
<cancelbutton>
The <cancelbutton> tag places a cancel button in a views user interface.
<choose>
This is the choose-when-otherwise tag that works much like the <if> tag. However, this tag provides
the otherwise tag that renders whenever none of the when tags evaluate to true. The test attribute is
the Boolean test to evaluate.
<choose>
<when test="@status='Open'">Open</when>
<when test="@status='Closed'">Closed</when>
<otherwise>Full</otherwise>
</choose>
198
Administrator Guide
<clearsearchbutton>
The <clearsearchbutton> tag places a "clear search" button in the Board Editor user interface.
When included in the code, this tag suppresses all default search buttons.
Refer also to <searchbutton>.
<clicktoedit>
Any text inside the <clicktoedit> tag is available to select for opening up the input view. This is
useful for expressions.
<clicktoedit>Some stuff here</clicktoedit>
<dataexpression>
The <dataexpression> tag specifies fields or values that populate a chart:
color - Color of the value in the chart.
label - Text of the label or legend for this value.
<dataid>
The <dataid> tag is used to display the dataid for the record and create a link users can click to update
the record. It has no attributes.
<datalink>
The <datalink> tag suppresses the standard datalinks section. It uses the "name" attribute.
<datalink name=Significant Events />

The default behavior is to include a datalinks section that lists each datalink by name with a check box
next to it. If you include the <datalink> tag, you need to specify the text and formatting for each
datalink defined because the standard section is completely suppressed.
For example, the default display of the datalink named To Regional might be:
To Regional
199
HTML Conventions
You can use the <datalink> tag to suppress this default display and customize how you want to
display the link. For example, your code might look like the following:
<td>Send this to the Regional Coordinator<datalink name="To

Regional"/></td>
This code yields the following result:
Send this to the Regional Coordinator
<delete>
The <delete> tag is used on a status board to delete entries from the Setup incident, or any entry in an
Incident Independent board.
<embedrss>
The <embedrss> tag allows an RSS feed to be embedded in a view. It is rendered as a <div> tag.
class - CSS class identifiers
displaytime - The number of seconds to display pagesize of items; 0 = no auto-paging
feedexpiration - How often the server goes to the feed for updates; minimum 5, measured in
minutes.
height - Container height.
omitheader - Display or don't display the title of the RSS feed.
pagesize - Number of items to display at once; 0 = all items.
quantity - Number of items to retrieve from the server; 0 = all items.
scrolling - Display or don't display a scroll bar.
src - URL of the RSS feed.
style - Inline style information.
updateinterval - How often the client goes to the server for updates; minimum 5, measured in
minutes.
width - Container width.
200
Administrator Guide
<embedrss src="http://rss.cnn.com/rss/cnn_topstories.rss"
width="100%" height="50" scrolling="true" />
<embedview>
The <embedview> tag is used to embed one view inside another. It is rendered as an iframe.
The following are valid tag attributes:
view Name of view to be embedded by default. (This is required)
board Name of the board that contains the view to be embedded. If not specified, then
the current board is assumed.
style This is a pass-through attribute that allows the resulting HTML containers style to be
specified.
class This is a pass-through attribute that allows the resulting HTML containers class to be
specified.
id This board-builder specified ID is used with the target attribute in the <viewlink> tag to
replace the default view.
enablefooter This is a true/false attribute that specifies whether to display the board footer as
part of the embedded view to allow paging. The default is false.
width Determines the width of the embedded view, in pixels or percentage.
height Determines the height of the embedded view, in pixels or percentage.
scrolling This is an auto/true/false attribute that determines whether to allow scrolling if the
content is bigger than the embedded view. The default is set to auto.
<embedview view="details" board="Objective Test" width="100px"

height="100px">
</embedview>
<enablerecordlocking>
The <enablerecordlocking> tag can be placed anywhere in the HTML for an input view to enable
record locking for the designated input. With record locking enabled, if two or more users open a record
for editing and one user saves the record, the second user receives a warning message when attempting
201
HTML Conventions
to save the record. The warning gives the user the opportunity to cancel. This forces the user to update
the newer record.
Note: This tag will not work with subscription boards.
<eocfield>
This tag is used inside the <eocrepeatallrecords> tag to display information from the database. It
is used only on a display view. The <eocfield> tag uses the name attribute to specify the field from
which the <eocfield> tag is to pull its information. See the example below.
<eocfield name-FieldName />

The following keywords can be used for specific values of the name attribute:
dataid Functionally equivalent to the <dataid> tag.
positionname Name of the position filled by the user who posted the record.
username Name of the user who posted the record.
The name in the <eocfield> tag must match the name in the <input> tag exactly. You can only use
any given <eocfield> tag once in the display. The following eocfields are available on every board.
dataid
entrydate
username
incident
The <eocfield> tag can also use the following attributes.
filetype
disableclick
type
202
Administrator Guide
<eocrepeatallrecords>
The <eocrepeatallrecords> tag should only be used for display views. It instructs WebEOC to
repeat an area of the boards display for each record contained in the board. Following is an example:
<table>
<tr>
<td>Data ID</td>
<td>Location</td>
<td>Description</td>
</tr>
<eocrepeatallrecords>
<tr>
<td><dataid /></td>
<td><eocfield name="location" /></td>
<td><eocfield name="description" /></td>
</tr>
</eocrepeatallrecords>
</table>
The <eocrepeatallrecords> tag has two attributes: rowcount and sort. The rowcount attribute
changes the default number of returned entries shown per page. For example, the code
<eocrepeatallrecords rowcount="20"> returns 20 entries per page. Giving the rowcount

attribute a value of zero displays all returned entries on the first page.
Note: If a display view where rowcount is set to zero is returning a large set of data entries (for example,
1000+), WebEOC performance could be adversely affected. Avoid setting the rowcount to zero where
large data input is expected.
203
HTML Conventions
The sort attribute changes the default sorting of returned entries (for example,
<eocrepeatallrecords sort="lastname, firstname">). Values of the sort attribute

consist of status board fields defined in the input views of the board. Multi-level sorts are done by
including the desired sort fields separated by commas. In this example, the records are sorted by a field
called lastname, then by a field called firstname.
<exportbutton>
The <exportbutton/> tag places a button in the display view that allows users to export the board
data from the board to a spreadsheet.
Note: You can use this tag if you are a WebEOC Enterprise (7.7 or later) user or are using WebEOC
Professional (7.7 or later) and have a license for the Data Manager add-on. See Board Data for more
information.
<expression>
The <expression> tag allows you to do calculations on the data in a board. The expression is
translated into a SQL Server expression. The <expression> tag can use the following attributes.
name
omitalias
useboardlevelfilters
usegrouplevelfilters
useuserlevelfilters
A name attribute is required and the contents of the tag must be the expression to be evaluated by the
SQL Server. If more than one <expression> tag is used in the same display view, each must have a
unique name.
<expression name="total">sum(quantity)</expression>
If you use this tag outside the <eocrepeatallrecords> tag, it performs the calculation on all data
within the board. This is useful for summing rows and other aggregate functions. If you use this tag inside
the <eocrepeatallrecords> tag, it performs the calculation on only one record at time.
204
Administrator Guide
<externalexpression>
The <externalexpression> tag is used to pull data from a table within the same board that is
unrelated to the current table. The name attribute displays the alias name of the external expression.
The table attribute displays the name of the table you want to pull data from.
<externalexpression name="extExpr" table="Other Table"/>count(*)</

externalexpression>
<field>
The <field> tag denotes fields to search against. The parent must be a <search> tag.
name - Name of the field to search.
<search>
<field name="RequestItemName"></field>
<field name="RequestorPosition"></field>
<field name="City_User_Requestor_Pos"></field>
<field name="posNext"></field>
<field name="posInCity"></field>
<field name="RequestQty"></field>
</search>
<filter>
The <filter> tag displays the text Filter Applied if the board has a filter set.
<filterbutton>
The <filterbutton> tag places a filter button in a views user interface. This filter button can be used
to toggle filter activation from a display view.
You can also group multiple filter buttons together for mutual exclusion (radio button behavior).
205
HTML Conventions
Available attributes are:
name - Name of the view filter.
group - An ID to group filterbuttons as mutually exclusive.
This tag is used in conjunction with the <on> and <off> tags.
<filterbutton name="My Requests" group="priority">

<on>
<attribute name="disabled">true</attribute>
<attribute name="class">btn btn-small</attribute>
<b>My Requests</b>
</on>
<off>
My Requests
</off>
</filterbutton>
<filterdropdown>
The <filterdropdown> tag provides the same functionality as multiple <filterbutton> tags
using the group attribute, but in a more convenient drop-down format. The defaulttext attribute is the
first option in the drop-down that represents no filters applied. Underneath the <filterdropdown>
tag, you must have <filter> tags with the name attribute set.
<filterdropdown defaulttext="All">
<filter name="Open Filter">Open</filter>
206
Administrator Guide
<filter name="Closed Filter">Closed</filter>

</filterdropdown>
<filterlistdropdown>
The <filterlistdropdown> tag streamlines the process of creating and using filters in board
views.
In some respects, this tag works the same as the <filterdropdown> tag. In this case, you can add
the tag to the views code and it does not require the creation of filters in the display view for it to work.
You can also specify in the tag which WebEOC list to use. As list items are added, edited, or removed
using the Lists Manager, the changes are automatically reflected in the filter.
Available attributes are:
defaulttext - First option in the drop-down that represents no filters applied.
list - Name of the WebEOC list to use as the values in the filter drop-down field.
field - Name of the WebEOC field on which the filter is based. The view must have a
corresponding <eocfield> entry inside the eocrepeatallrecords opening and closing
tags. If the corresponding <eocfield> tag is not provided, the drop-down appears, but it is
empty. Also, if you provide a field value but it is not being shown, it needs to be inside a hidden
container tag, such as a span or div.
<filterlistdropdown defaulttext="All" list="Counties" field="county">

</filterlistdropdown>
Note: Do not include an ID attribute in the filterlistdropdown tag.
<foreignkey>
The <foreignkey> tag is used to create a one-to-many relationship between tables. A
<foreignkey> tag must appear in any input form for a table that forms a one-to-many relationship to
another table. For example, the Resources board has two tables: Resources and Deployments.
Resources is the parent table in the parent-child relationship. When setting up a parent-child
relationship within WebEOC, the input view for the child table will always have a <foreignkey> tag
pointing back to the parent table. This causes WebEOC to create a field in the child table that stores the
ID of the parent record that each child record is related to. In this example, the Deployments input view
207
HTML Conventions
has a <foreignkey> tag that links many deployments to a single resource. The <foreignkey> tag
must have a table attribute that specifies the name of the table to be related.
Following is an example of a Deployments input view.
<foreignkey table="Resources" />

In this case, the tag produces no visible output and the view must be accessed using a <viewlink>
tag from a resources view. Another option is to have an attribute called type that can be set to select.
When this is set, a drop-down list appears, allowing the user to pick the record. The option text is based
on the content of the <foreignkey> tag. If an <eocfield> tag is used, set the type attribute to fk
and the table attribute to the name of the related table.
The <foreignkey> tag can use the following attributes.
filter
sort
<foreignkeyreference>
The <foreignkeyreference> tag replaces a child's eocfield reference to a parents data ID with a
reference to the parent's table name, wrapped within an expression. Since expressions in related lists are
not supported in WebEOC, this cannot be used in a parent to pull the childs data ID. The
<foreignkeyreference> tag can use the following attributes.
filter
sort
table - Name of the parent table.
<grouplist>
The <grouplist> tag adds the list of groups the user and/or position belongs to the XML for the board
to be used in conditional processing.
<if>
The <if> tag allows for conditional processing within the HTML. The <if> tag maps directly to an XSL:
<if> tag, and similar syntax should be used. Set the test attribute to conduct the test you want to
perform. The contents should be the output that results if the test is true. Use the @ symbol in front of
208
Administrator Guide
field names. Any WebEOC field referenced in the if statement must have a corresponding <eocfield>
tag somewhere in the view.
<td>
<attribute name="bgcolor">
<if test="@overdue='true'">red</if>
<if test="@overdue='false'">green</if>
</attribute>
</td>
<importbutton>
The <importbutton/> tag displays a button in the input view that allows users to import data from a
spreadsheet to the board.
Note: You can use this tag if you are a WebEOC Enterprise (7.7 or later) user or are using WebEOC
Professional (7.7 or later) and have a license for the Data Manager add-on. See Board Data for more
information.
<incidentname>
The <incidentname> tag displays the name of the incident the user is currently logged in to or, if
logged into a master view, a drop-down list of incidents that allows the user to filter the board by incident.
<incidentselector>
The <incidentselector> tag allows you to select a different incident for a board entry. It does not
show on incident independent or form views and is disabled for existing board entries when part of a
regional incident in a subscription board. This tag suppresses the master view drop-down list in boards.
<off>
The <off> tag contains text to display when a viewfilter is off. The parent must be a
<filterbutton> tag.
209
HTML Conventions

<on>
<b>My Requests</b>
</on>
<off>
My Requests
</off>
</filterbutton>
<on>
The <on> tag contains text to display when a viewfilter is on. The parent must be a <filterbutton>
tag.

<on>
<b>My Requests</b>
</on>
<off>
210
Administrator Guide

My Requests
</off>
</filterbutton>
<pdflink>
You can use the <pdflink> tag to add a button to the board:
<pdflink type="button">Print PDF</pdflink>

The <pdflink> tag can use the following attributes.
board - Name of the board.
enablejs - Allows JavaScript to run before rendering the PDF file.
name - Name on the button or the link text.
type - Specifies whether this is a button or a link.
view
WebEOC also offers a set of advanced PDF features that support formatting and display capabilities,
such as specifying header and footer text, determining how page breaks appear in the generated
document, and more.
The following attributes are available:
orientation Orientation of the pages in the PDF file; valid values are: landscape, portrait.
headerfootertextalign - Alignment of text in the header and footer; valid values are: left, center,
right, justify, default.
211
footertext - Text appearing in the footer.
_currentpage - Number of the current PDF page.
_pagecount - Total number of pages in the PDF.
headertext - Text appearing in the header.
HTML Conventions
footerfontsize - Size of the font in the footer.
headerfontsize - Size of the font in the header.
footerfloatx - Starting x coordinate of text in the footer.
footerfloaty - Starting y coordinate of text in the footer.
headerfloatx - Starting x coordinate of text in the header.
headerfloaty - Starting y coordinate of text in the header.
Control page break attributes are:
page-break-inside - avoid.
page-break-before - always.
page-break-after - always.
<pdflink type="button" orientation="landscape"

headerfootertextalign="center" headertext="For Official Use Only"
headerfontsize="12" footertext="Page _currentpage of _pagecount"
footerfontsize="12">Print PDF<pdflink>
<printbutton>
The <printbutton> tag creates a print button wherever the tag is located. The button itself is not
printed.
<relatedlist>
The <relatedlist> tag allows a view to display the many related records from another table to a
single record. It must be used in either an input view or a single-record display view that is linked from
another display view using a <viewlink> tag.
Functionally similar to the <eocrepeatallrecords> tag, be sure to set the type attribute to rl and
the table attribute to the name of the related table. You must use the table and type (rl) attributes on
any eocfields within the <relatedlist> tag. This tag also uses the sort attribute.
212
Administrator Guide
<relatedlist table="Deployments">
<eocfield name="FieldName" table="Deployments" type="rl" /> <br />
</releatedlist>
<relatedexpression>
Similar to the <expression> tag, the <relatedexpression> tag allows for calculations across
related tables. The table and name attributes must be set, and must be the many table. It may also
be used within an <expression> tag.
The name attribute displays the desired name of the <relatedexpression>.
The table attribute displays the name of the table that holds the foreignkey field to the current table.
Note: You can also use a <relatedexpression> tag inside an <expression> tag.
<relatedexpression name="totalcost" table="deployments">

Sum(cost*quantity)
</relatedexpression>
<returnbutton>
The <returnbutton> tag returns the user to the previous view.
<returnbutton>Return to List</returnbutton>
<search>
The <search> tag enables administrators to add searching capabilities to the display view.
Attributes allow searching across multiple fields, using multiple search tags, and searching over ranges,
such as a date range.
If you use multiple search tags, the operand "AND" is assumed. This means that the criteria specified in
all search tags must be met.
When this tag is combined with the <searchbutton> and <clearsearchbutton> tags, you can
set up a more customized look.
213
HTML Conventions
The tag can use the following attributes.
cleartext - Text appearing on the clear button. Default: Clear
exact - Specifies whether the search must be an exact match. If set to "true," the entire string
must be present in the record. The entire word or the first part of the word must be matched.
Example: If the search term is "rail," results can include: rail, railroad, railing. Results would not
include: derailment.
field - Displays the name of the field to be searched. Use the <field> sub-tag to specify
multiple fields.
range - Specifies whether to search based on a range of values. If set to "true," the display
includes text boxes for entering the "from" and "to" values of the range.
rangetext - Text appearing between the range's "from" and "to" text boxes. Default: To
searchtext - Text appearing on the search button. Default: Search
showcalendar - Specifies whether to show the calendar control to enable easy date entry when
searching datetime fields. Default: false
showclear - Specifies whether to display a clear button next to the search button. Default: false
<search field="description" exact="false" />
<searchbutton>
The <searchbutton> tag allows you to place the search button in a specific location.
This is most useful when using multiple search tags. This tag suppresses individual search buttons from
displaying next to search tags on the view. The text of the button corresponds to the contents of the tag.
When using multiple search tags, the operand "AND" is assumed. This means that the criteria specified in
all of the search tags must be met.
Refer also to <clearsearchbutton>.
<sortlink>
The <sortlink> tag enables the ability for users to click column headers to sort records in ascending
and descending order by the defined field.
214
Administrator Guide
<sortlink field="FieldName">
Label
</sortlink>
<space>
The <space> tag inserts a non-breaking space ( ) where the tag is located.
<userinfo>
<userinfo> - Displays information about a user, rendering as text in a pre-formatted div.
User info allows you to select a type of information to pull from user information. The <userinfo> tag
can use the following attributes.
realname
location
phonenumber
officephone
mobilephone
department
organization
supervisor
primaryemail
type
<userinfo type=realname/>
<validate>
The <validate> tag can be applied to any input[type=text] or textarea. When applied, WebEOC
verifies that the user-supplied value matches the specified format.
215
HTML Conventions
The following formats are available.
board
view
target
datetime Valid date and time.
date Valid date.
time Valid time.
integer Valid whole number.
decimal Valid number, with or without a decimal point.
<input type="text" name="due_date" validate="datetime" />
<value-of>
The <value-of> tag is used to display a field a second time after having already displayed it using an
<eocfield> tag.
<value-of select="@fieldname"/>
<viewlink>
The <viewlink> tags provide a mechanism to jump to another view from within a board. For example,
a summary list may have a <viewlink> tag that allows users to open a view showing a single record's
detail.
You can also use the board attribute in the tag to navigate to views in different boards.
The tag can use the following attributes:
board - Name of the board that contains the view to link to.
name - Name of the view to link to.
table - Name of the table. If the link is to another table, this attribute is required.
216
Administrator Guide
target - Specifies whether the view should open in a dialog box or a new browser window. When
not included, the user leaves the existing view and navigates to the named view. When set to
dialog box, two more attributes can be used:
refreshid - Identifier of an HTML element that should refresh when the user closes the dialog
box; only the content of the target is refreshed.
ondialogclose - JavaScript function that is executed when the user closes the dialog box;
this is used when more complex processing (beyond refreshing) is necessary.
type - Specifies whether this is a button or a link. The content of the tag displays on the button or
as the link text.
<viewlink name="Input" target="dialog" type="button">New

Record</viewlink>
You can also use this tag in conjunction with an <embedview> tag to change the view that shows in the
<embedview> tag. The view can be from the same or a different board in a view. The embedded view
works like any other view, including automatic refresh when new data is added. The <embedview> tag
is used to embed one view inside another. It is rendered as an iframe.
The target attribute of the <datalink> tag specifies which <embedview> tag is to be replaced with
the new view. This attribute can be used in any view, but it is only effective when the view is being shown
within an <embedview> tag.
The following are valid values for this attribute:
self - Replaces everything in the current <embedview> with the view specified. This is the
default.
parent - Replaces the entire view in which it is embedded (that is, its "parent"). If the view is not
within an <embedview> tag, it acts just like the "self" value.
top - Replaces the entire window. If the view is not within an <embedview> tag, it acts just like
the "self" value.
All three values operate up through the hierarchy of <embedview> tags in the current window. The
current window is always "top."
217
HTML Conventions
If a value other than those listed above is specified for the attribute, it is assumed to be the name of the
ID attribute on an <embedview>. For example, if you specify "target="previewdisplay," it is assumed
that an associated <embedview> is set up similar to the following:
<embedview enablefooter="false" id="previewdisplay" view="PlaceHolder"

width="100%" frameborder="0" height="600"/>
This option works differently than the three values listed above, as the <embedview> must exist in the
current view.
Multi-tiered Lists
Multi-tiered lists are created and defined in the Lists Manager. After you create the lists, they can be
added to a board using the Advanced Board Editor. The following example shows the code to use to
implement multi-tiered lists in your boards. In the example below, from_list is the name of your list, and
from_sublist is the name of your sublist. The from_sub_sublist is the name of your sub-sub-list.
Replace these items with the names of the lists you have created.
<select name="from_list" list="Multi-Tiered List" />

<select name="from_sublist" list="Multi-Tiered List"
parent="from_list" />
<select name="from_sub_sublist" list="Multi-Tiered List"
parent="from_sublist" />
Refer to The Lists Manager for details on creating and defining lists.
Chart and Data Tags

Increasingly, WebEOC administrators are seeking to convey information in graphical formats that
maximize information transfer while minimizing the screen real estate used. WebEOC dashboard views,
executive overviews, and display view-based summary reports support the display of numerical data in
chart and graph forms. Use the chart tag and data subtag to create these visual representations.
218
Administrator Guide
<chart> Tag
The <chart> tag is supported in any display view, and appears in PDFs generated using the
<pdflink> tag. The <chart> tag is not supported in remote boards or on the PDA interface. The tag
supports the following attributes:
type: Controls the type of chart. The supported types are pie, line, and bar.
legend: A Boolean value that specifies whether a legend is included. The default is false.
legendplacement: A string value that specifies the placement of the legend. The supported
values are top, middle, and bottom. The legend automatically appears to the right of the chart.
labels: Specifies whether values are labeled when not using a legend. The default is true.
backgroundcolor: Specifies the background color of the chart. Any HTML color can be used; the
default is white.
textcolor: The color of text in the legend or labels.
font: The font of the text in the legend or labels.
width: The width of the chart, in pixels.
height: The height of the chart, in pixels.
groupby: Causes chart data to be collated by the indicated value and is only specified when the
<chart> tag is outside of the <eocrepeatallrecords>. It is optional on board and pie

charts, but is required for line charts. In line charts, the groupby attribute provides the x-axis of
the chart.
filter: Condition that can be used to filter data. It is only applied when the <chart> tag is used
outside of the <eocrepeatallrecords>.
<dataexpression> Subtag
The <dataexpression> subtag specifies the fields or values that populate the chart and work much
like expression tags. When the <chart> tag is used outside of the <eocrepeatallrecords>, the
data tag must be an aggregate function.
The <dataexpression> subtag supports the following attributes:
219
label: Text of the label or legend for this value.
HTML Conventions
color: Color of the value in the chart.
Using Chart Tags

Below are three basic examples of charts that can be created using <chart> and
<dataexpression> tags.
Pie Chart
This example is a theoretical overall shelter availability pie chart that would be specified outside the
<eocrepeatallrecords> tag.
<chart type="pie" filter="status!='Closed'">
<dataexpression label="Occupied"
color="red">sum(occupancy)</dataexpression>
<dataexpression label="Available" color="green">sum(capacityoccupancy)
</dataexpression>
</chart>
Bar Chart
The following bar chart uses the groupby attribute to show the number of tasks in a Mission/Task board
for each status.
<chart type="bar" groupby="status" legend="true" labels="false">

<dataexpression>count(*)</dataexpression>
</chart>
220
Administrator Guide
Line Chart
This example uses a line chart to show the number of position log entries over time.
<chart type="line" groupby="convert(varchar,entrydate,101)">

<dataexpression label="entries">count(*)</dataexpression>
</chart>
221
Glossary
A
admin profile: Set of administrative functions and permissions that can be assigned to users. Users can
perform only those administrative tasks defined in the profile.
agency template: Default template that contains your agency's name, logo, font, and color scheme. It
can also be used to configure login policy statements and messages that appear to users when
they log in to WebEOC.
audit log: Tracks and records administrative events that occur in WebEOC. The log supports monitoring
and assessment of administrator and user activities and can aid in troubleshooting.
B
board: Customizable system component designed to transmit and share information between system
users in real time. Boards are also referred to as status boards.
C
checklist: Automated procedures and lists of steps used to track the progress of tasks. Administrators
can indicate when a task is due.
CIMS: Crisis Information Management System.
control panel: Window that contains all of the features and functions to which the logged in user has
access. These can include boards, menus, tools, plugins, links, and more.
D
data link: Enables posting the same data to multiple status boards at once. One- and two-way linking are
supported.
display view: Configuration of how a board displays data to users. Administrators can design and
configure display views.
dual commit: Means of setting up servers so that they can communicate and share information across
and among agencies that use WebEOC. Users with access to shared boards can view and post
information from within their installation of WebEOC.
222
Administrator Guide
E
ETime: Amount of time necessary to complete a step or task in a checklist. Configuring an ETime sets
when the task is due to be completed. For actual incidents and simulations, the ETime is
calculated from the start of the incident or simulation. For an actual incident, if the task has not
been marked as completed or not applicable when the ETime is reached, the status appears in
red to indicate it is past due. For a simulation, when the ETime is reached, the task is
automatically posted to the simulation's status board.
F
file library: Means by which WebEOC users can upload and share files and documents with other
WebEOC users.
G
group: Set of privileges that grants board, plugin, link, and menu access to the users assigned to the
group. A user's group governs the tools and functions available to them in their control panel. The
group profile can also grant other user permissions, such as read and write privileges. Groups are
generally based on user roles or positions assigned during an incident or on information the users
require during an incident.
H
HTML: Hypertext Markup Language. In WebEOC, an experienced administrator can use HTML code to
build and maintain boards.
I
ICS: Incident Command System.
incident: Any unplanned or planned event, emergency, or other occurrence that requires a response.
input view: Space in a board where the user can enter new data or update existing information.
Administrators can design these data entry views.
L
list: Related items presented to users as options from which they can select when updating a field on
boards and forms. A list can also be used as a filter on a status board. A multi-tiered list contains
two or more levels of sub-lists.
223
Glossary
list view: Set or subset of data for a board that allows the user to view only the data that is immediately
necessary. It can be used to create a high-level view of a particular area or subject.
M
MapTac: Plugin. Tool used to publish image files, such as maps and dispersion models. Administrators
can place markers, labels, and shapes on the map or image. These can be used to brief
members of the response team and other users on aspects of the incident.
master view: Option to track multiple incidents simultaneously; selected incidents are "rolled up" into the
master view.
menu: Group of boards, plugins, and links appearing in the control panel as a single link. Clicking the link
opens the menu, providing access to each item in the list.
message: Internal mechanism for transmitting incident or other information to users via the control panel
and Messages tool.
P
PAC: Position Access Code; serves as a layer of password protection for a position. Administrators
create PACs as a way of controlling the users who can register for a position.
plugin: Set of features and functions that can be added to or enabled within your WebEOC system.
Checklists, File Library, MapTac, and Messages are examples of standard plugins.
position: Defines the user's role in the response organization. A single user can be assigned multiple
positions. If assigned to more than one, the user is prompted to select the appropriate position
upon logging in to WebEOC.
R
remote board: Feature that allows users in one agency to access boards hosted by another agency for
the purpose of sharing information across agencies. All WebEOC installations that use this
feature view the same sets of data on the same boards.
report: Means of retrieving and reporting on specific sets of data, such as an incident. WebEOC has
preformatted reports and offers ad hoc reporting capabilities.
S
session: Period of time in which a user is logged in to WebEOC.
224
Administrator Guide
simulation: Scenarios that can be added to WebEOC and run as needed for training, drills, and
exercises. They can be designed to simulate inputs that would occur during an actual incident
while minimizing the number of support personnel needed to participate in the scenario.
U
user: Individual who has credentials and can log in to and use WebEOC. Some users are administrators
or are granted a subset of administrative rights.
user, group, position, incident: Each user must be assigned to at least one position. Each position
must be assigned to at least one group. Each group must be assigned to at least one incident.
225
Index
A
access
code 28, 29, 30
general manager 180
master view 64
position 28, 29, 30
report 26
account
add 19
change 22
delete 23
edit 22
lock 24
multi 19
plan 18
remove 23
single 19
type 19, 186
unlock 24
user 15, 18, 19, 22, 23, 24, 181
activity
incident 57
report 25, 57
user 25
add
account 19
board 99, 138
data link 122
display view 109
dual commit 145
filter 116
group 38
incident 54
input view 103
link 154
list 158
master view 65
menu 168
permission 44
position 30
profile 174
report 69, 74
server 142
simulation 82
sublist 160
template 137
user 19
admin
manager 8
profile 174, 175, 176
window 8
admin profile 173

manager 172
administrator 2
report 26
agency
template 134, 137, 138
agency template
manager 134
archive
delete 63
incident 60, 61, 62, 63
manager 60
remove 63
simulate 62
view 61, 62
assign
permission 43
process 43
assignment
board 133
report 133
audit
log 177, 179
audit log
manager 176
B
board 95
add 99
advanced 94
assignment 133
build 94
component 187
configure 128, 131, 138, 149
data 61, 125, 126
delete 100
display view 94, 109, 187
download 11
dual commit 145, 148
edit 95
email 128
export 120
filter 114, 116, 119
history 102
HTML options 93
import 119
input view 94, 103, 187
link 122
manager 91
message 131
option 94
226
Administrator Guide
permission 48
plan 92
remote 140, 148, 149
remove 100
report 69, 74, 79, 133
send 127, 145
server 127, 145
setup 149
share 120, 139
standard 69
status 13, 92
table 94
upload 119
view 61, 101
build
board 94
C
change
account 22
data link 122
display view 109
filter 116
group 42
incident 56
input view 103
item 163
link 155
list 163
master view 66
menu 170
permission 45
position 32
profile 175
server 143
simulation 84
user 22
chart
tag 218
CIMS 1
clear
log 179
Client Hub 11
code
access 28, 29, 30
position 28, 29, 30
component
board 187
configure
board 128, 131, 138, 149
email 128, 185
message 131
control panel 5
message 131
227
overview 5
convention
HTML 187
create
report 69
custom
report 74
D
data
board 61, 125, 126
export 126
import 125
link 122
plugin 62
data link 122
add 122
change 122
edit 122
delete
account 23
archive 63
board 100
filter 119
group 43
incident 56
link 156
list 164
master view 66
menu 171
permission 46
position 33
profile 176
report 79
server 144
simulation 86
display
view 109
display view 101
add 109
board 187
change 109
edit 109
history 102
download
board 11
dual commit 147, 148, 149
add 145
board 145, 148
manager 139
plan 140
prerequisites 140
server 141, 142, 143, 144, 146, 149
edit
account 22
board 95
data link 122
display view 109
filter 116
group 42
incident 56
input view 103
item 163
link 155
list 163
master view 66
menu 170
permission 45
position 32
profile 175
server 143
simulation 84
user 22
view 188
editor
HTML 188
email
board 128
configure 185
general manager 185
end
session 50
entry
incident 54
static 54
event 52
export
board 120
data 126
list 166
simulation 89
general
manager 179
general manager
access 180
email 185
options 180
security 181
generate
PAC 29, 30
report 26, 27, 34, 35, 47, 48, 57, 58, 59, 74,
133
genrate
report 25
get started 4
group
add 38
change 42
delete 43
edit 42
manager 36
permission 38
plan 37
remove 43
file
storage 181
filter
add 116
board 114, 116, 119
change 116
criteria 114
delete 119
edit 116
remove 119
import
board 119
data 125
list 164
simulation 89
incident 52
active 58
activity 57
add 54
archive 60, 61, 62, 63
change 56
delete 56
H
Help 2, 11
history
board 102
display view 102
input view 102
view 102
HTML 187, 189, 192, 218
editor 188
list 218
options 93
report 74
tag 134, 189, 192, 218
228
Administrator Guide
edit 56
entry 54
manager 52
map 146
remove 56
report 58, 59
set up 53, 54
simulate 82, 84, 86, 87, 89
view 61, 62
input
view 103
input view 101
add 103
board 187
change 103
edit 103
history 102
tag 189
item
change 163
edit 163
list 158
sublist 160
L
link
add 154
change 155
data 122
delete 156
edit 155
manager 154
one way 122
remove 156
two way 122
list
add 158
change 163
delete 164
edit 163
export 166
HTML 218
import 164
item 158
manager 156
multi-tiered 218
remove 164
share 166
tag 218
user 17
lock
account 24
user 24
lockout 181
229
log
audit 177, 179
clear 179
search 177
sort 177
view 177
log in
master view 64
login
session 49, 50
M
manager
admin 8
admin profiles 172
agency template 134
archive 60
audit log 176
board 91
dual commit 139
general 179
incident 52
links 154
lists 156
menus 167
positions 27
report 68
sessions 48
simulator 80
users 15
manger
groups 36
map
incident 146
message 147
Mapper Professional 13
master
view 63, 64, 65, 66, 67
master view
access 64
add 65
change 66
delete 66
edit 66
log in 64
manage 67
manager 63
remove 66
menu
add 168
change 170
delete 171
edit 170
manager 167
remove 171
message
board 131
map 147
queue 147
O
option
board 94
general manager 180
HTML 93
query 73
security 181
P
PAC 28
generate 29, 30
register 29
report 35
Passenger Data 13
password 181
permission
add 44
assign 43
board 48
change 45
delete 46
edit 45
group 38
process 43, 44, 45, 46, 47, 48
remove 46
report 47
plan
account 18
admin profile 173
board 92
dual commit 140
group 37
user 18
plugin 11, 13
data 62
Mapper Professional 13
Passenger Data 13
Resource Request and Deployment 13
RRDM 13
standard 11
Team Manager 13
view 62
position
access 28, 29, 30
add 30
change 32
code 28, 29, 30
delete 33
edit 32
manager 27
remove 33
report 26, 34, 35
user 26
print
simulation 86
process 91
agency template manager 134
assign 43
boards manager 91
dual commit manager 139
links manager 154
lists manager 156
menus manager 167
peremission 43
permission 44, 45, 46, 47, 48
profile
add 174
admin 174, 175, 176
change 175
delete 176
edit 175
plan 173
remove 176
Q
query
Boolean 73
option 73
statement 73
queue
message 147
R
register
PAC 29
user 29
remote
board 140, 148, 149
remove
account 23
archive 63
board 100
filter 119
group 43
incident 56
link 156
list 164
master view 66
menu 171
permission 46
230
Administrator Guide
position 33
profile 176
report 79
repor
administrator 26
report
access 26
activity 25, 57
add 69, 74
assignment 133
board 69, 74, 79, 133
create 69
custom 74
delete 79
generate 25, 26, 27, 34, 35, 47, 48, 57, 58,
59, 74, 133
HTML 74
incident 58, 59
manager 68
PAC 35
permission 47
position 26, 35
position matrix 34
process permissions 48
remove 79
run 25, 26, 27, 34, 35, 47, 48, 57, 58, 59, 74,
133
usage 27
user 25, 26
view 25, 26, 34, 35, 47, 48, 57, 58, 133
Resource Request and Deployment 13
RRDM 13
run
report 25, 26, 27, 34, 35, 47, 48, 57, 58, 59,
74, 133
simulation 87
S
search
log 177
security
general manager 181
lockout 181
option 181
password 181
self-registration 29
send
board 127, 145
server
add 142
board 127, 145
change 143
delete 144
dual commit 141, 142, 143, 144, 146, 149
231
edit 143
target 127, 140, 141, 142, 143, 144, 145, 146
session
end 50
login 49, 50
manager 48
terminate 50
user 49, 50
view 49
sessioni
login 50
set up
incident 53, 54
setup
board 149
share
board 120, 139
list 166
simulation 89
simulate
archive 62
incident 82, 84, 87, 89
simulation
add 82
change 84
delete 86
edit 84
export 89
import 89
print 86
run 87
share 89
upload 89
simulator
manager 80
sort
log 177
user 17
standard
board 69
statement
query 73
static
entry 54
status
board 13, 92
storage
file 181
sublist
add 160
item 160
system 172
admin profiles manager 172
audit log manager 176
general manager 179
lock 24
manager 15
multi 19
plan 18
position 26
positions manager 27
register 29
report 25, 26
session 49, 50
sessions manager 48
single 19
sort 17
unlock 24
users manager 15
T
tag
chart 218
custom 192
HTML 134, 189, 192, 218
input view 189
list 218
supported 189
Team Manager 13
template
add 137
agency 134, 137
terminate
session 50
tools
admin 8
type 186
account 19
U
unlock
account 24
user 24
upload
board 119
simulation 89
usage
report 27
review 27
user 15
account 15, 18, 19, 22, 23, 24, 181
activity 25
add 19
change 22
edit 22
groups manager 36
list 17
V
view 101
archive 61, 62
board 61, 101
display 109
edit 188
history 102
incident 61, 62
input 103
log 177
master 63, 64, 65, 66, 67
plugin 62
report 25, 26, 34, 35, 47, 48, 57, 58, 133
session 49
usage 27
W
WebEOC 1, 2
audience 2
purpose 2
window
admin 8
edit view 188
232

Administrator Guide v8.0

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Administrator Guide v8.0

Uploaded by

Copyright:

Available Formats

WebEOC

2015 Intermedix Corporation. All rights reserved.

WebEOC and ESi are registered trademarks of ESi Acquisition, Inc.

Address any questions, comments, or suggestions to:

Be easy to configure and tailor to the conditions of the agency.

Integrate public health into emergency management.

Operate within a variety of network configurations.

Have help desk support on a 24-hour basis.

WebEOC Home Page

at the top of the page.

in the upper left corner of the Home page.

Control Panel Overview

Open the control panel by clicking the control panel icon

in the upper left corner of the Home page.

of a link automatically opens that item in a new window.

preceding a menu item alerts users when a change has been

in the tab header and changing the updated tabs color to

to the left and right of the tabs.

Admin Manager Overview

WebEOC administration features.

The Incidents tab contains the following managers:

The Process tab contains the following managers:

Links: Set up and configure hyperlinks to URLs, other systems, or files.

The System tab contains the following managers:

General: Access security options, email servers, and more.

WebEOC Fusion: Set up and manage your WebEOC Fusion connection(s).

The Plugins tab contains the following managers:

File Library: Manage folders and assign permissions.

Help and Client Hub

. The User Help opens in a new browser

WebEOC Client Hub

Documentation - Download the latest documentation, including manuals, Quick Reference

buttons. Steps and sub-steps can be marked as Complete, Open, Previously

individual or all status boards in an agencys WebEOC system. Because WebEOC

Users can search for information across all their boards.

Upload, organize, and share documents and files.

The Users Manager

Read the following sections to learn about:

Position Access Code (PAC)

Position Access Code

Configuring the Users Window

2. Select the columns to display.

Planning a New User Account

Note: The sub-administrator account type is available in WebEOC Enterprise only.

Single-user or Multi-user Accounts

Creating a User Account

For a Partial Administrator, assign one or more Admin Profiles.

Editing an Existing User Account

For a Partial Administrator, assign one or more Admin Profiles.

, then click OK to confirm the action..

Deleting a User Account

3. In the confirmation window, click OK.

next to the user account you want to delete.

Locking a User Account

Unlocking a User Account

Viewing the User Activity Report

Viewing the Administrative Access Report

Administrative Access Report - Export CSV to export it to a CSV (comma-separated value)

Viewing the User Position Report

Viewing the Usage Report

The Positions Manager

Position Access Codes

PACs and User Self-registration

Generating a PAC for a Single Position