Onboardings
From MintHCM Wiki
Revision as of 10:26, 14 January 2020 by Kurkiewiczk (talk | contribs)
Onboardings | |
---|---|
Name: | Onboardings |
Tech Name: | Onboardings |
Class Name: | Onboardings |
Type: | Standard |
Template: | Security_groups, Employee_related, Assignable, Basic |
Custom Module: | No |
Auditable: | Yes |
Importable: | No |
Reportable: | Yes |
Hide module on Main Page: | No |
Contents
Short Description
Business Description
This module allows users to view and manage onboardings for specific candidates, generated from Module:Onboarding Templates. In a record view of an onboarding, you can also check onbording's status and which Module:Trainings and Module:Tasks new Module:Employee has to complete.
Custom Actions
Action | Type | Short Description |
---|---|---|
Close Onboarding | Other | Change Onboarding status to 'Held' |
Generate new Onboarding | Menu |
Processes
Related Processes
Process | Short Description |
---|---|
Meetings - Create new rekord | The process of creating a new meeting. |
Onboarding | How to start and conduct an onboarding process |
Related Process Steps
Process | Step Title | Short Description |
---|---|---|
Onboarding tasks | Generating onboarding | Generating onboarding for a new employee. |
Onboarding tasks | Checking the tasks. | Checking the tasks on the Tasks subpanel. |
Related Features
Affected by
Name | Type | Short Description | Affected Fields | Initiating Fields | Initiating 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 | Tasks, Exit Interviews, Trainings |
Feature:Dependency of Employee field | Automation | Employee |
Initiating
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 | |
Employee | relate | No | Yes | Yes | |
Employee ID | relate | No | Yes | Yes | |
Modified by Name | relate | No | Yes | No | |
Name | name | Yes | Yes | Yes | |
Onboarding Template | relate | No | Yes | Yes | |
Start Date | datetimecombo | No | Yes | Yes | |
Status | enum | No | Yes | Yes |
Relationships
Laft | Type | Right | Short Description | Relationship |
---|---|---|---|---|
Employees | one-to-many | Onboardings | One Employees record can have many related Onboardings records, but a specific Onboardings record can be related to only one Employees record. | Relationship: Employees - Onboardings |
Onboarding Templates | one-to-many | Onboardings | One Onboarding Templates record can have many related Onboardings records, but a specific Onboardings record can be related to only one Onboarding Templates record. | Relationship: OnboardingTemplates - Onboardings |
Onboardings | one-to-many | Tasks | Flex relate used in Onboardings | Relationship: Onboardings - Tasks |
Onboardings | one-to-many | Trainings | Flex relate used in Onboardings | Relationship: Onboardings - Trainings |
Users | one-to-many | Onboardings | Specific Sugar user can modify many account records, but specific account record last modification was performed by specific user. | Relationship: Users - Onboardings |
Users | one-to-many | Onboardings | Specific Sugar user can create many account records, but specific account record can be created by only one user. | Relationship: Users - Onboardings |
Users | one-to-many | Onboardings | Specific Sugar user can be assigned to many account records, but specific account record can only have one user assigned. | Relationship: Users - Onboardings |