Application program generation method, application program operation method, application program generation device, application program operation device and equipment

Abstract

The invention provides an application program generation method, an application program operation method, devices and equipment, and the method comprises the steps: responding to an application development request for a business process, and determining a plurality of business fields related to the business process; wherein the business process comprises at least one process node; for any flow node, responding to a selection operation of a user, and obtaining a service entity API matched with the flow node in at least one service field; wherein the service entity API matched with the process node is used for calling a corresponding program to execute a service function required by the process node; and according to the business process, arranging each business entity API to obtain a target application program corresponding to the business process. Therefore, the application development request of the business process can be flexibly responded, and the application program meeting the business requirement can be quickly constructed; and the service process can be customized and configured according to the actual demand of the user, so that the flexibility and the expandability of the system are improved.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to an application generation method, an application running method, a device and equipment. Background Art

[0002] In the business processes of some industries, there may be multiple scenarios. For example, in the loan opening and issuance process in the banking industry, there are multiple scenarios, and each scenario is considered based on different customer needs, credit status, product types, etc.

[0003] However, in the related art, when developing an application for a business process, each scenario needs to develop a set of functions corresponding to the business process (such as loan account opening and issuance functions), which may cause the following problems:

[0004] (1) A large amount of duplication and redundancy in functions;

[0005] (2) Rigid processes make it difficult to adapt to different scenarios and changes in customer needs, resulting in the system being unable to flexibly respond to new business products or services, limiting the industry's business innovation capabilities;

[0006] (3) For each customer, a large amount of customized development work may be required to meet their specific business needs and business processes, which not only increases the implementation cost, but also prolongs the project delivery cycle and reduces customer satisfaction. Summary of the invention

[0007] The present application provides an application generation method to solve one of the technical problems in the related art at least to a certain extent. The technical solution of the present application is as follows:

[0008] According to a first aspect of an embodiment of the present application, there is provided a method for generating an application program, comprising:

[0009] In response to an application development request for a business process, determining a plurality of business areas involved in the business process; wherein the business process includes at least one process node;

[0010] For any of the process nodes, in response to a user's selection operation, obtaining at least one business entity API in the business domain that matches the process node; wherein the API that matches the process node is used to call a corresponding program to execute a business function required by the process node;

[0011] According to the business process, each of the business entity APIs is arranged to obtain a target application corresponding to the business process.

[0012] According to a second aspect of an embodiment of the present application, a method for running an application is provided, the method comprising:

[0013] In response to a first user's request to execute a target business process, obtaining a target business product applied for by the first user;

[0014] According to the product identifier of the target business product, obtaining the value of the product parameter of the target business product;

[0015] A first target application program obtained by the method described in the embodiment of the first aspect is configured based on the value of the product parameter;

[0016] The configured first target application is run to execute the target business process requested by the first user.

[0017] According to a third aspect of an embodiment of the present application, there is provided an application generating device, including:

[0018] A determination module, configured to determine, in response to an application development request for a business process, a plurality of business areas involved in the business process; wherein the business process includes at least one process node;

[0019] An acquisition module, for acquiring, for any of the process nodes, a business entity API matching the process node in at least one of the business domains in response to a user's selection operation; wherein the API matching the process node is used to call a corresponding program to execute a business function required by the process node;

[0020] The orchestration module is used to orchestrate each of the business entity APIs according to the business process to obtain a target application corresponding to the business process.

[0021] According to a fourth aspect of an embodiment of the present application, there is provided an application program running device, including:

[0022] A first acquisition module, configured to acquire a target business product applied for by a first user in response to a request by the first user to execute the target business process;

[0023] A second acquisition module, used to acquire the value of the product parameter of the target business product according to the product identifier of the target business product;

[0024] A configuration module, configured to configure the first target application obtained by the method according to any one of claims 1 to 5 based on the value of the product parameter;

[0025] The running module is used to run the configured first target application to execute the target business process requested by the first user.

[0026] According to the fifth aspect of the embodiments of the present application, an electronic device is provided, comprising: a processor; a memory for storing instructions executable by the processor; wherein the processor is configured to execute the instructions to implement the application generation method as described in the first aspect embodiment of the present application, or the application running method as described in the second aspect embodiment.

[0027] According to the sixth aspect of the embodiments of the present application, a computer-readable storage medium is provided. When the instructions in the computer-readable storage medium are executed by the processor of an electronic device, the electronic device can execute the application generation method described in the embodiment of the first aspect of the present application, or the application running method described in the embodiment of the second aspect.

[0028] According to the seventh aspect of the embodiments of the present application, a computer program product is provided, including: a computer program, which, when executed by a processor, implements the application generation method described in the first aspect of the embodiments of the present application, or the application running method described in the second aspect of the embodiments.

[0029] The technical solution provided by the embodiments of the present application brings at least the following beneficial effects:

[0030] In response to an application development request for a business process, multiple business areas involved in the business process are determined; wherein the business process includes at least one process node; for any process node, in response to a user's selection operation, a business entity API matching the process node in at least one business field is obtained; wherein the business entity API matching the process node is used to call the corresponding program to execute the business function required by the process node; according to the business process, each business entity API is orchestrated to obtain a target application corresponding to the business process. Thus, it is possible to flexibly respond to application development requests for business processes and quickly build applications that meet business needs; it is also possible to customize and configure business processes according to actual user needs, thereby improving the flexibility and scalability of the system; and the division of specific business functions, that is, the attribution or division of business entity APIs, is based on the business fields to which they belong, which can achieve decoupling and collaboration between different business fields, so that business processes can more easily adapt to changes and updates in the business environment.

[0031] It should be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] The drawings herein are incorporated into the specification and constitute a part of the specification, illustrate embodiments consistent with the present application, and together with the specification are used to explain the principles of the present application, and do not constitute an improper limitation on the present application.

[0033] Figure 1 It is a flowchart of an application generation method shown in an embodiment of the present application;

[0034] Figure 2 is a flowchart of an application generation method shown in another embodiment of the present application;

[0035] Figure 3 is a flowchart of an application generation method shown in another embodiment of the present application;

[0036] Figure 4 is a flowchart of an application program running method shown in another embodiment of the present application;

[0037] Figure 5 is a structural diagram of an application generating device shown in another embodiment of the present application;

[0038] Figure 6 is a structural diagram of an application generating device shown in another embodiment of the present application;

[0039] Figure 7 It is a schematic diagram of the structure of an electronic device shown in an exemplary embodiment of the present application. DETAILED DESCRIPTION

[0040] In order to enable ordinary persons in the art to better understand the technical solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the accompanying drawings.

[0041] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. On the contrary, they are merely examples of devices and methods consistent with some aspects of the present application as detailed in the attached claims.

[0042] It should be noted that in the technical solution of this application, the collection, storage, use, processing, transmission, provision and application of user personal information involved are all carried out with the user's consent, and are in compliance with relevant laws and regulations and do not violate public order and good morals.

[0043] The following describes the application generation method, application running method, device and equipment of the embodiments of the present application with reference to the accompanying drawings.

[0044] Figure 1It is a flowchart of an application generation method shown in an embodiment of the present application.

[0045] The embodiment of the present application takes the application generation method being configured in an application generation device as an example. The application generation device can be applied to any electronic device so that the electronic device can perform the application generation function.

[0046] Among them, the electronic device can be any device with computing capabilities, such as a PC (Personal Computer), a mobile terminal, a server, etc. The mobile terminal can be, for example, a vehicle-mounted device, a mobile phone, a tablet computer, a personal digital assistant, a wearable device, and other hardware devices with various operating systems, touch screens and / or display screens.

[0047] like Figure 1 As shown, the application generation method may include the following steps:

[0048] Step 101 : In response to an application development request for a business process, a plurality of business areas involved in the business process are determined.

[0049] The business process may include at least one process node. It should be noted that the present application does not limit the number of process nodes included in the business process, and the process nodes and the number of process nodes of the business process may be set according to actual needs.

[0050] The business domain may be a specification of the scope of information involved in a business process and / or services provided.

[0051] As an example, the business process of loan account opening and issuance process is used as an example for explanation. The process nodes in the loan account opening and issuance process are in the following order: legality check → loan account creation → fund processing → asynchronous accounting of the bank accounting system; the information involved in the loan account opening and issuance process may include loan product information, loan account information, loan interest calculation and recovery information, loan accounting sub-account information, deposit account information, internal account information, etc. in various scenarios. The business domain may include product operation domain, account information domain, interest calculation and recovery domain, accounting sub-account domain, deposit subsystem, internal account subsystem, etc., among which:

[0052] 1. Product operation domain

[0053] The information involved may include, for example, product parameters of various loan products (referred to as business products in this application);

[0054] Its corresponding services include, for example, product parameter query API (Application Programming Interface), product parameter maintenance API, and product parameter synchronization API;

[0055] 2. Account information field

[0056] The information involved may include, for example, basic account information, issuance information, guarantor information, joint borrower information, entrusted payment information, etc.

[0057] Its corresponding services, such as providing external APIs based on the information related to the domain;

[0058] 3. Interest-bearing recovery domain

[0059] The information involved may include, for example, interest calculation information, interest subsidy account information, repayment information, repayment plan information, multiple repayment account information, accounting information, entrustment information, etc.;

[0060] Its corresponding services, such as providing external APIs based on the information related to the domain;

[0061] 4. Accounting sub-domain

[0062] The information involved may include, for example, principal account, interest account, transaction flow information, account mapping information, etc.

[0063] Its corresponding services, such as providing external APIs based on the information related to the domain;

[0064] 5. Deposit Subsystem

[0065] The information involved may include, for example, deposit account information under multiple deposit subsystems;

[0066] Its corresponding services, such as the withdrawal, deposit, freeze, control, query and other APIs provided by each subsystem;

[0067] 6. Internal User System

[0068] The information involved may include, for example, internal account information under multiple internal account subsystems;

[0069] Its corresponding services, such as withdrawal, deposit, query and other APIs for internal account provided by each internal account subsystem.

[0070] In an embodiment of the present application, in response to an application development request for a business process, multiple business areas involved in the business process may be determined.

[0071] As an example, when a user needs to develop an application for a business process, he can click the "Application Development" control in the relevant operation page, so that the execution subject of this application can respond to the application development request, and in response to the user's first operation, obtain multiple business areas involved in the business process corresponding to the application development request. Among them, the first operation can include but is not limited to input operation, click operation, sliding operation, etc., and this application does not limit this.

[0072] Step 102: for any process node, in response to a user's selection operation, obtain a business entity API matching the process node in at least one business domain.

[0073] The business entity API matching the process node is used to call the business functions required by the corresponding program execution process node. It should be noted that each business entity API can be highly cohesive and loosely coupled, that is, there may be no dependency between the business entity APIs.

[0074] It should also be noted that the number of business entity APIs matching the process node can be but is not limited to one, and this application does not impose any restrictions on this.

[0075] It is understandable that the business entity APIs in each business field can be displayed through the display page, so that for any process node, in response to the user's selection of the business entity APIs in each business field in the display page, a business entity API in at least one business field that matches the process node can be obtained.

[0076] Step 103: Arrange each business entity API according to the business process to obtain a target application corresponding to the business process.

[0077] In an embodiment of the present application, after obtaining the business entity APIs matching each process node, each business entity API may be orchestrated according to the business process, thereby obtaining a target application corresponding to the business process.

[0078] Optionally, the target application may apply at least one business product.

[0079] As an example, assuming that the business process is a loan account opening and issuance process, the corresponding target application can be applied to business products such as general loans, entrusted loans, mortgage loans, consumer loans, corporate loans, etc. This application does not impose any restrictions on this.

[0080] The application generation method of the embodiment of the present application determines the multiple business fields involved in the business process by responding to the application development request for the business process; wherein the business process includes at least one process node; for any process node, in response to the user's selection operation, obtains the business entity application programming interface API that matches the process node in at least one business field; wherein the API that matches the process node is used to call the corresponding program to execute the business function required by the process node; according to the business process, each business entity API is arranged to obtain the target application corresponding to the business process. Thus, it is possible to flexibly respond to the application development request of the business process and quickly build an application that meets the business needs; it is also possible to customize and configure the business process according to the actual needs of the user, thereby improving the flexibility and scalability of the system; and the division of specific business functions, that is, the attribution or division of the business entity API, is based on the business field to which it belongs, which can achieve decoupling and collaboration between different business fields, so that the business process can more easily adapt to changes and updates in the business environment.

[0081] In the case where the target application is applied to at least one business product, in order to clearly illustrate how, in the above-mentioned embodiment of the present application, for any process node, a business entity API matching the process node in at least one business field is obtained in response to a user's selection operation, the present application also proposes an application generation method.

[0082] Figure 2 It is a flowchart of an application generation method shown in another embodiment of the present application.

[0083] like Figure 2 As shown, based on the above embodiment of the present application, the application generation method may further include the following steps:

[0084] Step 201 : for any business product, determine a target business field corresponding to a process node and a business product from multiple business fields.

[0085] It is understandable that for any business product, the business product may involve or be associated with one or some business areas in multiple business areas at the process node. As an example, taking the business process as a process node including a legality check, when the business product is a mortgage loan, the business areas involved in the process node include the account information domain and the interest calculation and recovery domain; when the business product is an enterprise loan, the business areas involved in the process node include the account information domain, the interest calculation and recovery domain, and the internal account subsystem.

[0086] It should be noted that the above examples of business fields involved in or associated with business products are merely illustrative.

[0087] In an embodiment of the present application, for any business product, a target business domain corresponding to (or associated with) a process node and a business product can be determined from multiple business domains. As an example, for any business product, a target business domain corresponding to a process node and a business product can be determined from multiple business domains in response to a user's selection operation.

[0088] Step 202: In response to a selection operation by the user, a corresponding target business domain API is determined from at least one business domain API under the target business domain.

[0089] Among them, each business domain API under the target business domain can be used to standardize and divide the business functions belonging to each business entity API.

[0090] As an example, assuming that the target business domain is the "account information domain", the business domain APIs under the target business domain may include, for example, the "loan cancellation processing API", "account information domain public query API", "promissory note creation and closure API", "account maintenance management API", "guarantor guarantee maintenance management API", and "test loan account information API", among which the business functions of the "loan cancellation processing API" specification and the various business entity APIs divided include loan cancellation, loan cancellation rollback, loan correction check, etc., the business functions of the "account information domain public query API" specification and the various business entity APIs divided include teller operations, asset transaction instruction operations, miscellaneous parameter operations, etc., the business functions of the "promissory note creation and closure API" specification and the various business entity APIs divided include promissory note creation, closure and legality check, etc., the business functions of the "account maintenance management API" specification and the various business entity APIs divided include change maintenance related processing, the business functions of the "guarantor guarantee maintenance management API" specification and the various business entity APIs divided include guarantor guarantee inspection, addition, modification, deletion, etc., and the business functions of the "test loan account information API" specification and the various business entity APIs divided include testing loan account information.

[0091] It should be noted that the above examples are merely illustrative, and in actual applications, specific business domains and business domain APIs under the business domains may be divided and set as needed.

[0092] In the embodiment of the present application, in response to a selection operation of a user, a target business domain API corresponding to a process node and a business product may be determined from at least one business domain API under the target business domain.

[0093] It should also be noted that the number of target business domain APIs corresponding to process nodes and business products can be but is not limited to one, and this application does not impose any restrictions on this.

[0094] Step 203: Filter out a business entity API that matches both the business product and the process node from at least one business entity API included in the target business domain API.

[0095] Among them, the business entity API can be pre-defined and used to operate or manage the corresponding business entity to achieve specific business functions, such as query, modification, deletion, etc., and this application does not impose any restrictions on this.

[0096] In the embodiment of the present application, each business domain API may be obtained by encapsulating at least one corresponding business entity API. It should be noted that each business entity API may be highly cohesive and loosely coupled, that is, there may be no dependency between the business entity APIs.

[0097] In the embodiment of the present application, a business entity API that matches both the business product and the process node can be screened out from at least one business entity API included in the target business domain API.

[0098] As an example, in response to a user's selection operation, a business entity API matching both the business product and the process node may be acquired from at least one business entity API included in the displayed target business domain API.

[0099] In a possible implementation method of an embodiment of the present application, for any business product, after determining the business entity API that matches the business product in each process node, at least one first parameter associated with the business product can be determined based on the interaction parameters in the business entity API that matches the business product in each process node; based on the at least one first parameter, a parameter definition table is queried to determine the product parameters that need to be configured for the business product from the at least one first parameter; and the product parameters that need to be configured for the business product are saved.

[0100] The parameter definition table may be pre-set and may indicate whether each parameter needs to be configured.

[0101] Among them, the number of product parameters can be but is not limited to one, and this application does not impose any restrictions on this.

[0102] Specifically, for any business product, the interaction parameters in the business entity API that matches the business product in each process node can be determined as at least one first parameter associated with the business product; based on each first parameter, the parameter definition table is queried, and the first parameter that indicates the need to be configured in each first parameter is determined as the product parameter that needs to be configured for the business product, and a correspondence between the business product and the product parameter can be established, and the correspondence can be saved for subsequent data use.

[0103] The application generation method of this embodiment determines the target business domain corresponding to the process node and the business product from multiple business domains for any business product; determines the corresponding target business domain API from at least one business domain API under the target business domain in response to the user's selection operation; and selects the business entity API that matches both the business product and the process node from at least one business entity API included in the target business domain API. Thus, the division of specific business functions, that is, the attribution or division of business entity APIs, is not only based on the business domain to which they belong, but also based on the functions under each business domain to which they belong, so that users can customize and configure the specific functions required in the business process according to actual needs, thereby meeting the personalized needs of users, and can improve the maintainability, scalability and flexibility of the system, so that business products can more easily adapt to changes and updates in business processes.

[0104] In order to clearly explain how, in the above embodiments of the present application, each business entity API is arranged according to the business process to obtain a target application corresponding to the business process, the present application also proposes an application generation method.

[0105] Figure 3 It is a flowchart of an application generation method shown in another embodiment of the present application.

[0106] like Figure 3 As shown, based on the above embodiment of the present application, the application generation method may further include the following steps:

[0107] Step 301 , for any target business domain API of any process node, encapsulate the business entity API of each business product matching the process node under the target business domain API to obtain the sub-business module corresponding to the process node in the target business domain API.

[0108] It can be understood that when there are multiple business entity APIs matching the process node, for any target business domain API of any process node, there may be a business entity API matching the process node under the target business domain API, which is associated or matched with at least two business products, that is, there is a business entity API used to implement corresponding functions under at least two business products. For example, assuming that the process node is "Legality Check" and the target business domain API is "Account Information Domain Legitimacy Check API", when the business entity API that matches the process node "Legality Check" under "Account Information Domain Legitimacy Check API" is "Loan Guarantor Information Entity Check API", this business entity API can be used to implement the function of checking the legality of loan guarantor information under business products such as general loans and consumer loans; for another example, assuming that the process node is "Legality Check" and the target business domain API is "Account Information Domain Creation API", when the business entity API that matches the process node "Legality Check" under "Account Information Domain Creation API" is "Loan Note Basic Information Entity Creation API", this business entity API can be used to implement the function of creating the basic information of loan notes for loan users under business products such as general loans, consumer loans, mortgage loans, and corporate loans.

[0109] In order to reduce the code duplication rate of business entity APIs that implement the same function in an application, as a possible implementation method, in response to the existence of a target business entity API in multiple business entity APIs that match the process node under the target business domain API, each business product associated with the process node is abstracted into a target class, wherein the target business entity API is associated with at least two business products; for any business product associated with the process node, based on the business entity API and the target class that match both the business product and the process node, a subclass of the business product is created under the process node; based on the target class and each subclass, the sub-business module corresponding to the process node in the target business domain API is determined.

[0110] Specifically, when a target business entity API is associated with at least two business products among multiple business entity APIs matching the process node under the target business domain API, a target class can be defined based on the product identifiers of each business product associated with the process node to abstract the specific implementation functions under each business product associated with the process node to form a high-level class; for any business product associated with the process node, the business entity API matching the business product and the process node, that is, the specific implementation of the business product under the process node, can be used to generate a subclass that inherits the target class, so that the subclass can be referenced by referencing the parent class in subsequent program calls, thereby realizing the specific functions corresponding to the business product corresponding to the subclass; finally, based on the target class and each subclass, the business entity API matching the process node under the target business domain API of each business product is encapsulated to obtain the sub-business module corresponding to the process node in the target business domain API.

[0111] Therefore, the redundancy of the generated application code is reduced through abstraction and integration, and the maintainability and scalability of the code can be effectively improved; each business product inherits the target class and implements specific functions, making the business logic clearer and modular, and the sub-business module handles different types of business products through polymorphism, making the code more flexible and easy to manage.

[0112] It should be noted that, for any target business domain API of any process node, if there is no business entity API that matches the process node under the target business domain API and is associated or matched with at least two business products, abstract classes and subclasses can be used for encapsulation, and strategy patterns, factory patterns, etc. can also be used to encapsulate the business entity API of each business product that matches the process node under the target business domain API.

[0113] Step 302 , integrating the sub-business modules corresponding to the target business domain APIs of the process nodes to obtain the business modules corresponding to the process nodes.

[0114] In order to accurately obtain the business module corresponding to the process node, as a possible implementation method, the following steps can be used to implement the process:

[0115] Step 3021, obtaining the business logic sequence of the sub-business modules corresponding to each target business domain API under the process node.

[0116] As an example, in response to the user's input operation, the business logic sequence of the sub-business modules corresponding to each target business domain API under the process node can be obtained.

[0117] As another example, the business logic order of the sub-business modules corresponding to each target business domain API under the process node may be determined based on the sorting order of each business domain API under the process node preset by the user.

[0118] As an example, assuming that the process node is "legality check", the business domain APIs under this process node may include "account information domain legality check API", "interest calculation and recovery domain legality check API", "accounting sub-account domain legality check API", "deposit subsystem legality check API", and "internal account subsystem legality check API". The target business domain APIs under this process node include "account information domain legality check API", "interest calculation and recovery domain legality check API", "accounting sub-account domain legality check API", and "deposit subsystem legality check API". The sorting order of the business domain APIs under the process node pre-set by the user is: "account information domain legality check API" → "accounting sub-account domain legality check API" → "interest calculation and recovery domain legality check API" → "internal account subsystem legality check API" → "deposit subsystem legality check API", and the business logic order of the sub-business modules corresponding to the target business domain APIs under the process node is: "account information domain legality check API" → "accounting sub-account domain legality check API" → "interest calculation and recovery domain legality check API" → "deposit subsystem legality check API".

[0119] Step 3022, according to the business logic sequence, set the calling sequence between the sub-business modules under the process node.

[0120] Step 3023, configure the business call interface corresponding to the process node, so as to associate the sub-business modules under the process node through the business call interface to obtain the business module corresponding to the process node.

[0121] In this way, the business modules corresponding to the process nodes can be effectively obtained, with clear logic, which is easy to maintain and expand.

[0122] Step 303: Building a target application based on each business module in accordance with the order of each process node in the business process.

[0123] The application generation method of the embodiment of the present application, through any target business domain API of any process node, encapsulates the business entity API of each business product under the target business domain API that matches the process node, and obtains the sub-business module corresponding to the process node in the target business domain API; integrates the sub-business modules corresponding to each target business domain API of the process node, and obtains the business module corresponding to the process node; and builds the target application based on each business module according to the order of each process node in the business process. In this way, it is easy to cope with changes in business processes and updates of business products. When business processes or business products change, the system only needs to update the corresponding sub-business modules or business modules without the need to reconstruct the entire application; greatly improves the flexibility and scalability of the system and reduces maintenance costs. And because each sub-business module and business module is independently developed, it is possible to achieve function reuse and error isolation, improve the reliability and stability of the system, and ensure the smooth execution of business processes.

[0124] The above is an embodiment of a method for generating an application program, and the following is an embodiment of a method for running an application program.

[0125] Figure 4 It is a flowchart of an application running method shown in another embodiment of the present application.

[0126] The embodiment of the present application takes the application running method being configured in an application running device as an example. The application running device can be applied to any electronic device so that the electronic device can execute the application running function.

[0127] Among them, the electronic device can be any device with computing capabilities, such as a PC (Personal Computer), a mobile terminal, a server, etc. The mobile terminal can be, for example, a vehicle-mounted device, a mobile phone, a tablet computer, a personal digital assistant, a wearable device, and other hardware devices with various operating systems, touch screens and / or display screens.

[0128] like Figure 4 As shown, the application running method may include the following steps:

[0129] Step 401 : in response to a first user's request for executing a target business process, obtaining a product identifier of a target business product applied for by the first user.

[0130] Among them, the target business process is, for example, the loan account opening and issuance process.

[0131] Among them, the first user may be a user with corresponding business needs. For example, assuming that the target business process is a loan account opening and issuance process, the first user is a user with loan needs.

[0132] Among them, the target business products may be, for example, general loans, mortgage loans, consumer loans, corporate loans, etc., and this application does not impose any restrictions on this.

[0133] The product identifier can be used to uniquely identify the target business product. It should be noted that the product identifier can be represented by numbers, letters, symbols, etc.

[0134] In an embodiment of the present application, the target business product applied for by the first user can be obtained in response to the execution request of the first user for the target business process. As an example, in response to the execution request of the first user for the target business process, the execution request carrying the product identifier can be parsed to parse out the product identifier of the target business product applied for by the first user.

[0135] Step 402: Acquire the value of the product parameter of the target business product according to the product identifier of the target business product.

[0136] As an example, based on the product identification of the target business product, the relevant table can be queried to obtain the product parameters of the target business product from the relevant table, and the values ​​of the product parameters of the target business product can be determined based on the values ​​of each product parameter defined in the relevant table.

[0137] For example, assuming that the target business product is a general loan, and the product identifier of the target business product is "YBDK001", the relevant table can be queried based on the product identifier of the target business product, and the product parameters of the target business product can be obtained from the relevant table, such as "interest rate type", "interest calculation rules", "repayment method", "loan term", "automatic deduction mark", "interest transfer rules", "overdue interest rate adjustment method", "interest rate floating method", etc. The values ​​of each product parameter defined in the relevant table can be determined as the values ​​of the corresponding product parameters. Therefore, the value of the product parameter of the target business product can be set by pre-setting the parameter value.

[0138] Step 403: configuring the first target application program obtained by the application program generation method based on the values ​​of the product parameters.

[0139] In an embodiment of the present application, after obtaining the value of the product parameter, the first target application obtained by the application generation method can be configured.

[0140] Step 404 , running the configured first target application to execute the target business process requested by the first user.

[0141] In a possible implementation of the embodiment of the present application, in response to the operation of the second user, the values ​​of each product parameter are adjusted; based on the adjusted values ​​of each product parameter, the target business process requested by the first user is executed.

[0142] The second user may be, for example, a relevant business person or staff member, etc., and this application does not impose any restrictions on this.

[0143] Among them, the second user's operation may include but is not limited to input operation, click operation, sliding operation, etc., and this application does not impose any restrictions on this.

[0144] It should be noted that in the scenario where the target business process is the loan account opening and issuance process, there may be related users (such as the first user, the second user, etc.) who have the need to adjust the product parameters. For example, the loan user (referred to as the first user in this application) needs a longer repayment period, or due to the need for business expansion, the business personnel need to change the interest rate type, interest calculation method, etc. At this time, in order to meet the different needs of different users for the target business process and provide users with business products suitable for the users, the values ​​of each product parameter can be adjusted in response to the operation of the second user, and based on the adjusted values ​​of each product parameter, the target business process requested by the first user is executed.

[0145] Therefore, the parameter values ​​can be flexibly adjusted, which not only improves the flexibility and adaptability of the business process, but also meets the personalized needs of different users for product parameters in the business process, providing strong support for business development and user services.

[0146] The application running method of the embodiment of the present application obtains the target business product applied for by the first user by responding to the execution request of the first user for the target business process; obtains the value of the product parameter of the target business product according to the product identifier of the target business product; configures the first target application obtained by the application generation method based on the value of the product parameter; and runs the configured first target application to execute the target business process requested by the first user. As a result, the target business process can be flexibly executed according to the needs of the first user while ensuring the accuracy and compliance of the business process; in addition, since the application is dynamically generated according to the product parameters, the system can easily cope with changes in different business products and maintain the flexibility and scalability of the business process.

[0147] Corresponding to the application generation method provided in the above-mentioned embodiment, the present application also provides an application generation device. Since the application generation device provided in the embodiment of the present application corresponds to the application generation method provided in the above-mentioned embodiment, the implementation method of the application generation method is also applicable to the application generation device provided in the embodiment of the present application, and will not be described in detail in the embodiment of the present application.

[0148] Figure 5 It is a structural diagram of an application generating device shown in another embodiment of the present application.

[0149] like Figure 5 As shown, the application generating device 500 includes: a determination module 501 , an acquisition module 502 and an arrangement module 503 .

[0150] The determination module 501 is used to determine multiple business areas involved in the business process in response to an application development request for the business process; wherein the business process includes at least one process node.

[0151] The acquisition module 502 is used to obtain, for any process node, a business entity API in at least one business domain that matches the process node in response to a user's selection operation; wherein the API that matches the process node is used to call the corresponding program to execute the business function required by the process node.

[0152] The orchestration module 503 is used to orchestrate each business entity API according to the business process to obtain a target application corresponding to the business process.

[0153] In a possible implementation of an embodiment of the present application, the target application is applied to at least one business product; the acquisition module 502 is used to: for any business product, determine the target business domain corresponding to the process node and the business product from multiple business domains; in response to a user's selection operation, determine the corresponding target business domain API from at least one business domain API under the target business domain; and filter out the business entity API that matches both the business product and the process node from at least one business entity API included in the target business domain API.

[0154] In a possible implementation of an embodiment of the present application, the orchestration module 503 is used to: for any target business domain API of any process node, encapsulate the business entity API of each business product that matches the process node under the target business domain API to obtain the sub-business module corresponding to the process node in the target business domain API; integrate the sub-business modules corresponding to each target business domain API of the process node to obtain the business module corresponding to the process node; and build the target application based on each business module in the order of each process node in the business process.

[0155] In a possible implementation of an embodiment of the present application, there are multiple business entity APIs that match the process node; the orchestration module 503 is used to: in response to the existence of a target business entity API in multiple business entity APIs that match the process node under the target business domain API, abstract each business product associated with the process node into a target class, wherein the target business entity API is associated with at least two business products; for any business product associated with the process node, based on the business entity API and the target class that match both the business product and the process node, create a subclass of the business product under the process node; based on the target class and each subclass, determine the sub-business module corresponding to the process node in the target business domain API.

[0156] In a possible implementation of an embodiment of the present application, the orchestration module 503 is used to: obtain the business logic order of the sub-business modules corresponding to each target business domain API under the process node; set the calling order between the sub-business modules under the process node according to the business logic order; configure the business call interface corresponding to the process node to associate the sub-business modules under the process node through the business call interface to obtain the business module corresponding to the process node.

[0157] The application generation device of the embodiment of the present application determines the multiple business fields involved in the business process by responding to the application development request for the business process; wherein the business process includes at least one process node; for any process node, in response to the user's selection operation, obtains the business entity API matching the process node in at least one business field; wherein the business entity API matching the process node is used to call the business function required by the corresponding program execution process node; according to the business process, each business entity API is arranged to obtain the target application corresponding to the business process. Thus, it is possible to flexibly respond to the application development request of the business process and quickly build an application that meets the business needs; it is also possible to customize and configure the business process according to the actual needs of the user, thereby improving the flexibility and scalability of the system; and the division of specific business functions, that is, the attribution or division of the business entity API, is based on the business field to which it belongs, which can achieve decoupling and collaboration between different business fields, so that the business process can more easily adapt to changes and updates in the business environment.

[0158] Corresponding to the application running method provided in the above-mentioned embodiment, the present application also provides an application running device. Since the application running device provided in the embodiment of the present application corresponds to the application running method provided in the above-mentioned embodiment, the implementation method of the application running method is also applicable to the application running device provided in the embodiment of the present application, and will not be described in detail in the embodiment of the present application.

[0159] Figure 6It is a structural diagram of an application running device shown in another embodiment of the present application.

[0160] like Figure 6 As shown, the application running device 600 includes: a first acquisition module 601, a second acquisition module 602 and a configuration module 603.

[0161] The first acquisition module 601 is used to acquire the product identifier of the target business product applied for by the first user in response to the execution request of the first user for the target business process.

[0162] The second acquisition module 602 is used to acquire the value of the product parameter of the target business product according to the product identifier of the target business product.

[0163] The configuration module 603 is used to configure the first target application program obtained by the application program generation method based on the values ​​of the product parameters.

[0164] The running module 604 is used to run the configured first target application to execute the target business process requested by the first user.

[0165] In a possible implementation of the embodiment of the present application, the application program running device 600 may further include:

[0166] The adjustment module is used to adjust the value of each product parameter in response to the operation of the second user.

[0167] The execution module is used to execute the target business process requested by the first user based on the adjusted values ​​of each product parameter.

[0168] The application running device of the embodiment of the present application obtains the target business product applied by the first user by responding to the execution request of the first user for the target business process; obtains the value of the product parameter of the target business product according to the product identifier of the target business product; configures the first target application obtained by the application generation method based on the value of the product parameter; and runs the configured first target application to execute the target business process requested by the first user. As a result, the target business process can be flexibly executed according to the needs of the first user while ensuring the accuracy and compliance of the business process; in addition, since the application is dynamically generated according to the product parameters, the system can easily cope with changes in different business products and maintain the flexibility and scalability of the business process.

[0169] In an exemplary embodiment, an electronic device is also provided.

[0170] Among them, electronic equipment includes:

[0171] processor;

[0172] a memory for storing processor-executable instructions;

[0173] The processor is configured to execute instructions to implement the application generation method proposed in any of the aforementioned embodiments.

[0174] As an example, Figure 7 is a schematic diagram of the structure of an electronic device 900 shown in an exemplary embodiment of the present application. Figure 7 As shown, the electronic device 900 may further include:

[0175] The memory 910 and the processor 920, a bus 930 connecting different components (including the memory 910 and the processor 920), the memory 910 stores a computer program, and when the processor 920 executes the program, the application generation method described in the embodiment of the present application is implemented.

[0176] Bus 930 represents one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, a processor or a local bus using any of a variety of bus architectures. For example, these architectures include but are not limited to Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MAC) bus, Enhanced ISA bus, Video Electronics Standards Association (VESA) local bus and Peripheral Component Interconnect (PCI) bus.

[0177] The electronic device 900 typically includes a variety of electronic device readable media. These media can be any available media that can be accessed by the electronic device 900, including volatile and non-volatile media, removable and non-removable media.

[0178] The memory 910 may also include computer system readable media in the form of volatile memory, such as random access memory (RAM) 940 and / or cache memory 950. The server 900 may further include other removable / non-removable, volatile / non-volatile computer system storage media. By way of example only, the storage system 960 may be used to read and write non-removable, non-volatile magnetic media ( Figure 7 not shown, usually called a "hard drive"). Although Figure 7 Not shown, a disk drive for reading and writing to a removable non-volatile disk (e.g., a "floppy disk"), and an optical disk drive for reading and writing to a removable non-volatile optical disk (e.g., a CD-ROM, a DVD-ROM, or other optical medium) may be provided. In these cases, each drive may be connected to bus 930 via one or more data medium interfaces. Memory 910 may include at least one program product having a set (e.g., at least one) of program modules that are configured to perform the functions of each embodiment of the present application.

[0179] A program / utility 980 having a set (at least one) of program modules 970 may be stored, for example, in the memory 910, such program modules 970 including, but not limited to, an operating system, one or more application programs, other program modules, and program data, each of which or some combination may include an implementation of a network environment. The program modules 970 generally perform the functions and / or methods of the embodiments described herein.

[0180] The electronic device 900 may also communicate with one or more external devices 990 (e.g., keyboard, pointing device, display 991, etc.), may also communicate with one or more devices that enable a user to interact with the electronic device 900, and / or communicate with any device that enables the electronic device 900 to communicate with one or more other computing devices (e.g., network card, modem, etc.). Such communication may be performed through an input / output (I / O) interface 992. In addition, the electronic device 900 may also communicate with one or more networks (e.g., local area network (LAN), wide area network (WAN) and / or public network, such as the Internet) through a network adapter 993. As shown, the network adapter 993 communicates with other modules of the electronic device 900 through a bus 930. It should be understood that, although not shown in the figure, other hardware and / or software modules may be used in conjunction with the electronic device 900, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.

[0181] The processor 920 executes various functional applications and data processing by running the programs stored in the memory 910 .

[0182] It should be noted that the implementation process and technical principles of the electronic device of this embodiment refer to the aforementioned explanation of the application generation method of the embodiment of the present application, and will not be repeated here.

[0183] In an exemplary embodiment, a computer-readable storage medium including instructions is also provided, such as a memory including instructions, and the above instructions can be executed by a processor of an electronic device to complete the application generation method proposed in any of the above embodiments. Optionally, the computer-readable storage medium can be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, etc.

[0184] In an exemplary embodiment, a computer program product is also provided, including a computer program / instruction, wherein when the computer program / instruction is executed by a processor, the application generation method proposed in any of the above embodiments is implemented.

[0185] Those skilled in the art will readily appreciate other embodiments of the present application after considering the specification and practicing the inventions claimed herein. The present application is intended to cover any variations, uses or adaptations of the present application, which follow the general principles of the present application and include common knowledge or customary techniques in the art that are not claimed in the present application. The specification and examples are intended to be exemplary only, and the true scope and spirit of the present application are indicated by the following claims.

[0186] It should be understood that the present application is not limited to the precise structures that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present application is limited only by the appended claims.

Claims

1. A method for generating an application, characterized in that: The method comprises: In response to an application development request for a business process, determining a plurality of business areas involved in the business process; wherein the business process includes at least one process node; For any of the process nodes, in response to a user's selection operation, obtaining at least one business entity application programming interface API in the business domain that matches the process node; wherein the API that matches the process node is used to call a corresponding program to execute the business function required by the process node; According to the business process, each of the business entity APIs is arranged to obtain a target application corresponding to the business process.

2. The method according to claim 1, characterized in that The target application is applied to at least one business product; and in response to a user's selection operation, obtaining at least one business entity API matching the process node in the business domain includes: For any of the business products, determining a target business field corresponding to the process node and the business product from the multiple business fields; In response to the user's selection operation, determining a corresponding target business domain API from at least one business domain API under the target business domain; A business entity API matching both the business product and the process node is screened out from at least one of the business entity APIs included in the target business domain API.

3. The method according to claim 2, characterized in that The step of arranging the business entity APIs according to the business process to obtain a target application corresponding to the business process includes: For any of the target business domain APIs of any of the process nodes, encapsulate the business entity APIs of each of the business products that match the process node under the target business domain API to obtain the sub-business module corresponding to the process node in the target business domain API; Integrate the sub-business modules corresponding to the target business domain APIs of the process nodes to obtain the business modules corresponding to the process nodes; The target application is constructed based on each of the business modules in the order of each of the process nodes in the business process.

4. The method according to claim 3, characterized in that There are multiple business entity APIs matching the process node; encapsulating each of the business products under the target business domain API and the business entity API matching the process node to obtain a sub-business module corresponding to the process node in the target business domain API includes: In response to the existence of a target business entity API in the plurality of business entity APIs matching the process node under the target business domain API, abstracting each of the business products associated with the process node into a target class, wherein the target business entity API is associated with at least two of the business products; For any of the business products associated with the process node, based on the business entity API and the target class that match both the business product and the process node, create a subclass of the business product under the process node; Based on the target class and each of the subclasses, a sub-business module corresponding to the process node in the target business domain API is determined.

5. The method according to claim 3, characterized in that: The sub-business modules corresponding to the target business domain APIs of the process nodes are integrated to obtain the business modules corresponding to the process nodes, including: Obtain the business logic sequence of the sub-business modules corresponding to each of the target business domain APIs under the process node; According to the business logic sequence, the calling sequence between the sub-business modules under the process node is set; The business call interface corresponding to the process node is configured so as to associate the sub-business modules under the process node through the business call interface to obtain the business module corresponding to the process node.

6. A method for running an application, characterized in that: The method comprises: In response to a first user's request for executing a target business process, obtaining a product identifier of a target business product applied for by the first user; According to the product identifier of the target business product, obtaining the value of the product parameter of the target business product; A first target application program obtained by the method according to any one of claims 1 to 5 is configured based on the value of the product parameter; The configured first target application is run to execute the target business process requested by the first user.

7. The method according to claim 6, characterized in that The method further comprises: In response to an operation by a second user, adjusting the value of each of the product parameters; Based on the adjusted values ​​of each of the product parameters, the target business process requested by the first user is executed.

8. An application generation device, characterized in that: The device comprises: A determination module, configured to determine, in response to an application development request for a business process, a plurality of business areas involved in the business process; wherein the business process includes at least one process node; An acquisition module, for acquiring, for any of the process nodes, a business entity API matching the process node in at least one of the business domains in response to a user's selection operation; wherein the API matching the process node is used to call a corresponding program to execute a business function required by the process node; The orchestration module is used to orchestrate each of the business entity APIs according to the business process to obtain a target application corresponding to the business process.

9. An application program running device, characterized in that: The device comprises: A first acquisition module, configured to acquire a product identifier of a target business product applied for by a first user in response to a request by the first user to execute the target business process; A second acquisition module, used to acquire the value of the product parameter of the target business product according to the product identifier of the target business product; A configuration module, configured to configure the first target application obtained by the method according to any one of claims 1 to 5 based on the value of the product parameter; The running module is used to run the configured first target application to execute the target business process requested by the first user.

10. An electronic device, characterized in that: include: A processor, and a memory communicatively connected to the processor; The memory stores computer-executable instructions; The processor executes the computer-executable instructions stored in the memory to implement the method according to any one of claims 1-5, or any one of claims 6-7.

Images