Data circumscription method, data circumscription device, electronic device, and storage medium

Abstract

The application provides a data circumscription method, a data circumscription device, an electronic equipment and a storage medium, belongs to the field of financial technology, and through obtaining business requirement data of a target object, creating a circumscription scene according to the business requirement data, obtaining circumscription scene data, the circumscription scene data including a circumscription scene name, a circumscription object, a circumscription rule type and object identity information of a client, the circumscription rule type including a first rule type, obtaining a first target circumscription rule according to the circumscription object and the first rule type, generating a target page according to the first target circumscription rule and the circumscription scene name, and sending the target page to the client according to the object identity information, receiving circumscription condition data uploaded by the client, the circumscription condition data being circumscription conditions input by the target object on the target page, and performing circumscription on preset database data according to the circumscription condition data to obtain a data circumscription result, so that the development efficiency of the data circumscription function can be improved.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of financial technology, and in particular to a data circumscription method, a data circumscription device, an electronic device and a storage medium. BACKGROUND

[0002] In the recruitment scenario of insurance agents, as time develops and business processes change, the labels used by business clerks to circumscribe insurance agents often change. Each change requires the function side to be reissued, and the flexibility of the adjustment is limited and the timeliness is lagging, affecting the use of business clerks.

[0003] In other business scenarios, there are similar circumscription needs as in the recruitment scenario, such as screening and circumscribing agents with basic law risks according to the sales performance of insurance agents, screening business staff suitable for agent products according to the characteristics of different insurance products, and screening policies with single risks according to policy information. These different circumscription scenarios, different circumscription objects, and different labels all require independent customized function development, which is low in efficiency, high in development cost, weak in scalability, and almost no reusability. Moreover, for business clerks, the page style and function details are different in each different scenario, which is confusing and increases the learning and use cost of business clerks.

[0004] Since the circumscription object and the label of the circumscription object change with the change of the circumscription scenario, independent customized function development is required for different circumscription scenarios and different circumscription objects, resulting in low development efficiency of data circumscription functions. Therefore, how to improve the development efficiency of data circumscription functions has become a problem to be solved. SUMMARY

[0005] The main purpose of the embodiments of the present application is to propose a data circumscription method, a data circumscription device, an electronic device and a storage medium, which aims to improve the development efficiency of data circumscription functions, reduce the learning and use cost of business clerks, and thus improve the efficiency of data circumscription.

[0006] To achieve the above-mentioned purpose, a first aspect of the embodiments of the present application proposes a data circumscription method applied to a server side, the method comprising:

[0007] obtaining business requirement data of a target object;

[0008] creating a circumscription scenario according to the business requirement data to obtain circumscription scenario data; wherein the circumscription scenario data comprises a circumscription scenario name, a circumscription object, a circumscription rule type and object identity information of a client, and the circumscription rule type comprises a first rule type;

[0009] obtaining a first target circumscription rule according to the circumscription object and the first rule type;

[0010] generating a target page according to the first target circle rule and the circle scene name, and sending the target page to a client according to the object identity information;

[0011] receiving circle condition data uploaded by the client; the circle condition data is circle condition input by the target object on the target page;

[0012] performing circle on preset database data according to the circle condition data to obtain a data circle result.

[0013] In some embodiments, the first target circle rule is obtained according to the circle object and the first rule type, including:

[0014] generating a first front-end component according to the first rule type;

[0015] determining a circle label through the first front-end component and the circle object;

[0016] obtaining the first target circle rule according to the circle label.

[0017] In some embodiments, the circle rule type further includes a second rule type, and after the circle scene data is obtained by creating a circle scene according to the business requirement data, the data circle method further includes:

[0018] generating a second front-end component according to the second rule type;

[0019] determining circle label data through the second front-end component and the circle object; the circle label data includes a circle label, a label value of the circle label, and relationship data, and the relationship data is used to represent a logical operation relationship between the circle label and the label value;

[0020] generating a second target circle rule according to the circle label data;

[0021] obtaining the data circle result according to the second target circle rule.

[0022] In some embodiments, the data circle result is obtained according to the second target circle rule, including:

[0023] generating a database query statement according to the second target circle rule;

[0024] running the database query statement to perform circle on the database data to obtain the data circle result.

[0025] In some embodiments, the circling the preset database data according to the circling condition data to obtain a data circling result comprises:

[0026] obtaining an output label of the circling object; the output label is used to represent the output content of the circling object in the database data;

[0027] querying the database data according to the output label and the circling condition data to obtain the data circling result.

[0028] In some embodiments, the circling scenario data further comprises docking mode data of the server end and the client, and after the circling the preset database data according to the circling condition data to obtain a data circling result, the data circling method further comprises:

[0029] obtaining circling scenario state data;

[0030] if the circling scenario state data indicates that the circling scenario is enabled, the data circling result is pushed to the client according to the docking mode data.

[0031] In some embodiments, the docking mode data comprises docking mode and docking position information, and the pushing the data circling result to the client according to the docking mode data comprises:

[0032] if the docking mode is interface calling, the data circling result is sent to the interface corresponding to the docking position information, so that the client calls the interface to obtain the data circling result;

[0033] if the docking mode is message queue pushing, the data circling result is sent to the message queue corresponding to the docking position information, so that the client obtains the data circling result from the message queue.

[0034] To achieve the above object, a second aspect of the embodiment of the present application proposes a data circling device applied to a server end, the device comprises:

[0035] an obtaining module, configured to obtain business requirement data of a target object;

[0036] a circling scenario creating module, configured to create a circling scenario according to the business requirement data to obtain circling scenario data; wherein the circling scenario data comprises circling scenario name, circling object, circling rule type and object identity information of the client, and the circling rule type comprises a first rule type;

[0037] a circling rule determining module, configured to obtain a first target circling rule according to the circling object and the first rule type;

[0038] The sending module is configured to generate a target page according to the first target circle rule and the circle scene name, and send the target page to the client according to the object identity information.

[0039] The receiving module is configured to receive circle condition data uploaded by the client; the circle condition data is circle condition input by the target object on the target page.

[0040] The circle module is configured to circle preset database data according to the circle condition data to obtain a data circle result.

[0041] To achieve the above object, a third aspect of the embodiment of the present application provides an electronic device, which comprises a memory and a processor, the memory stores a computer program, and the processor implements the data circle method in the first aspect when executing the computer program.

[0042] To achieve the above object, a fourth aspect of the embodiment of the present application provides a computer readable storage medium, which stores a computer program, and the computer program is executed by a processor to implement the data circle method in the first aspect.

[0043] The data circle method, the data circle device, the electronic device and the storage medium provided by the present application can obtain business requirement data of a target object, create a circle scene according to the business requirement data, obtain circle scene data, and the circle scene data comprises a circle scene name, a circle object, a circle rule type and object identity information of a client, the circle rule type comprises a first rule type, different circle scenes can be created through the business requirement data, and a data circle result in different circle scenes can be generated, so that the data circle function can be used across scenes, instead of customized function development for each data circle scene. Further, the first target circle rule can be obtained according to the circle object and the first rule type, the target circle rule can be automatically generated according to different circle objects and circle rule types, instead of redeveloping corresponding data circle functions for each circle object, the expansibility of the data circle function is enhanced, and the development efficiency is improved. Furthermore, the target page can be generated according to the first target circle rule and the circle scene name, and the target page can be sent to the client according to the object identity information, so that the target object can obtain the target page meeting the business requirement. Finally, the circle condition data uploaded by the client is received, the preset database data is circled according to the circle condition data, and the data circle result is obtained, so that the target object can obtain the data circle result meeting the circle condition. While improving the development efficiency of the data circle function, the learning and use cost of business clerks is reduced, so that the efficiency of the data circle is improved. BRIEF DESCRIPTION OF DRAWINGS

[0044] Figure 1 This is a flowchart of the data delineation method provided in the embodiments of this application;

[0045] Figure 2 yes Figure 1 The flowchart of step S130 in the process;

[0046] Figure 3 This is another flowchart of the data delineation method provided in the embodiments of this application;

[0047] Figure 4 yes Figure 3 The flowchart of step S340 in the text;

[0048] Figure 5 yes Figure 1 The flowchart of step S160 in the process;

[0049] Figure 6 This is another flowchart of the data delineation method provided in the embodiments of this application;

[0050] Figure 7 yes Figure 6 The flowchart of step S620 in the process;

[0051] Figure 8 This is a schematic diagram of the data delineation device provided in the embodiments of this application;

[0052] Figure 9 This is a schematic diagram of the hardware structure of the electronic device provided in the embodiments of this application. Detailed Implementation

[0053] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0054] It should be noted that although functional modules are divided in the device schematic diagram and a logical order is shown in the flowchart, in some cases, the steps shown or described may be performed in a different order than the module division in the device or the order in the flowchart. The terms "first," "second," etc., in the specification, claims, and the aforementioned drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence.

[0055] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein is for the purpose of describing embodiments of this application only and is not intended to limit this application.

[0056] First, let's analyze some of the terms used in this application:

[0057] Data processing: Data processing involves extracting valuable information from large amounts of raw data and transforming it into information by processing and organizing raw data in various forms.

[0058] In the recruitment of insurance agents, the tags used by back-office staff to identify agents frequently change over time and with changes in business processes. Each change requires a complete redesign of the feature, limiting flexibility and causing delays, which impacts the usability for back-office staff.

[0059] In other business scenarios, there are similar targeting needs to recruitment scenarios. For example, screening agents with basic legal risks based on their sales performance, selecting agents suitable for different insurance products based on their characteristics, and screening policies with splitting risks based on policy information. These different targeting scenarios, different target groups, and different tags all require independent customized function development, resulting in low efficiency, high development costs, poor scalability, and almost no reusability. Furthermore, for business back-office staff, each different scenario has a different page style and functional details, which can be overwhelming and increase the learning and usage costs for them.

[0060] Because the defined objects and their tags change with the defined scenario, separate customized features need to be developed for different defined scenarios and objects, resulting in low development efficiency for data definition functionality. Therefore, improving the development efficiency of data definition functionality has become an urgent problem to be solved.

[0061] Based on this, embodiments of this application provide a data delineation method, a data delineation device, an electronic device, and a computer-readable storage medium, aiming to improve the development efficiency of data delineation functions.

[0062] The data delineation method, data delineation device, electronic device, and computer-readable storage medium provided in this application are specifically described through the following embodiments. First, the data delineation method in this application is described.

[0063] The data delineation method provided in this application relates to the field of financial technology. This data delineation method can be applied to a terminal, a server, or software running on either a terminal or a server. In some embodiments, the terminal can be a smartphone, tablet, laptop, desktop computer, etc.; the server can be configured as an independent physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN, and big data and artificial intelligence platforms; the software can be an application implementing the data delineation method, but is not limited to the above forms.

[0064] This application can be used in a wide variety of general-purpose or special-purpose computer system environments or configurations. Examples include: personal computers, server computers, handheld or portable devices, tablet devices, multiprocessor systems, microprocessor-based systems, set-top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe computers, and distributed computing environments including any of the above systems or devices. This application can be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform specific tasks or implement specific abstract data types. This application can also be practiced in distributed computing environments where tasks are performed by remote processing devices connected via a communication network. In distributed computing environments, program modules can reside in local and remote computer storage media, including storage devices.

[0065] It should be noted that in all specific embodiments of this application, when processing data related to user identity or characteristics, such as user information, user behavior data, user historical data, and user location information, user permission or consent is obtained first. Furthermore, the collection, use, and processing of this data comply with relevant laws, regulations, and standards. In addition, when embodiments of this application require access to sensitive personal information of users, separate permission or consent from the user is obtained through pop-ups or redirection to confirmation pages. Only after obtaining the user's separate permission or consent is the necessary user-related data required for the proper functioning of these embodiments acquired.

[0066] Figure 1 This is an optional flowchart of the data delineation method provided in the embodiments of this application. Figure 1 The method described herein is applied to the server side and may include, but is not limited to, steps S110 to S160.

[0067] Step S110: Obtain the business requirement data of the target object;

[0068] Step S120: Create a defined scenario based on business requirement data to obtain defined scenario data; wherein, the defined scenario data includes the defined scenario name, defined object, defined rule type and object identity information of the client, and the defined rule type includes the first rule type;

[0069] Step S130: Obtain the first target delineation rule based on the delineated object and the first rule type;

[0070] Step S140: Generate a target page based on the first target delineation rules and the delineated scene name, and send the target page to the client based on the object identity information;

[0071] Step S150: Receive the selection criteria data uploaded by the client; the selection criteria data is the selection criteria entered by the target object on the target page.

[0072] Step S160: Delineate the preset database data according to the delineation condition data to obtain the data delineation result.

[0073] Steps S110 to S160, as illustrated in this embodiment, involve acquiring business requirement data of the target object, creating a defined scenario based on the business requirement data, and obtaining defined scenario data. The defined scenario data includes the defined scenario name, the defined object, the defined rule type, and the client's object identity information. The defined rule type includes a first rule type. Different defined scenarios can be created using the business requirement data, and data defining results under different defined scenarios can be generated, enabling the data defining function to be used across scenarios, rather than requiring customized function development for each data defining scenario. Furthermore, by obtaining a first target defining rule based on the defined object and the first rule type, target defining rules can be automatically generated based on different defined objects and defined rule types, without needing to redevelop corresponding data defining functions for each defined object, thus enhancing the scalability of the data defining function and improving development efficiency. Even further, by generating a target page based on the first target defining rule and the defined scenario name, and sending the target page to the client based on the object identity information, the target object can obtain a target page that meets its business requirements. Finally, the system receives the delineation condition data uploaded by the client, delines the preset database data according to the delineation condition data, and obtains the data delineation result, which enables the target object to obtain the data delineation result that meets the delineation condition.

[0074] In step S110 of some embodiments, user business requirement data is acquired. The user can be a department manager, office staff, etc. This business requirement data represents the client user's business needs. The client is the front-end touchpoint for user-server interaction to achieve data targeting. It can be different types of applications, application platforms, or application systems. The server is a back-end server that supports data targeting functionality. It is understood that the client provides users with directly usable pages so that users can access back-end services through these pages.

[0075] In step S120 of some embodiments, a defined scenario can be created according to business needs by clicking the "Create Defined Scenario" button control. A shuttle component is generated in response to the click of the "Create Defined Scenario" button. The page information of the shuttle component includes basic information and other information. The basic information includes options such as defined scenario name, defined object, business owner, remarks, defined scope, and rule type. The other information includes options such as application name, application user, and integration method. The basic information and other information are configured through the shuttle component, and the configuration information of the basic information and other information is used as defined scenario data. Defined scenario data is obtained. The defined scenario name is obtained by filling in the defined scenario name option. A defined object suitable for business needs is selected from the drop-down list, such as insurance agent, prospective recruiter, or policy. The business owner is used to indicate the business domain and can be selected from the drop-down list, such as human resource development, training, or basic law. The remarks section is optional and is used to describe the details or business value of the defined scenario, facilitating the identification and management of the defined scenario. For example, if the defined scenario name is "Recruitment Entity Defined," the remarks could be used in the agent recruitment process for internal staff or department managers to screen agents with high recruitment potential. The defined scope includes a first defined scope and a second defined scope. The first defined scope is the entire system, i.e., the entire company. The second defined scope is determined based on the client user's permissions, encompassing the client user's organization and its subordinate organizations. For example, if the user is an internal staff member in a third-level organization in City B, Province A, then their defined scope is the third-level organization and its subordinate organizations in City B, Province A. The defined rule type can be selected as the first rule type using a radio button control. The first rule type is a custom rule, requiring user definition. The client's object identity information is obtained by filling in the application name and the application user. The application name can be the business analysis platform, and the application user can be the application's user ID. The connection method is selected from the dropdown menu to obtain the connection method data. By configuring different information content for different defined scenarios and defined objects, the usage and learning costs for business staff are reduced. Based on this information content, defined scenario data that meets business needs can be obtained, improving the reusability and scalability of the data definition function. This eliminates the need to develop customized data definition functions for each defined scenario and defined object, thus improving the development efficiency of the data definition function.

[0076] Please see Figure 2 In some embodiments, step S130 may include, but is not limited to, steps S210 to S230:

[0077] Step S210: Generate the first front-end component according to the first rule type;

[0078] Step S220: Determine the selection label using the first front-end component and the selection object;

[0079] Step S230: Obtain the first target delineation rule based on the delineation label.

[0080] In step S210 of some embodiments, in response to a click on the rule configuration button control, a first front-end component is generated according to a first rule type, wherein the first front-end component is a shuttle component. The page of the first front-end component includes a first page block and a second page block. The first page block is used to select tags, and the second page block is used to display the selected tags. The first page block includes a checkbox component, a query component, and all tags. The checkbox component is used to select one or more tags that match the selected object from all tags as the selected tags. The query box component is used to query whether a preset tag exists among all tags. Specifically, the preset tag is input to the query component. In response to the query operation of the query component, the preset tag is retrieved from all tags, and then the preset tag is selected as the selected tag through the checkbox component. The tag is used to describe the attributes of the selected object. For example, if the selected object is an agent, the attributes are the agent's age, level, gender, etc. The second page block includes the tags selected in the first page block and a query component. The query component is used to query whether the preset tag has been selected. The first front-end component supports importing tag IDs. Tags can be displayed in the form of tag ID-tag name or tag name. Tag IDs can be named tag1, tag2, etc.

[0081] It should be noted that the first rule type is a custom rule, which only configures the optional tag range, and does not configure the tag values ​​or tag logical operation rules. The tag values ​​and tag logical operation relationships are defined by the client user. The optional tag range is the tag range formed by all the selected tags, and the client user can only see the tags within the optional tag range.

[0082] In step S220 of some embodiments, one or more tags matching the selected object are selected from all tags as selection tags by the checkbox component of the first page block of the first front-end component, wherein the selection tags are available tags for the data selection function.

[0083] In recruitment and agent targeting scenarios, the tags used to target agents frequently change over time and with changes in recruitment processes. Each change requires re-modifying the code for that business segment and releasing a new version, limiting the flexibility and timeliness of tag adjustments. Furthermore, different business scenarios have different targeting needs. For example, in sales targeting, agents with basic legal risks need to be identified based on their sales performance. In insurance targeting, agents suitable for different insurance products need to be identified based on their characteristics, and policies with splitting risks need to be identified based on policy information. Different targeting scenarios, different target groups, and different tags all require independent customized function development, resulting in low development efficiency.

[0084] This application embodiment configures the tags corresponding to different targeted objects under different targeting scenarios through the first front-end component, which can flexibly adjust the targeting tags without modifying the code, and the modifications take effect immediately, improving the response efficiency to changes in business requirements. At the same time, it does not require customized function development for different targeting scenarios, targeted objects, and tags, so that the data targeting function can be used across scenarios and business lines, improving the scalability and reusability of the data targeting function.

[0085] In step S230 of some embodiments, the second page block further includes a confirm button control, which, in response to clicking the confirm button control, sets the selected label as the first target selection rule. The second page block also includes a cancel button control, which, in response to clicking the cancel button control, clears the selected label and exits the rule configuration task.

[0086] Through the above steps S210 to S230, a first target delineation rule corresponding to the first rule type can be generated, so as to delineate data according to the first target delineation rule and obtain a data delineation result that meets business requirements.

[0087] Please see Figure 3 In some embodiments, after step S120, the delineation rule type further includes a second rule type, and the data delineation method further includes, but is not limited to, steps S310 to S340:

[0088] Step S310: Generate the second front-end component according to the second rule type;

[0089] Step S320: Determine the delimited label data through the second front-end component and the delimited object; the delimited label data includes the delimited label, the label value of the delimited label, and the relationship data, which is used to characterize the logical operation relationship between the delimited label and the label value;

[0090] Step S330: Generate a second target delineation rule based on the delineation label data;

[0091] Step S340: Obtain the data delineation result according to the second target delineation rule.

[0092] In step S310 of some embodiments, in response to a click on the rule configuration button control, a second front-end component is generated according to a second rule type. The second rule type is a fixed rule type and does not require user definition. The second front-end component supports hierarchical configuration, which can be a multi-level configuration, up to three levels. If the hierarchical configuration is three levels, the page of the second front-end component includes a first-level tag configuration block, a second-level tag configuration block, and a third-level tag configuration block. Each level of tag configuration block includes three drop-down components: a first drop-down component, a second drop-down component, and a third drop-down component. The first drop-down component is used to select a tag that matches the selected object from all tags as the selected tag. The second drop-down component is used to select the logical operation relationship between the tag and the tag value. The logical operation relationship includes equal to, greater than, less than, greater than or equal to, and less than or equal to. The third drop-down component is used to select the tag value. The relationship between the three tag configuration blocks is a logical OR relationship. Each level of tag configuration block also includes an add configuration block component. Taking the first-level label configuration block as an example, in response to the click of the add configuration block component, a new label configuration block is added below the original label configuration block. The new label configuration block and the original label configuration block in this layer together constitute the new first-level label configuration block. The relationship between the label configuration blocks in the first-level label configuration block is a logical AND relationship.

[0093] If the configuration information represented by the first-level label configuration block is: "Gender = Female and Age > 35", then the first-level label configuration block includes two label configuration blocks. The first drop-down component of the first label configuration block selects gender, the second drop-down component selects =, and the third drop-down component selects female. The first drop-down component of the second label configuration block selects age, the second drop-down component selects >, and the third drop-down component selects 35.

[0094] If the configuration information represented by the first-level label configuration block is "gender = female and age > 35", and the configuration information represented by the second-level label configuration block is "gender = male", then the configuration information represented by the first-level label configuration block and the second-level label configuration block is either "gender = female and age > 35" or "gender = male".

[0095] In step S320 of some embodiments, a label matching the selected object is selected from all labels by the first drop-down box component of the label configuration block, the logical operation relationship between the label and the label value is selected by the second drop-down box component, and the label value is selected by the third drop-down box component. After all levels of configuration are completed, all selected labels, logical operation relationships and label values ​​are used as the selected label data.

[0096] In step S330 of some embodiments, the page of the second front-end component further includes a confirm button control and a cancel button control. In response to clicking the confirm button control, the selected label data is used as the second target selection rule. In response to clicking the cancel button control, the selected label, logical operation relationship and label value are canceled, and the rule configuration task is exited.

[0097] In step S340 of some embodiments, a database query statement is generated according to the second target delineation rule, the database query statement is run, the database data is queried in real time, and the data delineation result is obtained.

[0098] Through the above steps S310 to S340, a second target delineation rule corresponding to the second rule type can be generated, and the database data can be delineated according to the second target delineation rule to obtain a data delineation result that meets business requirements.

[0099] Please see Figure 4 In some embodiments, step S340 may include, but is not limited to, steps S410 to S420:

[0100] Step S410: Generate a database query statement according to the second target delineation rules;

[0101] Step S420: Run the database query statement to delineate the database data and obtain the data delineation result.

[0102] In step S410 of some embodiments, the second target delineation rule is filled into a preset query statement template to generate a database query statement.

[0103] In step S420 of some embodiments, the second front-end component further includes a runtime configuration component, which configures the runtime of the second target targeting rule. A database query statement is executed according to the runtime to process the database data and obtain the data targeting results. For example, if the runtime is 8:00 AM on the 2nd of each month, then the database query statement is automatically executed at 8:00 AM on the 2nd of each month to obtain the data targeting results.

[0104] This application embodiment can flexibly adjust the selection tags, tag values, logical operation relationships between selection tags and tag values, and running cycle through the second front-end component, and generate second target selection rules that meet business needs, thereby improving the response efficiency to changes in business needs. Moreover, all kinds of editing revisions take effect immediately without the need for re-release.

[0105] Through the above steps S410 to S420, the second target delineation rule can be run periodically and the corresponding data delineation results can be generated.

[0106] In step S140 of some embodiments, the selected scene name is used as the webpage title tag, the first target selection rule is used as the webpage content, the target page is generated according to the first target selection rule and the selected scene name, and the target page is sent to the client user according to the object identity information, i.e., the client user's ID.

[0107] In step S150 of some embodiments, the client user inputs selection criteria on the target page and obtains selection criteria data, wherein the selection criteria include the label values ​​of the selection tags and the logical operation relationship between the selection tags and the label values. In response to the click of the confirm button control on the target page, the selection criteria data is sent to the server.

[0108] Please see Figure 5 In some embodiments, step S160 may include, but is not limited to, steps S510 to S520:

[0109] Step S510: Obtain the output label of the selected object; the output label is used to represent the output content of the selected object in the database data;

[0110] Step S520: Query the database data based on the output labels and delineation conditions to obtain the data delineation results.

[0111] In step S510 of some embodiments, in response to the click of the output configuration button control, a third front-end component is generated. The third front-end component is a shuttle component, which is used to configure the output content of the relevant information of the selected object in the database data. The third front-end component selects one or more tags from all tags as output tags. The output tags are the attribute information of the selected object in the database data, such as name, employee number, job level, business area, business department, etc. The page of the third front-end component is the same as that of the first front-end component, and will not be described again here.

[0112] In step S520 of some embodiments, a database query statement is generated based on the output label, the selection label, and the selection condition data. The database query statement is then executed to query the database data, resulting in a data selection result. Specifically, the database query statement is executed to locate the database data based on the selection label and the selection condition data, obtaining the selection objects that meet the selection condition data. The information of the selection objects is then filtered using the output label, and the data selection result is output. For example, if the selection object is an agent, the selection label is age, the selection condition data for the selection label is >35, and the output labels are name, employee number, and job title, then agents older than 35 years old are located from the database data based on the selection label and the selection condition data. The names, employee numbers, and job titles of the agents older than 35 years old are then output based on the output labels, resulting in a data selection result consisting of the names, employee numbers, and job titles of all agents older than 35 years old in the database data.

[0113] It should be noted that each targeted object has a unique ID. If the targeted object is an agent, the unique ID is their ID card number; if the targeted object is an insurance policy, the unique ID is the policy number. Based on the output label and the unique ID of the targeted object, the label value of the output label is queried to obtain the data targeting result, which is then matched and output according to the unique ID of the targeted object. For example, if the agent's ID card number is 002, and the output label is age, querying the database based on the ID card number and the output label yields a label value of 45. Therefore, the data targeting result is: the agent with ID card number 002 is 45 years old.

[0114] In steps S510 to S530 above, the output labels enable the output content of the data delineation results to be automatically adjusted. By limiting the output content of the data delineation results through the output labels, the information that is allowed to be output to the delineated object can be displayed to the user, rather than all the information of the delineated object, thus ensuring the security of the delineated object information.

[0115] Please see Figure 6 In some embodiments, the delineation of scene data also includes data on the connection method between the server and the client. After step S160, the data delineation method may also include, but is not limited to, steps S610 to S620:

[0116] Step S610: Obtain the state data of the defined scene;

[0117] Step S620: If the scene definition status data indicates that scene definition is enabled, the scene definition result is sent to the client according to the connection method data.

[0118] In step S610 of some embodiments, the state of the selection switch is detected to obtain the switch state. Based on the switch state, selection scene state data is obtained, which indicates whether the selection scene is activated. If the selection switch is on, the switch state is the first state, and the selection scene state data indicates that the selection scene is activated. If the selection switch is off, the switch state is the second state, and the selection scene state data indicates that the selection scene is disabled. It is understood that the selection switch can be turned on or off via a click operation. When the selection switch is on, the client cannot access the selection results; when the selection switch is off, the client can access the selection results.

[0119] In step S620 of some embodiments, if the scene delineation status data indicates that scene delineation is enabled, meaning that the client is allowed to access the data delineation results, then the data delineation results are sent to the client according to the interface method data. If the scene delineation status data indicates that scene delineation is disabled, meaning that the client is not allowed to access the data delineation results, then the data delineation results are not sent.

[0120] In some embodiments, the page containing the newly created selection button control also includes existing selection scenarios. These scenarios include topics such as selection name, selection object, rule type, business owner, application name, status, creator, creation time, last update time, enable / disable, rule configuration, output configuration, and operations. Under these topics, specific information such as selection name, selection object, rule type, business owner, application name, status, creator, creation time, and last update time are included. The enable / disable topic includes the selection switch corresponding to the selection scenario, and the rule configuration topic includes the rules for the selection scenario. Configure button controls to generate first or second target delimitation rules by clicking the rule configuration button controls. Under the output configuration topic, there is an output configuration button control corresponding to the delimited scene, so that the output label can be obtained by clicking the output configuration button control. Under the operation topic, there are view button controls, edit button controls, and delete button controls. By clicking the view button control, you can view the delimited scene data, delimited label, and output label of the delimited scene. By clicking the edit button control, you can edit the delimited scene data, delimited label, and output label of the delimited scene. By clicking the delete button control, you can delete the delimited scene.

[0121] When developing customized features for different defined scenarios, defined objects, and defined tags, the page styles and functional details vary across different scenarios, increasing the usage and learning costs for operators. This application integrates multiple scenarios, centrally consolidating defined scenario data and defined tags, avoiding the need for operators to use multiple systems and terminals to operate different scenarios. This facilitates one-stop management for operators, reducing usage and learning costs.

[0122] In steps S610 to S620 above, the activation status of each selected scene can be managed with one click by clicking the selection switch.

[0123] Please see Figure 7 In some embodiments, the docking method data includes docking method and docking position information, and step S620 may include, but is not limited to, step S710 or step S720:

[0124] Step S710: If the docking method is an interface call, the data delineation result is sent to the interface corresponding to the docking location information so that the client can call the interface and obtain the data delineation result.

[0125] Step S720: If the connection method is message queue push, the data delineation result is sent to the message queue corresponding to the connection location information so that the client can obtain the data delineation result from the message queue.

[0126] In step S710 of some embodiments, the data delineation function only supports single manual delineation, requiring manual delineation and result distribution each time. To enable automatic distribution of data delineation results, this application uses two integration methods—interface call (API call) and message queue push (MQ push)—to distribute the data delineation results to the client. If the integration method is an interface call, the server sends the data delineation results to the API interface corresponding to the integration location information. The client calls this API interface based on the object identity information to distribute the data delineation results to the client user corresponding to the object identity information, where the integration location information is the address of the API interface.

[0127] In step S720 of some embodiments, if the docking method is message queue push, the server sends the data delineation result to the Kafka message queue corresponding to the docking location information. The client consumes the data delineation result from the Kafka message queue according to the object identity information. The docking location information is the address of the Kafka message queue and the message logical classification category (topic). Each topic includes multiple partitions.

[0128] It is understandable that each data segmentation result sent to Kafka has a message category, and data segmentation results of different message categories are stored in different topics, and the data segmentation results are stored in different partitions according to the topic's partitioning rules.

[0129] Through steps S710 to S720, the data delineation results can be automatically sent to the client, which improves the efficiency and accuracy of the sending compared with the manual sending method.

[0130] If the target audience is a department manager, the front-end touchpoint is the E application - Operations - Subject Targeting. The business requirement data is that the department manager opens the E application, enters the Subject Targeting function page, selects tags (job level, whether a top performer, current number of consecutive drills), and enters or selects tag values ​​to target personnel, and views the name, employee ID, subject type, recruitment potential, sales area, sales department, and job level of the targeted personnel. First, create a new targeting based on the business requirement data, and configure basic and other information. Configure the targeting name as "Application E Subject Targeting Configuration," the targeting object as "Agent," the targeting type as "Custom Rule," the business owner as "Recruitment," the targeting scope as the operator's (department manager's) organization and its subordinate organizations, the application name as "Application E," the application user as "LCDP-RCD," the connection method as "API Interface," and enter the API address. Then configure the rules, selecting the job level tag, whether a top performer tag, and the current number of consecutive drills tag as the targeting tags. Finally, configure the output, selecting the name. The system generates a target page by identifying tags, including employee ID tags, entity type tags, recruitment potential tags, sales area tags, sales department tags, and job level tags. Based on the application user's name and username, the target page is sent to the application user. The application user can see the identified tags on the target page and input the tag values ​​and logical operations for each tag. For example, job level = supervisor and "Talent Status" = yes and current consecutive diamond count > 5. After clicking confirm, the system returns matching agents with their "Name," "Employee ID," "Entity Type," "Recruitment Potential," "Sales Area," "Sales Department," and "Job Level" information. If additional tags need to be added later, or if adjustments are needed to tags such as "Job Level," "Talent Status," or "Current Consecutive Diamond Count," or if the output content needs to be adjusted, business requirement data can be obtained, and the rules or output configuration can be readjusted accordingly.

[0131] If the target is an organization's internal staff, the front-end touchpoint is System D - Risk Management - Risk Screening. The business requirement data is 8:00 AM on the 26th of each month. Identify risk agents suspected of switching from old to new business in the previous month and push the list of these individuals, along with their employee ID, date of joining the company, referrer's name, referrer's ID, and the statistical month, to System D. First, create a new targeting area based on the business requirement data and configure basic and other information. Configure the targeting area name as "D System Suspected Agents Switching from Old to New Business Risk Targeting," configure the targeting object as "agent," configure the targeting type as "fixed rule," configure the output frequency as "monthly," configure the output time as "26th of the month at 8:00 AM," configure the business owner as "Basic Law," configure the targeting scope as "entire system," configure the application party name as "System D," configure the application party user as "LBDP-LCS," configure the connection method as "MQ push," and enter the topic and scenario creator information. Then, in the fixed rule configuration interface, configure the rules, including the targeting tags, tag values, and logical operation relationships. For example, the agent's premium for returning old policies to new ones must be ≥100,000, the agent's number of long-term insurance policies must be ≥2, and the agent's 13-month premium persistency rate must be <75% or the cumulative number of sales dispute complaints in the past six months must be ≥1. Next, configure the output, selecting the name tag, employee ID tag, date of joining the company tag, referrer's name tag, referrer's number tag, and statistical month tag as output tags. Generate a second target targeting rule based on the targeting tags, tag values, and logical operation relationships. Run the second target targeting rule according to the configured output frequency and time. Based on the output tags, the system D can receive a list of agents suspected of returning old policies to new ones who meet the fixed rule conditions across the entire system at 8:00 AM on the 26th of each month. At the same time, you can see the tag information such as "Name", "Employee ID", "Date of Joining the Company", "Referrer's Name", "Referrer's Number", and "Statistical Month".

[0132] If you need to modify the fixed rules, adjust the output time, or change the output content later, you can go to the fixed rule configuration interface to reconfigure the fixed rules.

[0133] The data targeting method in this application embodiment allows for flexible adjustment of various configurations such as targeting tags, rules, output tags, and output time. Modifications take effect immediately without requiring release updates or code changes, improving responsiveness to changes in business requirements. Furthermore, the data targeting function can be used across scenarios and business lines, enhancing reusability and scalability, improving development efficiency, and reducing development costs. The data targeting method supports both custom rules and fixed rules. Custom and fixed rules enable real-time targeting of objects, and fixed rules eliminate the need for manual targeting and result distribution each time; once configured, data targeting results can be automatically generated and distributed.

[0134] Please see Figure 8This application also provides a data delineation device, applied on a server side, which can implement the above-described data delineation method. The device includes:

[0135] Module 810 is used to acquire business requirement data of the target object;

[0136] The scenario creation module 820 is used to create scenario-defined areas based on business requirement data and obtain scenario-defined area data. The scenario-defined area data includes the scenario-defined area name, the defined object, the defined rule type, and the object identity information of the client. The defined rule type includes the first rule type.

[0137] The delineation rule determination module 830 is used to obtain the first target delineation rule based on the delineation object and the first rule type;

[0138] The sending module 840 is used to generate a target page based on the first target delineation rules and the delineation scene name, and send the target page to the client based on the object identity information;

[0139] The receiving module 850 is used to receive the selection condition data uploaded by the client; the selection condition data is the selection condition entered by the target object on the target page;

[0140] The delineation module 860 is used to delineate the preset database data according to the delineation condition data to obtain the data delineation result.

[0141] The specific implementation of this data delineation device is basically the same as the specific embodiment of the data delineation method described above, and will not be repeated here.

[0142] This application also provides an electronic device, which includes a memory and a processor. The memory stores a computer program, and the processor executes the computer program to implement the above-described data selection method. This electronic device can be any smart terminal, including tablet computers, in-vehicle computers, etc.

[0143] Please see Figure 9 , Figure 9 The hardware structure of an electronic device according to another embodiment is illustrated. The electronic device includes:

[0144] The processor 910 can be implemented using a general-purpose CPU (Central Processing Unit), microprocessor, application-specific integrated circuit (ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solutions provided in the embodiments of this application.

[0145] The memory 920 can be implemented as a read-only memory (ROM), a static storage device, a dynamic storage device, or a random access memory (RAM). The memory 920 can store the operating system and other application programs. When the technical solutions provided in the embodiments of this specification are implemented through software or firmware, the relevant program code is stored in the memory 920 and is called and executed by the processor 910 using the data delimitation method of the embodiments of this application.

[0146] The input / output interface 930 is used to implement information input and output;

[0147] The communication interface 940 is used to enable communication and interaction between this device and other devices. Communication can be achieved through wired means (such as USB, network cable, etc.) or wireless means (such as mobile network, WIFI, Bluetooth, etc.).

[0148] Bus 950 transmits information between various components of the device (e.g., processor 910, memory 920, input / output interface 930, and communication interface 940);

[0149] The processor 910, memory 920, input / output interface 930 and communication interface 940 are connected to each other within the device via bus 950.

[0150] This application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the above-described data delimitation method.

[0151] Memory, as a non-transitory computer-readable storage medium, can be used to store non-transitory software programs and non-transitory computer-executable programs. Furthermore, memory may include high-speed random access memory, and may also include non-transitory memory, such as at least one disk storage device, flash memory device, or other non-transitory solid-state storage device. In some embodiments, memory may optionally include memory remotely located relative to the processor, and these remote memories can be connected to the processor via a network. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.

[0152] The data delineation method, data delineation device, electronic device, and computer-readable storage medium provided in this application embodiment acquire business requirement data of the target object, create delineation scenarios based on the business requirement data, and obtain delineation scenario data. The delineation scenario data includes the delineation scenario name, the delineation object, the delineation rule type, and the client's object identity information. The delineation rule type includes a first rule type. Different delineation scenarios can be created using the business requirement data, and data delineation results under different delineation scenarios can be generated, enabling the data delineation function to be used across scenarios, rather than requiring customized function development for each data delineation scenario. Furthermore, by obtaining a first target delineation rule based on the delineation object and the first rule type, target delineation rules can be automatically generated according to different delineation objects and delineation rule types, without needing to redevelop corresponding data delineation functions for each delineation object, enhancing the scalability of the data delineation function and improving development efficiency. Even further, by generating a target page based on the first target delineation rule and the delineation scenario name, and sending the target page to the client based on the object identity information, the target object can obtain a target page that meets its business requirements. Finally, the system receives the delineation condition data uploaded by the client, delines the preset database data according to the delineation condition data, and obtains the data delineation result, which enables the target object to obtain the data delineation result that meets the delineation condition.

[0153] The embodiments described in this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided by the embodiments of this application. As those skilled in the art will know, with the evolution of technology and the emergence of new application scenarios, the technical solutions provided by the embodiments of this application are also applicable to similar technical problems.

[0154] Those skilled in the art will understand that the technical solutions shown in the figures do not constitute a limitation on the embodiments of this application, and may include more or fewer steps than shown, or combine certain steps, or different steps.

[0155] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs.

[0156] Those skilled in the art will understand that all or some of the steps in the methods disclosed above, as well as the functional modules / units in the systems and devices, can be implemented as software, firmware, hardware, or suitable combinations thereof.

[0157] The terms “first,” “second,” “third,” “fourth,” etc. (if present) in the specification and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms “comprising” and “having,” and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0158] It should be understood that in this application, "at least one (item)" means one or more, and "more than" means two or more. "And / or" is used to describe the relationship between related objects, indicating that three relationships can exist. For example, "A and / or B" can represent three cases: only A exists, only B exists, and both A and B exist simultaneously, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one (item) of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one (item) of a, b, or c can represent: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, and c can be single or multiple.

[0159] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of the units described above 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 through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0160] The units described above 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.

[0161] 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.

[0162] 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 multiple 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 of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing programs, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0163] The preferred embodiments of the present application have been described above with reference to the accompanying drawings, but this does not limit the scope of the claims of the present application. Any modifications, equivalent substitutions, and improvements made by those skilled in the art without departing from the scope and substance of the embodiments of the present application shall be within the scope of the claims of the present application.

Claims

1. A data bounding method, characterized by, Applied to a server side, the data circumscription method comprises: obtaining business requirement data of a target object; creating a circumscription scene according to the business requirement data to obtain circumscription scene data; wherein the circumscription scene data comprises a circumscription scene name, a circumscription object, a circumscription rule type and object identity information of a client, and the circumscription rule type comprises a first rule type; obtaining a first target circumscription rule according to the circumscription object and the first rule type; generating a target page according to the first target circumscription rule and the circumscription scene name, and sending the target page to the client according to the object identity information; receiving circumscription condition data uploaded by the client; the circumscription condition data is a circumscription condition input by the target object on the target page; circumscribing preset database data according to the circumscription condition data to obtain a data circumscription result; the obtaining of the first target circumscription rule according to the circumscription object and the first rule type comprises: generating a first front-end component according to the first rule type; determining a circumscription label through the first front-end component and the circumscription object; and obtaining the first target circumscription rule according to the circumscription label; the circumscription rule type further comprises a second rule type, and after the obtaining of the circumscription scene data according to the business requirement data, the data circumscription method further comprises: generating a second front-end component according to the second rule type; determining circumscription label data through the second front-end component and the circumscription object; the circumscription label data comprises a circumscription label, a label value of the circumscription label and relationship data, the relationship data being used to represent a logical operation relationship between the circumscription label and the label value; generating a second target circumscription rule according to the circumscription label data; and obtaining the data circumscription result according to the second target circumscription rule.

2. The data bounding method of claim 1, wherein, the obtaining of the data circumscription result according to the second target circumscription rule comprises: generating a database query statement according to the second target circumscription rule; running the database query statement to circumscribe the database data to obtain the data circumscription result.

3. The data bounding method of claim 1, wherein, the circumscribing of the preset database data according to the circumscription condition data to obtain the data circumscription result comprises: obtaining an output label of the circumscription object; the output label is used to represent output content of the circumscription object in the database data; querying the database data according to the output label and the circumscription condition data to obtain the data circumscription result.

4. The data bounding method according to any one of claims 1 to 3, characterized in that, the circumscription scene data further comprises docking mode data of the server side and the client, and after the circumscribing of the preset database data according to the circumscription condition data to obtain the data circumscription result, the data circumscription method further comprises: obtaining circumscription scene state data; if the circumscription scene state data indicates that the circumscription scene is enabled, then downloading the data circumscription result to the client according to the docking mode data.

5. The data bounding method of claim 4, wherein, the docking mode data comprises a docking mode and docking position information, and the downloading of the data circumscription result to the client according to the docking mode data comprises: If the docking manner is an interface call, the data circumscription result is sent to an interface corresponding to the docking position information, so that the client calls the interface to obtain the data circumscription result; If the docking manner is a message queue push, the data circumscription result is sent to a message queue corresponding to the docking position information, so that the client obtains the data circumscription result from the message queue.

6. A data delineation device characterized by, The data circumscription device applied to a server side comprises: An acquisition module configured to acquire business requirement data of a target object; A circumscription scene creation module configured to create a circumscription scene according to the business requirement data to obtain circumscription scene data; wherein the circumscription scene data comprises a circumscription scene name, a circumscription object, a circumscription rule type, and object identity information of a client, and the circumscription rule type comprises a first rule type and a second rule type; A circumscription rule determination module configured to obtain a first target circumscription rule according to the circumscription object and the first rule type; A sending module configured to generate a target page according to the first target circumscription rule and the circumscription scene name, and send the target page to the client according to the object identity information; A receiving module configured to receive circumscription condition data uploaded by the client; the circumscription condition data is circumscription condition input by the target object on the target page; A circumscription module configured to circumscribe preset database data according to the circumscription condition data to obtain a data circumscription result; The data circumscription device is further configured to: generate a first front-end component according to the first rule type; determine a circumscription label through the first front-end component and the circumscription object; and obtain the first target circumscription rule according to the circumscription label; generate a second front-end component according to the second rule type; determine circumscription label data through the second front-end component and the circumscription object; the circumscription label data comprises a circumscription label, label value of the circumscription label, and relationship data, wherein the relationship data is used to represent a logical operation relationship between the circumscription label and the label value; generate a second target circumscription rule according to the circumscription label data; and obtain the data circumscription result according to the second target circumscription rule.

7. An electronic device, characterized by The electronic device comprises a memory and a processor, the memory stores a computer program, and the processor implements the data circumscription method of any one of claims 1 to 5 when executing the computer program.

8. A computer-readable storage medium storing a computer program, the computer program comprising instructions that, when executed by a computer, cause the computer to perform the method of any one of claims 1 to 7. The computer program is executed by the processor to implement the data circumscription method of any one of claims 1 to 5.

Images