Tasks
From MintHCM Wiki
| Tasks | |
|---|---|
| Name: | Tasks |
| Tech Name: | Tasks |
| Class Name: | Task |
| Type: | Standard |
| Template: | Security_groups, Assignable, Basic |
| Custom Module: | No |
| Auditable: | No |
| Importable: | No |
| Reportable: | Yes |
| Hide module on Main Page: | No |
Contents
Short Description
Business Description
Missing User input
Custom Actions
Processes
Related Processes
| Process | Short Description |
|---|---|
| Calendar | |
| Offboarding | How to start and conduct an offboarding process |
| Onboarding | How to start and conduct na onboarding process |
| Time Management | The process of planning the time spent on various activities, which aims to increase the efficiency of the time used |
Related Process Steps
Related Features
Affected by
Initiating
| Name | Type | Short Description | Initiating Fields | Affected Fields | Affected Modules |
|---|---|---|---|---|---|
| Feature:Close Onboarding/Offboarding if all other elements are closed | Automation | On save, if status of Exit Interview/Task/Training is equal to 'Held' or 'Completed' and record is an element of Onboarding or Offboarding, system checks if all other elements related to Onboarding/Offboarding are closed (Held or Completed). If so, status of Onboarding/Offboarding also changes to 'Held'. | Status, Status, Status | Status, Status | Offboardings, Onboardings |
| Feature:Tasks - date start - Validation IsBefore | Validation | Due Date | Start Date | Tasks |
Related Integrations
Structure
Fields
| Name | Type | Required | Validations | Visible | Editable |
|---|---|---|---|---|---|
| Assigned to | relate | No | Yes | Yes | |
| Created By | relate | No | Yes | No | |
| Date Created | datetime | No | Yes | No | |
| Date Modified | datetime | No | Yes | No | |
| Description | text | No | Yes | Yes | |
| Due Date | datetimecombo | No | Yes | Yes | |
| Due Time | datetime | No | Yes | Yes | |
| Modified By Name | relate | No | Yes | No | |
| No Due Date | bool | No | Yes | Yes | |
| No Start Date | bool | No | Yes | Yes | |
| Parent Type | parent type | No | Yes | Yes | |
| Priority | enum | Yes | Yes | Yes | |
| Related to | parent | No | Yes | Yes | |
| Start Date | datetimecombo | No | Yes | Yes | |
| Status | enum | Yes | Yes | Yes | |
| Subject | name | Yes | Yes | Yes |
Relationships
| Laft | Type | Right | Short Description | Relationship |
|---|---|---|---|---|
| Candidates | one-to-many | Tasks | Flex relate used in Candidate | Relationship: Candidates - Tasks |
| Candidatures | one-to-many | Tasks | Flex relate used in Candidature | Relationship: Candidatures - Tasks |
| Offboardings | one-to-many | Tasks | Flex relate used in Offboardings | Relationship: Offboardings - Tasks |
| Onboardings | one-to-many | Tasks | Flex relate used in Onboardings | Relationship: Onboardings - Tasks |
| Projects | one-to-many | Tasks | Flex relate used in Project | Relationship: Project - Tasks |
| Project Tasks | one-to-many | Tasks | Flex relate used in Project Task | Relationship: ProjectTask - Tasks |
| Recruitments | one-to-many | Tasks | Flex relate used in Recruitment | Relationship: Recruitments - Tasks |
| Tasks | one-to-many | Notes | One Task record can have many related Note records, but a specific Note record can be related to only one Task record. | Relationship: Tasks - Notes |
| Users | one-to-many | Tasks | Specific Sugar user can create many account records, but specific account record can be created by only one user. | Relationship: Users - Tasks |
| Users | one-to-many | Tasks | Specific Sugar user can be assigned to many account records, but specific account record can only have one user assigned. | Relationship: Users - Tasks |
| Users | one-to-many | Tasks | Specific Sugar user can modify many account records, but specific account record last modification was performed by specific user. | Relationship: Users - Tasks |