Data object processing method, electronic device and storage medium

Abstract

The embodiment of the present application provides a data object processing method, electronic device and storage medium, the method comprising: a business system end scans out multiple data objects and their attribute fields included in the business system through a software development kit; the business system end assembles the multiple data objects and their attribute fields to obtain a specified data structure to send to the management end; the management end parses the specified data structure to display multiple data objects and their attribute fields; the management end responds to the configuration operation of the first data object among the multiple data objects, obtains configuration data for the first data object, and sends the configuration data to the business system end for setting, the configuration data including the verification rules and generation rules of the attribute fields of the configured first data object. By adopting the present application, the verification and generation of data objects can be conveniently managed based on a unified framework. The present application relates to blockchain technology, such as the corresponding verification rules and generation rules can be written into the blockchain.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a data object processing method, electronic device, and storage medium. Background Art

[0002] Data object validation and generation are crucial components of business systems. Generally speaking, daily business systems involve a significant amount of data object validation and generation, a task often requiring extensive and repetitive execution. Currently, open source frameworks utilize data validation components, such as Hibernate Validator, for data validation. However, these require coding and lack the ability to compare and validate data against other data objects, making it impossible to centrally manage validation across all data objects. Furthermore, data object generation currently utilizes coding. Therefore, implementing a unified framework for conveniently managing data object validation and generation has become a pressing issue. Summary of the Invention

[0003] The embodiments of the present application provide a data object processing method, electronic device, and storage medium, which can provide a unified framework for convenient management of the verification and generation of data objects.

[0004] In a first aspect, an embodiment of the present application provides a data object processing method, including:

[0005] The business system side scans multiple data objects included in the business system and attribute fields of the data objects through a software development kit;

[0006] The business system end assembles multiple data objects and attribute fields of the data objects to obtain a specified data structure, and sends the specified data structure to the management end;

[0007] The management terminal parses the specified data structure to obtain the multiple data objects and the attribute fields of the data objects, and displays the multiple data objects and the attribute fields of the data objects;

[0008] The management end obtains configuration data for a first data object among the multiple data objects in response to a configuration operation on the first data object, and sends the configuration data to the business system end, the configuration data including a verification rule and a generation rule for a configured attribute field of the first data object, where the first data object is any data object among the multiple data objects;

[0009] The business system side sets the configuration data in the business system.

[0010] Optionally, the business system scans multiple data objects and attribute fields of the data objects included in the business system through a software development kit, including:

[0011] The business system side calls the software development kit to scan out multiple data objects and attribute fields of the data objects included in the business system according to the annotations predefined by the software development kit, wherein the annotations include declaring data objects, declaring attribute fields of data objects, and declaring attribute fields that need to be ignored.

[0012] Optionally, after the business system side sets the configuration data in the business system, the method further includes:

[0013] When the business system detects a call request for a target rule in the configuration data, the business system executes the target rule according to the call request, wherein the target rule is any rule included in the configuration data.

[0014] Optionally, when the configuration operation includes a rule configuration operation, the verification rule includes at least one of the following: a common verification rule and a reference object verification rule;

[0015] The general verification rules include at least one of the following: not empty or not a null string, length verification, range judgment, type judgment, special or common type verification, and regular expression matching;

[0016] The reference object verification rule includes comparison and verification with an attribute field of a second data object, where the second data object is a related data object of the first data object.

[0017] Optionally, when the configuration operation includes a rule configuration operation, the management end obtains configuration data for a first data object among the multiple data objects in response to the configuration operation on the first data object, including:

[0018] The management end configures a verification rule for an attribute field of a first data object among the plurality of data objects in response to a rule configuration operation on the first data object;

[0019] The management end generates configuration data including verification rules for the attribute fields of the first data object.

[0020] Optionally, when the verification rule includes the reference object verification rule, the method further includes:

[0021] The management terminal enters a first page and loads the first data object on the first page;

[0022] The management end adds a second data object to the first data object in response to the associated data object adding operation based on the first page.

[0023] Optionally, when the verification rule includes a reference object verification rule, the configuration data further includes source information of the second data object, and the source information is used to find the second data object.

[0024] Optionally, when the configuration operation further includes an object information editing operation, the management end obtains configuration data for a first data object among the multiple data objects in response to the configuration operation on the first data object, including:

[0025] The management terminal enters the second page;

[0026] The management end receives an object information editing operation based on the second page, and edits the object information of the second data object, wherein the object information includes source information of the second data object;

[0027] The management end generates configuration data including source information of the second data object.

[0028] A second aspect. An embodiment of the present application provides an electronic device, comprising a processor and a memory, the processor and the memory being connected to each other, wherein the memory is used to store a computer program, the computer program comprising program instructions, and the processor is configured to call the program instructions to execute the method described in the first aspect.

[0029] In a third aspect, an embodiment of the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and the computer program is executed by a processor to implement the method as described in the first aspect.

[0030] To summarize, the business system end scans out the multiple data objects and the attribute fields of the data objects included in the business system through the software development kit; the business system end assembles the multiple data objects and the attribute fields of the data objects to obtain a specified data structure, and sends the specified data structure to the management end; the management end parses the specified data structure to obtain the multiple data objects and the attribute fields of the data objects, and displays the multiple data objects and the attribute fields of the data objects; the management end responds to the configuration operation of the first data object among the multiple data objects, obtains the configuration data of the first data object, and sends the configuration data to the business system end, so that the business system end sets the configuration data in the business system. Compared with the data object verification and generation process in the prior art, the relevant functions cannot be realized due to the defects of the open source framework, and the code implementation method is too cumbersome. In order to facilitate the management of the verification and generation of data objects, the present application provides a unified framework for convenient management of the verification and generation of data objects. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0032] Figure 1 This is a flow chart of a method for processing data objects provided in an embodiment of the present application;

[0033] Figure 2 This is a schematic diagram of a first page provided in an embodiment of the present application;

[0034] Figure 3 is a schematic diagram of a second page provided in an embodiment of the present application;

[0035] Figure 4 is a schematic diagram of another second page provided in an embodiment of the present application;

[0036] Figure 5 This is a flowchart of another method for processing data objects provided by an embodiment of the present application;

[0037] Figure 6 This is a schematic diagram of the network architecture of a data object processing system provided by an embodiment of the present application;

[0038] Figure 7 This is a structural diagram of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0039] The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application.

[0040] The present application embodiment can provide a data engine, which can be divided into a software development kit (SDK) and a management end. The SDK can provide the business side (i.e., the business system) with an interface for scanning data objects, verifying data objects, generating rules, and interacting with the management end.

[0041] The SDK mainly provides annotations for defining data objects, namely predefined annotations:

[0042] ①@DataEntity declares the data object

[0043] ②@EntityField declares the attribute field of the data object

[0044] ③@IgnoreField declares the attribute fields that need to be ignored

[0045] Business systems can use the above annotations to mark data objects and attribute fields. Please refer to the following example:

[0046]

[0047]

[0048] In an embodiment of the present application, the business system end can report all data objects and attribute fields of data objects to the management end through the software development kit. The management end can configure different verification and generation rules for the same data object according to different business scenarios. After the management end has configured the verification and generation rules for all data objects, it can send the verification and generation rules of all data objects to the memory in the business system; when it is necessary to verify or generate a certain data object, the rules cached in the memory can be used, which not only improves the efficiency of verification and generation of data objects, but also reduces the pressure on the management end. Among them, the verification rules and generation rules of the embodiment of the present application can be executed using the lightweight expression parser mvel to obtain the final result.

[0049] The business system end mentioned in the embodiment of the present application uniformly manages the data objects of all business systems, and uniformly manages the verification and generation rules of data objects; without changing the code or restarting the application, the data objects can be verified and the generation rules can be modified in real time through the management end to achieve different business scenarios. This application can use different verification and generation rules to achieve a set of code running in multiple places. While configuring the verification and generation rules, it supports associating other data objects to better adapt to the scenarios of verification and generation of various data object attributes. In addition, the embodiment of the present application can free the business system from the verification and generation codes of various data objects, making the code logic of the business system clearer and more concise.

[0050] The data object processing method provided in the embodiment of the present application will be described in detail below.

[0051] See also Figure 1 , is a flow chart of a data object processing method provided in an embodiment of the present application. The data object processing method may include the following steps:

[0052] S101: The business system side scans multiple data objects included in the business system and attribute fields of the data objects through a software development kit.

[0053] The business system end may be a device running a business system, such as a business middle platform, and the software development kit may be embedded in the business system.

[0054] In one embodiment, the business system end may scan multiple data objects included in the business system and the attribute fields of the data objects through a software development kit during the startup process of the business system.

[0055] In an embodiment of the present application, the business system can specifically call a software development kit to scan the business system's data objects and attribute fields of the data objects according to annotations predefined by the software development kit. The annotations can include declaring data objects, declaring attribute fields of data objects, and declaring attribute fields to be ignored, such as the aforementioned @DataEntity, @EntityField, and @IgnoreField.

[0056] For example, the business system can use the software development kit to scan the data objects included in the aforementioned business system: (code="BudgetProject",name="Budget Project") and the attribute fields of the data object (name="id",chn="Serial Number",needful="true)(name="createBy",chn="Creator")(name="createBy",chn="Creator")(name="projectAmount",chn="Project Amount")(name="performanceTarget",chn="Performance Target")(name="desc",chn="Description").

[0057] The business system described in this application may include the following code examples:

[0058] a) Data object verification related code can be as follows:

[0059] ValidateResult validateResult=

[0060] DataEntityFactory.getInstance().build().validateData(project,

[0061] Lists.newArrayList(yearProject));

[0062] Among them, the valid date parameter of the validateData method is as follows:

[0063] entityData: Lists of data objects to be verified.

[0064] relationObjectList: a newArrayList of related objects of the data object to be verified (other data objects required to be used when verifying the data object to be verified, such as the second data object).

[0065] b) Data object generation related code can be as follows:

[0066] BudgetProject project=

[0067] DataEntityFactory.getInstance().build().buildEntityData(new HashMap<>(),

[0068] BudgetProject.class,new ArrayList<>());

[0069] Among them, the method builds the data object buildEntityData parameter description:

[0070] Map<String,Object> entityData: entity data

[0071] Class <t>target: the data object class to be generated.

[0072] List <object>relationObjectList: newArrayList of the related objects of the data object to be generated (other data objects required to be used when generating the data object to be generated).

[0073] S102: The business system end assembles multiple data objects and attribute fields of the data objects to obtain a specified data structure, and sends the specified data structure to the management end.

[0074] S103: The management terminal parses the designated data structure to obtain the multiple data objects and attribute fields of the data objects, and displays the multiple data objects and attribute fields of the data objects.

[0075] In step S102-step S103, the business system end can assemble multiple data objects and the attribute fields of the data objects into a specified data structure, and send the specified data structure to the management end. The management end can receive the specified data structure and parse the execution data structure to obtain the multiple data objects and the attribute fields of the data objects, and display the multiple data objects and the attribute fields of the data objects. The specified data structure refers to a data structure that can be parsed by the management end. Among them, the management end includes but is not limited to smart terminals such as desktop computers and laptops. The embodiment of the present application can standardize and simplify the data processing process of the management end by sending the data objects and their attribute fields to the management end in a unified data format for processing.

[0076] S104. The management end obtains configuration data for a first data object among the multiple data objects in response to a configuration operation on the first data object, and sends the configuration data to the business system end. The configuration data includes verification rules and generation rules for attribute fields of the configured first data object, where the first data object is any data object among the multiple data objects.

[0077] In an embodiment of the present application, when the configuration operation includes a rule configuration operation, the management end may specifically configure a verification rule for an attribute field of a first data object among multiple data objects in response to the rule configuration operation on the first data object among the multiple data objects, and generate configuration data including the verification rule for the attribute field of the first data object. Furthermore, the management end may also configure a generation rule for an attribute field of the first data object in response to the rule configuration operation on the first data object among the multiple data objects, and generate configuration data including the generation rule for the attribute field of the first data object. In one embodiment, a single attribute field may have multiple verification rules and one generation rule.

[0078] In an application scenario, the management end can display the multiple data objects on a page for rule configuration. The administrator can perform rule configuration based on selecting the first data object from the multiple data objects. In response to the selection operation on the first data object, the management end can display a rule configuration item, and the rule configuration item can be used to configure the verification rule of the attribute field of the first data object. The user can configure the verification rule of the attribute field of the first data object based on the rule configuration item. In response to the rule configuration operation on the first data object, the electronic device configures the verification rule of the attribute field of the first data object and generates configuration data including the verification rule of the attribute field of the first data object. In addition, the embodiment of the present application can also refer to this method to obtain configuration data including the generation rule of the attribute field of the first data object, which will not be repeated here.

[0079] In one embodiment, the verification rules mentioned in the embodiments of the present application may include at least one of the following: general verification rules and reference object verification rules; the general verification rules include at least one of the following: not empty or not a null string, length verification, range determination, type determination, special or common type determination, and regular expression matching. Length verification may include, for example, determining whether the length is greater than a preset value. Range determination may include, for example, determining whether the range is a numeric range or a time range. Type determination may include, for example, determining whether the type is a numeric type. Special or common type determination may include, for example, verification of information such as ID number, email address, age, or mobile phone number. The reference object verification rules include comparison verification with attribute fields of a second data object, where the second data object is a related data object of the first data object. The embodiments of the present application may use reference object verification rules to verify whether fields are repeated, whether the order amount is the maximum of all order amounts, and other scenarios, without limitation. The generation rules described in the embodiments of the present application, such as the generation rule for field c, may be field c = field a + field b. This is applicable in scenarios where the balance is calculated by subtracting the used amount from the total amount. The balance field here may be obtained by performing an operation on two other fields. For example, the generation rules of the number field are obtained according to certain rules. The applicable scenario is that the first few digits of the order number are the value of a certain area, the middle is the time, and the end is the order of order.

[0080] In one embodiment, when the verification rule includes a reference object verification rule, the first data object can add a second data object to the first data object in the following manner: the management terminal enters the first page and loads the first data object on the first page; the management terminal responds to the addition operation of the associated data object based on the first page and adds the second data object to the first data object. In an application scenario, the first page can be Figure 2 The page shown, Figure 2 The page shown includes the Add Input Data Object button and the Add Related Data Object button. Figure 2 When the page is shown, you can click the Add Input Data Object button to Figure 2 The page shown adds data object 1. The management terminal can respond based on Figure 2 Add an action to the input data object of the page shown to Figure 2 The page shown loads data object 1. The administrator can click the Add Related Object button to add data object 2 to data object 1. The management terminal can respond based on Figure 2 The associated data object adding operation on the page shown is to add data object 2 to data object 1, where data object 2 is the associated data object of data object 1.

[0081] In one embodiment, when the verification rule includes a reference object verification rule, the configuration data also includes source information of the second data object. This source information is used to locate the second data object. That is, when the business system executes the reference object verification rule, it can locate the second data object based on the source information, thereby implementing verification of the two data objects. In one embodiment, the source information can include a database query statement for obtaining the second data object, such as a Structured Query Language (SQL) statement or a Uniform Resource Locator (URL) of an Application Programming Interface (API) for obtaining the second data object. It can be seen that the methods for obtaining the second data object can be divided into SQL statement queries and API queries. For example, an example of configuring an SQL statement query is to configure the SQL statement, such as select * from user where userid = ?. When the first data object is associated with the second data object, a certain attribute field of the first data object is specified for the association (i.e., similar to a primary-foreign key relationship). This field is userid = ? in select * from user where userid = ?. In other words, the value of a certain attribute field of the first data object is specified, and the second data object is queried through the SQL statement. Configuration example of API query: configure the API URL and the incoming parameter information (ie, interface request parameters); similarly associate a property field of the first data object, and query the second data object through the API.

[0082] In one embodiment, when the configuration operation also includes an object information editing operation, the management end responds to the configuration operation of the first data object among the multiple data objects and obtains the configuration data of the first data object. Specifically, the management end enters the second page and receives the object information editing operation based on the second page, edits the object information of the second data object, and thus generates configuration data including the source information of the second data object. The object information includes the source information of the second data object. In an application scenario, the second page can be Figure 3 The page shown or Figure 4 The management terminal can Figure 3 The page shown or Figure 4 The page shown configures source information of the second data object.

[0083] S105: The business system side sets the configuration data in the business system.

[0084] In the embodiment of the present application, the business system end can receive the configuration data sent by the management end and set the configuration data in the business system. Subsequently, when the business system end detects a call request for the configuration data, it can execute the corresponding rules according to the request.

[0085] visible, Figure 1 In the illustrated embodiment, the business system end scans out the multiple data objects and the attribute fields of the data objects included in the business system through a software development kit; the business system end assembles the multiple data objects and the attribute fields of the data objects to obtain a specified data structure, and sends the specified data structure to the management end; the management end parses the specified data structure to obtain the multiple data objects and the attribute fields of the data objects, and displays the multiple data objects and the attribute fields of the data objects; the management end responds to the configuration operation of the first data object among the multiple data objects, obtains the configuration data of the first data object, and sends the configuration data to the business system end, so that the business system end sets the configuration data in the business system. The present application can conveniently manage the verification and generation of data objects with a unified framework.

[0086] See also Figure 5 , is another flowchart of a data object processing method provided in an embodiment of the present application. Figure 1 Example, Figure 5 The illustrated embodiment also describes the process of processing rules on the business system side.

[0087] Specifically, the data object processing method may include the following steps:

[0088] S501: The business system side scans multiple data objects included in the business system and attribute fields of the data objects through a software development kit.

[0089] S502: The business system end assembles multiple data objects and attribute fields of the data objects to obtain a specified data structure, and sends the specified data structure to the management end.

[0090] S503: The management terminal parses the designated data structure to obtain the multiple data objects and attribute fields of the data objects, and displays the multiple data objects and attribute fields of the data objects.

[0091] S504. The management end obtains configuration data for a first data object among the multiple data objects in response to a configuration operation on the first data object, and sends the configuration data to the business system end. The configuration data includes verification rules and generation rules for attribute fields of the configured first data object, where the first data object is any data object among the multiple data objects.

[0092] S505: The business system side sets the configuration data in the business system.

[0093] Among them, steps S501 to S505 can be found in Figure 1 Steps S101-S105 of the embodiment are not described in detail in this embodiment of the present application.

[0094] S506: When the business system detects a call request for a target rule in the configuration data, the business system executes the target rule according to the call request, wherein the target rule is any rule included in the configuration data.

[0095] In an embodiment of the present application, when a call request for a target rule in the configuration data is detected, the business system can execute the target rule according to the call request. Specifically, when a call request for a target rule in the rule configuration data is detected, the business system can call the validation and rule generation interface of the data object included in the SDK through the business system to execute the target rule according to the call request and return an execution result, which is the result obtained after executing the target rule.

[0096] The embodiments of the present application involve blockchain technology. For example, the obtained verification rules and generation rules can be written into the blockchain to achieve transparency and openness of the rules. Alternatively, the embodiments of the present application can host the corresponding verification rules and generation rules on a third-party data platform for management, which can also achieve transparency and openness of the rules to a certain extent.

[0097] visible, Figure 5 In the illustrated embodiment, when the business system detects a call request for a target rule in the configuration data, it can execute the target rule according to the call request, thereby implementing the call of the rule.

[0098] See also Figure 6 , which is a schematic diagram of the network architecture of a data object processing system provided in an embodiment of the present application. The aforementioned data object processing method can be applied to this data object data system. This data object processing system can utilize the aforementioned data engine. This data object processing system can include a business system terminal 10 and a management terminal 20.

[0099] By executing steps S101 and S102, the business system end 10 can obtain a specified data structure consisting of a data object and attribute fields and send it to the management end 20. The management end 20 can obtain configuration data of the first data object (including verification rules and generation rules for the corresponding attribute fields) by executing steps S103 and S104 and send it to the business system end 10. The business system end can then execute step S105 to set the configuration data in the business system, thereby realizing a process of conveniently managing the verification and generation of data objects based on a unified framework.

[0100] See also Figure 7 , is a schematic diagram of the structure of an electronic device provided in an embodiment of the present application. The electronic device described in this embodiment can be an independent device or a device integrated with multiple devices. For example, the electronic device can be the business system end or management end mentioned above, or it can be a device integrated with the business system end and the management end. The electronic device may include: one or more processors 1000 and a memory 2000. The processor 1000 and the memory 2000 may be connected via a bus.

[0101] In one embodiment, the electronic device may further include an input device (not shown) and an output device (not shown). In one embodiment, the input device and / or the output device may include a standard wired or wireless communication interface. The input device may also include a touch screen, a touch display screen, or the like, and the output device may also include a display screen, a touch display screen, or the like.

[0102] The processor 1000 may be a central processing unit (CPU), or may be another general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), an off-the-shelf programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor, or the processor may be any conventional processor, etc.

[0103] The memory 2000 may be a high-speed RAM memory or a non-volatile memory such as a disk memory. The memory 2000 is used to store a computer program, which includes program instructions. The processor 1000 is configured to call the program instructions and execute Figure 1 and Figure 5 The implementation method described in the embodiment of the business system end, or the execution Figure 1 and Figure 5 The implementation method described in the embodiment of the management end will not be described in detail here.

[0104] The functional modules in the various embodiments of the present application may be integrated into a single processing module, or each module may exist physically separately, or two or more modules may be integrated into a single module. The aforementioned integrated modules may be implemented in the form of sampling hardware or sampling software functional modules.

[0105] Those skilled in the art will appreciate that all or part of the processes in the above-described method embodiments can be implemented by instructing the relevant hardware through a computer program. The program can be stored in a computer-readable storage medium. When executed, the program can include the processes of the above-described method embodiments. The computer-readable storage medium can be volatile or non-volatile. For example, the computer storage medium can be a magnetic disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM). The computer-readable storage medium can primarily include a program storage area and a data storage area. The program storage area can store an operating system, at least one application required for a function, etc.; the data storage area can store data created based on the use of the blockchain node, etc.

[0106] The blockchain referred to in this application refers to a new application model for computer technologies such as distributed data storage, peer-to-peer transmission, consensus mechanisms, and encryption algorithms. Blockchain is essentially a decentralized database, a series of data blocks generated using cryptographic methods. Each data block contains information about a batch of network transactions, which is used to verify the validity of the information (to prevent counterfeiting) and generate the next block. Blockchain can include the underlying blockchain platform, the platform product service layer, and the application service layer.

[0107] The above disclosure is only a preferred embodiment of the present application, and certainly cannot be used to limit the scope of rights of the present application. Ordinary technicians in this field can understand that all or part of the processes of the above embodiment and equivalent changes made in accordance with the claims of the present application are still within the scope covered by the present application.< / object> < / t>

Claims

1. A data object processing method, characterized in that: include: The business system side scans multiple data objects included in the business system and attribute fields of the data objects through a software development kit; The business system end assembles multiple data objects and attribute fields of the data objects to obtain a specified data structure, and sends the specified data structure to the management end; The management terminal parses the specified data structure to obtain the multiple data objects and the attribute fields of the data objects, and displays the multiple data objects and the attribute fields of the data objects; The management end, in response to a configuration operation on a first data object among the multiple data objects, obtains configuration data for the first data object and sends the configuration data to the business system end, the configuration data including verification rules and generation rules for the configured attribute fields of the first data object, where the first data object is any data object among the multiple data objects; wherein the management end configures different verification and generation rules for the same data object based on different business scenarios; the verification rules include reference object verification rules, where the reference object verification rules include comparison verification with attribute fields of a second data object, where the second data object is a data object associated with the first data object; and the configuration data also includes source information of the second data object, where the source information is used to locate the second data object; The business system end sets the configuration data in the business system, and writes the obtained verification rules and generation rules of the attribute fields of the first data object into the blockchain.

2. The method according to claim 1, characterized in that The business system uses a software development kit to scan multiple data objects and attribute fields of the data objects included in the business system, including: The business system side calls the software development kit to scan out multiple data objects and attribute fields of the data objects included in the business system according to the annotations predefined by the software development kit, wherein the annotations include declaring data objects, declaring attribute fields of data objects, and declaring attribute fields that need to be ignored.

3. The method according to claim 1, characterized in that After the business system side sets the configuration data in the business system, the method further includes: When the business system detects a call request for a target rule in the configuration data, the business system executes the target rule according to the call request, wherein the target rule is any rule included in the configuration data.

4. The method according to claim 1, wherein When the configuration operation includes a rule configuration operation, the verification rules further include: a common verification rule; The general verification rules include at least one of the following: not empty or not a null string, length verification, range judgment, type judgment, special or common type verification, and regular expression matching.

5. The method according to claim 4, characterized in that When the configuration operation includes a rule configuration operation, the management end obtains configuration data for a first data object among the multiple data objects in response to the configuration operation on the first data object, including: The management end configures a verification rule for an attribute field of a first data object among the plurality of data objects in response to a rule configuration operation on the first data object; The management end generates configuration data including verification rules for the attribute fields of the first data object.

6. The method according to claim 4, characterized in that When the verification rule includes the reference object verification rule, the method further includes: The management terminal enters a first page and loads the first data object on the first page; The management end adds a second data object to the first data object in response to the associated data object adding operation based on the first page.

7. The method according to claim 1, characterized in that When the configuration operation further includes an object information editing operation, the management end obtains configuration data for a first data object among the multiple data objects in response to the configuration operation for the first data object, including: The management terminal enters the second page; The management end receives an object information editing operation based on the second page, and edits the object information of the second data object, wherein the object information includes source information of the second data object; The management end generates configuration data including source information of the second data object.

8. An electronic device, characterized in that: The method comprises a processor and a memory, wherein the processor and the memory are connected to each other, wherein the memory is used to store a computer program, the computer program includes program instructions, and the processor is configured to call the program instructions to execute the method according to any one of claims 1 to 7.

9. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, and the computer program is executed by a processor to implement the method according to any one of claims 1 to 7.

Images