Task planning execution method, device, equipment and medium based on process engine

Abstract

The present invention discloses a task planning and execution method, device, equipment and medium based on a process engine. The method includes: creating a process model, setting metadata of the process model, and making a flowchart according to the metadata of the process model, wherein the flowchart includes multiple process nodes; deploying the flowchart to the process engine to obtain executable process definition data; creating task execution, setting metadata of task execution, and binding the executable process definition data with the metadata of task execution; setting business data of each process node according to the executable process definition data, starting task execution according to the business data of the process node, running the metadata of task execution, and generating multiple to-do items according to the metadata information of the process model. The present application can more accurately control the task execution and the file data generated in the process, and the task execution can generate to-do items, which expands the business scenario, thereby timely tracking the progress of task execution.

Description

Technical Field

[0001] The present invention relates to the field of data processing technology, and in particular to a task planning and execution method, device, equipment and medium based on a process engine. Background Art

[0002] Most task tools on the market are task execution tools, focusing on process approvals. They are primarily used for approval-based tasks such as multi-task collaboration, progress control, and single-task execution, rather than focusing on the subtasks and task material aggregation within each task link. However, our customer base has a large number of process-based tasks, and each task link generates multiple to-do items and requires archiving of task materials.

[0003] In the existing technology, process task management is usually achieved through automated office work using a workflow engine. However, this method has high operational complexity and professional threshold, process design has limitations, process changes and management have certain difficulties, and there are deficiencies in the integration of process and task results. Summary of the Invention

[0004] In view of this, the purpose of the present invention is to overcome the deficiencies in the prior art and provide a task planning and execution method, device, equipment and medium based on a process engine.

[0005] The present invention provides the following technical solutions:

[0006] In a first aspect, an embodiment of the present disclosure provides a task planning and execution method based on a process engine, the method comprising:

[0007] Creating a process model, setting metadata of the process model, and making a flow chart based on the metadata of the process model, wherein the flow chart includes a plurality of process nodes;

[0008] Deploy the flowchart to a process engine to obtain executable process definition data;

[0009] Creating a task execution, setting metadata for the task execution, and binding the executable process definition data to the metadata for the task execution;

[0010] The business data of each process node is set according to the executable process definition data, the task execution is started according to the business data of the process node, the metadata of the task execution is run, and a plurality of to-do items are generated according to the metadata information of the process model.

[0011] Optionally, the metadata of the process model includes process name, process classification, reference knowledge, work documents, work content and process type. The flowchart also includes node executors, node template files, routing gateways and listeners. The process nodes include starting nodes, multiple task nodes and end nodes. The types of process nodes include multiple people handling multiple tasks and one person handling a single task.

[0012] Optionally, deploying the flowchart into a process engine to obtain executable process definition data includes:

[0013] Obtaining the BPMN file generated when making the flowchart through the front-end component;

[0014] The BPMN file is deployed to the process engine through the API interface to generate a process template, and corresponding executable process definition data is generated according to the process template.

[0015] Optionally, the metadata of the task execution includes task name, task type, task time, task description, task priority, task classification and participants, and the business data includes handling method, node executor, node co-organizer, work content, work template and reference knowledge.

[0016] Optionally, starting the task execution according to the business data includes:

[0017] Dynamically generate business data for each process node according to the requirements of task execution;

[0018] The business data of each process node is associated with the corresponding flow chart to start the task execution.

[0019] Optionally, generating a plurality of to-do items according to the metadata information of the process model includes:

[0020] generating a plurality of to-do items according to the work document;

[0021] A task reference file is generated according to the executable process definition data, the metadata of the task execution and the business data of each process node.

[0022] Optionally, generating a plurality of to-do items according to the metadata information of the process model further includes:

[0023] Each of the to-do items is completed through each of the process nodes, and when each of the process nodes is completed, a file flow operation of the process node is performed according to the completion status of the corresponding to-do item;

[0024] Monitor the process definition data during the task execution, wherein the process definition data includes task node status, document quantity, execution process and execution time.

[0025] In a second aspect, an embodiment of the present disclosure provides a task planning and execution device based on a process engine, the device comprising:

[0026] A creation module, configured to create a process model, set metadata of the process model, and create a flow chart based on the metadata of the process model, wherein the flow chart includes a plurality of process nodes;

[0027] A deployment module, used to deploy the flowchart into a process engine to obtain executable process definition data;

[0028] a binding module for creating a task execution, setting metadata for the task execution, and binding the executable process definition data with the metadata for the task execution;

[0029] An operation module is used to set the business data of each process node according to the executable process definition data, start the task execution according to the business data of the process node, run the metadata of the task execution, and generate multiple to-do items according to the metadata information of the process model.

[0030] In a third aspect, an embodiment of the present disclosure provides a computer device, which includes a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, it implements the steps of the task planning and execution method based on the process engine described in the first aspect.

[0031] In a fourth aspect, an embodiment of the present disclosure provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the task planning and execution method based on the process engine described in the first aspect are implemented.

[0032] Beneficial effects of this application:

[0033] The embodiment of the present application provides a task planning and execution method based on a process engine. By creating a process model, setting the metadata of the process model, and making a flowchart according to the metadata of the process model, wherein the flowchart includes multiple process nodes; deploying the flowchart to the process engine to obtain executable process definition data; creating a task execution, setting the metadata of the task execution, and binding the executable process definition data with the metadata of the task execution; setting the business data of each process node according to the executable process definition data, starting the task execution according to the business data of the process node, running the metadata of the task execution, and generating multiple to-do items according to the metadata information of the process model. The present application can more accurately control the task execution and the file data generated in the process, and the task execution can generate to-do items, which expands the business scenario, thereby timely tracking the progress of task execution.

[0034] In order to make the above-mentioned objects, features and advantages of the present invention more obvious and easy to understand, preferred embodiments are given below and described in detail with reference to the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] To more clearly illustrate the technical solutions of the embodiments of the present invention, the following briefly introduces the drawings required for use in the embodiments. It should be understood that the following drawings only illustrate certain embodiments of the present invention and should not be considered as limiting the scope. A person of ordinary skill in the art can also derive other relevant drawings based on these drawings without inventive effort. Similar components are numbered similarly in the various drawings.

[0036] Figure 1 A flowchart of a task planning and execution method based on a process engine provided in an embodiment of the present application is shown;

[0037] Figure 2 A flowchart of another task planning and execution method based on a process engine provided in an embodiment of the present application is shown;

[0038] Figure 3 A schematic diagram of the structure of a task planning and execution device based on a process engine provided in an embodiment of the present application is shown;

[0039] Figure 4 A structural diagram of a computer device provided in an embodiment of the present application is shown. DETAILED DESCRIPTION

[0040] The following describes embodiments of the present invention in detail. Examples of the embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar elements or elements having the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are intended only to explain the present invention and are not to be construed as limiting the present invention.

[0041] It should be noted that when an element is referred to as being "fixed to" another element, it may be directly on the other element or there may be an intermediate element. When an element is considered to be "connected to" another element, it may be directly connected to the other element or there may be an intermediate element. Conversely, when an element is referred to as being "directly on" another element, there is no intermediate element. The terms "vertical," "horizontal," "left," "right," and similar expressions used herein are for illustrative purposes only.

[0042] In the present invention, unless otherwise expressly specified or limited, the terms "mounted," "connected," "connect," "fixed," etc. should be understood broadly. For example, they may refer to fixed connection, detachable connection, or integration; mechanical connection or electrical connection; direct connection or indirect connection through an intermediate medium; internal communication between two components or interaction between two components. Those skilled in the art will understand the specific meanings of the above terms in the present invention based on specific circumstances.

[0043] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of the technical features being referred to. Thus, a feature identified as "first" or "second" may explicitly or implicitly include one or more of the features. In the description of the present invention, "plurality" means two or more, unless otherwise specifically defined.

[0044] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by those skilled in the art to which this application belongs. The terms used in the template description herein are for the purpose of describing specific embodiments only and are not intended to limit the present invention. The term "and / or" as used herein includes any and all combinations of one or more of the associated listed items.

[0045] Example 1

[0046] like Figure 1 FIG. 1 is a flowchart of a task planning and execution method based on a process engine in an embodiment of the present application. The task planning and execution method based on a process engine provided in an embodiment of the present application includes the following steps:

[0047] Step S110 , creating a process model, setting metadata of the process model, and making a flow chart according to the metadata of the process model, wherein the flow chart includes a plurality of process nodes.

[0048] In this embodiment, a new process model is first created and the metadata of the process model is set. The metadata of the process model is mainly used to record the basic information of the process model, including process name, process classification, reference knowledge, work documents, work content and process type.

[0049] Next, a flowchart corresponding to the metadata of the process model is drawn using a graphical process design tool. The flowchart includes multiple process nodes, node executors, node template files, routing gateways, and listeners. The process nodes include a start node, multiple task nodes, and an end node. The start node is used to mark the starting point of a process. The task node is used to request the user's to-do items when the task reaches the process node during execution. After completion, the process continues to execute; the routing gateway is used to distribute the approval flow to different task nodes according to different conditions when the process reaches a task node; the listener is used to capture specific events (such as task creation, task assignment, task completion, process start, process end, path connection, etc.) at different stages of process execution and perform corresponding operations; the end node is used to mark the end of the current process when a process reaches this point.

[0050] In this embodiment, the types of process nodes are expanded, including multiple people handling multiple processes and one person handling a single process. One person handling a single process means that only one person can receive and handle the process node, and multiple people handling multiple processes means that when multiple people handle the process at the same time, all of them must complete the process before they can pass the process node.

[0051] It should be noted that the flowcharts of this embodiment include two types: task planning and process approval. Among them, the task planning type supports pre-setting executors on the flowchart, supports adjusting executors during task execution, and supports supplementing to-do items, so that the process is more flexible during execution and reduces the risk of human error; the process approval type must set executors on the flowchart, clarify the responsible persons of the process nodes, and does not support personnel changes, determine the scope of responsibility, or supplement to-do items during task execution, thereby reducing unnecessary changes and interference.

[0052] In an optional embodiment, the flowchart drawing process supports more components, such as pool lanes, shape components, data components, internal storage components, external components, etc., and can also use artificial intelligence models to automatically generate flowcharts. The specific drawing method is not limited in this embodiment.

[0053] This method, which departs from the native process engine designer, creates flowcharts by defining built-in key data and rules. This streamlines user operations, simplifies the process drawing process, and reduces user costs. Furthermore, by pre-setting executors on the flowchart and assigning responsible individuals to each task, work assignments and responsibilities are clarified. Furthermore, the possibility of personnel changes during task execution is supported, making task planning and execution more flexible, ensuring smooth task execution, and further facilitating subsequent task data monitoring.

[0054] Step S120: deploy the flowchart into a process engine to obtain executable process definition data.

[0055] Specifically, when drawing a flowchart, a corresponding BPMN (Business Process Model and Notation) file will be generated. After the BPMN file is obtained through the front-end component, the BPMN file is deployed to the process engine through the API (Application Programming Interface) interface to generate a process template (it is necessary to ensure that the BPMN file is compatible with the version of the process engine). The corresponding executable process definition data can be generated according to the process template.

[0056] Step S130 : creating a task execution, setting metadata of the task execution, and binding the executable process definition data with the metadata of the task execution.

[0057] Specifically, task execution is created and metadata of task execution is set. The metadata of task execution includes information such as task name, task type, task time, task description, task priority, task classification and participants, and the above metadata of task execution is bound to executable process definition data.

[0058] This method allows changes to task execution metadata without disrupting the established workflow. Whether modifying task content, adjusting participants, or changing task priorities, adjustments can be made at any time, and the system automatically adapts to these changes, maintaining process continuity and stability. This flexible design allows users to dynamically adjust task execution metadata based on actual needs, ensuring that workflow execution is more aligned with reality and improving overall efficiency and accuracy.

[0059] Step S140, setting the business data of each process node according to the executable process definition data, starting the task execution according to the business data of the process node, running the metadata of the task execution, and generating multiple to-do items according to the metadata information of the process model.

[0060] Furthermore, the executable process definition data is configured to bind the business data of each process node, wherein the business data includes information such as handling method, node executor, node co-organizer, work content, work template and reference knowledge.

[0061] As you can understand, during the task creation process, we support dynamic configuration of process node business data. This business data can be dynamically generated based on task execution requirements without affecting the original data in the process engine. Furthermore, we can associate the corresponding flowcharts and executors, so that task execution can be initiated based on business data and run according to business needs.

[0062] Furthermore, when task execution is initiated, the work documents in the process model's metadata information will generate to-do items one by one, and each to-do item will be categorized according to the different stages of task execution. To-do items are tasks that must be completed. Relevant task reference files are generated based on the executable process definition data, the metadata of task execution, and the business data of each process node. During the task execution process of this embodiment, different display panels can be switched to facilitate users to view all to-do items and related task reference files online, making it easier for users to understand information such as the background and requirements of the task.

[0063] During task execution, the above method generates corresponding to-do items in the work document. These to-do items include task assignments, approvals, and notifications. For each to-do item, relevant information such as task description, deadline, and executor can be recorded and associated with the corresponding task. The completion status of the to-do items can be updated through system records or feedback from the executor, allowing for timely tracking of task execution progress. This expands business scenarios, binds processes to tasks, and allows tasks to drive process execution, enabling more precise control of task execution results and the aggregation and unified management of task files at each stage.

[0064] In an alternative embodiment, Figure 2 As shown, after step S140, the following steps are further included:

[0065] Step S150, completing each of the to-do items through each of the process nodes. When each of the process nodes is completed, performing a file transfer operation of the process node according to the completion status of the corresponding to-do item;

[0066] Step S160 , monitoring the process definition data during the task execution, wherein the process definition data includes the task node status, the number of documents, the execution process, and the execution time.

[0067] Specifically, during task execution, each process node supports the completion of to-do items. Upon completion of a process node, file flow operations such as approval, copying, and forwarding can be performed based on the completion status of the corresponding to-do items. Furthermore, a dashboard displays task to-do items, task completion status, and task submissions at different stages, allowing users to identify issues and discrepancies during task execution. Users can then provide comments to alert task performers and correct them.

[0068] At the same time, it provides multiple perspectives to monitor process definition data during task execution, including task node status, document count, execution progress, and execution time. By viewing process definition data, users can view a list of all open, executing, and completed processes, view the execution progress of all processes, view the execution records of each process instance, generated files and to-do items, view the completion status of to-do items, and view the specific steps of the current process execution to promote the smooth development of business.

[0069] Understandably, the user can also review and aggregate task process data of completed tasks during task execution, and support third-party access. For example, it can be integrated with search engine file retrieval, and then quickly retrieve and access task-related files and data through search engines, thereby improving the efficiency and convenience of system information retrieval.

[0070] The data generated during the execution of these tasks can be categorized and managed according to their type and stage. By managing to-do items and data, we can achieve comprehensive monitoring of task execution, analyze the processing time of different to-do items, as well as the number of files generated and execution at each stage, thereby identifying problems and making timely adjustments and optimizations.

[0071] The embodiment of the present application provides a task planning and execution method based on a process engine. By creating a process model, setting the metadata of the process model, and making a flowchart according to the metadata of the process model, wherein the flowchart includes multiple process nodes; deploying the flowchart to the process engine to obtain executable process definition data; creating a task execution, setting the metadata of the task execution, and binding the executable process definition data with the metadata of the task execution; setting the business data of each process node according to the executable process definition data, starting the task execution according to the business data of the process node, running the metadata of the task execution, and generating multiple to-do items according to the metadata information of the process model. The present application can more accurately control the task execution and the file data generated in the process, and the task execution can generate to-do items, which expands the business scenario, thereby timely tracking the progress of task execution.

[0072] Example 2

[0073] like Figure 3 FIG. 1 is a schematic diagram of a task planning and execution device 300 based on a process engine in an embodiment of the present application, wherein the device includes:

[0074] A creation module 310 is configured to create a process model, set metadata of the process model, and create a flow chart based on the metadata of the process model, wherein the flow chart includes a plurality of process nodes;

[0075] A deployment module 320 is used to deploy the flowchart to a process engine to obtain executable process definition data;

[0076] A binding module 330 is used to create a task execution, set metadata for the task execution, and bind the executable process definition data with the metadata for the task execution;

[0077] The operation module 340 is used to set the business data of each process node according to the executable process definition data, start the task execution according to the business data of the process node, run the metadata of the task execution, and generate multiple to-do items according to the metadata information of the process model.

[0078] The process engine-based task planning and execution device provided in the embodiment of the present application can more accurately control the task execution and the file data generated in the process, and the task execution can generate to-do items, expanding the business scenarios, so as to timely track the progress of task execution.

[0079] Example 3

[0080] The present application also provides a computer device. Figure 4 , Figure 4 This is a basic structural block diagram of the computer device in this embodiment.

[0081] The computer device 4 includes a memory 41, a processor 42, and a network interface 43 that are interconnected through a system bus. It should be noted that the figure only shows a computer device 4 with a memory 41, a processor 42, and a network interface 43, but it should be understood that it is not required to implement all the components shown, and more or fewer components can be implemented instead. Among them, those skilled in the art can understand that the computer device here is a device that can automatically perform numerical calculations and / or information processing according to pre-set or stored instructions, and its hardware includes but is not limited to a microprocessor, an application specific integrated circuit (ASIC), a field-programmable gate array (FPGA), a digital signal processor (DSP), an embedded device, etc.

[0082] The computer device may be a desktop computer, notebook computer, PDA, cloud server, etc. The computer device may interact with the user via a keyboard, mouse, remote control, touchpad, or voice control device.

[0083] The memory 41 includes at least one type of readable storage medium, including flash memory, hard disk, multimedia card, card-type memory (e.g., SD or D slot compatibility test memory), random access memory (RAM), static random access memory (SRAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), programmable read-only memory (PROM), magnetic memory, magnetic disk, optical disk, etc. In some embodiments, the memory 41 can be an internal storage unit of the computer device 4, such as the hard disk or memory of the computer device 4. In other embodiments, the memory 41 can also be an external storage device of the computer device 4, such as a plug-in hard disk equipped on the computer device 4, a smart media card (SMC), a secure digital (SD) card, a flash card, etc. Of course, the memory 41 can also include both the internal storage unit of the computer device 4 and its external storage device. In this embodiment, the memory 41 is generally used to store the operating system and various application software installed on the computer device 4, such as computer-readable instructions for the slot compatibility test method. In addition, the memory 41 can also be used to temporarily store various types of data that have been output or are to be output.

[0084] In some embodiments, the processor 42 can be a central processing unit (CPU), a controller, a microcontroller, a microprocessor, or other process engine-based task planning and execution chip. The processor 42 is generally used to control the overall operation of the computer device 4. In this embodiment, the processor 42 is used to execute computer-readable instructions or process data stored in the memory 41, such as computer-readable instructions for executing the slot compatibility testing method.

[0085] The network interface 43 may include a wireless network interface or a wired network interface. The network interface 43 is generally used to establish a communication connection between the computer device 4 and other electronic devices.

[0086] The computer device provided in this embodiment can execute the above-mentioned task planning and execution method based on the process engine. Here, the task planning and execution method based on the process engine can be the task planning and execution method based on the process engine in each of the above-mentioned embodiments.

[0087] Example 4

[0088] This embodiment further provides a computer-readable storage medium having a computer program stored thereon. When the computer program is executed by a processor, the steps of the task planning and execution method based on the process engine in the embodiment are implemented.

[0089] In this embodiment, the computer-readable storage medium includes flash memory, hard disks, multimedia cards, card-type memories (e.g., SD or DX memories), random access memory (RAM), static random access memory (SRAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), programmable read-only memory (PROM), magnetic storage, magnetic disks, optical disks, etc. In some embodiments, the computer-readable storage medium may be an internal storage unit of a computer device, such as the hard disk or memory of the computer device. In other embodiments, the computer-readable storage medium may also be an external storage device of the computer device, such as a plug-in hard disk equipped with the computer device, a Smart Media Card (SMC), a Secure Digital (SD) card, a flash memory card, etc. Of course, the computer-readable storage medium may also include both the internal storage unit of the computer device and its external storage device. In this embodiment, the computer-readable storage medium is generally used to store the operating system and various application software installed on the computer device. In addition, the computer-readable storage medium may also be used to temporarily store various types of data that have been output or are about to be output.

[0090] In the several embodiments provided in this application, it should be understood that the disclosed devices and methods can also be implemented in other ways. The device embodiments described above are merely schematic. For example, the flowcharts and structure diagrams in the accompanying drawings show the possible architectures, functions and operations of the devices, methods and computer program products according to multiple embodiments of the present invention. In this regard, each box in the flowchart or block diagram can represent a module, a program segment or a part of the code, and the module, program segment or a part of the code contains one or more executable instructions for implementing the specified logical functions. It should also be noted that in an alternative implementation, the functions marked in the box can also occur in an order different from that marked in the accompanying drawings. For example, two consecutive boxes can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the structure diagram and / or flowchart, and the combination of boxes in the structure diagram and / or flowchart, can be implemented using a dedicated hardware-based system that performs the specified function or action, or can be implemented using a combination of dedicated hardware and computer instructions.

[0091] In addition, the functional modules or units in the various embodiments of the present invention may be integrated together to form an independent part, or each module may exist independently, or two or more modules may be integrated to form an independent part.

[0092] If the function is implemented in the form of a software function module and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention is essentially or the part that contributes to the prior art or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions for enabling a computer device (which can be a smart phone, a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present invention. The aforementioned storage medium can be a non-volatile storage medium or a volatile storage medium. For example, the storage medium can be: a U disk, a mobile hard disk, a read-only memory (ROM, Read-Only Memory), a random access memory (RAM, Random Access Memory), a magnetic disk or an optical disk, and other media that can store program codes.

[0093] The above description is only a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any technician familiar with this technical field can easily think of changes or replacements within the technical scope disclosed by the present invention, which should be covered by the scope of protection of the present invention.

Claims

1. A task planning and execution method based on a process engine, characterized in that: The method comprises: Create a process model, set metadata for the process model, and create a flowchart based on the metadata of the process model, wherein the metadata of the process model includes the process name, process classification, reference knowledge, work documents, work content, and process type; the flowchart includes multiple process nodes, node executors, node template files, routing gateways, and listeners; the process nodes include a start node, multiple task nodes, and an end node; and the types of process nodes include multiple-person multi-tasking and single-person single-tasking; Deploy the flowchart to a process engine to obtain executable process definition data; Creating a task execution, setting metadata for the task execution, and binding the executable process definition data to the metadata for the task execution, wherein the metadata for the task execution includes task name, task type, task time, task description, task priority, task classification, and participants; Setting the business data of each process node according to the executable process definition data, starting the task execution according to the business data of the process node, running the metadata of the task execution, and generating a plurality of to-do items according to the metadata information of the process model, wherein the business data includes handling method, node executor, node co-organizer, work content, work template and reference knowledge; The step of deploying the flowchart to a process engine to obtain executable process definition data includes: Obtaining the BPMN file generated when making the flowchart through the front-end component; Deploy the BPMN file to the process engine through the API interface, generate a process template, and generate corresponding executable process definition data according to the process template; The step of starting the task execution according to the business data includes: Dynamically generate business data for each process node according to the requirements of task execution; Associating the business data of each process node with the corresponding flow chart to start the task execution; The step of generating a plurality of to-do items according to the metadata information of the process model includes: Each of the to-do items is completed through each of the process nodes, and when each of the process nodes is completed, a file flow operation of the process node is performed according to the completion status of the corresponding to-do item; Monitor the process definition data during the task execution, wherein the process definition data includes task node status, document quantity, execution process and execution time.

2. The task planning and execution method based on the process engine according to claim 1 is characterized in that: The step of generating a plurality of to-do items according to the metadata information of the process model further includes: generating a plurality of to-do items according to the work document; A task reference file is generated according to the executable process definition data, the metadata of the task execution and the business data of each process node.

3. A task planning and execution device based on a process engine, characterized in that: The device comprises: A creation module is used to create a process model, set metadata for the process model, and produce a flowchart based on the metadata of the process model, wherein the metadata of the process model includes the process name, process classification, reference knowledge, work documents, work content, and process type; the flowchart includes multiple process nodes, node executors, node template files, routing gateways, and listeners; the process nodes include a start node, multiple task nodes, and an end node; and the types of process nodes include multiple-person multi-tasking and single-person single-tasking; A deployment module, used to deploy the flowchart into a process engine to obtain executable process definition data; a binding module, configured to create a task execution, set metadata for the task execution, and bind the executable process definition data to the metadata for the task execution, wherein the metadata for the task execution includes task name, task type, task time, task description, task priority, task classification, and participants; an operation module, configured to set the business data of each process node according to the executable process definition data, initiate the task execution according to the business data of the process node, run the metadata of the task execution, and generate a plurality of to-do items according to the metadata information of the process model, wherein the business data includes the handling method, node executor, node co-organizer, work content, work template, and reference knowledge; The step of deploying the flowchart to a process engine to obtain executable process definition data includes: Obtaining the BPMN file generated when making the flowchart through the front-end component; Deploy the BPMN file to the process engine through the API interface, generate a process template, and generate corresponding executable process definition data according to the process template; The step of starting the task execution according to the business data includes: Dynamically generate business data for each process node according to the requirements of task execution; Associating the business data of each process node with the corresponding flow chart to start the task execution; The step of generating a plurality of to-do items according to the metadata information of the process model includes: Each of the to-do items is completed through each of the process nodes, and when each of the process nodes is completed, a file flow operation of the process node is performed according to the completion status of the corresponding to-do item; Monitor the process definition data during the task execution, wherein the process definition data includes task node status, document quantity, execution process and execution time.

4. A computer device, characterized in that: The method comprises a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the steps of the task planning and execution method based on the process engine according to any one of claims 1 to 2 are implemented.

5. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the task planning and execution method based on the process engine according to any one of claims 1 to 2 are implemented.

Images