The first step to start using this template is by importing your employees in the corresponding table, followed by defining categories, and causes for incidents.

Once this information is filled in, you can start reporting incidents. This is possible through either the database UI, the database form or the application. There are multiple views in the Incidents table to obtain a good overview of all the incidents from different perspectives.

Incidents are solved by adding responses to them. A response can use a predefined action plan. Adding and editing responses to an incident can be done both in the database UI or through the application.

Database: Incident Management

Employees

Fields

• Name (Text)

• Email (Email)

• Phone (Phone number)

• Picture (File)

• Job role (Text)

• Reported incidents (Link to table)

• Assigned incidents (Link to table)

• Responses (Link to table)

• Count reported (Count)

• Count assigned (Count)

• Count responses (Count)

• Password (Password)

Views

• All employees (Grid)

• Employees with reports, assignments or responses (Grid)

• Gallery: all employees (Gallery)

Risk categories

Fields

• Name (Text)

• Incidents (Link to table)

• Count incidents (Count)

• Count open incidents (Formula)

Views

• All categories (Grid)

Action plans

Fields

• Name (Text)

• Description (Text)

• Used in response (Link to table)

• Count usage (Count)

Views

• All action plans (Grid)

• Unused action plans (Grid)

• Used action plans (Grid)

• Used action plans for multiple responses (Grid)

Incidents

Fields

• Name (Text)

• Description (Text)

• Reporter (Link to table)

• Severity level (Single select)

• Date occurred (Date)

• Status (Single select)

• Source (Single select)

• Solution due date (Date)

• Category (Link to table)

• Escalated (Boolean)

• Recurring (Boolean)

• Assigned to (Link to table)

• Attachments (File)

• Responses (Link to table)

• Has action plan (Formula)

• Reporter name (Rollup)

• Assignee name (Rollup)

• Category name (Rollup)

• Last response date (Rollup)

• Caused by (Link to table)

• Cause name (Rollup)

• Has action plan symbol (Formula)

Views

• All incidents (Grid)

• All incidents grouped by cause (Grid)

• All incidents grouped by reporter (Grid)

• All incidents grouped by assignee (Grid)

• All incidents grouped by category (Grid)

• Open incidents (Grid)

• Open incidents beyond solution due date (Grid)

• Open incidents without responses (Grid)

• Internal incidents (Grid)

• External incidents (Grid)

• Escalated incidents (Grid)

• Recurring incidents (Grid)

• Incidents where action plan is used (Grid)

• Incidents stacked by status (Kanban)

• Incidents stacked by severity level (Kanban)

• Calendar: incident occurrence date (Calendar)

• Calendar: incident solution due date (Calendar)

• Report new incident (Form)

Incident causes

Fields

• Name (Text)

• Description (Text)

• Incidents (Link to table)

• Count incidents (Count)

Views

• All incident causes (Grid)

Responses

Fields

• Name (Text)

• Description (Long text)

• Date (Date)

• Owner (Link to table)

• Outcome (Single select)

• Incident (Link to table)

• Action plans (Link to table)

• Incident name (Rollup)

• Owner name (Rollup)

• Uses action plan (Formula)

• Action plan ID’s (Formula)

Views

• All responses (Grid)

• Responses that used an action plan (Grid)

• Responses that NOT used an action plan (Grid)

• All responses grouped by incident (Grid)

• All responses grouped by owner (Grid)

• Responses stacked by outcome (Kanban)

• Calendar: response date (Calendar)

Application: Incident Management

shared

Data sources

• Incidents by category

• Employees (incidents)

• Incident causes

• Action plans

Login

Data sources

Actions (event)

• open_page (after_login)

Incident Management

Data sources

• Incidents by category

• Incidents by cause

• Incidents by employee

• Open incidents beyond due date

• Open incidents without response

• All incidents

Actions (event)

• logout (click)

• open_page (click)

Incident Details

Data sources

• Incident details

• Incident responses

Actions (event)

• update_row (submit)

• logout (click)

• refresh_data_source (submit)

• open_page (click)

Add New Incident

Data sources

• Get incident

Actions (event)

• logout (click)

• create_row (submit)

• open_page (click)

• open_page (submit)

Response Details

Data sources

• Response details

• Response action plans

Actions (event)

• update_row (submit)

• logout (click)

• refresh_data_source (submit)

• open_page (click)

Add New Response

Data sources

• Get incident

• Get response

Actions (event)

• logout (click)

• create_row (submit)

• open_page (click)

• open_page (submit)