Business logic rechecking method and device, equipment, storage medium and product

Abstract

The invention discloses a business logic rechecking method, a business logic rechecking device, business logic rechecking equipment, a storage medium and a product, and relates to the technical field of mobile development platforms. Calling a unified review annotation interface to obtain review template parameters representing to-be-reviewed approval fields in the to-be-processed business and multi-dimensional information representing business function information, and generating a to-be-reviewed task; and receiving an approval result fed back by the rechecking personnel according to the to-be-rechecked task, and generating a rechecking result of the to-be-processed service according to the approval result. When it is detected that the business needs to be rechecked and approved, the to-be-rechecked task is generated through the unified rechecking annotation interface according to the rechecking template parameters and the information of the to-be-processed business so as to be approved by rechecking personnel, and transaction codes do not need to modify codes in the business logic implementation method; by adding the self-defined review annotation, the review logic can be added to the original function, so that the workload is greatly reduced, and the influence on the existing function is avoided.

Description

Technical Field

[0001] This application relates to the technical field of mobile development platforms, and particularly to a method, device, equipment, storage medium and product for business logic review. Background Art

[0002] Currently, in engineering, for review functions such as "mobile development platforms", different interfaces need to be written for each different function point to achieve the effect that the function is effective after being reviewed by the reviewer. In the actual development platform, there are many functions, and different customers have different ideas about the functions that need to be reviewed. Therefore, all functions may require a review process. However, if the review logic is added to the original function, the business implementation method needs to be modified. Therefore, if all functions need to be reviewed, the code of the business implementation methods corresponding to all functions needs to be modified. Writing review logic separately for different functions is too much work and will also affect the existing functions. Summary of the Invention

[0003] The main purpose of this application is to provide a method, device, equipment, storage medium and product for business logic review, aiming to solve the technical problems of large workload and affecting existing functions when writing review logic separately for different functions.

[0004] To achieve the above purpose, this application proposes a method for business logic review, and the method includes:

[0005] When it is detected that the business to be processed needs review and approval, call the unified review annotation interface, and the unified review annotation interface is a review interface constructed based on the review and approval requirements of multiple services;

[0006] Obtain review template parameters and multi-dimensional information corresponding to the business to be processed through the unified review annotation interface, where the review template parameters are used to represent the fields to be reviewed and approved in the business to be processed, and the multi-dimensional information is used to represent the business function information corresponding to the business to be processed;

[0007] Generate a review task to be reviewed according to the review template parameters and the multi-dimensional information;

[0008] Receive the approval result feedback by the reviewer according to the review task to be reviewed, and generate a review result of the business to be processed according to the approval result.

[0009] In an embodiment, before the step of calling the unified review annotation interface when it is detected that the business to be processed needs review and approval, the method further includes:

[0010] Determine the business to be approved according to the review and approval requirements of multiple services;

[0011] Generate a custom review annotation aspect class corresponding to the business to be approved;

[0012] Generate a unified review annotation interface in the aspect class of the custom review annotation, and set review template parameters in the unified review annotation interface, where the review template parameters include at least one of a service function identifier, a review level, and a data field mapping.

[0013] In one embodiment, after the step of generating a unified review annotation interface in the aspect class of the custom review annotation, the method further includes:

[0014] Add a custom review annotation declaration in the business logic implementation method corresponding to the business to be approved;

[0015] Determine whether there is a custom review annotation declaration in the business logic implementation method corresponding to the business to be processed;

[0016] If there is the custom review annotation declaration, it indicates that the business to be processed requires review and approval.

[0017] In one embodiment, after the step of determining whether there is a custom review annotation declaration in the business logic implementation method corresponding to the business to be processed, the method further includes:

[0018] If there is no such custom review annotation declaration, it indicates that the business to be processed does not require review and approval;

[0019] Call the original business logic implementation method, and store the logically processed data in the business table of the database.

[0020] In one embodiment, before the step of receiving the approval result feedback by the reviewer according to the review task to be reviewed and generating the review result of the business to be processed according to the approval result, the method further includes:

[0021] Generate a front-end approval process according to the review task to be reviewed, and push the front-end approval process to the reviewer, so that the reviewer approves the business to be processed according to the review task to be reviewed and generates an approval result.

[0022] In one embodiment, after the step of receiving the approval result feedback by the reviewer according to the review task to be reviewed and generating the review result of the business to be processed according to the approval result, the method further includes:

[0023] When the approval result is approval passed, call the original business logic implementation method according to the multi-dimensional information through the unified approval passed interface, and store the logically processed data in the business table of the database.

[0024] In addition, to achieve the above object, the present application also proposes a business logic review device, where the business logic review device includes:

[0025] A review interface call module, which is used to call a unified review annotation interface when it is detected that a business to be processed requires review and approval. The unified review annotation interface is a review interface constructed based on the review and approval requirements of multiple types of businesses;

[0026] A parameter information acquisition module, which is used to obtain review template parameters and multi-dimensional information corresponding to the business to be processed through the unified review annotation interface. Among them, the review template parameters are used to represent the fields to be reviewed and approved in the business to be processed, and the multi-dimensional information is used to represent the business function information corresponding to the business to be processed;

[0027] A review task generation module, which is used to generate a review task to be reviewed according to the review template parameters and the multi-dimensional information;

[0028] A review result generation module, which is used to receive the approval result feedback by the reviewer according to the review task to be reviewed, and generate the review result of the business to be processed according to the approval result.

[0029] In addition, to achieve the above object, the present application also proposes a business logic review device, which includes: a memory, a processor, and a computer program stored on the memory and executable on the processor. The computer program is configured to implement the steps of the business logic review method as described above.

[0030] In addition, to achieve the above object, the present application also proposes a storage medium, which is a computer-readable storage medium. A computer program is stored on the storage medium, and when the computer program is executed by a processor, it implements the steps of the business logic review method as described above.

[0031] In addition, to achieve the above object, the present application also provides a computer program product, which includes a computer program. When the computer program is executed by a processor, it implements the steps of the business logic review method as described above.

[0032] The present application provides a business logic review method. When it is detected that a business to be processed requires review and approval, a unified review annotation interface is called to obtain review template parameters representing the fields to be reviewed and approved in the business to be processed and multi-dimensional information representing business function information, and a review task to be processed is generated. The approval result feedback by the reviewer according to the review task to be processed is received, and the review result of the business to be processed is generated according to the approval result. When it is determined that the business requires review and approval, the original business logic implementation method will not be followed. Instead, only the unified review annotation interface will be used to generate a review task to be processed according to the review template parameters and the information of the business to be processed for the reviewer to approve. For many transaction codes, there is no need to modify the code inside the business logic implementation method, and the original function can be added with a review logic by adding a custom review annotation. Thus, the workload is greatly shortened while avoiding the impact on the existing functions. BRIEF DESCRIPTION OF THE DRAWINGS

[0033] The drawings herein are incorporated into and constitute a part of this specification, showing embodiments consistent with the present application, and are used together with the specification to explain the principles of the present application.

[0034] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the drawings required for use in the description of the embodiments or the prior art. Obviously, for those of ordinary skill in the art, other drawings can also be obtained based on these drawings without creative efforts.

[0035] Figure 1 It is a schematic flowchart provided for Embodiment 1 of the business logic review method of the present application;

[0036] Figure 2 It is a schematic flowchart provided for Embodiment 2 of the business logic review method of the present application;

[0037] Figure 3 It is a schematic overall flowchart of the business logic review method of the present application;

[0038] Figure 4 It is a schematic module structure diagram of the business logic review device in the embodiment of the present application;

[0039] Figure 5 It is a schematic device structure diagram of the hardware operating environment involved in the business logic review method in the embodiment of the present application.

[0040] The implementation, functional features and advantages of the present application will be further described in conjunction with the embodiments with reference to the drawings. DETAILED DESCRIPTION OF THE EMBODIMENTS

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

[0042] To better understand the technical solution of this application, the following will be described in detail in conjunction with the accompanying drawings of the specification and specific implementation manners.

[0043] The main solution of the embodiments of this application is: when it is detected that a business to be processed requires review and approval, a unified review annotation interface is called. The unified review annotation interface is a review interface constructed based on the review and approval requirements of multiple types of businesses; the review template parameters and multi-dimensional information corresponding to the business to be processed are obtained through the unified review annotation interface. Among them, the review template parameters are used to represent the fields to be reviewed and approved in the business to be processed, and the multi-dimensional information is used to represent the business function information corresponding to the business to be processed; a review task to be reviewed is generated according to the review template parameters and the multi-dimensional information; the approval result feedback by the reviewer according to the review task to be reviewed is received, and the review result of the business to be processed is generated according to the approval result.

[0044] At present, in engineering, for the review function of "mobile development platform", different interfaces need to be written for each different function point to achieve the effect that the function becomes effective after being reviewed by the reviewer. There are many functions in the actual development platform, and different customers have different ideas about the functions that need to be reviewed. Therefore, all functions may require a review process. However, if the review logic is added to the original function, the business implementation method needs to be modified. Therefore, if all functions need to be reviewed, the code of the business implementation methods corresponding to all functions needs to be modified. Writing the review logic separately for different functions is too much work and will also affect the existing functions.

[0045] This application provides a solution. When it is detected that a business to be processed requires review and approval, a unified review annotation interface is called to obtain review template parameters representing the fields to be reviewed and approved in the business to be processed and multi-dimensional information representing business function information, and a review task to be reviewed is generated; the approval result feedback by the reviewer according to the review task to be reviewed is received, and the review result of the business to be processed is generated according to the approval result. When this application determines that a business requires review and approval, it will not follow the original business logic implementation method, but only follow the unified review annotation interface to generate a review task to be reviewed according to the review template parameters and the information of the business to be processed for the reviewer to approve. The codes inside the business logic implementation methods of many trading codes do not need to be modified, and the review logic can be added to the original function by adding custom review annotations, thus greatly shortening the workload and avoiding the impact on the existing functions.

[0046] It should be noted that the execution subject of the method in this embodiment can be a computing service device with functions of business logic review, network communication, and program operation, such as a tablet computer, a personal computer, a mobile phone, etc.; it can also be a business logic review device with the same or similar functions. This embodiment and the following embodiments will be described by taking the business logic review device as an example.

[0047] Based on this, an embodiment of the present application provides a business logic review method. Referring to Figure 1 , Figure 1 is a schematic flowchart of the first embodiment of the business logic review method of the present application.

[0048] In this embodiment, the business logic review method includes steps S10 to S40:

[0049] Step S10, when it is detected that the business to be processed needs review and approval, call the unified review annotation interface, and the unified review annotation interface is a review interface constructed based on the review and approval requirements of multiple services.

[0050] It can be understood that the original business is processed in two steps. The first step is to perform basic verification on the business data, which can be security verification, data completeness verification, etc. The second step is to perform business logic processing through the original business logic implementation method, and after processing, store it in the database to end the process. "Storing in the database" refers to the process of storing data in a database or a persistent storage system. This process involves saving the processed data to a structured storage location so that it can be queried, updated, and managed in the future. In many applications, data storage in the database is an important part of the business logic. For example, in an e-commerce application, after a user completes a purchase, the order information needs to be stored in the database for subsequent order processing and historical record query.

[0051] It should be noted that if it is necessary to add review logic to the original function, the existing method needs to modify the business logic implementation method in the second step. Therefore, if all functions need to be reviewed, all function codes need to be modified. In this embodiment, the above problem is solved by customizing the review annotation. First, it is detected whether the business to be processed needs review and approval. When it is detected that the business to be processed needs review and approval, call the unified review annotation interface constructed in this embodiment. The unified review annotation interface is a review interface constructed based on the review and approval requirements of multiple services. That is, when multiple services need to be reviewed, this interface is uniformly called for review processing without modifying the business methods of each service. This method can improve the readability and maintainability of the code, avoid modifying the original business implementation method, and at the same time reduce the intrusion into the business code.

[0052] Step S20: Obtain the review template parameters and the multi-dimensional information corresponding to the to-be-processed service through the unified review annotation interface. Among them, the review template parameters are used to represent the fields to be reviewed and approved in the to-be-processed service, and the multi-dimensional information is used to represent the service function information corresponding to the to-be-processed service.

[0053] It can be understood that when it is detected that the service needs to be reviewed and approved, in this embodiment, a to-be-reviewed task is generated through the unified review annotation interface. Specifically, the multi-dimensional information corresponding to the to-be-processed service is stored in the database through the review template parameters in the unified review annotation interface to generate a record to be reviewed. The multi-dimensional information may include information such as classes, methods, and parameters. Through these multi-dimensional information, the system can identify which specific service the current data corresponds to. The review template parameters are a series of parameters predefined according to specific service requirements and review rules, which are used to guide the generation of the data to be reviewed, and can specify which specific function the current service to be reviewed is, and which fields need to be reviewed, etc.

[0054] Step S30: Generate a to-be-reviewed task according to the review template parameters and the multi-dimensional information.

[0055] Here, an example is given to illustrate the generated to-be-reviewed task. For example, if the to-be-processed service is the content publishing function, the multi-dimensional information corresponding to the original service method is: Class: ContentController, Method: publishArticle, Parameter: ArticlePublishRequest articleRequest (including article title, content, author ID, etc.). The review template parameters may include function identifier: "ArticlePublish", review level: "Level3", data field mapping: article title, article content, author ID, etc. Then, the unified review annotation interface generates the to-be-reviewed data according to the above information as: "Service function identifier: ArticlePublish, review level: Level3, ArticleTitle: article title, ArticleData: article content, AuthorId: author ID".

[0056] It should be noted that the above data to be reviewed is an intermediate data set generated according to the configuration parameters of the review template. It is a screening and collation of the original business data, only containing information related to the review, so as to facilitate subsequent review processing. The data to be reviewed is an abstraction and refinement of the original business data. It retains the key information and removes unnecessary details, enabling the reviewers to perform the approval work more efficiently. The unified review annotation interface further generates a review task according to the above data to be reviewed in a specific format of the review form. The "review task" is a structured record formed by further storing the "data to be reviewed" in the database. Here, the data of the review task will not be inserted into the specific business table, but the records to be reviewed will be added to the review form of the database, so as to provide the reviewers with the review form for review and approval, without affecting the original functions. The reviewers complete the approval work by querying or receiving the review form to read the records to be reviewed, and the approval results will also be recorded in the corresponding records, so as to realize the effective monitoring and management of the entire business process.

[0057] Step S40: Receive the approval result feedback by the reviewer according to the review task, and generate the review result of the business to be processed according to the approval result.

[0058] It can be understood that in the case where the business to be processed requires review and approval, after this embodiment generates the review task, the reviewer approves through the data recorded in the review form in the database, and gives an approval result of approval or disapproval, and stores it in the specific result table of the database. The system obtains the approval result from the result table of the database, and generates the review result of the business to be processed according to the approval result.

[0059] In a feasible implementation manner, before step S40, step S31 may further be included:

[0060] Step S31: Generate a front-end approval process according to the review task, and push the front-end approval process to the reviewer, so that the reviewer approves the business to be processed according to the review task and generates an approval result.

[0061] It can be understood that the system can generate a front-end approval process according to the review form at a specific time node (such as every Monday or every 3 days) or the number of records recorded in the review form (such as every time 1 or 10 records are generated), and push the front-end approval process to the reviewer. When the reviewer receives the front-end approval process, they query the review tasks in the review form. When different reviewers are responsible for different business functions, they can screen out the business they are responsible for according to the business function identifier in the review task, review the specific data fields, generate an approval result, and store the generated approval result in the database.

[0062] In a feasible implementation manner, after step S40, step S41 may further be included:

[0063] Step S41, when the approval result is approval passed, call the original business logic implementation method according to the multi-dimensional information through the unified approval passed interface, and store the logically processed data into the business table of the database.

[0064] It can be understood that a unified approval passed interface common to all services can be predefined in advance. When the reviewer approves, different services uniformly call this unified approval passed interface to read the above stored information such as classes, methods, parameters, etc. from the database, and use the information as parameters to pass into the business logic implementation method for business processing, and store the logically processed data into the business table of the database.

[0065] It should be understood that after the review approval is passed, the original business logic implementation method is followed, that is, multi-dimensional information such as classes, methods, parameters, etc. is read from the database, and the original business logic implementation method is called, and the multi-dimensional information is passed into the method for business logic processing to obtain the business logic processing result.

[0066] This embodiment provides a business logic review method. When it is detected that a business to be processed requires review and approval, a unified review annotation interface is called to obtain a review template parameter representing the field to be reviewed and approved in the business to be processed and multi-dimensional information representing business function information, and a review task to be processed is generated; the approval result feedback by the reviewer according to the review task to be processed is received, and a review result of the business to be processed is generated according to the approval result. In this embodiment, when it is determined that a business requires review and approval, the original business logic implementation method is not followed, and only the unified review annotation interface is used to generate a review task to be processed according to the review template parameter and the information of the business to be processed for the reviewer to approve. Many transaction codes do not need to modify the code inside the business logic implementation method, but can complete the addition of review logic to the original function by adding custom review annotations, thus greatly shortening the workload and avoiding the impact on existing functions.

[0067] Based on the first embodiment of the present application, in the second embodiment of the present application, the same or similar content as that in the above-mentioned first embodiment can be referred to the above introduction and will not be repeated hereinafter. On this basis, please refer to Figure 2 , before step S10, the business logic review method further includes steps S01 to S03:

[0068] Step S01, determine the business to be approved according to the review and approval requirements of multiple services.

[0069] It can be understood that, due to the numerous functions in the actual development platform and the inconsistent ideas of different customers regarding the functions to be reviewed, multiple business operations to be approved can be determined according to the review and approval requirements of multiple services.

[0070] Step S02: Generate an aspect class for the custom review annotation corresponding to the business operation to be approved.

[0071] It should be noted that an aspect class for the custom review annotation corresponding to the business operation to be approved can be generated. It can be written based on the syntax of a preset programming language, custom annotations, and reflection technology. The preset programming language can be languages such as JAVA, Python, or C++, without limitation here. A custom review annotation is a predefined annotation used to mark specific elements (such as classes, methods, fields, etc.) in the code so that these elements can be specially processed at runtime or compile time. Review annotations usually contain multiple attributes (for example, whether to record the return value of a method, whether to record exception information, etc.), and these attributes can configure the behavior of the annotation.

[0072] It should be understood that Aspect-Oriented Programming (AOP) is a programming paradigm used to solve the problem of cross-cutting concerns scattered in different modules in a program. An aspect class is a core component of aspect-oriented programming, which allows developers to encapsulate cross-cutting concerns into independent modules, thereby reducing code duplication and improving the maintainability of the system. By using an aspect class, functions such as logging and security checks can be added to the existing code without modifying the business logic itself.

[0073] Step S03: Generate a unified review annotation interface in the aspect class of the custom review annotation, and set review template parameters in the unified review annotation interface. The review template parameters include at least one of a business function identifier, a review level, and a data field mapping.

[0074] It can be understood that the implementation logic of the custom review annotation can be written in the aspect class, a unified review annotation interface is generated, and review template parameters are set in the unified review annotation interface. The review template parameters include business function identifiers, review levels, data field mappings, review conditions, and some other business rules. Among them, the business function identifier is used to distinguish different functional modules or business operations, so as to accurately locate the corresponding function when generating the data to be reviewed. The review level is used to set different review levels according to the importance and risk degree of the business, such as first-level review, second-level review, etc. Different review levels may correspond to different review processes and permission requirements. The data field mapping is used to specify which fields in the business data need to participate in the review, and the corresponding relationship between these fields and the fields in the task to be reviewed. The review condition is used to define the specific conditions for triggering the review, such as the amount exceeding a certain threshold, involving a specific business type, etc. Only operations that meet these conditions will generate the data to be reviewed. It can also include some specific business rules, such as data format requirements, value range limitations, etc., to ensure that the generated data to be reviewed complies with the business specifications.

[0075] It should be understood that the unified review annotation interface can store information such as the class, method, and parameters of the business to be approved in the database to generate the records to be reviewed and add them to the relevant review tables. This method can improve the readability and maintainability of the code, avoid modifying the original business logic implementation method, and at the same time reduce the intrusion into the business code.

[0076] In a feasible implementation manner, after step S03, steps S04 to S06 may further be included:

[0077] Step S04, adding a custom review annotation declaration in the business logic implementation method corresponding to the business to be approved.

[0078] It can be understood that adding a custom composite annotation declaration to the business logic implementation method corresponding to the function of the business to be approved can specifically be done by using the "@Auditable" field for annotation declaration. That is, using the above custom composite annotation on specific business logic methods so that these methods can be intercepted and processed by the aspect class. When the business actually occurs, the original business logic implementation method will not be executed, only the logic of the annotation will be executed. Therefore, data will not be inserted into the specific business table, and only data will be recorded in the relevant review tables.

[0079] Step S05, determining whether there is a custom review annotation declaration in the business logic implementation method corresponding to the business to be processed.

[0080] Step S06, if there is the custom review annotation declaration, it means that the business to be processed needs review and approval.

[0081] It should be understood that when the business actually occurs, it is necessary to determine whether there is a custom review annotation declaration in the business logic implementation method of the business, that is, whether the business logic implementation method is marked with the "@Auditable" field. If it exists, it means that the business needs to be reviewed and approved. In this embodiment, it is only necessary to determine whether there is a custom review annotation declaration in the method to determine whether review and approval are required. Compared with the existing method of writing functions for judgment, the amount of code of the coder can be greatly reduced, and the method of only judging one declared field makes the efficiency of judging whether review and approval are required higher.

[0082] In a feasible implementation manner, after step S06, steps S07 to S08 may further be included:

[0083] Step S07, if the custom review annotation declaration does not exist, it means that the to-be-processed business does not require review and approval.

[0084] Step S08, call the original business logic implementation method, and store the logically processed data into the business table of the database.

[0085] It should be understood that if the custom review annotation declaration does not exist, it is determined that the to-be-processed business does not require review and approval, and then the original original business logic implementation method is followed. After logical processing, the data is stored into the business table of the database to complete the warehousing.

[0086] In this embodiment, by writing an aspect class for the custom composite annotation and writing the implementation logic of the custom composite annotation in the aspect class, the logic of the annotation is to store information such as the class, method, and parameters of the original business into the database to generate a record to be reviewed and add it to the relevant review table. Then, a custom review annotation declaration is added to the business logic implementation method of the function that needs to review the business, and the custom review annotation is used on specific business logic methods so that these methods can be intercepted and processed by the aspect class. This method can improve the readability and maintainability of the code, avoid modifying the original business implementation method, and reduce the intrusion into the business code at the same time.

[0087] Exemplarily, to help understand the implementation process of the business logic review method obtained by combining the above embodiment 1 with this embodiment, please refer to Figure 3 , Figure 3 A schematic diagram of the overall process of the business logic review method of this application is provided. Specifically:

[0088] When reviewing the functions in the mobile development platform, the original business went through two steps: 1. Data verification; 2. After the business logic implementation method, it was stored in the database and ended. In this application, after the preliminary data verification, it is judged whether the business needs approval. If it does not need approval, the business logic implementation method is directly called and then stored in the database and ended. If approval is required, the information such as the class, method, and parameters of the business is stored in the database through the implementation logic in the aspect class of the pre-written custom composite annotation to generate a record to be reviewed, and added to the review table. Then, the reviewer approves through the record to be reviewed in the review table. If the approval is not passed, the approval record is stored in the database, and the process of directly calling the original business logic implementation method cannot be followed because there are exceptions in the business to be processed in this review, such as data not meeting the approval requirements, the business not meeting the approval conditions, etc., which is convenient for subsequent R & D personnel to improve the function according to the approval record and make corresponding modifications to the parts that do not meet the approval conditions. If the approval is passed, the information such as the stored class, method, and parameters is read from the database through the unified interface for passing approval, the original business logic implementation method is called, and the data is inserted into the specific business table. Thus, it can be realized that the transaction code does not need to modify the code inside the business logic implementation method, and the review logic can be added to the original function by adding a custom composite annotation.

[0089] It should be noted that the above examples are only for understanding this application and do not constitute a limitation on the business logic review method of this application. Based on this technical concept, more forms of simple transformations are within the protection scope of this application.

[0090] This application also provides a business logic review device. Please refer to Figure 4 , the business logic review device includes:

[0091] The review interface call module 10 is used to call the unified review annotation interface when it is detected that the business to be processed needs review and approval. The unified review annotation interface is a review interface constructed based on the review and approval requirements of multiple businesses;

[0092] The parameter information acquisition module 20 is used to obtain the review template parameters and the multi-dimensional information corresponding to the business to be processed through the unified review annotation interface. Among them, the review template parameters are used to represent the fields to be reviewed and approved in the business to be processed, and the multi-dimensional information is used to represent the business function information corresponding to the business to be processed;

[0093] The review task generation module 30 is used to generate a review task to be processed according to the review template parameters and the multi-dimensional information;

[0094] The review result generation module 40 is used to receive the approval result feedback by the reviewer according to the review task to be processed, and generate the review result of the business to be processed according to the approval result.

[0095] The service logic verification device provided by this application adopts the service logic verification method in the above embodiments and can solve technical problems. Compared with the prior art, the beneficial effects of the service logic verification device provided by this application are the same as those of the service logic verification method provided by the above embodiments, and other technical features in the service logic verification device are the same as the features disclosed in the method of the above embodiments, which will not be elaborated here.

[0096] This application provides a service logic verification device, which includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein, the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the service logic verification method in the first embodiment above.

[0097] Refer to the following Figure 5 , which shows a schematic structural diagram of a service logic verification device suitable for implementing the embodiments of this application. The service logic verification device in the embodiments of this 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 Descriptions), PMPs (Portable Media Players), vehicle-mounted terminals (such as vehicle-mounted navigation terminals), etc., and fixed terminals such as digital TVs, desktop computers, etc. Figure 5 The service logic verification device shown is only an example and should not impose any limitation on the functions and usage scope of the embodiments of this application.

[0098] As Figure 5As shown, the service logic verification device may include a processing device 1001 (such as a central processing unit, a graphics processing unit, etc.), which may perform various appropriate actions and processes according to the program stored in the read-only memory (ROM: Read Only Memory) 1002 or the program loaded from the storage device 1003 into the random access memory (RAM: Random Access Memory) 1004. In the RAM 1004, various programs and data required for the operation of the service logic verification device are also stored. The processing device 1001, the ROM 1002, and the RAM 1004 are connected to each other through a bus 1005. An input / output (I / O) interface 1006 is also connected to the bus. Generally, the following systems may be connected to the I / O interface 1006: an input device 1007 including, for example, a touch screen, a touchpad, a keyboard, a mouse, an image sensor, a microphone, an accelerometer, a gyroscope, etc.; an output device 1008 including, for example, a liquid crystal display (LCD: Liquid Crystal Display), a speaker, a vibrator, etc.; a storage device 1003 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 1009. The communication device 1009 may allow the service logic verification device to communicate with other devices wirelessly or wiredly to exchange data. Although the figure shows a service logic verification device having various systems, it should be understood that it is not required to implement or have all the systems shown. More or fewer systems may be implemented or had alternatively.

[0099] In particular, according to the embodiments disclosed in the present application, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, the embodiments disclosed in the present application include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes program codes for performing the methods shown in the flowcharts. In such an embodiment, the computer program may be downloaded and installed from the network through the communication device, or installed from the storage device 1003, or installed from the ROM 1002. When the computer program is executed by the processing device 1001, the above functions defined in the methods of the embodiments disclosed in the present application are performed.

[0100] The service logic verification device provided by the present application adopts the service logic verification method in the above embodiments and can solve the technical problems of service logic verification. Compared with the prior art, the beneficial effects of the service logic verification device provided by the present application are the same as those of the service logic verification method provided by the above embodiments, and other technical features in the service logic verification device are the same as the features disclosed in the method of the previous embodiment, which will not be elaborated here.

[0101] It should be understood that each part disclosed in this application can be implemented by hardware, software, firmware, or a combination thereof. In the description of the above embodiments, specific features, structures, materials, or characteristics can be combined in a suitable manner in any one or more embodiments or examples.

[0102] As described above, the above are only specific embodiments of this application, but the protection scope of this application is not limited thereto. Any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed in this application, and all of them should be covered by the protection scope of this application. Therefore, the protection scope of this application should be subject to the protection scope of the claims.

[0103] This application provides a computer-readable storage medium having computer-readable program instructions (i.e., computer programs) stored thereon, and the computer-readable program instructions are used to execute the business logic review method in the above embodiments.

[0104] The computer-readable storage medium provided by this application can be, for example, a USB flash drive, but is not limited to electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: electrical connections with one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM) or flash memory, optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the above. In this embodiment, the computer-readable storage medium can be any tangible medium that contains or stores a program, and this program can be used by or combined with an instruction execution system, device, or device. The program code contained on the computer-readable storage medium can be transmitted by any appropriate medium, including but not limited to: wires, optical cables, RF (radio frequency), etc., or any suitable combination of the above.

[0105] The above computer-readable storage medium can be included in the business logic review device; it can also exist separately without being assembled into the business logic review device.

[0106] The above computer-readable storage medium carries one or more programs, which, when executed by the business logic review device, cause the business logic review device to: when detecting that a business to be processed requires review and approval, call a unified review annotation interface, where the unified review annotation interface is a review interface constructed based on the review and approval requirements of multiple types of businesses; obtain review template parameters and multi-dimensional information corresponding to the business to be processed through the unified review annotation interface, where the review template parameters are used to represent the fields to be reviewed and approved in the business to be processed, and the multi-dimensional information is used to represent the business function information corresponding to the business to be processed; generate a to-be-reviewed task based on the review template parameters and the multi-dimensional information; receive the approval result feedback by the reviewer according to the to-be-reviewed task, and generate the review result of the business to be processed according to the approval result.

[0107] Computer program code for performing the operations of this application can be written in one or more programming languages or combinations thereof. The programming languages include object-oriented programming languages such as Java, Smalltalk, C++, and also include conventional procedural programming languages such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, executed as an independent software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, 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 can be connected to an external computer (for example, by using an Internet service provider to connect through the Internet).

[0108] The flowcharts and block diagrams in the accompanying drawings illustrate the possible architectures, functions, and operations of systems, methods, and computer program products according to various embodiments of this application. In this regard, each block in the flowchart or block diagram may represent a module, a program segment, or a part of code that contains one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the blocks may occur in a different order than that marked in the accompanying drawings. For example, two consecutive blocks shown may actually be executed substantially in parallel, and they may sometimes be executed in the reverse order, depending on the functions involved. It should also be noted that each block in the block diagram and / or flowchart, and the combination of blocks in the block diagram and / or flowchart, can be implemented by a dedicated hardware-based system for performing the specified functions or operations, or can be implemented by a combination of dedicated hardware and computer instructions.

[0109] The modules involved in the embodiments of the present application can be implemented in software or in hardware. Among them, the name of the module does not constitute a limitation to the unit itself in some cases.

[0110] The readable storage medium provided by the present application is a computer-readable storage medium, and the computer-readable storage medium stores computer-readable program instructions (i.e., computer programs) for executing the above-mentioned business logic review method, which can solve technical problems. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided by the present application are the same as those of the business logic review method provided by the above embodiments, and will not be elaborated here.

[0111] The present application also provides a computer program product, including a computer program, and when the computer program is executed by a processor, the steps of the business logic review method as described above are implemented.

[0112] The computer program product provided by the present application can solve technical problems. Compared with the prior art, the beneficial effects of the computer program product provided by the present application are the same as those of the business logic review method provided by the above embodiments, and will not be elaborated here.

[0113] The above are only some embodiments of the present application, and thus do not limit the patent scope of the present application. Any equivalent structural transformation made by using the content of the specification and drawings of the present application under the technical concept of the present application, or any direct / indirect application in other related technical fields is included in the patent protection scope of the present application.

Claims

1. A business logic review method, characterized in that: The method includes: When it is detected that the pending business needs to be reviewed and approved, the unified review annotation interface is called, and the unified review annotation interface is a review interface constructed based on the review and approval requirements of multiple businesses; Acquire the review template parameters and the multi-dimensional information corresponding to the pending business through the unified review annotation interface, wherein the review template parameters are used to represent the pending review and approval fields in the pending business, and the multi-dimensional information is used to represent the business function information corresponding to the pending business; Generate a task to be reviewed according to the review template parameters and the multi-dimensional information; Receive the approval result fed back by the reviewer based on the task to be reviewed, and generate the review result of the business to be processed based on the approval result.

2. The method according to claim 1, characterized in that Before the step of calling the unified review annotation interface when it is detected that the pending business needs review and approval, the step also includes: Determine the business to be approved based on the review and approval requirements of various businesses; Generate a custom review annotation section class corresponding to the pending approval business; A unified review annotation interface is generated in the aspect class of the custom review annotation, and review template parameters are set in the unified review annotation interface, wherein the review template parameters include at least one of a business function identifier, an audit level, and a data field mapping.

3. The method according to claim 2, characterized in that After the step of generating a unified review annotation interface in the aspect class of the custom review annotation, the method further includes: Add a custom review annotation statement in the business logic implementation method corresponding to the pending business; Determine whether there is a custom review annotation declaration in the business logic implementation method corresponding to the business to be processed; If the custom review annotation statement exists, it means that the pending business needs to be reviewed and approved.

4. The method according to claim 3, characterized in that After the step of determining whether there is a custom review annotation declaration in the business logic implementation method corresponding to the business to be processed, the method further includes: If the custom review annotation statement does not exist, it means that the pending business does not require review and approval; Call the original business logic implementation method and store the logically processed data in the business table of the database.

5. The method according to claim 1, characterized in that Before the step of receiving the approval result fed back by the reviewer according to the task to be reviewed and generating the review result of the pending business according to the approval result, the method further includes: A front-end approval process is generated according to the task to be reviewed, and the front-end approval process is pushed to the reviewer, so that the reviewer can review the pending business according to the task to be reviewed and generate an approval result.

6. The method according to claim 1, characterized in that After the step of receiving the approval result fed back by the reviewer according to the task to be reviewed and generating the review result of the pending business according to the approval result, the method further includes: When the approval result is approved, the original business logic implementation method is called according to the multi-dimensional information through the approval unified interface, and the logically processed data is stored in the business table of the database.

7. A business logic review device, characterized in that: The business logic review device comprises: A review interface calling module is used to call a unified review annotation interface when it is detected that the pending business needs review and approval. The unified review annotation interface is a review interface constructed based on the review and approval requirements of multiple businesses; A parameter information acquisition module, used to acquire the review template parameters and the multi-dimensional information corresponding to the pending business through the unified review annotation interface, wherein the review template parameters are used to represent the pending review and approval fields in the pending business, and the multi-dimensional information is used to represent the business function information corresponding to the pending business; A review task generation module, used to generate a task to be reviewed according to the review template parameters and the multi-dimensional information; The review result generating module is used to receive the approval result fed back by the reviewer based on the task to be reviewed, and generate the review result of the task to be processed based on the approval result.

8. A business logic review device, characterized in that: The device comprises: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program is configured to implement the steps of the business logic review method according to any one of claims 1 to 6.

9. A storage medium, characterized in that: The storage medium is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by a processor, the steps of the business logic review method according to any one of claims 1 to 6 are implemented.

10. A computer program product, characterized in that The computer program product comprises a computer program, and when the computer program is executed by a processor, the steps of the business logic review method according to any one of claims 1 to 6 are implemented.

Images