Configurable personnel information method

Abstract

The invention relates to the field of enterprise personnel management, and provides a configurable personnel information management method. The problems of fixed field limitation and inflexible information management of a traditional system are solved, and the design and implementation of the method are promoted. According to the method, a three-level Web page is constructed through a front end, an administrator is allowed to configure a personnel template according to requirements, further, a certain template enters a second-level page to configure field groups of the template, and a certain group enters a third-level page to configure attributes of each field of the template, including page display and edit authority control; the user can inquire, add, modify and cancel personal information, and the timeliness and accuracy of data management are improved. According to the embodiment of the invention, the efficiency and the flexibility of enterprise human resource management are effectively improved, and the method adapts to the demand changes of different customers.

Description

Technical Field

[0001] The present invention relates to the field of enterprise personnel management, and in particular to a configurable personnel information method, especially for the needs of continuous improvement of personnel information and increase of fields. Background Art

[0002] The personnel information method refers to the maintenance and presentation of employee roster information in the personnel management system by configuring personnel information fields in Web applications. With the continuous expansion of enterprise scale and the increasing complexity of organizational structure, enterprises have more and more diverse needs for personnel field management and personnel information presentation. Different customers have different needs for the presentation, increase and decrease, and permission control of personnel information fields. In order to meet the needs of different customers, developers need to be able to flexibly configure fields and dynamically present personnel information.

[0003] However, the existing personnel information management system is based on preset fields, which has the following major problems: fixed and non-scalable fields. The fields of traditional personnel management systems are fixed and cannot be flexibly adjusted according to the actual needs of enterprises; lack of flexible configuration and customization functions. Existing systems usually lack customized configuration functions for personnel information, and enterprises cannot define new fields or modify the properties of existing fields. This limitation makes the human resources department very passive in information collection and management; the information modification process is complicated and the audit is missing, which leads to untimely information updates, incomplete audit records, and difficulty in tracing change history, affecting the accuracy and security of data. Summary of the invention

[0004] The purpose of the present invention is to provide a configurable personnel information method to solve the technical problem that the prior art can only perform limited attribute configuration on fixed fields and lacks the differentiated requirements of personnel information pages that may exist for different customers.

[0005] In order to solve the above problems, the present invention specifically provides the following technical solutions.

[0006] A configurable personnel information method has the following steps: S1. In the front-end web page, a personnel parameter page is provided for user managers, and the page includes a sub-page of a personnel template; S2. Implementing the configuration function of the personnel information template through the sub-page of the personnel template, including operations of adding, copying, editing, and invalidating the template, and operations of publishing and canceling the template; S3. In the sub-page of the personnel template, an edit button is provided. After the administrator clicks the button, the user enters the setting screen of the personnel information field group of the template; S4. In the setting screen, the administrator configures the properties of the group, configures the sorting of all groups, and configures the function name, table name, primary key name, whether ESS is displayed, and whether employees can modify each group; S5. Each group has an edit button for subordinates. After clicking it, the administrator enters the edit page of all subordinate personnel information fields of the group. In this page, select to add or remove fields, and configure the properties of each field, including: table name, field name, field title, multilingual title key, placeholder text, data type, one row and one column, field type, data source, data source method, initial value, whether it is required, whether it is valid, whether it is a change field, whether it can be modified by employees, whether it is displayed in ESS, whether multiple selections are allowed, and field description; S6. In the front-end web page, in the ESS employee self-service system, provide a personnel information query page, a personnel information addition and modification window, and a cancellation window; S7. In the front-end web page, an employee information change confirmation page is provided for user managers to enable users to review personnel information changes.

[0007] Furthermore, in step S2, the personnel information template is used for various system-level pages. The roster, onboarding, quick onboarding and other pages of the personnel system have different requirements for the attribute configuration of the personnel information field and whether to present it. The above-mentioned personnel information template configuration function is used to realize customized processing for different pages.

[0008] Furthermore, in step S4, the attribute grouping and sorting is used to set the grouping and sorting order of the employee's personal personnel information page when querying it through the ESS employee self-service system.

[0009] Further, in step S4, the attribute whether ESS is displayed is used to set whether the employee can query the group and all its subordinate fields through the ESS employee self-service system.

[0010] Furthermore, in step S5, the field attribute change field is used to set whether the field is a changeable field.

[0011] Further, in step S4, the attribute whether the employee can modify is used to set whether the employee can add, edit and invalidate the personnel information under the group through the ESS employee self-service system.

[0012] Further, in step S5, whether the field attribute is ESS is displayed for setting whether the employee can query the value of the field through the ESS employee self-service system.

[0013] Further, in step S5, whether the field attribute is modifiable by employees is used to set whether the employee can modify the value of the field on the page in step S6. If modified, it will appear on the page in step S7 for approval by the administrator and will not take effect immediately.

[0014] Further, in step S6, the personnel information query page dynamically renders the web page according to the configuration of the group described in step S4 above, and the page renders different groups respectively in the mode of Tab tags. If in step S4 above, the group is configured with the value of employee modifiable as yes, and the value of whether ESS is displayed is yes, all subordinate fields of the group will be configured according to the field attribute configuration described in step S5 above, and all fields configured with the value of whether ESS is displayed as yes will be rendered into the newly added editing window of the group, presenting a two-column layout.

[0015] The rendering of the column is completed according to the following properties configured in step S5 above: The column name is the field name.

[0016] The column title is the label of the column that users see by default. The title multilingual key is used to configure the label to display in different languages ​​in a multilingual environment.

[0017] When the placeholder text configuration field is empty, the placeholder text content is displayed in the field component.

[0018] The data type is the data type of the configuration field in the database.

[0019] One row and one column configures the column rendering mode. If the value is yes, the column will not be rendered in the above two-column layout, but one column will occupy two columns for rendering. If the value is no, the above two-column layout will be used for rendering.

[0020] The column type configures the column rendering component type to be one of the following types: input box, drop-down box, attachment upload, Switch, etc. If the column type is a drop-down box, the data source and data source method configure the data source of the remote drop-down.

[0021] The initial value is the default value of the field before the user manually enters it.

[0022] The Required field configures whether the user must enter the value in this field. If the value is yes, the user cannot submit and save the data in the current newly added edit window before entering the field value.

[0023] Furthermore, in step S7, the page can record and display the modification record and review status of each field value, so that managers can track and manage changes in employee information. After approval, the ESS employee self-service system can query the changed value.

[0024] Through the above technical solution, the present invention realizes the flexible configuration and management of personnel information, greatly improving the efficiency and accuracy of enterprise human resource management. At the same time, through the approval process and change records, the security and traceability of information are ensured. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] In order to more clearly illustrate the implementation methods of the present invention or the technical solutions in the prior art, the following briefly introduces the drawings required for the implementation methods or the description of the prior art. Obviously, the drawings in the following description are only exemplary, and for ordinary technicians in this field, other implementation drawings can be derived from the provided drawings without creative work.

[0026] Figure 1 A schematic diagram of a method for constructing a personnel template page provided by an embodiment of the present invention;

[0027] Figure 2 A schematic diagram of a method for implementing a personnel information query page provided by an embodiment of the present invention;

[0028] Figure 3 A schematic diagram of a method for implementing an employee information change page provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0029] In order to further explain the technical means and effects adopted by the present invention to achieve the predetermined invention purpose, the following is a further detailed description of a configurable personnel information method proposed according to the present invention, its specific implementation method, structure, characteristics and effects in combination with specific embodiments. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of them. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work belong to the scope of protection of the present invention.

[0030] A best embodiment is given below:

[0031] like Figure 1 As shown, a method for constructing a personnel template page in this embodiment has the following steps:

[0032] Step 101: Build the main entry interface of the personnel template for enterprise user administrators based on the Vue framework.

[0033] Step 102: Build an editing page for the personnel template.

[0034] Step 103: Based on the personnel template editing page, a pop-up interface for the personnel template field grouping is constructed to configure the attributes of the fields in the group, as well as to enable, disable, add, and invalidate the fields.

[0035] Among them, in step 101, the implementation method of the main entrance of the personnel template is:

[0036] The front end uses Axios to call the back end interface through Query to obtain the personnel template list data. The data format returned by the interface is Array, in which each element generally contains the eight main fields of IsMaster, IsPublish, TemplateName, TemplateNo, RemarkSz, TemplateType, SortNo, and Id. According to TemplateType, the data is divided into two parts: standard template and custom template, and rendered in different blocks of the page respectively.

[0037] Usually, the system will have a built-in data as a standard template, and mark the data through the IsMaster field. Such data is prohibited from being invalidated by users through front-end and back-end management. In principle, the template list page does not allow users to directly add data, but to copy the existing template data based on the copy interface provided by the back-end, and further customize the configuration.

[0038] Dynamically render the web page according to the list data returned by the interface, build the component of the template list item, and pass each element of the list to the list item component through props. The component presents the template name (TemplateName), user remarks (RemarkSz), and whether the template is enabled (IsPublish). IsPublish is bound to the Switch component to allow the user to switch the template enablement status. In addition, the component provides edit, detail, copy, and cancel buttons: the edit button calls the Update interface to modify the template name and user remarks according to the Id; the copy button calls the Copy interface according to the Id to generate a new copy of the current data; the cancel button calls the Delete interface according to the Id to delete the current data; the detail button uses the current Id as a routing parameter and jumps to the edit page for the current template data described in step 102 through router.push({ name: 'routeName', query: { templateId: templateId}}).

[0039] The SortNo field determines the order of the template list. According to specific user needs, a sorting interface can be provided to adjust the value of the SortNo field to adjust the template data sorting.

[0040] In step 102, a route for a new template editing page is created, route parameters are obtained in the onBeforeMount hook, the template ID is obtained, and detailed data of the template is obtained through the interface.

[0041] The backend provides two layers of nested data. The first layer is a list of groups. Generally, there are many personnel fields. According to the specific needs of users, the fields need to be classified and managed. Each category corresponds to a group. Its basic attributes include: group ID, group name, group number, table name, primary key name, whether ESS display, whether employees can modify, field list, whether configurable, whether deletable, and whether sortable. Among them, the field list is the second-level nested structure, which contains the basic attributes of all enabled fields of the group. Its data structure is JSON Schema: { "StaffInfoColumnName": "Field Name", "StaffInfoColumnId": "Field ID", "IsSingleColumn": "Whether to display one row and one column", "DataType": "Data type", "ColumnType": "Component Type", "SortNo": "Sort", "Placeholder": "Placeholder text", }

[0042] According to the first layer of nested data, a grouped form component is constructed. According to the properties of the above group, the group name and configuration button are rendered on the title row of the form component. The field list is passed as props to the grouped form component. According to the SortNo and IsSingleColumn in the basic properties of the field, the field is rendered to each column in the form area of ​​the component. The column label corresponds to the StaffInfoColumnName of the above Json. The column component type is determined by ColumnType, and the column layout is determined by IsSingleColumn. If the Placeholder field is not empty, it is displayed as the placeholder text of the column.

[0043] This component implements the sorting capability of fields by referencing sortable.js. Users can perform manual sorting as needed, update the SortNo of all fields in the sortable callback, and return the data to the backend for update through the interface.

[0044] The grouped components are rendered in the page in sequence according to the group sorting. Since all subordinate fields are presented on the page, the page content is too long, so a concise group list needs to be implemented to provide editing, invalidation, control display or hiding, and sorting functions for each group. In addition, the list also provides a new button to enable users to create custom groups. Through the Ant design Modal component, a new and edit pop-up window is implemented, and the basic properties of the Group are presented in the form of a Form, allowing users to fill in and submit. At the same time, the group list provides a sorting function, which can modify the SortNo of all Groups.

[0045] In step 103, the pop-up page of the field group is the page entered by clicking the configuration button in the title row of the above-mentioned form component. All fields of the group are obtained through the interface request by the group ID. Unlike the field list of the second layer in the two-sided nested structure described in step 102, the fields in the field list in step 102 only include enabled fields, while the fields returned by the backend here include three states: enabled, selectable, and invalidated. Allow users to enable or disable fields according to their needs.

[0046] The front end constructs three lists in the main area of ​​the pop-up page, rendering lists of fields in three states respectively. And the sorting of fields is implemented through sortable.js, where the sorting of the list of enabled fields is synchronized with the sorting of fields in the form area of ​​the form component described in step 102 above. The status of the field can be updated through the interface, and the field can be switched in the three lists at any time according to user needs. The data structure of the field list inherits the data structure of the field list in step 102, and on this basis, the attribute DisplayType is added to mark the three states of the field, and the attribute Removable is added to mark whether the field can be deleted. Generally speaking, the basic fields built into the system do not allow users to delete them at will.

[0047] Build a form next to the main area of ​​the pop-up page. When the user clicks a field in the field list, the field ID is obtained in the onclick event, all the attributes of the field are obtained through the interface, and the attributes are assigned to the form. Allow users to edit the value of the form and submit. In addition, a Add button and a Delete button are provided below the form. Users can create custom fields as needed, and can delete fields whose field attribute Removable is true.

[0048] like Figure 2 As shown, the method for constructing a personnel information query page in this embodiment has the following steps:

[0049] Step 201: Build a basic grouping page through the Ant design Tab component, where each Tab corresponds to a field group of a personnel template.

[0050] Step 202: construct a table component in the area within the Tab, where the table header column corresponds to each field of the personnel field group.

[0051] Step 203: Based on the information configured by the user on the personnel template page, construct a new add and edit pop-up window, and provide a new add button at the bottom of the page.

[0052] In step 201, the configuration information of the personnel template page is read, and the groups whose ESS display value is True are obtained in all group attributes, and the list is returned to the page. The data structure of each element in the list is: { "cardType": "Grouping type", "StaffInfoGroupName": "Group name", "SortNo": 1, "CanDel": 0, "CanUpdate": 0, "CanInsert": 0, "ToDoCount": 3, } The value of SortNo is read from the group sorting configured on the personnel template page. The page configures the Tab sorting based on the value of SortNo. StaffInfoGroupName reads the group name from the grouping properties. CanDel (can be invalidated), CanUpldate (can be edited), and CanInsert (can be added) read whether the employee can be modified from the grouping properties. ToDoCount marks that the current employee has modified the items to be reviewed, and provides a pop-up box to render the list of changed items in the group, so that employees can view the data to be approved and compare it before and after the change.

[0053] In step 202, the table under the current Tab (group) is rendered, and the field with the attribute "Whether ESS display" value of true in the field in the current field group of the personnel template configuration is read as the header column of the table to render the entire table. If the values ​​of CanDel, CanUpldate, and CanInsert of this group obtained in step 201 are all 1, two frozen columns will be added to the first two columns of the table, providing the functions of editing and invalidating respectively, and a new button will be added at the bottom of the table to provide new functions.

[0054] It is worth noting that whether employees can modify the group configuration only controls whether the current table contains edit and cancel buttons and whether there is a new button at the bottom, and will not penetrate and affect the "whether employees can modify" attribute value of each field under the group.

[0055] In step 203, the field with the field attribute "whether employees can modify" value of true in the current field group of the personnel template configuration is read and rendered to the new edit pop-up window. When a user adds, edits or cancels a piece of data, it will not take effect in real time, and the change record will be synchronized to the employee information change page for the administrator to approve.

[0056] like Figure 3 As shown, this embodiment also provides a method for implementing the employee information change page, and the steps are as follows:

[0057] Step 301, construct a standard table query page with the following query conditions: employee, department, confirmation status, project category. The confirmation status is used to filter the change information of the three states of pending, approved, and rejected; the project category corresponds to the group in the personnel template configuration, and is used to filter the employee change information of different groups.

[0058] Step 302: If any changes are made to the employee information page, such as adding, editing, or canceling, the change records will be recorded in this page for the administrator to review and approve. At the same time, the change list in the employee information query page will also record the change records to be reviewed and approved.

[0059] Step 303, the first three columns of the table are frozen, and buttons for approval, rejection, and cancellation are provided respectively: If you agree, the user field information will be changed, and the change history will be retained on this page; If rejected, the user field information will not be changed, and the change history will be retained on this page; If it is invalidated, the user field information will not be changed and the change history record will not be retained.

[0060] The above are merely embodiments of the present invention and are not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present invention are included in the scope of the claims of the present invention to be approved.

Claims

1. A configurable personnel information management method, characterized in that: The method comprises the following steps: S1. In the Web front-end page, a main interface of personnel templates is provided to implement the configuration function of personnel information templates, including operations of adding, copying, editing, invalidating templates, and publishing and canceling templates; S2. Provide a template editing page, and dynamically render the template editing page according to the parameters provided by the list items in the template main interface; S3. In the template editing page, the administrator configures the properties of the group, configures the sorting of all groups, and configures the function name, table name, primary key name, whether ESS is displayed, and whether employees can modify each group; S4. Each group has an edit button for subordinates. After clicking it, the administrator enters the edit page of all subordinate personnel information fields of the group. In this page, select to add or remove fields, and configure the properties of each field, including: table name, field name, field title, multilingual title key, placeholder text, data type, one row and one column, field type, data source, data source method, initial value, whether it is required, whether it is valid, whether it is a change field, whether it can be modified by employees, whether it is displayed in ESS, whether multiple selections are allowed, and field description; S5. In the front-end web page, in the ESS employee self-service system, provide a personnel information query page, a list of changed items, a personnel information addition and modification window, and a cancellation window; S6. In the front-end web page, an employee information change confirmation page is provided for user managers to enable users to review personnel information changes.

2. The configurable personnel information management method according to claim 1, characterized in that: In step S3, the ESS, namely the ESS employee self-service system, provides a web page for presenting personnel information, and provides an operation portal for users to add, edit, and invalidate personal personnel information.

3. The configurable personnel information management method according to claim 1, characterized in that: In step S3, the attribute grouping and sorting is used to set the grouping and sorting order of the employee's personal personnel information page when querying it through the ESS employee self-service system.

4. The configurable personnel information management method according to claim 1, characterized in that: In step S3, whether the attribute is ESS display is used to set whether the employee can query the group through the ESS employee self-service system. This attribute only affects the visualization status of the group and will not penetrate and affect the attributes of the fields in the group.

5. The configurable personnel information management method according to claim 1, characterized in that: In step S3, whether the attribute is modifiable by employees is used to set whether employees can add, edit and invalidate personnel information under this group through the ESS employee self-service system.

6. The configurable personnel information management method according to claim 1, characterized in that: In step S4, whether the field attribute is ESS display is used to set whether the employee can query the value of the field through the ESS employee self-service system.

7. The configurable personnel information management method according to claim 1, characterized in that: In step S4, whether the field attribute is modifiable by employees is used to set whether employees can modify the value of the field on the ESS employee self-service system. If modified, it will appear on the employee information change confirmation page for approval by the administrator and will not take effect immediately.

8. The configurable personnel information method according to claims 1 and 7, characterized in that: In step S6, the employee information change confirmation page can record and display the modification record and review status of each field value, so that managers can track and manage changes to employee information. After approval, the ESS employee self-service system can query the changed value.

9. The configurable personnel information management method according to claim 1, characterized in that: In step S4, the field attribute change field is used to set whether the field is a changeable field.

Images