Early warning data acquisition method and related device

Abstract

Embodiments of the present application disclose a method for obtaining early warning data and related equipment, which are used to improve the flexibility of obtaining early warning data. The method comprises the following steps: obtaining early warning configuration information based on an early warning scheme creation instruction, wherein the early warning configuration information comprises a plurality of business table identifiers corresponding to a plurality of early warning business tables, a data association relationship between the plurality of early warning business tables, and an early warning condition; constructing an early warning scheme comprising the early warning configuration information; receiving a data extraction instruction for the early warning scheme, determining the plurality of early warning business tables according to the plurality of business table identifiers; and based on the data association relationship, merging a plurality of pieces of business data that meet the early warning condition and are filtered from the plurality of early warning business tables to obtain early warning data.

Description

Technical Field

[0001] This application relates to the field of business early warning, and in particular to methods for acquiring early warning data and related equipment. Background Technology

[0002] Human resource early warning plays a crucial and irreplaceable role in the overall operation of an enterprise. It acts as a barometer in the field of human resource management, providing early warnings of various potential risks and challenges related to human resources through keen insight. In-depth analysis and accurate forecasting of human resource conditions provide solid and valuable evidence for strategic decision-making, helping enterprises seize opportunities in a complex and ever-changing market environment and achieve sustainable development.

[0003] Because the design of human resource early warning schemes is quite complex, existing methods typically configure the required early warning schemes for different scenarios using fixed code logic. Enterprises can now select from the early warning schemes pre-configured in the human resource system by developers, based on their specific needs. This allows them to configure the fixed code logic for the corresponding early warning scheme and run it within the human resource system. Finally, the early warning data for the corresponding scenario is obtained through the execution of the code.

[0004] In the above approach, enterprises can only choose the required alert scheme from a limited set of alert options for different scenarios. Clearly, this alert scheme, built with fixed code logic, can only obtain alert data that conforms to that fixed logic, resulting in poor flexibility. Summary of the Invention

[0005] This application provides a method and related equipment for acquiring early warning data, which improves the flexibility of acquiring early warning data.

[0006] The first aspect of this application provides a method for acquiring early warning data, including:

[0007] The warning configuration information is obtained based on the warning scheme creation instruction. The warning configuration information includes multiple business table identifiers corresponding to multiple warning business tables, the data association relationship between the multiple warning business tables, and the warning conditions.

[0008] Construct an early warning scheme that includes the aforementioned early warning configuration information;

[0009] Receive data retrieval instructions for the aforementioned early warning scheme;

[0010] Based on the data association, multiple business data entries that meet the warning conditions and are selected from the multiple warning business tables are merged to obtain warning data.

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

[0012] In response to the selection of the configuration confirmation control on the configuration page, the warning scheme creation instruction is generated;

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

[0014] The warning scheme creation instruction determines each configuration information in the configuration page as the warning configuration information.

[0015] In one specific implementation, before responding to the selection of a configuration confirmation control on the configuration page, the method further includes:

[0016] In response to the selection of any warning template, the configuration page displays each preset configuration information of the warning template, including multiple preset table identifiers, preset associations, and the warning conditions;

[0017] Receive configuration adjustment operations initiated based on each of the preset configuration information displayed on the configuration page, the configuration adjustment operations including adding configuration information, replacing configuration information, and deleting configuration information;

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

[0019] In one specific implementation, the early warning configuration information further includes an early warning field, which is determined based on a business field in the corresponding early warning business table. The early warning condition is used to constrain the field value of the early warning field. The step of merging multiple business data entries that meet the early warning conditions and are filtered from the multiple early warning business tables based on the data association relationship to obtain early warning data includes:

[0020] If the warning configuration information does not contain any warning field corresponding to any of the warning business tables, then the business table identifier corresponding to any of the warning business tables will be determined as an invalid table identifier.

[0021] Multiple valid table identifiers are identified as corresponding to multiple valid early warning business tables, wherein the valid table identifiers are business table identifiers other than the invalid table identifiers among the multiple business table identifiers;

[0022] Based on the data association, multiple business data entries that meet the warning conditions and are selected from the multiple valid warning business tables are merged to obtain warning data.

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

[0024] If the business table identifier corresponding to the target early warning business table is determined to be an invalid table identifier, then an early warning business table to be queried that has a dependency relationship with the target early warning business table is determined. The target early warning business table is any one of the multiple early warning business tables.

[0025] If, in any of the dependencies between the pending early warning business table and the target early warning business table, the pending early warning business table depends on the target early warning business table, then the business table identifier of the pending early warning business table is determined to be an invalid table identifier.

[0026] In one specific implementation, the multiple early warning business tables include one master table and multiple slave tables. Each of the early warning business tables has a dependency relationship with other early warning business tables different from the master table. The step of merging multiple business data entries that meet the early warning conditions, selected from the multiple early warning business tables, based on the data association relationships to obtain early warning data includes:

[0027] In the target sub-tables that have dependencies on the main table, filter out multiple business data that meet the warning conditions;

[0028] Based on the data relationships and dependencies between the main table and the target sub-table, multiple pieces of intermediate data are obtained by combining multiple pieces of business data filtered from the main table and the target sub-table, and each piece of intermediate data is recorded in a temporary table;

[0029] Each of the sub-tables other than the target sub-table is identified as a sub-table to be queried in turn, and multiple business data that meet the warning conditions are filtered from the sub-tables to be queried;

[0030] If the temporary table contains an early warning business table that the query sub-table depends on, then based on the early warning business table that the query sub-table depends on and the data association and dependency relationship between the query sub-table and the query sub-table, the intermediate data in the temporary table is combined with multiple business data that meet the early warning conditions in the query sub-table to obtain new intermediate data, and the new intermediate data is recorded in the temporary table.

[0031] If there is no unfiltered early warning business table, then each new intermediate data in the temporary table will be identified as the early warning data.

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

[0033] The acquisition unit is used to acquire early warning configuration information based on the early warning scheme creation instruction. The early warning configuration information includes multiple business table identifiers corresponding to multiple early warning business tables, the data association relationship between the multiple early warning business tables, and early warning conditions.

[0034] The construction unit is used to construct an early warning scheme including the early warning configuration information;

[0035] The data retrieval unit is used to receive data retrieval instructions for the early warning scheme;

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

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

[0038] The generation unit is used to generate the warning scheme creation instruction in response to the operation of selecting the configuration confirmation control on the configuration page;

[0039] The acquisition unit is specifically used to determine each configuration information in the configuration page as the early warning configuration information based on the early warning scheme creation instruction.

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

[0041] The display unit is configured to, in response to the selection of any warning template, display each preset configuration information of the warning template on the configuration page. The preset configuration information includes multiple preset table identifiers, preset association relationships, and the warning conditions.

[0042] The receiving unit is configured to receive configuration adjustment operations initiated based on each preset configuration information displayed on the configuration page, the configuration adjustment operations including adding configuration information, replacing configuration information, and deleting configuration information;

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

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

[0045] Multiple valid table identifiers are identified as corresponding to multiple valid early warning business tables, wherein the valid table identifiers are business table identifiers other than the invalid table identifiers among the multiple business table identifiers;

[0046] Based on the data association, multiple business data entries that meet the warning conditions and are selected from the multiple valid warning business tables are merged to obtain warning data.

[0047] In one specific implementation, the multiple 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 that are different from the master table. The early warning system also includes: a determination unit.

[0048] The determining unit is configured to determine, if the business table identifier corresponding to the target early warning business table is determined to be an invalid table identifier, an early warning business table to be queried that has a dependency relationship with the target early warning business table, wherein the target early warning business table is any one of the multiple early warning business tables;

[0049] If, in any of the dependencies between the pending early warning business table and the target early warning business table, the pending early warning business table depends on the target early warning business table, then the business table identifier of the pending early warning business table is determined to be an invalid table identifier.

[0050] In one specific implementation, 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 that are different from the early warning business table. The data retrieval unit is specifically used to filter multiple business data that meet the early warning conditions from the target subordinate tables that have a dependency relationship with the main table.

[0051] Based on the data relationships and dependencies between the main table and the target sub-table, multiple pieces of intermediate data are obtained by combining multiple pieces of business data filtered from the main table and the target sub-table, and each piece of intermediate data is recorded in a temporary table;

[0052] Each of the sub-tables other than the target sub-table is identified as a sub-table to be queried in turn, and multiple business data that meet the warning conditions are filtered from the sub-tables to be queried;

[0053] If the temporary table contains an early warning business table that the query sub-table depends on, then based on the early warning business table that the query sub-table depends on and the data association and dependency relationship between the query sub-table and the query sub-table, the intermediate data in the temporary table is combined with multiple business data that meet the early warning conditions in the query sub-table to obtain new intermediate data, and the new intermediate data is recorded in the temporary table.

[0054] If there is no unfiltered early warning business table, then each new intermediate data entry in the temporary table will be identified as the early warning data.

[0055] A third aspect of this application provides a computer device, including:

[0056] Central processing unit, memory, and input / output interfaces;

[0057] The memory is either 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 this application provides a computer program product containing instructions that, when run on a computer, cause the computer to perform the method described in the first aspect.

[0060] A fifth aspect of this application provides a computer storage medium storing instructions that, when executed on a computer, cause the computer to perform the method described in the first aspect.

[0061] As can be seen from the above technical solutions, the embodiments of this application have the following advantages: By using the early warning scheme creation instruction, the multiple business table identifiers corresponding to the multiple early warning business tables required for constructing the early warning scheme, the data association relationships between the multiple early warning business tables, and the early warning conditions can be directly obtained. In other words, the embodiments of this application structure the complex early warning scheme into business table identifiers, data association relationships, and early warning conditions. Thus, constructing a specific early warning scheme only requires recording the business table identifiers, data association relationships, and early warning conditions. Furthermore, upon receiving the data retrieval instruction for the constructed early warning scheme, regardless of the early warning scenario, the same processing method is adopted: that is, multiple early warning business tables are determined based on the multiple business table identifiers, and based on the data association relationships, multiple business data entries that meet the early warning conditions selected from the multiple early warning business tables are merged to obtain the early warning data. Based on the above, it can be seen that the early warning scheme construction method and early warning data acquisition method provided by the embodiments of this application can flexibly adapt to early warning data acquisition in any scenario. Attached Figure Description

[0062] Figure 1 A schematic diagram of the early warning scheme model design disclosed in the embodiments of this application;

[0063] Figure 2 This is a schematic flowchart of a method for acquiring early warning data disclosed in an embodiment of this application;

[0064] Figure 3 This is an example diagram of the configuration interface disclosed in an embodiment of this application;

[0065] Figure 4 This is a schematic diagram of a process for confirming invalid table identifiers as disclosed in an embodiment of this application;

[0066] Figure 5 This is an architecture diagram of the early warning system disclosed in an embodiment of this application;

[0067] Figure 6 This is a schematic diagram of the early warning system disclosed in an embodiment of this application;

[0068] Figure 7 This is another schematic diagram of the computer device disclosed in the embodiments of this application. Detailed Implementation

[0069] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0070] This application provides a method and related equipment for acquiring early warning data, which improves the flexibility of acquiring early warning data.

[0071] Please see Figure 1 To better implement the early warning data acquisition method of this application embodiment, this application embodiment provides the following: Figure 1The illustrated early warning scheme model structurally breaks down the early warning scheme into early warning business tables, data relationships between these tables, early warning fields belonging to a specific early warning business table, and early warning conditions. Each required early warning business table has a corresponding early warning business identifier; each early warning business table needs to have a data 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 that 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 early warning conditions itself needs to be associated with the corresponding early warning fields, in the model design of this embodiment, the early warning fields can be directly recorded in the early warning conditions.

[0072] In some specific implementations, the early warning scheme model also includes a dependency relationship between two early warning business tables that have a data association. 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 line connecting the two early warning business tables, the early warning business table pointed to by the arrow is the one that is depended on, while the dependent early warning business table is the one that is not pointed to by the arrow.

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

[0074] Please see Figure 2 This application provides a method for acquiring early warning data, including the following steps:

[0075] 201. Obtain early warning configuration information based on the early warning scheme creation command. The early warning configuration information includes multiple business table identifiers corresponding to multiple early warning business tables, data association relationships between multiple early warning business tables, and early warning conditions.

[0076] Understandably, in real-world business scenarios, before obtaining relevant early warning data based on a specific early warning scheme, a usable early warning scheme must first be constructed. Generally, upon receiving an early warning scheme creation instruction, the system can obtain each early warning configuration information required to construct the early warning scheme according to the instructions.

[0077] In conjunction with the foregoing embodiments, a complete early warning scheme must at least include configuration item information as included in any of the aforementioned early warning model schemes. In the scenario where a complex early warning scheme needs to be constructed in this application embodiment, data from multiple business tables is typically required; that is, the early warning configuration information includes multiple business table identifiers corresponding to each of the multiple early warning business tables.

[0078] Furthermore, the data association relationships between the aforementioned multiple early warning business tables do not mean that any two early warning business tables need to have corresponding data association relationships configured. Figure 3 As shown in the content, it is sufficient that each early warning business table has a data association relationship with at least one early warning business table corresponding to any business table identifier in the early warning scheme.

[0079] 202. Construct an early warning scheme that includes early warning configuration information.

[0080] As can be seen from the aforementioned early warning scheme model design, this application embodiment breaks down the early warning scheme into a structured early warning scheme model. Conversely, the early warning scheme of this application embodiment needs to be composed of various structured early warning configuration information indicated by the early warning scheme model. Therefore, in this application embodiment, each piece of early warning configuration information obtained in step 201 based on the early warning scheme creation instruction can be associated and stored as an early warning scheme.

[0081] In this way, when a data retrieval instruction is received for the aforementioned early warning scheme, each early warning configuration information associated with the early warning scheme can be retrieved as the basis for data retrieval.

[0082] 203. Receive data retrieval instructions for the early warning scheme.

[0083] Generally, upon receiving a data retrieval command for an alert scheme, each associated alert configuration information can be retrieved from the alert scheme's storage, and alert data can be obtained according to the instructions of each alert configuration information. Typically, retrieving alert configuration information from an alert scheme includes retrieving each alert configuration information obtained when the alert scheme creation command is used. The data retrieval command for any alert scheme can be triggered directly by the user or by a scheduled task, and can be configured as needed based on the required update frequency and business scenario.

[0084] It is understood that if a corresponding early warning scheme identifier is configured when constructing the early warning scheme in step 202, then in this embodiment of the application, a data retrieval instruction including the corresponding early warning scheme identifier can be generated to instruct the completion of the data retrieval instruction based on the aforementioned early warning scheme.

[0085] 204. Merge multiple business data entries that meet the early warning conditions from multiple early warning business tables based on data association relationships to obtain early warning data.

[0086] Specifically, obtaining early warning data requires identifying multiple early warning business tables based on multiple business table identifiers, and then searching through these tables for multiple pieces of business data that the early warning scheme aims to filter. It should be noted that the filtering of multiple pieces of business data can be achieved using various existing data retrieval tools, and this application's embodiments do not limit this approach.

[0087] In complex early warning configuration scenarios, a single early warning data entry is built upon business data from different early warning business tables, and the different business data within the same early warning entry essentially point to the same early warning object. For example, in human resources early warnings, a birthday early warning entry might contain the name and employee ID from the enterprise personnel table, and the department and date of birth from the personnel business file table. Each early warning entry specifically points to a particular person within the company (i.e., the early warning object). However, the name and employee ID from the enterprise personnel table that meet the requirements (such as early warning conditions) constitute one business data entry, and similarly, the department and date of birth from the personnel business file table that meet the requirements (such as early warning conditions) constitute another business data entry. Therefore, it is necessary to merge the name, employee ID, department, and date of birth of the same employee (or the one associated with the same early warning object) into a single early warning data entry. This merging process utilizes the data relationships between the enterprise personnel table and the personnel business file table. In other words, data association refers to the associated fields that can be established between two early warning business tables, as well as the constraints (i.e., association conditions) that the field values ​​of the associated fields in the business data established from the two early warning business tables need to satisfy. The associated fields are determined based on the business fields in each early warning business table. The association required for the same early warning business table in different data associations may be the same, not exactly the same, or completely different, which is not limited here.

[0088] Additionally, it should be noted that since step 203 requires obtaining business data from multiple different early warning business tables, and this step requires matching the corresponding data relationships between tables from different early warning business tables, steps 204 and 203 can be executed alternately. For example, after executing the business data filtering operation for the second early warning business table, after obtaining all the business data or one piece of business data from each early warning business table, it can be merged with the business data from other previously obtained early warning business tables. After merging, the process of obtaining all the business data or the next piece of business data from the next early warning business table can be executed. This is not limited here.

[0089] In practical applications, different enterprises have different design requirements for early warning solutions even for the same early warning scenario. Existing early warning solutions and early warning data acquisition processes built with fixed code logic cannot meet users' customization needs for early warning solutions, and have significant limitations.

[0090] This application's embodiments structure complex early warning schemes into business table identifiers, data relationships, and early warning conditions. Thus, constructing a specific early warning scheme only requires recording the business table identifiers, data relationships, and early warning conditions. Furthermore, upon receiving a data retrieval instruction for the constructed early warning scheme, regardless of the early warning scenario, the same processing method is employed: multiple early warning business tables are determined based on multiple business table identifiers, and multiple business data entries are merged based on data relationships to obtain the early warning data. Based on the above, it can be seen that the early warning scheme construction method and early warning data acquisition method provided in this application's embodiments are not limited to fixed code logic and can flexibly adapt to early warning data acquisition in any scenario.

[0091] Based on the foregoing embodiments, prior to step 201, this application embodiment further includes: generating an early warning scheme creation instruction in response to the selection of the configuration confirmation control in the configuration page; and step 201 can be specifically implemented in the following manner: determining each configuration information in the configuration page as early warning configuration information based on the early warning scheme creation instruction.

[0092] To reduce the cost of building alert schemes, users can configure them through a visual configuration page. In this case, every configuration piece of information required for the current alert scheme is included in the configuration page. When the configuration confirmation control on the configuration page is selected, it indicates that the user believes that each configuration piece of information included in the configuration page is sufficient to build a required alert scheme. Therefore, a corresponding alert scheme creation instruction is generated, and each configuration piece of information in the configuration page is determined as the alert configuration information based on this instruction. The specific implementation of the configuration page can be found in [reference needed]. Figure 3 .

[0093] Furthermore, prior to the step of "responding to the operation of selecting the configuration confirmation control in the configuration page", this embodiment of the application further includes: in response to the operation of selecting any warning template, displaying each preset configuration information in the warning template in the configuration page, the preset configuration information including multiple preset table identifiers, preset association relationships and 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] In other words, in this embodiment, each preset configuration information on the configuration page does not need to start from "zero". Instead, it is based on a pre-configured warning template, and configuration adjustments are made to obtain a warning scheme that meets personalized needs. Based on the foregoing, the warning template can be understood as a complete example of a warning scheme. That is, after selecting a warning template, one can directly select the configuration confirmation control, which is equivalent to directly building the warning template as a warning scheme. Alternatively, configuration adjustment operations such as adding, replacing, and deleting configuration information can be initiated to complete personalized customization. Among them, adding configuration information refers to adding different types of configuration information such as warning conditions, business tables, and data association relationships based on the warning template. The added business tables come from each business table that can be obtained by the warning system that deploys the method of this application. Replacing configuration information refers to replacing the configuration information on the configuration page with configuration information of the corresponding type but with different values. For example, replacing business table 1 with business table 2. The replaced business table can be each business table that can be obtained by the warning system that deploys the method of this application. The replaced warning conditions and data association relationships can be configured as needed. Deleting configuration information refers to deleting any configuration information on the configuration page. In addition, configuration adjustment operations can be batch adjustments initiated simultaneously for multiple configuration information, and there are no restrictions here.

[0095] Therefore, after each configuration adjustment operation is performed, all the configuration information contained in the configuration page is not exactly the same as before the configuration adjustment operation was performed. Thus, after each configuration adjustment operation is performed, the configuration information contained in the configuration page will be updated synchronously.

[0096] For details on how to select an alert template on the configuration page, please refer to [link / reference]. Figure 3 In the left-hand list, after selecting an alert template, the corresponding alert plan will be displayed. Figure 3 In the middle relationship configuration module, users can use a visual, drag-and-drop interactive method to add business tables across databases and applications, as well as configure data relationships and dependencies between alert business tables. The dependency relationship between two alert business tables supports multiple configuration methods, such as left join (the right depends on the left), right join (the left depends on the right), and inner join (the left and right tables depend on each other).

[0097] In addition, users can also... Figure 3 In the alert field selection module on the right, you can select a business field from a specific alert business table as an alert field, or add a calculated field as an alert field; there are no restrictions here. The value of the calculated field can be obtained by performing logical expression operations on the values ​​of multiple business fields in the alert business table.

[0098] The preceding text described various embodiments of constructing an early warning scheme. The following text describes various embodiments of acquiring early warning data based on the early warning scheme.

[0099] In one specific implementation, the early warning configuration information also includes an early warning field. The early warning field is determined based on the business field in the corresponding early warning business table, and the early warning condition is used to constrain the field value of the early warning field. Then, the aforementioned step 204 can be implemented by referring to the following steps: If the early warning configuration information does not contain an early warning field corresponding to any early warning business table, then the business table identifier corresponding to any early warning business table is determined as an invalid table identifier; determine multiple valid early warning business tables corresponding to multiple valid table identifiers, where the valid table identifier is the business table identifier other than the invalid table identifier among the multiple business table identifiers; based on the data association relationship, merge multiple business data that meet the early warning conditions selected from multiple valid early warning business tables to obtain early warning data.

[0100] Specifically, the warning conditions are used to constrain the field values ​​of the warning fields. These warning fields are determined based on the business fields in the corresponding warning business tables. As illustrated in the aforementioned embodiments, filtering business data from each warning business table depends on the corresponding warning field and the warning conditions that constrain it. Therefore, if any warning business table indicated by a business table identifier in the warning scheme does not contain any warning fields, it means that the final synthesized warning data will not contain any business data from that warning business table. In this case, the business table identifier corresponding to this invalid business table is the invalid table identifier. Subsequently, during the filtering of business data, it is not necessary to obtain any data from the invalid business tables for processing. Instead, multiple pieces of business data that meet the warning conditions need to be filtered from multiple valid warning business tables corresponding to multiple valid table identifiers, thereby reducing data retrieval costs and improving data retrieval efficiency.

[0101] like Figure 4 As shown in the upper part, the warning fields include personnel, organization, unit, relationship, and position. The constraint condition for each warning field is all field values. Different warning business tables are linked through the employee ID field. Based on the four warning business tables—personnel business files, occupational information, position, and job grade—and each warning field, it is known that the job grade business table does not contain any warning fields. This means that the final synthesized warning data will not contain any business data from the job grade business table, and therefore it needs to be classified as an invalid business table. Furthermore, as... Figure 4The lower half of the content shows three warning business tables: personnel business files, occupational information, and job positions. All of these are valid business tables. According to the above constraints, this embodiment only needs to traverse the data in these three warning business tables. In practical applications dealing with large amounts of data, this embodiment eliminates the need to query and traverse invalid business tables, significantly reducing the complexity of data queries and improving data retrieval performance.

[0102] Furthermore, in some specific implementations, the multiple early warning business tables in this application embodiment include one master table and at least one slave table. Each early warning business table has a dependency relationship with other early warning business tables different from itself. Specifically, each early warning record must contain business data in the master table. If any early warning record contains business data in a certain early warning business table, and that early warning business table depends on other early warning business tables different from itself, then the early warning record necessarily contains business data from the aforementioned other early warning business tables. In other words, if in the dependency relationship between any early warning business table to be queried and the target early warning business table, the early warning business table to be queried depends on the target early warning business table, then the business table identifier of the early warning business table to be queried is determined to be an invalid table identifier.

[0103] Furthermore, in addition to configuring calculated fields, this application embodiment can also optimize the data retrieval process. Specifically, multiple early warning business tables include one main table and multiple subordinate tables. Each early warning business table has a dependency relationship with other early warning business tables different from the main table. The aforementioned step 204 can be implemented as follows: In the target subordinate tables that have a dependency relationship with the main table, multiple business data that meet the early warning conditions are filtered; Based on the data association and dependency relationship between the main table and the target subordinate tables, multiple business data filtered from the main table and the target subordinate tables are combined to obtain multiple intermediate data, and each intermediate data is then processed. Intermediate data is recorded in a temporary table; each sub-table other than the target sub-table is identified as the sub-table to be queried in turn, and multiple business data that meet the early warning conditions are filtered from the sub-table to be queried; if the temporary table contains an early warning business table that the sub-table to be queried depends on, then based on the early warning business table that the sub-table to be queried depends on and the data association and dependency relationship between the two, the intermediate data in the temporary table is combined with the multiple business data that meet the early warning conditions filtered from the sub-table to be queried to obtain new intermediate data, and the new intermediate data is recorded in the temporary table; if there is no early warning business table that has not been filtered, then each new intermediate data in the temporary table is identified as early warning data.

[0104] Specifically, the multiple early warning business tables include one master table and multiple slave tables. Furthermore, there are data relationships between these multiple early warning business tables in this embodiment. This allows for the formation of data relationships based on these relationships, such as... Figure 3The relationship configuration module shows a multi-level business table, with the main table at the first level. Considering that the main table is the starting point for users to configure alert schemes, the field values ​​of the alert fields contained in the main table should be necessary information in the alert data; that is, each alert record must contain the field values ​​of the alert fields in the main table.

[0105] Importantly, this application's embodiments introduce dependencies between multiple early warning business tables. These dependencies determine the importance of early warning fields in different early warning business tables. For example, table A depends on table B, where table A contains early warning fields A1, A2, and A3, and table B contains early warning fields B1 and B2. Therefore, in any final determined early warning data, if field values ​​for B1 or B2 are absent, then field values ​​for A1, A2, and A3 will definitely not exist. Figure 4 For example, if the content shown is shown, Figure 4 If the occupational information table depends on the personnel business file table, and the job position table depends on the occupational information table, then a warning data entry with a value under the "unit" field must also have a value under the "organization" field; however, the reverse is not necessarily true. For example... Figure 4 The warning data corresponding to Zhao Liu and Sun Qi are shown below. This warning data includes field values ​​under the unit field and field values ​​under the organization field, but does not include field values ​​under the position field.

[0106] Leveraging the aforementioned properties of dependencies, this embodiment introduces attention to dependencies during the execution of step 204. First, based on the corresponding warning fields and conditions, multiple business data entries are selected from both the main table and the target sub-table (i.e., any sub-table dependent on the main table). Then, based on the data relationship between the two, the corresponding business data is combined to obtain multiple intermediate data entries. Simultaneously, for the business data entries that were not combined in the previous selection, it is necessary to determine whether to retain them as intermediate data based on the dependency relationship between the main table and the target sub-table. Finally, all obtained intermediate data is stored in a temporary table. Then, referring to... Figure 3The multi-layered architecture shown first identifies each subordinate table in the second layer that has a data relationship with the master table in the first layer, and then identifies them in turn as subordinate tables to be queried. Taking the first subordinate table identified as the early warning business table as an example, multiple business data records are filtered from the subordinate table based on the corresponding early warning fields and conditions. Furthermore, based on the dependency relationship between this data and the early warning business tables in the temporary table, the multiple business data records filtered from the subordinate table are combined into the temporary table to form new intermediate data. Here, the early warning business tables that have a dependency relationship with the temporary table are the master tables whose corresponding business data has already been combined into the temporary table. Finally, after processing the second-layer subordinate tables, the third-layer subordinate tables are processed one by one in the same way, until each layer of subordinate tables has been processed and there are no more unfiltered early warning business tables. At this point, each intermediate record in the temporary table is an early warning record.

[0107] It should be noted that, in addition to identifying each sub-table as the sub-table to be queried layer by layer, if an early warning business table that has a data relationship or dependency relationship with any sub-table also exists in the temporary table, then any of the aforementioned sub-tables can also be identified as the sub-table to be queried, without any limitation here.

[0108] In the data query process of this application embodiment, the dependency relationship between any two early warning business tables is fully utilized. Furthermore, during the query process, the data required by the new early warning business table is merged into a temporary table sequentially from the main table to the subordinate table according to the dependency relationship. The query results are reused by updating the data in the temporary table. This eliminates the need to traverse different data tables multiple times, effectively improving the overall data retrieval efficiency in scenarios involving large amounts of data.

[0109] Please see Figure 5 Based on the foregoing embodiments, in the application scenario of a human resource control system (HRCS), the early warning data acquisition method provided in this application embodiment can be deployed in, for example, Figure 5 The HRCS application shown here. The early warning scheme creation command can be initiated through various scheduling configurations configured by the scheduling center, such as cron expressions, or manually executed by the user via computer devices; no restrictions are placed here. Upon receiving the early warning scheme creation command, the early warning scheme is configured based on the early warning template, and related logical expression execution and data retrieval engine modules are invoked to obtain the field values ​​of the early warning fields. Plugin execution and message service modules are used to implement inter-module calls and send early warning data to specific HR users.

[0110] Furthermore, the early warning data acquisition component can deploy the data retrieval engine locally for local calls, or deploy it in an external data retrieval engine cluster for cluster calls. Moreover, 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 retrieved from different business units within the human resources business database and stored within those different business units.

[0111] Please see Figure 6 This application provides an early warning system, including:

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

[0113] Construction unit 602 is used to construct an early warning scheme including early warning configuration information;

[0114] The data retrieval unit 603 is used to receive data retrieval instructions for the early warning scheme and to determine multiple early warning business tables based on multiple business table identifiers;

[0115] The data retrieval unit 603 is also used to merge multiple business data that meet the early warning conditions and are selected from multiple early warning business tables based on data association relationships to obtain early warning data.

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

[0117] The generation unit is used to generate an early warning scheme creation instruction in response to the selection of the configuration confirmation control on the configuration page;

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

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

[0120] The display unit is used to respond to the operation of selecting any warning template and display each preset configuration information in the warning template on the configuration page. The preset configuration information includes multiple preset table identifiers, preset association relationships and warning conditions.

[0121] The receiving unit is used to receive configuration adjustment operations initiated based on each preset configuration information displayed on the configuration page. The configuration adjustment operations include adding configuration information, replacing configuration information, and deleting configuration information.

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

[0123] In one specific implementation, the early warning configuration information also includes an early warning field. The early warning field is determined based on the business field in the corresponding early warning business table. The early warning condition is used to constrain the field value of the early warning field. The data retrieval unit 603 is specifically used to determine the business table identifier corresponding to any early warning business table as an invalid table identifier if the early warning configuration information does not contain an early warning field corresponding to any early warning business table.

[0124] Determine the multiple valid early warning business tables corresponding to the multiple valid table identifiers. The valid table identifier is the business table identifier other than the invalid table identifier among the multiple business table identifiers.

[0125] Based on data relationships, multiple business data entries that meet the early warning conditions are merged from multiple valid early warning business tables to obtain early warning data.

[0126] In one specific implementation, multiple early warning business tables include a master table and at least one slave table, each slave table depends on at least one early warning business table, and the early warning system also includes: a determination unit;

[0127] The determination unit is used to determine the early warning business table to be queried that has a dependency relationship with the target early warning business table if the business table identifier corresponding to the target early warning business table is determined to be an invalid table identifier. The target early warning business table is any one of the multiple early warning business tables.

[0128] If, in any dependency relationship between a pending early warning business table and a target early warning business table, the pending early warning business table depends on the target early warning business table, then the business table identifier of the pending early warning business table will be determined as an invalid table identifier.

[0129] In one specific implementation, multiple early warning business tables include one main table and multiple subordinate tables. Each early warning business table has a dependency relationship with other early warning business tables that are different from the main table. The data retrieval unit 603 is specifically used to filter multiple business data that meet the early warning conditions from the target subordinate tables that have a dependency relationship with the main table.

[0130] Based on the data relationships and dependencies between the main table and the target sub-table, multiple pieces of intermediate data are obtained by combining multiple pieces of business data filtered from the main table and the target sub-table, and each piece of intermediate data is recorded in a temporary table;

[0131] Each sub-table other than the target sub-table is identified as the sub-table to be queried in turn, and multiple business data that meet the warning conditions are selected from the sub-table to be queried;

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

[0133] If there is no unfiltered early warning business table, then each new intermediate data in the temporary table will be identified as early warning data.

[0134] Figure 7 This is a schematic diagram of a computer device structure provided in an embodiment of this application. The computer device 700 may include one or more central processing units (CPUs) 701 and a memory 705, in which one or more application programs or data are stored.

[0135] The memory 705 can be volatile or persistent storage. The program stored in the memory 705 can include one or more modules, each module including a series of instruction operations on the computer device. Furthermore, the central processing unit 701 can be configured to communicate with the memory 705 and execute the series of instruction operations stored 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 / output interfaces 704, and / or one or more operating systems, such as Windows Server™, Mac OS X™, Unix™, Linux™, FreeBSD™, etc.

[0137] The central processing unit 701 can perform the aforementioned... Figures 1 to 6 The specific 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 of the various embodiments are drawn sequentially according to the arrows, unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the various embodiments may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages in other steps.

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

[0140] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection between apparatuses or units through some interfaces, and may be electrical, mechanical, or other forms.

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

[0142] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0143] If the integrated unit is implemented as 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 this application, in essence, 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. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0144] This application also provides a computer program product containing instructions, which, when run on a computer, causes the computer to execute the aforementioned early warning data acquisition method.

Claims

1. A method for acquiring early warning data, characterized in that, include: The warning configuration information is obtained based on the warning scheme creation instruction. The warning configuration information includes multiple business table identifiers corresponding to multiple warning business tables, the data association relationship between the multiple warning business tables, and the warning conditions. Construct an early warning scheme that includes the aforementioned early warning configuration information; Receive data retrieval instructions for the aforementioned early warning scheme; Based on the data association, multiple business data entries that meet the warning conditions and are selected from the multiple warning business tables are merged to obtain warning data; The multiple early warning business tables include one master table and multiple slave tables. Each of the early warning business tables has a dependency relationship with other early warning business tables different from the master table. Based on the data relationship, multiple business data that meet the early warning conditions and are selected from the multiple early warning business tables are merged to obtain early warning data, including: In the target sub-tables that have dependencies on the main table, filter out multiple business data that meet the warning conditions; Based on the data relationships and dependencies between the main table and the target sub-table, multiple pieces of intermediate data are obtained by combining multiple pieces of business data filtered from the main table and the target sub-table, and each piece of intermediate data is recorded in a temporary table; Each of the sub-tables other than the target sub-table is selected as the sub-table to be queried in turn, and multiple business data that meet the warning conditions are filtered in the sub-table to be queried to obtain the warning data.

2. The method for acquiring early warning data according to claim 1, characterized in that, The method further includes: In response to the selection of the configuration confirmation control on the configuration page, the warning scheme creation instruction is generated; The method of obtaining early warning configuration information based on the early warning scheme creation instruction includes: The warning scheme creation instruction determines each configuration information in the configuration page as the warning configuration information.

3. The method for acquiring early warning data according to claim 2, characterized in that, Before responding to the selection of a configuration confirmation control on the configuration page, the method further includes: In response to the selection of any warning template, the configuration page displays each preset configuration information of the warning template, including multiple preset table identifiers, preset associations, and the warning conditions; Receive configuration adjustment operations initiated based on each of the preset configuration information displayed on the configuration page, the configuration adjustment operations including adding configuration information, replacing configuration information, and deleting configuration information; In response to the execution of the configuration adjustment operation, each configuration information in the configuration page is determined after the configuration adjustment operation is executed.

4. The method for acquiring early warning data according to claim 1, characterized in that, The early warning configuration information also includes an early warning field, which is determined based on a business field in the corresponding early warning business table. The early warning conditions are used to constrain the field value of the early warning field. The method further includes: If the warning configuration information does not contain any warning field corresponding to any of the warning business tables, then the business table identifier corresponding to any of the warning business tables will be determined as an invalid table identifier. Multiple valid table identifiers are identified as corresponding to multiple valid early warning business tables, wherein the valid table identifiers are business table identifiers other than the invalid table identifiers among the multiple business table identifiers; Based on the data association, multiple business data entries that meet the warning conditions and are selected from the multiple valid warning business tables are merged to obtain warning data.

5. The method for acquiring early warning data according to claim 4, characterized in that, The method further includes: If the business table identifier corresponding to the target early warning business table is determined to be an invalid table identifier, then an early warning business table to be queried that has a dependency relationship with the target early warning business table is determined. The target early warning business table is any one of the multiple early warning business tables. If, in any of the dependencies between the pending early warning business table and the target early warning business table, the pending early warning business table depends on the target early warning business table, then the business table identifier of the pending early warning business table is determined to be an invalid table identifier.

6. The method for acquiring early warning data according to claim 1, characterized in that, The process involves sequentially identifying each of the sub-tables other than the target sub-table as a sub-table to be queried, and then filtering multiple pieces of business data that meet the warning conditions from the sub-tables to be queried to obtain warning data, including: If the temporary table contains an early warning business table that the query sub-table depends on, then based on the early warning business table that the query sub-table depends on and the data association and dependency relationship between the query sub-table and the query sub-table, the intermediate data in the temporary table is combined with multiple business data that meet the early warning conditions in the query sub-table to obtain new intermediate data, and the new intermediate data is recorded in the temporary table. If there is no unfiltered early warning business table, then each new intermediate data entry in the temporary table will be identified as the early warning data.

7. A device for acquiring early warning data, characterized in that, include: The acquisition unit is used to acquire early warning configuration information based on the early warning scheme creation instruction. The early warning configuration information includes multiple business table identifiers corresponding to multiple early warning business tables, the data association relationship between the multiple early warning business tables, and early warning conditions. The construction unit is used to construct an early warning scheme including the early warning configuration information; The data retrieval unit is used to receive data retrieval instructions for the early warning scheme; The merging unit is used to merge multiple business data that meet the warning conditions and are selected from the multiple warning business tables based on the data association relationship to obtain warning data; The multiple early warning business tables include one main table and multiple subordinate tables. Each of the early warning business tables has a dependency relationship with other early warning business tables that are different from the main table. The merging unit is specifically used to: filter multiple business data that meet the early warning conditions from the target subordinate tables that have a dependency relationship with the main table; combine the multiple business data filtered from the main table and the target subordinate tables to obtain multiple intermediate data according to the data association and dependency relationship between the main table and the target subordinate tables, and record each of the intermediate data in a temporary table; Each of the sub-tables other than the target sub-table is selected as the sub-table to be queried in turn, and multiple business data that meet the warning conditions are filtered in the sub-table to be queried to obtain the warning data.

8. A computer device, characterized in that, include: Central processing unit, memory, and input / output interfaces; The memory is either a short-term 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 of any one of claims 1 to 6.

9. A computer program product containing instructions, characterized in that, When the computer program product is run on a computer, it causes the computer to perform the method as described in any one of claims 1 to 6.

10. A computer storage medium, characterized in that, The computer storage medium stores instructions that, when executed on the computer, cause the computer to perform the method as described in any one of claims 1 to 6.

Images