Employees

From MintHCM Wiki

Employees
Name: Employees
Tech Name: Employees
Class Name: Employee
Type: Standard
Template:
Custom Module: No
Auditable: No
Importable: No
Reportable: Yes
Hide module on Main Page: No

Short Description

Screens


Business Description

Missing User input


Custom Actions

Action Type Short Description
Generate new Offboarding DetailView Button
Generate new Onboarding DetailView Button

Processes

Related Processes

ProcessShort Description
OffboardingHow to start and conduct an offboarding process
OnboardingHow to start and conduct na onboarding process
RecruitmentThe recruitment process with a description of all records needed to carry it out

Related Process Steps

Related Features

Affected by

Initiating

Related Integrations


Structure

Fields


Name Type Required Validations Visible Editable
Accept Status varchar No Yes Yes
Accept Status enum No Yes Yes
Accept Status relate No Yes Yes
Accept Status relate No Yes Yes
Address City varchar No Yes Yes
Address Country varchar No Yes Yes
Address Postal Code varchar No Yes Yes
Address State varchar No Yes Yes
Address Street varchar No Yes Yes
Authentication Id varchar No Yes Yes
Candidate relate No Yes Yes
Created By varchar No Yes No
Date Entered datetime Yes Yes No
Date Modified datetime Yes Yes No
Department varchar No Yes Yes
Description text No Yes Yes
Display Employee Record bool No Yes Yes
Email Address varchar No Yes Yes
Email Client enum No Yes Yes
Employee Status varchar No Yes Yes
External Authentication bool No Yes Yes
Fax phone No Yes Yes
First Name name No Yes Yes
Group User bool No Yes Yes
Home Phone phone No Yes Yes
IM Name varchar No Yes Yes
IM Type enum No Yes Yes
Is Administrator bool No Yes Yes
Is User bool No Yes Yes
LBL_EDITOR_TYPE enum No Yes Yes
LBL_FACTOR_AUTH bool No Yes Yes
LBL_FACTOR_AUTH_INTERFACE enum No Yes Yes
LBL_USERS_FORCED_TABS_DASHBOARDS relate No Yes Yes
LBL_USERS_LOCKED_DASHBOARDS relate No Yes Yes
LBL_USERS_ONE_TIME_DEFAULT_DASHBOARDS relate No Yes Yes
LBL_securitygroup_noninherit_id varchar No Yes Yes
Last Name name Yes Yes Yes
Mobile phone No Yes Yes
Modified By varchar No Yes No
Name name No Yes Yes
Name varchar No Yes Yes
Non-Inheritable Group bool No Yes Yes
Notify on Assignment bool No Yes Yes
Organizational Unit relate No Yes Yes
Other Phone phone No Yes Yes
Password varchar No Yes Yes
Password Last Changed datetime No Yes Yes
Photo image No Yes Yes
Portal API User bool No Yes Yes
Position relate Yes Yes Yes
Primary Group bool No Yes Yes
Reports to relate No Yes Yes
Status enum No Yes Yes
System Generated Password bool Yes Yes Yes
Title varchar No Yes Yes
User Name relate No Yes Yes
User Name user name Yes Yes Yes
User Type enum No Yes Yes
Work Phone phone No Yes Yes

Relationships

LaftTypeRightShort DescriptionRelationship
Employeesone-to-manyApplicationsOne Employees record can have many related Applications records, but a specific Applications record can be related to only one Employees record.Relationship: Employees - Applications
Employeesone-to-manyAppraisalsOne Employees record can have many related Appraisals records, but a specific Appraisals record can be related to only one Employees record.Relationship: Employees - Appraisals
Employeesone-to-manyCertificatesOne Employees record can have many related Certificates records, but a specific Certificates record can be related to only one Employees record.Relationship: Employees - Certificates
Employeesone-to-manyCompetency RatingsFlex relate used in EmployeesRelationship: Employees - CompetencyRatings
Employeesone-to-manyExit InterviewsOne Employees record can have many related Exit Interviews records, but a specific Exit Interviews record can be related to only one Employees record.Relationship: Employees - ExitInterviews
Employeesone-to-manyGoalsOne Employees record can have many related Goals records, but a specific Goals record can be related to only one Employees record.Relationship: Employees - Goals
Employeesone-to-manyOffboardingsOne Employees record can have many related Offboardings records, but a specific Offboardings record can be related to only one Employees record.Relationship: Employees - Offboardings
Employeesone-to-manyOnboardingsOne Employees record can have many related Onboardings records, but a specific Onboardings record can be related to only one Employees record.Relationship: Employees - Onboardings
Employeesone-to-manyOrganizational UnitsOne Employees record can have many related Organizational Units records, but a specific Organizational Units record can be related to only one Employees record.Relationship: Employees - OrganizationalUnits
Employeesone-to-manyPeriods of EmploymentOne Employees record can have many related Periods of Employment records, but a specific Periods of Employment record can be related to only one Employees record.Relationship: Employees - PeriodsOfEmployment
Employeesone-to-manyReservationsOne Employees record can have many related Reservations records, but a specific Reservations record can be related to only one Employees record.Relationship: Employees - Reservations
Employeesone-to-manyResourcesOne Employees record can have many related Resources records, but a specific Resources record can be related to only one Employees record.Relationship: Employees - Resources
Employeesone-to-manyUsers Actual EffortOne Employees record can have many related Users Actual Effort records, but a specific Users Actual Effort record can be related to only one Employees record.Relationship: Employees - SpentTime

Mentioned in other articles


Dev Notes