Version 1.2.0
In the new version of the SimpleOne HRMS application, we have added the capability to track changes in employment contracts from hiring to termination. To assess applicants' knowledge and skills, we have added hiring criteria. Hiring criteria are related to individual applicants or employees, as well as job posts and applicant submission tasks.
Improvements have been made to the management of position slots that are aimed at increasing budget owners' control over hiring. We have also made changes to onboarding requests to make it easier for HR agents in multi-company organizations to process such requests.
In this update, we have continued to expand the functionality of the Test HR forms by updating the Evaluation widget and making it possible to assign any user to review tests.
New features
Employment contracts
In the new HRMS version, we have added the capability to track changes in employment contracts signed between companies and their employees.
Now the Employment contract (hrm_employment_contract) table located at {URL your instance}/list/hrm_employment_contract contains not only current employment contracts but also records of the new child table Employment change (hrm_employment_change).
Creating an employment contract, changing it, or firing an employee with a contract automatically creates a new employment change record.
The list that contains only employment contract changes is located in Human Resource Management → Onboarding and Dismissal → Employment Contracts as before.
The new list that contains only employment change records is located in Human Resource Management → Onboarding and Dismissal → Employment Changes.
Read more in the Employment Contract and Employment Change articles.
Hiring criteria
In this HRMS version, we have added a new entity titled Hiring Criterion (hrm_hiring_criterion). By using hiring criteria in an Applicant Submission task, it is possible to evaluate the level of an applicant's knowledge and skills required for a job position.
The related lists with hiring criteria have been added to the Applicant (hrm_applicant), Job Post (hrm_job_post), and Applicant Submission (hrm_applicant_submission) tables.
Read more in the Hiring Criterion article.
Improvements
Position slot access
In the new version, we have restricted access to the operations with Position Slot (hrm_position_slot) records in order to enhance control over the company's budget. Now users with the hrm_manager role and hiring managers can specify an employment contract on the position slot form only after getting this slot approved by the budget owner (hrm_budget_owner).
We have also updated the state color model for the main entities of HRMS.
Read more in the Position Slot article.
Onboarding request
Another important update is the change of access to creating an onboarding request for a new hire. Now this service is available to organizational unit managers of all levels and their delegates, while other users need to have the hrm_agent or hrm_supervisor special roles.
Now, when creating an onboarding request for a new hire, you can specify any company from the list of those registered in the system.
The request in the agent interface now displays two new fields: Caller's company and New hire's company.
These improvements help users who process requests in multiple-company organizations.
Process HR forms of the Test category
Evaluation widget
In the improved version of the Evaluation widget, the author of a test now can specify only the minimum score range. The upper score is calculated automatically. For this reason, we have removed the Lower score and Upper score fields and added a new Min score field.
Read more in the HR Form article.
Fields
In the new version, respondents can view the correct and incorrect answers to the questions of the test if no retries are allowed.
To provide this functionality, we have removed the Show correct answers field and added a new Show answers field.
The number of retries can now be limited. This is done by filling in the new Number of retakes field, which is displayed if the Retake allowed checkbox is selected.
Checkers
Now any assigned users can check HR form instances of the Test category. For this reason, we have added a new Checkers field to the Launch (hrm_form_launch) form. The field is mandatory if the question type is Manual. The field is read-only on the respondents' instances.
When a respondent submits a filled instance, the checker receives an email notification and is able to check it both on the portal and in the agent interface.
After completing the work with the instance, the checker can now leave a comment to the respondent by filling in the General comment field.
Check type
The Check type field on the Question (hrm_form_question) forms no longer needs to be filled in manually. Now it is filled in automatically depending on the selected Response format:
- if the response format is Single select multiple choice or Multi-select multiple choice, the check type is Automatic,
- in all other cases, the check type is Manual.
Answer key
We have added a new Answer key field on the Question (hrm_form_question) forms for questions with the Constructed and File upload response formats. If the field is completed, the checker can check the answer of the respondent against the test author's answer.
Score per option
We have moved the Score per option field from the Response option (hrm_form_response_option) form to the Question (hrm_form_question) form. The field is displayed if the selected response format is Single select multiple choice or Multi-select multiple choice. All correct response options have the same weight in points.
Now the user needs to specify the score for each response option only once for each question.
State model
Since the functionality of HR forms belonging to the Test category has been expanded, a separate state model has been introduced for their Instances (hrm_form_instance):
| State | Description |
|---|---|
| New | An HR form instance enters this state after it is saved for the first time. |
| In progress | An HR form instance enters this state when the respondent starts filling out the instance. |
| Submitted | An HR form instance enters this state after its respondent clicks Submit on the instance. |
| Check in progress | An HR form instance enters this state after its checker clicks Check on the instance. |
| Completed | An HR form instance enters this state after the auto check is completed. If an HR form is checked manually, it enters this state after the checker clicks Send results on the instance. |
| Canceled | A New instance enters this state if its HR form launch is canceled or completed. |
Read more in the HR Form article.
Employee profile and history
The Organization unit view, which was used in the HRMS and Simple applications to work with the Employee (employee) table, has been renamed to HRMS.
Also, the Immediate unit field is now displayed instead of Unit on the Employee History (hrm_employee_history) forms.
Read more in the Employee Profile and Employee History articles.
Demo data
In the new version, we have also supplemented the demo- and master-data. The two lists can be found in the HRMS Demonstration and Master Data article.
Fixes
DEF0022402: We have fixed an issue where the employee selection would display a total number of respondents equal to zero when multiple companies were added to it.
DEF0021157: We have fixed a defect that made the mandatory Position slot field have an empty list of records when creating a new employee hiring request.
DEF0021031: We have fixed a defect that allowed users with the hrm_manager role to process an absence request without waiting for a re-approval.