ej_category Table (257)
Some tooltip text!
• 4 minutes to read
• 4 minutes to read
This table contains categories, in which tickets are categorized. The categories are organized in a hierarchial manner.
Fields
| Name | Description | Type | Null |
|---|---|---|---|
| id | The primary key (auto-incremented) | PK | |
| parent_id | The parent category for this category. -1 if this is a toplevel category. | FK ej_category | |
| name | The (short) name of this category. E.g. 'support'. | String(64) | ● |
| category_master | The user associated with this category. | FK ejuser | ● |
| fullname | The fullname (compiled from parents' names) for this category. E.g. 'norway/product A/support'. | String(255) | ● |
| flags | A bitmask representing flags for this category. | Enum TicketCategoryFlags | ● |
| delegate_method | An integer indicating the delegation method for this category. | Enum TicketCategoryDelegateMethod | ● |
| delegate_counter | A delegate counter, incremented by 1 for every delegation | Int | |
| external_name | The external name for this category, used for the customer frontend. | String(255) | ● |
| assignment_lag | Number of minutes we shall override the assignment if a customer sends consecutive messages to this category | Int | ● |
| reply_template | Reply template to merge with messages posted in this category | FK reply_template | ● |
| notification_email | Comma separated list of addresses to notify when requests are redelegated to (unassigned) in this category. | String(2047) | ● |
| closing_status | Default status for new tickets, if 0 then there is a fallback to a user-dependent value | FK ticket_status | ● |
| msg_closing_status | Default status for new messages, if 0 then there is a fallback to a user-dependent value | FK ticket_status | ● |
Indexes
| Fields | Types | Description |
|---|---|---|
| id | PK | Clustered, Unique |
| parent_id | FK | Index |
| category_master | FK | Index |
| reply_template | FK | Index |
Relationships
| Table | Description |
|---|---|
| category_membership | This table connects users to categories (many-to-many). |
| chat_topic | This table contains chat topics. |
| cust_category | This table contains entries for categories exposed through a customer language. |
| ej_category | This table contains categories, in which tickets are categorized. The categories are organized in a hierarchial manner. |
| EjCategoryGroupLink | User group link table for EjCategory, for mass handling ej_category members |
| ejuser | This table contains entries for the users of the system. |
| kb_group | This table contains FAQ groups. A group is a cluster of entries (potentially located anywhere in the FAQ hierarchy). A group is located in a certain category. |
| mail_in_filter | This table contains entries for the mailboxes the eJournal system is fetching mail from (POP3 or IMAP). |
| ms_filter | This table contains email filters. These are the filters allowing you to do advanced parsing of incomming emails. |
| notify | This table contains the pop-up messages displayed for users for various events, such as 'new ticket', etc. |
| reply_template | Templates for automatic and manual replies to emails/sms organized hierachically |
| role_category | Category membership associated with a role |
| s_link | Links in messages to measure success rate of a campaign. |
| ticket | This table contains the tickets (requests) of the system. Its purpose should be evident. |
| ticket_status | This table user defined ticket status values. |
Replication Flags
- None
Security Flags
- No access control via user's Role.