Api and flowable based cloud platform business process driving method and system

Abstract

The application provides a cloud platform business process driving method and system based on API and flowable, the method comprising business type registration management, business type associated business flow and business process driving execution. The user business type is defined by means of API combination, the request carries token, and the asynchronous type business processing is supported. The business type registration mode is used for saving in the cloud platform, and permanent reuse is realized through one-time configuration. The configuration and driving of the business process are based on the open source flowable, and in the implementation method of the business node, the standard request header template, request parameter template and return value template are defined. The token support, business execution success judgment and request parameter transmission are realized by parsing and filling the template. Meanwhile, the business process driving is based on the flowable, and the processing logic of the business node is realized by self-definition, so that the business can be completely connected with different business scenes based on API.

Description

Technical Field

[0001] This invention relates to the field of cloud platform technology, and specifically to a cloud platform business process driving method and system based on APIs and flowables. Background Technology

[0002] With the development of cloud platforms, various related businesses are constantly growing, bringing users a variety of functions and business scenarios. To meet business needs, in a single business scenario, users typically need to integrate multiple business modules and configure and create various resources when using the cloud platform, resulting in complexity, heavy workload, and poor user experience. Therefore, users urgently need a streamlined, one-click business processing method.

[0003] Flowable is a commonly used workflow control engine that allows for customized control of workflow execution order and personalized approval processes. Users can create and execute a pre-defined workflow flowchart. However, native Flowable configuration is cumbersome, supports limited functionality for workflow nodes, and has poor inter-node connectivity, typically requiring modification to suit specific business scenarios. Summary of the Invention

[0004] In view of this, the purpose of this invention is to propose a cloud platform business process-driven method and system based on APIs and Flowable. Based on Flowable, by modifying and integrating cloud platform business APIs, it enables the process-driven execution of multiple business nodes. This method can link different business types on the cloud platform and drive their execution with a single click in the form of business processes. It also supports the reuse of APIs and business processes, reducing the workload of user configuration and improving the user experience. This API-driven method decouples the process module from other business modules, forming a universal solution and improving the platform's scalability.

[0005] To achieve the above objectives, in a first aspect, the present invention provides a cloud platform business process-driven method based on APIs and flowables, the method comprising the following steps:

[0006] Step 1: Business Type Registration Management

[0007] The user registers and saves the business types corresponding to the business modules to the cloud platform via API. The cloud platform manages them uniformly and binds the associated business processes based on the business types registered by the user, thereby driving the execution of the business processes.

[0008] Step 2: Associating Business Types with Business Processes

[0009] The user client draws business process diagrams based on the Flowable process engine. In the process nodes, business nodes are defined by custom implementation of the ServiceTask node type in Flowable. The process diagram is drawn based on the business nodes, and the business types associated with the user are configured in the business nodes to complete the creation of the business process.

[0010] Step 3: Business Process-Driven Execution

[0011] In Flowable, you can define custom implementation methods for business nodes, parse the API in the business type, execute business operations, and write the operation results into process variables for subsequent nodes in the process to parse and use, thereby automating parameter passing and driving the flow of the business process.

[0012] As a further aspect of the present invention, in step one, the business type registration management includes filling in the API and registering the business type, wherein the business type includes basic parameters of the business type and three API interfaces.

[0013] As a further aspect of the present invention, the basic parameters of the business type include the business type's ID, name, description, service, URL, request method, herder, request body, and return value.

[0014] As a further aspect of the present invention, the three API interfaces include a Token API interface, an Execution API interface, and a Verification API interface.

[0015] As a further aspect of the present invention, the TokenAPI interface is used to support scenarios where a token is required when calling a business API, and the token used by subsequent APIs can be obtained through the tokenAPI.

[0016] The execution API interface is the core API used to execute user business logic, and the business logic corresponding to the business type is realized through the execution API;

[0017] The verification API interface is used to support asynchronous task scenarios. When executing the API, if the business logic being executed is complex, it is executed in an asynchronous manner. The execution result of the asynchronous task is obtained through the verification API to ensure that the current business processing is completed.

[0018] As a further aspect of the present invention, in step one, in addition to the basic parameters of the business type, the API definition also includes filling in the API request header template, request parameter template, and return value template. The templates use ${key} as placeholders. The header template and request parameter template are used to define API request parameters and are not required. The return value template is used to verify the API execution result and the parameter alias mapping of the execution result.

[0019] As a further aspect of the present invention, in step two, the user terminal draws a business process diagram based on the flowable process engine. When selecting a process node, the serviceTask type of flowable is used. This type is an extension type of flowable and supports custom implementation of the business logic of the process node. The business node is custom implemented based on serviceTask.

[0020] As a further aspect of the present invention, in step two, the user terminal configures and selects the registered business type in the parameters of the business node, and also completes the binding of the business type and the business node through the ID, and connects the business through the flowable process.

[0021] As a further aspect of the present invention, in step three, after the user completes the parameters required for process execution, the flowable process engine drives the business process to execute the user-configured business nodes sequentially according to the flowchart until the process is completed. When executing a business node, the business node is custom-implemented based on a serviceTask, which includes the following steps:

[0022] Get the business type details based on the business type ID bound to the business node. If the business type includes TokenAPI, first call tokenAPI to get the token, replace the ${token} placeholder in the execution API and verification API header template in the business type with the token, and get the request header.

[0023] Iterate through the API request parameter template, obtain the key of the placeholder in the parameter template, retrieve the parameter value corresponding to the key in the global parameter Map of the process, replace the placeholder corresponding to the key, and assemble and fill the complete request parameters in this way.

[0024] Call the execution API to process the business logic of the business node. After the API execution is completed, match and verify the return value with the return value template. If they match, it means that the API call was successful; otherwise, an error is reported and the process ends.

[0025] When performing return value validation, if the value of a field in the return value template corresponds to a placeholder, then obtain the key of the placeholder and save the corresponding parameter value in the return value to the global parameters of the process using the key as the keyword.

[0026] A second aspect of the present invention also provides a cloud platform business process driven system based on APIs and flowables, comprising:

[0027] The registration management module is used to register and save the business types corresponding to the business modules to the cloud platform via API through the user terminal. The cloud platform manages them uniformly and binds the associated business processes based on the business types registered by the user, thereby driving the execution of the business processes.

[0028] The business process association module is used by the user to draw business process diagrams based on the flowable process engine. In the process nodes, business nodes are defined by custom implementation of the serviceTask node type in flowable. The process diagram is drawn based on the business nodes, and the associated business types of the user are configured in the business nodes to complete the creation of the business process.

[0029] The process-driven module is used to define the implementation methods of custom business nodes in Flowable, parse the API in the business type, execute business operations, and write the operation results into process variables for subsequent nodes in the process to parse and use, thereby completing the automatic transmission of parameters and driving the flow of business processes.

[0030] In another aspect, the present invention provides a computer device including a memory and a processor, wherein the memory stores a computer program that, when executed by the processor, performs any of the above-described API-based and flowable cloud platform business process driving methods according to the present invention.

[0031] In another aspect, the present invention provides a computer-readable storage medium storing computer program instructions that, when executed, implement any of the above-described API-based and flowable cloud platform business process driving methods according to the present invention.

[0032] The present invention has at least the following beneficial technical effects:

[0033] This invention proposes a cloud platform business process-driven method and system based on APIs and flowables. It can link different business types on the cloud platform and drive execution with a single click in the form of business processes. It also supports the reuse of APIs and business processes, reducing user configuration workload and improving user experience. This API-driven method decouples the process module from other business modules, forming a universal solution and improving the platform's scalability.

[0034] This invention designs and implements an API-based business type definition specification. This specification enables business nodes in the business process to support tokens, determine the success of business execution, and pass request parameters. It is based on business process driven by Flowable and has customized the processing logic of business nodes, allowing different business scenarios to be fully connected based on the API.

[0035] These or other aspects of this application will become more apparent from the following description of embodiments. It should be understood that the foregoing general description and the following detailed description are exemplary and explanatory only, and are not intended to limit the application. Attached Figure Description

[0036] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other embodiments can be obtained based on these drawings without creative effort.

[0037] In the diagram:

[0038] Figure 1 This is a flowchart illustrating a cloud platform business process-driven method based on APIs and flowable, according to an embodiment of the present invention.

[0039] Figure 2 This is a structural diagram of the business types in a cloud platform business process driving method based on API and flowable according to an embodiment of the present invention;

[0040] Figure 3 This is a schematic diagram of a process in a cloud platform business process driven method based on API and flowable according to an embodiment of the present invention, in which business nodes are custom-implemented based on serviceTask;

[0041] Figure 4 This is a schematic diagram of the hardware structure of a computer device that implements a cloud platform business process driving method based on API and flowable, according to an embodiment of the present invention.

[0042] Figure 5 This is a schematic diagram of an embodiment of a computer-readable storage medium for implementing an API-based and flowable cloud platform business process driving method according to an embodiment of the present invention. Detailed Implementation

[0043] The present application will now be further described in conjunction with the accompanying drawings and specific embodiments. It should be noted that, without conflict, the various embodiments or technical features described below can be arbitrarily combined to form new embodiments.

[0044] To make the objectives, technical solutions, and advantages of the present invention clearer, the embodiments of the present invention will be further described in detail below with reference to specific examples and the accompanying drawings. It should be understood that the specific embodiments described herein are merely illustrative and are not intended to limit the scope of this application.

[0045] It should be noted that all uses of "first" and "second" in the embodiments of the present invention are for the purpose of distinguishing two different entities or different parameters with the same name. Therefore, "first" and "second" are merely for convenience of expression and should not be construed as limiting the embodiments of the present invention. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion, such as other steps or units inherent in a process, method, system, product, or device that includes a series of steps or units.

[0046] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0047] The flowchart shown in the attached diagram is for illustrative purposes only and does not necessarily include all content and operations / steps, nor does it necessarily have to be performed in the order described. For example, some operations / steps can be broken down, combined, or partially merged, so the actual execution order may change depending on the actual situation.

[0048] The following detailed description of some embodiments of this application is provided in conjunction with the accompanying drawings. Unless otherwise specified, the following embodiments and features can be combined with each other.

[0049] Because the native Flowable configuration is cumbersome, supports only a limited range of process node functions, and has poor inter-node correlation, it usually needs to be modified to suit specific business scenarios.

[0050] Therefore, this invention proposes an improved cloud platform business process driving method and system based on APIs and Flowable. Based on Flowable, it achieves process-driven execution of multiple business nodes by modifying and integrating cloud platform business APIs. This method can link different business types on the cloud platform and drive their execution with a single click in the form of business processes. It also supports the reuse of APIs and business processes, reducing user configuration workload and improving user experience. This API-driven method decouples the process module from other business modules, forming a universal solution and improving the platform's scalability.

[0051] See Figure 1 As shown, an embodiment of the present invention provides a cloud platform business process-driven method based on APIs and flowables, the method comprising the following steps:

[0052] Step 1: Business Type Registration Management

[0053] The user registers and saves the business types corresponding to the business modules to the cloud platform via API. The cloud platform manages these business types uniformly and binds them to associated business processes based on the registered business types, thereby driving the execution of the business processes.

[0054] In this embodiment, the business type registration management includes filling in the API and registering the business type. The business type includes basic parameters and three API interfaces.

[0055] See Figure 2 As shown, the basic parameters of the business type include the business type's ID, name, description, service, URL, request method, border, request body, and return value. The three API interfaces include the Token API interface, the Execution API interface, and the Verification API interface.

[0056] The TokenAPI interface is used to support scenarios where a token is required when calling business APIs. The token used by subsequent APIs can be obtained through the tokenAPI. The TokenAPI field is optional and can be left blank if the API request does not require a token.

[0057] The execution API interface is the core API used to execute user business logic. The business logic corresponding to the business type is implemented through the execution API. The verification API interface is used to support asynchronous task scenarios. When executing the API, if the business logic being executed is complex, it is executed in an asynchronous manner. The execution result of the asynchronous task is obtained through the verification API to ensure that the current business processing is completed.

[0058] In this embodiment, in addition to the basic parameters of the business type, defining the API also includes filling in the API request header template, request parameter template, and return value template. Placeholders in the templates are represented by ${key}. The header template and request parameter template are used to define the API request parameters and are not required. The return value template is used to validate the API execution result and map the parameter aliases of the execution result.

[0059] For example, the API request header template can be:

[0060] Header template:

[0061]

[0062] Request parameter template:

[0063]

[0064] Return value template:

[0065]

[0066] Step 2: Associating Business Types with Business Processes

[0067] The user client draws business process diagrams based on the Flowable process engine. In the process nodes, business nodes are defined by custom implementation of the ServiceTask node type in Flowable. The process diagram is drawn based on the business nodes, and the associated business types of the user are configured in the business nodes to complete the creation of the business process.

[0068] In this embodiment, the user client draws a business process diagram based on the flowable process engine. When selecting a process node, the serviceTask type of flowable is used. This type is an extension type of flowable and supports custom implementation of the business logic of the process node. The business node is implemented based on the serviceTask.

[0069] In this process, the user can configure and select the registered business type in the parameters of the business node, and also bind the business type to the business node through the ID, and connect the business through the flowable process.

[0070] For example, creating a cloud host with a mounted cloud disk data disk can be a business process that includes three business nodes: creating a cloud host, creating a cloud disk data disk, and mounting a cloud disk. The corresponding business types are bound, and users can complete the creation with one click after filling in the creation parameters.

[0071] Step 3: Business Process-Driven Execution

[0072] In Flowable, you can define custom implementation methods for business nodes, parse the API in the business type, execute business operations, and write the operation results into process variables for subsequent nodes in the process to parse and use, thereby automating parameter passing and driving the flow of the business process.

[0073] In this embodiment, after the user fills in the parameters required for process execution, the flowable process engine drives the business process to execute the user-configured business nodes sequentially according to the flowchart until the process is completed. When executing business nodes, the business nodes are custom-implemented based on serviceTask, as shown in [reference needed]. Figure 3 As shown, the custom implementation of the business node based on serviceTask includes the following steps:

[0074] Get the business type details based on the business type ID bound to the business node. If the business type includes TokenAPI, first call tokenAPI to get the token, replace the ${token} placeholder in the execution API and verification API header template in the business type with the token, and get the request header.

[0075] Iterate through the API request parameter template, obtain the key of the placeholder in the parameter template, retrieve the parameter value corresponding to the key in the global parameter Map of the process, replace the placeholder corresponding to the key, and assemble and fill the complete request parameters in this way.

[0076] Call the execution API to process the business logic of the business node. After the API execution is completed, match and verify the return value with the return value template. If they match, it means that the API call was successful; otherwise, an error is reported and the process ends.

[0077] When performing return value validation, if the value of a field in the return value template corresponds to a placeholder, then obtain the key of the placeholder and save the corresponding parameter value in the return value to the global parameters of the process using the key as the keyword.

[0078] For example, the return value template can be:

[0079]

[0080] The return value is as follows:

[0081]

[0082] Then, vmId=aaa is stored in the global parameters of the process. This method allows the return value of the previous process node to be used as the input parameter for the next process node, automatically passing parameters without manual intervention and driving the business API of the process to execute. After the API call is completed, if the verification API is not empty (i.e., the business is executed asynchronously), the verification API is called periodically to determine whether the business node has successfully completed. If it is not completed within the maximum waiting time, an error is reported and the process exits; otherwise, the process ends.

[0083] This invention presents a cloud platform business process driving method based on APIs and Flowable. This method defines user business types through API combinations, supports requests carrying tokens, and asynchronous business processing. Business types are registered and stored on the cloud platform, allowing for one-time configuration and permanent reuse. The configuration and driving of business processes are based on the open-source Flowable. By implementing custom business nodes, registered business types are bound to the business process. This binding is ID-based and decoupled from the business process, allowing adaptation only by modifying the registered business type when the API changes, without needing to rewrite the entire business process. The implementation method of business nodes defines standardized request header templates, request parameter templates, and return value templates. By parsing and filling these templates, it implements token support, business execution success verification, and request parameter passing.

[0084] This invention presents a cloud platform business process-driven method based on APIs and flowables. This method can link different business types on a cloud platform and drive their execution with a single click in the form of business processes. It also supports the reuse of APIs and business processes, reducing user configuration workload and improving user experience. This API-driven method decouples the process module from other business modules, forming a universal solution and improving the platform's scalability.

[0085] It should be noted that the above figures are merely illustrative of the processes included in the method according to exemplary embodiments of the present invention, and are not intended to be limiting. It is readily understood that the processes shown in the above figures do not indicate or limit the temporal order of these processes. Furthermore, it is readily understood that these processes may, for example, be executed synchronously or asynchronously in multiple modules.

[0086] It should be understood that although the above description follows a certain order, these steps are not necessarily executed in that order. Unless otherwise expressly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, some steps in this embodiment may include multiple steps or multiple stages, which are not necessarily completed at the same time, but may be executed at different times. The execution order of these steps or stages is not necessarily sequential, but may be performed alternately or in turn with other steps or at least a portion of the steps or stages in other steps.

[0087] A second aspect of the present invention also provides a cloud platform business process driven system based on APIs and flowables. The system includes:

[0088] The registration management module is used to register and save the business types corresponding to the business modules to the cloud platform via API through the user terminal. The cloud platform manages them uniformly and binds the associated business processes based on the business types registered by the user, thereby driving the execution of the business processes.

[0089] The business process association module is used by the user to draw business process diagrams based on the flowable process engine. In the process nodes, business nodes are defined by custom implementation of the serviceTask node type in flowable. The process diagram is drawn based on the business nodes, and the associated business types of the user are configured in the business nodes to complete the creation of the business process.

[0090] The process-driven module is used to define the implementation methods of custom business nodes in Flowable, parse the API in the business type, execute business operations, and write the operation results into process variables for subsequent nodes in the process to parse and use, thereby completing the automatic transmission of parameters and driving the flow of business processes.

[0091] A cloud platform business process driven system based on API-based business type definition specifications. This specification enables business nodes in the business process to support tokens, determine the success of business execution, and pass request parameters. Furthermore, based on the business process driven system and Flowable, the system customizes the processing logic of business nodes, allowing different business scenarios to be fully connected based on the API.

[0092] It should be noted that although several modules or units of the device for performing actions have been mentioned in the detailed description above, this division is not mandatory. In fact, according to embodiments of the present invention, the features and functions of two or more modules or units described above can be embodied in one module or unit. Conversely, the features and functions of one module or unit described above can be further divided and embodied by multiple modules or units.

[0093] A third aspect of the present invention also provides a computer device 1000, including a memory 1001 and a processor 1002, wherein the memory stores a computer program, which, when executed by the processor, implements the method of any of the above embodiments.

[0094] like Figure 4 The diagram shown is a hardware structure schematic of an embodiment of a computer device for executing a cloud platform business process-driven method based on APIs and flowables, as provided by the present invention. Figure 4Taking the computer device 1000 shown as an example, this computer device includes a processor 1002 and a memory 1001, and may also include an input device 430 and an output device 440. The processor 1002, memory 1001, input device 430, and output device 440 can be connected via a bus or other means. Figure 4 Taking a bus connection as an example, input device 430 can receive input digital or character information, and generate signal inputs related to the driving of cloud platform business processes based on APIs and flowable. Output device 440 may include display devices such as a display screen.

[0095] Memory 1001, as a non-volatile computer-readable storage medium, can be used to store non-volatile software programs, non-volatile computer-executable programs, and modules, such as the program instructions / modules corresponding to the API-based and flowable cloud platform business process driving method in this embodiment. Memory 1001 may include a program storage area and a data storage area, wherein the program storage area may store the operating system and applications required for at least one function; the data storage area may store data created by the use of the API-based and flowable cloud platform business process driving method, etc. In addition, memory 1001 may include high-speed random access memory and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other non-volatile solid-state storage device. In some embodiments, memory 1001 may optionally include memory remotely located relative to processor 1002, and these remote memories can be connected to the local module via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0096] In some embodiments, processor 1002 may be a central processing unit (CPU), controller, microcontroller, microprocessor, or other data processing chip. Processor 1002 is typically used to control the overall operation of computer device 1000. In this embodiment, processor 1002 is used to run program code stored in memory 1001 or process data. In this embodiment, the processors 1002 of multiple computer devices 1000 execute various server functions and data processing by running non-volatile software programs, instructions, and modules stored in memory 1001, thereby implementing the API-based and flowable cloud platform business process driving method of the above method embodiment, including the following steps:

[0097] Step 1: Business Type Registration Management

[0098] The user registers and saves the business types corresponding to the business modules to the cloud platform via API. The cloud platform manages them uniformly and binds the associated business processes based on the business types registered by the user, thereby driving the execution of the business processes.

[0099] Step 2: Associating Business Types with Business Processes

[0100] The user client draws business process diagrams based on the Flowable process engine. In the process nodes, business nodes are defined by custom implementation of the ServiceTask node type in Flowable. The process diagram is drawn based on the business nodes, and the business types associated with the user are configured in the business nodes to complete the creation of the business process.

[0101] Step 3: Business Process-Driven Execution

[0102] In Flowable, you can define custom implementation methods for business nodes, parse the API in the business type, execute business operations, and write the operation results into process variables for subsequent nodes in the process to parse and use, thereby automating parameter passing and driving the flow of the business process.

[0103] A fourth aspect of the present invention also provides a computer-readable storage medium. Figure 5 This is a schematic diagram of a computer-readable storage medium for a cloud platform business process-driven method based on APIs and flowables provided according to an embodiment of the present invention. Figure 5 As shown, the computer-readable storage medium 2000 stores computer program instructions 2001, which can be executed by a processor. When the computer program instructions 2001 are executed, they implement the method of any of the above embodiments, that is, implement the API-based and flowable cloud platform business process driven method of the above method embodiments, including the following steps:

[0104] Step 1: Business Type Registration Management

[0105] The user registers and saves the business types corresponding to the business modules to the cloud platform via API. The cloud platform manages them uniformly and binds the associated business processes based on the business types registered by the user, thereby driving the execution of the business processes.

[0106] Step 2: Associating Business Types with Business Processes

[0107] The user client draws business process diagrams based on the Flowable process engine. In the process nodes, business nodes are defined by custom implementation of the ServiceTask node type in Flowable. The process diagram is drawn based on the business nodes, and the business types associated with the user are configured in the business nodes to complete the creation of the business process.

[0108] Step 3: Business Process-Driven Execution

[0109] In Flowable, you can define custom implementation methods for business nodes, parse the API in the business type, execute business operations, and write the operation results into process variables for subsequent nodes in the process to parse and use, thereby automating parameter passing and driving the flow of the business process.

[0110] It should be understood that, where there is no conflict, all the embodiments, features and advantages described above for the API-based and flowable cloud platform business process driving method according to the present invention are equally applicable to the API-based and flowable cloud platform business process driving system and storage medium according to the present invention.

[0111] Those skilled in the art will also understand that the various exemplary logic blocks, modules, circuits, and algorithm steps described in conjunction with the disclosure herein can be implemented as electronic hardware, computer software, or a combination of both. To clearly illustrate this interchangeability between hardware and software, the functionality of various illustrative components, blocks, modules, circuits, and steps has been generally described. Whether this functionality is implemented as software or as hardware depends on the specific application and the design constraints imposed on the system as a whole. Those skilled in the art can implement the functionality in various ways for each specific application, but such implementation decisions should not be construed as departing from the scope of the embodiments disclosed herein.

[0112] Finally, it should be noted that the computer-readable storage medium (e.g., memory) described herein can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. By way of example, and not limitation, non-volatile memory may include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory may include random access memory (RAM), which can act as external cache memory. By way of example, and not limitation, RAM can be obtained in various forms, such as synchronous RAM (DRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), dual data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), and direct Rambus RAM (DRRAM). The storage devices disclosed herein are intended to include, but are not limited to, these and other suitable types of memory.

[0113] The various exemplary logic blocks, modules, and circuits described herein can be implemented or performed using the following components designed to perform the functions herein: general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or any combination of these components. A general-purpose processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP, and / or any other such configuration.

[0114] In summary, this invention proposes a cloud platform business process-driven method and system based on APIs and flowables. This method can link different business types on the cloud platform and drive execution with a single click in the form of business processes. It also supports the reuse of APIs and business processes, reducing user configuration workload and improving user experience. This API-driven method decouples the process module from other business modules, forming a universal solution and improving the platform's scalability.

[0115] This invention designs and implements an API-based business type definition specification. This specification enables business nodes in the business process to support tokens, determine the success of business execution, and pass request parameters. It is based on business process driven by Flowable and has customized the processing logic of business nodes, allowing different business scenarios to be fully connected based on the API.

[0116] The above are exemplary embodiments disclosed in this invention. However, it should be noted that various changes and modifications can be made without departing from the scope of the embodiments of this invention as defined by the claims. The functions, steps, and / or actions of the methods according to the disclosed embodiments described herein do not need to be performed in any particular order. Furthermore, although the elements disclosed in the embodiments of this invention may be described or claimed individually, they may be understood as multiple unless explicitly limited to a singular number.

[0117] It should be understood that, as used herein, the singular form "a" is intended to include the plural form as well, unless the context clearly supports an exception. It should also be understood that, as used herein, "and / or" refers to any and all possible combinations of one or more of the associatedly listed items. The embodiment numbers disclosed above are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0118] Those skilled in the art should understand that the discussion of any of the above embodiments is merely exemplary and is not intended to imply that the scope of the invention (including the claims) is limited to these examples. Within the framework of the invention, technical features of the above embodiments or different embodiments can be combined, and many other variations of different aspects of the invention exist, which are not provided in the details for the sake of brevity. Therefore, any omissions, modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the invention should be included within the protection scope of the invention.

Claims

1. A cloud platform business process-driven method based on APIs and flowables, characterized in that, Includes the following steps: The user registers and saves the business types corresponding to the business modules to the cloud platform via API. The cloud platform manages them uniformly and binds the associated business processes based on the business types registered by the user, thereby driving the execution of the business processes. The user client draws business process diagrams based on the Flowable process engine. In the process nodes, business nodes are defined by custom implementation of the ServiceTask node type in Flowable. The process diagram is drawn based on the business nodes, and the business types associated with the user are configured in the business nodes to complete the creation of the business process. In Flowable, you can define custom implementation methods for business nodes, parse the API in the business type, execute business operations, and write the operation results into process variables for subsequent nodes in the process to parse and use, thereby automating parameter passing and driving the flow of the business process.

2. The cloud platform business process driving method based on API and flowable according to claim 1, characterized in that, Business type registration management includes filling in API information and registering business types. The business type includes basic parameters and three API interfaces.

3. The cloud platform business process driving method based on API and flowable according to claim 2, characterized in that, The basic parameters of the business type include the business type's ID, name, description, service, URL, request method, header, request body, and return value.

4. The cloud platform business process driving method based on API and flowable according to claim 2, characterized in that, The three API interfaces include the Token API interface, the Execution API interface, and the Verification API interface.

5. The cloud platform business process driving method based on API and flowable according to claim 4, characterized in that, The TokenAPI interface is used to support scenarios where a token is required when calling business APIs, and the token used by subsequent APIs can be obtained through the TokenAPI. The execution API interface is the core API used to execute user business logic, and the business logic corresponding to the business type is realized through the execution API; The verification API interface is used to support asynchronous task scenarios. When executing the API, if the business logic being executed is complex, it is executed in an asynchronous manner. The execution result of the asynchronous task is obtained through the verification API to ensure that the current business processing is completed.

6. The cloud platform business process driving method based on API and flowable according to claim 2, characterized in that, In addition to the basic parameters of the business type, when defining an API, you also need to fill in the API request header template, request parameter template, and return value template. Placeholders in the form of ${key} are used in the template. The header template and request parameter template are used to define API request parameters and are not required. The return value template is used to validate the API execution result and map the parameter aliases of the execution result.

7. The cloud platform business process driving method based on API and flowable according to claim 1, characterized in that, The client draws business process diagrams based on the flowable process engine. When selecting process nodes, the serviceTask type of flowable is used. This type is an extension type of flowable and supports custom implementation of business logic for process nodes. Business nodes are implemented based on serviceTask.

8. The cloud platform business process driving method based on API and flowable according to claim 7, characterized in that, The client configures and selects the registered business type in the parameters of the business node, and also binds the business type to the business node by ID, and connects the business through the flowable process.

9. The cloud platform business process driving method based on API and flowable according to claim 1, characterized in that, In step three, after the user fills in the parameters required for process execution, the flowable process engine drives the business process to execute the user-configured business nodes sequentially according to the flowchart until the process is completed. When executing business nodes, the business nodes are custom-implemented based on serviceTask, which includes the following steps: Get the business type details based on the business type ID bound to the business node. If the business type includes TokenAPI, first call TokenAPI to get the token, replace the ${token} placeholder in the execution API and verification API header template in the business type with the token, and get the request header. Iterate through the API request parameter template, obtain the key of the placeholder in the parameter template, retrieve the parameter value corresponding to the key in the global parameter Map of the process, replace the placeholder corresponding to the key, and assemble and fill the complete request parameters in this way. Call the execution API to process the business logic of the business node. After the API execution is completed, match and verify the return value with the return value template. If they match, it means that the API call was successful; otherwise, an error is reported and the process ends. When performing return value validation, if the value of a field in the return value template corresponds to a placeholder, then obtain the key of the placeholder and save the corresponding parameter value in the return value to the global parameters of the process using the key as the keyword.

10. A cloud platform business process driven system based on APIs and flowables, characterized in that, include: The registration management module is used to register and save the business types corresponding to the business modules to the cloud platform via API through the user terminal. The cloud platform manages them uniformly and binds the associated business processes based on the business types registered by the user, thereby driving the execution of the business processes. The business process association module is used by the user to draw business process diagrams based on the flowable process engine. In the process nodes, business nodes are defined by custom implementation of the serviceTask node type in flowable. The process diagram is drawn based on the business nodes, and the associated business types of the user are configured in the business nodes to complete the creation of the business process. The process-driven module is used to define the implementation methods of custom business nodes in Flowable, parse the API in the business type, execute business operations, and write the operation results into process variables for subsequent nodes in the process to parse and use, thereby completing the automatic transmission of parameters and driving the flow of business processes.

Images