Through this screen it is possible to establish general settings. This routine is controlled by the license file.
Lets make the routine for the approval of assessments of internal and external candidates.
Enter the email address of the person responsible for the Recruitment and Selection module that will be used in the messages sent through the SendEmail and EnviaEmailHtml programmer functions. To consider this address in the functions it is necessary to use the EmaRemPad system variable in the first parameter.
EnviaEmail (EmaRemPad, "candidato@email.com", "", "", "subject", "body text", "");
Email communication with Candidate
Select the email that will be used to communicate with the candidate:
Enter the rule code that will be used to send the new password to the candidate, if you do not want to use the default text.
Simultaneous selection processes
In this field you can define if candidates (with "active in the process") may participate in several simultaneous selection processes to include or reactivate a candidate in a selection process. This check is also made to change the status of a request to "in progress".
In this field you can define which template should be displayed by clicking the Print Ad nominations for screen.
It is possible to define the origin of the requirements (Location/position or groups of requirements). This field is available only with the routine of management skills (with legacy), located in module CS in Various Indications >, aba record.
It indicates the group uses requirements considered in recruitment. This field is available only with the routine of management skills (with or without legacy), located in module CS in Various Indications >, aba record.
To check the requirements for the groups, which are defined in the module CS in positions Requirements > > Group of requirements are used the groups that belong to the uses set out in this field and who have the capacity and the post request. If the field Group Requirements Use blank, the system considers all uses.
Inform the position structure considered in the register of the desired positions of the Web Curriculum. The record of previous employment is still considering the structure of positions informed fieldOffice Structure.
Indicate the job structure that will be used in the registration of external candidates' CVs via the Web. Lets make a structure of positions other than the same used by the company but which later, in the selection process is considered the position equivalent to the position of the request as pre-registration on tables/Positions/equivalency.
Enter the desired company.
This guide is only displayed when the workstation is used. On this window you can define the hierarchy of approvers window Scriptapproval.
Type Hierarchy Rank - Increase of vacancy
Inform the desired hierarchy for approval of vacancy cases.
Select a default reason for salary change. This information will be stored in the field Reason of wage information and request request to include a new record.
In this field you can change the name of the button, which is displayed on the screens of Candidate search and Selection > Selection > Manage selection processes.
External Candidate Curriculum Model
In this field you can define the model that is shown when external candidates are selected, by clicking the Resume in Applications > Selection x Ads. You can enter the code of the template or click the button Selection Models to select the desired model.
Internal Candidate Curriculum Model
In this field you can define the model that is shown when internal candidates are selected, by clicking the Resume in Applications > Selection x Ads. You can enter the code of the template or click the button Selection Models to select the desired model.
Customizable buttons
Just below the field Name Curriculum button, there are fields 1 st to 4th Button , which allow up to four custom buttons to be configured for reporting or executing LSP rules. These fields are composed of five spaces where they should be informed, in this order: button name, report template for external candidates, report template for internal candidates, LSP rule number and the screen where it should appear.
Set the pattern adopted for this filter. This pattern is observed when adding a new filter or include filters from a request.
Name/Mod/Reg Button 1-external
Report:
Reg name/Mod/2-external Button
Report:
Name/Mod/Reg Button 1-internal
Report:
Reg name/Mod/2 built-in Button
Report:
Enter "Yes" in this field to enable the change, inclusion and exclusion of dependents of the finalist candidates by the Web Curriculum. Once enabled in this field, the group corresponding to the dependents should be included in the Layout tab of the screen Registration of profiles of the curriculum WEB (FRGERLAY).
Allows non-registered neighbourhoods
This setting influences the District field and description on the window of registration of external candidates.
When this field is marked, whenever an employee is fired, he happens to be considered in selection processes, case is linked to an external candidate.
Such candidate:
Once the termination or clearance history are deleted, the candidate linked to the developer is:
Allows insurance lines not registered: this setting influences the acting Branch field and description on the window previous employment of employees and External candidates.
| Y | If "Yes", the Description field is enabled when reporting zero in code, allowing a branch of activity that does not exist in the base. |
| N | If "no", it is only possible to inform insurance lines in the base. The field is optional. When reporting zero in the code, the description will be empty. |
Allows administrative regions registered: this setting influences the field In and description on the window of External Candidates and Supplementary Sheet:
| Y | Yes, the Description field is enabled when reporting zero in code, allowing to inform an administrative region that does not exist in the base. |
| N | No, it is only possible to inform existing administrative regions at the base. The field is optional, reporting zero in the code, the description will be empty. |
Select a default reason for salary change. This information will be stored in the field Reason of wage information and request request to include a new record.
Inform acceptable codes of practice for ASO (Occupational Health Attestation). This information will be used when the registration of a new request for the field look like ASO is in the General requirements.
Inform the ASO types acceptable to the ASO (occupational health certificate). This information will be used when the registration of a new request for the ASO type field that lies in the General requirements.
Requisition Template
Report:
This parameter is intended to give the option to limit or not the vacancy (s) by area, as the vacancy (s) set (s) for the position in the contest.
This parameter is intended to allow the user to be alerted about the year field Competition located in the registration window requests.
Sets whether the tender allows pre-ranking. If set to "Yes", the button Classification of public procurement Register (selection > > Contest > Record tab Positions) will allow you to run even if some classifications step has not been evaluated.
Inform how the Medical Record code should be generated.
Enter the code of the rule that will be executed at the beginning of the individual or collective execution in Personnel Administration. This rule enables you to set criteria before identifying the candidate (s) to commit.
Must be registered to the personnel administration the same code rule used in RS.
Enter the rule that will be executed at the end of the individual or collective execution in Personnel Administration. Allows the criteria set out in the rule are broken boot in this rule.
Note
Must be registered to the personnel administration the same code rule used in RS.
Enter the rule that will be executed before each candidate completes. In this rule candidates can be identified allowing wide enough interference on the data of the basic specs of the developer (R034FUN) through this rule including user fields, with the exception of key fields (NumEmp, TipCol, NumCad) and in the case of collective manpower, the values of the fields modified via rule will be effectively recorded. In the case of individual manpower, the values of the fields changed via rule will be suggested on the window Basic form, and may be changed by the user before writing to the registry. To identify which routine is being executed, the variable EfeCan can be used. If the RS is integrated with the personnel administration-personnel administration, this rule will be executed at the moment in the schedule of Basic personnel administration, or will be performed in the execution of the RS.
In this rule may also be suggested at the salary history during the execution of the external and internal candidates fields (CodEst, ValSal, TipSal, CodMot, NivSal, ClaSal) R038HSA table (employee salary history).
Note
In all situations must be registered in the personnel administration the same code rule used in RS.
Enter the rule that will be executed after the completion of each candidate. Allows the conditions used in the rule before you commit are undone. If the RS is integrated with the personnel administration-personnel administration, is rule will be executed at the moment on basic Personal administration Record, or this rule will be executed on the execution of the RS. For key fields (NumEmp, TipCol, NumCad) (R034FUN) it is possible to read.
Note
Must be registered to the personnel administration the same code rule used in RS.
These rules will be used in the routine that updates external candidates from employees laid off, available on the Various Utilities > Updates > applicants.
This rule will be executed when you press the generate button on the window Updates in several Candidates > utilities. During the execution of the rule, you cannot use the feature ' table. ' Field to change records. If it is necessary to use the ExecSQL command. If the rule is executed the command Cancel (2), the whole process will be cancelled.
Rule Submission
This rule will be executed after the whole process of updating candidates ended. When the rule is executed, it is not possible to use ' table. ' Field to handle records. If it is necessary to use the ExecSQL command. If the rule is cancelled through the Cancel command (2), the whole process is cancelled. In relation to Cancel commands (0) and Cancel (1), these cancel the rule execution but not cancel the whole process.
Rule Before Update Candidate
This rule will be executed for each contributor selected, before updating the candidate. This rule will be possible to use the table feature. ' Field to view the information from the developer (for tables R034FUN, R122CEX and R036DEP). However, to change registers must use the ExecSQL command. If the rule is cancelled through the Cancel command (), the routine to update candidates will behave as follows:
Cancel (0)-rule Execution is canceled but process continues normally;
Cancel (1)-rule Execution is canceled and jumps to the next contributor fired;
Cancel (2)-Cancel the entire process.
Rule Then Upgrade Candidate
This rule will be executed for each contributor selected, after updating the candidate. This rule will be possible to use the table feature. ' Field to view the information from the developer. However, to change registers must use the ExecSQL command. If the rule from being canceled, the execution of the process will be aborted.
Set how many characters the AutoComplete feature is enabled.
Tell how long after the last character to be entered to enable the AutoComplete feature.
Specify the limit of records returned in the fields with the AutoComplete feature.
Through this field, you can set whether there should be a time to expire the curriculum Web browser session.
Through this tab you can customize the composition of the window for vacancies presentation, Web Curriculum public area.
If there are no registered settings, default to window existing ads system.