A process running method and device, electronic equipment and storage medium

Abstract

The application provides a process running method and device, electronic equipment and storage medium. The method comprises the following steps: obtaining a work process instance identifier of a to-be-run process; obtaining a corresponding work process instance according to the work process instance identifier; wherein the work process instance comprises a stage process, the stage process comprises a plurality of measures, and the plurality of measures can be executed simultaneously without gateway judgment when the corresponding stage process is called; and running the work process instance to execute the plurality of measures. According to the application, the stage process capable of being executed simultaneously without gateway judgment is introduced into the work process instance, and the efficiency of the work process running is improved because the gateway judgment node is reduced.

Description

Technical Field

[0001] This application relates to the field of computer technology, and more specifically, to a process operation method, apparatus, electronic device, and storage medium. Background Technology

[0002] A workflow refers to the sequential flow of activities related to a task, including the steps, procedures, and processes involved. In the traditional implementation of business processes, many companies use paper forms and manual processes, requiring approvals and signatures at each level, resulting in extremely low efficiency.

[0003] With the development of information technology, workflow systems have emerged. In the flowcharts generated by workflow systems, the flowchart structure and node configurations are bound together. A corresponding flowchart can be generated for each task to process that task.

[0004] Currently, workflows are all pre-created by staff based on requirements, which prevents multiple discrete measures from being executed simultaneously without gateway judgment, resulting in low efficiency when using workflows to process tasks. Summary of the Invention

[0005] The purpose of this application is to provide a process operation method, apparatus, electronic device, and storage medium to improve the efficiency of running workflows and processing tasks.

[0006] In a first aspect, embodiments of this application provide a process execution method, including:

[0007] Obtain the workflow instance identifier of the process to be run;

[0008] The corresponding workflow instance is obtained based on the workflow instance identifier; wherein, the workflow instance includes a stage process, and the stage process includes multiple measures and means, which can be executed simultaneously without gateway judgment when the corresponding stage process is invoked;

[0009] Run a workflow instance to execute multiple measures and means.

[0010] This application embodiment introduces a stage process in the workflow instance that can be executed simultaneously without gateway judgment. Since the gateway judgment node is reduced, the efficiency of workflow operation is improved.

[0011] In any embodiment, the workflow instance further includes a sub-plan workflow, which is generated by referencing a workflow scheme orchestrated by a third party.

[0012] This application embodiment uses a process scheme orchestrated by a third party, so there is no need to re-arrange the sub-plan processes during the process orchestration stage, which improves the efficiency of generating workflow instances.

[0013] In any embodiment, running a workflow instance includes:

[0014] Obtain the task list corresponding to the workflow instance. The task list includes multiple tasks, and the multiple tasks are processed by calling the measures and means corresponding to the stage process.

[0015] Generate a corresponding handle object for each task in the task list, and obtain a collection of handle objects corresponding to the task list;

[0016] The process executes multiple measures and methods within the workflow instance to process the handle objects in the handle object collection.

[0017] This application embodiment generates handle objects for each task in the task list corresponding to the workflow instance. When running the workflow instance, the tasks are executed in the order of the handle objects in the handle object collection, thereby improving the efficiency of running the workflow.

[0018] In any embodiment, generating a handle object for a corresponding task based on the task type of each task in the task list includes:

[0019] For each phase task in the phase process, deploy and enable the corresponding phase process.

[0020] Query the list of phase tasks corresponding to the phase process, wherein the list of phase tasks includes information on the phase tasks contained in the phase process;

[0021] Generate a corresponding handle object based on the task information for each stage in the task list.

[0022] This application embodiment deploys stage tasks for stage types, queries the stage task list, generates corresponding handle objects, and finally integrates the generated handle objects into the overall process. This enables the simultaneous execution of various stage tasks in a stage without using gateway judgment. Since there is no gateway node, the number of process nodes executed during process operation is reduced, thus improving the efficiency of process operation.

[0023] In any embodiment, the workflow instance further includes sub-plan workflows, which are generated by referencing a workflow scheme orchestrated by a third party; the task list includes sub-plan tasks; and a handle object is generated for each task in the task list based on its corresponding task type, including:

[0024] For sub-plan tasks whose task type is sub-plan, copy the sub-plan process template information corresponding to the sub-plan task and instantiate the sub-plan process;

[0025] Deploy and enable the business process diagram information corresponding to the instantiated sub-plan process;

[0026] Query the list of sub-contingency plan tasks corresponding to the sub-contingency plan process; the list of sub-contingency plan tasks includes information on the sub-contingency plan tasks contained in the sub-contingency plan process;

[0027] Generate a corresponding handle object based on the information of each sub-plan task in the sub-plan task list.

[0028] This application embodiment uses pre-arranged sub-plans from third parties, eliminating the need to rearrange sub-plans when creating a process, thus improving the efficiency of process creation.

[0029] In any embodiment, processing the handle objects in the handle object collection includes:

[0030] The handle objects in the handle object collection are called sequentially, and the running status of the handle object is determined according to the task identifier and process instance identifier corresponding to the handle object.

[0031] Obtain the method instance information of the task node whose running status is "running", and process the task node according to the method instance information.

[0032] This application embodiment integrates the handle objects corresponding to the tasks contained in the stage and the tasks contained in the sub-plan into the overall process, thereby sequentially calling the collection of handle objects corresponding to the overall process. This allows the process to reference processes that have been arranged by third parties and to execute multiple discrete tasks simultaneously without gateway judgment.

[0033] In any embodiment, the method further includes:

[0034] Receive workflow change requests, which include the task node identifier to be changed and the change type;

[0035] If the task node to be changed is not yet started in the workflow instance, then the task to be changed in the workflow instance will be modified according to the change type.

[0036] This application embodiment allows for changes to tasks that have not yet started in the workflow, thereby meeting the user's change requirements without affecting the normal operation of the workflow.

[0037] In any embodiment, the method further includes:

[0038] If an exception is received during the execution of a workflow instance, exception handling options are displayed for the user to choose how to handle the exception in the task. Exception handling options include restarting the task, skipping the task, and ending the workflow.

[0039] This application provides exception handling options. When an exception occurs during the operation of the workflow, the user can select the corresponding exception handling method.

[0040] In any embodiment, the method further includes:

[0041] Obtain the completed work plan workflow template, and generate template BPMN file information and workflow node information based on the work plan workflow template;

[0042] Store the template BPMN file information and process node information.

[0043] In this application embodiment, a work plan process template is pre-created during the preparation stage, which can be reused during the application stage, thereby improving the efficiency of creating processes corresponding to tasks.

[0044] In any embodiment, the method further includes:

[0045] Copy the work plan and workflow template information required for the target task. The work plan and workflow template information includes basic workflow information, template BPMN information, and measures and means; and the work plan and workflow template information is pre-configured.

[0046] Add basic workflow information to the workflow instantiation table to instantiate the workflow template and generate a workflow instance identifier.

[0047] Deploy the instantiated template BPMN information on the Camunda workflow engine tool, generate a deployment identifier, and update the deployment identifier to the workflow instantiation table;

[0048] Bind the work plan instance identifier to the task identifier corresponding to the target task.

[0049] This application embodiment references the work plan process template by copying the work plan process template information, so that subsequent changes to the work plan process template will not affect the execution of other tasks that reference the same template.

[0050] In any embodiment, the method further includes:

[0051] Receive the start request of the target task, which includes the task identifier corresponding to the target task;

[0052] Retrieve the work plan instance identifier that is bound to the task identifier;

[0053] Retrieve the deployment identifier from the corresponding work plan instance table based on the work plan instance identifier;

[0054] The process definition identifier is obtained by calling the method to retrieve the process definition based on the deployment identifier.

[0055] Run the corresponding instantiated template BPMN according to the process definition identifier to instantiate the workflow, generate the workflow instance identifier, and the task identifier of each task corresponding to the workflow instance.

[0056] Bind the workflow instance identifier to the work plan instance identifier.

[0057] In this embodiment of the application, before running the process, the created workflow is instantiated, and the workflow instance identifier is bound to the work plan instance identifier, so that the corresponding workflow instance identifier can be determined by the task identifier that also has a binding relationship with the work plan instance identifier.

[0058] Secondly, embodiments of this application provide a process operation apparatus, including:

[0059] The identifier acquisition module is used to obtain the workflow instance identifier of the process to be run;

[0060] The instance acquisition module is used to obtain the corresponding workflow instance based on the workflow instance identifier. The workflow instance includes a stage process, and the stage process includes multiple measures and means. When the corresponding stage process is called, the multiple measures and means can be executed simultaneously without gateway judgment.

[0061] The process execution module is used to run workflow instances to execute multiple measures and means.

[0062] Thirdly, embodiments of this application provide an electronic device, including: a processor, a memory, and a bus, wherein,

[0063] The processor and the memory communicate with each other via the bus;

[0064] The memory stores program instructions that can be executed by the processor, and the processor can execute the method of the first aspect by calling the program instructions.

[0065] Fourthly, embodiments of this application provide a non-transitory computer-readable storage medium, comprising:

[0066] The non-transitory computer-readable storage medium stores computer instructions that cause the computer to perform the method of the first aspect.

[0067] Other features and advantages of this application will be set forth in the following description and will be apparent in part from the description or may be learned by practicing embodiments of this application. The objectives and other advantages of this application may be realized and obtained by means of the structures particularly pointed out in the written description, claims, and drawings. Attached Figure Description

[0068] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments of this application will be briefly introduced below. It should be understood that the following drawings only show some embodiments of this application and should not be regarded as a limitation of the scope. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0069] Figure 1 A workflow diagram provided for existing technologies;

[0070] Figure 2 A flowchart including stages is provided for an embodiment of this application;

[0071] Figure 3 This is a schematic flowchart of a process operation method provided in an embodiment of this application;

[0072] Figure 4 This application provides a schematic diagram of a workflow template for a specific embodiment.

[0073] Figure 5 A schematic diagram of the reference stage provided for embodiments of this application;

[0074] Figure 6 This application provides a schematic diagram of a preprocessing stage flow.

[0075] Figure 7 This application provides a schematic diagram of a method for generating a collection of handle objects.

[0076] Figure 8 This is a schematic diagram of the method flow for processing handle objects provided in an embodiment of this application;

[0077] Figure 9 This application provides a schematic diagram of a process operation device structure.

[0078] Figure 10 This is a schematic diagram of the physical structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0079] The embodiments of the technical solution of this application will now be described in detail with reference to the accompanying drawings. These embodiments are only used to more clearly illustrate the technical solution of this application and are therefore merely examples, and should not be used to limit the scope of protection of this application.

[0080] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application pertains; the terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the application; the terms “comprising” and “having”, and any variations thereof, in the specification, claims, and foregoing description of the drawings are intended to cover non-exclusive inclusion.

[0081] In the description of the embodiments of this application, technical terms such as "first" and "second" are used only to distinguish different objects and should not be construed as indicating or implying relative importance or implicitly specifying the number, specific order, or primary and secondary relationship of the indicated technical features. In the description of the embodiments of this application, "multiple" means two or more, unless otherwise explicitly defined.

[0082] In this document, the term "embodiment" means that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of this application. The appearance of this phrase in various places throughout the specification does not necessarily refer to the same embodiment, nor is it a separate or alternative embodiment mutually exclusive with other embodiments. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described herein can be combined with other embodiments.

[0083] In the description of the embodiments in this application, the term "and / or" is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Additionally, the character " / " in this document generally indicates that the preceding and following related objects have an "or" relationship.

[0084] In the description of the embodiments of this application, the term "multiple" refers to two or more (including two), similarly, "multiple sets" refers to two or more (including two sets), and "multiple pieces" refers to two or more (including two pieces).

[0085] In the description of the embodiments of this application, the technical terms "center," "longitudinal," "lateral," "length," "width," "thickness," "upper," "lower," "front," "rear," "left," "right," "vertical," "horizontal," "top," "bottom," "inner," "outer," "clockwise," "counterclockwise," "axial," "radial," and "circumferential" indicate the orientation or positional relationship based on the orientation or positional relationship shown in the accompanying drawings. They are only for the convenience of describing the embodiments of this application and simplifying the description, and are not intended to indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation. Therefore, they should not be construed as limitations on the embodiments of this application.

[0086] In the description of the embodiments of this application, unless otherwise expressly specified and limited, technical terms such as "installation," "connection," "joining," and "fixing" should be interpreted broadly. For example, they can refer to a fixed connection, a detachable connection, or an integral part; they can refer to a mechanical connection or an electrical connection; they can refer to a direct connection or an indirect connection through an intermediate medium; they can refer to the internal communication of two components or the interaction between two components. For those skilled in the art, the specific meaning of the above terms in the embodiments of this application can be understood according to the specific circumstances.

[0087] First, the concepts involved in the embodiments of this application will be explained:

[0088] Camunda workflow engine is one of the mainstream workflow engines currently available.

[0089] Camunda Modeler is a flowchart designer officially provided by Camunda, used to edit flowcharts and other models [forms], that is, a flowchart drawing tool.

[0090] Camunda BPM is a business process management platform officially provided by Camunda. It is used to manage and deploy process definitions, execute tasks, policies, etc. After downloading and installing a Camunda platform, and successfully extracting the Camunda distribution, execute the script named start.bat (for Windows users) or start.sh (for Unix users).

[0091] Business Process Modeling Notation (BPMN) is a standardized specification that outlines how graphical elements are combined to form a Business Process Diagram. BPMN's primary goal is to provide a markup language understandable to all business users, including business analysts, software developers, and business managers and monitors. BPMN will also support the generation of executable BPEL4WS language. Therefore, BPMN builds a standardized bridge between business process design and implementation. BPMN defines business process diagrams, based on flowchart technology, while tailoring the creation of graphical models of business process operations. The business process model is a network of graphical objects, including activities (or tasks) and flow control defining the sequence of operations.

[0092] Example of measures and means: When compiling a contingency plan, measures and means are selected from the measures and means library and entered into the compilation process. After the measures and means are instantiated, they belong only to the compilation process and are equivalent to nodes in the process.

[0093] Contingency plans / work plans: A set of measures and methods arranged together to form a complete process plan is called a contingency plan or work plan. It is equivalent to a process library. Before being commanded and dispatched, the process library must be prepared in advance and ready to be called.

[0094] Implementation of measures and means: Implementation of measures and means is the definition after the data information of the implementation of measures and means instances is configured. This data information content is the implementation of measures and means, that is, the definition after the node is configured.

[0095] Process Definition: A Process Definition is a complete description of a business process.

[0096] Stage: A collection of examples of measures and methods.

[0097] Sub-plan: Referencing pre-prepared work plans and processes from third parties.

[0098] API approach: The underlying layer uses HttpClient technology to send HTTP requests to other interfaces to obtain data.

[0099] Through long-term research, the inventors of this application have discovered that in existing workflows, for multiple parallel measures and methods, the judgment is made through the upper-level gateway. Figure 1This document describes a workflow diagram for existing technology. In this diagram, measures named "Instruction" and measures named "Message" are two parallel measures, with their preceding process node serving as a branch (i.e., a gateway). The decision to execute either the instruction measure or the message measure is determined by the branch node's decision. Furthermore, this workflow diagram references a workflow template stored in a workflow library. Therefore, the existing workflow suffers from the following technical problems:

[0100] (1) Unable to reference and use workflows already orchestrated by third parties;

[0101] (2) Discrete measures and means cannot be arranged. That is, in a certain process, it is not allowed to execute multiple measures and means simultaneously without gateway judgment or add them to independent process arrangement. Figure 2 A flowchart including stages is provided for embodiments of this application, such as Figure 2 As shown, the three methods named "Instruction", "General API", and "Message" are listed side by side, and there is no gateway in the upper-level process node.

[0102] To address the aforementioned technical problems, embodiments of this application provide a process execution method. During execution, this method generates a set of handles from all task nodes in the entire process flow diagram. By processing each handle object in the handle set, it can execute workflows pre-arranged by a third party or run stage tasks (i.e., a collection of multiple discrete measures and means).

[0103] It is understood that the process operation method provided in this application embodiment can be applied to electronic devices, which include terminals and servers; wherein the terminal can specifically be a smartphone, tablet computer, computer, personal digital assistant (PDA), etc.; the server can specifically be an application server or a web server.

[0104] Figure 3 This is a flowchart illustrating a process operation method provided in an embodiment of this application, such as... Figure 3 As shown, the method includes:

[0105] Step 301: Obtain the workflow instance identifier of the process to be run.

[0106] Users can create one or more tasks on the electronic device according to their actual needs, with the target task being one of the user-created tasks. It is understood that tasks can include major risk warnings, expense reimbursements, etc., but this embodiment does not specifically limit this. The electronic device generates a unique task identifier for each task. When a task is started, the electronic device can obtain the corresponding workflow instance identifier based on the task identifier corresponding to the target task.

[0107] A workflow instance identifier is used to characterize the uniqueness of a workflow. Each task corresponds to one workflow, and this workflow is generated by running an instantiated BPMN and obtaining the workflow instance identifier.

[0108] Step 302: Obtain the corresponding workflow instance based on the workflow instance identifier; wherein, the workflow instance includes a stage process, the stage process includes multiple measures and means, and the multiple measures and means can be executed simultaneously without gateway judgment when the corresponding stage process is invoked.

[0109] In the specific implementation process, each workflow instance has its own unique workflow instance identifier. Therefore, after obtaining the workflow instance identifier, the electronic device can obtain the corresponding workflow instance based on the workflow instance identifier.

[0110] It is understandable that a workflow instance consists of multiple measures and means. Among these measures and means, all or part may belong to a stage process. That is, a stage process includes multiple discrete measures and means, which can be executed simultaneously without gateway judgment, such as... Figure 2 As shown.

[0111] Step 303: Run a workflow instance to execute multiple measures and means.

[0112] When a workflow instance is running, and it reaches a stage of the workflow, multiple measures and means included in that stage can be executed simultaneously. Figure 2 For example, it can simultaneously execute general API methods, command methods, and message methods.

[0113] This application embodiment introduces a stage process in the workflow instance that can be executed simultaneously without gateway judgment. Since the gateway judgment node is reduced, the efficiency of workflow operation is improved.

[0114] Based on the above embodiments, the workflow example also includes a sub-plan workflow, which is generated by referencing a workflow scheme orchestrated by a third party.

[0115] In practical implementation, workflow examples may include not only stage processes but also sub-plan processes. Sub-plan processes refer to processes already prepared by a third party. By incorporating sub-plan processes into the workflow example, staff can directly reference them without needing to prepare them during the workflow preparation phase. It is understood that sub-plan processes also include at least one measure or measure.

[0116] In addition, workflow instances can also include general measures and means, which refer to measures and means in the workflow instance other than those included in the stage process and sub-plan process. Workflow instances can also include only sub-plan processes, or include sub-plan processes and general measures and means, or include stage processes and general measures and means, etc.

[0117] Based on the above embodiments, running the workflow instance includes:

[0118] Obtain the task list corresponding to the workflow instance. The task list includes multiple tasks, and the multiple tasks are processed by calling the measures and means corresponding to the stage process.

[0119] Generate a corresponding handle object for each task in the task list, and obtain a collection of handle objects corresponding to the task list;

[0120] The process executes multiple measures within a workflow instance, processing the handle objects in the handle object collection. In practice, a workflow instance identifier refers to a workflow, which consists of multiple logically related tasks. Once a workflow is instantiated, the resulting task set of the workflow instance constitutes a task list. Therefore, the electronic device can obtain the corresponding workflow's task list through the workflow instance identifier. This task list contains multiple tasks, each corresponding to a task identifier. The task identifier is used to uniquely identify the corresponding task. Furthermore, the tasks in the task list can be sorted according to the workflow's runtime logic.

[0121] The task type in the task list can include at least one of the following: normal type, stage type, and sub-plan type. Stage type refers to the type of task belonging to a stage; multiple tasks belonging to the same stage can be executed simultaneously without gateway judgment. Sub-plan type refers to the type of task belonging to a sub-plan, which is the type of task included in a workflow that has been pre-arranged by a third party. Normal type refers to the type of task in the workflow other than stage and sub-plan types.

[0122] It should be noted that the workflow may include multiple stages or multiple sub-plans. This application embodiment does not limit the specific types of tasks included in the workflow.

[0123] The handle objects in the handle object collection are obtained by processing each task in the workflow. Therefore, each task is strongly bound to its corresponding handle, and the handle object is what provides operations to the outside world.

[0124] During the process, the handle objects are processed sequentially according to their order in the handle object collection to complete the processing of the target task.

[0125] This application embodiment converts tasks in a workflow instance into handle objects, thereby obtaining a set of handle objects that correspond to a complete workflow. Thus, by processing the handle objects in the handle object set sequentially, multiple discrete tasks can be executed simultaneously without going through a gateway.

[0126] For ease of understanding, this application describes the overall scheme of the embodiments of this application from the preparation stage, the reference stage, the initiation stage, and the compensation stage.

[0127] I. Preparation Stage

[0128] During the preparation phase, users can pre-create multiple work plan workflow templates according to actual needs. For example, they can create a work plan workflow template with a "major risk warning" type, and arrange the relevant measures and means under this workflow. It is understood that electronic devices can provide a visual interactive interface, offering various measure and means components. When arranging the workflow, users can drag and drop the corresponding type of measure and means components from the toolbar to the arrangement area. After arrangement is complete, the work plan workflow template can generate BPMN file information and workflow node information, and store them in the database.

[0129] Among them, BPMN file information, i.e., those with BPMN tags (i.e. <bpmn:xxx>The XML file data includes the start and end nodes of the process, newly added nodes (measures / means), the required parameter configurations for BPMN, and the coordinates of the nodes. Node information includes: ID, name, the next node (output) (ID), and the previous node (input). Process node information consists of information about the measures / means: name, description, node ID, parent node ID, description, and node type (whether it's a regular node, a stage, or a subprocess node).

[0130] Figure 4 This is a schematic diagram of a work plan flowchart provided in an embodiment of this application, such as... Figure 4 As shown, the workflow template for this risk warning scheme includes two phases: Phase 1 and Phase 2. Phase 1 includes task nodes for compiling risk warning reports, issuing risk warning instructions, and issuing risk warning cancellation reports. Phase 2 includes task nodes for emergency response. Parameter configuration is also possible within the risk warning instruction task node, allowing for the configuration of instruction content and the recipient of the instructions.

[0131] II. Citation Stage

[0132] Electronic devices create a new task through the command and dispatch platform, referencing a relevant work plan and workflow template that was prepared during the preparation phase. See the detailed workflow for... Figure 5 :

[0133] Step 501: Create a task; Create a task through the command and dispatch platform. It can be understood that the command and dispatch platform is the front end, providing users with a visual interface for creating tasks.

[0134] Step 502: Copy the work plan workflow template; Since the work plan workflow template created in the preparation phase can be referenced by multiple tasks, it is necessary to ensure the independence of each task. Otherwise, modifying the measures and means of one workflow will affect all tasks referencing that workflow. Therefore, copying the work plan workflow template can isolate the work plan workflow template corresponding to that task from the work plan workflow template stored in the preparation phase and the work plan workflow template referenced by other tasks. When copying the work plan workflow template, you can copy the basic information of the work plan, the BPMN information of the work plan arrangement, and the measures and means of the work plan. If the measures and means in the plan already have matching value information, you can also copy the configuration information of the measures and means. Among them, the basic information of the work plan includes the work plan name, version number, status, creator, reviewer, review status, tags, description, and type. The measures and means of the work plan refer to the process node information stored in the preparation phase.

[0135] Step 503: Create an instantiated scheme; create a workflow instantiation table, add the basic information of the work scheme to the workflow instantiation table to realize the instantiation of the work scheme workflow template.

[0136] Step 504: Deploy the workflow; deploy the instantiated solution's BPMN information (business process diagram information) in the form of a file ending with .bpmn or .bpmn20.xml using the Camunda workflow engine tool. The Camunda workflow engine tool generates the corresponding deployment identifier.

[0137] Step 505: Update the instantiated scheme information; update the deployment identifier to the workflow instantiation table, and generate the work scheme instance identifier.

[0138] Step 506: Bind the task identifier to the work plan instance identifier.

[0139] This application embodiment references the work plan process template by copying the work plan process template information, so that subsequent changes to the work plan process template will not affect the execution of other tasks that reference the same template.

[0140] III. Activation Phase

[0141] The activation phase is divided into two sub-phases: the preprocessing phase and the runtime phase.

[0142] Figure 6 A schematic diagram of a preprocessing stage provided in an embodiment of this application is shown below. Figure 6 As shown, it includes:

[0143] Step 601: Receive the start request of the target task. The start request includes the task identifier corresponding to the target task.

[0144] Step 602: Obtain the work plan instance identifier that is bound to the task identifier; since the task identifier and the work plan instance identifier are bound, the work plan instance identifier can be obtained based on the task identifier.

[0145] Step 603: Obtain the deployment identifier from the corresponding work plan instance table based on the work plan instance identifier; during the referencing phase, the deployment identifier was updated in the work plan instance table. Therefore, the corresponding work plan instance table can be obtained through the work plan instance identifier, and then the deployment identifier can be obtained from the work plan instance table.

[0146] Step 604: Obtain the process definition identifier by calling the method to obtain the process definition based on the deployment identifier; and obtain the process definition identifier by calling the method to obtain the process definition in the Camunda process engine tool based on the deployment identifier.

[0147] Step 605: Run the corresponding instantiated template BPMN according to the process definition identifier to instantiate the workflow, generate the workflow instance identifier, and the task identifier of each task corresponding to the workflow instance.

[0148] Step 606: Bind the workflow instance identifier to the work plan instance identifier.

[0149] Figure 7 This application provides a flowchart illustrating a method for generating a collection of handle objects, as shown in the embodiments below. Figure 7 As shown, the method includes:

[0150] Step 701: Query the task list; based on the workflow instance identifier, query the task list corresponding to the corresponding workflow instance through the Camunda workflow engine. In a workflow, one stage process corresponds to one task. If a stage process includes multiple measures, then the stage process also has its corresponding stage task list. A sub-plan process also corresponds to one task, and the sub-plan process also has its corresponding sub-plan task list. If a workflow includes task A, task B, and task C, where task B is a stage task, containing tasks B1 and B2; and task C is a sub-plan task, containing tasks C1, C2, and C3, then the task list includes tasks A, B, and C.

[0151] Step 702: Determine the task type; when converting each task in the task list into a handle object, determine whether the task type is a normal type, a stage type, or a sub-plan type; if it is a normal type, proceed to step 703; if it is a stage type, proceed to step 704; if it is a sub-plan type, proceed to step 705.

[0152] Step 703: Create a collection of handle objects; convert ordinary type tasks into corresponding handle objects, and form a collection of handle objects, i.e., handleA, for all ordinary type tasks.

[0153] Step 704: Deploy the phase process; For tasks with a phase type, deploy the phase process. Specifically, run the BPMN corresponding to the phase through the Camunda workflow engine to deploy the phase process.

[0154] Step 705: Activate the process instance; Query the process definition table based on the unique identifier of the deployment process stored in the contingency plan instance, obtain the unique identifier of the process definition, and then call the Camunda run method to start the process and generate a process instance based on the defined unique identifier.

[0155] Step 706: Query the phase task list; the phase task list includes task B1 and task B2.

[0156] Step 707: Create a collection of handle objects; convert task B1 and task B2 into corresponding handle objects, thus forming a collection of handle objects. The collection of handle objects includes handle B1 and handle B2.

[0157] Step 708: Copy the sub-plan arrangement information; for tasks whose task type is a sub-plan, copy the arrangement information of the sub-plan process to reference the sub-plan process.

[0158] Step 709: Instantiate the sub-plan process; fill in the basic information of the sub-plan process into the sub-plan process instantiation table to realize the instantiation of the sub-plan process.

[0159] Step 710: Deploy the sub-plan process; deploy the BPMN information corresponding to the instantiated sub-plan process on the Camunda workflow engine tool.

[0160] Step 711: Activate the process instance; After completing the deployment of the sub-plan process, activate the sub-plan process instance.

[0161] Step 712: Query the sub-plan task list; the sub-plan task list includes task C1 and task C2.

[0162] Step 713: Create a collection of handle objects; convert task C1 and task C2 into corresponding handle objects, thus forming a collection of handle objects. The collection of handle objects includes handle C1 and handle C2.

[0163] Step 714: Merge and store the handle object collection; merge steps 703, 707 and 713 to obtain the total handle object collection. It can be understood that the generated handle object collection is handle A, handle B1, handle B2, handle C1 and handle C2.

[0164] Figure 8 This is a schematic diagram of the method flow for processing handle objects provided in an embodiment of this application, as shown below. Figure 8 As shown, it includes:

[0165] Step 801: Loop through the collection of handle objects; obtain one handle object from the collection of handle objects.

[0166] Step 802: Determine if it is a running node; Based on the task identifier and process instance identifier, call the Camunda workflow engine to determine whether the task corresponding to the handle object is a running process node. If so, proceed to step 803; otherwise, proceed to step 801.

[0167] Step 803: Obtain the measure / method instance; query the management resource module interface based on the measure / method instance ID and task ID corresponding to the handle object, and obtain the measure / method instance information through this interface. It can be understood that the instantiated measure / method is called a task, or a process node in a workflow.

[0168] Step 804: Determine if it is automatically executed; After obtaining the measure instance information, determine if the measure is an automatically executed type. If yes, proceed to step 805; otherwise, the processing of the handle object can be terminated. That is, during business processing, the completion interface should be called only after processing is complete. During this period, the handle object remains in a ready state, and its state is changed to completed after the completion interface is called. If the handle objects in the handle object collection are not fully processed, step 801 is re-executed. It is understood that automatically executed measures can include API-type measures.

[0169] Step 805: Based on global variables and API configuration information, call the method to perform business processing; request the method implementation module to perform business processing based on the parameters configured by the global configuration parameters and the method, and call the completion interface of the method if successful.

[0170] Step 806: Message notification; After processing all handle objects in the handle object collection, use the Kafka message queue to asynchronously notify the scheduling platform that the task has started.

[0171] This application embodiment deploys stage tasks for stage types, queries the stage task list, generates corresponding handle objects, and finally integrates the generated handle objects into the overall process. This enables the simultaneous execution of various stage tasks in a stage without using gateway judgment. Since there is no gateway node, the number of process nodes executed during process operation is reduced, thus improving the efficiency of process operation.

[0172] Based on the above embodiments, the method further includes:

[0173] Receive workflow change requests, which include the task node identifier to be changed and the change type;

[0174] If the task node to be changed, corresponding to the task node to be changed, is not yet started in the workflow instance, then the task to be changed in the workflow instance is modified according to the change type.

[0175] In practice, users can modify the workflow according to actual needs. When a change is required, a workflow change request is sent via electronic device. This request includes the task node identifier to be changed and the change type. The change type indicates the method of changing the task node identifier, such as adding a new workflow node after the task node identifier or deleting the workflow node corresponding to the task node identifier.

[0176] It should be noted that, in this embodiment of the application, when modifying a task node, the task node to be modified must not have started processing, that is, the task node's status must be "not started". For task nodes that are ready or completed, configuration modifications and node additions / deletions are not permitted.

[0177] If the workflow is changed, the activation phase will be re-executed at the task nodes of the workflow that need to be reconfigured, but previously run handle objects will not be re-executed.

[0178] This application embodiment allows for changes to tasks that have not yet started in the workflow, thereby meeting the user's change requirements without affecting the normal operation of the workflow.

[0179] Based on the above embodiments, the method further includes:

[0180] If an exception is received during the execution of a workflow instance, exception handling options are displayed for the user to choose how to handle the exception in the task. Exception handling options include restarting the task, skipping the task, and ending the workflow.

[0181] In the specific implementation process, the embodiments of this application also provide an anomaly compensation mechanism so that if an anomaly occurs during the operation of the workflow, there is a way to make the workflow continue to run or exit.

[0182] The specific method is as follows:

[0183] If an error occurs during workflow execution due to incorrect configuration information at a node or network issues, preventing the workflow from functioning properly, the workflow diagram will have an exception handling function with three selectable types:

[0184] 01. Restart the current node: Rerun the current measure instance node.

[0185] 2. Skip the current node: Set the current node to completed and start the next action node.

[0186] 3. End the current process: Directly end the current work plan process.

[0187] Understandably, this exception handling function can automatically pop up a selection box when an exception occurs, allowing the user to choose how to handle the exception.

[0188] In another embodiment, a default exception handling method can be pre-configured for each task node, and the exception handling method can be automatically executed when an exception is triggered.

[0189] This application provides exception handling options. When an exception occurs during the operation of the workflow, the user can select the corresponding exception handling method.

[0190] 0 Figure 9 This is a schematic diagram of a process operation device provided in an embodiment of this application. The device can...

[0191] This refers to modules, program segments, or code on electronic devices. It should be understood that this device is related to the above... Figure 3 The method implementation corresponds to this and can be executed. Figure 3 The various steps involved in the method embodiment, and the specific functions of the device, can be found in the description above. To avoid repetition, detailed descriptions are appropriately omitted here. The device...

[0192] The system includes: an identifier acquisition module 901, an instance acquisition module 902, and a process execution module 903, wherein: the identifier acquisition module 901 is used to acquire the workflow instance identifier of the process to be executed;

[0193] The instance acquisition module 902 is used to acquire the corresponding workflow instance according to the workflow instance identifier; wherein, the workflow instance includes a stage process, the stage process includes multiple measures and means, and the multiple measures and means can be executed simultaneously without gateway judgment when the corresponding stage process is invoked;

[0194] The process execution module 903 is used to run the workflow instance to execute the multiple measures and means.

[0195] Based on the above embodiments, the workflow example also includes a sub-plan workflow, which is generated by referencing a workflow scheme orchestrated by a third party.

[0196] Based on the above embodiments, the process execution module 903 is specifically used for:

[0197] Obtain the task list corresponding to the workflow instance. The task list includes multiple tasks, and the multiple tasks are processed by calling the measures and means corresponding to the stage process.

[0198] Generate a corresponding handle object for each task in the task list, and obtain a collection of handle objects corresponding to the task list;

[0199] The process executes multiple measures and methods in the workflow instance to process the handle objects in the handle object collection.

[0200] Based on the above embodiments, the process execution module 903 is specifically used for:

[0201] For each phase task in the phase process, deploy and enable the phase process corresponding to that phase task.

[0202] Query the list of stage tasks corresponding to the stage process, wherein the list of stage tasks includes the stage task information contained in the stage process;

[0203] Generate a corresponding handle object based on the task information for each stage in the task list.

[0204] Based on the above embodiments, the workflow example further includes a sub-plan workflow, which is generated by referencing a workflow scheme orchestrated by a third party; the task list includes sub-plan tasks; the workflow execution module 903 is specifically used for:

[0205] For a sub-plan task whose task type is a sub-plan, copy the sub-plan process template information corresponding to the sub-plan task and instantiate the sub-plan process;

[0206] Deploy and enable the business process diagram information corresponding to the instantiated sub-plan process;

[0207] Query the list of sub-contingency plan tasks corresponding to the sub-contingency plan process; wherein, the list of sub-contingency plan tasks includes sub-contingency plan task information contained in the sub-contingency plan process;

[0208] Generate a corresponding handle object for each sub-plan task in the sub-plan task list.

[0209] Based on the above embodiments, the process execution module 903 is specifically used for:

[0210] The handle objects in the handle object collection are called sequentially, and the running status of the handle object is determined according to the task identifier and the process instance identifier corresponding to the handle object.

[0211] Obtain the measure instance information of the task node whose running status is "running", and process the task node according to the measure instance information.

[0212] Based on the above embodiments, the device further includes a modification module for:

[0213] Receive a workflow change request, the workflow change request including the task node identifier to be changed and the change type;

[0214] If the task node to be changed corresponding to the task node identifier to be changed is not started in the workflow instance, then the task to be changed in the workflow instance is modified according to the change type.

[0215] Based on the above embodiments, the device further includes an exception handling module, used for:

[0216] If an exception is received during the execution of the workflow instance, exception handling options are displayed for the user to choose how to handle the exception in the task; the exception handling options include restarting the task, skipping the task, and ending the workflow.

[0217] Based on the above embodiments, the device further includes an arrangement module for:

[0218] Obtain the completed work plan workflow template, and generate template BPMN file information and workflow node information based on the work plan workflow template;

[0219] The template BPMN file information and the process node information are stored.

[0220] Based on the above embodiments, the device further includes a reference module, used for:

[0221] Copy the work plan process template information required for the target task. The work plan process template information includes basic workflow information, template BPMN information, and measures and means; and the work plan process template information is pre-configured.

[0222] Add the basic information of the workflow to the workflow instantiation table to instantiate the workflow template of the work plan and generate the instance identifier of the work plan.

[0223] The instantiated template BPMN information is deployed on the Camunda workflow engine tool, a deployment identifier is generated, and the deployment identifier is updated in the workflow instantiation table;

[0224] Bind the instance identifier of the work plan to the task identifier corresponding to the target task.

[0225] Based on the above embodiments, the device further includes a preprocessing module for:

[0226] Receive the start request of the target task, the start request including the task identifier corresponding to the target task;

[0227] Obtain the instance identifier of the work plan that is bound to the task identifier based on the task identifier;

[0228] The deployment identifier is obtained from the corresponding work plan instance table based on the work plan instance identifier;

[0229] The process definition identifier is obtained by calling the method for obtaining the process definition based on the deployment identifier;

[0230] Run the corresponding instantiated template BPMN according to the process definition identifier to instantiate the workflow, generate the workflow instance identifier, and the task identifier of each task corresponding to the workflow instance.

[0231] Bind the workflow instance identifier to the work plan instance identifier.

[0232] Figure 10 This is a schematic diagram of the physical structure of the electronic device provided in the embodiments of this application, such as... Figure 10 As shown, the electronic device includes: a processor 1001, a memory 1002, and a bus 1003; wherein,

[0233] The processor 1001 and the memory 1002 communicate with each other through the bus 1003;

[0234] The processor 1001 is used to call program instructions in the memory 1002 to execute the methods provided in the above method embodiments, such as: obtaining a workflow instance identifier of the process to be run; obtaining a corresponding workflow instance according to the workflow instance identifier; wherein, the workflow instance includes a stage process, the stage process includes multiple measures and means, the multiple measures and means can be executed simultaneously without gateway judgment when the corresponding stage process is called; running the workflow instance to execute the multiple measures and means.

[0235] The processor 1001 can be an integrated circuit chip with signal processing capabilities. The processor 1001 can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it can also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or any conventional processor.

[0236] The memory 1002 may include, but is not limited to, random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), etc.

[0237] This embodiment discloses a computer program product, which includes a computer program stored on a non-transitory computer-readable storage medium. The computer program includes program instructions, and when the program instructions are executed by a computer, the computer can perform the methods provided in the above-described method embodiments, such as:

[0238] Obtain the workflow instance identifier of the process to be run; obtain the corresponding workflow instance based on the workflow instance identifier; wherein, the workflow instance includes a stage process, the stage process includes multiple measures and means, the multiple measures and means can be executed simultaneously without gateway judgment when the corresponding stage process is invoked; run the workflow instance to execute the multiple measures and means.

[0239] This embodiment provides a non-transitory computer-readable storage medium that stores computer instructions that cause the computer to execute the methods provided in the above-described method embodiments, including, for example:

[0240] Obtain the workflow instance identifier of the process to be run; obtain the corresponding workflow instance based on the workflow instance identifier; wherein, the workflow instance includes a stage process, the stage process includes multiple measures and means, the multiple measures and means can be executed simultaneously without gateway judgment when the corresponding stage process is invoked; run the workflow instance to execute the multiple measures and means.

[0241] In the embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. The apparatus embodiments described above are merely illustrative. For example, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. Furthermore, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Additionally, the displayed or discussed mutual couplings, direct couplings, or communication connections may be through some communication interfaces; indirect couplings or communication connections between devices or units may be electrical, mechanical, or other forms.

[0242] Furthermore, the units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0243] Furthermore, the functional modules in the various embodiments of this application can be integrated together to form an independent part, or each module can exist independently, or two or more modules can be integrated to form an independent part.

[0244] In this document, relational terms such as first and second are used only to distinguish one entity or operation from another entity or operation, without necessarily requiring or implying any such actual relationship or order between these entities or operations.

[0245] The above description is merely an embodiment of this application and is not intended to limit the scope of protection of this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of protection of this application.< / bpmn:xxx>

Claims

1. A process operation method, characterized in that, include: Obtain the workflow instance identifier of the process to be run; Obtain the corresponding workflow instance based on the workflow instance identifier; wherein, the workflow instance includes a stage process, the stage process includes multiple measures and means, and the multiple measures and means can be executed simultaneously without gateway judgment when the corresponding stage process is invoked; Run the workflow instance to execute the multiple measures and means; The execution of the workflow instance includes: Obtain the task list corresponding to the workflow instance. The task list includes multiple tasks, and the multiple tasks are processed by calling the measures and means corresponding to the stage process. Generate a corresponding handle object for each task in the task list, and obtain a set of handle objects corresponding to the task list; Run multiple measures and methods in the workflow instance to process the handle objects in the handle object collection; The processing of the handle objects in the handle object collection includes: The handle objects in the handle object collection are called sequentially, and the running status of the handle object is determined according to the task identifier and the process instance identifier corresponding to the handle object. Obtain the measure instance information of the task node whose running status is "running", and process the task node according to the measure instance information.

2. The method according to claim 1, characterized in that, The workflow example also includes sub-plan workflows, which are generated by referencing workflow schemes orchestrated by a third party.

3. The method according to claim 1, characterized in that, The step of generating a handle object for each task in the task list includes: For the phase tasks corresponding to the phase process, deploy and enable the phase process corresponding to the phase tasks; Query the list of stage tasks corresponding to the stage process, wherein the list of stage tasks includes the stage task information contained in the stage process; Generate a corresponding handle object based on the task information for each stage in the task list.

4. The method according to claim 1, characterized in that, The workflow instance also includes sub-plan workflows, which are generated by referencing a workflow scheme orchestrated by a third party; the task list includes sub-plan tasks; generating a handle object for each task in the task list includes: For the sub-plan task, copy the sub-plan process template information corresponding to the sub-plan task and instantiate the sub-plan process; Deploy and enable the business process diagram information corresponding to the instantiated sub-plan process; Query the list of sub-contingency plan tasks corresponding to the sub-contingency plan process; wherein, the list of sub-contingency plan tasks includes sub-contingency plan task information contained in the sub-contingency plan process; Generate a corresponding handle object based on the information of each sub-plan task in the sub-plan task list.

5. The method according to claim 1, characterized in that, The method further includes: Receive a workflow change request, the workflow change request including the task node identifier to be changed and the change type; If the task node to be changed corresponding to the task node identifier to be changed is not started in the workflow instance, then the task to be changed in the workflow instance is modified according to the change type.

6. The method according to claim 1, characterized in that, The method further includes: If an exception is received during the execution of the workflow instance, exception handling options are displayed for the user to choose how to handle the exception in the task; the exception handling options include restarting the task, skipping the task, and ending the workflow.

7. The method according to any one of claims 1-6, characterized in that, The method further includes: Obtain the completed work plan workflow template, and generate template BPMN file information and workflow node information based on the work plan workflow template; The template BPMN file information and the process node information are stored.

8. The method according to any one of claims 1-6, characterized in that, The method further includes: Copy the work plan process template information required for the process to be run. The work plan process template information includes basic workflow information, template BPMN information, and measures and means; and the work plan process template information is pre-configured. Add the basic information of the workflow to the workflow instantiation table to instantiate the workflow template of the work plan and generate a work plan instance identifier. The instantiated template BPMN information is deployed on the Camunda workflow engine tool, a deployment identifier is generated, and the deployment identifier is updated in the workflow instantiation table; The instance identifier of the work plan is bound to the task identifier of the target task corresponding to the process to be run.

9. The method according to claim 8, characterized in that, The method further includes: Receive the start request of the target task, the start request including the task identifier corresponding to the target task; Obtain the instance identifier of the work plan that is bound to the task identifier based on the task identifier; The deployment identifier is obtained from the corresponding work plan instance table based on the work plan instance identifier; Obtain the process definition identifier based on the deployment identifier; Run the corresponding instantiated template BPMN according to the process definition identifier to instantiate the workflow, generate the workflow instance identifier, and the task identifier of each task corresponding to the workflow instance. Bind the workflow instance identifier to the work plan instance identifier.

10. A process operation device, characterized in that, include: The identifier acquisition module is used to obtain the workflow instance identifier of the process to be run; The instance acquisition module is used to acquire the corresponding workflow instance based on the workflow instance identifier; wherein, the workflow instance includes a stage process, the stage process includes multiple measures and means, and the multiple measures and means can be executed simultaneously without gateway judgment when the corresponding stage process is invoked; The process execution module is used to run the workflow instance to execute the multiple measures and means; The process execution module is specifically used for: Obtain the task list corresponding to the workflow instance. The task list includes multiple tasks, and the multiple tasks are processed by calling the measures and means corresponding to the stage process. Generate a corresponding handle object for each task in the task list, and obtain a set of handle objects corresponding to the task list; Run multiple measures and methods in the workflow instance to process the handle objects in the handle object collection; The processing of the handle objects in the handle object collection includes: The handle objects in the handle object collection are called sequentially, and the running status of the handle object is determined according to the task identifier and the process instance identifier corresponding to the handle object. Obtain the measure instance information of the task node whose running status is "running", and process the task node according to the measure instance information.

11. An electronic device, characterized in that, include: Processor, memory, and bus, among which, The processor and the memory communicate with each other via the bus; The memory stores program instructions that can be executed by the processor, and the processor can execute the method as described in any one of claims 1-9 by calling the program instructions.

12. A non-transitory computer-readable storage medium, characterized in that, The non-transitory computer-readable storage medium stores computer instructions that, when executed by a computer, cause the computer to perform the method as described in any one of claims 1-9.

Images