Trainings
From MintHCM Wiki
| Trainings | |
|---|---|
| Name: | Trainings |
| Tech Name: | Trainings |
| Class Name: | Trainings |
| Type: | Standard |
| Template: | Security_groups, Assignable, Basic |
| Custom Module: | No |
| Auditable: | Yes |
| Importable: | No |
| Reportable: | Yes |
| Hide module on Main Page: | No |
Contents
Short Description
Business Description
Missing User input
Custom Actions
| Action | Type | Short Description |
|---|---|---|
| Close Training | Other | Change Training status to 'Held' |
Processes
Related Processes
| Process | Short Description |
|---|---|
| Competencies and Skills | Management of employees' competences and skills |
| Offboarding | How to start and conduct an offboarding process |
| Onboarding | How to start and conduct na onboarding process |
Related Process Steps
Related Features
Affected by
| Name | Type | Short Description | Affected Fields | Initiating Fields | Initiating Modules |
|---|---|---|---|---|---|
| Feature:Conversion of Onboarding/Offboarding Elements | Automation | ||||
| Feature:Create a related Meeting to each Training on Onboarding/Offboarding generation | Automation | On Onboarding/Offboarding generation, for each Training related to Onboarding/Offboarding Template, a new meeting is created related to that Training. | |||
| Feature:Trainings - date start - Validation IsBefore | Validation | Start Date | End Date | Trainings |
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:Close all related Meetings | Automation | On save, when Training status is changed to 'Held', all Meetings related to that Training also change their status to 'Held' | Status | Status | Meetings |
| Feature:Trainings - date start - Validation IsBefore | Validation | End Date | Start Date | Trainings |
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 | |
| End Date | datetimecombo | No | Yes | Yes | |
| Modified by Name | relate | No | Yes | No | |
| Name | name | Yes | Yes | Yes | |
| Parent Type | parent type | No | Yes | Yes | |
| Related to | parent | No | Yes | Yes | |
| Start Date | datetimecombo | No | Yes | Yes | |
| Status | enum | No | Yes | Yes | |
| Type | enum | No | Yes | Yes |
Relationships
| Laft | Type | Right | Short Description | Relationship |
|---|---|---|---|---|
| Offboardings | one-to-many | Trainings | Flex relate used in Offboardings | Relationship: Offboardings - Trainings |
| Onboardings | one-to-many | Trainings | Flex relate used in Onboardings | Relationship: Onboardings - Trainings |
| Users | one-to-many | Trainings | Specific Sugar user can modify many account records, but specific account record last modification was performed by specific user. | Relationship: Users - Trainings |
| Users | one-to-many | Trainings | Specific Sugar user can create many account records, but specific account record can be created by only one user. | Relationship: Users - Trainings |
| Users | one-to-many | Trainings | Specific Sugar user can be assigned to many account records, but specific account record can only have one user assigned. | Relationship: Users - Trainings |