Early warning data acquisition method and related equipment

Abstract

The embodiment of the invention discloses an early warning data acquisition method and related equipment, which are used for improving the flexibility of early warning data acquisition. The method provided by the embodiment of the invention comprises the following steps: acquiring early warning configuration information based on an early warning scheme creation instruction, wherein the early warning configuration information comprises a plurality of service table identifiers corresponding to a plurality of early warning service tables, a data association relationship among the plurality of early warning service tables and an early warning condition; constructing an early warning scheme including the early warning configuration information; receiving an access instruction for the early warning scheme, and determining the plurality of early warning service tables according to the plurality of service table identifiers; and on the basis of the data association relationship, combining a plurality of pieces of service data which are screened from the plurality of early warning service tables and meet the early warning condition to obtain early warning data.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of business warning, and in particular to a warning data acquisition method and related equipment. Background Art

[0002] Human resource early warning plays an important and irreplaceable role in the overall operation of an enterprise. It is like a barometer in the field of human resource management. With its keen insight, it can warn enterprises of various risks and thorny problems hidden in human resources in advance. Through in-depth analysis and accurate prediction of human resource conditions, it provides a solid and valuable basis for the strategic decision-making of enterprises, helping enterprises seize opportunities in a complex and changing market environment and achieve sustainable development.

[0003] Since the design of human resources early warning schemes is relatively complicated, the existing ones are generally configured with fixed code logic for different early warning scenarios. Enterprises can choose from the early warning schemes pre-configured by developers in the human resources system according to the scenario requirements, and then configure the fixed code logic of the corresponding early warning scheme to run in the human resources system. Finally, the early warning data in the corresponding early warning scenario is obtained through the operation of the code.

[0004] In the above scheme, enterprises can only choose the required early warning scheme from a limited number of early warning schemes for different scenarios. Obviously, this early warning scheme built by fixed code logic can only be based on obtaining early warning data that conforms to the fixed code logic, and has poor flexibility. Summary of the invention

[0005] The embodiments of the present application provide a warning data acquisition method and related devices for improving the flexibility of warning data acquisition.

[0006] A first aspect of an embodiment of the present application provides a method for obtaining early warning data, comprising:

[0007] Acquire warning configuration information based on the warning plan creation instruction, the warning configuration information including a plurality of business table identifiers corresponding to a plurality of warning business tables, data association relationships between the plurality of warning business tables, and warning conditions;

[0008] Constructing an early warning plan including the early warning configuration information;

[0009] Receiving a data acquisition instruction for the early warning scheme;

[0010] Based on the data association relationship, a plurality of business data that meet the warning conditions and are screened from the plurality of warning business tables are merged to obtain warning data.

[0011] In a specific implementation, the method further includes:

[0012] In response to the operation of selecting the configuration confirmation control in the configuration page, generating the early warning plan creation instruction;

[0013] The step of obtaining warning configuration information based on the warning scheme creation instruction includes:

[0014] Each configuration information in the configuration page is determined as the warning configuration information based on the warning plan creation instruction.

[0015] In a specific implementation, before responding to the operation of selecting a configuration confirmation control in the configuration page, the method further includes:

[0016] In response to an operation in which any warning template is selected, each preset configuration information in the warning template is displayed on the configuration page, wherein the preset configuration information includes a plurality of preset table identifiers, preset association relationships, and the warning condition;

[0017] Receiving a configuration adjustment operation initiated based on each of the preset configuration information displayed in the configuration page, wherein the configuration adjustment operation includes adding configuration information, replacing configuration information, and deleting configuration information;

[0018] In response to the execution of the configuration adjustment operation, each of the configuration information in the configuration page after the configuration adjustment operation is executed is determined.

[0019] In a specific implementation, the warning configuration information further includes a warning field, the warning field is determined based on a business field in the corresponding warning business table, the warning condition is used to constrain the field value of the warning field, and based on the data association relationship, multiple business data that meet the warning condition and are screened from the multiple warning business tables are merged to obtain the warning data, including:

[0020] If the warning configuration information does not include the warning field corresponding to any of the warning service tables, determining the service table identifier corresponding to any of the warning service tables as an invalid table identifier;

[0021] Determine a plurality of valid early warning service tables corresponding to a plurality of valid table identifiers, wherein the valid table identifiers are service table identifiers other than the invalid table identifier among the plurality of service table identifiers;

[0022] Based on the data association relationship, a plurality of business data that meet the warning conditions and are screened from the plurality of valid warning business tables are merged to obtain warning data.

[0023] In a specific implementation, the plurality of warning service tables include a master table and at least one slave table, each of the warning service tables has a dependency relationship with other warning service tables different from the warning service table, and the method further includes:

[0024] If the service table identifier corresponding to the target warning service table is determined to be an invalid table identifier, determining a warning service table to be checked that has a dependency relationship with the target warning service table, wherein the target warning service table is any warning service table among the multiple warning service tables;

[0025] If, in the dependency relationship between any of the to-be-checked warning service tables and the target warning service table, the to-be-checked warning service table depends on the target warning service table, the service table identifier of the to-be-checked warning service table is determined as an invalid table identifier.

[0026] In a specific implementation, the plurality of early warning business tables include a master table and a plurality of slave tables, each of the early warning business tables has a dependency relationship with other early warning business tables different from the early warning business table, and based on the data association relationship, merging a plurality of business data that meet the early warning conditions screened from the plurality of early warning business tables to obtain early warning data includes:

[0027] Filtering a plurality of business data that meet the warning condition in target slave tables that have a dependency relationship with the master table respectively;

[0028] According to the data association relationship and dependency relationship between the master table and the target slave table, multiple business data obtained by screening from the master table and the target slave table are combined to obtain multiple intermediate data, and each of the intermediate data is recorded in a temporary table;

[0029] Determining each of the slave tables except the target slave table as a slave table to be checked in turn, and screening a plurality of business data that meet the warning condition in the slave tables to be checked;

[0030] If the temporary table contains the early warning business table on which the to-be-checked slave table depends, then based on the data association relationship and dependency relationship between the early warning business table on which the to-be-checked slave table depends and the to-be-checked slave table, the intermediate data in the temporary table is combined with a plurality of business data that meet the early warning condition in the to-be-checked slave table to obtain new intermediate data, and the new intermediate data is recorded in the temporary table;

[0031] If there is no unscreened warning business table, each of the new intermediate data in the temporary table is determined as the warning data.

[0032] A second aspect of the embodiment of the present application provides an early warning system, including:

[0033] An acquisition unit, configured to acquire warning configuration information based on the warning scheme creation instruction, wherein the warning configuration information includes a plurality of business table identifiers corresponding to a plurality of warning business tables, a data association relationship between the plurality of warning business tables, and a warning condition;

[0034] A construction unit, used to construct an early warning plan including the early warning configuration information;

[0035] A data acquisition unit, used for receiving a data acquisition instruction for the early warning scheme;

[0036] The data acquisition unit is further used to merge multiple business data that meet the warning conditions and are screened from the multiple warning business tables based on the data association relationship to obtain warning data.

[0037] In a specific implementation, the early warning system further includes: a generating unit;

[0038] The generating unit is used to generate the early warning plan creation instruction in response to the operation of selecting the configuration confirmation control in the configuration page;

[0039] The acquisition unit is specifically configured to determine each piece of configuration information in the configuration page as the warning configuration information based on the warning plan creation instruction.

[0040] In a specific implementation, before responding to the operation of selecting the configuration confirmation control in the configuration page, the early warning system further includes: a display unit, a receiving unit, and a determining unit;

[0041] The display unit is used to display each preset configuration information in the warning template in the configuration page in response to the operation of selecting any warning template, wherein the preset configuration information includes a plurality of preset table identifiers, preset association relationships and the warning condition;

[0042] The receiving unit is used to receive a configuration adjustment operation initiated based on each of the preset configuration information displayed in the configuration page, wherein the configuration adjustment operation includes adding configuration information, replacing configuration information, and deleting configuration information;

[0043] The determining unit is configured to determine, in response to the execution of the configuration adjustment operation, each of the configuration information in the configuration page after the configuration adjustment operation is executed.

[0044] In a specific implementation, the warning configuration information further includes a warning field, the warning field is determined based on the corresponding business field in the warning business table, the warning condition is used to constrain the field value of the warning field, and the data acquisition unit is specifically used to determine the business table identifier corresponding to any of the warning business tables as an invalid table identifier if the warning configuration information does not contain the warning field corresponding to any of the warning business tables;

[0045] Determine a plurality of valid early warning service tables corresponding to a plurality of valid table identifiers, wherein the valid table identifiers are service table identifiers other than the invalid table identifier among the plurality of service table identifiers;

[0046] Based on the data association relationship, a plurality of business data that meet the warning conditions and are screened from the plurality of valid warning business tables are merged to obtain warning data.

[0047] In a specific implementation, the plurality of warning service tables include a master table and at least one slave table, each of the warning service tables has a dependency relationship with other warning service tables different from the warning service table, and the warning system further includes: a determination unit;

[0048] The determining unit is configured to determine a to-be-checked warning service table that has a dependency relationship with the target warning service table if the service table identifier corresponding to the target warning service table is determined to be an invalid table identifier, wherein the target warning service table is any warning service table among the multiple warning service tables;

[0049] If, in the dependency relationship between any of the to-be-checked warning service tables and the target warning service table, the to-be-checked warning service table depends on the target warning service table, the service table identifier of the to-be-checked warning service table is determined as an invalid table identifier.

[0050] In a specific implementation, the plurality of warning business tables include a master table and a plurality of slave tables, each of the warning business tables has a dependency relationship with other warning business tables different from the warning business table, and the data acquisition unit is specifically used to filter a plurality of business data that meet the warning condition in the target slave tables that have a dependency relationship with the master table;

[0051] According to the data association relationship and dependency relationship between the master table and the target slave table, multiple business data obtained by screening from the master table and the target slave table are combined to obtain multiple intermediate data, and each of the intermediate data is recorded in a temporary table;

[0052] Determining each of the slave tables except the target slave table as a slave table to be checked in turn, and screening a plurality of business data that meet the warning condition in the slave tables to be checked;

[0053] If the temporary table contains the early warning business table on which the to-be-checked slave table depends, then based on the data association relationship and dependency relationship between the early warning business table on which the to-be-checked slave table depends and the to-be-checked slave table, the intermediate data in the temporary table is combined with a plurality of business data that meet the early warning condition in the to-be-checked slave table to obtain new intermediate data, and the new intermediate data is recorded in the temporary table;

[0054] If there is no unscreened warning business table, each of the new intermediate data in the temporary table is determined as the warning data.

[0055] A third aspect of an embodiment of the present application provides a computer device, including:

[0056] CPU, memory and input / output interface;

[0057] The memory is a short-term storage memory or a persistent storage memory;

[0058] The central processing unit is configured to communicate with the memory and execute instructions in the memory to perform the method described in the first aspect.

[0059] A fourth aspect of the embodiments of the present application provides a computer program product comprising instructions, and when the computer program product is run on a computer, the computer is caused to execute the method described in the first aspect.

[0060] A fifth aspect of an embodiment of the present application provides a computer storage medium, wherein the computer storage medium stores instructions, and when the instructions are executed on a computer, the computer executes the method described in the first aspect.

[0061] It can be seen from the above technical solutions that the embodiments of the present application have the following advantages: through the early warning scheme creation instruction, the multiple business table identifiers corresponding to the multiple early warning business tables required for building the early warning scheme, the data association relationship between the multiple early warning business tables, and the early warning conditions are directly obtained. In other words, the embodiment of the present application structures the complex early warning scheme into business table identifiers, data association relationships, and early warning conditions. In this way, to build a specific early warning scheme, it is only necessary to record the business table identifier, data association relationship, and early warning conditions in it. In addition, after receiving the data acquisition instruction for the constructed early warning scheme, no matter which early warning scenario the early warning scheme belongs to, the same processing method is adopted: that is, multiple early warning business tables are determined according to multiple business table identifiers, and based on the data association relationship, multiple business data that meet the early warning conditions are merged from multiple early warning business tables to obtain early warning data. Based on the above content, it can be seen that the early warning scheme construction method and early warning data acquisition method provided in the embodiment of the present application can flexibly adapt to the acquisition of early warning data in any scenario. BRIEF DESCRIPTION OF THE DRAWINGS

[0062] Figure 1 A schematic diagram of the early warning scheme model disclosed in the embodiment of the present application;

[0063] Figure 2 A schematic diagram of a process flow of a method for obtaining early warning data disclosed in an embodiment of the present application;

[0064] Figure 3 An example diagram of the configuration interface disclosed in the embodiment of the present application;

[0065] Figure 4 A schematic diagram of a process for confirming an invalid table identifier disclosed in an embodiment of the present application;

[0066] Figure 5 An architecture diagram of the early warning system disclosed in the embodiment of the present application;

[0067] Figure 6 A schematic diagram of the structure of the early warning system disclosed in the embodiment of the present application;

[0068] Figure 7 Another structural schematic diagram of the computer device disclosed in the embodiment of the present application. DETAILED DESCRIPTION

[0069] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0070] The embodiments of the present application provide a warning data acquisition method and related devices for improving the flexibility of warning data acquisition.

[0071] See also Figure 1 In order to better implement the early warning data acquisition method of the embodiment of the present application, the embodiment of the present application provides the following Figure 1The early warning scheme model shown in the figure structurally divides the early warning scheme into early warning business tables, data association relationships between early warning business tables, early warning fields belonging to a certain early warning business table, and early warning conditions. Among them, each required early warning business table has a corresponding early warning business identifier; each early warning business table needs to have a data association relationship with at least one early warning business table in the early warning scheme; based on the business fields in each early warning business table, the early warning fields belonging to the early warning business table can be determined; and the early warning conditions are used to constrain the values ​​of the early warning fields. It should be noted that since the configuration of the early warning conditions themselves needs to be associated with the corresponding early warning fields, under the model design of the embodiment of the present application, the early warning fields can be directly recorded in the early warning conditions.

[0072] In some specific implementations, the early warning solution model also includes a dependency relationship between two early warning business tables with a data association relationship. Among them, a dependency relationship includes a dependent early warning business table and a dependent early warning business table, such as Figure 1 As shown, in the connection line between two warning business tables, the warning business table pointed to by the arrow is the dependent warning business table of the two, and the dependent warning business table is the warning business table not pointed to by the arrow.

[0073] Based on the aforementioned warning scheme model design, the embodiments of the present application allow the use of a unified processing flow to achieve the acquisition of warning data based on different warning schemes, as detailed in the embodiments described below.

[0074] See also Figure 2 The present invention provides a method for obtaining early warning data, comprising the following steps:

[0075] 201. Acquire warning configuration information based on a warning plan creation instruction, where the warning configuration information includes a plurality of business table identifiers corresponding to a plurality of warning business tables, data association relationships between the plurality of warning business tables, and warning conditions.

[0076] It is understandable that in a real business scenario, before obtaining corresponding warning data based on a specific warning plan, it is necessary to first build a usable warning plan. Generally, after receiving the warning plan creation instruction, according to the instructions of the warning plan creation instruction, each warning configuration information required to be included in the warning plan that the warning plan creation instruction expects to build can be obtained.

[0077] In combination with the above embodiments, a complete early warning solution needs to include at least the configuration item information included in any of the above early warning model solutions. Among them, in the scenario where a complex early warning solution needs to be constructed in the embodiment of the present application, data from multiple business tables is usually required, that is, the early warning configuration information includes multiple business table identifiers corresponding to multiple early warning business tables.

[0078] In addition, the data association relationship between the aforementioned multiple warning business tables does not mean that any two warning business tables need to configure corresponding data association relationships, such as Figure 3 As shown in the content, as long as there is a data association relationship between each early warning business table and at least one early warning business table corresponding to any business table identifier in the early warning plan.

[0079] 202. Construct an early warning plan including early warning configuration information.

[0080] According to the aforementioned early warning scheme model design, the embodiment of the present application splits the early warning scheme into a structured early warning scheme model. In other words, the early warning scheme of the embodiment of the present application is composed of various structured early warning configuration information indicated by the early warning scheme model. Then, in the embodiment of the present application, each early warning configuration information obtained based on the early warning scheme creation instruction in step 201 can be associated and stored as an early warning scheme.

[0081] In this way, when receiving the data acquisition instruction for the aforementioned early warning scheme, each item of early warning configuration information associated and stored in the early warning scheme can be taken out as the basis for data acquisition.

[0082] 203. Receive data acquisition instructions for the early warning plan.

[0083] Generally, if a data acquisition instruction for an early warning scheme is received, each item of early warning configuration information associated with the early warning scheme can be retrieved, and early warning data can be obtained under the instructions of each item of early warning configuration information. Generally, the early warning configuration information retrieved from the early warning scheme includes each item of early warning configuration information obtained when the early warning configuration information is acquired based on the early warning scheme creation instruction. Among them, the data acquisition instruction for any early warning scheme can be directly triggered by the user, or triggered by a scheduled task, which can be configured on demand according to the required update frequency and business scenario.

[0084] It is understandable that if a corresponding warning scheme identifier is configured when the warning scheme is constructed in step 202, then in the embodiment of the present application, a data acquisition instruction including the corresponding warning scheme identifier can be generated to indicate the completion of the data acquisition instruction based on the aforementioned warning scheme.

[0085] 204. Based on the data association relationship, multiple business data that meet the warning conditions and are screened from multiple warning business tables are merged to obtain warning data.

[0086] Specifically, the premise of obtaining the warning data is to determine multiple warning business tables according to multiple business table identifiers, and to search the warning business tables for multiple business data that the warning scheme expects to filter out. It should be noted that the screening of multiple business data may be achieved through various existing data acquisition tools, which is not limited in the embodiments of this application.

[0087] In complex early warning scheme configuration scenarios, the construction of an early warning data is based on business data from different early warning business tables, and different business data in the same early warning data actually point to the same early warning object. For example, in the birthday early warning in human resources early warning, an early warning data may contain the name and work number from the enterprise human table, the department and birthday date from the personnel business archive table, and each early warning data specifically points to a person in the enterprise (i.e., the early warning object). However, the name and work number in the enterprise human table that meet the requirements (such as early warning conditions) constitute a business data, and similarly, the department and birthday date in the personnel business archive table that meet the requirements (such as early warning conditions) constitute a business data. Therefore, it is necessary to merge the name and work number, department and birthday date of the same employee (or associated with the same early warning object) into one early warning data. Among them, the data association relationship between the enterprise human table and the personnel business archive table will be used in the merging process. That is, the data association relationship refers to the association fields that can be associated in the two early warning business tables, as well as the constraints that the field values ​​of the association fields in the business data from the two early warning business tables need to meet (i.e., association conditions). The association fields are confirmed based on the business fields in each early warning business table. The association relationships required for the same early warning business table in different data association relationships may be the same, not completely the same, or completely different, and are not limited here.

[0088] In addition, it should be noted that since step 203 needs to obtain business data from multiple different early warning business tables, and this step needs to obtain tables from different early warning business tables that meet the corresponding data association relationship, this step 204 and step 203 can be executed alternately. For example, after executing the business data screening operation of the second early warning business table, each time all the business data or one piece of business data of an early warning business table is obtained, it can be merged with the business data in other early warning business tables obtained previously, and after the merger, the acquisition of all the business data of the next early warning business table or the acquisition of the next piece of business data is executed, which is not limited here.

[0089] In actual applications, different companies have different design requirements for early warning solutions even for the same early warning scenario. The early warning solutions and early warning data acquisition processes built with fixed code logic in the existing technology cannot meet the user's customized needs for early warning solutions and have great limitations.

[0090] The embodiment of the present application structures the complex early warning scheme into business table identifiers, data associations, and early warning conditions. In this way, to construct a specific early warning scheme, it is only necessary to record the business table identifiers, data associations, and early warning conditions. In addition, after receiving the data acquisition instruction for the constructed early warning scheme, no matter which early warning scenario the early warning scheme belongs to, the same processing method is adopted: that is, multiple early warning business tables are determined according to multiple business table identifiers, and multiple business data are merged based on data associations to obtain early warning data. Based on the above content, it can be seen that the early warning scheme construction method and early warning data acquisition method provided in the embodiment of the present application are not limited to fixed code logic, and can flexibly adapt to the acquisition of early warning data in any scenario.

[0091] On the basis of the aforementioned embodiment, before the aforementioned step 201, the embodiment of the present application also includes: in response to the operation of selecting the configuration confirmation control in the configuration page, generating an early warning plan creation instruction; and the aforementioned step 201 can be specifically implemented in the following manner: based on the early warning plan creation instruction, each configuration information in the configuration page is determined as early warning configuration information.

[0092] In order to reduce the cost of building the early warning plan, the user can be allowed to configure the early warning plan through a visual configuration page. In this case, each configuration information required for the current early warning plan is included in the configuration page. In this way, when the configuration confirmation control of the configuration page is selected, it means that the object that selects the configuration confirmation control believes that each configuration information included in the configuration page is sufficient to build a required early warning plan, so it generates a corresponding early warning plan creation instruction, and based on the early warning plan creation instruction, each configuration information in the configuration page is determined as early warning configuration information. The specific implementation of the configuration page can be referred to Figure 3 .

[0093] Furthermore, before the step of "responding to the operation of selecting a configuration confirmation control in the configuration page", an embodiment of the present application also includes: in response to the operation of selecting any early warning template, displaying each preset configuration information in the early warning template in the configuration page, the preset configuration information including multiple preset table identifiers, preset association relationships and early warning conditions; receiving a configuration adjustment operation initiated based on each preset configuration information displayed in the configuration page, the configuration adjustment operation including adding configuration information, replacing configuration information and deleting configuration information; in response to the execution of the configuration adjustment operation, determining each configuration information in the configuration page after the configuration adjustment operation is executed.

[0094] That is to say, in this embodiment, each preset configuration information in the configuration page does not need to start from "zero", but on the basis of the pre-configured warning template, it is configured and adjusted, and finally an early warning scheme that meets personalized needs is obtained. Based on the foregoing content, it can be understood that the early warning template can be understood as a complete early warning scheme example. That is to say, after selecting the early warning template, you can directly select the configuration confirmation control, which is equivalent to directly constructing the early warning template as an early warning scheme. Alternatively, initiate configuration adjustment operations such as adding configuration information, replacing configuration information, and deleting configuration information to complete personalized customization. Among them, adding configuration information refers to adding different types of configuration information such as early warning conditions, business tables, and data associations on the basis of the early warning template. The newly added business table comes from each business table that can be obtained by the early warning system that deploys the method of this application; replacing configuration information refers to replacing the configuration information in the configuration page with configuration information of the corresponding type but with different values, such as replacing business table 1 with business table 2. The replaced business table can be from each business table that can be obtained by the early warning system that deploys the method of this application, and the replaced early warning conditions and data associations can be configured as needed; deleting configuration information refers to deleting any configuration information in the configuration page. In addition, the configuration adjustment operation may be a batch adjustment operation initiated simultaneously for multiple configuration information, which is not limited here.

[0095] It can be seen that after each configuration adjustment operation is performed, all configuration information contained in the configuration page is not completely the same as before the configuration adjustment operation is performed. Therefore, after each configuration adjustment operation is performed, the configuration information contained in the configuration page will be synchronously updated.

[0096] For details, please refer to the specific implementation of selecting the warning template on the configuration page. Figure 3 In the left list, after selecting an alert template in the left list, the alert plan in the corresponding alert template will be displayed. Figure 3 In the middle association configuration module. In the association configuration module, users can use visual, drag-and-drop interaction to complete the addition of cross-database and cross-application business tables, as well as the data association and dependency configuration between warning business tables. The dependency on the middle connection line between the two warning business tables supports multiple configuration methods, such as left connection (the right side depends on the left side), right connection (the left side depends on the right side), and inner connection (the left and right tables depend on each other).

[0097] In addition, users can also Figure 3 In the warning field selection module on the right, select a business field under a warning business table as a warning field, or add a calculated field as a warning field. There is no limitation here. The field value of the calculated field can be obtained by logical expression operation based on the field values ​​of multiple business fields in the warning business table.

[0098] The foregoing describes various embodiments of constructing an early warning scheme. The following describes various embodiments of obtaining early warning data based on the early warning scheme.

[0099] In a specific implementation, the warning configuration information also includes a warning field, which is determined based on the business field in the corresponding warning business table, and the warning condition is used to constrain the field value of the warning field. Then, the aforementioned step 204 can be specifically implemented with reference to the following steps: if the warning configuration information does not contain a warning field corresponding to any warning business table, then the business table identifier corresponding to any warning business table is determined as an invalid table identifier; multiple valid warning business tables corresponding to multiple valid table identifiers are determined, and the valid table identifier is the business table identifier among the multiple business table identifiers except the invalid table identifier; based on the data association relationship, multiple business data that meet the warning conditions screened from multiple valid warning business tables are merged to obtain warning data.

[0100] Specifically, the warning condition is used to constrain the field value of the warning field. The warning field is determined based on the business field in the corresponding warning business table. In combination with the above-mentioned embodiments, it can be known that filtering business data from each warning business table needs to rely on the corresponding warning field and the warning condition that constrains the warning field. Therefore, if the warning business table indicated by any business table identifier in the warning scheme does not have any warning field, it means that the final synthesized warning data will not contain any business data in the warning business table, and the business table identifier corresponding to this invalid business table is the invalid table identifier. Subsequently, in the process of filtering business data, there is no need to obtain any data from the invalid business table for processing. It is only necessary to filter multiple business data that meet the warning conditions from multiple valid warning business tables corresponding to multiple valid table identifiers, so as to reduce the data acquisition cost and improve the data acquisition efficiency.

[0101] like Figure 4 From the content shown in the upper part, it can be seen that the warning fields include personnel, organizations, units, relationships and positions. The constraints corresponding to each warning field are all field values. Different warning business tables establish data association relationships through the employee ID field. Based on the four warning business tables of personnel business files, occupational information, positions, and ranks and grades, as well as each warning field, it can be seen that there is no business table of ranks and grades that does not contain any warning fields, which means that the final synthesized warning data will not contain any business data in the business table of ranks and grades, so it needs to be classified as an invalid business table. Furthermore, if Figure 4The three early warning business tables of personnel business files, occupational information and positions shown in the lower part are all valid business tables. According to the above constraints, the embodiment of the present application only needs to traverse the data in the three early warning business tables. When facing a large amount of data in actual application scenarios, the embodiment of the present application excludes the query and traversal operations on invalid business tables, which greatly reduces the complexity of querying data and improves data acquisition performance.

[0102] In addition, in some specific implementations, the multiple warning business tables in the embodiments of the present application include a main table and at least one subordinate table, and each warning business table has a dependency relationship with other warning business tables that are different from the warning business table. Among them, each warning record must have business data in the main table, and if any warning record has business data in a certain warning business table, and the warning business table depends on other warning business tables different from itself, it means that the business data in the aforementioned other warning business tables must exist in the warning record. In other words, if in the dependency relationship between any warning business table to be checked and the target warning business table, the warning business table to be checked depends on the target warning business table, then the business table identifier of the warning business table to be checked is determined to be an invalid table identifier.

[0103] Furthermore, in addition to configuring the calculation fields, the embodiment of the present application can also optimize the data acquisition process. Specifically, the multiple warning business tables include a main table and multiple slave tables, and each warning business table has a dependency relationship with other warning business tables different from the warning business table. The aforementioned step 204 can be specifically implemented in the following manner: in the target slave table between which there is a dependency relationship between the main table and the main table, multiple business data that meet the warning conditions are screened; according to the data association relationship and dependency relationship between the main table and the target slave table, the multiple business data screened from the main table and the target slave table are combined to obtain multiple intermediate data, and each intermediate data is The intermediate data is recorded in a temporary table; each slave table except the target slave table is determined as the slave table to be checked in turn, and multiple business data that meet the warning conditions are screened in the slave table to be checked; if the temporary table contains the warning business table on which the slave table to be checked depends, then based on the data association relationship and dependency relationship between the warning business table on which the slave table to be checked depends and the slave table to be checked, the intermediate data in the temporary table and the multiple business data that meet the warning conditions are screened in the slave table to be checked to obtain new intermediate data, and the new intermediate data is recorded in the temporary table; if there is no unscreened warning business table, each new intermediate data in the temporary table is determined as warning data.

[0104] Specifically, the multiple early warning service tables include a master table and multiple slave tables. At the same time, there is a data association relationship between the multiple early warning service tables in the embodiment of the present application, so that the data association relationship between the multiple early warning service tables can be formed as follows: Figure 3The multi-layer business table shown in the association configuration module, where the main table is at the first layer. Considering that the main table is the starting point for users to configure the warning plan, the field value of the warning field contained in the main table should be the necessary information in the warning data, that is, each warning data must contain the field value of the warning field in the main table.

[0105] Importantly, the embodiment of the present application introduces a dependency relationship between multiple warning business tables, and this dependency determines the importance of the warning fields in different warning business tables. For example, table A depends on table B, table A contains warning fields A1, A2 and A3, and table B contains warning fields B1 and B2. In any of the warning data that is finally determined, if there is no field value for B1 or B2, there must be no field value for A1, A2 and A3. Figure 4 Taking the content shown as an example, if Figure 4 The occupation information table in the table depends on the personnel business file table, and the position table depends on the occupation information table. This means that a warning data with a field value under the unit field must have a field value under the organization field, and a warning data with a field value under the unit field must have a field value under the unit field; but the reverse is not necessarily true. Figure 4 As shown in the warning data corresponding to Zhao Liu and Sun Qi respectively, the warning data includes the field values ​​under the unit field and the field values ​​under the organization field, but does not include the field values ​​under the position field.

[0106] With the help of the above-mentioned properties of the dependency relationship, the embodiment of the present application introduces attention to the dependency relationship during the execution of step 204. First, according to the corresponding warning fields and warning conditions, multiple business data are respectively screened out in the main table and the target slave table (that is, any slave table that depends on the main table), and then. Based on the data association relationship between the two, a combination of corresponding business data is constructed to obtain multiple intermediate data. At the same time, for the business data that has not been combined in the multiple business data that have been screened out previously, it is necessary to specifically decide whether to retain it as intermediate data based on the dependency relationship between the main table and the target slave table, and finally store all the obtained intermediate data in a temporary table. Then, refer to Figure 3In the multi-layer architecture shown, each slave table that has a data association relationship with the main table of the first layer, that is, each slave table in the second layer, is first found, and each slave table is determined as a slave table to be checked in turn. Taking the first warning business table determined as the slave table to be checked as an example, multiple business data are screened in the slave table to be checked according to the corresponding warning field and warning conditions, and according to the dependency relationship between this data to be checked and the warning business table with a dependency relationship in the temporary table, the multiple business data screened in the slave table to be checked are combined into the temporary table to form new intermediate data. Among them, the warning business table with a dependency relationship with the temporary table is the main table whose corresponding business data has been combined into the temporary table. Finally, after processing the slave tables of the second layer, the slave tables of the third layer are processed one by one according to the above method until each slave table is processed and there is no unscreened warning business table. At this time, each intermediate record in the temporary table is a warning record.

[0107] It should be noted that in addition to determining each slave table as a slave table to be checked layer by layer, if an early warning business table that has a data association or dependency relationship with any slave table also exists in the temporary table, then any of the aforementioned slave tables can also be determined as a slave table to be checked, and this is not limited here.

[0108] In the data query process of the embodiment of the present application, the dependency relationship between any two early warning business tables is fully utilized. In addition, in the query process, the data required in the new early warning business table is merged into the temporary table in sequence from the main table to the slave table according to the dependency relationship, and the query results are reused by updating the data in the temporary table. There is no need to traverse different data tables multiple times, and in the face of large data query scenarios, the overall data acquisition efficiency can be effectively improved.

[0109] See also Figure 5 Based on the above embodiments, in the application scenario of human resource control system (HRCS), the early warning data acquisition method provided by the embodiment of the present application can be deployed in Figure 5 In the HRCS application shown in . Among them, the initiation of the early warning plan creation instruction can be executed regularly through various scheduling configuration methods such as cron expressions configured by the scheduling center or manually executed by the user through a computer device, and there is no restriction here. After receiving the early warning plan creation instruction, the early warning plan is configured based on the early warning template, and the relevant logical expression execution and data acquisition engine modules are called to respectively obtain the field value of the early warning field; the calls between different modules and the sending of early warning data to specific human resources users are respectively realized through plug-in execution and message service modules.

[0110] In addition, the early warning data acquisition part can deploy the data acquisition engine locally to implement local calls, or deploy it in an external data acquisition engine cluster to implement cluster calls. In addition, the acquisition or storage of early warning data can be achieved through persistence technologies such as ORM and / or streaming data processing technologies such as KSQL. Finally, early warning data can be obtained from different businesses in the human resources business database and stored in different businesses in the human resources business database.

[0111] See also Figure 6 , the embodiment of the present application provides an early warning system, including:

[0112] The acquisition unit 601 is used to acquire the warning configuration information based on the warning plan creation instruction, where the warning configuration information includes multiple business table identifiers corresponding to multiple warning business tables, data association relationships between the multiple warning business tables, and warning conditions;

[0113] A construction unit 602 is used to construct an early warning plan including early warning configuration information;

[0114] The data acquisition unit 603 is used to receive the data acquisition instruction for the early warning scheme, and determine multiple early warning business tables according to multiple business table identifiers;

[0115] The data acquisition unit 603 is also used to merge multiple business data that meet the warning conditions screened from multiple warning business tables based on data association relationships to obtain warning data.

[0116] In a specific implementation, the early warning system further includes: a generation unit;

[0117] A generating unit, configured to generate an early warning plan creation instruction in response to an operation in which a configuration confirmation control is selected in the configuration page;

[0118] The acquisition unit 601 is specifically configured to determine each configuration information in the configuration page as the warning configuration information based on the warning plan creation instruction.

[0119] In a specific implementation, before responding to the operation of selecting the configuration confirmation control in the configuration page, the early warning system further includes: a display unit, a receiving unit, and a determining unit;

[0120] A display unit, configured to display each preset configuration information in the warning template in a configuration page in response to an operation of selecting any warning template, wherein the preset configuration information includes a plurality of preset table identifiers, preset association relationships, and warning conditions;

[0121] A receiving unit, configured to receive a configuration adjustment operation initiated based on each preset configuration information displayed in the configuration page, wherein the configuration adjustment operation includes adding configuration information, replacing configuration information, and deleting configuration information;

[0122] The determining unit is used to determine, in response to the execution of the configuration adjustment operation, each configuration information in the configuration page after the configuration adjustment operation is executed.

[0123] In a specific implementation, the warning configuration information further includes a warning field, the warning field is determined based on a business field in a corresponding warning business table, the warning condition is used to constrain the field value of the warning field, and the data acquisition unit 603 is specifically used to determine the business table identifier corresponding to any warning business table as an invalid table identifier if the warning configuration information does not include the warning field corresponding to any warning business table;

[0124] Determine a plurality of valid early warning business tables corresponding to a plurality of valid table identifiers, wherein the valid table identifiers are business table identifiers other than the invalid table identifiers among the plurality of business table identifiers;

[0125] Based on the data association relationship, multiple business data that meet the warning conditions screened from multiple effective warning business tables are merged to obtain warning data.

[0126] In a specific implementation, the plurality of warning service tables include a master table and at least one slave table, each slave table is dependent on at least one warning service table, and the warning system further includes: a determination unit;

[0127] a determination unit, configured to determine, if the service table identifier corresponding to the target warning service table is determined to be an invalid table identifier, a to-be-checked warning service table that has a dependency relationship with the target warning service table, wherein the target warning service table is any warning service table among the multiple warning service tables;

[0128] If, in the dependency relationship between any warning business table to be checked and the target warning business table, the warning business table to be checked depends on the target warning business table, the business table identifier of the warning business table to be checked is determined as an invalid table identifier.

[0129] In a specific implementation, the plurality of warning business tables include a main table and a plurality of subordinate tables, each warning business table has a dependency relationship with other warning business tables different from the warning business table, and the data acquisition unit 603 is specifically used to filter a plurality of business data that meet the warning condition in the target subordinate tables that have a dependency relationship with the main table;

[0130] According to the data association and dependency relationship between the master table and the target slave table, multiple business data filtered from the master table and the target slave table are combined to obtain multiple intermediate data, and each intermediate data is recorded in a temporary table;

[0131] Each slave table except the target slave table is determined as a slave table to be checked in turn, and multiple business data that meet the warning conditions are screened in the slave table to be checked;

[0132] If the temporary table contains the warning business table that the to-be-checked slave table depends on, then based on the data association and dependency relationship between the warning business table that the to-be-checked slave table depends on and the to-be-checked slave table, the intermediate data in the temporary table is combined with multiple business data that meet the warning conditions in the to-be-checked slave table to obtain new intermediate data, and the new intermediate data is recorded in the temporary table;

[0133] If there is no unfiltered warning business table, each new intermediate data in the temporary table is determined as warning data.

[0134] Figure 7 It is a schematic diagram of a computer device structure provided in an embodiment of the present application. The computer device 700 may include one or more central processing units (CPU) 701 and a memory 705. The memory 705 stores one or more application programs or data.

[0135] The memory 705 may be a volatile storage or a persistent storage. The program stored in the memory 705 may include one or more modules, each of which may include a series of instruction operations in the computer device. Furthermore, the central processing unit 701 may be configured to communicate with the memory 705 and execute a series of instruction operations in the memory 705 on the computer device 700.

[0136] The computer device 700 may also include one or more power supplies 702, one or more wired or wireless network interfaces 703, one or more input and output interfaces 704, and / or one or more operating systems, such as Windows Server™, Mac OS X™, Unix™, Linux™, FreeBSD™, etc.

[0137] The CPU 701 can execute the aforementioned Figures 1 to 6 The operations performed by the early warning system in the illustrated embodiment will not be described in detail here.

[0138] It should be noted that, although the steps in the flowcharts involved in the embodiments are drawn in sequence according to the indications of the arrows, unless otherwise clearly stated in this document, there is no strict order restriction on the execution of these steps, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the embodiments may include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily sequential, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.

[0139] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0140] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, which can be electrical, mechanical or other forms.

[0141] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0142] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0143] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, read-only memory), random access memory (RAM, random access memory), disk or optical disk and other media that can store program code.

[0144] An embodiment of the present application also provides a computer program product including instructions. When the computer program product is run on a computer, the computer executes the above-mentioned early warning data acquisition method.

Claims

1. A method for obtaining early warning data, characterized in that: include: Acquire warning configuration information based on the warning plan creation instruction, the warning configuration information including a plurality of business table identifiers corresponding to a plurality of warning business tables, data association relationships between the plurality of warning business tables, and warning conditions; Constructing an early warning plan including the early warning configuration information; Receiving a data acquisition instruction for the early warning scheme; Based on the data association relationship, a plurality of business data that meet the warning conditions and are screened from the plurality of warning business tables are merged to obtain warning data.

2. The method for obtaining early warning data according to claim 1, characterized in that: The method further comprises: In response to the operation of selecting the configuration confirmation control in the configuration page, generating the early warning plan creation instruction; The step of obtaining warning configuration information based on the warning scheme creation instruction includes: Each configuration information in the configuration page is determined as the warning configuration information based on the warning plan creation instruction.

3. The method for obtaining early warning data according to claim 2, characterized in that: Before responding to the operation of selecting the configuration confirmation control in the configuration page, the method further includes: In response to an operation in which any early warning template is selected, each preset configuration information in the early warning template is displayed on the configuration page, wherein the preset configuration information includes a plurality of preset table identifiers, preset association relationships, and the early warning condition; Receiving a configuration adjustment operation initiated based on each of the preset configuration information displayed in the configuration page, wherein the configuration adjustment operation includes adding configuration information, replacing configuration information, and deleting configuration information; In response to the execution of the configuration adjustment operation, each of the configuration information in the configuration page after the configuration adjustment operation is executed is determined.

4. The method for obtaining early warning data according to claim 1, characterized in that: The warning configuration information also includes a warning field, the warning field is determined based on the corresponding business field in the warning business table, the warning condition is used to constrain the field value of the warning field, and based on the data association relationship, a plurality of business data that meet the warning condition and are screened from the plurality of warning business tables are merged to obtain the warning data, including: If the warning configuration information does not include the warning field corresponding to any of the warning service tables, determining the service table identifier corresponding to any of the warning service tables as an invalid table identifier; Determine a plurality of valid early warning service tables corresponding to a plurality of valid table identifiers, wherein the valid table identifiers are service table identifiers other than the invalid table identifier among the plurality of service table identifiers; Based on the data association relationship, a plurality of business data that meet the warning conditions and are screened from the plurality of valid warning business tables are merged to obtain warning data.

5. The method for obtaining early warning data according to claim 4, characterized in that: The plurality of early warning service tables include a master table and at least one slave table, each of the early warning service tables has a dependency relationship with other early warning service tables different from the early warning service table, and the method further includes: If the service table identifier corresponding to the target warning service table is determined to be an invalid table identifier, determining a warning service table to be checked that has a dependency relationship with the target warning service table, wherein the target warning service table is any warning service table among the multiple warning service tables; If, in the dependency relationship between any of the to-be-checked warning service tables and the target warning service table, the to-be-checked warning service table depends on the target warning service table, the service table identifier of the to-be-checked warning service table is determined as an invalid table identifier.

6. The method for obtaining early warning data according to claim 4 or 5, characterized in that: The multiple early warning business tables include a main table and multiple subordinate tables, each of the early warning business tables has a dependency relationship with other early warning business tables different from the early warning business table, and based on the data association relationship, multiple business data that meet the early warning conditions screened from the multiple early warning business tables are merged to obtain early warning data, including: Filtering a plurality of business data that meet the warning condition in target slave tables that have a dependency relationship with the master table respectively; According to the data association relationship and dependency relationship between the master table and the target slave table, multiple business data obtained by screening from the master table and the target slave table are combined to obtain multiple intermediate data, and each of the intermediate data is recorded in a temporary table; Determining each of the slave tables except the target slave table as a slave table to be checked in turn, and screening a plurality of business data that meet the warning condition in the slave tables to be checked; If the temporary table contains the early warning business table on which the to-be-checked slave table depends, then based on the data association relationship and dependency relationship between the early warning business table on which the to-be-checked slave table depends and the to-be-checked slave table, the intermediate data in the temporary table is combined with a plurality of business data that meet the early warning condition in the to-be-checked slave table to obtain new intermediate data, and the new intermediate data is recorded in the temporary table; If there is no unscreened warning business table, each of the new intermediate data in the temporary table is determined as the warning data.

7. A computer device, characterized in that: include: An acquisition unit, configured to acquire warning configuration information based on the warning scheme creation instruction, wherein the warning configuration information includes a plurality of business table identifiers corresponding to a plurality of warning business tables, a data association relationship between the plurality of warning business tables, and a warning condition; A construction unit, used to construct an early warning plan including the early warning configuration information; A data acquisition unit, used for receiving a data acquisition instruction for the early warning scheme; The merging unit is used to merge the multiple business data that meet the warning conditions screened from the multiple warning business tables based on the data association relationship to obtain warning data.

8. A computer device, characterized in that: include: CPU, memory and input / output interface; The memory is a transient storage memory or a persistent storage memory; The central processing unit is configured to communicate with the memory and execute instructions in the memory to perform the method according to any one of claims 1 to 6.

9. A computer program product comprising instructions, characterized in that When the computer program product is run on a computer, the computer is caused to execute the method according to any one of claims 1 to 6.

10. A computer storage medium, characterized in that: The computer storage medium stores instructions, and when the instructions are executed on a computer, the computer is caused to execute the method according to any one of claims 1 to 6.

Images