Emails
From MintHCM Wiki
| Emails | |
|---|---|
| Name: | Emails |
| Tech Name: | Emails |
| Class Name: | |
| Type: | Standard |
| Template: | Security_groups, Assignable, Basic |
| Custom Module: | No |
| Auditable: | No |
| Importable: | No |
| Reportable: | Yes |
| Hide module on Main Page: | No |
Contents
[hide]Short Description
Business Description
Missing User input
Collapse
Related Process Steps
| Process | Step Title | Short Description |
|---|---|---|
| Administration Guide | Email Settings | Manage outbound and inbound emails. The email settings must be configured in order to enable users to send out email and newsletter campaigns. |
Related Features
Structure
Collapse
Fields
| Name | Type | Required | Validations | Visible | Editable |
|---|---|---|---|---|---|
| Assigned to | relate | No | Yes | Yes | |
| Category | enum | No | Yes | Yes | |
| Created By | relate | No | Yes | No | |
| Date Created | datetime | No | Yes | No | |
| Date Modified | datetime | No | Yes | No | |
| Date Sent/Received | datetime | No | Yes | Yes | |
| Email Status | enum | No | Yes | Yes | |
| Email Template | relate | No | Yes | Yes | |
| Flagged | bool | No | Yes | Yes | |
| Has Attachments | function | No | Yes | Yes | |
| IMAP Keywords | varchar | No | Yes | Yes | |
| Indicator | function | No | Yes | Yes | |
| Intent | varchar | No | Yes | Yes | |
| Last Synchronised | datetime | No | Yes | Yes | |
| Message ID | varchar | No | Yes | Yes | |
| Modified By Name | relate | No | Yes | No | |
| Opt In | function | No | Yes | Yes | |
| Orphaned | bool | No | Yes | Yes | |
| Parent Type | varchar | No | Yes | Yes | |
| Related To | parent | No | Yes | Yes | |
| Reply To Status | bool | No | Yes | Yes | |
| Subject | function | No | Yes | Yes | |
| Subject | name | No | Yes | Yes | |
| Type | enum | No | Yes | Yes | |
| bcc_addrs_names | varchar | No | Yes | Yes | |
| cc_addrs_names | varchar | No | Yes | Yes | |
| description | text | No | Yes | Yes | |
| description_html | emailbody | No | Yes | Yes | |
| raw_source | varchar | No | Yes | Yes | |
| reply_to_addr | varchar | No | Yes | Yes | |
| to_addrs_names | varchar | No | Yes | Yes |
Collapse
Relationships
| Laft | Type | Right | Short Description | Relationship |
|---|---|---|---|---|
| Candidates | many-to-many | Emails | Many Candidate records can be related to many Email records | Relationship: Candidates - Emails |
| Emails | one-to-many | Meetings | One Email record can have many related Meeting records, but a specific Meeting record can be related to only one Email record. | Relationship: Emails - Meetings |
| Emails | one-to-many | Notes | One Email record can have many related Note records, but a specific Note record can be related to only one Email record. | Relationship: Emails - Notes |
| Project | one-to-many | Emails | Flex relate used in Project | Relationship: Project - Emails |
| Project Tasks | one-to-many | Emails | Flex relate used in Project Task | Relationship: ProjectTask - Emails |
| Users | one-to-many | Emails | Specific Sugar user can modify many account records, but specific account record last modification was performed by specific user. | Relationship: Users - Emails |
| Users | one-to-many | Emails | Specific Sugar user can create many account records, but specific account record can be created by only one user. | Relationship: Users - Emails |
| Users | one-to-many | Emails | Specific Sugar user can be assigned to many account records, but specific account record can only have one user assigned. | Relationship: Users - Emails |