Enate Data Dictionary
Enate Warehouse Database Dictionaries
2024.1 Warehouse Database Dictionary
2023.5 Warehouse Database Dictionary
2023.4 Warehouse Database Dictionary
2023.3 Warehouse Database Dictionary
2023.2 Warehouse Database Dictionary
2023.1 Warehouse Database Dictionary
2022.6 Warehouse Database Dictionary
2022.5 Warehouse Database Dictionary
2022.4 Warehouse Database Dictionary
2022.3 Warehouse Database Dictionary
2022.2 Warehouse Database Dictionary
2022.1 Warehouse Database Dictionary
2021.2 Warehouse Database Dictionary
2021.1 Warehouse Database Dictionary
Database Design Standards
Standard tables are prefixed with ’tbl’.
Table and field names are written in CamelCase.
Standard fields are prefixed with an underscore ‘_’.
Extension fields which are dynamically generated based on your unique configuration in Enate are not prefixed with an underscore ‘_’.
Here is a brief overview of the design standards across the data warehouse:
Table Structure Explanation
The following sections cover the main tables within the data warehouse, providing details on context (Customer, Contract, Service, and Process), work items (packets), communications, users, and configuration attributes. For each table, the column names, data types, and descriptions are provided, highlighting primary and foreign keys.
Primary keys [PK] uniquely identify a row/record within a given table while
Foreign keys [FK] represent primary keys in another table and can be used to join on.
The central table in the warehouse is tblPackets which holds key information on all packets within Enate – 1 row per work item in its current state. Please note, packets are work items - either a ticket / case / action. All packets belong to a certain ‘Context’, this is the combination of Company, Contract, Service and Process, as built within Enate – data on which can be found in tblProcesses, tblServices, tblContracts and tblCompanies.
For specific details on different types of work items (ticket / case / action), refer to tblTickets, tblCases, and tblActions accordingly. Furthermore, attribute details i.e. configurations on how work items should behave such as estimated duration, can be found in tblTicketAttributes, tblCaseAttributes, and tblActionAttributes.
User details can be found in tblUsers along with user activity for each work item in tblPacketActivities.
Last updated
Was this helpful?