A computer business process control method, execution engine, device and medium

By using module configuration information to enable process phase reversals and module scheduling, the problem of high coupling between modules is solved, and module reuse and process universality are achieved.

CN114037413BActive Publication Date: 2026-03-17WUHAN ZILAN INFORMATION TECH CO LTD
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
CN202111293627.7
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2021-11-03
Publication Date
2026-03-17
Estimated Expiration
2041-11-03

AI Technical Summary

Technical Problem

The existing modular solutions under the process engine require external service integration, resulting in high coupling between modules and weak versatility.

Method used

By using the configuration information of modules, the process stages can be reversed and modules can be scheduled, reducing the coupling between modules. Modules can be reused and adapted to various processes.

Benefits of technology

It reduces the coupling between modules, allows modules to be reused, adapts to various processes, and has high versatility.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN114037413B_ABST
    Figure CN114037413B_ABST
Patent Text Reader

Abstract

The application discloses a computer business process control method, an execution engine, a device and a medium, and relates to the technical field of computer business process control. The method comprises the following steps: acquiring stage change notification of a target process; wherein the target process comprises multiple stages, and any stage comprises multiple modules; according to the type of the stage change notification and module configuration information, a corresponding target module is found; and the target module is triggered to execute function logic corresponding to the stage change notification, so as to realize stage change of the target process. In this way, the execution engine and the configuration information of the module can be used to realize twisting of a process stage and scheduling of a module, the coupling degree between modules is reduced, the module can be reused, the module can be adapted to various processes, and the generality is high.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the field of computer business process control, and in particular to a computer business process control method, execution engine, device and medium. Background Technology

[0002] Service-oriented architecture (SOA) is a component model that refers to different functional units of an application as services, connected by well-defined interfaces and contracts. These interfaces are defined in a neutral manner, independent of the hardware platform, operating system, and programming language used to implement the service. A process engine enables services built on various such systems to interact in a unified and universal way. For example, Flowable is a lightweight business process engine written in Java. Flowable allows the deployment of BPMN 2.0 process definitions, industry XML standards for defining processes, creating process instances of these definitions, running queries, accessing active or historical process instances and related data, and more.

[0003] Applications often include computer business processes, which typically consist of multiple stages. Each stage contains multiple independent modules, i.e., the aforementioned services. Existing module solutions based on process engines often require external services to interface with the process engine. The modules are called through interfaces based on the process engine. This interaction method places high demands on basic services, results in high coupling between modules, and lacks versatility. Summary of the Invention

[0004] In view of this, the purpose of this application is to provide a computer business process control method, execution engine, device, and medium, which can realize the reversal of process stages and the scheduling of modules through module configuration information, reduce the coupling between modules, allow modules to be reused, adapt to various processes, and have high versatility. The specific solution is as follows:

[0005] In a first aspect, this application discloses a computer business process control method, applied to an execution engine, comprising:

[0006] Obtain stage change notifications for the target process; wherein the target process includes multiple stages, and any stage includes multiple modules;

[0007] Based on the type of the phase change notification and the module configuration information, locate the corresponding target module;

[0008] The target module is triggered to execute the functional logic corresponding to the stage change notification in order to realize the stage change of the target process.

[0009] Optionally, the module configuration information includes a start flag, and correspondingly,

[0010] The step of finding the corresponding target module based on the type of the phase change notification and the module configuration information includes:

[0011] If the type is submission, then the module with the start flag set to the first preset flag value in the current stage of the target process is found according to the module configuration information, and the target module is obtained.

[0012] Optionally, the module configuration information may also include an end marker and an end condition;

[0013] Accordingly, after triggering the target module to execute the functional logic corresponding to the stage change notification, the method further includes:

[0014] During the execution of the functional logic by the target module, a module status change notification carrying the module status is obtained from the target module. It is determined whether the end flag of the target module is a second preset flag value. If it is a second preset flag value, it is determined whether the module status meets the end condition of the target module. If it does, the target module is marked as completed.

[0015] Based on the module configuration information, locate all modules in the current stage of the target process, determine whether all modules in the current stage of the target process have been executed. If all have been executed, notify the process engine to execute the next stage of the target process.

[0016] Optionally, before determining whether the end marker of the target module is a second preset flag value, the method further includes:

[0017] Based on the preset state recording identifier, determine whether it is necessary to record the module state. If it is necessary to record the module state, trigger the step of determining whether the end marker of the target module is a second preset flag value.

[0018] Optionally, the step of finding the corresponding target module based on the type of the stage change notification and the module configuration information includes:

[0019] If the type is rejection, then based on the module configuration information, find all modules between the current stage of the target process and the stage to which it was rejected, and obtain the target module;

[0020] If the type is termination, then based on the module configuration information, find all modules in the current stage of the target process to obtain the target module.

[0021] Optionally, obtaining the stage change notification of the target process includes:

[0022] Retrieve stage change notifications for the target process sent by the process engine.

[0023] Optional, also includes:

[0024] During the execution of the target process, log records are generated.

[0025] Secondly, this application discloses an execution engine, including:

[0026] A stage change notification acquisition module is used to acquire stage change notifications for a target process; wherein, the target process includes multiple stages, and any one of the stages includes multiple modules;

[0027] The target module search module is used to search for the corresponding target module based on the type of the phase change notification and the module configuration information.

[0028] The module function logic triggering module is used to trigger the target module to execute the functional logic corresponding to the stage change notification, so as to realize the stage change of the target process.

[0029] Thirdly, this application discloses an electronic device, including:

[0030] Memory, used to store computer programs;

[0031] A processor for executing the computer program, in accordance with the aforementioned computer business process control method.

[0032] Fourthly, this application discloses a computer-readable storage medium for storing a computer program, which, when executed by a processor, implements the aforementioned computer business process control method.

[0033] As can be seen, the execution engine in this application obtains the stage change notification of the target process, then finds the corresponding target module according to the type of the stage change notification and the module configuration information; finally, it triggers the target module to execute the functional logic corresponding to the stage change notification to realize the stage change of the target process. That is, after obtaining the stage change notification of the process, the embodiment of this application finds the corresponding target module according to the type of the stage change notification and the module configuration information, and executes the functional logic corresponding to the stage change notification. In this way, the reversal of process stages and the scheduling of modules can be realized through the execution engine and the configuration information of the modules, reducing the coupling between modules, making the modules reusable, adaptable to various processes, and highly versatile. Attached Figure Description

[0034] To more clearly illustrate the technical solutions in the embodiments of this application 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 embodiments of this application. For those skilled in the art, other drawings can be obtained based on the provided drawings without creative effort.

[0035] Figure 1 This is a flowchart of a computer business process control method disclosed in this application;

[0036] Figure 2 This is a schematic diagram of an execution engine structure disclosed in this application;

[0037] Figure 3 This is a structural diagram of an electronic device disclosed in this application. Detailed Implementation

[0038] 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, and 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.

[0039] Applications often include computer business processes, which typically consist of multiple stages, each containing several independent modules (i.e., the aforementioned services). Existing module solutions based on process engines often require external services to interface with the process engine, calling modules through interfaces based on the process engine. This interaction method places high demands on basic services, results in high coupling between modules, and lacks versatility. Therefore, this application provides a computer business process control scheme that can achieve process stage reversal and module scheduling through module configuration information, reducing coupling between modules. Modules are reusable, adaptable to various processes, and highly versatile.

[0040] See Figure 1 As shown in the figure, this application discloses a computer business process control method, applied to an execution engine, including:

[0041] Step S11: Obtain the stage change notification of the target process; wherein the target process includes multiple stages, and any stage includes multiple modules.

[0042] In a specific implementation, the stage change notification of the target process sent by the process engine can be obtained. This includes multiple instances of 2 or more.

[0043] Step S12: Locate the corresponding target module based on the type of the stage change notification and the module configuration information.

[0044] Step S13: Trigger the target module to execute the functional logic corresponding to the stage change notification in order to realize the stage change of the target process.

[0045] The module configuration information includes the module name, the stage to which the module belongs, and the process to which the module belongs.

[0046] In specific implementations, the corresponding target module can be found based on the module name, the stage to which the module belongs, and the process to which the module belongs. It should be noted that, according to the relationship between the stages and modules of different processes, the configuration is carried out according to the module dimension. The module name cannot be repeated in all stages of a process. The module name is the method name for the later execution engine scheduling. Different module configuration information is configured for different processes. The process engine and the execution engine are used to realize the stage reversal and module scheduling of different processes. The process engine reaches the execution engine through message notification. The execution engine processes according to the notification type. In this way, the module can be developed independently, can be reused, and has high versatility.

[0047] The module configuration information includes a start flag, and correspondingly,

[0048] The step of finding the corresponding target module based on the type of the phase change notification and the module configuration information includes:

[0049] If the type is submission, then the module with the start flag set to the first preset flag value in the current stage of the target process is found according to the module configuration information, and the target module is obtained.

[0050] Furthermore, the module configuration information also includes an end marker and an end condition;

[0051] Accordingly, after triggering the target module to execute the functional logic corresponding to the stage change notification, it also includes...

[0052] During the execution of the functional logic by the target module, a module status change notification carrying the module status is obtained from the target module. It is determined whether the end flag of the target module is a second preset flag value. If it is a second preset flag value, it is determined whether the module status meets the end condition of the target module. If it does, the target module is marked as completed.

[0053] Based on the module configuration information, the system locates all modules in the current stage of the target process and determines whether all modules in the current stage have been completed. If so, it notifies the process engine to execute the next stage of the target process. In a specific implementation, upon receiving the notification, the process engine sends a stage change notification for the target process to the execution engine, enabling the execution engine to schedule modules for the next stage.

[0054] In addition, before determining whether the end marker of the target module is a second preset flag value, the method further includes:

[0055] Based on the preset state recording identifier, determine whether it is necessary to record the module state. If it is necessary to record the module state, trigger the step of determining whether the end marker of the target module is a second preset flag value.

[0056] It should be noted that, according to the needs of the business process, the embodiments of this application can set a preset status record identifier for the status that needs to be recorded. When the module status is obtained, it is determined whether the module status needs to be recorded according to the preset status record identifier. If it needs to be recorded, it is determined whether the end mark of the target module is a second preset flag value. If it is a second preset flag value, it is determined whether the module status meets the end condition of the target module. If it is met, the target module is marked as completed. Specifically, the module status and the completion of execution can be recorded in the status table.

[0057] For example, determine whether the end flag of the target module is true. If so, determine whether the module state meets the end condition of the target module. If it does, mark the target module as completed.

[0058] Understandably, the end marker of the corresponding module can be configured to true according to the needs of the business process, while the end marker of some modules can be configured to false if the module status does not need to be monitored.

[0059] If the type is rejection, then based on the module configuration information, find all modules between the current stage of the target process and the stage to which it was rejected, and obtain the target module.

[0060] If the type is termination, then based on the module configuration information, find all modules in the current stage of the target process to obtain the target module.

[0061] For example, for a submission type: based on the module configuration information, find all modules whose start flag is true for the current stage of the target process, and execute the module's creation method. For a rejection type: based on the module configuration information, find all modules between the current stage of the process and the stage to which it is rejected, and execute the module's rejection method. For a termination type: based on the module configuration information, find all modules in the current stage of the process, and execute the termination method. It should be noted that the module's end flag can be set to true or false according to the process requirements. Setting it to false will mark the module as completed after the creation method is executed.

[0062] In addition, the embodiments of this application may also generate log records during the execution of the target process.

[0063] In a specific implementation, after the log recording is completed, all modules in the current stage of the target process can be found according to the module configuration information. It can be determined whether all modules in the current stage of the target process have been executed. If all have been executed, the process engine is notified to execute the next stage of the target process.

[0064] In other words, this embodiment first configures the modules according to their relationships with different process stages and modules, with each module's attributes, i.e., its configuration information, including: module name, start flag, end flag, end condition, stage, and process. A process engine and an execution engine are used to implement stage transitions and module scheduling for different processes. Different processes require different module configuration information. The process engine sends a stage change notification to the execution engine. The execution engine, based on the type of the stage change notification, finds the corresponding module and executes the corresponding functional logic. If the type is "Submission," it finds all modules with a start flag of true for the current process stage based on the module configuration information and executes the module's creation method. If the type is "Rejection," it finds all modules between the current process stage and the stage to which it was rejected based on the module configuration information and executes the module's rejection method. If the type is "Termination," it finds all modules in the current process stage based on the module configuration information and executes the termination method. When the type is "Submission," the execution engine notifies the module's status of the change. The execution engine, based on a preset status record identifier, determines whether to record the module's status in the status table. If recording is required, it calculates whether the current module status matches the end condition in the configuration information. If they match, the current module is marked as completed. This application embodiment can also record logs. After the logs are recorded, the execution engine finds all modules in the current stage according to the configuration information, and then determines whether these modules have been completed. If they have all been completed, the stage reversal condition is met, and the execution engine reverses the process engine to enable the process to enter the next stage. Otherwise, the current stage remains unchanged.

[0065] In this way, the stages of the process can be dynamically configured, with different stages configured for different processes, achieving a dynamic effect. Each stage contains multiple independent modules, which do not affect each other. The number of modules in each stage is determined by the configuration, and the execution of the modules is scheduled. The relationship between process stages and functional modules can be dynamically configured. Furthermore, different termination conditions can be configured for modules for different processes. The execution engine resolves the scheduling relationship between stages and modules based on the configuration.

[0066] As can be seen, the execution engine in this application obtains the stage change notification of the target process, then finds the corresponding target module according to the type of the stage change notification and the module configuration information; finally, it triggers the target module to execute the functional logic corresponding to the stage change notification to realize the stage change of the target process. That is, after obtaining the stage change notification of the process, the embodiment of this application finds the corresponding target module according to the type of the stage change notification and the module configuration information, and executes the functional logic corresponding to the stage change notification. In this way, the reversal of process stages and the scheduling of modules can be realized through the execution engine and the configuration information of the modules, reducing the coupling between modules, making the modules reusable, adaptable to various processes, and highly versatile.

[0067] The following example, using the franchisee onboarding process, details the computer business process control solution provided in this application:

[0068] The franchisee onboarding process is divided into 9 main stages: document submission, interview and review, training, access review, site selection, signing, store construction, construction and decoration, and online application. Each stage's modules are configured. For example, the training stage includes 4 modules: Confidentiality Agreement, Letter of Intent, Training, and Background Check. Module configuration information includes: Module Name: Confidentiality Agreement, Start Flag: true, End Flag: true, End Condition: Complete; Module Name: Letter of Intent, Start Flag: true, End Flag: true, End Condition: Complete; Module Name: Training, Start Flag: false, End Flag: true, End Condition: Complete; Module Name: Background Check, Start Flag: true, End Flag: false, End Condition: Not configured.

[0069] In the current process, after selecting the submit instruction during the interview review stage, the execution engine receives the submit notification. At this point, the process is in the learning and training phase. It identifies the modules marked as "true" in the configuration: Confidentiality Agreement, Letter of Intent, and Background Check, and executes their creation methods. Since the end marker for the Background Check is "false," the current module is marked as completed upon creation. When the Confidentiality Agreement status changes, the execution engine is notified. The engine then checks if the current status is complete. If it is, the current module is marked as completed in the status table. The execution engine then queries all modules in the current stage and checks the status table to see if all modules are completed. If all are completed, the process engine is notified to proceed to the next stage.

[0070] When the current process selects a termination instruction during the interview review stage, the execution engine receives the termination notification, locates all modules of the current process through the configuration, and executes the corresponding termination operations.

[0071] The current process selected a rejection instruction during the signing stage, reverting to the learning and training stage. When the execution engine receives the rejection notification, it locates all modules in all stages between learning and training and signing based on the configuration, and executes the corresponding rejection operations.

[0072] See Figure 2 As shown in the figure, an execution engine is disclosed in this application embodiment, including:

[0073] The stage change notification acquisition module 11 is used to acquire stage change notifications of the target process; wherein, the target process includes multiple stages, and any one of the stages includes multiple modules;

[0074] The target module search module 12 is used to search for the corresponding target module based on the type of the stage change notification and the module configuration information.

[0075] The module function logic triggering module 13 is used to trigger the target module to execute the function logic corresponding to the stage change notification.

[0076] As can be seen, the execution engine in this application obtains the stage change notification of the target process, then finds the corresponding target module according to the type of the stage change notification and the module configuration information; finally, it triggers the target module to execute the functional logic corresponding to the stage change notification to realize the stage change of the target process. That is, after obtaining the stage change notification of the process, the embodiment of this application finds the corresponding target module according to the type of the stage change notification and the module configuration information, and executes the functional logic corresponding to the stage change notification. In this way, the reversal of process stages and the scheduling of modules can be realized through the execution engine and the configuration information of the modules, reducing the coupling between modules, making the modules reusable, adaptable to various processes, and highly versatile.

[0077] The module configuration information includes a start flag, and correspondingly,

[0078] The target module search module 12 is specifically used to search for the module whose start flag is a first preset flag value in the current stage of the target process, based on the module configuration information, if the type is submission, and thus obtain the target module.

[0079] Furthermore, the module configuration information also includes an end marker and an end condition.

[0080] Accordingly, the execution engine also includes:

[0081] The module status acquisition module is used to acquire the module status change notification of the target module carrying the module status during the execution of the functional logic corresponding to the stage change notification by the target module after the module function logic triggering module 13 triggers the target module to execute the functional logic.

[0082] The end marker determination module is used to determine whether the end marker of the target module is a second preset flag value. If it is a second preset flag value, the end marker determination module is used to determine whether the end marker of the target module is a second preset flag value.

[0083] The termination condition determination module is used to determine whether the module state satisfies the termination condition of the target module if the termination mark determination module determines that the termination mark is a first preset flag value.

[0084] The execution completion marking module is used to mark the target module as executed successfully if the termination condition judgment module determines that the module state meets the termination condition of the target module.

[0085] The stage execution completion judgment module is used to find all modules in the current stage of the target process according to the module configuration information, and determine whether all modules in the current stage of the target process have been executed. If all have been executed, the process engine is notified to execute the next stage of the target process.

[0086] The preset state recording identifier module is used to determine whether the module state needs to be recorded based on the preset state recording identifier. If the module state needs to be recorded, the end marker judgment module is triggered to perform the step of judging whether the end marker of the target module is a second preset flag value.

[0087] The target module lookup module 12 is used to find all modules between the current stage of the target process and the stage where it was rejected, based on the module configuration information, if the type is rejection, to obtain the target module.

[0088] The target module search module 12 is used to search for all modules in the current stage of the target process according to the module configuration information if the type is termination, and obtain the target module.

[0089] The Phase Change Notification Acquisition Module 11 is specifically used to acquire phase change notifications for the target process sent by the process engine.

[0090] Furthermore, the execution engine also includes:

[0091] The log generation module is used to generate log records during the execution of the target process.

[0092] See Figure 3 As shown in the figure, this application discloses an electronic device 20, including a processor 21 and a memory 22; wherein, the memory 22 is used to store a computer program; the processor 21 is used to execute the computer program, the computer business process control method disclosed in the foregoing embodiment.

[0093] For details regarding the specific process of the above-mentioned computer business process control method, please refer to the relevant content disclosed in the foregoing embodiments, which will not be repeated here.

[0094] Furthermore, the memory 22, as a carrier for resource storage, can be a read-only memory, random access memory, disk, or optical disk, and the storage method can be temporary storage or permanent storage.

[0095] In addition, the electronic device 20 also includes a power supply 23, a communication interface 24, an input / output interface 25, and a communication bus 26; wherein, the power supply 23 is used to provide operating voltage for the various hardware devices on the electronic device 20; the communication interface 24 can create a data transmission channel between the electronic device 20 and external devices, and the communication protocol it follows can be any communication protocol applicable to the technical solution of this application, and is not specifically limited here; the input / output interface 25 is used to acquire external input data or output data to the outside world, and its specific interface type can be selected according to specific application needs, and is not specifically limited here.

[0096] Furthermore, embodiments of this application also disclose a computer-readable storage medium for storing a computer program, wherein the computer program, when executed by a processor, implements the computer business process control method disclosed in the foregoing embodiments.

[0097] For details regarding the specific process of the above-mentioned computer business process control method, please refer to the relevant content disclosed in the foregoing embodiments, which will not be repeated here.

[0098] The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on its differences from other embodiments. Similar or identical parts between embodiments can be referred to interchangeably. As for the execution engine disclosed in the embodiments, since it corresponds to the method disclosed in the embodiments, the description is relatively simple; relevant parts can be referred to the method section.

[0099] The steps of the methods or algorithms described in conjunction with the embodiments disclosed herein can be implemented directly by hardware, a software module executed by a processor, or a combination of both. The software module can be located in random access memory (RAM), main memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art.

[0100] The above provides a detailed description of a computer business process control method, execution engine, device, and medium provided in this application. Specific examples have been used to illustrate the principles and implementation methods of this application. The descriptions of the above embodiments are only for the purpose of helping to understand the method and core ideas of this application. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of this application. Therefore, the content of this specification should not be construed as a limitation of this application.

Claims

1. A computer business process control method, characterized by, The application is applied to an execution engine, comprising: Obtaining a stage change notification of a target process sent by a process engine; wherein the target process comprises a plurality of stages, and any stage comprises a plurality of modules; According to the type of the stage change notification and module configuration information, a corresponding target module is found; Triggering the target module to execute the function logic corresponding to the stage change notification to realize the stage change of the target process; The module configuration information comprises a module name, a stage to which the module belongs, and a process to which the module belongs, and the corresponding target module is found according to the module name, the stage to which the module belongs, and the process to which the module belongs; the modules in all stages of one process have different names, the module configuration information of different processes is configured, the process engine and the execution engine are used to realize the stage change and module scheduling of different processes, the process engine reaches the execution engine through message notification, and the execution engine is processed according to the notification type; The module configuration information further comprises an end marker and an end condition; correspondingly, after the target module executes the function logic, the module state change notification carrying the module state of the target module is obtained in the process in which the target module executes the function logic, it is judged whether the end marker of the target module is a second preset flag value, if the end marker is the second preset flag value, it is judged whether the module state satisfies the end condition of the target module, if yes, the target module is marked as execution completed; all modules in the current stage of the target process are found according to the module configuration information, it is judged whether all the modules in the current stage of the target process have been executed, if yes, the process engine is notified to execute the next stage of the target process, and the process engine sends the stage change notification of the target process to the execution engine after receiving the notification, so that the execution engine schedules the modules in the next stage.

2. The computer business process control method of claim 1, wherein, The module configuration information comprises a start flag, and correspondingly, The target module is found according to the module configuration information if the type is submission and the start flag in the current stage of the target process is a first preset flag value. Before judging whether the end marker of the target module is a second preset flag value, the following step is further included:

3. The computer business process control method of claim 2, wherein, According to the preset state record identifier, it is judged whether the module state needs to be recorded, if the module state needs to be recorded, the step of judging whether the end marker of the target module is a second preset flag value is triggered. The target module is found according to the module configuration information if the type is submission and the start flag in the current stage of the target process is a first preset flag value.

4. The computer business process control method of claim 1, wherein, The target module is found according to the module configuration information if the type is submission and the start flag in the current stage of the target process is a first preset flag value. The target module is found according to the module configuration information if the type is submission and the start flag in the current stage of the target process is a first preset flag value. ​ 5. The computer business process control method according to any one of claims 1 to 4, characterized by, Also include: Generate log records during the execution of the target process.

6. An execution engine, comprising: Include: Stage change notification acquisition module, for acquiring the stage change notification of the target process sent by the process engine; wherein the target process includes multiple stages, and any stage includes multiple modules; Target module searching module, for searching the corresponding target module according to the type of the stage change notification and the module configuration information; Module function logic triggering module, for triggering the target module to execute the function logic corresponding to the stage change notification, so as to realize the stage change of the target process; Wherein, the module configuration information includes module name, module belonging stage, and module belonging process, and the corresponding target module is searched according to the module name, the module belonging stage, and the module belonging process; the modules are configured according to the association relationship between the stages and the modules of different processes in the dimension of the modules, the module names in all stages of a process are not repeated, different module configuration information is configured for different processes, the process engine and the execution engine are used to realize the stage change and the module scheduling of different processes, the process engine reaches the execution engine through message notification, and the execution engine is processed according to the notification type; The module configuration information also includes end mark and end condition; correspondingly, after triggering the target module to execute the function logic corresponding to the stage change notification, it also includes: acquiring the module state change notification carrying the module state of the target module in the process that the target module executes the function logic, judging whether the end mark of the target module is a second preset flag value, if it is the second preset flag value, judging whether the module state meets the end condition of the target module, if it meets, marking the target module as execution completed; searching all modules of the current stage of the target process according to the module configuration information, judging whether all modules of the current stage of the target process have been executed, if yes, notifying the process engine to execute the next stage of the target process, and the process engine sends the stage change notification of the target process to the execution engine after receiving the notification, so that the execution engine schedules the modules of the next stage.

7. An electronic device, comprising: Include: Memory, for saving computer programs; Processor, for executing the computer programs to realize the computer business process control method in any one of claims 1 to 5.

8. A computer-readable storage medium, characterized in that, For saving computer programs, the computer programs are executed by the processor to realize the computer business process control method in any one of claims 1 to 5.

Citation Information

Patent Citations

  • Task flow processing method, storage medium and processor

    CN112286521A