Search by property

From MintHCM Wiki

This page provides a simple browsing interface for finding entities described by a property and a named value. Other available search interfaces include the page property search, and the ask query builder.

Search by property

A list of all pages that have property "Short Description" with value "The field is associated with the Delegation's Work Schedule". Since there have been only a few results, also nearby values are displayed.

Showing below up to 244 results starting with #1.

View (previous 500 | next 500) (20 | 50 | 100 | 250 | 500)


    

List of results

  • 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.)
  • Feature:Dependency of Work Schedule Type  + (Specific types of Work Schedule have additional fields or options)
  • 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.)
  • Field: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)
  • Field: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)
  • Field:reminder time@Calls  + (Specifies when a reminder alert should be issued; -1 means no alert; otherwise the number of seconds prior to the start)
  • Field:reminder time@Meetings  + (Specifies when a reminder alert should be issued; -1 means no alert; otherwise the number of seconds prior to the start)
  • Field:status@SpentTime  + (Spent time record status)
  • Field:description@basic  + (Standard text field to store additional notes about the record)
  • Field:description@AOK Knowledge Base Categories  + (Standard text field to store additional notes about the record)
  • Field:description@AOK KnowledgeBase  + (Standard text field to store additional notes about the record)
  • Field:description@Applications  + (Standard text field to store additional notes about the record)
  • Field:description@AppraisalItems  + (Standard text field to store additional notes about the record)
  • Field:description@Appraisals  + (Standard text field to store additional notes about the record)
  • Field:description@Benefits  + (Standard text field to store additional notes about the record)
  • Field:description@Calls  + (Standard text field to store additional notes about the record)
  • Field:description@Candidates  + (Standard text field to store additional notes about the record)
  • Field:description@Candidatures  + (Standard text field to store additional notes about the record)
  • Field:description@CareerPaths  + (Standard text field to store additional notes about the record)
  • Field:description@Certificates  + (Standard text field to store additional notes about the record)
  • Field:description@Competencies  + (Standard text field to store additional notes about the record)
  • Field:description@CompetencyRatings  + (Standard text field to store additional notes about the record)
  • Field:description@Conclusions  + (Standard text field to store additional notes about the record)
  • Field:description@Delegations  + (Standard text field to store additional notes about the record)
  • Field:description@DelegationsLocale  + (Standard text field to store additional notes about the record)
  • Field:description@Documents  + (Standard text field to store additional notes about the record)
  • Field:description@Emails  + (Standard text field to store additional notes about the record)
  • Field:description@EmailTemplates  + (Standard text field to store additional notes about the record)
  • Field:description@EmployeeRoles  + (Standard text field to store additional notes about the record)
  • Field:description@Employees  + (Standard text field to store additional notes about the record)
  • Field:description@ExitInterviews  + (Standard text field to store additional notes about the record)
  • Field:description@FP events  + (Standard text field to store additional notes about the record)
  • Field:description@FP Event Locations  + (Standard text field to store additional notes about the record)
  • Field:description@Goals  + (Standard text field to store additional notes about the record)
  • Field:description@Ideas  + (Standard text field to store additional notes about the record)
  • Field:description@Improvements  + (Standard text field to store additional notes about the record)
  • Field:description@Meetings  + (Standard text field to store additional notes about the record)
  • Field:description@News  + (Standard text field to store additional notes about the record)
  • Field:description@NonWorkingDays  + (Standard text field to store additional notes about the record)
  • Field:description@Notes  + (Standard text field to store additional notes about the record)
  • Field:description@Offboardings  + (Standard text field to store additional notes about the record)
  • Field:description@OffboardingTemplates  + (Standard text field to store additional notes about the record)
  • Field:description@OnboardingOffboardingElements  + (Standard text field to store additional notes about the record)
  • Field:description@Onboardings  + (Standard text field to store additional notes about the record)
  • Field:description@OnboardingTemplates  + (Standard text field to store additional notes about the record)
  • Field:description@OrganizationalUnits  + (Standard text field to store additional notes about the record)
  • Field:description@PeriodsOfEmployment  + (Standard text field to store additional notes about the record)
  • Field:description@Positions  + (Standard text field to store additional notes about the record)
  • Field:description@Problems  + (Standard text field to store additional notes about the record)
  • Field:description@Project  + (Standard text field to store additional notes about the record)
  • Field:description@ProjectTask  + (Standard text field to store additional notes about the record)
  • Field:description@Recruitments  + (Standard text field to store additional notes about the record)
  • Field:description@Reservations  + (Standard text field to store additional notes about the record)
  • Field:description@Resources  + (Standard text field to store additional notes about the record)
  • Field:description@Responsibilities  + (Standard text field to store additional notes about the record)
  • Field:description@ResponsibilityActivities  + (Standard text field to store additional notes about the record)
  • Field:description@SpentTime  + (Standard text field to store additional notes about the record)
  • Field:description@SurveyQuestionOptions  + (Standard text field to store additional notes about the record)
  • Field:description@SurveyQuestionResponses  + (Standard text field to store additional notes about the record)
  • Field:description@SurveyQuestions  + (Standard text field to store additional notes about the record)
  • Field:description@SurveyResponses  + (Standard text field to store additional notes about the record)
  • Field:description@Surveys  + (Standard text field to store additional notes about the record)
  • Field:description@Tasks  + (Standard text field to store additional notes about the record)
  • Field:description@TermsOfEmployment  + (Standard text field to store additional notes about the record)
  • Field:description@Trainings  + (Standard text field to store additional notes about the record)
  • Field:description@Transportations  + (Standard text field to store additional notes about the record)
  • Field:description@Users  + (Standard text field to store additional notes about the record)
  • Field:description@UsersNews  + (Standard text field to store additional notes about the record)
  • Field:description@WorkingMonths  + (Standard text field to store additional notes about the record)
  • Field:description@WorkSchedules  + (Standard text field to store additional notes about the record)
  • Field:alt address state@person  + (State for alternate address)
  • Field:alt address state@Candidates  + (State for alternate address)
  • Field:primary address state@person  + (State for primary address)
  • Field:primary address state@Candidates  + (State for primary address)
  • Feature: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.)
  • Positions  + (Stores all the information about positions)
  • Documents  + (Stores electronic versions of documents)
  • Reservations  + (Stores information about the reservations of resources)
  • User's News  + (Stores information about which users have read the news)
  • Document Revisions  + (Stores the versions of a document)
  • Field:alt address street@person  + (Street address for alternate address)
  • Field:alt address street@Candidates  + (Street address for alternate address)
  • Field:primary address street@person  + (Street address for primary address)
  • Action:WorkSchedules - Submit  + (Submit button allows user to close a Work Schedule)
  • Action:Surveys - Survey Responses  + (Subpanel to check submitted responses. All responses are added with the creation date.)
  • Field:parent type@Notes  + (Sugar module the Note is associated with)
  • Field:intent@Emails  + (Target of action used in Inbound Email assignment)
  • Feature:Feature:Tasks - due date - color selection on the list view  + (Tasks due_date changes color if exceeded (View list))
  • Tasks to be done during onbording process  + (Tasks generated in the onboarding process that the employee should perform independently.)
  • Emails  + (The "Emails" module is designed to enhanceThe "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.d current with their email communications.)
  • Employees  + (The "Employees" module is thoughtfully craThe "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. retrieval and reference for future needs.)
  • Locations  + (The "Locations" module offers a straightfoThe "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.sers to quickly select appropriate venues.)
  • Non Working Days Registry  + (The "Non Working Days" module is a straightforward tool designed to manage non-working days within the system.)
  • Project Tasks  + (The "Project Task" module is a component oThe "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.s, timelines, priorities, and assignments.)
  • Project  + (The "Project" module is designed to streamThe "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.resources for efficient project execution.)
  • 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.)
  • Working Months  + (The "Working Months" module serves is a tool to input the number of working days within a given month.)
  • Basic  + (The <b>Basic</b> template type provides basic fields, such as the Name, Assigned to, Team, Date Created and Description fields.)
  • 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.)
  • Activities  + (The Activities module enables users to strThe 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.praisal items for performance evaluations.)
  • Applications  + (The Applications module within MintHCM sysThe 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-makingrity and accountability in decision-making)
  • Appraisal Items  + (The Appraisal Items module in MintHCM systThe 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.hich candidates or employees are assessed.)
  • Appraisals  + (The Appraisals module is a tool primarily 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.ffers flexibility in candidate assessment.)
  • Benefits  + (The Benefits module in MintHCM serves as aThe 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.d benefits for transparency and awareness.)
  • Calendar  + (The Calendar Module within the MintHCM SysThe 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.res effective scheduling and productivity.)
  • Competency Ratings  + (The Competency Ratings module in MintHCM iThe 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. decisions about training and development.)
  • Feature: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.)
  • 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.)
  • Feature: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)
  • 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.)
  • 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.)
  • Field:parent id@Notes  + (The ID of the Sugar item specified in parent_type)
  • Field:parent id@Calls  + (The ID of the parent Sugar object identified by parent_type)
  • 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.)
  • KB - Categories  + (The Knowledge Base Category Module efficieThe 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.uctured and interconnected knowledge base.)
  • Installation guide MintHCM v4  + (The MintHCM Installing Guide is a technicaThe 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.up and configure the software effectively.)
  • 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)
  • Problems  + (The Problems module is a tool for companieThe 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.and problem resolution among team members.)
  • Field:parent type@Calls  + (The Sugar object to which the call is related)
  • Field:parent type@Tasks  + (The Sugar object to which the call is related)
  • Feature: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)
  • Feature: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.)
  • 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.)
  • Action:Documents - Download document  + (The action allows to download the attached document.)
  • Feature:Dependency of Gross Field  + (The amount of money Employees receives before any taxes and deductions are taken out.)
  • Feature:Dependency of Net Field  + (The amount paid to employee on the day of payment)
  • Action:WorkSchedules - Accept Work Plan  + (The button allows specific users to accept selected Work Schedules)
  • Action:Tasks - Close task  + (The button allows users to close Task)
  • Action:Tasks - Close and create new  + (The button allows users to close and create new Task)
  • Action:WorkSchedules - Undo Acceptance  + (The button enables specific users to withdraw acceptance of selected Work Schedules)
  • Action:News - Publish  + (The button for publishing news)
  • Field:department@person  + (The department of the contact)
  • Field:department@Candidates  + (The department of the contact)
  • Employment History  + (The description of functionalities enabling documentation collection and analysis related to terms of employment of employees)
  • Job Description  + (The description of the functionalities associated with workplace)
  • Terms of Employment  + (The employment conditions of the employee, including dates of commencement and termination of work as well as issues related to remuneration)