Plug-in type workflow management system, electronic device, and business workflow management method

Abstract

We provide a plug-in workflow management system, electronic device, and business workflow management method in the field of computers. The plug-in workflow management system includes N memory spaces and N business plug-ins, where N is an integer greater than or equal to 2, and each business plug-in corresponds to an independent memory space. Each business plug-in is configured to receive business data to be processed, store the business data to be processed in the corresponding memory space, copy the business data to be processed, and process the copied business data to be processed. This solves the problem in conventional plug-in workflow management systems that, when an error occurs in a plug-in, the entire business workflow must be restarted from the beginning, which takes a lot of time.

Description

[Technical Field]

[0001] The present application belongs to the field of computers, and specifically relates to a plug-in type workflow management system, an electronic device, and a business workflow management method. [Background technology]

[0002] A plug-in workflow management system has the advantage of enabling the deployment of business projects and facilitating the establishment of business projects, and is therefore widely used in business approval workflows, software development workflows, etc. A plug-in workflow management system includes a workflow management component and a set of parameterized business plug-ins. The workflow management component provides functions such as querying all business plug-ins, establishing and deploying business projects by configuring and deploying business plug-ins, and executing and scheduling business plug-ins.

[0003] In current plug-in workflow management systems, when a task is executed, a higher-level plug-in processes the received data and sends it to a lower-level plug-in, which then processes the received data and sends it to a further lower-level plug-in. If an error occurs in a plug-in, the entire task workflow must be restarted from the beginning. Summary of the Invention [Problem to be solved by the invention]

[0004] In view of this, an object of the present application is to provide a plug-in type workflow management system, an electronic device, and a business workflow management method that can solve the problem in conventional plug-in type workflow management systems where, when an error occurs in a plug-in, the entire business workflow must be restarted and executed from the beginning, which takes a lot of time. [Means for solving the problem]

[0005] An embodiment of the present application is realized as follows.

[0006] In a first aspect, an embodiment of the present application provides a plug-in workflow management system, which includes N memory spaces and N business plug-ins, where N is an integer greater than or equal to 2, each of the business plug-ins corresponding to an independent memory space, and each of the business plug-ins is configured to receive business data to be processed, store the business data to be processed in the corresponding memory space, copy the business data to be processed, and process the copied business data to be processed.

[0007] In the embodiment of the present application, each business plug-in corresponds to one independent memory space, and each business plug-in stores the business data it receives as the target of processing in the corresponding memory space. In this way, when an error occurs in a business plug-in, rather than restarting the entire workflow from the beginning, the data in the memory space can be read directly by the business plug-in in which the error occurred and re-executed, thereby significantly improving processing efficiency.

[0008] In one possible embodiment of the example of the first aspect, each of the business plug-ins is further configured to, in response to a re-execution command, re-process the pre-stored business data to be processed and transmit the re-processed business data.

[0009] In the embodiment of the present application, each business plug-in responds to a re-execution command by re-processing the pre-stored business data to be processed and transmitting the re-processed business data. In this way, when an error occurs in a business plug-in, rather than restarting and executing the entire workflow from the beginning, the business plug-in in which the error occurred can directly read the data in memory space and re-execute it, thereby significantly improving processing efficiency.

[0010] In one possible embodiment of the first aspect of the embodiment, the plug-in type workflow management system further includes a workflow management component, the workflow management component is connected to each of the business plug-ins, and the workflow management component is configured to, when business data needs to be re-executed in a lower-level business plug-in, determine a target business plug-in for re-executing the business and send a re-execution command to the target business plug-in.

[0011] In an embodiment of the present application, by sending a re-execution command to a target business plug-in that uses a workflow management component to re-execute a business, the target business plug-in is instructed to re-process the business data to be processed that has been stored in advance, eliminating the need to re-execute the entire workflow from the beginning, thereby significantly improving processing efficiency.

[0012] In one possible embodiment of the example of the first aspect, the plug-in type workflow management system further includes a shared memory space, the shared memory space is configured to store business data shared by a plurality of business plug-ins, and each independent memory space of the business plug-ins is configured to store business data specific to that business plug-in.

[0013] In the embodiment of the present application, by using a shared memory space to store business data shared by multiple business plug-ins, the number of times the same data is sent can be reduced, thereby improving execution efficiency.

[0014] In one possible embodiment of the first aspect of the invention, each business plug-in has a sleep state and a work state, and power consumption in the sleep state is less than power consumption in the work state.

[0015] In an embodiment of the present application, each business plug-in includes a sleep state and a work state, and in this way, the business plug-ins can be configured to be in different states, for example, each business plug-in is in a "sleep" state after the execution of all workflows has finished, thereby saving power consumption.

[0016] In one possible embodiment of the embodiment of the first aspect, each business plug-in is further configured to delete the business data to be processed stored therein in response to a deletion command.

[0017] In the embodiment of the present application, in order to save the cost of data storage, after the whole workflow is accomplished, a business workflow for cleaning data is automatically started, so that each business plug-in deletes its own stored data.

[0018] In one possible embodiment of the embodiment of the first aspect, each of the business plug-ins is a single plug-in or a combination plug-in, and the combination plug-in includes a plurality of single plug-ins.

[0019] In the embodiment of the present application, multiple single plug-ins can be combined and used as a combined plug-in, which simplifies the maintenance of the system structure and business workflow by combining a series of complex workflows into one combined plug-in, and reduces the difficulty of use.

[0020] In a second aspect, an embodiment of the present application further provides a plug-in type workflow management system, the plug-in type workflow management system including N business plug-ins and a workflow management component, each of the business plug-ins configured to store received business data to be processed in a corresponding memory space, copy the business data to be processed, and process the copied business data to be processed, where N is an integer greater than or equal to 2, the workflow management component is connected to each of the business plug-ins, and when the business data needs to be re-executed by a lower-level business plug-in, the workflow management component is configured to determine a target business plug-in to re-execute the business data and send a re-execution command to the target business plug-in, and the target business plug-in is configured to re-process the pre-stored business data to be processed in response to the re-execution command and send the re-processed business data.

[0021] In a third aspect, an embodiment of the present application further provides an electronic device, the electronic device including a workflow management system according to the embodiment of the first aspect and / or any one of possible embodiments based on the embodiment of the first aspect, or a workflow management system according to the embodiment of the second aspect.

[0022] In a fourth aspect, an embodiment of the present application further provides a business workflow management method, which includes the steps of, when business data needs to be re-executed by a lower-level business plug-in, determining a target business plug-in to re-execute the business data by a workflow management component and sending a re-execution command to the target business plug-in, the target business plug-in responding to the re-execution command to re-process input business data that was backed up in advance and sending the re-processed business data, and, when all business plug-ins below the target business plug-in receive the business data to be processed from the business plug-in one level above it, storing the business data to be processed in a corresponding memory space, copying the business data to be processed, and processing the copied business data to be processed.

[0023] In one possible embodiment of the fourth aspect, the method further includes obtaining, by the workflow management component, the position of the target business plug-in in the entire business workflow; obtaining, by the workflow management component, all business plug-ins after the target business plug-in; and sending, by the workflow management component, a save command to all business plug-ins after the target business plug-in, wherein the save command instructs the business plug-ins to store the received business data to be processed in corresponding memory spaces.

[0024] Other features and advantages of the present application will be described hereinafter. The objectives and other advantages of the present application will be realized and attained by the structure particularly pointed out in the description and drawings. [Brief explanation of the drawings]

[0025] In order to more clearly describe the embodiments of the present application or the technical solutions of the prior art, the drawings used in the embodiments will be briefly described below. The drawings described only show some embodiments of the present application. Those skilled in the art can obtain other drawings based on these drawings without using inventive ability. The drawings will make the above and other objects, features and advantages of the present application more apparent. [Figure 1] 1 is a schematic diagram illustrating the principle of a plug-in type workflow management system according to an embodiment of the present application; [Figure 2] FIG. 2 is a schematic configuration diagram of a combination of plug-ins according to an embodiment of the present application. [Figure 3] FIG. 2 is a schematic diagram equivalent to FIG. 1. [Figure 4] FIG. 10 is a schematic diagram illustrating the principle of another plug-in type workflow management system according to an embodiment of the present application. [Figure 5] 1 is a schematic flowchart of a business workflow management method according to an embodiment of the present application; [Figure 6] 1 is a schematic configuration diagram of an electronic device according to an embodiment of the present application. DETAILED DESCRIPTION OF THE INVENTION

[0026] The technical solutions of the embodiments of the present application will be described below with reference to the drawings used in the embodiments of the present application. The described embodiments are only some of the embodiments of the present application, not all of the embodiments. The following embodiments are merely illustrative to more clearly explain the technical solutions of the present application, and do not limit the scope of protection of the present application. As will be understood by those skilled in the art, the following embodiments and features in the embodiments can be combined with each other unless there is a contradiction.

[0027] The terms "having" and "including" and any variations thereof are intended to cover a non-exclusive inclusion. Thus, a process, method, article, or device that includes a set of elements is not limited to those elements and may include other elements not specified or inherent to the process, method, article, or device. Unless otherwise specified, an element limited by the phrase "comprising" does not exclude the situation where the process, method, article, or device that includes the element also includes other similar elements.

[0028] The term "and / or" in this application expresses a relationship between related objects and expresses a three-way relationship, for example, A and / or B expresses a three-way relationship in which only A is present, both A and B are present, or only B is present.

[0029] In the current plug-in type workflow management system, when an error occurs in the operation of a business plug-in, the entire business workflow must be restarted and executed from the beginning, which takes a lot of time. It is desirable to save the time required for the workflow and make it possible to repeatedly execute each business plug-in, so that when an error occurs in a business plug-in, the error can be corrected and execution can continue from the current business plug-in, rather than restarting and executing from the beginning.

[0030] In view of this, the plug-in type workflow management system according to the embodiment of the present application supports the parallel execution of business flows and allows each business plug-in to save its own input data. As a result, when an error occurs in a business plug-in, the error can be corrected in the current business plug-in and execution can continue, rather than restarting and executing the entire workflow from the beginning.

[0031] For better understanding, a plug-in workflow management system according to an embodiment of the present application will be described below with reference to FIG. 1. The plug-in workflow management system includes N memory spaces and N business plug-ins, where N is an integer equal to or greater than 2. The value of N is determined by the complexity of the business project; the more complex the business project to be processed, the more business plug-ins are required. For example, the configuration of the plug-in workflow management system when used for a business approval workflow differs from the configuration of the plug-in workflow management system when used for a development workflow.

[0032] If a plug-in workflow management system is considered to be a single application (for example, a business approval application or a software development application), the business plug-ins can be considered as functional modules that make up the entire application. As the application's design functions increase, the number of corresponding business plug-ins also increases. To add a certain business function, a business plug-in is added and a collaborative relationship is established between the added business plug-in and the existing business plug-ins, thereby achieving the purpose of adding the function. These N memory spaces can belong to the same storage device, and the memory space of the storage device can be divided into N spaces, with each business plug-in corresponding to an independent memory space.

[0033] A specific business project is realized through the cooperation of these N business plug-ins. These N business plug-ins are connected in series or in a manner including both series and parallel connections according to the needs of the business project to process the specific business project. For example, Business Plug-in 1, Business Plug-in 2, Business Plug-in 3, Business Plug-in 4, and Business Plug-in 5 shown in Figure 1 are all business plug-ins, and Business Plug-in 1, Business Plug-in 4, and Business Plug-in 5 are connected in series, Business Plug-in 1, Business Plug-in 2, Business Plug-in 3, and Business Plug-in 5 are connected in series, and Business Plug-in 4, Business Plug-in 2, and Business Plug-in 3 are connected in parallel.

[0034] In a conventional workflow, Business Plug-in 2, Business Plug-in 3, and Business Plug-in 4 cannot run in parallel, and if parallel processing is required, two different tasks must generally be created. In a parallel business workflow, they can run in parallel as different business plug-ins of the same task, saving workflow time.

[0035] Business plug-ins send data to other business plug-ins in either parallel or serial connection, and read and execute them sequentially. When executed in serial connection, the higher-level plug-in stores the data in its own memory space, copies the data, processes it, and provides the processed data to the lower-level plug-in. After receiving data from the higher-level plug-in, the lower-level plug-in stores the data in its own memory space, copies the data, processes it, and sends the new processed data to the plug-in further down the line.

[0036] The structure of a plug-in workflow management system is not limited to that shown in Figure 1; the corresponding structure varies depending on the processing task. In other words, the connection method for these N business plug-ins can be changed or the value of N can be increased or decreased depending on the processing target and usage scenario.

[0037] Each business plug-in may be a single plug-in or a combination plug-in, and a combination plug-in may include multiple single plug-ins. For example, in one embodiment, business plug-in 2, business plug-in 3, and business plug-in 4 in FIG. 1 are combined to form a new combination plug-in. Such a combination plug-in may be called a template plug-in, and its principle is shown in FIG. 2. Business projects in a plug-in-based workflow management system are configured to support template plug-ins. Such a plug-in is not a specific business plug-in, but a new plug-in built by combining other business plug-ins. A business project can directly use such a template plug-in as a single business plug-in. In this way, by combining a series of complex workflows into a single template plug-in, business workflow maintenance can be simplified and the difficulty of use can be reduced.

[0038] In an alternative embodiment, the plug-in type workflow management system shown in Fig. 1 can be simplified as the plug-in type workflow management system shown in Fig. 3. The combination plug-in 2 shown in Fig. 3 includes the business plug-in 2, business plug-in 3, and business plug-in 4 in Fig. 1. Regardless of whether the business plug-in is a single plug-in or a combination plug-in, each business plug-in corresponds to one memory space, for example, the combination plug-in in Fig. 3 corresponds to memory space 2'.

[0039] Each business plug-in is classified as a higher-level plug-in or a lower-level plug-in based on its position in the workflow of the business project. A lower-level plug-in is configured to process business data (i.e., business data to be processed) from the higher-level plug-in connected to it. Multiple lower-level plug-ins may be connected in series below a certain business plug-in, and these lower-level plug-ins run in parallel, each processing its own business data. Further sub-tasks may be connected in series within each parallel task, and may be aggregated into a single business plug-in that supports multiple inputs.

[0040] Each business plug-in corresponds to one independent memory space, which allows each business plug-in to save its own input data. Each business plug-in is configured to receive business data to be processed, store the business data to be processed in the corresponding memory space, copy the received business data to be processed, process the copied business data to be processed, and transmit the processed data.

[0041] Depending on the business plug-in, the processing method for processing received business data differs, and depending on the application scenario, the corresponding processing method also differs. For example, processing methods include, but are not limited to, data calculation, data transfer, format conversion, data filtering, etc.

[0042] Since each business plug-in has its own corresponding memory space, it can support processing of multiple types of data streams. Even if simultaneous processing of data streams is not possible, the data is first stored in the memory space, and when processing is possible, the business data is copied from the memory space and processed.

[0043] In the plug-in workflow management system according to the embodiment of the present application, each business plug-in has its own corresponding memory space, so when processing a data stream, the business data to be processed is stored in the corresponding memory space, and parallel processing is supported. Furthermore, since each business plug-in can save its own input data, when an error occurs in a business plug-in, the current business plug-in can correct the error and continue execution, rather than restarting the entire workflow from the beginning, thereby significantly improving processing efficiency.

[0044] Since each business plug-in copies upper-level business data and performs processing based on the copied business data, there is no change in the original upper-level data, and thus when it is necessary to redo and execute a business workflow, there is no need to redo the execution from the beginning, and execution can be resumed by simply changing the location of the problematic business plug-in.

[0045] In one alternative embodiment, each business plug-in is further configured to, in response to a re-execution command, re-process the pre-stored target business data and transmit the re-processed business data. In this way, when an error occurs in a business plug-in, the error is corrected and execution continues from the current business plug-in, rather than restarting execution from the beginning.

[0046] In an alternative embodiment, the plug-in workflow management system further includes a workflow management component connected to each of the business plug-ins. When business data needs to be re-executed by a lower-level business plug-in, the workflow management component is configured to determine a target business plug-in for re-executing the business and send a re-execution command to the target business plug-in. In response to the re-execution command, the target business plug-in then re-processes the previously stored target business data and sends the re-processed business data.

[0047] Subordinate business plug-ins are distinguished based on the location of the business plug-in in the plug-in workflow management system, and all business plug-ins that are not located at the beginning (or tip) can be called subordinate business plug-ins. For example, in FIG. 1, Business Plug-in 2, Business Plug-in 3, Business Plug-in 4, and Business Plug-in 5 are subordinate business plug-ins to Business Plug-in 1. Any one of the above business plug-ins can function as a business plug-in that re-executes business data if an error occurs during operation.

[0048] The workflow management component establishes and arranges business projects by configuring and arranging business plug-ins, executes and schedules functions of the business plug-ins, etc., and instructs each business plug-in to cooperate in accomplishing the business project by sending respective setting instructions to each business plug-in.

[0049] In an alternative embodiment, it is also possible to configure whether each business plug-in saves input data. If a business plug-in does not save input data, the lower-level plug-ins of that business plug-in will not be able to re-acquire the same input data, and therefore cannot be used as the starting plug-in for re-execution. If a business needs to be re-executed, the only option is to start execution from a business plug-in that precedes that business plug-in. Whether each business plug-in saves input data can be configured by sending a command from the workflow management component.

[0050] In an alternative embodiment, to save data storage costs, after the entire workflow is completed, each business plug-in may automatically start a business workflow for cleaning data so that the business plug-in deletes its stored data. In this embodiment, each business plug-in is further configured to delete the business data to be processed stored therein in response to a deletion command. The deletion command is sent by the workflow management component, and after the entire workflow is completed, the workflow management component sends the deletion command to each business plug-in, and each business plug-in responds to the deletion command and deletes the business data to be processed stored therein.

[0051] In an alternative embodiment, each business plug-in has its own unique attributes, such as a sleep state and a work state. The sleep state consumes less power than the work state. A business plug-in with such attributes enters a "sleep" state after the entire workflow has finished executing. After the user prepares new configuration data, the business plug-in is triggered again to return from the sleep state to the work state and continue execution. The business plug-in can be configured to enter different states by sending commands from the workflow management component.

[0052] In an alternative embodiment, the plug-in workflow management system further includes a shared memory space (not shown). The shared memory space is configured to store business data shared by multiple business plug-ins. Each business plug-in has its own independent memory space configured to store business data specific to that business plug-in. The business data is classified into global data and business plug-in specific data. When establishing a business, if more than one plug-in is required for the required deployment name, the data type is global data; otherwise, it is plug-in specific data. Storing global data in the shared memory space shared by each business plug-in eliminates the need for a business initiator to repeatedly input duplicate data when starting a business; the global data can simply be stored in the shared memory space.

[0053] Based on the same inventive idea, an embodiment of the present application further provides a plug-in workflow management system, which includes N business plug-ins and a workflow management component, where N is an integer equal to or greater than 2, as shown in FIG.

[0054] A specified business project is accomplished through the cooperation of N business plug-ins. Each business plug-in is configured to store the received business data to be processed in a corresponding memory space, copy the business data to be processed, and process the copied business data to be processed.

[0055] A workflow management component is connected to each of the business plug-ins. When business data needs to be re-executed by a lower-level business plug-in, the workflow management component is configured to determine the target business plug-in that will re-execute the business data and send a re-execution command to the target business plug-in. In response to the re-execution command, the target business plug-in is configured to re-process the pre-stored target business data and send the re-processed business data.

[0056] The implementation principle and technical effects of the above plug-in workflow management system (FIG. 4) are the same as those of the embodiment of the plug-in workflow management system shown in FIG. 1. For ease of explanation, for the content not mentioned in this embodiment, reference can be made to the corresponding content in the embodiment of the plug-in workflow management system described above.

[0057] Based on the same inventive idea, an embodiment of the present application further provides a business workflow management method. The business workflow management method will be described below with reference to Fig. 5. The business workflow management method shown in Fig. 5 can be used in the above-mentioned plug-in type workflow management system.

[0058] S1: When business data needs to be re-executed by a lower-level business plug-in, the workflow management component determines the target business plug-in that will re-execute the business data, and sends a re-execution command to the target business plug-in.

[0059] When an error occurs in the operation of a certain business plug-in and the business data needs to be re-executed by a lower-level business plug-in, the workflow management component determines the target business plug-in that will re-execute the business data and sends a re-execution command to the target business plug-in.

[0060] S2: The target business plug-in responds to the re-execution command, re-processes the input business data that was backed up in advance, and transmits the re-processed business data.

[0061] Each business plug-in stores input business data in a corresponding memory space, and when it receives a re-execution command later, it re-processes the input business data that was backed up in advance, and transmits the re-processed business data.

[0062] S3: When all the business plug-ins subsequent to the target business plug-in receive the business data to be processed from the business plug-in one level above, they store the business data to be processed in the corresponding memory space, copy the business data to be processed, and process the copied business data to be processed.

[0063] Each business plug-in is configured to receive the business data to be processed, store the business data to be processed in the corresponding memory space, copy the business data to be processed, and process the copied business data to be processed. In this way, after the target business plug-in of a lower-level business plug-in re-executes the business data, all business plug-ins below the target business plug-in, when they each receive the business data to be processed from the business plug-in one level above it, store the business data to be processed in the corresponding memory space, copy the business data to be processed, and process the copied business data to be processed.

[0064] Optionally, the method further includes using a workflow management component to obtain the position of the target business plug-in in the entire business workflow, using the workflow management component to obtain all business plug-ins after the target business plug-in, and sending a save command to all business plug-ins after the target business plug-in. The save command instructs the business plug-in to store the received business data to be processed in the corresponding memory space. In this embodiment, whether each business plug-in saves the received input data can be configured, and the configuration method is relatively simple; it only requires sending a corresponding configuration command. For example, sending a save command instructs the business plug-in to save the received input data.

[0065] Optionally, the method further includes the workflow management component sending a deletion command to each business plug-in after the entire workflow has been accomplished, and each business plug-in responding to the deletion command deletes the business data to be processed stored therein.

[0066] The implementation principles and technical effects of the business workflow management method according to the embodiments of the present application are the same as those of the above-mentioned plug-in workflow management system embodiments. For the sake of simplicity, for the contents not mentioned in the method embodiments, reference can be made to the corresponding contents in the above-mentioned plug-in workflow management system embodiments.

[0067] An embodiment of the present application further provides an electronic device. The electronic device includes the plug-in type workflow management system. Optionally, as shown in FIG. 6 , the electronic device 200 includes a transceiver 210, a storage device 220, a communication bus 230, and a processor 240. Various plug-ins in the plug-in type workflow management system are located in the processor 240. The memory space in the plug-in type workflow management system is provided by the storage device 220. The storage device 220 is divided into N memory spaces that correspond one-to-one to the N business plug-ins.

[0068] The transceiver 210, the storage device 220, and the processor 240 are electrically connected to each other directly or indirectly to transmit or exchange data. For example, these elements are electrically connected to each other via one or more communication buses 230 or signal lines. The transceiver 210 is used for transmitting and receiving data. The storage device 220 is configured to store computer programs, and for example, the storage device 220 stores computer programs necessary for executing the business workflow management method. The computer programs include at least one software function module stored in the storage device 220 in the form of software or firmware or written into the operating system (OS) of the electronic device 200. The processor 240 is configured to execute the executable modules stored in the storage device 220 to execute the business workflow management method.

[0069] The memory device 220 may be, but is not limited to, a random access memory (RAM), a read only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or the like.

[0070] The processor 240 may be an integrated circuit chip having signal processing capabilities. The processor may be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, capable of implementing or executing the methods, steps, and logic blocks according to embodiments of the present application. Alternatively, the processor 240 may be any conventional processor.

[0071] The electronic device 200 includes, but is not limited to, a tablet, a computer, an in-vehicle device, and the like.

[0072] Each embodiment in this specification is described in a step-by-step manner, and the emphasis is placed on describing the differences between each embodiment and other embodiments, and similar or similar parts between the embodiments are cross-referenced.

[0073] The apparatus and method disclosed in some embodiments of the present application may also be implemented in other ways. The apparatus embodiments described above are merely illustrative. For example, the flowcharts and block diagrams in the drawings illustrate possible architectures, functions, and operations based on the apparatus, method, and computer program products according to some embodiments of the present application. Each block in the flowchart or block diagram may represent a module, program segment, or part of code, including one or more executable instructions that can implement a specific logical function. In alternative implementations, the functions described in the blocks may be implemented in a different order than shown in the drawings. For example, two consecutive blocks may actually be executed substantially in parallel, or may even be executed in the reverse order, depending on the required functionality. Each block in the block diagram and / or flowchart, and a combination of blocks in the block diagram and / or flowchart, may be implemented by a dedicated hardware-based system that performs a specific function or operation, or by a combination of dedicated hardware and computer instructions.

[0074] Furthermore, each functional module in each embodiment of the present application may be integrated to form a single independent part, each module may exist independently, or two or more modules may be integrated to form a single independent part.

[0075] The above are only specific embodiments of the present application, and the scope of protection of the present application is not limited thereto. Any modifications or substitutions made by those skilled in the art within the technical scope disclosed in the present application will fall within the scope of protection of the present application. Therefore, the scope of protection of the present application is subject to the scope of the claims.

Claims

1. N memory spaces and N business plug-ins, where N is an integer equal to or greater than 2; Each of the business plug-ins corresponds to one independent memory space, and each of the business plug-ins is configured to receive business data to be processed, store the business data to be processed in the corresponding memory space, copy the business data to be processed, and process the copied business data to be processed. A plug-in type workflow management system characterized by:

2. Each of the business plug-ins is further configured to, in response to a re-execution command, re-process the pre-stored business data to be processed and transmit the re-processed business data.

2. The plug-in type workflow management system according to claim 1.

3. the plug-in type workflow management system further includes a workflow management component, the workflow management component being connected to each of the business plug-ins; The workflow management component is configured to, when business data needs to be re-executed by a lower-level business plug-in, determine a target business plug-in for re-executing the business, and send a re-execution command to the target business plug-in.

3. The plug-in type workflow management system according to claim 2.

4. the plug-in type workflow management system further includes a shared memory space, the shared memory space being configured to store business data shared by a plurality of business plug-ins; The independent memory space of each of the business plug-ins is configured to store business data specific to each of the business plug-ins.

2. The plug-in type workflow management system according to claim 1.

5. Each business plug-in has a sleep state and a work state, and power consumption in the sleep state is less than power consumption in the work state.

2. The plug-in type workflow management system according to claim 1.

6. Each business plug-in is further configured to delete the business data to be processed stored therein in response to a deletion command.

2. The plug-in type workflow management system according to claim 1.

7. Each of the business plug-ins is a single plug-in or a combination plug-in, and the combination plug-in includes a plurality of single plug-ins.

7. The plug-in type workflow management system according to claim 1, wherein the workflow management system is a system for managing a workflow of a computer.

8. N business plug-ins and a workflow management component, each of the business plug-ins is configured to store the received business data to be processed in a corresponding memory space, copy the business data to be processed, and process the copied business data to be processed, where N is an integer equal to or greater than 2; the workflow management component is connected to each of the business plug-ins, and when business data needs to be re-executed in a lower-level business plug-in, the workflow management component is configured to determine a target business plug-in that will re-execute the business data, and send a re-execution command to the target business plug-in; The target business plug-in is configured to, in response to the re-execution command, re-process the pre-stored target business data and transmit the re-processed business data. A plug-in type workflow management system characterized by:

9. The workflow management system according to any one of claims 1 to 7 or claim 8 is provided. An electronic device characterized by:

10. When the business data needs to be re-executed by a lower-level business plug-in, a workflow management component determines a target business plug-in that will re-execute the business data, and sends a re-execution command to the target business plug-in; a step in which the target business plug-in responds to the re-execution command, re-processes the input business data that has been backed up in advance, and transmits the re-processed business data; and when all the business plug-ins subsequent to the target business plug-in receive the processing target business data from the business plug-in one level above, storing the processing target business data in the corresponding memory space, copying the processing target business data, and processing the copied processing target business data. A business workflow management method comprising:

Images