Application tag configuration method and device, computer equipment and storage medium

Abstract

The invention relates to the field of data analysis, and discloses an application tag configuration method and device, computer equipment and a storage medium, and the method comprises the steps: obtaining a first configuration demand of a current user for a data source connection string; determining a basic label and an initial data source according to the first configuration requirement, and mapping the basic label with each field type in the initial data source to obtain initial configuration information; acquiring a second configuration demand of the current user for the initial configuration information; and combining the basic tags according to the second configuration requirement to obtain application tags, and performing mapping configuration on the application tags and each field type in the data source to obtain target configuration information of the application tags. According to the method, the problems of poor configuration flexibility, high research, development and learning cost and low calculation and storage efficiency of traditional user tag generation are solved.

Description

Technical Field

[0001] The present invention relates to the field of data analysis, and in particular to a configuration method, device, computer equipment and storage medium for application tags. Background Art

[0002] Under the general trend of digital transformation in China, the digitization of user information is crucial. Deposit label information built based on massive data forms a complete user system. Its labeling, informationization, and visualization features help various types of institutions to carry out personalized business processes, unify internal cognition, and allow business personnel to intuitively understand users and mobilize personnel enthusiasm. In this context, the label automatic generation tool was born, which can help business personnel configure and generate user labels, and also support the creation of new labels on demand for business processes.

[0003] In traditional ways, the generation of user tags faces many difficulties. On the one hand, the flexibility of tag configuration is poor. When business personnel configure basic tags and derived application tags, secondary development is required, which not only increases R&D costs, but also makes the learning cost of business personnel quite high, limiting their flexibility in configuring and using tags according to business needs. On the other hand, in a non-distributed architecture, the efficiency of tag calculation and storage is low, data storage and query are difficult to carry out efficiently, and the time cost increases greatly, which cannot meet the needs of fast and accurate personalized business. Summary of the invention

[0004] In view of this, embodiments of the present invention provide a configuration method, apparatus, computer device and storage medium for application tags to solve the problems faced by traditional user tag generation, such as poor configuration flexibility, high R&D and learning costs, and low computing and storage efficiency.

[0005] In a first aspect, an embodiment of the present invention provides a method for configuring an application tag, the method comprising:

[0006] Obtain the current user's first configuration requirement for the data source connection string;

[0007] Determine a basic tag and an initial data source according to the first configuration requirement, and map the basic tag to each field type in the initial data source to obtain initial configuration information;

[0008] Obtaining a second configuration requirement of the current user for the initial configuration information;

[0009] The basic tags are combined according to the second configuration requirement to obtain an application tag, and the application tag is mapped and configured with each field type in the data source to obtain target configuration information of the application tag.

[0010] Further, determining a basic tag and an initial data source according to the first configuration requirement, and mapping the basic tag with each field type in the initial data source to obtain initial configuration information includes:

[0011] Extracting the data source type and connection information in the first configuration requirement;

[0012] Determine the corresponding database according to the connection information, and test the database through a preset interface to obtain a test result;

[0013] If the test result is that the test passes, initial configuration information is constructed based on the data source type and the database.

[0014] Further, the constructing initial configuration information based on the data source type and the database includes:

[0015] Establish basic tags corresponding to the data source type in the visual interface;

[0016] Traversing multiple initial data tables in the database to obtain an initial data table matching the basic tag, and using the initial data table as an initial data source of the basic tag;

[0017] The basic tags are mapped and configured with each field type in the initial data source to obtain initial configuration information.

[0018] Furthermore, the obtaining of the second configuration requirement of the current user for the initial configuration information includes:

[0019] Detecting a click operation of the current user on the visual interface;

[0020] Determine the first basic tag and the second basic tag according to the click operation, and obtain the calculation strategy of the current user input;

[0021] A second configuration requirement is constructed based on the first basic tag, the second basic tag, and the operation strategy.

[0022] Further, the basic tags are combined according to the second configuration requirement to obtain application tags, and the application tags are mapped and configured with each field type in the data source to obtain target configuration information of the application tags, including:

[0023] Generate an application tag based on the first basic tag and the second basic tag;

[0024] Constructing a data query instruction according to the operation strategy, the first basic tag, and the second basic tag;

[0025] Using the data query instruction, perform a query operation in a first data source corresponding to the first basic tag and a second data source corresponding to the second basic tag to obtain a target data set, and use the target data set as a target data source for the application tag;

[0026] The application tag is mapped and configured with each field type in the target data source to obtain target configuration information.

[0027] Furthermore, the method further comprises:

[0028] Obtaining a third configuration requirement of the current user for the target configuration information;

[0029] The application tag and / or basic tag are combined according to the third configuration requirement to obtain a derived tag, and the derived tag is mapped and configured with each field type in the data source to obtain target configuration information of the derived tag.

[0030] Furthermore, after mapping and configuring the application tag with each field type in the data source to obtain target configuration information of the application tag, the method further includes:

[0031] Detect the tag value currently entered by the user and the triggered application tags and / or derived tags;

[0032] Filling the tag value into the data query instruction corresponding to the application tag and / or the derived tag to obtain the filled data query instruction;

[0033] Filtering from the data sources corresponding to the application tags and / or derived tags according to the data query instruction to obtain a list of business personnel;

[0034] Detect whether the current business status reaches the trigger state, and when the trigger state is reached, send the business personnel list to the corresponding business channel.

[0035] In a second aspect, an embodiment of the present invention provides a device for configuring an application tag, the device comprising:

[0036] A first acquisition module, used to acquire a first configuration requirement of the current user for a data source connection string;

[0037] A determination module, configured to determine a basic tag and an initial data source according to the first configuration requirement, and map the basic tag with each field type in the initial data source to obtain initial configuration information;

[0038] A second acquisition module, used to acquire a second configuration requirement of the current user for the initial configuration information;

[0039] A combination module is used to combine the basic tags according to the second configuration requirement to obtain an application tag, and map the application tag with each field type in the data source to obtain target configuration information of the application tag.

[0040] In a third aspect, an embodiment of the present invention provides a computer device, comprising: a memory and a processor, the memory and the processor being communicatively connected to each other, the memory storing computer instructions, and the processor executing the method of the first aspect or any corresponding embodiment thereof by executing the computer instructions.

[0041] In a fourth aspect, an embodiment of the present invention provides a computer-readable storage medium having computer instructions stored thereon, the computer instructions being used to enable a computer to execute the method of the first aspect or any corresponding embodiment thereof.

[0042] The method provided in the embodiment of the present application has the following beneficial effects:

[0043] The method provided in the embodiment of the present application provides a clear guide for the subsequent process by obtaining the user's initial requirements for the data source connection, ensuring that the configuration fits the user's actual needs and avoiding blind operations. According to the first configuration requirement, the basic label and the initial data source are clarified, and the initial configuration information is obtained after field mapping, and the association between the basic data and the label is established, laying the foundation for subsequent label generation. Based on the initial configuration information, further user requirements are collected, and the basic label and operation strategy are determined by the user's operation on the visual interface, so that the label configuration is more targeted and flexible. According to the second configuration requirement, the basic label is combined to generate an application label, and the target configuration information is obtained by mapping with the data source field to meet the requirements for labels in diversified business scenarios. In addition, a way to further personalized configuration is provided, and derivative labels are obtained by combining application labels, enriching the label system, and improving the system's support for complex businesses. According to the user's combined requirements for application labels and derivative labels, the screening conditions are determined, and a list of business personnel is screened out to provide personnel basis for business activities. Automatically detect the business status, and send the list of business personnel to the corresponding business channel in time when the trigger condition is met, so as to realize the automation and efficient execution of business processes. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] In order to more clearly illustrate the specific implementation methods of the present invention or the technical solutions in the prior art, the drawings required for use in the specific implementation methods or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are some implementation methods of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0045] Figure 1is a flowchart of a method for configuring an application tag according to an embodiment of the present invention;

[0046] Figure 2 is a schematic diagram of a data source configuration interface according to an embodiment of the present invention;

[0047] Figure 3 is a schematic diagram of a label configuration interface according to an embodiment of the present invention;

[0048] Figure 4 is a flowchart of label configuration and processing according to an embodiment of the present invention;

[0049] Figure 5 is a structural block diagram of a device for configuring application tags according to an embodiment of the present invention;

[0050] Figure 6 It is a schematic diagram of the hardware structure of a computer device according to an embodiment of the present invention. DETAILED DESCRIPTION

[0051] In order to make the purpose, technical solution and advantages of the embodiments of the present invention clearer, the technical solution in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of the present invention.

[0052] According to an embodiment of the present invention, a configuration method, apparatus, computer device and storage medium for application tags are provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0053] In this embodiment, a method for configuring an application tag is provided. Figure 1 is a flow chart of a method for configuring an application tag according to an embodiment of the present invention. Figure 1 As shown, the process includes the following steps:

[0054] Step S11, obtaining the first configuration requirement of the current user for the data source connection string.

[0055] In the embodiment of the present application, the purpose of obtaining the first configuration requirement is to collect the user's specific configuration requirements for the data source connection string, which are the basis for subsequent operations such as data source determination and basic label configuration. The user expresses the relevant information of the data source he wants to connect to in a specific way (such as visual interface input, etc.), and the system captures this information so that it can be processed accordingly according to these requirements, such as determining the database type to be connected, the parameters required for the connection, etc., thereby laying the foundation for generating accurate basic labels and the construction of the subsequent label system.

[0056] Step S12: determine the basic tag and the initial data source according to the first configuration requirement, and map the basic tag with each field type in the initial data source to obtain initial configuration information.

[0057] In the embodiment of the present application, step S12 includes the following steps A1-A3:

[0058] Step A1: extract the data source type and connection information in the first configuration requirement.

[0059] Specifically, after obtaining the first configuration requirement of the current user for the data source connection string, the configuration requirement input by the user is parsed. The purpose is to accurately separate the data source type (for example, relational data source, distributed data source or file data source, and specific database types such as MySQL, Hive, etc.) and connection information (such as database IP, account, password, etc., necessary parameters for establishing database connection) from the overall configuration requirements given by the user. The extracted information is the basis for subsequent operations such as determining the database, establishing the connection, and performing label configuration.

[0060] When extracting data source types and connection information, record the extraction time, specific values ​​of the extracted data source types, and various parameter values ​​of the connection information. When format errors or abnormal data are encountered during the extraction process, record the specific circumstances of the abnormality, such as incorrect data source type format, incomplete IP address, etc. These records can be used for subsequent troubleshooting of configuration problems.

[0061] Step A2, determining the corresponding database according to the connection information, and testing the database through a preset interface to obtain a test result.

[0062] Specifically, after obtaining the connection information, the system locates the corresponding database based on this information. For example, the target database server is found based on the database IP, port and other information. Then, the database is tested for connection operation through the preset interface (such as the JDBC corresponding API). The purpose of the connection test is to verify whether the provided account, password and other connection information is accurate and whether the connection to the target database can be successfully established. Only when the test passes can it be guaranteed that data can be obtained from the database for operations such as label configuration. If the test fails, the user is required to recheck and modify the connection information. The test results will serve as an important basis for whether to continue to build the initial configuration information.

[0063] When testing the connection to the database, in addition to recording the test results (success or failure), you can also record the number of attempts for each test connection, the timestamp of each attempt, and the specific error information returned during the test (such as the specific reason why the database rejected the connection, etc.). In addition, you can also record the time consumed by the test connection. This information helps to analyze the problem more accurately when the connection fails, such as determining whether it is a network delay that causes a connection timeout or an account and password error, and can provide data support for optimizing the database connection test mechanism.

[0064] As an example, Figure 2 As shown, an interface related to data source configuration is displayed. Among them, data source classification includes relational, big data, MPP and other categories, which can be used to distinguish different types of data sources; data source types include ORACLE, TEANSWAPP, SQLSERVER, etc., which clarify the specific database type; connection status includes connection success, connection failure, successful save and other states, which are used to display the connection status of the data source. In the list below the interface, detailed information of the data source is recorded, such as the data source with serial number 1, its data source code is DS_0001, the data source name is local database, the application number is Abcd, the database type is MYSQL, the service / IP address is Dafewbvfu, the connection status is successful, and operation options such as modification, deletion, and testing are provided.

[0065] This interface can be used as a visual presentation example of the data source configuration-related operations in the above steps. For example, after extracting the data source type and connection information, they can be displayed and managed in this interface; the test connection results of the database can also be reflected in the connection status; the constructed initial configuration information can also be associated with the data source information in the interface.

[0066] Step A3: If the test result is that the test passes, initial configuration information is constructed based on the data source type and the database.

[0067] Specifically, when the database test connection is successful (i.e., the test result is a passed test), the initial configuration information is constructed based on the determined data source type (such as relational, distributed, or file data source and its specific type) and the successfully connected database. The acquired connection information and database resources are converted into initial configuration information that can be used for subsequent label configuration, providing the necessary data structure and mapping relationship basis for subsequent operations such as generating basic labels and applying labels. Subsequent further refinement of the construction of the initial configuration information includes establishing basic labels, determining the initial data source, and completing field type mapping.

[0068] The method provided in the embodiment of the present application can accurately identify the characteristics and connection requirements of the data source by extracting the data source type and connection information in the first configuration requirement, providing a clear basis for subsequent operations. Determine the corresponding database and test it according to the connection information, and discover database connection problems in advance, ensuring that subsequent configuration work is based on a stable and reliable data source, thereby improving the stability of the system. After the test passes, the initial configuration information is constructed based on the data source type and database, laying the foundation for subsequent label configuration.

[0069] As an example, Figure 3 As shown, the tag configuration interface contains multiple mandatory and optional items, among which the tag name is required to be within 20 characters and is used to define the name of the tag. The tag category is a business tag, which clarifies the category to which the tag belongs. The tag type is a basic tag, which specifies the type of the tag. The associated data table field is CUST_ABCD, indicating the field in the data table associated with the tag. The result value type, tag code value category, and tag description are empty and can be filled in by the current user according to the actual situation. They are used to describe the type of the tag result value, the category of the tag code value, and the detailed description of the tag.

[0070] This interface can be used as a visual example of tag configuration operations after the initial configuration information is built. After the initial configuration information is built, based on the connected database and data source type, basic tags and other operations can be established in this interface to associate tags with database table fields, etc., which is a visual reflection of subsequent tag configuration work.

[0071] In the embodiment of the present application, initial configuration information is constructed based on the data source type and the database, including steps A31-A33:

[0072] Step A31, creating a basic tag corresponding to the data source type in the visual interface.

[0073] Specifically, after the database test connection is passed, the corresponding basic tags are created in the visual operation interface based on the data source type. For example, if the data source type is MySQL in the relational database, then in the visual interface, according to the established rules and formats, basic tags that can characterize the relevant attributes or business dimensions of the data source are established, such as "age", "gender" and other basic tags. These basic tags are the basic elements for the subsequent construction of the tag system, and they provide clear identification and classification basis for extracting and organizing data from the data source.

[0074] Step A32, traverse multiple initial data tables in the database, obtain an initial data table that matches the basic tag, and use the initial data table as the initial data source of the basic tag.

[0075] Specifically, on the basis of the established basic tags, the multiple initial data tables stored in the database are checked and analyzed one by one. By presetting matching rules (such as matching of field names, data meanings, etc.), the initial data tables corresponding to each basic tag are found. For example, if there is a basic tag called "age", the system will search for a table containing age-related data in many tables in the database, and identify it as the initial data source for the "age" basic tag. The purpose of this is to accurately associate each basic tag with its corresponding data storage location, ensuring that data can be obtained from the correct data table to generate the tag value later.

[0076] Step A33, mapping and configuring the basic tags with various field types in the initial data source to obtain initial configuration information.

[0077] Specifically, through the visualization page, the basic tags and data sources are mapped and configured, including the tag name, category, associated fields, etc., so as to automatically generate basic tags. The basic tag generation process is as follows:

[0078] First, the data is processed through the big data platform to obtain a large wide table of basic labels, and then the data is transferred to the corresponding relational database through sqoop. Then, the basic labels are matched one by one with the fields of the large wide table of basic labels using the front-end visual interface, and then the query statements corresponding to the basic labels are generated. Finally, the corresponding basic label values ​​are obtained through flink calculation. Among them, Flink is a distributed stream processing and batch processing framework. After receiving the query statement (sql statement) corresponding to the basic label, Flink will start processing according to its internal execution mechanism.

[0079] The first step is to parse the basic tag sql statement and convert it into an executable task graph. This task graph clarifies the data processing flow, including data reading, conversion, and output operations. For example, if the basic tag sql contains an age field, Flink will determine the operation of reading age data from the relational database and use it as a node in the task graph.

[0080] The second step is task scheduling. Flink will allocate tasks in the cluster based on the task graph and distribute tasks to multiple nodes in the cluster for parallel execution. For example, when processing age data, multiple nodes may read and process different parts of the age data at the same time, thereby speeding up the overall calculation speed.

[0081] The third step is data processing. Flink can convert the read data according to the definition and requirements of the basic tags. For fields with code values, Flink can perform code value mapping operations. For example, if the age field in the large wide table has a specific code value range mapping relationship, Flink can convert the original code value to the corresponding target value based on these relationships. At the same time, Flink can also perform operations such as field type modification to ensure that the data meets the requirements of the basic tags.

[0082] The fourth step is output storage. Flink outputs the basic label values ​​obtained after processing and stores them in ElasticSearch. In this process, Flink ensures the accuracy and consistency of the data, and provides reliable basic data support for subsequent application labels, generation of derived labels, and operations such as business labels.

[0083] In summary, the basic tag essentially maps the fields of the large wide table generated by ETL one by one. If there is a code value, the corresponding data is mapped to the code value. That is, the MySQL table data is input into ElasticSearch, and only one layer of code value mapping and field type modification is performed. For example, the age field in the large wide table corresponds to the basic tag (age). The basic tag will not be applied to business personnel, but is only used to generate application tags and derived tags, and the latter two can be used to screen business personnel. Through such a mapping configuration process, the initial configuration information is finally obtained.

[0084] The method provided in the embodiment of the present application establishes basic labels corresponding to data source types in a visual interface, so that business personnel can operate intuitively and conveniently, reducing learning costs and improving work efficiency; traverses the initial data table in the database, and finds the data table matching the basic label as the initial data source, ensuring the correlation between the basic label and the actual data, making the label more targeted; maps and configures the basic label with the field type in the initial data source, and clarifies the correspondence between the data and the label. The obtained initial configuration information can provide an accurate and reliable basis for the generation of subsequent application labels, thereby improving the accuracy and effectiveness of the entire label configuration process.

[0085] Step S13: obtaining the second configuration requirement of the current user for the initial configuration information.

[0086] In the embodiment of the present application, step S13 includes the following steps B1-B3:

[0087] Step B1, detecting a click operation of the current user on the visual interface.

[0088] Specifically, in the design of the visual interface, in order to achieve interaction with the user, the system will deploy a series of interaction detection mechanisms. When the user uses a mouse, touchpad or other input device to interact with the visual interface, the system can monitor these operations in real time. Specifically, when the user moves the cursor to a specific element in the visual interface (such as a basic label icon, an operation button, a configuration area, etc.) and clicks, the system will immediately capture the click event. This detection process includes obtaining multiple information such as the precise location where the click occurred, the time of the click, and the type of device that triggered the click. For example, if the user clicks the "age" label in the basic label display area, the system will not only record the click event, but also the specific coordinate location of the click in the area, the timestamp of the click time accurate to the millisecond level, and the device information such as whether the click was made by clicking the left mouse button or touching the screen. This rich information will provide a comprehensive and detailed data foundation for the subsequent steps to analyze user intentions.

[0089] Step B2, determining the first basic tag and the second basic tag according to the click operation, and obtaining the calculation strategy currently input by the user.

[0090] Specifically, first determine the basic label clicked by the user based on the location of the click event and the definition of the relevant visualization element. If the user clicks on two different basic labels in the visualization interface in sequence, the label clicked first is set as the first basic label, and the label clicked later is set as the second basic label. For example, if the user first clicks on the "age" label and then clicks on the "consumption frequency" label, "age" is the first basic label and "consumption frequency" is the second basic label.

[0091] At the same time, in order to achieve flexible combination and processing of basic tags, the system also needs to obtain the operation strategy that the user expects to adopt. In the visual interface, multiple ways are provided for users to enter the operation strategy. It can be through a drop-down menu, from which users select logical operation options such as "and", "or", "not", etc.; or it can be entered in a specific input box. Numerical operation expressions, such as "addition", "subtraction", "multiplication", "division" and other mathematical operations. In addition, more complex logical combinations can also be supported, such as nested operations such as "and first, then not". The operation strategy entered by the user is obtained in real time, and it is parsed and verified. If the operation strategy entered by the user does not meet the preset rules of the system (such as syntax errors, unsupported operation symbols, etc.), prompt information will be given in time to guide the user to make corrections.

[0092] Step B3, constructing a second configuration requirement based on the first basic tag, the second basic tag and the calculation strategy.

[0093] Specifically, based on the first two steps, the determined first basic label, second basic label and the obtained operation strategy are integrated. According to the established rules and formats, this information is organized into a complete second configuration requirement. This configuration requirement clarifies the specific operations and combinations that the user wants to perform on the basic labels, such as "combining the first basic label (age) and the second basic label (gender) through an 'and' operation", which provides accurate guidance for subsequent operations such as generating application labels according to the configuration requirement.

[0094] The method provided in the embodiment of the present application detects the current user's click operation on the visual interface, captures the user's interactive intention in an intuitive manner that conforms to the user's operating habits, can improve the user experience, and ensure that the system accurately perceives the starting point of the user's needs. The first basic label and the second basic label are determined according to the click operation, and the operation strategy input by the user is obtained, so that the system can accurately identify the basic labels and combination rules that the user wants to combine, which provides key elements for generating application labels that meet specific business needs, and enhances the flexibility and pertinence of label configuration. The second configuration requirement is constructed based on the first basic label, the second basic label, and the operation strategy, and the user's operation and input are integrated into clear configuration instructions, providing a clear direction for the generation of subsequent application labels, improving the efficiency and accuracy of the entire label configuration process, and effectively solving the problem of poor flexibility of label configuration under traditional methods.

[0095] Step S14, combining the basic tags according to the second configuration requirement to obtain an application tag, and mapping the application tag with each field type in the data source to obtain target configuration information of the application tag.

[0096] In the embodiment of the present application, step S14 includes the following steps C1-C4:

[0097] Step C1: Generate an application tag based on the first basic tag and the second basic tag.

[0098] Specifically, based on the business meaning and data features represented by the basic tags, combined with the tag combination principle of the visual interface design, the first basic tag and the second basic tag are merged. For example, if the first basic tag is "age over 30 years old" and the second basic tag is "business credit limit over 5000 in the past three months", a new application tag is generated through specific combination logic, such as "users over 30 years old and business credit limit over 5000 in the past three months".

[0099] Step C2, constructing a data query instruction according to the operation strategy, the first basic tag and the second basic tag.

[0100] Specifically, first, analyze the operation strategy, such as logical operations or digital operation rules such as "and", "or", and "not". Then, combine the data source structure and data characteristics corresponding to the first basic label and the second basic label to convert the operation strategy into a specific data query statement. Taking the "and" operation as an example, if the first basic label corresponds to the "age" field in the data source table A, and the second basic label corresponds to the "business limit" field in the data source table B, the constructed data query instruction can be: "SELECT*FROM tableAJOIN tableBON tableA.UserID=tableB.UserIDWHERE tableA.Age>30AND tableB.Business limit>5000". This query instruction specifies which data sources (tableA and tableB) to obtain data from, based on what association conditions (same ID) and screening conditions (age and consumption amount restrictions), to ensure that subsequent query operations can accurately extract data related to the application labels.

[0101] Step C3, using the data query instruction to perform a query operation in the first data source corresponding to the first basic tag and the second data source corresponding to the second basic tag, to obtain a target data set, and to use the target data set as the target data source for the application tag.

[0102] Specifically, the data source can be a relational database, a distributed database, or a file data source. According to the type and characteristics of the data source, the corresponding database connection and query technology are used to execute the query. For example, for a relational database, you can use JDBC to connect and execute SQL queries; for a distributed database, you can use a specific distributed query framework. After the query is executed, the data records that meet the query conditions are obtained from the data source, and these records constitute the target data set. This target data set reflects the group data characteristics defined by the application tag, so it is used as the target data source of the application tag, providing accurate data support for the subsequent determination of the specific value and application of the application tag.

[0103] Step C4, mapping and configuring the application tag with each field type in the target data source to obtain target configuration information.

[0104] Specifically, analyze each field type in the target data source one by one, such as numeric type, character type, date type, etc., and correspond them to each attribute or data requirement of the application tag. For example, if there is a "business time" field of date type in the target data source, and the application tag needs to perform time dimension analysis based on this field, then the system will map the "business time analysis" attribute of the application tag with the "business time" field. Through this mapping configuration, the target configuration information is generated, which clarifies the detailed data association relationship between the application tag and the target data source, ensuring that in subsequent business applications, the application tag can accurately obtain and process data from the target data source.

[0105] The method provided in the embodiment of the present application generates an application tag based on the first and second basic tags, realizes a flexible combination of basic tags, and meets the customized needs of tags in diversified business scenarios. Constructing data query instructions based on the operation strategy, the first and second basic tags, provides clear query rules for accurately acquiring target data, and ensures the accuracy of subsequent query operations. Query instructions are used to execute queries in the corresponding data source, and the target data set is obtained and merged as the target data source for the application tag, ensuring that the application tag has reliable and relevant data support. The application tag is configured with the field type of the target data source to obtain the target configuration information, and the association between the application tag and the actual data is established, so that the configured application tag can accurately reflect the characteristics of the business data, providing strong support for personalized business activities.

[0106] In the embodiment of the present application, the method further includes the following steps D1-D2:

[0107] Step D1, obtaining the third configuration requirement of the current user for the target configuration information.

[0108] Specifically, the interactive portal allows users to propose more in-depth and personalized configuration requirements based on the existing target configuration information. Users may want to optimize the configured label system again based on changes in business scenarios, new data analysis directions, or business strategy adjustments. For example, users find that the previously configured application labels need to be combined with the specific attributes of some basic labels in actual use to more accurately filter groups. These new requirements entered by users are received through a visual interface, input box, or other interactive methods, and organized into a third configuration requirement that the system can recognize. This requirement includes the user's intention to adjust the existing label configuration, and provides clear direction guidance for the subsequent generation of derivative labels.

[0109] Step D2, combining application tags and / or basic tags according to the third configuration requirement to obtain derived tags, and mapping and configuring the derived tags with various field types in the data source to obtain configuration information of the derived tags.

[0110] Specifically, according to the third configuration requirement, the application tags and / or basic tags involved are analyzed, and these tags are combined according to the combination logic in the requirement. For example, if the user requirement is to combine a certain application tag "high-value user (generated based on the combination of business quota and business frequency)" with the basic tag "age", a new derivative tag is generated according to the preset combination rule (such as "high-value user and age greater than 40 years old").

[0111] After generating a derived tag, in order to enable the tag to accurately associate and use the data in the data source, the derived tag can be mapped and configured with each field type in the data source. This process is similar to the mapping configuration when generating the application tag previously. By analyzing the structure and field characteristics of the data source, the various attributes of the derived tag are matched with the corresponding data source fields. For example, if the derived tag involves a logical combination of age and business limit, it is mapped with the corresponding "age" field and "business limit" field in the data source to clarify the corresponding relationship of the data, thereby obtaining the configuration information of the derived tag. This configuration information ensures that the derived tag can accurately obtain data from the data source in subsequent business applications such as personnel screening and business activities.

[0112] As an example, Figure 4 As shown in the figure, the flowchart of label configuration and processing is as follows: after the process starts, the label data source configuration operation is performed through the WEB page to determine the initial data source corresponding to the basic label; based on this configuration, the basic label is established on the WEB page and stored in ElasticSearch; then the label combination, filtering, and AND, OR, and NOT operations are performed on the WEB page; after these label operations, derived labels and application labels are generated, and Flink calculations can be executed regularly or customized to process the data, and the processing results are stored in ElasticSearch; finally, the generated labels and other data are used to carry out business processes, and the process ends.

[0113] This flowchart shows the entire process from configuring the label data source to generating basic labels, performing label operations, and then generating derived labels and application labels, processing data through Flink calculations and storing them, and finally applying them to business processes. It is a visual presentation example of the label configuration-related operations in the above text, and intuitively reflects the logical relationship and data flow between the steps.

[0114] The method of the embodiment of the present application obtains the user's third configuration requirement for the target configuration information, allowing the user to further refine and adjust the label configuration, so that the system can better respond to changing business needs and enhance flexibility and adaptability. According to the requirements, the combination of application labels is used to obtain derived labels, enrich the label system, and meet the diverse label requirements in complex business scenarios. The derived labels are mapped to the data source fields to obtain configuration information, ensuring that they are accurately associated with the data, improving practicality and effectiveness, and providing stronger support for business development.

[0115] In the embodiment of the present application, after mapping and configuring the application tag with each field type in the data source to obtain the target configuration information of the application tag, the method further includes the following steps E1-E4:

[0116] Step E1, detecting the tag value currently input by the user and the triggered application tag and / or derived tag.

[0117] Specifically, after completing the configuration of application tags and derived tags, users can enter specific tag values ​​according to specific needs in actual business scenarios, and trigger related application tags and / or derived tags. Through the interactive monitoring mechanism of the visual interface, the tag values ​​entered by the user and the triggered tag types are captured in real time. For example, in a business scenario, the user enters a tag value such as "The business amount in the last month is greater than 5,000" in a specific input box, and the application tag "high value" is triggered at the same time. The tag values ​​entered by the user are recorded, and the triggered application tags or derived tags are identified, providing a clear basis for subsequent data processing and operations.

[0118] Step E2, filling the tag value into the data query instruction corresponding to the application tag and / or the derived tag to obtain the filled data query instruction.

[0119] Specifically, first find the corresponding original data query instruction based on the triggered application tag or derived tag. These instructions are constructed when the application tag or derived tag is generated before, and define the rules for obtaining relevant data from the data source. Then, fill the tag value entered by the user into the corresponding position according to the syntax and logic requirements of the instruction. For example, the original data query instruction is "SELECT*FROM data table WHERE [business limit condition] AND [other conditions]", and the user enters "the business limit in the most recent month is greater than 5000", which is converted into a conditional expression that conforms to the instruction syntax and filled into the "[business limit condition]" position to obtain the filled data query instruction "SELECT*FROM data table WHERE the business limit in the most recent month>5000AND[other conditions]". In this way, the filled instruction can accurately filter out data that meets the user's specific requirements from the data source.

[0120] Step E3, filtering from the data sources corresponding to the application tags and / or derived tags according to the data query instruction to obtain a list of business personnel.

[0121] Specifically, after obtaining the filled data query instruction, start to perform the filtering operation in the data source corresponding to the application tag or derived tag. The data source contains rich data information. According to the filled query instruction, the corresponding data processing technology and algorithm are used to traverse and filter the data in the data source. For example, if the data source is a relational database, the filtering is achieved by executing SQL query statements; if it is a distributed data storage, the data is processed with the help of a distributed computing framework. During the screening process, each data record in the data source is judged one by one to see whether it meets the conditions in the query instruction. Only the business personnel information corresponding to the data records that meet the conditions will be extracted, and finally a list of business personnel will be formed. This list accurately locates the target population that meets the user's specific tag value requirements, providing a clear object for subsequent activities.

[0122] Step E4, detecting whether the current business status reaches the trigger state, and when the trigger state is reached, sending the business personnel list to the corresponding business channel.

[0123] Specifically, the various status indicators of the current business are continuously monitored. These indicators can be pre-set time conditions, the occurrence of business events, the reaching of specific data thresholds, etc. For example, the arrival of the set business time, the inventory of a specific product falling to a certain level, and the meeting of certain conditions of a specific market indicator can all be used as trigger conditions. When it is detected that these preset trigger conditions are met, that is, when the business status reaches the trigger state, the subsequent business process is started. At this time, the generated business personnel list is sent to the pre-set corresponding business channels through file transfer, interface call, etc. These business channels include SMS platforms, mobile banking, intelligent customer service, and other channels for direct interaction with personnel. For example, when the business personnel list is sent to the SMS platform, the platform will send customized SMS to the corresponding personnel according to the contact information in the list; when it is sent to mobile banking, a targeted pop-up window will pop up when the personnel log in. In this way, the automated execution of precise business processes is achieved to ensure that the activities reach the target group at the right time.

[0124] The method of the embodiment of the present application can accurately capture the user's business needs and provide a clear direction for subsequent data processing by real-time detecting the tag value input by the current user and the triggered application tag or derivative tag; filling the tag value into the corresponding data query instruction can make the query instruction meet the user's specific requirements and accurately filter the data; filtering from the corresponding data source according to the filled data query instruction can locate the target group that meets the user's tag value requirements, form a list of business personnel, and provide clear objects for business activities; detect whether the current business status reaches the trigger state, and send the list of business personnel to the corresponding business channel when the conditions are met, so as to realize the automated execution of accurate business processes and ensure that business activities reach the target group at the right time.

[0125] In this embodiment, a configuration device for an application tag is also provided, which is used to implement the above-mentioned embodiments and preferred implementation modes, and will not be repeated hereafter. As used below, the term "module" may be a combination of software and / or hardware that implements a predetermined function. Although the devices described in the following embodiments are preferably implemented in software, the implementation in hardware, or a combination of software and hardware, is also possible and conceivable.

[0126] This embodiment provides a configuration device for application tags, such as Figure 5 As shown, including:

[0127] A first acquisition module 51 is used to acquire a first configuration requirement of the current user for a data source connection string;

[0128] A determination module 52 is used to determine a basic tag and an initial data source according to a first configuration requirement, and map the basic tag with each field type in the initial data source to obtain initial configuration information;

[0129] A second acquisition module 53 is used to acquire a second configuration requirement of the current user for the initial configuration information;

[0130] The combination module 54 is used to combine the basic tags according to the second configuration requirement to obtain the application tag, and map the application tag with each field type in the data source to obtain the target configuration information of the application tag.

[0131] In an optional embodiment of the present application, the determination module 52 includes: an extraction submodule and a mapping submodule;

[0132] The extraction submodule is used to extract the data source type and connection information in the first configuration requirement; determine the corresponding database according to the connection information, and test the database through a preset interface to obtain a test result; if the test result is that the test passes, construct initial configuration information based on the data source type and the database.

[0133] The mapping submodule is used to establish basic tags corresponding to the data source type in the visual interface; traverse multiple initial data tables in the database, obtain the initial data table that matches the basic tag, and use the initial data table as the initial data source of the basic tag; map and configure the basic tag with each field type in the initial data source to obtain initial configuration information.

[0134] In an optional embodiment of the present application, the second acquisition module 53 is used to detect the current user's click operation on the visual interface; determine the first basic tag and the second basic tag according to the click operation, and obtain the calculation strategy input by the current user; and construct a second configuration requirement based on the first basic tag, the second basic tag and the calculation strategy.

[0135] In an optional embodiment of the present application, the combination module 54 is used to generate an application tag based on the first basic tag and the second basic tag; construct a data query instruction according to the operation strategy, the first basic tag and the second basic tag; use the data query instruction to perform a query operation in the first data source corresponding to the first basic tag and the second data source corresponding to the second basic tag to obtain a target data set, and use the target data set as the target data source of the application tag; map and configure the application tag with each field type in the target data source to obtain target configuration information.

[0136] In an optional embodiment of the present application, the device also includes: a derivation module, used to obtain the third configuration requirement of the current user for the target configuration information; combine the application tag and / or the basic tag according to the third configuration requirement to obtain a derived tag, and map the derived tag with each field type in the data source to obtain configuration information of the derived tag.

[0137] In an optional embodiment of the present application, the device also includes: a screening module, which is used to detect the tag value input by the current user and the triggered application tag and / or derivative tag; fill the tag value into the data query instruction corresponding to the application tag and / or derivative tag to obtain the filled data query instruction; filter from the data source corresponding to the application tag and / or derivative tag according to the data query instruction to obtain a list of business personnel; detect whether the current business status reaches the trigger state, and when the trigger state is reached, send the list of business personnel to the corresponding business channel.

[0138] See also Figure 6 , Figure 6 is a schematic diagram of the structure of a computer device provided by an optional embodiment of the present invention, such as Figure 6As shown, the computer device includes: one or more processors 10, a memory 20, and interfaces for connecting various components, including high-speed interfaces and low-speed interfaces. Various components are connected to each other using different buses for communication, and can be installed on a common mainboard or installed in other ways as needed. The processor can process the instructions executed in the computer device, including instructions stored in or on the memory to display the graphical information of the GUI on an external input / output device (such as, a display device coupled to the interface). In some optional embodiments, if necessary, multiple processors and / or multiple buses can be used together with multiple memories and multiple memories. Similarly, multiple computer devices can be connected, and each device provides some necessary operations (for example, as a server array, a group of blade servers, or a multi-processor system).

[0139] The processor 10 may be a central processing unit, a network processor or a combination thereof. The processor 10 may further include a hardware chip. The hardware chip may be a dedicated integrated circuit, a programmable logic device or a combination thereof. The programmable logic device may be a complex programmable logic device, a field programmable gate array, a general purpose array logic or any combination thereof.

[0140] The memory 20 stores instructions executable by at least one processor 10, so that at least one processor 10 executes the method shown in the above embodiment.

[0141] The memory 20 may include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application required for at least one function; the data storage area may store data created by the use of a computer device based on the presentation of a small program landing page, etc. In addition, the memory 20 may include a high-speed random access memory, and may also include a non-transient memory, such as at least one disk storage device, a flash memory device, or other non-transient solid-state storage device. In some optional embodiments, the memory 20 may optionally include a memory remotely arranged relative to the processor 10, and these remote memories may be connected to the computer device via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0142] The memory 20 may include a volatile memory, such as a random access memory; the memory may also include a non-volatile memory, such as a flash memory, a hard disk or a solid state drive; the memory 20 may also include a combination of the above types of memory.

[0143] The computer device further comprises a communication interface 30 for the computer device to communicate with other devices or a communication network.

[0144] The embodiment of the present invention also provides a computer-readable storage medium. The method according to the embodiment of the present invention can be implemented in hardware, firmware, or can be implemented as a computer code that can be recorded in a storage medium, or can be implemented as a computer code that is originally stored in a remote storage medium or a non-temporary machine-readable storage medium and will be stored in a local storage medium through a network download, so that the method described herein can be stored in such software processing on a storage medium using a general-purpose computer, a dedicated processor, or programmable or dedicated hardware. Among them, the storage medium can be a magnetic disk, an optical disk, a read-only storage memory, a random access memory, a flash memory, a hard disk or a solid-state hard disk, etc.; further, the storage medium can also include a combination of the above types of memories. It can be understood that a computer, a processor, a microprocessor controller, or programmable hardware includes a storage component that can store or receive software or computer code. When the software or computer code is accessed and executed by a computer, a processor, or hardware, the method shown in the above embodiment is implemented.

[0145] Although the embodiments of the present invention have been described in conjunction with the accompanying drawings, those skilled in the art may make various modifications and variations without departing from the spirit and scope of the present invention, and such modifications and variations are all within the scope defined by the appended claims.

Claims

1. A method for configuring an application tag, characterized in that: The method comprises: Obtain the current user's first configuration requirement for the data source connection string; Determine a basic tag and an initial data source according to the first configuration requirement, and map the basic tag to each field type in the initial data source to obtain initial configuration information; Obtaining a second configuration requirement of the current user for the initial configuration information; The basic tags are combined according to the second configuration requirement to obtain an application tag, and the application tag is mapped and configured with each field type in the data source to obtain target configuration information of the application tag.

2. The method according to claim 1, characterized in that The determining of the basic tag and the initial data source according to the first configuration requirement, and mapping the basic tag with each field type in the initial data source to obtain the initial configuration information includes: Extracting the data source type and connection information in the first configuration requirement; Determine the corresponding database according to the connection information, and test the database through a preset interface to obtain a test result; If the test result is that the test passes, initial configuration information is constructed based on the data source type and the database.

3. The method according to claim 2, characterized in that The constructing initial configuration information based on the data source type and the database includes: Establish basic tags corresponding to the data source type in the visual interface; Traversing multiple initial data tables in the database to obtain an initial data table matching the basic tag, and using the initial data table as an initial data source of the basic tag; The basic tags are mapped and configured with each field type in the initial data source to obtain initial configuration information.

4. The method according to claim 3, characterized in that The obtaining of the second configuration requirement of the current user for the initial configuration information includes: Detecting a click operation of the current user on the visual interface; Determine the first basic tag and the second basic tag according to the click operation, and obtain the calculation strategy of the current user input; A second configuration requirement is constructed based on the first basic tag, the second basic tag, and the operation strategy.

5. The method according to claim 4, characterized in that The combining of the basic tags according to the second configuration requirement to obtain an application tag, and mapping and configuring the application tag with each field type in the data source to obtain target configuration information of the application tag includes: Generate an application tag based on the first basic tag and the second basic tag; Constructing a data query instruction according to the operation strategy, the first basic tag, and the second basic tag; Using the data query instruction, perform a query operation in a first data source corresponding to the first basic tag and a second data source corresponding to the second basic tag to obtain a target data set, and use the target data set as a target data source for the application tag; The application tag is mapped and configured with each field type in the target data source to obtain target configuration information.

6. The method according to claim 1, characterized in that The method further comprises: Obtaining a third configuration requirement of the current user for the target configuration information; The application tag and / or basic tag are combined according to the third configuration requirement to obtain a derived tag, and the derived tag is mapped and configured with each field type in the data source to obtain target configuration information of the derived tag.

7. The method according to claim 1, characterized in that After mapping and configuring the application tag with each field type in the data source to obtain target configuration information of the application tag, the method further includes: Detect the tag value currently entered by the user and the triggered application tags and / or derived tags; Filling the tag value into the data query instruction corresponding to the application tag and / or the derived tag to obtain the filled data query instruction; Filtering from the data sources corresponding to the application tags and / or derived tags according to the data query instruction to obtain a list of business personnel; Detect whether the current business status reaches the trigger state, and when the trigger state is reached, send the business personnel list to the corresponding business channel.

8. A device for configuring an application tag, characterized in that: The device comprises: A first acquisition module, used to acquire a first configuration requirement of the current user for a data source connection string; A determination module, configured to determine a basic tag and an initial data source according to the first configuration requirement, and map the basic tag with each field type in the initial data source to obtain initial configuration information; A second acquisition module, used to acquire a second configuration requirement of the current user for the initial configuration information; A combination module is used to combine the basic tags according to the second configuration requirement to obtain an application tag, and map the application tag with each field type in the data source to obtain target configuration information of the application tag.

9. A computer device, characterized in that: include: A memory and a processor, wherein the memory and the processor are communicatively connected to each other, the memory stores computer instructions, and the processor executes the method according to any one of claims 1 to 7 by executing the computer instructions.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a computer to execute the method according to any one of claims 1 to 7.

Images