cust_lang Table (320)
This table contains entries for customer languages.Fields
| Name | Description | Type | Nullable |
|---|---|---|---|
| id | The primary key (auto-incremented) | PK | No |
| name | The name/alias for this language. | String(255) | Yes |
| lang_code | A short code for this language ('no', 'dk', etc). Used in pathname to templates. | String(5) | Yes |
| virtual_domain | The virtual domain which should trigger this language (e.g. 'support.company.dk' vs. 'support.company.uk') | String(255) | Yes |
| web_domains | The domains from where the user should originate (when surfing) in order to trigger this language. Commaseparated list. | String(255) | Yes |
| email_domains | Commaseparated list of toplevel domains from where an email should originate in order to trigger this language. | String(255) | Yes |
| email_header | The email header line for this language ('Please keep the subject in any replies…'). | String(255) | Yes |
| kb_root | The reference to the FAQ category which is the root category for this language (for separating the FAQ per language). | FK kb_category | Yes |
| is_default | Bool indicating whether this language is the default (fallback) language. | Bool | Yes |
| iso_code | A two letter iso code for this customer language | String(63) | Yes |
Indexes
| Fields | Types | Description |
|---|---|---|
| kb_root | FK | Index |
Relationships
| Table | Description |
|---|---|
| chat_topic | This table contains chat topics. |
| contact | Companies and Organizations. |
| cust_category | This table contains entries for categories exposed through a customer language. |
| cust_config | This table contains JSON structures used for customizing the customer center |
| kb_category | Knowledge base folder hierarchy |
| mail_in_filter | This table contains entries for the mailboxes the eJournal system is fetching mail from (POP3 or IMAP). |
| person | Persons |
| reply_template_body | Contains the body of the reply templates in different languages |
Replication Flags
- None
Security Flags
- No access control via user’s Role.