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@Applications + (Name of the user who modified the record)
- Field:modified by name@AppraisalItems + (Name of the user who modified the record)
- Field:modified by name@Appraisals + (Name of the user who modified the record)
- Field:modified by name@Benefits + (Name of the user who modified the record)
- Field:modified by name@Calls + (Name of the user who modified the record)
- Field:modified by name@Candidates + (Name of the user who modified the record)
- Field:modified by name@Candidatures + (Name of the user who modified the record)
- Field:modified by name@CareerPaths + (Name of the user who modified the record)
- Field:modified by name@Certificates + (Name of the user who modified the record)
- Field:modified by name@Competencies + (Name of the user who modified the record)
- Field:modified by name@CompetencyRatings + (Name of the user who modified the record)
- Field:modified by name@Conclusions + (Name of the user who modified the record)
- Field:modified by name@Delegations + (Name of the user who modified the record)
- Field:modified by name@DelegationsLocale + (Name of the user who modified the record)
- Field:modified by name@Documents + (Name of the user who modified the record)
- Field:modified by name@Emails + (Name of the user who modified the record)
- Field:modified by name@EmployeeRoles + (Name of the user who modified the record)
- Field:modified by name@Employees + (Name of the user who modified the record)
- Field:modified by name@ExitInterviews + (Name of the user who modified the record)
- Field:modified by name@FP events + (Name of the user who modified the record)
- Field:modified by name@FP Event Locations + (Name of the user who modified the record)
- Field:modified by name@Goals + (Name of the user who modified the record)
- Field:modified by name@Ideas + (Name of the user who modified the record)
- Field:modified by name@Improvements + (Name of the user who modified the record)
- Field:modified by name@Meetings + (Name of the user who modified the record)
- Field:modified by name@News + (Name of the user who modified the record)
- Field:modified by name@NonWorkingDays + (Name of the user who modified the record)
- Field:modified by name@Notes + (Name of the user who modified the record)
- Field:modified by name@Offboardings + (Name of the user who modified the record)
- Field:modified by name@OffboardingTemplates + (Name of the user who modified the record)
- Field:modified by name@OnboardingOffboardingElements + (Name of the user who modified the record)
- Field:modified by name@Onboardings + (Name of the user who modified the record)
- Field:modified by name@OnboardingTemplates + (Name of the user who modified the record)
- 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.)
- 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.)
- Field:phone other@person + (Other phone number for the contact)
- Field:phone other@Candidates + (Other phone number for the contact)
- Field:file url@Notes + (Path to file (can be URL))
- Feature:Dependency of Period Ending Date + (Period Ending Date is the date the employee ends work)
- Feature:Dependency of Period Starting Date + (Period Starting Date is the date when the employee starts work)
- Field:assistant phone@person + (Phone number of the assistant of the contact)
- Field:assistant phone@Candidates + (Phone number of the assistant of the contact)
- Field:body@EmailTemplates + (Plain text body to be used in resulting email)
- Choosing means of transport + (Planning transportation during business trip)
- Field:portal flag@Notes + (Portal flag indicator determines if note created via portal)
- Field:alt address postalcode@person + (Postal code for alternate address)
- Field:alt address postalcode@Candidates + (Postal code for alternate address)
- Field:primary address postalcode@person + (Postal code for primary address)
- Field:primary address postalcode@Candidates + (Postal code for primary address)
- 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.)
- Field:name@Project + (Project name)
- Report the trip + (Reckoning delegations)
- Field:repeat pane@Meetings + (Repeat Pane)
- Field:repeat pane@WorkSchedules + (Repeat Pane)
- Field:repeat until@Calls + (Repeat until specified date)
- Field:repeat until@Meetings + (Repeat until specified date)
- Field:repeat until@WorkSchedules + (Repeat until specified date)
- Field:text only@EmailTemplates + (Should be checked if email template is to be sent in text only)
- Delegations Locale + (Simple reference module to set and store data on basic costs of travelling to certain countries.)
- Field:recurring source@Calls + (Source of recurring call)
- Field:recurring source@Meetings + (Source of recurring meeting)
- 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.)