Business application review methods, devices, equipment and storage media

Abstract

This application relates to the field of financial technology, and more particularly to a method, apparatus, device, and storage medium for reviewing business applications. The method includes: acquiring business applications developed from different development sources in parallel; creating a menu ID for each business application; determining the review process associated with each menu ID; and submitting each business application to the review process associated with its corresponding menu ID for review. This application facilitates improved efficiency in the review process of business applications.

Description

Technical Field

[0001] This application relates to the field of financial technology, and in particular to a business application review method, apparatus, equipment and storage medium. Background Technology

[0002] In recent years, traditional banks have begun their digital transformation and achieved initial success, building a series of fundamental capabilities such as user operations, event operations, content operations, and channel operations. With the improvement of operational platform functions, business personnel are no longer satisfied with simply configuring and executing operational functions on a customer-facing basis; they hope to transfer existing offline application processes online to further improve communication efficiency between applicant and configuration personnel.

[0003] After the development team completes the business application development, the next step is to review the business application online. The review process involves first obtaining multiple business applications developed by the development team, and then submitting all the business applications to the review node for review.

[0004] However, on the one hand, multiple business applications are developed by a single team, resulting in low development efficiency and consequently low subsequent review efficiency; on the other hand, the multiple business application flows are heavily coupled internally, and the review nodes need to review each business application process separately, which leads to low review efficiency. Summary of the Invention

[0005] To improve the efficiency of business application review processes, this application provides a business application review method, apparatus, device, and storage medium.

[0006] Firstly, this application provides a method for reviewing business applications, including: Retrieve business applications from different development sources in parallel, and create menu IDs for each of the business applications; Determine the review process associated with each of the menu IDs; Each of the aforementioned business applications will be submitted to the review process associated with the menu ID corresponding to each business application for review.

[0007] Through the above implementation, firstly, the acquired business applications are developed by different development sources, avoiding the problem of low development efficiency caused by a single development pattern developing multiple business applications, which in turn leads to low review efficiency, as well as the problem of complex coupling between different business applications; secondly, during the review process, different business applications are sent to different review processes for review, which not only avoids the need to solve the coupling problem between business applications during the review process, but also effectively improves the review efficiency of business applications.

[0008] Preferably, the step of determining the review process associated with each of the menu IDs includes: Determine the application page URL for each of the menu IDs corresponding to the business application; Based on the URLs of the application pages, the corresponding business applications are displayed to obtain the business application menu; Determine the review process associated with each menu ID corresponding to each business application in the business application menu.

[0009] The above implementation allows for the display of corresponding business applications via the application page URL, improving the ease of maintaining business applications.

[0010] Preferably, the step of determining the review process associated with each menu ID corresponding to each business application in the business application menu includes: In response to the fact that the number of business applications in the business application menu is not greater than a preset number threshold, determine whether an application submission instruction has been received; If so, determine the review process associated with each menu ID corresponding to the aforementioned business application.

[0011] By implementing the above measures, the number of business applications sent for review at one time is limited, which helps to prevent excessive pressure on computing resources and can effectively improve the review efficiency of subsequent business applications.

[0012] Preferably, the step of submitting each of the business applications to the review process associated with the menu ID corresponding to each business application for review includes: Determine the URL of the review page corresponding to each of the aforementioned review processes; Submit each of the aforementioned business applications to the review page URL corresponding to the corresponding menu ID to obtain the review process menu; The business applications described in the review process menu are reviewed; wherein, the business application and the corresponding review page URL have the same menu ID.

[0013] By implementing the above methods, the corresponding business applications can be reviewed in the review page URL, which facilitates the maintenance and display of business applications in the review page URL, thereby effectively improving the efficiency of subsequent business application review.

[0014] Preferably, this application provides a business application review method, which further includes: blocking the business application menu and / or the review process menu.

[0015] By implementing the above measures, the business application menu and the review process menu are hidden during the review stage, which makes it easier to ensure that the application business is maintained uniformly during the review stage.

[0016] Preferably, this application provides a business application review method, which further includes: in response to the business application passing the review, configuring the business application.

[0017] Through the above implementation, business applications can be configured after approval, which facilitates the efficiency of subsequent business deployment and use.

[0018] Secondly, this application provides a business application review device, comprising: The ID creation module is used to retrieve business applications from different development sources in parallel and create menu IDs for each of the business applications. The process association module is used to determine the review process associated with each of the menu IDs. The application review module is used to submit each of the aforementioned business applications to the review process associated with the menu ID corresponding to each of the aforementioned business applications for review.

[0019] Through the above implementation, firstly, the acquired business applications are developed by different development sources, avoiding the problem of low development efficiency caused by a single development pattern developing multiple business applications, which in turn leads to low review efficiency, as well as the problem of complex coupling between different business applications; secondly, during the review process, different business applications are sent to different review processes for review, which not only avoids the need to solve the coupling problem between business applications during the review process, but also effectively improves the review efficiency of business applications.

[0020] Thirdly, this application provides a computer device, which includes a memory and a processor. The memory stores a computer program, and the processor executes the computer program to implement the steps in the method described above.

[0021] Fourthly, this application provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps in the above-described method.

[0022] Fifthly, this application also provides a computer program product. The computer program product includes a computer program that, when executed by a processor, implements the steps in any of the above method embodiments.

[0023] The aforementioned business application review method, apparatus, equipment, and storage medium acquire business applications developed by different development sources in parallel, create menu IDs for each business application, determine the review process associated with each menu ID, and submit each business application to the review process associated with its corresponding menu ID for review. Through this implementation, firstly, the acquired business applications are developed by different development sources, avoiding the problem of low development efficiency and consequently low review efficiency caused by a single development pattern developing multiple business applications, as well as the problem of complex coupling between different business applications; secondly, during review, different business applications are sent to different review processes for review, not only avoiding the need to resolve the coupling problem between business applications during review, but also effectively improving the review efficiency of business applications.

[0024] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of this application, nor is it intended to limit the scope of this application. Other features of this application will become readily apparent from the following description. Attached Figure Description

[0025] To more clearly illustrate the technical solutions of the embodiments of the present invention, the accompanying drawings used in the embodiments will be briefly introduced below. It should be understood that the following drawings only show some embodiments of the present invention and should not be regarded as a limitation on the scope. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0026] Figure 1 This is a flowchart of a business application review method provided in the embodiments of this application; Figure 2 This is a schematic diagram illustrating the three stages after the completion of development of a business application, as provided in this embodiment of the application. Figure 3 This is a schematic diagram of the structure of a business application review device provided in the embodiments of this application; Figure 4 This is a schematic diagram of the structure of a computer device provided in an embodiment of this application; Figure 5 This is an internal structural diagram of a computer-readable storage medium provided in an embodiment of this application. Detailed Implementation

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

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

[0029] In this article, the term "and / or" is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, and B alone. Additionally, the character " / " in this article generally indicates that the preceding and following related objects have an "or" relationship.

[0030] Example 1 Figure 1 A flowchart of a business application review method provided in Embodiment 1 of this application is shown below. Figure 1 The method can be executed by a device that performs the method, which can be implemented in software and / or hardware, and the method includes: S110. Obtain business applications developed from different development sources in parallel, and create menu IDs for each of the business applications.

[0031] It should be noted that banks and other financial institutions use their internally built operating platforms to help their staff conduct user acquisition and user engagement activities. For example, the operating activities that can be achieved through these platforms include, but are not limited to, user operations, event operations, content operations, and channel operations. To enrich the business application functions of the operating platform, the financial institution's internal development team can develop corresponding business functions for the platform. For example, business applications include, but are not limited to, applications for operating slots, applications for consumer voucher activities, applications for task activities, applications for outbound calls, and applications for messaging, etc., without specific limitations. Each type of business application is developed by the development team as a corresponding operating platform function.

[0032] It should also be noted that operating platforms generally need to develop multiple business applications (business functions). If multiple business applications are handled by a single development team as is the case with current technology, it will not only severely reduce development efficiency, but also result in complex coupling between the developed business applications. If there is complex coupling between business applications, it will also severely reduce the efficiency of business application review, because in the process of reviewing a single business application, the coupling between that business application and other business applications must be fully considered.

[0033] To improve the development efficiency of business applications and eliminate the complex coupling between different business applications, this implementation assigns different business applications to different development teams for independent development, with each development team being a separate development source.

[0034] To enable the acquisition and review of business applications, this embodiment also includes a pre-defined unified framework for project management business applications, which can acquire business applications sent from different development sources.

[0035] It should be noted that, since different business applications are developed by different development teams, in order to facilitate the effective management and maintenance of each business application, in this embodiment, the framework also creates corresponding menu IDs for different business applications; for example, menu ID1 is created for operation position application, menu ID2 is created for consumer voucher activity application, menu ID3 is created for task activity application, menu ID4 is created for outbound telephone application, and menu ID5 is created for message application.

[0036] S120. Determine the review process associated with each of the menu IDs.

[0037] It should be noted that in the existing technology, when an audit node audits multiple business applications, it needs to audit multiple business applications with coupling relationships at the same time, which seriously reduces the efficiency of the audit. In order to improve the audit efficiency of business applications, this embodiment has a corresponding audit process for each business application. In order to ensure that each audit process can audit a single business application, after the menu ID of each business application is created, an audit process is associated with each menu ID.

[0038] For example, the review process associated with menu ID1 is used as the operation position application review process, the review process associated with menu ID2 is used as the consumer voucher activity application review process, the review process associated with menu ID3 is used as the task activity application review process, the review process associated with menu ID4 is used as the outbound call application review process, and the review process associated with menu ID5 is used as the message application review process.

[0039] S130. Submit each of the aforementioned business applications to the review process associated with the menu ID corresponding to each of the aforementioned business applications for review.

[0040] It should be noted that after the unified framework for project management business applications completes the acquisition of each independent business application and the determination of the review process for each business application's menu ID, the next step is to forward each independent business application to the review process associated with the menu ID of each menu, so as to realize the review of each independent business application separately.

[0041] Specifically, the application for an operational slot will be submitted to the operational slot application review process associated with menu ID1 for review; the application for a consumer voucher activity will be submitted to the consumer voucher activity application review process associated with menu ID2 for review; the application for a task activity will be submitted to the task activity application review process associated with menu ID3 for review; the application for outbound calls will be submitted to the outbound call application review process associated with menu ID4 for review; and the application for a message will be submitted to the message application review process associated with menu ID5 for review.

[0042] It should be noted that since the business applications submitted to the review process are independent and unique, eliminating the coupling relationship with other business applications, each review process reviews the business applications in parallel, which can greatly improve the review efficiency of each business application.

[0043] It should be noted that this embodiment acquires business applications developed by different development sources in parallel, creates a menu ID for each business application, determines the review process associated with each menu ID, and submits each business application to the review process associated with its corresponding menu ID for review. Through the above implementation, firstly, the acquired business applications are developed by different development sources, avoiding the problem of low development efficiency and consequently low review efficiency caused by a single development pattern developing multiple business applications, as well as the problem of complex coupling between different business applications; secondly, during the review process, different business applications are sent to different review processes for review, which not only avoids the need to resolve the coupling problem between business applications during review but also effectively improves the review efficiency of business applications.

[0044] Example 2 This application provides a business application review method in Embodiment 2, which optimizes the "determining the review process associated with each menu ID" in Embodiment 1. It should be noted that for parts not detailed in this embodiment, please refer to the descriptions in other embodiments. The method includes: S210. Obtain business applications developed from different development sources in parallel, and create menu IDs for each of the business applications.

[0045] S221. Determine the application page URL of the business application corresponding to each menu ID.

[0046] It should be noted that, in order to facilitate the management and maintenance of the acquired business applications, this embodiment intends to demonstrate the acquired business applications; each business application has its own unique URL (Uniform Resource Locator), which is also the URL of the corresponding business application, and the URL corresponding to the business application is recorded as the application page URL; each business application has its own unique menu ID, and since each business application also has its own unique application page URL, the menu ID of each business application has its own unique application page URL.

[0047] Specifically, the URL of the application page corresponding to each business application is determined by the menu ID.

[0048] S222. Display the corresponding business applications based on the URLs of the application pages to obtain the business application menu.

[0049] For example, one of the application page URLs can be used to display the corresponding business applications; the displayed business applications can be combined into an application menu, and this menu is called the business application menu.

[0050] Specifically, the application page URL1 for the operation position application displays the operation position application, the application page URL2 for the consumer voucher activity application displays the consumer voucher activity application, the application page URL3 for the task activity application displays the task activity application, the application page URL4 for the outbound call application displays the outbound call application, and the application page URL5 for the message application displays the message application; the above-mentioned combination of various business applications forms the business application menu.

[0051] The above implementation allows for the display of corresponding business applications via the application page URL, improving the ease of maintaining business applications.

[0052] S223. Determine the review process associated with each menu ID corresponding to each business application in the business application menu.

[0053] S230. Submit each of the aforementioned business applications to the review process associated with the menu ID corresponding to each of the aforementioned business applications for review.

[0054] Example 3 This application provides a business application review method in Embodiment 3, which optimizes the review process of "determining the review process associated with the menu IDs corresponding to each business application in the business application menu" in Embodiment 2. It should be noted that for parts not detailed in this embodiment, please refer to the descriptions in other embodiments. The method includes: S310. Obtain business applications developed from different development sources in parallel, and create menu IDs for each of the business applications.

[0055] S321. Determine the application page URL of the business application corresponding to each menu ID.

[0056] S322. Display the corresponding business applications based on the URLs of the application pages to obtain the business application menu.

[0057] S323A. In response to the fact that the number of service applications in the service application menu is not greater than a preset number threshold, determine whether an application submission instruction has been received.

[0058] It should be noted that the overall computing resources of the unified framework for project management business applications are limited, meaning that the number of business applications that the unified framework can process in parallel within a certain time is limited. Therefore, before submitting each business application in the application menu to the review process, it is necessary to determine whether the number of each business application in the application menu is too large. If it is not too large, then submit the business applications in the application menu. If it is too large, a certain number of business applications can be randomly selected and submitted first.

[0059] Specifically, to determine whether the number of each business application in the application menu is too large, this embodiment presets a quantity threshold based on historical experience data. If the number of each business application in the application menu is not greater than the quantity threshold, then the number of each business application in the application menu is not too large.

[0060] It should also be noted that, if it is determined that the number of applications for each business in the application menu is not excessive, an application submission instruction from the business personnel is required before each application in the application menu can be submitted to the corresponding review process.

[0061] S323B, If so, determine the review process associated with each menu ID corresponding to the aforementioned business application.

[0062] It should be noted that, taking one of the business applications as an example, the menu ID of the business application is also associated with a corresponding review process. The business application and the review process can be linked through the menu ID, thus achieving a one-to-one correspondence between the business application and the review process. The business application can be directly submitted to the corresponding review process for review through the menu ID.

[0063] By implementing the above measures, the number of business applications sent for review at one time is limited, which helps to prevent excessive pressure on computing resources and can effectively improve the review efficiency of subsequent business applications.

[0064] S330. Submit each of the aforementioned business applications to the review process associated with the menu ID corresponding to each of the aforementioned business applications for review.

[0065] Example 4 This application provides a business application review method in Embodiment 4, which optimizes the "submitting each business application to the review process associated with the menu ID corresponding to each business application for review" in Embodiment 2. It should be noted that for parts not detailed in this embodiment, please refer to the descriptions in other embodiments. The method includes: S410. Obtain business applications developed from different development sources in parallel, and create menu IDs for each of the business applications.

[0066] S421. Determine the application page URL of the business application corresponding to each menu ID.

[0067] S422. Display the corresponding business applications based on the URLs of the application pages to obtain the business application menu.

[0068] S423. Determine the review process associated with each menu ID corresponding to each business application in the business application menu.

[0069] S431. Determine the URL of the review page corresponding to each of the aforementioned review processes.

[0070] Just as a business application corresponds to a URL, each review process also has a pre-defined URL (Uniform Resource Locator), and the URL corresponding to each review process is recorded as the review page URL.

[0071] S432. Submit each of the aforementioned business applications to the review page URL corresponding to the corresponding menu ID to obtain the review process menu.

[0072] It should be noted that, taking one of the business applications as an example, the menu ID corresponding to the business application corresponds to both the application page URL associated with the business application and the review page URL associated with the review process.

[0073] Specifically, taking one of the business applications as an example, by submitting the business application to the review page URL corresponding to the menu ID of the business application, that is, submitting the business application to a review process corresponding to the business application; the review processes containing the corresponding business applications together form the review process menu.

[0074] S433. Review each of the business applications in the review process menu; wherein, the business application and the corresponding review page URL have the same menu ID.

[0075] For example, one of the review processes in the review process menu is used to review the corresponding business application. The review process and the business application are one-to-one and they have the same menu ID.

[0076] By implementing the above methods, the corresponding business applications can be reviewed in the review page URL, which facilitates the maintenance and display of business applications in the review page URL, thereby effectively improving the efficiency of subsequent business application review.

[0077] Example 5 This application provides a business application review method in Embodiment 5, which supplements the method described in Embodiment 1. It should be noted that for parts not detailed in this embodiment, please refer to the descriptions in other embodiments. The method includes: S510. Obtain business applications developed from different development sources in parallel, and create menu IDs for each of the business applications.

[0078] S521. Determine the application page URL of the business application corresponding to each menu ID.

[0079] S522. Display the corresponding business applications based on the URLs of the application pages to obtain the business application menu.

[0080] S523. Determine the review process associated with each menu ID corresponding to each business application in the business application menu.

[0081] S531. Determine the URL of the review page corresponding to each of the aforementioned review processes.

[0082] S532. Submit each of the aforementioned business applications to the review page URL corresponding to the corresponding menu ID to obtain the review process menu.

[0083] S533. Review each of the business applications in the review process menu; wherein, the business application and the corresponding review page URL have the same menu ID.

[0084] S540. Hides the business application menu and / or the review process menu.

[0085] It should be noted that, see Figure 2After a business application is developed, it needs to go through three stages before it can be used by users. These three stages are: project management stage, business configuration stage, and customer deployment stage. The project management stage corresponds to the method shown in this embodiment, and specifically includes two sub-stages: online business application and business application review.

[0086] Referring to the above embodiments, during the execution of this method, corresponding transaction menus will be generated, such as the business application menu obtained in S522 and the review process menu obtained in S532. Both of these menus belong to the project management stage. In order to facilitate the unified maintenance of transactions in the project management stage, the business application menu and / or review process menu are displayed for the subsequent business configuration stage. In this embodiment, the business application menu and / or review process menu are not displayed by hiding them.

[0087] By implementing the above measures, the business application menu and the review process menu are hidden during the review stage, which makes it easier to ensure that the application business is maintained uniformly during the review stage.

[0088] Example 6 This application provides a business application review method in Embodiment Six, which supplements the method described in Embodiment One. It should be noted that for parts not detailed in this embodiment, please refer to the descriptions in other embodiments. The method includes: S610. Obtain business applications developed from different development sources in parallel, and create menu IDs for each of the business applications.

[0089] S620. Determine the review process associated with each of the menu IDs.

[0090] S630. Submit each of the aforementioned business applications to the review process associated with the menu ID corresponding to each of the aforementioned business applications for review.

[0091] S640. In response to the approval of the service application, the service application is configured.

[0092] It should be noted that the business application is a preliminary development of the function. In order to make the function applicable to specific business, the business application needs to be specifically configured. Business configuration means changing the behavior, rules or performance of the function by modifying some external parameters, switches or files without modifying the program code or redeploying the program, so as to adapt to specific business needs.

[0093] Specifically, taking a business application as an example, after the application is approved, the external parameters of the application are modified according to the specific business it corresponds to, thereby realizing the business configuration of the application. The specific business it corresponds to includes, but is not limited to, operations slot applications, consumer voucher activity applications, task activity applications, message applications, etc. The external parameters that need to be configured include, but are not limited to, database connection, log level, server port, command line parameters, etc.

[0094] Through the above implementation, business applications can be configured after approval, which facilitates the efficiency of subsequent business deployment and use.

[0095] It should be understood that although the steps in the flowcharts of the embodiments described above are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the embodiments described above may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages of other steps.

[0096] Example 7 Based on the same inventive concept, this embodiment also provides a business application review apparatus for implementing the business application review method described above. The solution provided by this apparatus is similar to the implementation scheme described in the above method; therefore, the specific limitations in one or more business application review apparatus embodiments provided below can be found in the limitations of the business application review method described above, and will not be repeated here.

[0097] In this embodiment, as Figure 3 As shown, a business application review device is provided, including: The ID creation module is used to retrieve business applications from different development sources in parallel and create menu IDs for each of the business applications. The process association module is used to determine the review process associated with each of the menu IDs. The application review module is used to submit each of the aforementioned business applications to the review process associated with the menu ID corresponding to each business application for review. Each module in the aforementioned business application review device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in a computer device, or stored in the memory of a computer device as software, so that the processor can call and execute the corresponding operations of each module.

[0098] It should be noted that this embodiment acquires business applications developed by different development sources in parallel, creates a menu ID for each business application, determines the review process associated with each menu ID, and submits each business application to the review process associated with its corresponding menu ID for review. Through the above implementation, firstly, the acquired business applications are developed by different development sources, avoiding the problem of low development efficiency and consequently low review efficiency caused by a single development pattern developing multiple business applications, as well as the problem of complex coupling between different business applications; secondly, during the review process, different business applications are sent to different review processes for review, which not only avoids the need to resolve the coupling problem between business applications during review but also effectively improves the review efficiency of business applications.

[0099] In an optional embodiment, determining the review process associated with each of the menu IDs includes: Determine the application page URL for each of the menu IDs corresponding to the business application; Based on the URLs of the application pages, the corresponding business applications are displayed to obtain the business application menu; Determine the review process associated with each menu ID corresponding to each business application in the business application menu.

[0100] In an optional embodiment, determining the review process associated with each menu ID corresponding to each business application in the business application menu includes: In response to the fact that the number of business applications in the business application menu is not greater than a preset number threshold, determine whether an application submission instruction has been received; If so, determine the review process associated with each menu ID corresponding to the aforementioned business application.

[0101] In an optional embodiment, submitting each of the business applications to the review process associated with the menu ID corresponding to each business application for review includes: Determine the URL of the review page corresponding to each of the aforementioned review processes; Submit each of the aforementioned business applications to the review page URL corresponding to the corresponding menu ID to obtain the review process menu; The business applications described in the review process menu are reviewed; wherein, the business application and the corresponding review page URL have the same menu ID.

[0102] In an optional embodiment, the business application review device further includes: The menu blocking module is used to block the business application menu and / or the review process menu.

[0103] In an optional embodiment, the business application review device further includes: The business configuration module is used to configure the business application in response to the approval of the business application.

[0104] Example 8 In this embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be as follows. Figure 4 As shown, the computer device includes a processor, memory, and a network interface connected via a system bus. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system, computer programs, and a database. The internal memory provides an environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The database stores data. The network interface communicates with external terminals via a network connection. When executed by the processor, the computer program implements a business application review method.

[0105] Those skilled in the art will understand that Figure 4 The structure shown is merely a block diagram of a portion of the structure related to the present disclosure and does not constitute a limitation on the computer device to which the present disclosure is applied. A specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0106] Example 9 In this embodiment, a computer-readable storage medium is provided, such as... Figure 5 As shown, a computer program is stored thereon, and when the computer program is executed by the processor, it implements the steps in the above-described method embodiments.

[0107] Example 10 In this embodiment, a computer program product is provided, including a computer program that, when executed by a processor, implements the steps in the above-described method embodiments.

[0108] It should be noted that the information collected is information and data authorized by the user or fully authorized by all parties, and the collection, storage, use, processing, transmission, provision, disclosure and application of the relevant data all comply with the relevant laws, regulations and standards of the relevant countries and regions, necessary confidentiality measures have been taken, and it does not violate public order and good morals. Corresponding operation portals are provided for users to choose to authorize or refuse.

[0109] Those skilled in the art will understand that all or part of the processes in the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. Any references to memory, databases, or other media used in the embodiments provided in this disclosure can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this disclosure may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this disclosure may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, etc., and are not limited to these.

[0110] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0111] The embodiments described above are merely illustrative of several implementations of this disclosure, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent disclosure. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this disclosure, and these all fall within the protection scope of this disclosure. Therefore, the protection scope of this disclosure should be determined by the appended claims.

Claims

1. A method for reviewing business applications, characterized in that, include: Retrieve business applications developed from different development sources in parallel, and create menu IDs for each of the business applications; Determine the review process associated with each of the menu IDs; Each of the aforementioned business applications will be submitted to the review process associated with the menu ID corresponding to each business application for review.

2. The method according to claim 1, characterized in that, The process for determining the review process associated with each menu ID includes: Determine the application page URL for each of the menu IDs corresponding to the business application; Based on the URLs of the application pages, the corresponding business applications are displayed to obtain the business application menu; Determine the review process associated with each menu ID corresponding to each business application in the business application menu.

3. The method according to claim 2, characterized in that, The step of determining the review process associated with the menu ID corresponding to each business application in the business application menu includes: In response to the fact that the number of business applications in the business application menu is not greater than a preset number threshold, determine whether an application submission instruction has been received; If so, determine the review process associated with each menu ID corresponding to the aforementioned business application.

4. The method according to claim 2, characterized in that, The step of submitting each of the aforementioned business applications to the review process associated with the menu ID corresponding to each of the aforementioned business applications for review includes: Determine the URL of the review page corresponding to each of the aforementioned review processes; Each of the aforementioned business applications is submitted to the review page URL corresponding to the corresponding menu ID to obtain the review process menu; The business applications described in the review process menu are reviewed; wherein, the business application and the corresponding review page URL have the same menu ID.

5. The method according to claim 4, characterized in that, Also includes: The business application menu and / or the review process menu are hidden.

6. The method according to claim 1, characterized in that, Also includes: In response to the approval of the service application, the service application is configured.

7. A business application review device, characterized in that, The device includes: The ID creation module is used to retrieve business applications from different development sources in parallel and create menu IDs for each of the business applications. The process association module is used to determine the review process associated with each of the menu IDs. The application review module is used to submit each of the aforementioned business applications to the review process associated with the menu ID corresponding to each of the aforementioned business applications for review.

8. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 6.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 6.

10. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 6.

Images