Service field configuration method and device, equipment and storage medium

Abstract

The invention relates to the technical field of data processing, and discloses a service field configuration method, device and equipment and a storage medium, the method comprises the following steps: in response to an association configuration request of a service field, establishing an association relationship between a current service field and a form field, querying matched form field data according to the association relationship based on an asynchronous thread, and configuring the form field according to the matched form field data. The method comprises the following steps: acquiring form field data, performing value conversion on the form field data according to a business field type to generate business field data, filtering the business field data, and storing a field set which can be stored and is filtered out into a business database to complete business field configuration. According to the method, by dynamically establishing association between the business fields and the form fields and automatically converting the values, flexible support for custom fields is enhanced, various business requirements are met, asynchronous thread processing is utilized, the system response capability and expansibility are improved, business field data are filtered and then stored, effective data can be screened, potential risk data can be eliminated, and the business efficiency is improved. And the data security and accuracy are ensured.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of data processing, and particularly relates to a business field configuration method and device, equipment and a storage medium. BACKGROUND

[0002] In the background of the acceleration of digital transformation, industries have higher requirements for the flexibility and adaptability of business system functions. As a key link in the construction of business systems, the importance of business field configuration is increasingly prominent.

[0003] However, the existing business field configuration method can realize content type business field reuse and content library business field individualization, but lacks flexibility and independence, only supports system controls and business fields, cannot meet the content mapping needs of custom individualized controls or business fields, and does not support multiple control and attribute mapping, which makes it difficult to flexibly configure business fields and generate forms when facing complex and variable business requirements, and limits the expansibility and adaptability of the system. SUMMARY

[0004] The main purpose of the present application is to provide a business field configuration method, device, equipment and storage medium, which aims to solve the technical problem of insufficient flexibility of business field and form field association and data processing when the existing method processes business requests.

[0005] To achieve the above purpose, the present application provides a business field configuration method, which comprises:

[0006] In response to the association configuration request of the business field, the association relationship between the current business field and the form field is established;

[0007] Based on the asynchronous thread, the matching form field data is queried according to the association relationship, and the form field data is value-converted according to the business field type to generate business field data;

[0008] The filtered field set that can be stored is stored in the business database to complete the business field configuration by filtering the business field data.

[0009] In an embodiment, the step of establishing the association relationship between the current business field and the form field in response to the association configuration request of the business field comprises:

[0010] In response to the association configuration request of the business field, it is judged whether the current business field supports form field association by querying the system configuration table to generate an association support result;

[0011] If the association support result is to allow association, a set of associable form types is generated based on a form type list;

[0012] generating a target form type identifier in response to a selection operation of the user on the set of associable form types;

[0013] loading a corresponding form set according to the target form type identifier to generate a set of associable forms;

[0014] filtering form fields in the set of associable forms based on a preset field type matching rule to generate a set of associable fields, and saving the association relationship between the current business field and the form field according to the set of associable fields.

[0015] In an embodiment, the step of filtering form fields in the set of associable forms based on a preset field type matching rule to generate a set of associable fields comprises:

[0016] obtaining a business field type to generate a business field type identifier;

[0017] querying an allowed association type matching the business field type identifier in the preset field type matching rule to generate a set of allowed association types;

[0018] filtering form fields in the set of associable forms whose field types belong to the set of allowed association types to generate the set of associable fields.

[0019] In an embodiment, the step of querying matching form field data according to the association relationship based on an asynchronous thread and converting the form field data into business field data according to the business field type comprises:

[0020] querying matching association records according to the association relationship based on an asynchronous thread to generate a set of target mapping relationships;

[0021] traversing each record in the set of target mapping relationships to extract a business field type and a range configuration to generate a field constraint rule;

[0022] converting a form field data value according to a preset rule to generate a conversion result:

[0023] aggregating conversion results of all records to generate the business field data;

[0024] In the process of generating the business field data, when the queue of asynchronous threads is full, the task of generating the business field data is resubmitted after a preset time of hibernation.

[0025] In an embodiment, the step of converting a form field data value according to a preset rule to generate a conversion result comprises:

[0026] if the form field data value is of a text type, a string of the form field data value is truncated according to a length range to obtain a conversion result;

[0027] If the form field data value is of a numerical type, the data precision of the form field data value is converted according to a precision rule to obtain a conversion result;

[0028] If the form field data value is of a date type, the form field data value is formatted according to a format rule to obtain a conversion result;

[0029] If the form field data value is of an option type, whether the form field data value is within the option code range of the business field is checked to obtain a conversion result;

[0030] If the form field data value is of an attachment type, the form field data value is stored to the attachment corresponding field of the business field to obtain a conversion result.

[0031] In an embodiment, the step of completing the business field configuration by filtering the business field data and storing the filtered set of storable fields to the business database includes:

[0032] Filtering data in the business field data whose field name belongs to an allowed modification field list to generate a set of storable fields, wherein the allowed modification field list is modification restriction rule information queried from a system configuration table according to user information;

[0033] Storing the set of storable fields to the business database.

[0034] In an embodiment, after the step of completing the business field configuration by filtering the business field data and storing the filtered set of storable fields to the business database, the method further includes:

[0035] Based on the storage result of the business field data and historical data, analyzing the use of the business field by a reinforcement learning algorithm and a spatio-temporal graph convolution network to generate a business field use report;

[0036] Generating a recommended field configuration scheme corresponding to the business field use report by a generative adversarial network;

[0037] Based on the received user confirmation or modification operation on the recommended field configuration scheme, adjusting the business field configuration and synchronizing the adjusted configuration information to the business database.

[0038] In addition, to achieve the above-mentioned purpose, the present application also provides a business field configuration device, which comprises:

[0039] A data association module configured to, in response to an association configuration request of a business field, establish an association relationship between the current business field and a form field;

[0040] a data mapping module, configured to query matched form field data according to the association relationship based on an asynchronous thread, and convert the form field data according to a business field type to generate business field data;

[0041] a data storage module, configured to store a filtered field set that can be stored to a business database to complete business field configuration by filtering the business field data.

[0042] In addition, to achieve the above object, the present application further provides a business field configuration device, which comprises a memory, a processor and a computer program stored in the memory and executable on the processor, and the computer program is configured to implement the steps of the business field configuration method as described above.

[0043] In addition, to achieve the above object, the present application further provides a storage medium, which is a computer readable storage medium, and the storage medium stores a computer program, and the computer program is executed by a processor to implement the steps of the business field configuration method as described above.

[0044] In addition, to achieve the above object, the present application further provides a computer program product, which comprises a computer program, and the computer program is executed by a processor to implement the steps of the business field configuration method as described above.

[0045] The technical solution provided by the present application, in response to the association configuration request of the business field, establishes the association relationship between the current business field and the form field, queries the matched form field data according to the association relationship based on an asynchronous thread, converts the form field data according to the business field type to generate business field data, filters the business field data, stores the filtered field set that can be stored to a business database to complete business field configuration. The present application dynamically establishes the association between the business field and the form field and automatically converts the value, enhances the flexible support for the custom field, meets the diverse business requirements, uses the asynchronous thread processing to improve the system response ability and expandability, stores the business field data after filtering, can filter the effective data and exclude the potential risk data, and guarantees the data security and accuracy. BRIEF DESCRIPTION OF DRAWINGS

[0046] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and serve to explain the principles of the present application together with the specification.

[0047] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the accompanying drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced as follows. Obviously, the drawings are only for the purpose of illustrating the embodiments of the present application, and for those of ordinary skill in the art, other drawings can also be obtained without creative labor.

[0048] Figure 1 The flowchart provided for the business field configuration method embodiment one of the present application;

[0049] Figure 2 The flowchart provided for the business field configuration method embodiment two of the present application;

[0050] Figure 3 The flowchart provided for the business field configuration method embodiment three of the present application;

[0051] Figure 4 The flowchart for the association relationship storage process;

[0052] Figure 5 The flowchart for the association field value mapping implementation;

[0053] Figure 6 The module structure diagram of the business field configuration device according to the embodiment of the present application;

[0054] Figure 7 The device structure diagram of the hardware running environment involved in the business field configuration method according to the embodiment of the present application.

[0055] The object implementation, functional features and advantages of the present application will be further described with reference to the accompanying drawings in conjunction with the embodiments. DETAILED DESCRIPTION

[0056] It should be understood that the specific embodiments described herein are only used to explain the technical solutions of the present application, and are not used to limit the present application.

[0057] In order to better understand the technical solutions of the present application, the following will be described in detail in conjunction with the drawings in the specification and specific embodiments.

[0058] Although the existing business field configuration method can realize content type business field multiplexing and content library business field individualization, it is not flexible and independent, only supports system controls and business fields, and cannot meet the content mapping requirements of custom individualized controls or business fields, nor supports multiple control and attribute mapping, resulting in that it is difficult to flexibly configure business fields and generate forms when facing complex and variable business requirements, which limits the expansibility and adaptability of the system.

[0059] Therefore, in order to overcome the above-mentioned defects, the present application provides a solution, which enhances the flexible support for custom fields by dynamically establishing the association between the business field and the form field and automatically converting the value, meets the diverse business requirements, improves the system response capability and expansibility by using asynchronous thread processing, and stores the business field data after filtering, which can filter the effective data and exclude the potential risk data, thereby guaranteeing the data security and accuracy.

[0060] It should be noted that the execution subject of each embodiment of the present application can be a computing service system with data processing, network communication and program running functions, such as an electronic system, a business field configuration system, etc. capable of realizing the above-mentioned functions. Hereinafter, the business field configuration system (hereinafter referred to as "system") is taken as an example to describe each embodiment.

[0061] Based on this, the present application provides a business field configuration method, which is described with reference to Figure 1 , Figure 1 The flowchart of the first embodiment of the business field configuration method of the present application is shown in FIG. 1.

[0062] In this embodiment, the business field configuration method comprises steps S10-S30:

[0063] Step S10, in response to the association configuration request of the business field, the association relationship between the current business field and the form field is established.

[0064] It should be understood that the association configuration request of the business field is usually initiated by the user through interface operation, and the business field to be configured is specified. When the system receives the association configuration request of the business field, the configuration information of the current business field is queried, which is stored in the system configuration table, including the type of the field, whether the association is supported, etc. According to the queried configuration information, it is determined whether the current business field supports the association with the form field. If it is supported, the association relationship between the current business field and the form field is established.

[0065] Step S20, based on the asynchronous thread, the matching form field data is queried according to the association relationship, and the form field data is value-converted according to the business field type to generate the business field data.

[0066] According to the established association relationship, the form field data associated with the business field is queried in the asynchronous thread, which ensures that the data query will not block the main thread. After the form field data is queried, the value conversion is performed on these data according to the type of the business field, and the data after the value conversion is aggregated to generate the business field data.

[0067] It should be noted that the value conversion refers to converting data in one format or type into data in another format or type according to a preset rule in a data processing process. In the business field configuration method, the value conversion specifically refers to converting the data value of a form field into a data value that meets the requirements of the business field type and constraints, so as to ensure that the data of the form field can be correctly mapped to the business field and meet the requirements of the business logic.

[0068] In step S30, the filtered set of storable fields is stored in the business database by filtering the business field data, so as to complete the business field configuration.

[0069] The business field data is filtered according to a preset rule to filter out field data that meets specific conditions. The preset rule can include modification restrictions of the field, mandatory of the field, and the like. After filtering, the system generates a set of storable fields, which contains all field data that meets the storage conditions. Finally, the system stores the set of storable fields in the business database to complete the configuration of the business field, so as to ensure that only data that meets the business rules is stored.

[0070] As an implementation, the above step S30 in the embodiment can include: filtering data in which the field name belongs to the allowed modification field list from the business field data to generate a set of storable fields, wherein the allowed modification field list is modification restriction rule information queried from the system configuration table according to user information; and storing the set of storable fields in the business database.

[0071] In a specific implementation, the modification restriction rule information is queried from the system configuration table according to user information, and these rules define which fields can be modified under what conditions. Based on these rules, the system generates an allowed modification field list, which contains all field names that are allowed to be modified. Then, the system traverses the business field data and checks whether the field name of each field is in the allowed modification field list. If the field name is in the list, it means that the data of the field can be modified and stored in the database; otherwise, if the field name is not in the list, it means that the data of the field is not allowed to be modified and will be excluded. In this way, the system generates a set of storable fields, which contains all field data that meets the modification restriction rules. Finally, the system stores the set of storable fields in the business database to complete the configuration of the business field.

[0072] It should be noted that the business field configuration method of the present application is applicable to various business scenarios and has wide applicability. For example, in the financial industry, whether it is a bank's transaction system or a securities trading platform, data accuracy and real-time performance are crucial. In a bank's customer relationship management system, it is necessary to flexibly configure business fields such as customer information, account type, transaction records, etc. The present application can quickly respond to and accurately process a large amount of transaction data through asynchronous thread processing and data filtering, meeting the bank's demand for fine management of customer data.

[0073] The present embodiment dynamically establishes the association between the business field and the form field and automatically converts the value, thereby enhancing the flexible support for custom fields, meeting various business needs, using asynchronous thread processing to improve system response capability and expandability, and filtering the business field data before storing it in the database, which can filter valid data and exclude potential risk data to ensure data security and accuracy. In addition, dynamic loading of modification rules generates a list of fields that allow modification, and through a pre-filtering mechanism, only the modifiable fields are stored in the database, blocking illegal field tampering, and solving the contradiction between sensitive data protection and personalized configuration.

[0074] Based on the first embodiment of the present application, in the second embodiment of the present application, the same or similar contents as the above-mentioned first embodiment can refer to the above introduction, and the following will not be repeated. On this basis, please refer to Figure 2 , the step S10 can include steps S101-S105:

[0075] Step S101, in response to the association configuration request of the business field, judging whether the current business field supports the form field association by querying the system configuration table, and generating an association support result.

[0076] It should be understood that when the system receives the association configuration request of the business field, it is necessary to first determine whether the current business field supports association with the form field by querying the system configuration table. The system configuration table stores detailed information of the business field, including field type, whether it supports association, etc. According to the query result, an association support result is generated to determine whether the current business field can be associated. If the query result shows that the current business field supports association with the form field, the next operation is entered; otherwise, the system will prompt the user that the current field does not support association, and terminate the subsequent operation.

[0077] Step S102, if the association support result is allowed to associate, generating a set of associable form types based on the form type list.

[0078] After confirming that the current business field supports association with form fields, a set of associable form types will be generated based on the preset form type list. The form type list contains all available form types in the system, and each form type corresponds to a specific set of form fields. Based on the requirements of the current business field, the system filters out the form types that meet the conditions and forms a set of associable form types. This set provides users with a range of choices, allowing them to select a form type based on their actual needs for subsequent association operations.

[0079] Step S103 : generating a target form type identifier in response to the user's selection operation on the set of associable form types.

[0080] After the user selects a form type from the set of associated form types, the system records the user's selection and generates a target form type identifier, which is a unique identifier of the form type selected by the user and is used to subsequently load a specific form set.

[0081] Step S104: loading a corresponding form set according to the target form type identifier to generate an associable form set.

[0082] According to the target form type identifier, the form collection of the corresponding type is loaded from the database or configuration file. The form collection contains all form instances under the form type. Each form instance contains a set of specific form fields, and the loaded corresponding form collection is then used as an associative form collection.

[0083] Step S105 : Based on a preset field type matching rule, the form fields in the associable form set are screened to generate an associable field set, and the associative relationship between the current business field and the form field is saved according to the associable field set.

[0084] Furthermore, form fields are filtered based on preset field type matching rules. Matching rules define which form fields can be associated with the current business field. For example, a text field can be associated with a text-type business field, and a numeric field can be associated with a numeric-type business field. Based on these rules, the system filters out form fields that meet the conditions, generates a set of associated fields, and then saves the association between the current business field and the form field, completing the field association configuration.

[0085] As an implementation method, the above-mentioned step S105 in this embodiment may include: obtaining the current business field type and generating a business field type identifier; querying the preset field type matching rules for the allowed association types that match the business field type identifier and generating an allowed association type set; filtering the form fields in the associable form set whose field types belong to the allowed association type set and generating the associable field set.

[0086] In a specific implementation, in the business field configuration process, in order to ensure the correct association between the form field and the business field, the system first needs to obtain the type of the current business field, and generate a business field type identifier, and then query the preset field type matching rule to generate an allowed association type set, which contains all form field types that can be associated with the current business field type. Finally, the system filters the form fields in the associated form set, and selects the form fields whose field types belong to the allowed association type set to generate an associated field set.

[0087] The embodiment takes the associated field set generation as the core, supports flexible association of the same business field across multiple forms through a three-level filtering mechanism of dynamically loading form type-form-field, automatically judges the association feasibility based on the system configuration table and the preset rule, solves the defects of the prior art that only supports fixed system form fields, and improves the system expansibility. Moreover, the field type matching rule table is introduced as a filtering engine to ensure the type compatibility of the associated fields, the chain conversion of the business field type identifier-allowed association type set-associated field set is used to avoid invalid association, eliminate mapping errors caused by data type conflicts from the source, and reduce the system exception rate.

[0088] Based on the first embodiment of the application, in the third embodiment of the application, the same or similar contents as the above-mentioned first embodiment can be referred to the above introduction, and the subsequent will not be repeated. On this basis, please refer to Figure 3 , the step S20 can include steps S201-S205:

[0089] Step S201, based on an asynchronous thread, querying the matching association record according to the association relationship, and generating a target mapping relationship set.

[0090] It should be understood that, in the business field configuration method, the system uses an asynchronous thread to process data to improve efficiency and response speed. First, according to the established association relationship between the business field and the form field, the matching association record is queried, which describes the mapping relationship between the form field and the business field in detail, including the type of the field, the associated form ID (unique identifier), the field ID and other information. A target mapping relationship set is generated through these records, which contains all the field mapping relationships that need to be processed.

[0091] Step S202, traversing each record in the target mapping relationship set, extracting the business field type and range configuration, and generating a field constraint rule.

[0092] Further, each record in the target mapping relationship set is traversed to extract the type and range configuration information of the business field from the record, which defines the constraint conditions of the business field, such as whether the type of the field is text, numerical value or date, and the length, precision, format and the like of the field. According to the extracted information, the system generates field constraint rules, which will be used in subsequent data conversion and verification processes.

[0093] In step S203, the form field data value is converted according to a preset rule to generate a conversion result.

[0094] After the field constraint rules are extracted, the system converts the data value of the form field according to the rules. The purpose of the conversion is to adjust the data format and type of the form field to a form matched with the business field.

[0095] As an implementation, the above step S203 in the embodiment can include: if the form field data value is of a text type, a string of the form field data value is truncated according to a length range to obtain a conversion result; if the form field data value is of a numerical value type, the data precision of the form field data value is converted according to a precision rule to obtain a conversion result; if the form field data value is of a date type, the form field data value is formatted according to a format rule to obtain a conversion result; if the form field data value is of an option type, it is verified whether the form field data value is within the option code range of the business field to obtain a conversion result; and if the form field data value is of an attachment type, the form field data value is stored to a corresponding field of the attachment of the business field to obtain a conversion result.

[0096] In a specific implementation, for the form field data value of a text type, a string is truncated according to a set length range, for example, if the length range is 1 to 10 characters, the part of the original text data meeting the length requirement is truncated to obtain a converted result. For the form field data value of a numerical value type, the precision of the data is adjusted according to a predetermined precision rule, for example, if the precision rule is to retain two decimal places, the numerical value is rounded or directly truncated to two decimal places to obtain a converted result.

[0097] For form field data values ​​of date type, they will be formatted according to the formatting rules. For example, "2025-06-25" will be formatted as "June 25, 2025" or "06 / 25 / 2025" or other formats that meet the requirements, and then the conversion result will be obtained. For form field data values ​​of option type, the data value will first be checked to see if it is within the option code range specified by the business field. If it is within the range, it means that the data is valid and can be used as the conversion result; if it is not within the range, corresponding prompts or processing may be required. For form field data values ​​of attachment type, they will be stored in the attachment field corresponding to the business field. Once stored successfully, the conversion process is completed and the conversion result is obtained.

[0098] Step S204: Aggregate the conversion results of all records to generate the business field data.

[0099] After the data values ​​of all form fields have been converted, the scattered conversion results are integrated into a complete business field data set.

[0100] Step S205 : During the process of generating the business field data, when the queue of the asynchronous thread is full, the task of generating the business field data is resubmitted after sleeping for a preset time.

[0101] While processing business field data, the system may encounter a situation where the asynchronous thread queue is full. This is because the asynchronous thread queue has a limited capacity. When the queue reaches its maximum capacity, new tasks cannot be submitted immediately. To prevent task loss or system crashes, the system implements a strategy: when the asynchronous thread queue is full, the system temporarily sleeps for a preset period of time, waiting for space to become available in the queue. The sleep period is a preset value, typically determined based on system performance and the urgency of the task. After the sleep period, the system resubmits the task generating the business field data to ensure successful completion.

[0102] This embodiment uses an asynchronous thread pool to perform value conversion, and a sleep-retry mechanism ensures task reliability in high-concurrency scenarios. It decouples field constraint rules from conversion logic, supports dynamic expansion of conversion strategies, and resolves the issue of synchronous processing blocking the main business. Furthermore, an innovative direct storage strategy is adopted for attachment types, skipping the complex conversion process. For text / numeric / date / option types, interception / precision conversion / formatting / encoding verification are designed separately, covering multiple business scenarios and improving conversion efficiency.

[0103] For easier understanding, refer to Figures 4-5This description is provided for illustrative purposes only and does not limit the business field configuration method of this application. The business field configuration method of this application involves the following modules: form, form type, form field, form field data, business field, field type, and business field data. Forms support both system-preset forms and user-defined forms; form fields and business fields support both system fields and user-defined fields; and business data refers to the data that ultimately resides in the database after the business transaction is completed.

[0104] A complete technical solution may include the following:

[0105] 1. Association between form fields and business fields

[0106] The premise of using this function is that there is an association between form fields and business fields. Figure 4 As shown ( Figure 4 (See the flowchart for storing association relationships.) The association operation between form fields and business fields is performed on the business field. When operating a single business field, all form types are filtered out. After the user selects one, all forms under the changed type are filtered out. After the user selects one form, the form fields that support association with the current type of business field are filtered out. If the selected form has no available fields, the user needs to reselect; if there are matching fields, multiple forms and fields can be selected to ultimately save the association relationship. In addition, using the Add button, the user can continue to add any form under the modified type form, select form fields that can be associated with the current type of business field, and continue the association.

[0107] The specific implementation is as follows:

[0108] (1) When a new business field is added, determine whether the current field supports form field association based on the configuration table data. The configuration table is a system public configuration storage table, which mainly contains fields such as tenant number, root configuration code, parent configuration code, child configuration code, and configuration name. The field types that are currently allowed to be associated or not allowed to be associated are configured in this table;

[0109] (2) If (1) returns yes, query the form type that can be associated with the field. Currently, the dataMap format is cached in the foreground and is fixed to the system's commonly used entry, transfer, and withdrawal type forms;

[0110] (3) Based on the form type list returned by (2), a drop-down menu is displayed in the "Form Type" column on the page, and the user selects the form type.

[0111] (4) After the user selects a single option in the drop-down menu in (3), all forms of this type are queried and displayed in the "Select Form" column on the page;

[0112] (5) After the user selects the single option in (4) by pulling down, the user obtains all fields and their field types in the OA form through the Office Automation (OA) form configuration query interface, compares the types of the current business fields, filters out the OA form fields that can be associated according to the rules of the allowed association between the form field types and the business field types, and displays the fields in the "Associated Fields" column on the page;

[0113] (6) The user can repeat step (5) to continue the field association;

[0114] (7) After the user clicks "Save", the association relationship of the page is saved; specifically, the page parameters include the current tenant number, the business field Key, the group, the type of the form, the form ID, the form field Key, and the type of the form field;

[0115] Table 1: Rules of allowed association between form field types and business field types

[0116]

[0117] Table 2: Persistent association relationship between business fields and form fields

[0118]

[0119] As described above, Table 1 details the association rules between business field types and form field types, for example, a text type business field can be associated with a text, option, numerical value, and date type form field, but cannot be associated with an attachment type form field. Table 2 shows the persistent association relationship between business fields and form fields, which explicitly specifies the corresponding rules of each entity through structured data, including the group identification (GroupId) and ID of the business field, the associated form type and form ID, the target form field and its type ID, and the extended information (such as format or configuration parameters). Example data (such as "Grp001" "Fld001", etc.) materializes an association record, indicating that the business field "Fld001" needs to be mapped to the field "FmFld01" in the form "Fm01", and the field type is "FmFldTyp01", the extended information "YMD" represents the date format requirement, and only the year, month, and day are stored.

[0120] 2. Mapping of form field data to business field data

[0121] When the main business generates transaction data, it completes its main process according to its business rules. In the asynchronous thread, data mapping of the associated fields is performed. Figure 5The flowchart for the association field value mapping implementation is shown: starting from the query association relationship, the system first determines whether the target data exists. If it exists, the association relationship is traversed to locate the business field that needs to be mapped, and the mapping rule of the value is checked to see if it meets the requirements. If it does not meet the requirements, it is re-traversed; if it meets the requirements, the field value is pre-processed (such as format conversion or verification) before being written into the database, and finally overwritten and written into the database. Figure 5 In the processing logic shown, asynchronous thread pool, strategy pattern, MathUtil (math tool class in Java programming), DateUtil (tool library for simplifying date and time processing), etc. are mainly applied. Among them, the asynchronous thread pool parameters include: core thread number 10, maximum thread number 30, allowed idle time 60s, queue capacity 1000, rejection policy is a custom policy, and sleep 300ms. Specifically:

[0122] (1) Take the business main transaction, which contains: transaction form type, form ID, form field and field data;

[0123] (2) According to the tenant number, form type, form ID, query the record in the "association relationship table", filter out the association relationship record containing the form field in the current transaction, wherein the primary key in the association relationship table is: tenant number, business field grouping, Key, form ID and form field ID, and the index uses the primary key index;

[0124] (3) Traverse the mapping relationship in the association relationship table obtained in (2), take the tenant number, business field grouping, and business field Key from the field configuration table on the business side, and take out the field details, mainly the type and range information of the business field;

[0125] Take the value of the form field in the business transaction information, and take the field type and range information of the business field:

[0126] If the type of the business field is text, take the range information of the business word, for example: (0, 50) indicates that the field length is 0 to 50 characters, then before constructing the business field storage information, the data value of the associated form field is string truncated.

[0127] If the type of the business field is numerical, take the range information of the business word, for example: %.2f indicates that 2 decimal places are saved, then before constructing the business field storage information, the data value of the associated form field is converted and precision processed according to the precision conversion function.

[0128] If the type of the business field is date, take the range information of the business word, for example: YMD indicates that only the year, month and day are stored, then before constructing the business field storage information, the data value of the associated form field is date formatted and converted according to the date formatting function.

[0129] If the type of the business field is attachment, and the business field has no range information, the value of the associated form field will be directly stored in the attachment ID field before constructing the business field storage information.

[0130] If the type of the business field is option, option code matching needs to be performed. If it is a single selection type, all option codes and selection names can be listed in the range information of the business field, or the corresponding relationship can be stored in a configuration table. The data value of the form field needs to be determined. If it is a code, it is determined whether it is contained in the code in the range information of the business field. If yes, it is allowed to be mapped into the business library, otherwise it is not mapped into the business library. If it is a multiple selection, the range information of the business field can contain all option IDs, option codes and selection names, or the corresponding relationship can be stored in a configuration table. It is determined whether the data value of the form field is a code. If yes, it is determined whether it is contained in the code in the range information of the business field. If yes, it is allowed to be mapped into the business library, otherwise it is not mapped into the business library.

[0131] It should be noted that in the asynchronous thread, the system first extracts the necessary data from the main business process according to the business rules and the field association relationship. Then, the data is processed by using MathUtil and DateUtil tool classes. That is, in the step of querying the matching form field data based on the association relationship and converting the form field data into business field data according to the business field type based on the asynchronous thread, the field value conversion is performed by the intelligent data processing engine. The processing logic of MathUtil can include: classifying the form field data obtained by querying according to the field type mapping rule recorded in the association relationship, identifying data types such as numerical type, time type and text type; automatically performing cleaning operations on abnormal data, including null value filling, format standardization and illegal character filtering; for numerical type fields, dynamically selecting calculation strategies based on their business type identifiers: enabling Decimal operation for financial type fields, and automatically loading exchange rate conversion coefficients; statistical type fields adopt parallel aggregation algorithm, supporting block calculation and result merging; boundary check is performed before operation, and when it is detected that the value exceeds the preset threshold, the large number operation mode is automatically switched and a warning log is generated.

[0132] In addition, the processing logic of DateUtil can include: parsing the metadata of the time type field, converting UTC time to the target business time zone according to the time zone parameter configured in the association relationship; completing the incomplete time data according to the business rules: expanding the annual data to the first day of the current year, and converting the quarterly data to the end of the period; filtering the time data that exceeds the effective range of the current business cycle through the time window verification mechanism.

[0133] The data processed by mathematical operation and time processing is re-aggregated according to the business field identifier.

[0134] 3. Business data warehousing

[0135] After the field mapping and value processing are completed in step 2, the values of the business fields need to be filtered according to the modification restriction rules before being finally warehoused. In the system, some fields have strong business attributes or uniqueness and are not allowed to be arbitrarily tampered with. Therefore, the allowed modification scenarios for such fields will be maintained in the configuration table. Thus, the following processing will be performed:

[0136] (1) According to the "field association" scenario, the tenant number is used to query the modification restriction rule information in the configuration, which will include the list of fields allowed to be modified under this scenario;

[0137] (2) According to the business fields of the business data, the changeable fields are filtered from the rules;

[0138] (3) The final warehouseable field list is obtained for database operations.

[0139] It can be seen that the above steps achieve significant progress in flexible configuration of business fields, mainly reflected in the improvement of flexibility and independence. Not only does it support the association of system predefined form fields and business attributes, but also allows users to customize the mapping relationship between form fields and business attributes, thus meeting individual needs. Secondly, it supports the use of multiple business forms under the association module, so that a business attribute can be associated with multiple form fields at the same time, which is particularly important in scenarios where multiple forms are needed in a single business type. In addition, the association relationship business logic is processed independently and decoupled from the main business process, which not only does not affect the execution of the main business process, but also improves the flexibility and scalability of the system. Finally, through asynchronous processing of the mapping backfill of the associated field values, the smoothness of user interaction is ensured, thus improving the user experience.

[0140] As an implementation, after the step S30, it can further include: based on the storage result and historical data of the business field data, analyzing the use situation of the business field by a reinforcement learning algorithm and a spatio-temporal graph convolution network, generating a business field use situation report; generating a recommended field configuration scheme corresponding to the business field use situation report through a generative adversarial network; based on the received user confirmation or modification operation on the recommended field configuration scheme, adjusting the business field configuration, and synchronizing the adjusted configuration information to the business database.

[0141] In specific implementation, in order to optimize field configuration and improve the adaptability and efficiency of the system, the system will conduct in-depth analysis based on the storage result and historical data of the business field data. This analysis process combines reinforcement learning algorithm and spatio-temporal graph convolution network to comprehensively evaluate the use situation of the business field.

[0142] It should be noted that the reinforcement learning algorithm learns the optimal strategy through interaction with the environment. In the use case analysis of business fields, the reinforcement learning algorithm can dynamically adjust the analysis strategy to adapt to the changing business needs, that is, according to the multi-dimensional data such as the frequency of use of business fields, the stability of association relationship, the distribution of field values, and the frequency of change of field values, the parameters of the analysis model are constantly adjusted to find the optimal analysis path. In this way, the reinforcement learning algorithm can identify which field configuration performs well in actual use and which needs to be improved.

[0143] The spatio-temporal graph convolutional network is a deep learning model for processing spatio-temporal data. In the use case analysis of business fields, the spatio-temporal graph convolutional network can effectively capture the spatio-temporal relationship between fields. For example, some fields may be frequently used in a certain time period, while others may exhibit different usage patterns in different business processes. The spatio-temporal graph convolutional network can identify the association patterns and time series features between fields by constructing a graph structure between fields. By analyzing these patterns, the system can generate detailed business field usage reports to provide data support for subsequent optimization.

[0144] The results of the reinforcement learning algorithm (such as field usage frequency, association relationship stability, etc.) and the results of the spatio-temporal graph convolutional network (such as association patterns between fields, time series features, etc.) are integrated to generate a business field usage report.

[0145] Further, the system uses a generative adversarial network to generate a recommended field configuration scheme. The generative adversarial network consists of a generator and a discriminator, and through the adversarial training of the two, a high-quality recommended scheme is generated, that is, according to the data in the business field usage report, a recommended field configuration scheme including field type adjustment, field association relationship optimization, and field value range adjustment is generated. The goal of the generator is to generate a configuration scheme that meets the business needs as much as possible, while the discriminator evaluates the generated scheme to determine whether it is reasonable and effective. Through the continuous confrontation and optimization of the generator and the discriminator, the system finally generates a high-quality recommended field configuration scheme.

[0146] The generated recommended field configuration scheme is presented to the user, who can confirm or modify the scheme according to the actual situation. The system dynamically adjusts the business field configuration according to the user's confirmation or modification operation. The adjusted configuration information is synchronized to the business database in real time to ensure the real-time and accuracy of the business system.

[0147] The embodiment performs deep analysis on the storage result of the business field and the historical data by using a reinforcement learning algorithm and a spatio-temporal graph convolution network, generates a detailed business field usage report, dynamically adjusts the analysis strategy by using the reinforcement learning algorithm to adapt to the changes of the business requirements, captures the spatio-temporal relationship between fields by using the spatio-temporal graph convolution network, identifies the usage mode, generates a recommended field configuration scheme by using a generative adversarial network based on the analysis result, and the user can confirm or modify the recommended scheme, the system adjusts the business field configuration according to the adjustment, and synchronizes the adjusted configuration information to the business database, thereby ensuring the real-time performance and accuracy of the system, and improving the flexibility and user satisfaction of the system.

[0148] It should be noted that the above examples are only used for understanding the present application and do not constitute a limitation on the business field configuration method of the present application. More forms of simple transformation based on the technical concept are within the protection scope of the present application.

[0149] The present application also provides a business field configuration device, please refer to Figure 6 , the business field configuration device comprises:

[0150] The data association module 10 is configured to establish an association relationship between the current business field and the form field in response to an association configuration request of the business field.

[0151] The data mapping module 20 is configured to query the matched form field data based on the association relationship and convert the form field data according to the business field type to generate business field data based on an asynchronous thread.

[0152] The data storage module 30 is configured to store the filtered field set that can be stored into the business database to complete the business field configuration by filtering the business field data.

[0153] The business field configuration device provided by the present application adopts the business field configuration method in the above embodiment, and can solve the technical problem of insufficient flexibility of the association between the business field and the form field and the data processing when the existing method processes the business request. Compared with the prior art, the business field configuration device provided by the present application has the same beneficial effects as the business field configuration method provided by the above embodiment, and the other technical features in the business field configuration device are the same as the features disclosed in the above embodiment method, which will not be repeated here.

[0154] The present application provides a business field configuration device, which comprises at least one processor and a memory connected with the at least one processor in communication. The memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform the business field configuration method in the above embodiment one.

[0155] Reference below Figure 7 , which shows a schematic diagram of the structure of a service field configuration device suitable for implementing the embodiments of the present application. The service field configuration device in the embodiments of the present application may include, but is not limited to, mobile terminals such as mobile phones, laptop computers, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Portable Application Devices), PMPs (Portable Media Players), in-vehicle terminals (such as in-vehicle navigation terminals), and fixed terminals such as digital TVs and desktop computers. Figure 7 The service field configuration device shown is merely an example and should not limit the functions and scope of use of the embodiments of the present application.

[0156] like Figure 7 As shown, the service field configuration device may include a processing device 1001 (e.g., a central processing unit, a graphics processing unit, etc.), which can perform various appropriate actions and processes based on programs stored in a read-only memory 1002 or programs loaded from a storage device 1003 into a random access memory 1004. The random access memory 1004 also stores various programs and data required for the operation of the service field configuration device. The processing device 1001, the read-only memory 1002, and the random access memory 1004 are interconnected via a bus 1005. An input / output interface 1006 is also connected to the bus. Typically, the following systems can be connected to the input / output interface 1006: an input device 1007 including, for example, a touch screen, touchpad, keyboard, mouse, image sensor, microphone, accelerometer, gyroscope, etc.; an output device 1008 including, for example, a liquid crystal display (LCD), speaker, vibrator, etc.; a storage device 1003 including, for example, a magnetic tape, hard disk, etc.; and a communication device 1009. The communication device 1009 can allow the service field configuration device to communicate with other devices wirelessly or by wire to exchange data. Although the figure shows a service field configuration device with various systems, it should be understood that it is not required to implement or have all of the systems shown. More or fewer systems can be implemented or have alternatively.

[0157] In particular, according to the embodiments disclosed in the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, the embodiments disclosed in the present application include a computer program product comprising a computer program carried on a computer readable medium, the computer program containing program codes for executing the method shown in the flowchart. In such embodiments, the computer program can be downloaded and installed from a network through a communication device, or installed from the storage device 1003, or installed from the read-only memory 1002. When the computer program is executed by the processing device 1001, the above-mentioned functions defined in the method of the embodiments disclosed in the present application are executed.

[0158] The service field configuration device provided by the present application adopts the service field configuration method in the above-mentioned embodiments, and can solve the technical problem of insufficient flexibility of association of service fields with form fields and data processing when a service request is processed by the existing method. Compared with the prior art, the service field configuration device provided by the present application has the same beneficial effects as the service field configuration method provided by the above-mentioned embodiments, and other technical features in the service field configuration device are the same as the features disclosed in the previous embodiment method, which will not be described here.

[0159] It should be understood that various parts of the present application can be realized by hardware, software, firmware or a combination thereof. In the description of the above-mentioned embodiments, specific features, structures, materials or characteristics can be combined in any one or more embodiments or examples in a suitable manner.

[0160] The above is merely specific embodiments of the present application, but the protection scope of the present application is not limited thereto, and any person skilled in the art can easily think of changes or replacements within the technical scope disclosed in the present application, which should be covered in the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

[0161] The present application provides a computer readable storage medium having stored thereon computer readable program instructions (i.e. computer program) for executing the service field configuration method in the above-mentioned embodiments.

[0162] The computer readable storage medium provided in the application may be, for example, a U disk, but is not limited to an electric, magnetic, optical, electromagnetic, infrared, or semiconductor system or device, or any combination of the above. More specific examples of the computer readable storage medium may include, but are not limited to, an electric connection with one or more conductive wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the embodiment, the computer readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system or device. The program code contained on the computer readable storage medium can be transmitted by any suitable medium, including but not limited to an electric wire, an optical cable, an RF (Radio Frequency), and the like, or any suitable combination of the above.

[0163] The computer readable storage medium described above may be contained in the service field configuration device, or may exist separately without being assembled into the service field configuration device.

[0164] The computer readable storage medium described above carries one or more programs, when the one or more programs are executed by the service field configuration device, the service field configuration device is caused to: in response to an association configuration request of a service field, establish an association relationship between the current service field and a form field, query matched form field data according to the association relationship based on an asynchronous thread, perform value conversion on the form field data according to a service field type to generate service field data, filter the service field data, and store a filtered field set that can be stored into a business database to complete service field configuration.

[0165] Computer program code for carrying out operations of the present application can be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C++ or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code can execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer can be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection can be made to an external computer (for example, through the Internet using an Internet Service Provider).

[0166] The flow diagrams and the block diagrams in the drawings are illustrations of architectures, functionalities, and operations of possible implementations of systems, methods, and computer program products according to various embodiments of the present application. In this regard, each block in the flow diagrams or block diagrams can represent a module, a segment, or a portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that in some alternative implementations, the functions noted in the blocks can occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently or the blocks may

[0167] The modules involved in the embodiments of the present application can be implemented in the form of software or in the form of hardware. In some cases, the name of the module does not constitute a limitation on the module itself.

[0168] The readable storage medium provided by the present application is a computer readable storage medium, which stores computer readable program instructions (i.e. computer program) for executing the above business field configuration method, and can solve the technical problem of insufficient flexibility of the association of the business field with the form field and data processing when the existing method processes a business request. Compared with the prior art, the computer readable storage medium provided by the present application has the same beneficial effects as the business field configuration method provided by the above embodiments, and will not be described here.

[0169] The application also provides a computer program product comprising a computer program which, when executed by a processor, implements the steps of the service field configuration method as described above.

[0170] The computer program product provided by the application can solve the technical problem of insufficient flexibility of association of the service field with the form field and data processing when a service request is processed by the existing method. Compared with the prior art, the beneficial effects of the computer program product provided by the application are the same as those of the service field configuration method provided by the above-described embodiments, and are not described here.

[0171] The above only describes some embodiments of the application, and does not limit the patent scope of the application. Any equivalent structural transformation, direct / indirect application in other related technical fields, or the like made by using the content of the specification and drawings within the technical concept of the application is included in the patent protection scope of the application.

Claims

1. A method for configuring a business field, characterized in that: The method comprises the following steps: In response to the business field association configuration request, establish an association relationship between the current business field and the form field; Based on the asynchronous thread, matching form field data is searched according to the association relationship, and the form field data is converted into values ​​according to the business field type to generate business field data; The business field data is filtered and the filtered out storable field set is stored in the business database to complete the business field configuration.

2. The service field configuration method according to claim 1, wherein: The step of establishing an association relationship between the current business field and the form field in response to the association configuration request of the business field includes: In response to a request for association configuration of a business field, determine whether the current business field supports form field association by querying the system configuration table, and generate an association support result; If the association supportability result indicates that association is allowed, generating an associable form type set based on the form type list; In response to a user's selection operation on the set of associable form types, generating a target form type identifier; Load the corresponding form set according to the target form type identifier to generate an associable form set; Based on a preset field type matching rule, the form fields in the associable form set are screened to generate an associable field set, and the association relationship between the current business field and the form field is saved according to the associable field set.

3. The service field configuration method according to claim 2, wherein: The step of screening the form fields in the associable form set based on the preset field type matching rule to generate the associable field set includes: Get the current business field type and generate a business field type identifier; Querying the preset field type matching rules for allowed association types that match the business field type identifier, and generating an allowed association type set; The form fields whose field types belong to the allowed association type set in the associable form set are filtered to generate the associable field set.

4. The service field configuration method according to any one of claims 1 to 3, characterized in that: The step of querying the matched form field data according to the association relationship based on the asynchronous thread, converting the value of the form field data according to the business field type, and generating the business field data includes: Based on the asynchronous thread, query the matching associated records according to the associated relationship and generate a target mapping relationship set; Traverse each record in the target mapping relationship set, extract the business field type and range configuration, and generate field constraint rules; Convert form field data values ​​according to preset rules to generate conversion results: Aggregating the conversion results of all records to generate the business field data; In the process of generating the business field data, when the queue of the asynchronous thread is full, the task of generating the business field data is resubmitted after sleeping for a preset time.

5. The service field configuration method according to claim 4, wherein: The step of converting the form field data values ​​according to the preset rules to generate the conversion results includes: If the form field data value is of text type, the character string of the form field data value is intercepted according to the length range to obtain a conversion result; If the form field data value is a numeric type, convert the data precision of the form field data value according to the precision rule to obtain a conversion result; If the form field data value is of date type, formatting the form field data value according to the format rule to obtain a conversion result; If the form field data value is of option type, obtaining a conversion result by checking whether the form field data value is within the option code range of the business field; If the form field data value is of attachment type, the form field data value is stored in the attachment corresponding field of the business field to obtain a conversion result.

6. The service field configuration method according to any one of claims 1 to 3, characterized in that: The step of filtering the business field data and storing the filtered storable field set in the business database to complete the business field configuration includes: Filtering the business field data for data whose field names belong to a list of fields that can be modified, and generating a set of fields that can be stored in the database, wherein the list of fields that can be modified is modification restriction rule information queried in a system configuration table based on user information; The set of storable fields is stored in the business database.

7. The service field configuration method according to any one of claims 1 to 3, characterized in that: After the step of filtering the business field data and storing the filtered storable field set in the business database to complete the business field configuration, the method further includes: Based on the storage results and historical data of the business field data, the usage of the business field is analyzed through the reinforcement learning algorithm and the spatiotemporal graph convolutional network to generate a business field usage report; Generate a recommended field configuration solution corresponding to the business field usage report through a generative adversarial network; Based on the received user confirmation or modification operation on the recommended field configuration solution, the business field configuration is adjusted, and the adjusted configuration information is synchronized to the business database.

8. A service field configuration device, characterized in that: The service field configuration device includes: The data association module is used to establish an association relationship between the current business field and the form field in response to the association configuration request of the business field; A data mapping module is used to query the matching form field data according to the association relationship based on an asynchronous thread, and convert the value of the form field data according to the business field type to generate business field data; The data storage module is used to filter the business field data and store the filtered storage field set into the business database to complete the business field configuration.

9. A service field configuration device, characterized in that: The service field configuration device includes: a memory, a processor, and a service field configuration program stored in the memory and executable on the processor. When the service field configuration program is executed by the processor, the service field configuration method according to any one of claims 1 to 7 is implemented.

10. A storage medium, characterized in that: The storage medium stores a service field configuration program, which, when executed by a processor, implements the service field configuration method according to any one of claims 1 to 7.

Images