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.
List of results
- Field:modified by name@OrganizationalUnits + (Name of the user who modified the record)
- Field:modified by name@OutboundEmailAccounts + (Name of the user who modified the record)
- Field:modified by name@PeriodsOfEmployment + (Name of the user who modified the record)
- Field:modified by name@Positions + (Name of the user who modified the record)
- Field:modified by name@Problems + (Name of the user who modified the record)
- Field:modified by name@Project + (Name of the user who modified the record)
- Field:modified by name@ProjectTask + (Name of the user who modified the record)
- Field:modified by name@Recruitments + (Name of the user who modified the record)
- Field:modified by name@Reservations + (Name of the user who modified the record)
- Field:modified by name@Resources + (Name of the user who modified the record)
- Field:modified by name@Responsibilities + (Name of the user who modified the record)
- Field:modified by name@ResponsibilityActivities + (Name of the user who modified the record)
- Field:modified by name@SpentTime + (Name of the user who modified the record)
- Field:modified by name@SurveyQuestionOptions + (Name of the user who modified the record)
- Field:modified by name@SurveyQuestionResponses + (Name of the user who modified the record)
- Field:modified by name@SurveyQuestions + (Name of the user who modified the record)
- Field:modified by name@SurveyResponses + (Name of the user who modified the record)
- Field:modified by name@Surveys + (Name of the user who modified the record)
- Field:modified by name@Tasks + (Name of the user who modified the record)
- Field:modified by name@TermsOfEmployment + (Name of the user who modified the record)
- Field:modified by name@Trainings + (Name of the user who modified the record)
- Field:modified by name@Transportations + (Name of the user who modified the record)
- Field:modified by name@Users + (Name of the user who modified the record)
- Field:modified by name@UsersNews + (Name of the user who modified the record)
- Field:modified by name@WorkingMonths + (Name of the user who modified the record)
- Field:modified by name@WorkSchedules + (Name of the user who modified the record)
- Field:repeat count@Calls + (Number of recurrence)
- Field:repeat count@Meetings + (Number of recurrence)
- Field:repeat count@WorkSchedules + (Number of recurrence)
- Offboarding Templates + (Offboarding Templates are used for generating an actual offboarding for a particular employee and position)
- Feature: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)
- Feature: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.)
- Feature:Close Onboarding/Offboarding if all other elements are closed + (On save, if status of Exit Interview/Task/ … 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'.arding/Offboarding also changes to 'Held'.)
- Feature: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')
- Feature: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')
- Onboarding Templates + (Onboarding Templates are used for generating an actual onboarding for a particular employee and position)
- 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.)