Offboardings
From MintHCM Wiki
| Offboardings | |
|---|---|
| Name: | Offboardings |
| Tech Name: | Offboardings |
| Class Name: | Offboardings |
| 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
Missing User input
Custom Actions
| Action | Type | Short Description |
|---|---|---|
| Close Offboarding | Other | Change status of Offboarding to 'Held' |
| Generate new Offboarding | Menu |
Processes
Related Processes
| Process | Short Description |
|---|---|
| Meetings - Create new rekord | The process of creating a new meeting. |
| Offboarding | How to start and conduct an offboarding process |
Related Process Steps
Related Features
Affected by
| Name | Type | Short Description | Affected Fields | Initiating Fields | Initiating Modules |
|---|---|---|---|---|---|
| Feature:Automatic Offboarding name generation | Automation | Name of an Offboarding is generated automatically after Generate new Offboarding action is triggered. It consists of first and last name of an employee and start date, both provided in popup of Generate new Offboarding action. | Name | Employee, Start Date | |
| 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 |
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 | |
| Offboarding 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 | Offboardings | One Employees record can have many related Offboardings records, but a specific Offboardings record can be related to only one Employees record. | Relationship: Employees - Offboardings |
| Offboarding Templates | one-to-many | Offboardings | One Offboarding Templates record can have many related Offboardings records, but a specific Offboardings record can be related to only one Offboarding Templates record. | Relationship: OffboardingTemplates - Offboardings |
| Offboardings | one-to-many | Tasks | Flex relate used in Offboardings | Relationship: Offboardings - Tasks |
| Offboardings | one-to-many | Trainings | Flex relate used in Offboardings | Relationship: Offboardings - Trainings |
| Users | one-to-many | Offboardings | Specific Sugar user can modify many account records, but specific account record last modification was performed by specific user. | Relationship: Users - Offboardings |
| Users | one-to-many | Offboardings | Specific Sugar user can create many account records, but specific account record can be created by only one user. | Relationship: Users - Offboardings |
| Users | one-to-many | Offboardings | Specific Sugar user can be assigned to many account records, but specific account record can only have one user assigned. | Relationship: Users - Offboardings |