Difference between revisions of "Module:Candidatures"
(Created page with "{{Module-infobox |Module-name=Candidatures |Module-tech-name=Candidatures |Module-class=Candidatures |Module-type=Standard |Module-template=security_groups,assignable,basic |M...") |
|||
Line 10: | Line 10: | ||
|Module-reportable=Yes | |Module-reportable=Yes | ||
|Module-hidden=No | |Module-hidden=No | ||
− | |Short Description= | + | |Short Description=This module allows users to add a candidate to candidatures, thanks to which they will be able to participate in further recruitment processes. |
}} | }} | ||
− | |||
=={{int:ev-business_description}}== | =={{int:ev-business_description}}== | ||
+ | The next step in the recruitment process is assigning a [[Module:Candidates|candidate]] to suitable candidatures. One candidate can be assigned to many candidatures. | ||
+ | In this module, users can check and change the status of the candidature. We can choose from several different levels that will allow us to define the candidate's stage precisely. The module in cerate mode is divided into three main sections. In the first section, in addition to the status, we set the original and current recruitment, application date, description or source of acquisition of the candidate and his scoring. The second section contains the candidate's financial expectations and the type of contract. In the third section, we already introduce the terms of employment and possible notes. | ||
+ | After creating a candidacy, we have two options: make an [[Module:Appraisals|appraisal]] and convert the candidacy into an employee. | ||
+ | The [[Action:Candidatures - Create Appraisal|Create Appraisal]] button creates a record in the [[Module:Appraisals|appraisal]] module, in which we are automatically assigned the skills and requirements to be assessed on a given [[Module:Positions|position]]. | ||
− | [[ | + | The [[Action:Candidatures - Convert to employee|Convert to employee]] button allows you to quickly transform a candidate for an employee, distinguishing between an employee without access and with access to the system (user). |
{{Module-links}} | {{Module-links}} | ||
− | + | {{technical-description}} | |
{{DevNotes}} | {{DevNotes}} |
Latest revision as of 12:57, 6 September 2021
Candidatures | |
---|---|
Name: | Candidatures |
Tech Name: | Candidatures |
Class Name: | Candidatures |
Type: | Standard |
Template: | Security_groups, Assignable, Basic |
Custom Module: | No |
Auditable: | Yes |
Importable: | No |
Reportable: | Yes |
Hide module on Main Page: | No |
Contents
[hide]Short Description
This module allows users to add a candidate to candidatures, thanks to which they will be able to participate in further recruitment processes.
Business Description
The next step in the recruitment process is assigning a candidate to suitable candidatures. One candidate can be assigned to many candidatures. In this module, users can check and change the status of the candidature. We can choose from several different levels that will allow us to define the candidate's stage precisely. The module in cerate mode is divided into three main sections. In the first section, in addition to the status, we set the original and current recruitment, application date, description or source of acquisition of the candidate and his scoring. The second section contains the candidate's financial expectations and the type of contract. In the third section, we already introduce the terms of employment and possible notes. After creating a candidacy, we have two options: make an appraisal and convert the candidacy into an employee.
The Create Appraisal button creates a record in the appraisal module, in which we are automatically assigned the skills and requirements to be assessed on a given position.
The Convert to employee button allows you to quickly transform a candidate for an employee, distinguishing between an employee without access and with access to the system (user).
Custom Actions
Action | Type | Short Description |
---|---|---|
Candidatures - Create Appraisal | DetailView Button | Create Appraisal button in a candidature record view starts a background action that creates appraisal, which, after it is created, is related to the candidature. |
Convert to employee | DetailView Button | This action creates new employee and user records from a candidature |
Processes
Related Processes
Process | Short Description |
---|---|
Meetings - Create new rekord | The process of creating a new meeting. |
Recruitment | The recruitment process with a description of all records needed to carry it out |
Related Features
Initiating
Name | Type | Short Description | Initiating Fields | Affected Fields | Affected Modules |
---|---|---|---|---|---|
Feature:Appraisal Items generated from Competencies | Automation | [[Module:Appraisal Items|]] |
Structure
Fields
Relationships
Laft | Type | Right | Short Description | Relationship |
---|---|---|---|---|
Candidates | one-to-many | 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 - Candidatures |
Candidatures | one-to-many | Appraisals | One Candidature record can have many related Appraisals records, but a specific Appraisals record can be related to only one Candidature record. | Relationship: Candidatures - Appraisals |
Candidatures | one-to-many | Calls | Flex relate used in Candidature | Relationship: Candidatures - Calls |
Candidatures | one-to-many | Meetings | Flex relate used in Candidature | Relationship: Candidatures - Meetings |
Candidatures | one-to-many | Notes | Flex relate used in Candidature | Relationship: Candidatures - Notes |
Candidatures | one-to-many | Tasks | Flex relate used in Candidature | Relationship: Candidatures - Tasks |
Recruitments | one-to-many | 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 |
Recruitments | one-to-many | 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 |
Users | one-to-many | Candidatures | Specific Sugar user can modify many account records, but specific account record last modification was performed by specific user. | Relationship: Users - Candidatures |
Users | one-to-many | Candidatures | Specific Sugar user can create many account records, but specific account record can be created by only one user. | Relationship: Users - Candidatures |
Users | one-to-many | Candidatures | Specific Sugar user can be assigned to many account records, but specific account record can only have one user assigned. | Relationship: Users - Candidatures |