Skip to main content
Version: 1.3.2

Version 1.3.2

In this version, we have implemented job offers, overtime requests, and internal contract amendment requests. Document management is now faster and more convenient thanks to the generation of documents from templates. We have improved form interaction by enabling forms to be launched via subtasks and adding a universal link for form completion that can be shared with portal users. The workflow for filling out and interacting with form instances in the agent interface is now identical to the one on the portal.

To improve the notification process for stakeholders, we have added approvals for employment changes. We have also enhanced new hire requests by adding a check for available position slots, and updated the termination request model – it is now possible to specify delegates for departing managers to ensure business continuity while searching for a replacement. Additionally, resettable filters have been added to HRMS list views to display the records most relevant to employees.

We have also improved the user experience by fixing a number of defects.

New features​

Job offers​

It is now possible to register sent job offers in the system. This prevents data distortion or loss when processing papers.

Job offers are created via the related list of the same name on the Applicant Submission form and are stored in the Job Offer (hrm_job_offer) table. They display all the core information regarding the applicant's negotiated employment terms: their position, salary and other payments, work format, schedule, employment date, and more. Once created, job offers are subject to approval by managers. The applicant must accept the offer to move to the next stage.

Read more in the Job Offer article.

Employment change approval procedure​

To keep managers informed about modifications to employment contracts, an approval procedure has been implemented for the Employment Change (hrm_employment_change) table records.

You can Send for approval changes that are in the Draft or Rejected state. The state then changes to Pending approval, and notifications are sent to the approvers. If at least one approver rejects the change, it enters the Rejected state. Once approved by all the participants, the change moves to the Pending signature state.

The signing of the change can be confirmed by clicking the Document signed button. After signing, the change moves to either the Awaiting Activation or Active state, depending on its start date.

An HR change and an employment contract can also be Archived. When an active employment contract is archived, a termination HR change record is created, and the Hiring horizon, Vacancy, and Employment contract fields are cleared in the associated position slot.

Read more in the Employment Change and Employment Contract articles.

Internal employment contract amendment request​

Employment changes within a company can now be requested and tracked using internal employment contract amendment requests.

These requests are created by managers for their subordinates. The request form contains both current and proposed values. If the position changes, the related slot is reserved, if any.

Once created, the request is sent for approval to the head of the company, as well as to the new organizational unit head and the new direct manager if corresponding changes were made. The request is rejected if at least one approver rejects it. A rejected request can be edited and resent for a repeat approval.

The request is assigned to the group specified in the hrm.hrm_request.default_group_for_employment_change_model system property (by default, HR Document Management / Кадровый документооборот). The agent processes the request and creates an employment change based on its results by clicking the Create employment change button. If necessary, the employment change values can be edited, which will require a repeat approval. The request can be completed once the related employment change moves to the Pending activation or Active state.

Read more in the Subordinate's Employment Contract Amendment Request article.

Generation of documents from templates​

Starting with the new version, documents can be generated automatically.

To do this, you need to create document templates with tags. Documents will be generated based on these templates, replacing the tags with the required values. You can click the Generate document button on a form of any table, provided the Generate document widget is included in its layout. By default, this widget is available on the Plan an absence portal page when requesting paid and unpaid leave, as well as on the Resign or terminate an employee page.

Templates are stored in the Document Templates (hrm_company_document, formerly Company Documents) table, and tags are stored in the Template Tags (hrm_template_tag) table.

Read more in the Document Template with Tags and Document Template Tags articles.

Now you can share a link to HR forms with portal users.

To this end, the Link access checkbox was added to the form launch modal window. If you select this checkbox along with the Launch now checkbox, the link to the form is automatically copied to the clipboard upon clicking Launch in the modal window. It can also be copied manually by clicking Copy Link. Automatic copying and the Copy link button are available for One-time launches in the Scheduled or In Progress state, and for Regular launches In Progress executed Periodically.

Users who open the form via the link are automatically designated as Respondents. Portal users' access to the form via the link can be revoked by clearing the Link access checkbox, provided the launch is in the Scheduled or In Progress state.

We have also modified the logic for existing launches:

  • The Start date and time field is editable if the launch is One-time and in the Scheduled state. To modify the start date and time of a regular launch, create a new launch with required values.
  • Adding or modifying the list of Checkers is only possible before the launch is completed. Removed checkers will be able to finish working on the tests they have already started, but they will not be able to review any new instances.

Read more in the HR Form Launch article.

Overtime work request​

Employees can now submit requests for overtime work. Users with the hrm_agent role, direct managers, and their delegates can submit these requests on behalf of other employees. Requests are submitted on the service portal and are stored in the HRM Request (hrm_request) table of the agent interface.

An overtime request is subject to approval by the manager or, if it is submitted on behalf of another employee, by that employee. Rejected requests can be resent for a repeat approval. Once approved, the request is assigned to HR Document Management specialists for processing.

Read more in the Overtime Work Request article.

Improvements​

Onboarding request​

We have added a check for the availability of position slots when creating a new hire request. This reduces the likelihood of the request being delayed at subsequent processing stages.

To this end, the Position field is now displayed on the request form instead of the Job title field. When the Position field is filled, the system checks for the presence of related slots in the Approved, Available, or Recruiting state. If such slots are found, a mandatory Position slot field appears, where the corresponding slots become available for selection. If no slots are found, further work with the request is impossible until a corresponding slot is created and approved.

When a slot is selected in the request and the record is saved, the slot moves to the Reserved state. If the related onboarding request is closed unresolved, the slot status automatically changes to:

  • Recruiting if the slot is related to a vacancy,
  • Available if the slot is not related to a vacancy but has a hiring horizon specified,
  • Approved in all other cases.

Company is now automatically populated with the value for the current employee, and Organizational unit is populated with the value of the Immediate unit of the current employee. These values can be modified, and the Organizational unit can be selected from those existing for the Company.

The request can now be completed only if an Employment contract is specified. The contract can be created directly from the hire request form. In this case, if a related Applicant submission exists for the request, the employment contract will be pre-filled with information from the last approved job offer.

Read more in the Onboarding Request article.

Resignation or termination requests and launching forms from subtasks​

We have enhanced the Resign or terminate an employee request model: it now includes a Delegate field to specify the employee who will perform the duties of the departing person while a replacement is being searched for. The Delegate field is displayed on the form if the departing Employee is an organizational unit head or manager. Upon closing the resignation or termination request, the employee specified in the Delegate field is designated as the head of the organizational unit or manager. After the resignation or termination request is closed with the Resolved code, the departing employee's record is deactivated.

We have also added the ability to launch forms from subtask records that are in the New or In Progress state. To this end, the following items have been added to subtask forms:

  • a Form completion required checkbox,
  • a Forms field and a Launch forms button, which appear after the checkbox is selected,
  • Form Launches and Form Instances related lists, which display the launches and instances created via the subtask. The Form Instances list is also displayed on the forms of HRM Requests and Employee Tasks related to the subtask.

The Exit Interview (Проведение выходного интервью) subtask template now requires the completion of the corresponding forms: Exit-interview (employee) and Exit-interview (company). A Form instance attribute has been added to the termination request model to specify the instances associated with the employee's departure.

Agent interface users can now fill out, approve, and view instances the same way this is done on the portal, provided they have the necessary access permissions. Interaction with instances is also possible via the Form Instances related list.

Respondents can now fill out and resubmit rejected instances.

Read more in the following articles:

List views, navigation and access​

To help users focus on the tasks and information relevant to them, we have added corresponding filters to a number of list views accessed via the navigation menu.

Where appropriate, employees will see active records related to them by default, while managers will also see records related to their subordinates. These filters can be reset to view all the records that the user has the permission to read.

List views with updated filters
  • Employment Contracts
  • Employment Changes
  • Loyalty Cards
  • HRM Requests (All Requests, Onboarding Requests, Requests for Dismissal; Absences and Vacations and HR Documents menu categories and their items)
  • Subtasks
  • Available Absences
  • Form Launches
  • Form Responses
  • Employee Tasks
  • Applicant Submissions
  • Job Posts
  • Job Publication
  • Applicants
  • CVs
  • Position Slots
  • Positions

Read permissions for records have also been modified:

  • HRM Subtasks can now be viewed by approvers.
  • Employee Tasks can now be viewed by the approvers of their related subtasks. These tasks can also be viewed by members of the assigned group.
  • Positions can now be viewed by heads of higher-level organizational units.
  • Position Slots can now be viewed and edited by heads of higher-level organizational units.

Items have been added to the Absences and Vacations and HR Documents menu categories, allowing users to view all their records or specific types only. We have also added the hrm.request_models_visible_to_managers system property, where you can specify the request models to which managers will have read access.

Fixes​

DEF0023553: Fixed a defect where line breaks disappeared from the Introduction field of the HR form after saving.

DEF0023538: Fixed a defect where, when creating a subtask via the related list on the Employee Tasks form, the Forms field was displayed even though the Form completion required checkbox was cleared.

DEF0023390: Fixed an issue where the tooltip was not displayed in the document generation widget on the job offer form.

DEF0023385: Fixed a defect where the Result field was not cleared when returning a completed request to work.

DEF0023159: Fixed an issue where changing the dates and manager in a leave request resulted in the approval request being sent to the previous manager.

DEF0023056: Fixed a defect where negative values were allowed and processed in the Days count at your own expense field when requesting vacation.

DEF0023050: Fixed a defect where it was possible to submit a day off request on the portal with a Days count at your own expense exceeding the available Absence time.

DEF0022372: Fixed an issue where the total score in Test type forms included points for deactivated questions when duplicating questions or the form itself.

DEF0022347: Fixed a defect where the recruitment funnel was not displayed and approval requests were created during applicant submission task creation if the specified job post lacked a position slot.