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

Abstract

The invention discloses a task planning execution method and device based on a process engine, equipment and a medium. The method comprises the steps that a process model is created, metadata of the process model is set, a flow chart is made according to the metadata of the process model, and the flow chart comprises a plurality of process nodes; deploying the flow chart into a flow engine to obtain executable flow definition data; creating task execution, setting metadata of the task execution, and binding the executable process definition data with the metadata of the task execution; and 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 nodes, running metadata of the task execution, and generating a plurality of backlogs according to metadata information of the process model. According to the method and the device, the file data generated in the task execution process and the task execution process can be controlled more accurately, the to-do list can be generated in the task execution process, and the business scene is expanded, so that the task execution progress is tracked in time.

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 of the task tools on the market are task execution tools, focusing on process approval, and are mostly used for approval matters such as multi-task collaboration, progress control, and single task execution, rather than focusing on the subtasks and task material aggregation of each task link. However, among the customer groups, there are a large number of process tasks and each task link will derive multiple to-do sub-items and the need to archive 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 to 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 according to 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 of the task execution, and binding the executable process definition data to the metadata of the task execution;

[0010] The business data of each of the process nodes 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 a start node, multiple task nodes and an end node; the types of process nodes include multiple people handling multiple tasks and one person handling a single task.

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

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

[0014] The BPMN file is deployed to the process engine through an 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 of each process node according to the requirements of task execution;

[0018] The business data of each of the process nodes 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] Generate 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 of the process nodes.

[0022] Optionally, the 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 in 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, used to create a process model, set metadata of the process model, and make a flow chart according to 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, used to create a task execution, set metadata of the task execution, and bind the executable process definition data with the metadata of 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, a computer device is provided in an embodiment of the present disclosure, wherein the computer device includes 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 described in the first aspect are implemented.

[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 task planning and execution method based on the process engine provided in the embodiment of the present application creates a process model, sets the metadata of the process model, and produces a flowchart according to the metadata of the process model, wherein the flowchart includes multiple process nodes; deploys the flowchart to the process engine to obtain executable process definition data; creates task execution, sets the metadata of the task execution, and binds the executable process definition data to the metadata of the task execution; sets the business data of each process node according to the executable process definition data, starts the task execution according to the business data of the process node, runs the metadata of the task execution, and generates 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 understandable, preferred embodiments are given below and described in detail with reference to the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] In order 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 regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without creative work. In each of the drawings, similar components are numbered similarly.

[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 schematic diagram of the structure of a computer device provided in an embodiment of the present application is shown. DETAILED DESCRIPTION

[0040] Embodiments of the present invention are described in detail below, examples of which 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 only used to explain the present invention, and cannot be understood 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 a central 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 a central element at the same time. In contrast, 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 clearly specified and limited, the terms "installed", "connected", "connected", "fixed" and the like should be understood in a broad sense, for example, it can be a fixed connection, a detachable connection, or an integral connection; it can be a mechanical connection or an electrical connection; it can be a direct connection or an indirect connection through an intermediate medium, it can be the internal connection of two elements or the interaction relationship between two elements. For ordinary technicians in this field, the specific meanings of the above terms in the present invention can be understood according to specific circumstances.

[0043] In addition, the terms "first" and "second" are used for descriptive purposes only and should not be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features. Therefore, the features defined as "first" and "second" may explicitly or implicitly include one or more of the features. In the description of the present invention, the meaning of "plurality" is two or more, unless otherwise clearly and specifically defined.

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

[0045] Example 1

[0046] like Figure 1 As shown, it 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 through a graphical process design tool. The flowchart includes multiple process nodes, node executors, node template files, routing gateways and listeners. Among them, 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 executes to 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 things and one person handling one thing. One person handling one thing means that only one person can receive and handle the process node, and multiple people handling multiple things means that when multiple people handle it at the same time, all of them must complete the process before the process can be passed.

[0051] It should be noted that the flowchart of this embodiment includes 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 to clarify the responsible persons of the process nodes. It does not support personnel changes and determine the scope of responsibility during task execution. It does not support supplementing to-do items, thereby reducing unnecessary changes and interference.

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

[0053] The above method is separated from the native designer of the process engine. By drawing the flowchart with built-in key data and rule definitions, it streamlines the user's operations, simplifies the process of process drawing, and reduces the user's usage cost. In addition, by presetting the executors on the flowchart and specifying the responsible person for each task, the work distribution and responsibility are clarified. At the same time, the possibility of personnel changes during task execution is supported, making task planning and execution more flexible, ensuring the smooth progress of the task, and further facilitating the subsequent task data monitoring.

[0054] Step S120, deploying 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, a task execution is created and metadata of the task execution is set. The metadata of the task execution includes information such as task name, task type, task time, task description, task priority, task classification and participants, and the above-mentioned metadata of the task execution is bound to the executable process definition data.

[0058] The above method supports the change of metadata of task execution without affecting the established settings in the process. Whether it is to modify the task content, adjust the participants, or change the task priority, it can be adjusted at any time. The system will automatically adapt to these changes and maintain the continuity and stability of the process. Through flexible design, users can dynamically adjust the metadata of task execution according to actual needs, ensure that the execution of the process is more in line with the actual situation, and improve overall work efficiency and accuracy.

[0059] Step S140, setting the business data of each of the process nodes 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] Understandably, in the process of creating task execution, it supports dynamically configuring the business data of the process node. These business data can be dynamically generated according to the needs of task execution without affecting the original data in the process engine. And the corresponding flowchart and executor can be associated, so that the task execution can be started according to the business data and run a deployed task execution metadata according to business needs.

[0062] Furthermore, when starting task execution, the work documents in the metadata information of the process model will generate to-do items one by one, and classify each to-do item 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, so that users can understand the background and requirements of the task and other information.

[0063] In the above method, work documents will generate to-do items during task execution, including task assignment, approval, notification, etc. For each to-do item, relevant information such as task description, deadline, executor, etc. 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 executors, so as to track the progress of task execution in a timely manner. The business scenarios are expanded, processes are bound to tasks, and task-driven process execution can more accurately control the results of task execution, and the task files of each link can be summarized and managed in a unified manner.

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

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

[0066] Step S160, monitoring the process definition data in 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 the task execution process, each process node supports the completion of to-do items. When the process node is completed, the approval, copy, transfer and other file flow operations of the process node can be performed according to the completion status of the corresponding to-do items. In addition, the task to-do items, task completion status, task submission files, etc. at different stages can be displayed on the viewing panel to judge the problems and differences generated during the task execution process. Users can remind the executors of the tasks to correct them through comments.

[0068] At the same time, it provides multiple perspectives to monitor the process definition data in task execution, including task node status, document quantity, execution process, execution time, etc. Users can view the process definition data to understand the list of all unopened, executing, and completed processes, view the execution process of all processes, view the execution records, generated files and to-do items of each process instance, view the completion status of to-do items, and view the specific links of the current process execution to promote the smooth development of business.

[0069] Understandably, the user can also review and aggregate the 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 the above tasks can be classified and managed according to their types and stages. Through the management of to-do items and data, comprehensive monitoring of task execution can be achieved, and the processing time of different types of to-do items, as well as the number of files generated and executed at each stage can be analyzed, so as to discover problems and make timely adjustments and optimizations.

[0071] The task planning and execution method based on the process engine provided in the embodiment of the present application creates a process model, sets the metadata of the process model, and produces a flowchart according to the metadata of the process model, wherein the flowchart includes multiple process nodes; deploys the flowchart to the process engine to obtain executable process definition data; creates task execution, sets the metadata of the task execution, and binds the executable process definition data to the metadata of the task execution; sets the business data of each process node according to the executable process definition data, starts the task execution according to the business data of the process node, runs the metadata of the task execution, and generates 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, used to create a process model, set metadata of the process model, and make a flow chart according to the metadata of the process model, wherein the flow chart includes a plurality of process nodes;

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

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

[0077] The running 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 track the progress of task execution in a timely manner.

[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 and communicated 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 microprocessors, application specific integrated circuits (Application Specific Integrated Circuit, ASIC), programmable gate arrays (Field-Programmable Gate Array, FPGA), digital processors (Digital Signal Processor, DSP), embedded devices, etc.

[0082] The computer device may be a computing device such as a desktop computer, a notebook, a PDA, a cloud server, etc. The computer device may interact with a user through a keyboard, a mouse, a remote controller, a touch pad, or a voice control device.

[0083] The memory 41 includes at least one type of readable storage medium, and the readable storage medium includes flash memory, hard disk, multimedia card, card-type memory (for example, SD or D slot compatibility test memory, etc.), 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, disk, optical disk, etc. In some embodiments, the memory 41 can be an internal storage unit of the computer device 4, such as a 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 memory card (Smart Media Card, SMC), a secure digital (Secure Digital, SD) card, a flash card (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 of the slot compatibility test method, etc. 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] The processor 42 may be a central processing unit (CPU), a controller, a microcontroller, a microprocessor, or other task planning execution chips based on a process engine in some embodiments. 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 run computer-readable instructions or process data stored in the memory 41, such as computer-readable instructions for running the slot compatibility test 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 also provides a computer-readable storage medium, on which a computer program is stored. 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 disk, multimedia card, card-type memory (for example, SD or DX memory, etc.), 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, disk, optical disk, etc. In some embodiments, the computer-readable storage medium can be an internal storage unit of a computer device, such as a hard disk or memory of the computer device. In other embodiments, the computer-readable storage medium can also be an external storage device of a computer device, such as a plug-in hard disk equipped on the computer device, a smart memory card (Smart Media Card, referred to as SMC), a secure digital (Secure Digital, referred to as SD) card, a flash card, etc. Of course, the computer-readable storage medium can 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 an operating system and various application software installed on the computer device. In addition, the computer-readable storage medium can also be used to temporarily store various types of data that have been output or are to be output.

[0090] In several embodiments provided in the present 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 architecture, 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 a code, and the module, a program segment or a part of a code contains one or more executable instructions for implementing the specified logical function. It should also be noted that in an alternative implementation, the functions marked in the box can also occur in a different order from the order 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 the flow chart, and the combination of boxes in the structure diagram and / or the flow chart, can be implemented with a dedicated hardware-based system that performs a specified function or action, or can be implemented with 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 partly contributed to the prior art or 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 several instructions to enable 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 disk or an optical disk, and other media that can store program codes.

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

Claims

1. A task planning and execution method based on a process engine, characterized in that: The method comprises: 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; Deploy the flowchart to a process engine to obtain executable process definition data; Creating a task execution, setting metadata of the task execution, and binding the executable process definition data to the metadata of the task execution; The business data of each of the process nodes 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.

2. The task planning and execution method based on the process engine according to claim 1 is characterized in that: 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 start 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.

3. The task planning and execution method based on the process engine according to claim 1 is characterized in that: The step of deploying the flowchart to a process engine to obtain executable process definition data includes: Acquire the BPMN file generated when making the flowchart through the front-end component; The BPMN file is deployed to the process engine through an API interface to generate a process template, and corresponding executable process definition data is generated according to the process template.

4. The task planning and execution method based on the process engine according to claim 1 is characterized in that: The metadata of 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.

5. The task planning and execution method based on the process engine according to claim 1 is characterized in that: The starting the task execution according to the business data includes: Dynamically generate business data of each process node according to the requirements of task execution; The business data of each of the process nodes is associated with the corresponding flow chart to start the task execution.

6. The task planning and execution method based on the process engine according to claim 2 is characterized in that: The generating a plurality of to-do items according to the metadata information of the process model comprises: Generate 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 of the process nodes.

7. 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: 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 in the task execution, wherein the process definition data includes task node status, document quantity, execution process and execution time.

8. A task planning and execution device based on a process engine, characterized in that: The device comprises: A creation module, used to create a process model, set metadata of the process model, and make a flow chart according to the metadata of the process model, wherein the flow chart includes a plurality of process nodes; A deployment module, used to deploy the flowchart into a process engine to obtain executable process definition data; A binding module, used to create a task execution, set metadata of the task execution, and bind the executable process definition data with the metadata of the task execution; 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.

9. A computer device, characterized in that: It 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 described in any one of claims 1 to 7 are implemented.

10. 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 a process engine according to any one of claims 1 to 7 are implemented.

Images