Implementing IncidentAnalytix (IA) starts with deciding what data is important to track for your organization. Use the Tables and Columns document below to help you identify which data tables are most important to track.
This database schema outline provides an in-depth view of all the Incident Tables and Columns in IA. These are the numerous Incident Data Types (Incident Tables) that you can track in IA. To set up your IA solution first decide what Data Types are important for your organization to track for your initial configuration.
The Table Summary below shows an overview checklist of all the incident tables in IncidentAnalytix. The Table Details below all the Columns in each table. Table Names are color-coded based on their hierarchy within the database schema.
Level 1: Parent Table (Green)
Level 2: Child Tables of Level 1 (Blue)
Level 3: Child Tables of Level 2 (Violet)
Level 4: Child Tables of Level 3 (Brown)
If you wish to gather information about a child table (for example Person Injury), you must also include a link to its parent table (Person) and the parent table value must be added first. For example, to include Person Injury, you must first add data about the Person (parent object) before you can add data about the Person Injury (child object). If a table is a Child Table to another table, it must include the ID to the Parent Table. These are marked as Lookup Parent in the Attribute Type and are handled automatically by the system whenever a new child record is added.
There are a number of optional Lookup Tables that provide data for dropdown lists in the application. Columns that link to Lookup Tables are marked as Lookup in the Attribute Type and out-of-the-box they are optional. Check off the Incident Tables that you plan to include in your application and then review the associated Lookup Tables for each Incident Table you plan to use. Sample Microsoft Excel copies of the Lookup Tables are available for you to create Lookup values that fit your organization’s needs. The Lookup Tables are described in a separate document.
The document is setup up for you to check the box next to each Table that you want to include in your implementation. We recommend you start with the base level of what you need. You can always add additional tables into your application.
Out of the box, all tables are enabled across all of the included Security Roles which means that they are visible in the navigation sidebar and on individual pages. If you decide not to use a particular subset of tables, removing those from some or all of the Security Roles will remove them from being visible to users. They can be enabled by turning them back on in Security Roles