Plug-in workflow management systems, electronic devices, and business workflow management methods

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] This 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 Art

[0002] The plug-in type workflow management system has the advantages that business projects can be arranged and established easily, so it is widely used in business approval workflows, software development workflows, etc. The plug-in type workflow management system includes one workflow management component and a series of parameterized business plugins. The workflow management component provides functions such as querying all business plugins, establishing and arranging business projects by configuring and arranging business plugins, executing and scheduling business plugins.

[0003] When the current plug-in type workflow management system executes a business, the upper-level plugin processes the received data and sends it to the lower-level plugin, and the lower-level plugin processes the received data and sends it to a further lower-level plugin. If an error occurs in a certain plugin, the entire business workflow has to be executed from the beginning again.

Summary of the Invention

Problems to be Solved by the Invention

[0004] In view of this, an object of this application is to provide a plug-in type workflow management system, an electronic device, and a business workflow management method that can improve the problem in the conventional plug-in type workflow management system that when an error occurs in a certain plugin, the entire business workflow has to be executed from the beginning again, which takes a lot of time.

Means for Solving the Problems

[0005] The embodiment of this application is realized as follows.

[0006] In the first phase, an embodiment of the present application provides a plug-in type workflow management system. The plug-in type workflow management system includes N memory spaces and N business plugins, where N is an integer of 2 or more, and each business plugin corresponds to one independent memory space, and each business plugin 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 this application, each business plugin corresponds to a separate memory space, and each business plugin stores the received business data to be processed in its corresponding memory space. In this way, when an error occurs in a business plugin, instead of restarting the entire workflow from the beginning, the data in the memory space can be read directly by the business plugin that caused the error and the workflow can be re-executed. This significantly improves processing efficiency.

[0008] In one implementable embodiment of the first phase of the embodiment, each business plugin is further configured to respond to a re-execution command, reprocess the previously stored business data to be processed, and transmit the reprocessed business data.

[0009] In the embodiment of this application, each business plugin responds to a re-execution command by reprocessing the pre-stored business data to be processed and transmitting the reprocessed business data. In this way, when an error occurs in a business plugin, instead of restarting the entire workflow from the beginning, the data in the memory space can be read directly by the business plugin that caused the error and re-executed, thereby significantly improving processing efficiency.

[0010] In one implementable embodiment of the first phase embodiment, the plug-in workflow management system further includes a workflow management component, the workflow management component is connected to each of the business plugins, and the workflow management component is configured to determine which business plugin to re-execute the business when business data needs to be re-executed by a subordinate business plugin, and to send a re-execution command to the target business plugin.

[0011] In the embodiment of this application, by sending a re-execution command to the target business plugin that re-executes the business using the workflow management component, the target business plugin is instructed to re-process the previously stored target business data, eliminating the need to restart the entire workflow from the beginning, thereby significantly improving processing efficiency.

[0012] In one implementable embodiment of the first phase embodiment, the plug-in workflow management system further includes a shared memory space configured to store shared business data of a plurality of business plugins, and each of the business plugins has its own independent memory space configured to store business data specific to that business plugin.

[0013] In the embodiment of this application, by using a shared memory space to store shared business data for multiple business plugins, the number of times the same data is transmitted can be reduced, thereby improving execution efficiency.

[0014] In one implementable embodiment of the first phase embodiment, each business plugin has a sleep state and a work state, wherein the power consumption in the sleep state is less than the power consumption in the work state.

[0015] In the embodiment of this application, each business plugin includes a sleep state and a work state, and in this way, business plugins can be arranged to be in different states. For example, each business plugin is in a "sleep" state after the execution of all workflows is complete, thereby saving power consumption.

[0016] In one implementable embodiment of the first phase of the embodiment, each business plugin is further configured to delete the business data it stores in response to a delete command.

[0017] In the embodiment of this application, in order to save on data storage costs, a business workflow for cleaning data is automatically started after the entire workflow has been completed, thereby allowing each business plugin to delete its own stored data.

[0018] In one implementable embodiment of the first phase embodiment, each of the business plugins is a single plugin or a combination plugin, and the combination plugin includes a plurality of single plugins.

[0019] In the embodiments of this application, multiple single plugins can be combined and used as a single combination plugin. By combining a series of complex workflows into one combination plugin, the maintenance of the system structure and business workflows can be simplified, and the difficulty of use can be reduced.

[0020] In the second aspect, embodiments of the present application further provide a plug-in type workflow management system. The plug-in type workflow management system includes N business plugins and a workflow management component, each of which is 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, where N is an integer of 2 or more, and the workflow management component is connected to each of the business plugins, and the workflow management component is configured to determine which business plugin to re-execute the business data when it is necessary to re-execute the business data in a lower-level business plugin, and to send a re-execution command to the target business plugin, and the target business plugin is configured to respond to the re-execution command, reprocess the previously stored business data to be processed, and send the reprocessed business data.

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

[0022] In the fourth aspect, embodiments of the present application further provide a business workflow management method. The business workflow management method includes the steps of: when business data needs to be reexecuted by a lower-level business plugin, the workflow management component determines the target business plugin to reexecute the business data and sends a reexecution command to the target business plugin; the target business plugin responds to the reexecution command, reprocesses the previously backed-up input business data, and sends the reprocessed business data; and when all business plugins after the target business plugin receive the business data to be processed from their higher-level business plugin, they store the 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.

[0023] In one possible embodiment of the example of the fourth situation, the method includes obtaining, by the workflow management component, the position of the target service plugin in all service workflows, obtaining, by the workflow management component, all service plugins after the target service plugin, and further includes sending, by the workflow management component, a save instruction to all service plugins after the target service plugin, where the save instruction is for instructing the service plugin to store the received service data to be processed in the corresponding memory space.

[0024] Other features and advantages of this application will be described in the following part. The objectives and other advantages of this application can be realized and obtained by the structure specifically shown in the specification and drawings.

Brief Description of the Drawings

[0025] To more clearly explain the examples of this application or the technical solutions of the prior art, the drawings used in the examples will be briefly described below. The drawings to be described only show some examples of this application. A person skilled in the art can obtain other drawings based on these drawings without using inventive capabilities. The above objectives, other objectives, features, and advantages of this application will become clearer from the drawings. [Figure 1] It is a schematic diagram showing the principle of the plugin-based workflow management system according to an example of this application. [Figure 2] It is a schematic structural diagram of the combination of plugins according to an example of this application. [Figure 3] It is a schematic diagram equivalent to Figure 1. [Figure 4] It is a schematic diagram showing the principle of another plugin-based workflow management system according to an example of this application. [Figure 5] It is a schematic flowchart of the service workflow management method according to an example of this application. [Figure 6] It is a schematic structural diagram of an electronic device according to an example of this application. [Modes for carrying out the invention]

[0026] The technical concept of the embodiments of this application will be described below with reference to the drawings used in the embodiments of this application. The embodiments described are only a selection of embodiments of this application, not all embodiments. The embodiments described below are merely illustrative examples to more clearly illustrate the technical concept of this application and do not limit the scope of protection of this application. As will be apparent to those skilled in the art, the embodiments and features described below can be combined with each other, insofar as they do not contradict each other.

[0027] The terms “have,” “include,” and any variations thereof are intended to encompass non-exclusive inclusion. Thus, a process, method, article, or apparatus that includes a set of elements is not limited to these elements and may include other elements not specified or specific to these processes, methods, articles, or apparatus. Unless otherwise specified, the expression “includes” does not exclude situations where a process, method, article, or apparatus that includes such elements also has other similar elements.

[0028] The term "and / or" in this application represents a relationship between related objects, indicating that three types of relationships exist. For example, A and / or B represents three types of relationships: A exists alone, both A and B exist, and B exists alone.

[0029] Current plug-in workflow management systems are time-consuming because, if an error occurs in one business plugin, the entire workflow must be restarted from the beginning. It would be desirable to save workflow time and allow each business plugin to be run repeatedly, so that when an error occurs in a business plugin, the system corrects the error and continues execution from the current business plugin, rather than restarting from the beginning.

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

[0031] To better understand the invention, the plug-in workflow management system according to an embodiment of this application will be described below with reference to Figure 1. The plug-in workflow management system includes N memory spaces and N business plugins, where N is an integer of 2 or greater. The value of N is determined by the complexity of the business project, and the more complex the business project to be processed, the more business plugins are required. For example, the configuration of the plug-in workflow management system when used in a business approval workflow is different from the configuration when used in a development workflow.

[0032] If a plug-in type workflow management system is considered as a single application (for example, a business approval application and a software development application), then business plugins can be viewed as functional modules that make up the entire application. As the design functions of the application increase, the number of corresponding business plugins also increases. When adding a business function, a business plugin is added, and a collaborative relationship is established between the added business plugin and the existing business plugins, 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 is divided into N parts, with each business plugin corresponding to one independent memory space.

[0033] These N business plugins work together to realize a specific business project. These N business plugins are connected in series, or in a manner that includes both series and parallel connections, depending on the needs of the business project, to realize the processing of the specific business project. For example, business plugins 1, 2, 3, 4, and 5 shown in Figure 1 are all business plugins, business plugin 1, business plugin 4, and business plugin 5 are connected in series, business plugin 1, business plugin 2, business plugin 3, and business plugin 5 are connected in series, and business plugin 4, business plugin 2, and business plugin 3 are connected in parallel.

[0034] In conventional workflows, business plugins 2, 3, and 4 cannot be executed in parallel. When parallel processing is required, it is generally necessary to create two different tasks. In a parallel business workflow, however, they can be executed in parallel as different business plugins for the same task, saving workflow time.

[0035] Business plugins transmit data to other business plugins using either parallel or serial connection methods, and then read and execute the data sequentially. In the case of serial execution, the higher-level plugin stores the data in its own memory space, copies the data, processes the copied data, and provides the processed data to the lower-level plugin. The lower-level plugin, after receiving the data from the higher-level plugin, stores it in its own memory space, copies the data, processes the copied data, and transmits the newly obtained processed data to an even lower-level plugin.

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

[0037] Each business plugin can be a single plugin or a combination plugin, with a combination plugin containing multiple single plugins. For example, in one embodiment, business plugins 2, 3, and 4 in Figure 1 are combined to form a new combination plugin, which may also be called a template plugin, and its principle diagram is shown in Figure 2. Business projects in a plugin-type workflow management system are arranged to support template plugins. Such plugins are not a single specific business plugin, but rather new plugins constructed by combining other business plugins. Business projects can directly use such template plugins as a single business plugin. In this way, by combining a series of complex workflows into a single template plugin, the maintenance of business workflows can be simplified and the difficulty of use can be reduced.

[0038] In one selectable embodiment, the plug-in workflow management system shown in Figure 1 can be simplified to the plug-in workflow management system shown in Figure 3. The combination plugin 2 shown in Figure 3 includes business plugin 2, business plugin 3, and business plugin 4 in Figure 1. Regardless of whether the business plugins are single plugins or combination plugins, each business plugin corresponds to one memory space, for example, the combination plugin in Figure 3 corresponds to memory space 2'.

[0039] Each business plugin is divided into a parent plugin or a child plugin based on its position in the business project workflow. Child plugins are configured to process business data (i.e., the business data to be processed) from the parent plugin to which they are connected. Multiple child plugins may be connected in series below a business plugin, and these child plugins will run in parallel, each processing its own business data. Sub-businesses may be further connected in series within each parallel business, so that they converge into a single business plugin that supports multiple inputs.

[0040] Each business plugin corresponds to a separate, independently stored memory space, allowing each plugin to save its own input data. Each business plugin is configured to receive the business data to be processed, store the business data in its corresponding memory space, copy the received business data, process the copied business data, and transmit the processed data.

[0041] Depending on the business plugin, the processing method used when processing received business data may differ, and the supported processing method may also differ depending on the application scenario. For example, the processing method may include, but is not limited to, data calculation, data transfer, format conversion, and data filtering.

[0042] Each business plugin has its own corresponding memory space, allowing it to support processing of multiple types of data streams. Even if it is not possible to process data streams simultaneously, the data is first stored in the memory space, and when processing becomes possible, the business data is copied from the memory space and processed.

[0043] The plug-in workflow management system according to the embodiment of this application has a corresponding memory space for each business plugin. Therefore, when processing a data stream, the business data to be processed is stored in the corresponding memory space, enabling parallel processing. Furthermore, since each business plugin can save its own input data, if an error occurs in a business plugin, instead of restarting the entire workflow from the beginning, the error is corrected in the current business plugin and execution continues, thereby significantly improving processing efficiency.

[0044] Each business plugin copies the higher-level business data and processes based on that copied data. Therefore, if the original higher-level data remains unchanged, and if a business workflow needs to be re-executed, it is not necessary to start the execution from the beginning. Instead, the problematic business plugin can be reconfigured, and execution can be resumed with that plugin.

[0045] In one selectable embodiment, each business plugin is further configured to respond to a re-execution command by reprocessing the previously stored business data to be processed and sending the reprocessed business data. In this way, when an error occurs in a business plugin, instead of restarting execution from the beginning, the error is corrected and execution continues from the current business plugin.

[0046] In one selectable embodiment, the plug-in workflow management system further includes a workflow management component, which is connected to each of the business plugins. The workflow management component is configured to determine which business plugin to re-execute the business when business data needs to be re-executed by a subordinate business plugin, and to send a re-execution command to the target business plugin. The target business plugin then responds to the re-execution command by re-processing the previously stored business data to be processed and sending the re-processed business data.

[0047] Subordinate business plugins are distinguished based on their position within the plug-in workflow management system of the business plugin; any business plugin that is not located at the beginning (or end) can be called a subordinate business plugin. For example, in Figure 1, business plugins 2, 3, 4, and 5 are subordinate business plugins to business plugin 1. Any one of the above business plugins can function as a business plugin that re-executes business data if an error occurs in its operation.

[0048] The workflow management component establishes and deploys business projects by configuring and deploying business plugins, executes and schedules functions such as business plugins, and instructs each business plugin to cooperate in completing the business project by sending its respective configuration commands to each business plugin.

[0049] In one selectable embodiment, it is also possible to configure whether each business plugin saves input data. If a business plugin does not save input data, its subordinate plugins will not be able to retrieve similar input data and therefore cannot be used as a starting plugin for re-execution. If re-execution of a task is necessary, execution can only be started from a business plugin prior to such a business plugin. Whether each business plugin saves input data can be configured by sending a command via the workflow management component.

[0050] In one optional embodiment, to save on data storage costs, a business workflow may be automatically initiated to clean the data after the entire workflow has been completed, causing each business plugin to delete its stored data. In this embodiment, each business plugin is further configured to respond to a delete command and delete the processed business data stored within itself. A delete command is sent by the workflow management component, and after the entire workflow has been completed, the workflow management component sends a delete command to each business plugin, and each business plugin responds to the delete command and deletes the processed business data stored within itself.

[0051] In one selectable embodiment, each business plugin has its own unique attributes, such as sleep state and work state. Power consumption in sleep state is less than power consumption in work state. Business plugins with such attributes enter a "sleep" state after the execution of all workflows is complete, and after the user has prepared new placement data, the business plugin is triggered again to return it from sleep state to work state and continue execution. Business plugins can be placed into different states by sending commands via the workflow management component.

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

[0053] Based on a similar inventive concept, embodiments of this application further provide a plug-in workflow management system. As shown in Figure 4, the plug-in workflow management system includes N business plug-ins and workflow management components, where N is an integer of 2 or more.

[0054] The specified business project is accomplished through the collaboration of N business plugins. Each business plugin is configured to store the received business data to be processed in its corresponding memory space, copy the business data, and process the copied business data.

[0055] The workflow management component is connected to each business plugin. The workflow management component is configured to determine which business plugin should re-execute the business data if it needs to be re-executed by a subordinate business plugin, and to send a re-execution command to that business plugin. The target business plugin is configured to respond to the re-execution command by re-processing the business data that it has previously stored and sending the re-processed business data.

[0056] The implementation principle and technical effects of the above-described plug-in workflow management system (Figure 4) are the same as those of the plug-in workflow management system embodiment shown in Figure 1. For the sake of simplicity, any content not mentioned in this embodiment can be referenced to the corresponding content in the above-described plug-in workflow management system embodiment.

[0057] Based on a similar inventive concept, the embodiments of this application further provide a business workflow management method. The business workflow management method will be described below with reference to Figure 5. The business workflow management method shown in Figure 5 can be used in the above-described plug-in type workflow management system.

[0058] S1: If business data needs to be re-executed by a subordinate business plugin, the workflow management component determines which business plugin should re-execute the business data and sends a re-execution command to the target business plugin.

[0059] When an error occurs in the operation of a business plugin, and the business data needs to be re-executed by a subordinate business plugin, the workflow management component determines which business plugin should re-execute the business data and sends a re-execution command to that business plugin.

[0060] S2: The target business plugin responds to the re-execution command, reprocesses the previously backed-up input business data, and transmits the reprocessed business data.

[0061] Each business plugin stores the input business data in its corresponding memory space. When it receives a re-execution command later, it reprocesses the previously backed-up input business data and sends the reprocessed business data.

[0062] S3: When all business plugins following the aforementioned target business plugin receive the target business data from the business plugin one level higher, they store the target business data in the corresponding memory space, copy the target business data, and process the copied target business data.

[0063] Each business plugin is configured to receive the target business data, store the target business data in its corresponding memory space, copy the target business data, and process the copied target business data. In this way, after the target business plugin of a lower-level business plugin re-executes the business data, all business plugins after the target business plugin receive the target business data from the business plugin one level higher, store the target business data in its corresponding memory space, copy the target business data, and process the copied target business data.

[0064] Optionally, the method further includes obtaining the position of the target business plugin in the entire business workflow using a workflow management component, obtaining all business plugins after the target business plugin using a workflow management component, and sending save commands to all business plugins after the target business plugin using a workflow management component. The save command instructs the business plugin to store the received target business data in the corresponding memory space. In this embodiment, it is configurable whether each business plugin saves the received input data, and the configuration method is relatively simple, requiring the sending of a corresponding configuration command. For example, sending a save command instructs the business plugin to save the received input data.

[0065] Optionally, the method further includes the workflow management component sending a delete command to each business plugin after the entire workflow has been completed, and each business plugin responding to the delete command by deleting the processed business data stored within itself.

[0066] The implementation principle and technical effects of the business workflow management method according to the embodiment of this application are the same as those of the above-mentioned plug-in type workflow management system embodiment. For the sake of simplicity, for matters not mentioned in the embodiment of the method, the corresponding matters in the above-mentioned plug-in type workflow management system embodiment can be referenced.

[0067] Embodiments of this application further provide an electronic device comprising the plug-in workflow management system described above. Optionally, as shown in Figure 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 workflow management system are arranged on the processor 240. The memory space in the plug-in workflow management system is provided by the storage device 220. The storage device 220 is divided into N memory spaces, each corresponding one-to-one with 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 enable data transmission or exchange. For example, these elements are electrically connected by one or more communication buses 230 or signal lines. The transceiver 210 is for sending and receiving data. The storage device 220 is configured to store computer programs, for example, the storage device 220 stores computer programs necessary for executing the above-described business workflow management method. The computer program includes at least one software function module stored in the storage device 220 in the form of software or firmware, or written to the operating system (OS) of the electronic device 200. The processor 240 is configured to execute the above-described business workflow management method by executing executable modules stored in the storage device 220.

[0069] The storage 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), or an electrically erasable programmable read-only memory (EEPROM).

[0070] The processor 240 may be an integrated circuit chip having signal processing capabilities. The processor described above is capable of realizing or executing each method, step, and logic block according to the embodiments of this application, such as a general-purpose processor including a Central Processing Unit (CPU), Network Processor (NP), microprocessor, Digital Signal Processor (DSP), Application Specific Integrated Circuit (ASIC), Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, etc. Alternatively, the processor 240 may be any conventional processor, etc.

[0071] The above-mentioned electronic devices 200 include, but are not limited to, tablets, computers, and in-vehicle devices.

[0072] Each example in this specification is described progressively, with emphasis on describing the differences between each example and the similarities between them, which can be discussed by cross-referencing.

[0073] Apparatus and methods disclosed in some embodiments of this application can also be implemented in other ways. The embodiments of the apparatus described above are illustrative only, and for example, flowcharts and block diagrams in the drawings illustrate implementable architectures, functions and operations based on some embodiments of the apparatus, methods and computer program products of this application, where each block in the flowchart or block diagram can represent a module, program segment or part of code containing one or more executable instructions capable of implementing a predetermined logical function. In an interchangeable implementation, the implementation of the functions described in the blocks may differ from the order shown in the drawings. For example, two consecutive blocks may actually be executed almost in parallel, or in some cases in reverse order. This is determined by the required functions. Each block in the block diagram and / or flowchart, and combinations of blocks in the block diagram and / or flowchart, may be implemented by a dedicated, hardware-based system that performs a predetermined function or operation, or by a combination of dedicated hardware and computer instructions.

[0074] Furthermore, each functional module in each embodiment of this application may be formed by integrating them into a single independent part, each module may exist independently, or it may be formed by integrating two or more modules into a single independent part.

[0075] The above are merely specific embodiments of the present application, and the scope of protection of this application is not limited to these. A person skilled in the art will know that any modification or substitution made within the scope of the art disclosed in this application falls within the scope of protection of this application. Therefore, the scope of protection of this application is equivalent to the claims.

Claims

1. It includes N memory spaces and N business plugins, where N is an integer greater than or equal to 2. Each of the aforementioned business plugins corresponds to a single independent memory space, and each of the aforementioned business plugins 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. Each of the aforementioned business plugins is further configured to respond to a re-execution command by reprocessing the previously stored business data to be processed and transmitting the reprocessed business data. A plug-in type workflow management system characterized by the following features.

2. The aforementioned plug-in type workflow management system further includes a workflow management component, the workflow management component being connected to each of the business plugins, The workflow management component is configured to determine which business plugin to re-execute the business when business data needs to be re-executed by a subordinate business plugin, and to send a re-execution command to the target business plugin. The plug-in type workflow management system according to feature 1.

3. The aforementioned plug-in type workflow management system further includes a shared memory space, which is configured to store shared business data of multiple business plug-ins. Each of the aforementioned business plugins has its own independent memory space, which is configured to store the specific business data of that business plugin. The plug-in type workflow management system according to feature 1.

4. Each business plugin has a sleep state and a working state, and the power consumption in the sleep state is less than the power consumption in the working state. The plug-in type workflow management system according to feature 1.

5. Each business plugin is further configured to respond to a delete command by deleting the business data it has stored within itself. The plug-in type workflow management system according to feature 1.

6. Each of the aforementioned business plugins is either a single plugin or a combination plugin, and the combination plugin includes multiple single plugins. A plug-in type workflow management system according to any one of claims 1 to 5.

7. It includes N business plugins and workflow management components, Each of the aforementioned business plugins 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, wherein N is an integer of 2 or more. The workflow management component is connected to each of the business plugins, and the workflow management component is configured to determine which business plugin to re-execute the business data in when it is necessary to re-execute the business data in a subordinate business plugin, and to send a re-execution command to the target business plugin. The aforementioned target business plugin is configured to respond to the re-execution command by reprocessing the previously stored target business data and transmitting the reprocessed business data. A plug-in type workflow management system characterized by the following features.

8. A workflow management system according to any one of claims 1 to 5, or a workflow management system according to claim 7. An electronic device characterized by the following features.

9. A method for managing business workflows performed by electronic devices, If business data needs to be re-executed by a subordinate business plugin, the workflow management component determines the business plugin to which the business data should be re-executed and sends a re-execution command to the said business plugin. The aforementioned target business plugin responds to the re-execution command, reprocesses the previously backed-up input business data, and transmits the reprocessed business data; The process includes the steps of: when all business plugins following the aforementioned target business plugin receive processing target business data from the business plugin one level higher, 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 characterized by the following features.

Images