Property:Short Description

From MintHCM Wiki

This is a property of type Text.

previous 5002050100250500next 500
Showing 500 pages using this property.
m
modified by name@Offboardings +
Name of the user who modified the record  +
modified by name@OffboardingTemplates +
Name of the user who modified the record  +
modified by name@OnboardingOffboardingElements +
Name of the user who modified the record  +
modified by name@Onboardings +
Name of the user who modified the record  +
modified by name@OnboardingTemplates +
Name of the user who modified the record  +
modified by name@OrganizationalUnits +
Name of the user who modified the record  +
modified by name@OutboundEmailAccounts +
Name of the user who modified the record  +
modified by name@PeriodsOfEmployment +
Name of the user who modified the record  +
modified by name@Positions +
Name of the user who modified the record  +
modified by name@Problems +
Name of the user who modified the record  +
modified by name@Project +
Name of the user who modified the record  +
modified by name@ProjectTask +
Name of the user who modified the record  +
modified by name@Recruitments +
Name of the user who modified the record  +
modified by name@Reservations +
Name of the user who modified the record  +
modified by name@Resources +
Name of the user who modified the record  +
modified by name@Responsibilities +
Name of the user who modified the record  +
modified by name@ResponsibilityActivities +
Name of the user who modified the record  +
modified by name@SpentTime +
Name of the user who modified the record  +
modified by name@SurveyQuestionOptions +
Name of the user who modified the record  +
modified by name@SurveyQuestionResponses +
Name of the user who modified the record  +
modified by name@SurveyQuestions +
Name of the user who modified the record  +
modified by name@SurveyResponses +
Name of the user who modified the record  +
modified by name@Surveys +
Name of the user who modified the record  +
modified by name@Tasks +
Name of the user who modified the record  +
modified by name@TermsOfEmployment +
Name of the user who modified the record  +
modified by name@Trainings +
Name of the user who modified the record  +
modified by name@Transportations +
Name of the user who modified the record  +
modified by name@Users +
Name of the user who modified the record  +
modified by name@UsersNews +
Name of the user who modified the record  +
modified by name@WorkingMonths +
Name of the user who modified the record  +
modified by name@WorkSchedules +
Name of the user who modified the record  +
r
repeat count@Calls +
Number of recurrence  +
repeat count@Meetings +
Number of recurrence  +
repeat count@WorkSchedules +
Number of recurrence  +
O
Offboarding Templates +
Offboarding Templates are used for generating an actual offboarding for a particular employee and position  +
D
Dependency of Offboarding start date field +
Offboarding start date is filled in with a value provided by the user in popup appearing during Generate new Offboarding action  +
C
Create a related Meeting to each Training on Onboarding/Offboarding generation +
On Onboarding/Offboarding generation, for each Training related to Onboarding/Offboarding Template, a new meeting is created related to that Training.  +
Close Onboarding/Offboarding if all other elements are closed +
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'.  +
Close all related Trainings that have other related Meetings closed +
On save, when Meeting status is changed to 'Held', all Trainings related to that Meeting that have all other related Meetings set to 'Held', will also be set to 'Held'  +
Close all related Meetings +
On save, when Training status is changed to 'Held', all Meetings related to that Training also change their status to 'Held'  +
O
Onboarding Templates +
Onboarding Templates are used for generating an actual onboarding for a particular employee and position  +
R
Relationship: Appraisals - AppraisalItems +
One Appraisals record can have many related Appraisal Items records, but a specific Appraisal Items record can be related to only one Appraisals record.  +
Relationship: Candidates - Candidatures +
One Candidate record can have many related Candidature records, but a specific Candidature record can be related to only one Candidate record.  +
Relationship: Candidates - Certificates +
One Candidate record can have many related Certificates records, but a specific Certificates record can be related to only one Candidate record.  +
Relationship: Candidatures - Appraisals +
One Candidature record can have many related Appraisals records, but a specific Appraisals record can be related to only one Candidature record.  +
Relationship: Competencies - CompetencyRatings +
One Competencies record can have many related Competency Ratings records, but a specific Competency Ratings record can be related to only one Competencies record.  +
Relationship: DelegationsLocale - Delegations +
One Delegations Locale record can have many related Delegations records, but a specific Delegations record can be related to only one Delegations Locale record.  +
Relationship: Delegations - Transportations +
One Delegations record can have many related Transportations records, but a specific Transportations record can be related to only one Delegations record.  +
Relationship: Delegations - WorkSchedules +
One Delegations record can have many related Work Schedule records, but a specific Work Schedule record can be related to only one Delegations record.  +
Relationship: Delegations - Reservations +
One Delegations record can have many related Reservations records, but a specific Reservations record can be related to only one Delegations record.  +
Relationship: Documents - DocumentRevisions +
One Document record can have many related Document Revisions records, but a specific Document Revisions record can be related to only one Document record.  +
Relationship: Emails - Meetings +
One Email record can have many related Meeting records, but a specific Meeting record can be related to only one Email record.  +
Relationship: Emails - Notes +
One Email record can have many related Note records, but a specific Note record can be related to only one Email record.  +
Relationship: Employees - SpentTime +
One 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 - Appraisals +
One Employees record can have many related Appraisals records, but a specific Appraisals record can be related to only one Employees record.  +
Relationship: Employees - 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 - Applications +
One Employees record can have many related Applications records, but a specific Applications record can be related to only one Employees record.  +
Relationship: Employees - PeriodsOfEmployment +
One 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 - ExitInterviews +
One 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 - Goals +
One Employees record can have many related Goals records, but a specific Goals record can be related to only one Employees record.  +
Relationship: Employees - 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 - Certificates +
One Employees record can have many related Certificates records, but a specific Certificates record can be related to only one Employees record.  +
Relationship: Employees - OrganizationalUnits +
One 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 - Resources +
One Employees record can have many related Resources records, but a specific Resources record can be related to only one Employees record.  +
Relationship: Employees - Reservations +
One Employees record can have many related Reservations records, but a specific Reservations record can be related to only one Employees record.  +
Relationship: Meetings - Conclusions +
One Meeting record can have many related Conclusions records, but a specific Conclusions record can be related to only one Meeting record.  +
Relationship: News - UsersNews +
One News record can have many related User's News records, but a specific User's News record can be related to only one News record.  +
Relationship: OffboardingTemplates - 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: OnboardingTemplates - 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: OrganizationalUnits - OrganizationalUnits +
One Organizational Units record can have many related Organizational Units records, but a specific Organizational Units record can be related to only one Organizational Units record.  +
Relationship: Positions - CareerPaths +
One Position record can have many related Career Paths records, but a specific Career Paths record can be related to only one Position record.  +
Relationship: Positions - CareerPaths +
One Position record can have many related Career Paths records, but a specific Career Paths record can be related to only one Position record.  +
Relationship: Positions - Appraisals +
One Position record can have many related Appraisals records, but a specific Appraisals record can be related to only one Position record.  +
Relationship: Positions - Recruitments +
One Position record can have many related Recruitment records, but a specific Recruitment record can be related to only one Position record.  +
Relationship: Positions - OffboardingTemplates +
One Position record can have many related Offboarding Templates records, but a specific Offboarding Templates record can be related to only one Position record.  +
Relationship: Positions - Positions +
One Position record can have many related Position records, but a specific Position record can be related to only one Position record.  +
Relationship: Positions - OnboardingTemplates +
One Position record can have many related Onboarding Templates records, but a specific Onboarding Templates record can be related to only one Position record.  +
Relationship: Project - ProjectTask +
One Project record can have many related Project Task records, but a specific Project Task record can be related to only one Project record.  +
Relationship: Recruitments - Candidatures +
One Recruitment record can have many related Candidature records, but a specific Candidature record can be related to only one Recruitment record.  +
Relationship: Recruitments - Candidatures +
One Recruitment record can have many related Candidature records, but a specific Candidature record can be related to only one Recruitment record.  +
Relationship: Resources - Reservations +
One Resources record can have many related Reservations records, but a specific Reservations record can be related to only one Resources record.  +
Relationship: SurveyQuestions - SurveyQuestionOptions +
One Survey Questions record can have many related Survey Question Options records, but a specific Survey Question Options record can be related to only one Survey Questions record.  +
Relationship: SurveyResponses - SurveyQuestionResponses +
One Survey Responses record can have many related Survey Question Responses records, but a specific Survey Question Responses record can be related to only one Survey Responses record.  +
Relationship: Surveys - SurveyQuestions +
One Surveys record can have many related Survey Questions records, but a specific Survey Questions record can be related to only one Surveys record.  +
Relationship: Surveys - SurveyResponses +
One Surveys record can have many related Survey Responses records, but a specific Survey Responses record can be related to only one Surveys record.  +
Relationship: Tasks - Notes +
One Task record can have many related Note records, but a specific Note record can be related to only one Task record.  +
Relationship: Users - Ideas +
One User record can have many related Idea records, but a specific Idea record can be related to only one User record.  +
Relationship: Users - OnboardingOffboardingElements +
One User record can have many related Onboarding/Offboarding Elements records, but a specific Onboarding/Offboarding Elements record can be related to only one User record.  +
Relationship: Users - Users +
One User record can have many related User records, but a specific User record can be related to only one User record.  +
p
phone other@person +
Other phone number for the contact  +
phone other@Candidates +
Other phone number for the contact  +
f
file url@Notes +
Path to file (can be URL)  +
D
Dependency of Period Ending Date +
Period Ending Date is the date the employee ends work  +
Dependency of Period Starting Date +
Period Starting Date is the date when the employee starts work  +
a
assistant phone@person +
Phone number of the assistant of the contact  +
assistant phone@Candidates +
Phone number of the assistant of the contact  +
b
body@EmailTemplates +
Plain text body to be used in resulting email  +
C
Choosing means of transport +
Planning transportation during business trip  +
p
portal flag@Notes +
Portal flag indicator determines if note created via portal  +
a
alt address postalcode@person +
Postal code for alternate address  +
alt address postalcode@Candidates +
Postal code for alternate address  +
p
primary address postalcode@person +
Postal code for primary address  +
primary address postalcode@Candidates +
Postal code for primary address  +
C
Create a new Call +
Process of create and managment new call  +
Create new Document +
Process of creating a new document in the documents module.  +
Create New Survey +
Process of creating a new survey.  +
n
name@Project +
Project name  +
R
Report the trip +
Reckoning delegations  +
r
repeat pane@Meetings +
Repeat Pane  +
repeat pane@WorkSchedules +
Repeat Pane  +
repeat until@Calls +
Repeat until specified date  +
repeat until@Meetings +
Repeat until specified date  +
repeat until@WorkSchedules +
Repeat until specified date  +
t
text only@EmailTemplates +
Should be checked if email template is to be sent in text only  +
D
Delegations Locale +
Simple reference module to set and store data on basic costs of travelling to certain countries.  +
r
recurring source@Calls +
Source of recurring call  +
recurring source@Meetings +
Source of recurring meeting  +
R
Relationship: Users - AOK_Knowledge_Base_Categories +
Specific Sugar user can be assigned to many account records, but specific account record can only have one user assigned.  +
Relationship: Users - AOK_KnowledgeBase +
Specific Sugar user can be assigned to many account records, but specific account record can only have one user assigned.  +
Relationship: Users - Applications +
Specific Sugar user can be assigned to many account records, but specific account record can only have one user assigned.  +
Relationship: Users - AppraisalItems +
Specific Sugar user can be assigned to many account records, but specific account record can only have one user assigned.  +
Relationship: Users - Appraisals +
Specific Sugar user can be assigned to many account records, but specific account record can only have one user assigned.  +
Relationship: Users - Benefits +
Specific Sugar user can be assigned to many account records, but specific account record can only have one user assigned.  +
Relationship: Users - Calls +
Specific Sugar user can be assigned to many account records, but specific account record can only have one user assigned.  +
Relationship: Users - Candidates +
Specific Sugar user can be assigned to many account records, but specific account record can only have one user assigned.  +
Relationship: Users - Candidatures +
Specific Sugar user can be assigned to many account records, but specific account record can only have one user assigned.  +
Relationship: Users - CareerPaths +
Specific Sugar user can be assigned to many account records, but specific account record can only have one user assigned.  +
Relationship: Users - Certificates +
Specific Sugar user can be assigned to many account records, but specific account record can only have one user assigned.  +
Relationship: Users - Competencies +
Specific Sugar user can be assigned to many account records, but specific account record can only have one user assigned.  +
Relationship: Users - CompetencyRatings +
Specific Sugar user can be assigned to many account records, but specific account record can only have one user assigned.  +
Relationship: Users - Conclusions +
Specific Sugar user can be assigned to many account records, but specific account record can only have one user assigned.  +
Relationship: Users - Delegations +
Specific Sugar user can be assigned to many account records, but specific account record can only have one user assigned.  +
Relationship: Users - DelegationsLocale +
Specific Sugar user can be assigned to many account records, but specific account record can only have one user assigned.  +
Relationship: Users - Emails +
Specific Sugar user can be assigned to many account records, but specific account record can only have one user assigned.  +
Relationship: Users - EmailTemplates +
Specific Sugar user can be assigned to many account records, but specific account record can only have one user assigned.  +
Relationship: Users - EmployeeRoles +
Specific Sugar user can be assigned to many account records, but specific account record can only have one user assigned.  +
Relationship: Users - ExitInterviews +
Specific Sugar user can be assigned to many account records, but specific account record can only have one user assigned.  +
Relationship: Users - FP_events +
Specific Sugar user can be assigned to many account records, but specific account record can only have one user assigned.  +
Relationship: Users - FP_Event_Locations +
Specific Sugar user can be assigned to many account records, but specific account record can only have one user assigned.  +
Relationship: Users - Goals +
Specific Sugar user can be assigned to many account records, but specific account record can only have one user assigned.  +
Relationship: Users - Ideas +
Specific Sugar user can be assigned to many account records, but specific account record can only have one user assigned.  +
Relationship: Users - Improvements +
Specific Sugar user can be assigned to many account records, but specific account record can only have one user assigned.  +
Relationship: Users - Meetings +
Specific Sugar user can be assigned to many account records, but specific account record can only have one user assigned.  +
Relationship: Users - News +
Specific Sugar user can be assigned to many account records, but specific account record can only have one user assigned.  +
Relationship: Users - Notes +
Specific Sugar user can be assigned to many account records, but specific account record can only have one user assigned.  +
Relationship: Users - Offboardings +
Specific Sugar user can be assigned to many account records, but specific account record can only have one user assigned.  +
Relationship: Users - OffboardingTemplates +
Specific Sugar user can be assigned to many account records, but specific account record can only have one user assigned.  +
Relationship: Users - OnboardingOffboardingElements +
Specific Sugar user can be assigned to many account records, but specific account record can only have one user assigned.  +
Relationship: Users - Onboardings +
Specific Sugar user can be assigned to many account records, but specific account record can only have one user assigned.  +
Relationship: Users - OnboardingTemplates +
Specific Sugar user can be assigned to many account records, but specific account record can only have one user assigned.  +
Relationship: Users - OrganizationalUnits +
Specific Sugar user can be assigned to many account records, but specific account record can only have one user assigned.  +
Relationship: Users - OutboundEmailAccounts +
Specific Sugar user can be assigned to many account records, but specific account record can only have one user assigned.  +
Relationship: Users - PeriodsOfEmployment +
Specific Sugar user can be assigned to many account records, but specific account record can only have one user assigned.  +
Relationship: Users - Positions +
Specific Sugar user can be assigned to many account records, but specific account record can only have one user assigned.  +
Relationship: Users - Problems +
Specific Sugar user can be assigned to many account records, but specific account record can only have one user assigned.  +
Relationship: Users - Project +
Specific Sugar user can be assigned to many account records, but specific account record can only have one user assigned.  +
Relationship: Users - ProjectTask +
Specific Sugar user can be assigned to many account records, but specific account record can only have one user assigned.  +
Relationship: Users - Recruitments +
Specific Sugar user can be assigned to many account records, but specific account record can only have one user assigned.  +
Relationship: Users - Reservations +
Specific Sugar user can be assigned to many account records, but specific account record can only have one user assigned.  +
Relationship: Users - Resources +
Specific Sugar user can be assigned to many account records, but specific account record can only have one user assigned.  +
Relationship: Users - Responsibilities +
Specific Sugar user can be assigned to many account records, but specific account record can only have one user assigned.  +
Relationship: Users - ResponsibilityActivities +
Specific Sugar user can be assigned to many account records, but specific account record can only have one user assigned.  +
Relationship: Users - SpentTime +
Specific Sugar user can be assigned to many account records, but specific account record can only have one user assigned.  +
Relationship: Users - SurveyQuestionOptions +
Specific Sugar user can be assigned to many account records, but specific account record can only have one user assigned.  +
Relationship: Users - SurveyQuestionResponses +
Specific Sugar user can be assigned to many account records, but specific account record can only have one user assigned.  +
Relationship: Users - SurveyQuestions +
Specific Sugar user can be assigned to many account records, but specific account record can only have one user assigned.  +
Relationship: Users - SurveyResponses +
Specific Sugar user can be assigned to many account records, but specific account record can only have one user assigned.  +
Relationship: Users - Surveys +
Specific Sugar user can be assigned to many account records, but specific account record can only have one user assigned.  +
Relationship: Users - Tasks +
Specific Sugar user can be assigned to many account records, but specific account record can only have one user assigned.  +
Relationship: Users - TermsOfEmployment +
Specific Sugar user can be assigned to many account records, but specific account record can only have one user assigned.  +
Relationship: Users - Trainings +
Specific Sugar user can be assigned to many account records, but specific account record can only have one user assigned.  +
Relationship: Users - Transportations +
Specific Sugar user can be assigned to many account records, but specific account record can only have one user assigned.  +
Relationship: Users - UsersNews +
Specific Sugar user can be assigned to many account records, but specific account record can only have one user assigned.  +
Relationship: Users - WorkingMonths +
Specific Sugar user can be assigned to many account records, but specific account record can only have one user assigned.  +
Relationship: Users - WorkSchedules +
Specific Sugar user can be assigned to many account records, but specific account record can only have one user assigned.  +
Relationship: Users - AOK_Knowledge_Base_Categories +
Specific Sugar user can create many account records, but specific account record can be created by only one user.  +
Relationship: Users - AOK_KnowledgeBase +
Specific Sugar user can create many account records, but specific account record can be created by only one user.  +
Relationship: Users - Applications +
Specific Sugar user can create many account records, but specific account record can be created by only one user.  +
Relationship: Users - AppraisalItems +
Specific Sugar user can create many account records, but specific account record can be created by only one user.  +
Relationship: Users - Appraisals +
Specific Sugar user can create many account records, but specific account record can be created by only one user.  +
Relationship: Users - Benefits +
Specific Sugar user can create many account records, but specific account record can be created by only one user.  +
Relationship: Users - Calls +
Specific Sugar user can create many account records, but specific account record can be created by only one user.  +
Relationship: Users - Candidates +
Specific Sugar user can create many account records, but specific account record can be created by only one user.  +
Relationship: Users - Candidatures +
Specific Sugar user can create many account records, but specific account record can be created by only one user.  +
Relationship: Users - CareerPaths +
Specific Sugar user can create many account records, but specific account record can be created by only one user.  +
Relationship: Users - Certificates +
Specific Sugar user can create many account records, but specific account record can be created by only one user.  +
Relationship: Users - Competencies +
Specific Sugar user can create many account records, but specific account record can be created by only one user.  +
Relationship: Users - CompetencyRatings +
Specific Sugar user can create many account records, but specific account record can be created by only one user.  +
Relationship: Users - Conclusions +
Specific Sugar user can create many account records, but specific account record can be created by only one user.  +
Relationship: Users - Delegations +
Specific Sugar user can create many account records, but specific account record can be created by only one user.  +
Relationship: Users - DelegationsLocale +
Specific Sugar user can create many account records, but specific account record can be created by only one user.  +
Relationship: Users - DocumentRevisions +
Specific Sugar user can create many account records, but specific account record can be created by only one user.  +
Relationship: Users - Emails +
Specific Sugar user can create many account records, but specific account record can be created by only one user.  +
Relationship: Users - EmployeeRoles +
Specific Sugar user can create many account records, but specific account record can be created by only one user.  +
Relationship: Users - ExitInterviews +
Specific Sugar user can create many account records, but specific account record can be created by only one user.  +
Relationship: Users - FP_events +
Specific Sugar user can create many account records, but specific account record can be created by only one user.  +
Relationship: Users - FP_Event_Locations +
Specific Sugar user can create many account records, but specific account record can be created by only one user.  +
Relationship: Users - Goals +
Specific Sugar user can create many account records, but specific account record can be created by only one user.  +
Relationship: Users - Ideas +
Specific Sugar user can create many account records, but specific account record can be created by only one user.  +
Relationship: Users - Improvements +
Specific Sugar user can create many account records, but specific account record can be created by only one user.  +
Relationship: Users - Meetings +
Specific Sugar user can create many account records, but specific account record can be created by only one user.  +
Relationship: Users - News +
Specific Sugar user can create many account records, but specific account record can be created by only one user.  +
Relationship: Users - NonWorkingDays +
Specific Sugar user can create many account records, but specific account record can be created by only one user.  +
Relationship: Users - Notes +
Specific Sugar user can create many account records, but specific account record can be created by only one user.  +
Relationship: Users - Offboardings +
Specific Sugar user can create many account records, but specific account record can be created by only one user.  +
Relationship: Users - OffboardingTemplates +
Specific Sugar user can create many account records, but specific account record can be created by only one user.  +
Relationship: Users - OnboardingOffboardingElements +
Specific Sugar user can create many account records, but specific account record can be created by only one user.  +
Relationship: Users - Onboardings +
Specific Sugar user can create many account records, but specific account record can be created by only one user.  +
Relationship: Users - OnboardingTemplates +
Specific Sugar user can create many account records, but specific account record can be created by only one user.  +
Relationship: Users - OrganizationalUnits +
Specific Sugar user can create many account records, but specific account record can be created by only one user.  +
Relationship: Users - OutboundEmailAccounts +
Specific Sugar user can create many account records, but specific account record can be created by only one user.  +
Relationship: Users - PeriodsOfEmployment +
Specific Sugar user can create many account records, but specific account record can be created by only one user.  +
Relationship: Users - Positions +
Specific Sugar user can create many account records, but specific account record can be created by only one user.  +
Relationship: Users - Problems +
Specific Sugar user can create many account records, but specific account record can be created by only one user.  +
Relationship: Users - Project +
Specific Sugar user can create many account records, but specific account record can be created by only one user.  +
Relationship: Users - ProjectTask +
Specific Sugar user can create many account records, but specific account record can be created by only one user.  +
Relationship: Users - Recruitments +
Specific Sugar user can create many account records, but specific account record can be created by only one user.  +
Relationship: Users - Reservations +
Specific Sugar user can create many account records, but specific account record can be created by only one user.  +
Relationship: Users - Resources +
Specific Sugar user can create many account records, but specific account record can be created by only one user.  +
Relationship: Users - Responsibilities +
Specific Sugar user can create many account records, but specific account record can be created by only one user.  +
Relationship: Users - ResponsibilityActivities +
Specific Sugar user can create many account records, but specific account record can be created by only one user.  +
Relationship: Users - SpentTime +
Specific Sugar user can create many account records, but specific account record can be created by only one user.  +
Relationship: Users - SurveyQuestionOptions +
Specific Sugar user can create many account records, but specific account record can be created by only one user.  +
Relationship: Users - SurveyQuestionResponses +
Specific Sugar user can create many account records, but specific account record can be created by only one user.  +
Relationship: Users - SurveyQuestions +
Specific Sugar user can create many account records, but specific account record can be created by only one user.  +
Relationship: Users - SurveyResponses +
Specific Sugar user can create many account records, but specific account record can be created by only one user.  +
Relationship: Users - Surveys +
Specific Sugar user can create many account records, but specific account record can be created by only one user.  +
Relationship: Users - Tasks +
Specific Sugar user can create many account records, but specific account record can be created by only one user.  +
Relationship: Users - TermsOfEmployment +
Specific Sugar user can create many account records, but specific account record can be created by only one user.  +
Relationship: Users - Trainings +
Specific Sugar user can create many account records, but specific account record can be created by only one user.  +
Relationship: Users - Transportations +
Specific Sugar user can create many account records, but specific account record can be created by only one user.  +
Relationship: Users - UsersNews +
Specific Sugar user can create many account records, but specific account record can be created by only one user.  +
Relationship: Users - WorkingMonths +
Specific Sugar user can create many account records, but specific account record can be created by only one user.  +
Relationship: Users - WorkSchedules +
Specific Sugar user can create many account records, but specific account record can be created by only one user.  +
Relationship: Users - AOK_Knowledge_Base_Categories +
Specific Sugar user can modify many account records, but specific account record last modification was performed by specific user.  +
Relationship: Users - AOK_KnowledgeBase +
Specific Sugar user can modify many account records, but specific account record last modification was performed by specific user.  +
Relationship: Users - Applications +
Specific Sugar user can modify many account records, but specific account record last modification was performed by specific user.  +
Relationship: Users - AppraisalItems +
Specific Sugar user can modify many account records, but specific account record last modification was performed by specific user.  +
Relationship: Users - Appraisals +
Specific Sugar user can modify many account records, but specific account record last modification was performed by specific user.  +
Relationship: Users - Benefits +
Specific Sugar user can modify many account records, but specific account record last modification was performed by specific user.  +
Relationship: Users - Calls +
Specific Sugar user can modify many account records, but specific account record last modification was performed by specific user.  +
Relationship: Users - Candidates +
Specific Sugar user can modify many account records, but specific account record last modification was performed by specific user.  +
Relationship: Users - Candidatures +
Specific Sugar user can modify many account records, but specific account record last modification was performed by specific user.  +
Relationship: Users - CareerPaths +
Specific Sugar user can modify many account records, but specific account record last modification was performed by specific user.  +
Relationship: Users - Certificates +
Specific Sugar user can modify many account records, but specific account record last modification was performed by specific user.  +
Relationship: Users - Competencies +
Specific Sugar user can modify many account records, but specific account record last modification was performed by specific user.  +
Relationship: Users - CompetencyRatings +
Specific Sugar user can modify many account records, but specific account record last modification was performed by specific user.  +
Relationship: Users - Conclusions +
Specific Sugar user can modify many account records, but specific account record last modification was performed by specific user.  +
Relationship: Users - Delegations +
Specific Sugar user can modify many account records, but specific account record last modification was performed by specific user.  +
Relationship: Users - DelegationsLocale +
Specific Sugar user can modify many account records, but specific account record last modification was performed by specific user.  +
Relationship: Users - Emails +
Specific Sugar user can modify many account records, but specific account record last modification was performed by specific user.  +
Relationship: Users - EmployeeRoles +
Specific Sugar user can modify many account records, but specific account record last modification was performed by specific user.  +
Relationship: Users - ExitInterviews +
Specific Sugar user can modify many account records, but specific account record last modification was performed by specific user.  +
Relationship: Users - FP_events +
Specific Sugar user can modify many account records, but specific account record last modification was performed by specific user.  +
Relationship: Users - FP_Event_Locations +
Specific Sugar user can modify many account records, but specific account record last modification was performed by specific user.  +
Relationship: Users - Goals +
Specific Sugar user can modify many account records, but specific account record last modification was performed by specific user.  +
Relationship: Users - Ideas +
Specific Sugar user can modify many account records, but specific account record last modification was performed by specific user.  +
Relationship: Users - Improvements +
Specific Sugar user can modify many account records, but specific account record last modification was performed by specific user.  +
Relationship: Users - Meetings +
Specific Sugar user can modify many account records, but specific account record last modification was performed by specific user.  +
Relationship: Users - News +
Specific Sugar user can modify many account records, but specific account record last modification was performed by specific user.  +
Relationship: Users - NonWorkingDays +
Specific Sugar user can modify many account records, but specific account record last modification was performed by specific user.  +
Relationship: Users - Notes +
Specific Sugar user can modify many account records, but specific account record last modification was performed by specific user.  +
Relationship: Users - Offboardings +
Specific Sugar user can modify many account records, but specific account record last modification was performed by specific user.  +
Relationship: Users - OffboardingTemplates +
Specific Sugar user can modify many account records, but specific account record last modification was performed by specific user.  +
Relationship: Users - OnboardingOffboardingElements +
Specific Sugar user can modify many account records, but specific account record last modification was performed by specific user.  +
Relationship: Users - Onboardings +
Specific Sugar user can modify many account records, but specific account record last modification was performed by specific user.  +
Relationship: Users - OnboardingTemplates +
Specific Sugar user can modify many account records, but specific account record last modification was performed by specific user.  +
Relationship: Users - OrganizationalUnits +
Specific Sugar user can modify many account records, but specific account record last modification was performed by specific user.  +
Relationship: Users - OutboundEmailAccounts +
Specific Sugar user can modify many account records, but specific account record last modification was performed by specific user.  +
Relationship: Users - PeriodsOfEmployment +
Specific Sugar user can modify many account records, but specific account record last modification was performed by specific user.  +
Relationship: Users - Positions +
Specific Sugar user can modify many account records, but specific account record last modification was performed by specific user.  +
Relationship: Users - Problems +
Specific Sugar user can modify many account records, but specific account record last modification was performed by specific user.  +
Relationship: Users - Project +
Specific Sugar user can modify many account records, but specific account record last modification was performed by specific user.  +
Relationship: Users - ProjectTask +
Specific Sugar user can modify many account records, but specific account record last modification was performed by specific user.  +
Relationship: Users - Recruitments +
Specific Sugar user can modify many account records, but specific account record last modification was performed by specific user.  +
Relationship: Users - Reservations +
Specific Sugar user can modify many account records, but specific account record last modification was performed by specific user.  +
Relationship: Users - Resources +
Specific Sugar user can modify many account records, but specific account record last modification was performed by specific user.  +
Relationship: Users - Responsibilities +
Specific Sugar user can modify many account records, but specific account record last modification was performed by specific user.  +
Relationship: Users - ResponsibilityActivities +
Specific Sugar user can modify many account records, but specific account record last modification was performed by specific user.  +
Relationship: Users - SpentTime +
Specific Sugar user can modify many account records, but specific account record last modification was performed by specific user.  +
Relationship: Users - SurveyQuestionOptions +
Specific Sugar user can modify many account records, but specific account record last modification was performed by specific user.  +
Relationship: Users - SurveyQuestionResponses +
Specific Sugar user can modify many account records, but specific account record last modification was performed by specific user.  +
Relationship: Users - SurveyQuestions +
Specific Sugar user can modify many account records, but specific account record last modification was performed by specific user.  +
Relationship: Users - SurveyResponses +
Specific Sugar user can modify many account records, but specific account record last modification was performed by specific user.  +
Relationship: Users - Surveys +
Specific Sugar user can modify many account records, but specific account record last modification was performed by specific user.  +
Relationship: Users - Tasks +
Specific Sugar user can modify many account records, but specific account record last modification was performed by specific user.  +
Relationship: Users - TermsOfEmployment +
Specific Sugar user can modify many account records, but specific account record last modification was performed by specific user.  +
Relationship: Users - Trainings +
Specific Sugar user can modify many account records, but specific account record last modification was performed by specific user.  +
Relationship: Users - Transportations +
Specific Sugar user can modify many account records, but specific account record last modification was performed by specific user.  +
Relationship: Users - UsersNews +
Specific Sugar user can modify many account records, but specific account record last modification was performed by specific user.  +
Relationship: Users - WorkingMonths +
Specific Sugar user can modify many account records, but specific account record last modification was performed by specific user.  +
Relationship: Users - WorkSchedules +
Specific Sugar user can modify many account records, but specific account record last modification was performed by specific user.  +
D
Dependency of Work Schedule Type +
Specific types of Work Schedule have additional fields or options  +
R
Relationship: Module:Users - Module:Documents +
Specific user can be assigned to many account records, but specific account record can only have one user assigned.  +
Relationship: Module:Users - Module:Documents +
Specific user can create many account records, but specific account record can be created by only one user.  +
Relationship: Module:Users - Module:Documents +
Specific user can modify many account records, but specific account record last modification was performed by specific user.  +
e
email reminder time@Calls +
Specifies when a email reminder alert should be issued; -1 means no alert; otherwise the number of seconds prior to the start  +
email reminder time@Meetings +
Specifies when a email reminder alert should be issued; -1 means no alert; otherwise the number of seconds prior to the start  +
r
reminder time@Calls +
Specifies when a reminder alert should be issued; -1 means no alert; otherwise the number of seconds prior to the start  +
reminder time@Meetings +
Specifies when a reminder alert should be issued; -1 means no alert; otherwise the number of seconds prior to the start  +
s
status@SpentTime +
Spent time record status  +
d
description@basic +
Standard text field to store additional notes about the record  +
description@AOK Knowledge Base Categories +
Standard text field to store additional notes about the record  +
description@AOK KnowledgeBase +
Standard text field to store additional notes about the record  +
description@Applications +
Standard text field to store additional notes about the record  +
description@AppraisalItems +
Standard text field to store additional notes about the record  +
description@Appraisals +
Standard text field to store additional notes about the record  +
description@Benefits +
Standard text field to store additional notes about the record  +
description@Calls +
Standard text field to store additional notes about the record  +
description@Candidates +
Standard text field to store additional notes about the record  +
description@Candidatures +
Standard text field to store additional notes about the record  +
description@CareerPaths +
Standard text field to store additional notes about the record  +
description@Certificates +
Standard text field to store additional notes about the record  +
description@Competencies +
Standard text field to store additional notes about the record  +
description@CompetencyRatings +
Standard text field to store additional notes about the record  +
description@Conclusions +
Standard text field to store additional notes about the record  +
description@Delegations +
Standard text field to store additional notes about the record  +
description@DelegationsLocale +
Standard text field to store additional notes about the record  +
description@Documents +
Standard text field to store additional notes about the record  +
description@Emails +
Standard text field to store additional notes about the record  +
description@EmailTemplates +
Standard text field to store additional notes about the record  +
description@EmployeeRoles +
Standard text field to store additional notes about the record  +
description@Employees +
Standard text field to store additional notes about the record  +
description@ExitInterviews +
Standard text field to store additional notes about the record  +
description@FP events +
Standard text field to store additional notes about the record  +
description@FP Event Locations +
Standard text field to store additional notes about the record  +
description@Goals +
Standard text field to store additional notes about the record  +
description@Ideas +
Standard text field to store additional notes about the record  +
description@Improvements +
Standard text field to store additional notes about the record  +
description@Meetings +
Standard text field to store additional notes about the record  +
description@News +
Standard text field to store additional notes about the record  +
description@NonWorkingDays +
Standard text field to store additional notes about the record  +
description@Notes +
Standard text field to store additional notes about the record  +
description@Offboardings +
Standard text field to store additional notes about the record  +
description@OffboardingTemplates +
Standard text field to store additional notes about the record  +
description@OnboardingOffboardingElements +
Standard text field to store additional notes about the record  +
description@Onboardings +
Standard text field to store additional notes about the record  +
description@OnboardingTemplates +
Standard text field to store additional notes about the record  +
description@OrganizationalUnits +
Standard text field to store additional notes about the record  +
description@PeriodsOfEmployment +
Standard text field to store additional notes about the record  +
description@Positions +
Standard text field to store additional notes about the record  +
description@Problems +
Standard text field to store additional notes about the record  +
description@Project +
Standard text field to store additional notes about the record  +
description@ProjectTask +
Standard text field to store additional notes about the record  +
description@Recruitments +
Standard text field to store additional notes about the record  +
description@Reservations +
Standard text field to store additional notes about the record  +
description@Resources +
Standard text field to store additional notes about the record  +
description@Responsibilities +
Standard text field to store additional notes about the record  +
description@ResponsibilityActivities +
Standard text field to store additional notes about the record  +
description@SpentTime +
Standard text field to store additional notes about the record  +
description@SurveyQuestionOptions +
Standard text field to store additional notes about the record  +
description@SurveyQuestionResponses +
Standard text field to store additional notes about the record  +
description@SurveyQuestions +
Standard text field to store additional notes about the record  +
description@SurveyResponses +
Standard text field to store additional notes about the record  +
description@Surveys +
Standard text field to store additional notes about the record  +
description@Tasks +
Standard text field to store additional notes about the record  +
description@TermsOfEmployment +
Standard text field to store additional notes about the record  +
description@Trainings +
Standard text field to store additional notes about the record  +
description@Transportations +
Standard text field to store additional notes about the record  +
description@Users +
Standard text field to store additional notes about the record  +
description@UsersNews +
Standard text field to store additional notes about the record  +
description@WorkingMonths +
Standard text field to store additional notes about the record  +
description@WorkSchedules +
Standard text field to store additional notes about the record  +
a
alt address state@person +
State for alternate address  +
alt address state@Candidates +
State for alternate address  +
p
primary address state@person +
State for primary address  +
primary address state@Candidates +
State for primary address  +
W
Work Schedule Status Automation +
Status is automatically changed during adding the Spent Time record or submitting the Work Schedule. Specific users can withdraw the status of the approved Work Schedule.  +
P
Positions +
Stores all the information about positions  +
D
Documents +
Stores electronic versions of documents  +
R
Reservations +
Stores information about the reservations of resources  +
U
User's News +
Stores information about which users have read the news  +
D
Document Revisions +
Stores the versions of a document  +
a
alt address street@person +
Street address for alternate address  +
alt address street@Candidates +
Street address for alternate address  +
p
primary address street@person +
Street address for primary address  +
W
WorkSchedules - Submit +
Submit button allows user to close a Work Schedule  +
S
Surveys - Survey Responses +
Subpanel to check submitted responses. All responses are added with the creation date.  +
p
parent type@Notes +
Sugar module the Note is associated with  +
i
intent@Emails +
Target of action used in Inbound Email assignment  +
F
Feature:Tasks - due date - color selection on the list view +
Tasks due_date changes color if exceeded (View list)  +
T
Tasks to be done during onbording process +
Tasks generated in the onboarding process that the employee should perform independently.  +
E
Emails +
The "Emails" module is designed to enhance and simplify email management within an organization. Its primary objective is to offer users a swift and efficient means to oversee their email correspondence while also serving as a comprehensive email repository. By presenting a concise presentation of email threads and pertinent message records, it empowers users to remain well-informed and current with their email communications.  +
Employees +
The "Employees" module is thoughtfully crafted to streamline and optimize personnel management within an organization. Its core purpose is to provide users with a seamless and effective way to handle their workforce-related tasks while also serving as a comprehensive repository of employee information. By offering a succinct overview of employee profiles, essential HR records, and performance metrics, it empowers users to stay well-informed and up-to-date with their workforce management responsibilities. Simultaneously, it functions as a secure and accessible archive for all employee-related data, ensuring easy retrieval and reference for future needs.  +
L
Locations +
The "Locations" module offers a straightforward approach to managing organizational spaces. Users can create, edit, and store various location entries, supporting event planning. The module's entries act as references when organizing events, allowing users to quickly select appropriate venues.  +
N
Non Working Days Registry +
The "Non Working Days" module is a straightforward tool designed to manage non-working days within the system.  +
P
Project Tasks +
The "Project Task" module is a component of the larger Projects module, designed to facilitate the organization and management of internal and recruitment projects within the company. It allows users to track and coordinate project tasks, including their status, timelines, priorities, and assignments.  +
Project +
The "Project" module is designed to streamline and manage the company's projects undertaken by the organization. It allows tracking the progress and status of each project, assigning project managers, setting priorities, and defining project timelines. Additionally, it offers the capability to utilize predefined project templates and maintain a list of allocated resources for efficient project execution.  +
R
Responsibilities +
The "Responsibilities" module helps manage tasks and allows users to define, assign and perform in the organization. This module is integrated with key modules like Positions, Roles, Appraisal Items, and Activities.  +
W
Working Months +
The "Working Months" module serves is a tool to input the number of working days within a given month.  +
B
Basic +
The <b>Basic</b> template type provides basic fields, such as the Name, Assigned to, Team, Date Created and Description fields.  +
P
Person +
The <b>Person</b> template type provides individual-specific fields, such as Salutation, Title, Name, Address and Phone Number.<br/><br/>Use this template to create modules that are similar to the standard Contacts and Leads modules.  +
A
Activities +
The Activities module enables users to streamline and track various HR-related tasks and activities. Its functionalities include assigning and monitoring responsibilities, linking them to specific positions and roles, and setting up appraisal items for performance evaluations.  +
Applications +
The Applications module within MintHCM system offers a straightforward and efficient means for employees to submit various types of applications to their superiors, people from other departments or other employees within the organization, responsible for a considered subject. This module serves as a tool for streamlining the application submission process, ensuring clarity and accountability in decision-making  +
Appraisal Items +
The Appraisal Items module in MintHCM system serves as a component for standardizing the appraisal process. It stores specific evaluation criteria and a relation to a specific appraisal process, where it's been used. Each record represents a distinct relation of an appraisal process and a criterion upon which candidates or employees are assessed.  +
Appraisals +
The Appraisals module is a tool primarily designed for HR professionals within the organization. It serves as a platform for storing assessments of candidates, allowing for a detailed evaluation process. With an expanded feature set, including the ability to add appraisal item fields dynamically, the Appraisals module offers flexibility in candidate assessment.  +
B
Benefits +
The Benefits module in MintHCM serves as a tool for Human Resources (HR) personnel to manage employee benefits. It allows the creation and assignment of benefits to individual employees within the organization. Additionally, it provides other employees with the ability to view their assigned benefits for transparency and awareness.  +
C
Calendar +
The Calendar Module within the MintHCM System that allows users to efficiently manage their schedules, tasks, calls, and meetings. It provides different views for easy navigation and organization, helping users stay on top of their daily activities. With collaborative features and detailed event information, the module ensures effective scheduling and productivity.  +
Competency Ratings +
The Competency Ratings module in MintHCM is a tool for companies engaged in recruitment, management, and employee support. It allows organizations to assess and rate the competencies of their employees, helping in the effective matching of skills with job roles and career development. This module can be used to track and evaluate employee performance, identify skill gaps, and make informed decisions about training and development.  +
D
Dependency of Duration Hours +
The Duration depends on the Start Time and End Time fields at the Work Schedule. The Work Schedule plan length cannot be greater than 24 hours.  +
E
Email - Templates +
The E-mail Templates module allows users to use pre-designed, freely configurable e-mail templates. Templates can be used anywhere in the system where the user sends emails to other system users.  +
D
Dependency of Employee field in Offboarding +
The Employee field in the Offboarding record is automatically completed during the Generate new Offboarding action. The employee's name is taken from the popup that appears after clicking Generate in the Offboarding template  +
E
Events +
The Events module within MintHCM is a tool designed to facilitate event scheduling and management within an organization. It offers functionalities to create, track, and organize various events efficiently.  +
G
Goals +
The Goals module in MintHCM is a tool for setting and tracking objectives in recruitment and employee management. It enables to define and monitor various targets, such as recruitment quotas, employee retention rates, and revenue goals.  +
p
parent id@Notes +
The ID of the Sugar item specified in parent_type  +
parent id@Calls +
The ID of the parent Sugar object identified by parent_type  +
I
Ideas +
The Ideas Module in the MintHCM system is designed to facilitate the submission, evaluation, and management of ideas related to the company and its processes.  +
Improvements +
The Improvements module facilitates performance enhancement within the workplace. It provides tools for goal-setting, skill development, and constructive feedback, fostering a conducive environment for professional growth.  +
K
KB - Categories +
The Knowledge Base Category Module efficiently categorizes knowledge base articles with a many-to-many relationship model. Users can create and manage categories, associating them with various articles for improved organization and accessibility. This module enhances knowledge management by allowing users to easily navigate a structured and interconnected knowledge base.  +
I
Installation guide MintHCM v4 +
The MintHCM Installing Guide is a technical document that provides detailed instructions on how to install and configure the software. The guide covers everything from system requirements to database configuration and user setup. It is a comprehensive technical resource that provides you with the information you need to set up and configure the software effectively.  +
N
Notes +
The Notes module is a simple feature that allows users to quickly add comments, explanations, or simple summaries under a record, providing users with up-to-date information about the record  +
P
Problems +
The Problems module is a tool for companies management. This module allows users to track and manage various issues, challenges, or concerns related to employees and their work. It is linked to the Employees module, facilitating seamless communication and problem resolution among team members.  +
p
parent type@Calls +
The Sugar object to which the call is related  +
parent type@Tasks +
The Sugar object to which the call is related  +
W
Work Schedule - Supervisor Acceptance Automation +
The Supervisor Acceptance field is shown for a specific Work Schedule and is automatically changed when the user clicks specific buttons  +
D
Dependency of Assigned to +
The Supervisor can assign the Work Schedule to Users which are his subordinate. The System Administrator can assign the Work Schedule to all Users. This functionality displays the Work Schedule in the User's calendar that has been assigned.  +
W
Work Schedule +
The Work Schedule module in Mint HCM enables the management of employees' work hours within a company. It allows users to create, manage, and monitor work schedules, as well as generate time-related reports.  +
D
Documents - Download document +
The action allows to download the attached document.  +
Dependency of Gross Field +
The amount of money Employees receives before any taxes and deductions are taken out.  +
Dependency of Net Field +
The amount paid to employee on the day of payment  +
W
WorkSchedules - Accept Work Plan +
The button allows specific users to accept selected Work Schedules  +
T
Tasks - Close task +
The button allows users to close Task  +
Tasks - Close and create new +
The button allows users to close and create new Task  +
W
WorkSchedules - Undo Acceptance +
The button enables specific users to withdraw acceptance of selected Work Schedules  +
N
News - Publish +
The button for publishing news  +
d
department@person +
The department of the contact  +
department@Candidates +
The department of the contact  +
E
Employment History +
The description of functionalities enabling documentation collection and analysis related to terms of employment of employees  +
J
Job Description +
The description of the functionalities associated with workplace  +
T
Terms of Employment +
The employment conditions of the employee, including dates of commencement and termination of work as well as issues related to remuneration  +
D
Dependency of Delegation Duration +
The field is associated with the Delegation's Work Schedule  +
s
satisfied text@Surveys +
The field where user can add text if he chooses the question option is "Matrix" question.  +
n
neither text@Surveys +
The field where user can add text to the intermediate option.  +
d
dissatisfied text@Surveys +
The field where user can add text to unsatisfacton option  +
f
filename@Documents +
The filename of the document attachment  +
g
gsync id@Meetings +
The internal Google ID of the event record  +
l
last synced@Emails +
The last date and time the email was synced with the server  +
g
gsync lastsync@Meetings +
The last time this record was synced with Google Account as unix time  +
S
Survey Question Responses +
The module in which user saw a list of all questions from the survey along with the respons in tabular and graphic form.  +
L
Limit List +
The number of results can be limited to a certain value.  +
M
Meetings - Create new rekord +
The process of creating a new meeting.  +
A
Add call/meeting reminder process +
The process of creating a reminder in the form of a popup or e-mail that informs participants about a potential phone call or meeting.  +
T
Time Management +
The process of planning the time spent on various activities, which aims to increase the efficiency of the time used  +
R
Recruitment +
The recruitment process with a description of all records needed to carry it out  +
r
related doc name@Documents +
The related document name for Meta-Data framework  +
related doc rev number@Documents +
The related document version number for Meta-Data framework  +
s
status@Calls +
The status of the call (Held, Not Held, etc.)  +
p
primary address street@Candidates +
The street address used for primary address  +
n
name@Emails +
The subject of the email  +
t
title@person +
The title of the contact  +
title@Candidates +
The title of the contact  +
P
Periods of Employment +
The total employment time resulting from the individual contracts of an employee  +
D
Dependency of Spent Time +
The value in the field depends on certain fields in the Work Time records  +
Documents - Linking two documents +
This action allows to link one document to another.  +
C
Candidatures - Convert to employee +
This action creates new employee and user records from a candidature  +
s
status@Offboardings +
This filed informs about Onboarding status. It can be toggled between two values: In progress and Held. By default it is set to In progress.  +
status@Onboardings +
This filed informs about Onboarding status. It can be toggled between two values: In progress and Held. By default it is set to In progress.  +
D
Deploy MintHCM on Docker +
This guide covers the deployment of MintHCM in a Docker environment. We provide a comprehensive Docker Compose setup for deploying MintHCM in a containerized environment. <br> MintHCM is ready to go with this easy-to-use Docker configuration.  +
M
MintHCM Installation Guide +
This guide covers the installation process for MintHCM version 4.x onwards.  +
MintHCM 3.x Installation Guide +
This guide covers the installation process for MintHCM version 3.x.  +
Meetings - date start - Validation IsBefore +
This is a simple validation of the meeting start date field, which cannot be later than the end date.  +
D
Dependency of Employer Cost Field +
This is the actual amount paid for all employee wages and benefits.  +
C
Candidatures +
This module allows users to add a candidate to candidatures, thanks to which they will be able to participate in further recruitment processes.  +
Candidates +
This module allows users to add new Candidates, thanks to which they will be able to participate in further recruitment processes.  +
T
Tasks +
This module allows users to create new Task  +
D
Delegations +
This module stores comprehensive information regarding employees' business trips, their costs and duration. All conveniently linked to working time tracking and company resources.  +
T
Transportations +
This submodule of Delegations stores data on routes taken by traveling employees and means of transport they used. Car and train are available options, others can be specified. It is important to link an existing delegation to see all related transportation. Records can be further related to costs for reckoning fuel invoices or train/plane tickets etc.  +
N
News +
To create reminders and annoucements, that will be displayed to users  +
t
type@Emails +
Type of email (ex: draft)  +
r
repeat type@Calls +
Type of recurrence  +
repeat type@Meetings +
Type of recurrence  +
repeat type@WorkSchedules +
Type of recurrence  +
D
Default value of type field in Appraisal after Create Appraisal action +
Type of the appraisal generated by Create Appraisal action is automatically set to Recruiting  +
t
type@EmailTemplates +
Type of the email template  +
a
assigned user id@assignable +
User ID assigned to record  +
assigned user id@AOK Knowledge Base Categories +
User ID assigned to record  +
assigned user id@AOK KnowledgeBase +
User ID assigned to record  +
assigned user id@Applications +
User ID assigned to record  +
assigned user id@AppraisalItems +
User ID assigned to record  +
assigned user id@Appraisals +
User ID assigned to record  +
assigned user id@Benefits +
User ID assigned to record  +
assigned user id@Calls +
User ID assigned to record  +
assigned user id@Candidates +
User ID assigned to record  +
assigned user id@Candidatures +
User ID assigned to record  +
assigned user id@CareerPaths +
User ID assigned to record  +
assigned user id@Certificates +
User ID assigned to record  +
assigned user id@Competencies +
User ID assigned to record  +
assigned user id@CompetencyRatings +
User ID assigned to record  +
assigned user id@Conclusions +
User ID assigned to record  +
assigned user id@Delegations +
User ID assigned to record  +
assigned user id@DelegationsLocale +
User ID assigned to record  +
assigned user id@Documents +
User ID assigned to record  +
assigned user id@Emails +
User ID assigned to record  +
assigned user id@EmailTemplates +
User ID assigned to record  +
assigned user id@EmployeeRoles +
User ID assigned to record  +
assigned user id@ExitInterviews +
User ID assigned to record  +
assigned user id@FP events +
User ID assigned to record  +
assigned user id@FP Event Locations +
User ID assigned to record  +
assigned user id@Goals +
User ID assigned to record  +
assigned user id@Ideas +
User ID assigned to record  +
Retrieved from "https://wiki.minthcm.org/index.php?title=Property:Short_Description&oldid=376"