Workflow engine methods, systems, devices, and media based on low-code platforms

By leveraging the visual configuration and multi-node execution of a low-code platform, the deployment complexity and stability issues of existing workflow engine systems are resolved, achieving efficient data processing and concurrency capabilities, making it suitable for enterprise process management and approval functions.

CN116069311BActive Publication Date: 2026-11-10SHANGHAI WANQI MINGDAO SOFTWARE CO LTD
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202310062240.3
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2023-01-16
Publication Date
2026-11-10
Estimated Expiration
2043-01-16

AI Technical Summary

Technical Problem

Existing workflow engine systems are complex to deploy, costly, difficult to scale, have a single triggering method, cannot handle large volumes of concurrent requests, and have poor system stability.

Method used

Employing a low-code platform, the flowchart can be configured through a visual web interface, supporting multiple triggering methods and node configurations to achieve visual design and execution of processes, including nodes such as data processing, notification, building, developer and organizational collaboration, supporting sequential and concurrent execution, and saving execution logs.

Benefits of technology

It achieves data automation on a low-code platform, improves update speed and security under large data volumes, enhances batch processing capabilities and system concurrency, and supports enterprise approval functions.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN116069311B_ABST
    Figure CN116069311B_ABST
Patent Text Reader

Abstract

This disclosure relates to a workflow engine method, system, device, and medium based on a low-code platform. The method includes the following steps: configuring a flowchart for workflow execution through a visual web interface, including configuring the workflow triggering method and configuring the corresponding execution nodes; after the corresponding execution nodes are configured, publishing the workflow, receiving instructions to trigger the workflow, and executing the workflow according to the received instructions; after the workflow is executed, saving the workflow execution log, which supports filtering by time and status. This disclosure achieves data automation on the low-code platform, diversifies triggering methods, enhances batch data processing capabilities, and improves system concurrency and operational stability.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This disclosure relates to the field of workflow engines, and more specifically to a workflow engine method, system, device, and medium based on a low-code platform. Background Technology

[0002] Traditional workflows mostly integrate open-source frameworks such as Activity and Flowable. These frameworks provide complete workflow services, but their configuration is complex, and their scalability is poor. Modifying core tables can cause many problems, placing high demands on administrators. Existing workflow systems all require a corresponding hardware environment, which needs to be purchased, increasing additional costs. Most existing workflows support adding tables for triggering, and sub-processes can only be executed one at a time. Furthermore, their product efficiency and concurrency handling capabilities are somewhat lacking, making them unable to handle millions of data points, or even tens of millions of business requests per day.

[0003] The existing technical solution (or the closest technical solution) currently has the following disadvantages / deficiencies:

[0004] 1. Complex deployment, high cost, and difficult to scale;

[0005] 2. The triggering method is singular, and it does not have the ability to process sub-processes in batches;

[0006] 3. It cannot handle large volumes of concurrent business, resulting in poor system stability. Summary of the Invention

[0007] This disclosure provides a workflow engine method, system, device, and medium based on a low-code platform, which can solve the problems of existing workflow engine systems, such as complex deployment, high cost, difficulty in expansion, single triggering method, inability to handle large-volume concurrent processing, and poor system stability. To solve the above technical problems, this disclosure provides the following technical solutions:

[0008] As one aspect of this disclosure, a workflow engine method based on a low-code platform is provided. It includes the following steps:

[0009] Configure the workflow execution flowchart through a visual web interface, including configuring the workflow triggering method and configuring the corresponding execution nodes;

[0010] After the corresponding execution node is configured, the process is published, instructions to trigger the workflow are received, and the process is executed according to the received instructions.

[0011] After the process is completed, the process execution log is saved.

[0012] Optionally, the triggering method includes one or more of the following: triggering for adding, modifying, or deleting data, triggering by a timed event, triggering for retrieving data at a specified time, triggering manually, triggering via webhook, or triggering by a human event.

[0013] Optionally, the node may include one or more of the following: data processing, delegation, notification, building, developer, or organization / department / collaboration.

[0014] Optionally, the release process includes the following steps: verifying the availability of the flowchart; if the verification passes, the release is successful and a release version is generated; otherwise, the release fails and the reason for the release failure is displayed.

[0015] Optionally, after receiving the instruction to trigger the workflow, the following steps are also included: determining whether the trigger conditions are met based on the trigger conditions; if the conditions are not met, the process ends.

[0016] Optionally, after the triggering conditions of the execution process are met, the following steps are also included: execute the process according to the nodes configured in the flowchart, determine whether it is the end node, if not, continue execution; if so, the process execution ends.

[0017] Optionally, in the process of executing the configuration node, the sub-process supports one or more of the following execution methods: sequential execution or concurrent execution.

[0018] As one aspect of this disclosure, a workflow engine system based on a low-code platform is provided, comprising:

[0019] The configuration process module allows you to configure the workflow execution flowchart through a visual web interface, including configuring the workflow triggering method and configuring the corresponding execution nodes;

[0020] The execution process module publishes the process after the corresponding execution node is configured; it receives instructions to trigger the workflow and executes the process according to the received instructions.

[0021] The execution log module saves the execution log of the process after it is completed.

[0022] As another aspect of this disclosure, an electronic device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the workflow engine method based on a low-code platform described above.

[0023] As another aspect of the present disclosure, a computer-readable storage medium is provided having a computer program stored thereon, characterized in that the program, when executed by a processor, implements the above-described workflow engine method based on a low-code platform.

[0024] Compared to the prior art, the beneficial effects of this disclosure are as follows:

[0025] 1. It achieves data automation on a low-code platform, which enables fast updates, high security, and easier management when dealing with large amounts of data.

[0026] 2. Enhanced batch processing capabilities improve system concurrency; sequential execution is also an option.

[0027] 3. Unified process design, process modeling, and process monitoring can effectively solve the approval functions of some enterprises. Attached Figure Description

[0028] Figure 1 This is a flowchart of the workflow engine method based on a low-code platform in Example 1;

[0029] Figure 2 This is a flowchart of the workflow execution process based on the low-code platform in Example 1;

[0030] Figure 3 This is a flowchart illustrating the cyclic triggering of processes A, B, and C in Example 1;

[0031] Figure 4 This is a normal triggering flowchart for processes A, B, and C in Example 1;

[0032] Figure 5 This is a schematic block diagram of the workflow engine system of the low-code platform in Example 2. Detailed Implementation

[0033] Various exemplary embodiments, features, and aspects of this disclosure will now be described in detail with reference to the accompanying drawings. The same reference numerals in the drawings denote elements that have the same or similar functions. Although various aspects of the embodiments are shown in the drawings, they are not necessarily drawn to scale unless specifically indicated otherwise.

[0034] The term “exemplary” as used herein means “serving as an example, embodiment, or illustration.” Any embodiment illustrated herein as “exemplary” is not necessarily to be construed as superior to or better than other embodiments.

[0035] In this document, 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 three cases: A alone, A and B simultaneously, and B alone. Furthermore, the term "at least one" in this document means any combination of at least two of any one or more elements. For example, including at least one of A, B, and C can mean including any one or more elements selected from the set consisting of A, B, and C.

[0036] Furthermore, to better illustrate this disclosure, numerous specific details are set forth in the following detailed description. Those skilled in the art will understand that this disclosure can be practiced without certain specific details. In some instances, methods, means, components, and circuits well known to those skilled in the art have not been described in detail in order to highlight the main points of this disclosure.

[0037] It is understood that the various method embodiments mentioned above in this disclosure can be combined with each other to form combined embodiments without violating the principle and logic. Due to space limitations, this disclosure will not elaborate further.

[0038] In addition, this disclosure also provides a workflow engine method, system, device and medium based on a low-code platform. All of the above can be used to implement any of the workflow engine methods based on a low-code platform provided in this disclosure. The corresponding technical solutions and descriptions are described in the corresponding records in the method section and will not be repeated here.

[0039] The execution entity of a workflow engine method based on a low-code platform can be a computer or other device capable of implementing a low-code platform-based workflow engine. For example, the method can be executed by a terminal device, server, or other processing device. The terminal device can be a user equipment (UE), mobile device, user terminal, terminal, cellular phone, cordless phone, personal digital assistant (PDA), handheld device, computing device, in-vehicle device, wearable device, etc. In some possible implementations, the low-code platform-based workflow engine method can be implemented by the processor calling computer-readable instructions stored in memory.

[0040] Example 1

[0041] This embodiment provides a workflow engine method based on a low-code platform, such as... Figure 1 As shown, it includes the following steps:

[0042] S10. Configure the workflow execution flowchart through a visual web interface, including configuring the workflow triggering method and configuring the corresponding execution nodes;

[0043] S20. After the corresponding execution node is configured, the process is published, the instruction to trigger the workflow is received, and the process is executed according to the received instruction.

[0044] S30. After the process is completed, save the process execution log.

[0045] Based on the above steps, this embodiment of the disclosure constructs a workflow engine method based on a low-code platform. A flowchart for process execution is configured through a visual web interface. After the corresponding execution nodes are configured, the process is published, achieving data automation on the low-code platform. The method receives instructions to trigger the workflow and executes the process according to the received instructions. The diversity of triggering methods enhances the batch processing capability of data and improves the system's concurrency. After the process is executed, the execution log of the process is saved, and the execution log supports filtering by time and status.

[0046] The steps of each embodiment of this disclosure will be described in detail below.

[0047] S10. Configure the workflow execution flowchart through a visual web interface, including configuring the workflow triggering method and configuring the corresponding execution nodes;

[0048] The triggering methods include one or more of the following: triggering for adding, modifying, or deleting data, triggering on a timer, triggering for retrieving data at a specified time, manual triggering, webhook triggering, or triggering for personnel events.

[0049] Specifically, the timed trigger refers to execution according to the configured specified time; the specified time data lookup trigger refers to execution after the specified time has arrived, by filtering out data that meets the conditions; the manual trigger refers to execution by manually clicking a button; the webhook trigger refers to execution after receiving an HTTP request; and the personnel event trigger refers to execution after changes in platform personnel onboarding or offboarding.

[0050] The nodes include one or more of the following: data processing, delegation, notification, construction, developer, or organization / department / collaboration.

[0051] The data processing includes: adding nodes, which are used to add data and support triggering processes; modifying nodes, which are used to modify data and support triggering processes; and deleting data, which are used to delete data and support triggering processes.

[0052] The delegated tasks include: approval, which initiates an approval message to a designated approver; filling, which initiates a fill message to a designated filler; and copying nodes, which send an internal message with data records to a designated copyer.

[0053] The notifications include: in-platform messages, which send in-platform messages to the low-code platform according to the configured message content; SMS messages, which send SMS messages to a specified mobile phone number according to the configured SMS template content; email messages, which send emails to a specified email address according to the configured email template content; and WeChat service account messages, which send messages to a specified WeChat account according to the configured service account template content.

[0054] The construction includes: branches, which determine the direction of the process based on configured conditions; delays, which wait for a period of time before execution; calculations, which perform calculations on a formula and record the results for use by other nodes; and sub-process nodes, which enter a sub-process and execute the relevant node configurations of the sub-process.

[0055] The developers include: sending API requests, sending an HTTP request and recording the return value of the request; executing code blocks and recording the return result of the code execution; and parsing JSON data, renaming JSON data and filtering out data that does not meet the conditions.

[0056] The organizations, departments, and collaborations include: acquiring personnel, acquiring one or more personnel based on conditions; and acquiring departments, acquiring one or more departments based on conditions.

[0057] The flowchart for configuring the execution process through a visual web interface enables data automation on the low-code platform. When dealing with large amounts of data, it offers fast update speeds, high security, and easier management.

[0058] S20. After the corresponding execution node is configured, the process is published, the instruction to trigger the workflow is received, and the process is executed according to the received instruction.

[0059] S201. The release process includes the following steps: verify the availability of the flowchart. If the verification is successful, the release is successful and a release version is generated; otherwise, the release fails and the reason for the release failure is displayed.

[0060] In a preferred embodiment, a single workflow has one edit version and one or more release versions. The edit version is used to configure the process. After all configurations are complete, and the usability of the flowchart is verified, one or more release versions can be generated. The release versions are used for executing the process and restoring historical versions. Editing does not affect processes that have already been executed.

[0061] S202. After receiving the instruction to trigger the workflow, the following steps are also included: determining whether the trigger conditions are met based on the trigger conditions; if the conditions are not met, the process ends. For example... Figure 2 As shown.

[0062] S203. After the triggering conditions of the execution process are met, the following steps are also included: execute the process according to the nodes configured in the flowchart, determine whether it is the end node, if not, continue execution; if so, the process execution ends.

[0063] In the process of executing the configuration node, the sub-processes support one or more of the following execution methods: sequential execution or concurrent execution.

[0064] Sequential execution means waiting for the sub-process to complete before continuing execution, while concurrent execution means executing the sub-process while continuing to execute the nodes following it. The process supports batch processing, enhancing data batch processing capabilities and improving system concurrency and operational stability.

[0065] During the execution process, operations such as adding, updating, and deleting data can trigger a new workflow, which may lead to the looping of the process, causing the system process to keep running and unable to end, forming an infinite loop.

[0066] For example, for the three processes A, B, and C, such as Figure 3 , Figure 4 As shown, when process A is triggered, it adds a new data entry, triggering process B. After process B is triggered, it adds a new data entry, triggering process C. After process C is triggered, it adds a new data entry, triggering process A. This leads to a loop: A->B->C->A->B->CA... This creates an infinite loop, which is not allowed by the system. Therefore, the correct steps are as follows:

[0067] 2.1A was triggered after the condition was met, and a new data entry for B was added;

[0068] 2.2B was triggered when the condition was met, and a new data entry for C was added;

[0069] 2.3C was triggered when the condition was met, and a new data entry for A was added;

[0070] 2.4 Once the entire process is complete, process A will not be triggered again even if the conditions are met.

[0071] S30. After the process is completed, save the process execution log.

[0072] The execution log supports filtering by time and status. The workflow engine method based on the low-code platform mainly includes two parts: workflow process storage and workflow execution. Workflow storage is used to save workflow configurations and workflow execution logs; it stores node configurations such as workflow trigger conditions, action execution, data retrieval, and notification messages; and it stores workflow execution logs. Workflow execution mainly involves updating low-code platform data, calling external interfaces, sending emails and SMS messages, initiating approvals, and filling out forms according to the configured flowchart.

[0073] Example 2

[0074] As another aspect of this disclosure, a workflow engine system 100 based on a low-code platform is also provided, such as... Figure 5 As shown, it includes the following steps:

[0075] Configuration Process Module 1 allows you to configure the workflow execution flowchart through a visual web interface, including configuring the workflow triggering method and configuring the corresponding execution nodes;

[0076] Execution process module 2, after the corresponding execution node is configured, publishes the process; receives instructions to trigger the workflow, and executes the process according to the received instructions;

[0077] Execution log module 3 saves the execution log of the process after the process is completed.

[0078] Based on the above modules, this embodiment of the disclosure constructs a workflow engine method based on a low-code platform. A flowchart for process execution is configured through a visual web interface. After the corresponding execution nodes are configured, the process is published, achieving data automation on the low-code platform. The system receives instructions to trigger the workflow and executes the process according to the received instructions. The diversity of triggering methods enhances the batch processing capability of data and improves the system's concurrency. After the process execution is completed, the process execution log is saved. The execution log supports filtering by time and status, realizing a workflow engine system 100 based on a low-code platform.

[0079] The various modules of the embodiments of this disclosure will be described in detail below.

[0080] Configuration Process Module 1 allows you to configure the workflow execution flowchart through a visual web interface, including configuring the workflow triggering method and configuring the corresponding execution nodes.

[0081] The triggering methods include one or more of the following: triggering for adding, modifying, or deleting data, triggering on a timer, triggering for retrieving data at a specified time, manual triggering, webhook triggering, or triggering for personnel events.

[0082] Specifically, the timed trigger refers to execution according to the configured specified time; the specified time data lookup trigger refers to execution after the specified time has arrived, by filtering out data that meets the conditions; the manual trigger refers to execution by manually clicking a button; the webhook trigger refers to execution after receiving an HTTP request; and the personnel event trigger refers to execution after changes in platform personnel onboarding or offboarding.

[0083] The nodes include one or more of the following: data processing, delegation, notification, construction, developer, or organization / department / collaboration.

[0084] The data processing includes: adding nodes, which are used to add data and support triggering processes; modifying nodes, which are used to modify data and support triggering processes; and deleting data, which are used to delete data and support triggering processes.

[0085] The delegated tasks include: approval, which initiates an approval message to a designated approver; filling, which initiates a fill message to a designated filler; and copying nodes, which send an internal message with data records to a designated copyer.

[0086] The notifications include: in-platform messages, which send in-platform messages to the low-code platform according to the configured message content; SMS messages, which send SMS messages to a specified mobile phone number according to the configured SMS template content; email messages, which send emails to a specified email address according to the configured email template content; and WeChat service account messages, which send messages to a specified WeChat account according to the configured service account template content.

[0087] The construction includes: branches, which determine the direction of the process based on configured conditions; delays, which wait for a period of time before execution; calculations, which perform calculations on a formula and record the results for use by other nodes; and sub-process nodes, which enter a sub-process and execute the relevant node configurations of the sub-process.

[0088] The developers include: sending API requests, sending an HTTP request and recording the return value of the request; executing code blocks and recording the return result of the code execution; and parsing JSON data, renaming JSON data and filtering out data that does not meet the conditions.

[0089] The organizations, departments, and collaborations include: acquiring personnel, acquiring one or more personnel based on conditions; and acquiring departments, acquiring one or more departments based on conditions.

[0090] The flowchart for configuring the execution process through a visual web interface enables data automation on the low-code platform. When dealing with large amounts of data, it offers fast update speeds, high security, and easier management.

[0091] Execution process module 2, after the corresponding execution node is configured, publishes the process, receives instructions to trigger the workflow, and executes the process according to the received instructions.

[0092] S201. The release process includes the following steps: verify the availability of the flowchart. If the verification is successful, the release is successful and a release version is generated; otherwise, the release fails and the reason for the release failure is displayed.

[0093] In a preferred embodiment, a single workflow has one edit version and one or more release versions. The edit version is used to configure the process. After all configurations are complete, and the usability of the flowchart is verified, one or more release versions can be generated. The release versions are used for executing the process and restoring historical versions. Editing does not affect processes that have already been executed.

[0094] S202. After receiving the instruction to trigger the workflow, the following steps are also included: determining whether the trigger conditions are met based on the trigger conditions; if the conditions are not met, the process ends. For example... Figure 2 As shown.

[0095] S203. After the triggering conditions of the execution process are met, the following steps are also included: execute the process according to the nodes configured in the flowchart, determine whether it is the end node, if not, continue execution; if so, the process execution ends.

[0096] In the process of executing the configuration node, the sub-processes support one or more of the following execution methods: sequential execution or concurrent execution.

[0097] Sequential execution means waiting for the sub-process to complete before continuing execution, while concurrent execution means executing the sub-process while continuing to execute the nodes following it. The process supports batch processing, enhancing data batch processing capabilities and improving system concurrency and operational stability.

[0098] During the execution process, operations such as adding, updating, and deleting data can trigger a new workflow, which may lead to the looping of the process, causing the system process to keep running and unable to end, forming an infinite loop.

[0099] For example, for the three processes A, B, and C, such as Figure 3 , Figure 4 As shown, when process A is triggered, it adds a new data entry, triggering process B. After process B is triggered, it adds a new data entry, triggering process C. After process C is triggered, it adds a new data entry, triggering process A. This leads to a loop: A->B->C->A->B->CA... This creates an infinite loop, which is not allowed by the system. Therefore, the correct steps are as follows:

[0100] 2.1A was triggered after the condition was met, and a new data entry for B was added;

[0101] 2.2B was triggered when the condition was met, and a new data entry for C was added;

[0102] 2.3C was triggered when the condition was met, and a new data entry for A was added;

[0103] 2.4 Once the entire process is complete, process A will not be triggered again even if the conditions are met.

[0104] Execution log module 3 saves the execution log of the process after the process is completed. The execution log supports filtering by time and status.

[0105] The workflow engine method based on the low-code platform mainly includes two parts: workflow process storage and workflow execution. Workflow storage is used to save the workflow configuration and workflow execution logs; it stores the node configurations such as workflow trigger conditions, action execution, data retrieval, and notification messages; and it stores the workflow execution logs. Workflow execution mainly involves updating the low-code platform's data, calling external interfaces, sending emails and SMS messages, initiating approvals, and filling out forms according to the configured flowchart.

[0106] In some embodiments, the workflow engine system 100 described above operates in the following manner:

[0107] S1: Run the configuration process module 1. Configure the workflow execution flowchart through a visual web interface, including configuring the workflow triggering method and the corresponding execution nodes;

[0108] S2: Run execution process module 2. After the corresponding execution node is configured, publish the process, receive instructions to trigger the workflow, and execute the process according to the received instructions;

[0109] S3: Run execution log module 3. After the process is completed, save the process execution log. The execution log supports filtering by time and status.

[0110] Based on the description of the above embodiments, it can be seen that the embodiments of this disclosure can achieve the following technical effects:

[0111] 1) By configuring the process flow through a visual web interface, data automation of the low-code platform is achieved. When the data volume is large, the update speed is fast, the security is high, and the management is more convenient.

[0112] 2) The execution process supports batch processing, which enhances the batch processing capability of data and improves the concurrency of the system.

[0113] 3) Unified process design, process modeling, and process monitoring can effectively solve the approval functions of some enterprises.

[0114] Example 3

[0115] An electronic device includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the workflow engine method based on a low-code platform as described in Embodiment 1.

[0116] Embodiment 3 of this disclosure is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of this disclosure.

[0117] Electronic devices can take the form of general-purpose computing devices, such as server devices. Components of an electronic device may include, but are not limited to: at least one processor, at least one memory, and buses connecting different system components (including memory and processor).

[0118] The bus includes a data bus, an address bus, and a control bus.

[0119] The memory may include volatile memory, such as random access memory (RAM) and / or cache memory, and may further include read-only memory (ROM).

[0120] The memory may also include program tools having a set (at least one) of program modules, including but not limited to: an operating system, one or more application programs, other program modules, and program data, each or some combination of these examples may include an implementation of a network environment.

[0121] The processor performs various functional applications and data processing by running computer programs stored in memory.

[0122] Electronic devices can also communicate with one or more external devices (such as keyboards, pointing devices, etc.). This communication can be achieved through input / output (I / O) interfaces. Furthermore, electronic devices can communicate with one or more networks (such as local area networks (LANs), wide area networks (WANs), and / or public networks, such as the Internet) via network adapters. The network adapter communicates with other modules of the electronic device via a bus. It should be understood that, although not shown in the figures, other hardware and / or software modules can be used in conjunction with the electronic device, including but not limited to: microcode, device drivers, redundant processors, external disk drive arrays, RAID (disk array) systems, tape drives, and data backup storage systems.

[0123] It should be noted that although several units / modules or sub-units / modules of the electronic device have been mentioned in the detailed description above, this division is merely exemplary and not mandatory. In fact, according to the embodiments of this application, the features and functions of two or more units / modules described above can be embodied in one unit / module. Conversely, the features and functions of one unit / module described above can be further divided and embodied by multiple units / modules.

[0124] Example 4

[0125] A computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps of the workflow engine method based on a low-code platform in Embodiment 1.

[0126] The readable storage medium may be more specifically adopted, including but not limited to: portable disk, hard disk, random access memory, read-only memory, erasable programmable read-only memory, optical storage device, magnetic storage device, or any suitable combination thereof.

[0127] In a possible implementation, this disclosure can also be implemented as a program product comprising program code that, when the program product is run on a terminal device, causes the terminal device to perform the steps of implementing the workflow engine method based on a low-code platform as described in Embodiment 1.

[0128] The program code for executing this disclosure can be written in any combination of one or more programming languages, and the program code can be executed entirely on a user device, partially on a user device, as a stand-alone software package, partially on a user device and partially on a remote device, or entirely on a remote device.

[0129] Although embodiments of the present disclosure have been shown and described, it will be understood by those skilled in the art that various changes, modifications, substitutions and alterations can be made to these embodiments without departing from the principles and spirit of the present disclosure, the scope of which is defined by the appended claims and their equivalents.

Claims

1. A workflow engine method based on a low-code platform, characterized in that, Includes the following steps: The workflow execution flowchart is configured through a visual web interface, including configuring the triggering method and the corresponding execution node. The triggering method includes at least one of the following: adding data trigger, modifying data trigger, deleting data trigger, timed trigger, retrieving data at a specified time trigger, manual trigger, webhook trigger, and personnel event trigger. The node includes at least one of the following: data processing node, task node, notification node, build node, developer node, and organization / department / collaboration node. The data processing node is used to add, modify, or delete data. The configuration corresponds to the execution nodes, including the node configurations for storing workflow trigger conditions, action execution, data retrieval, and notification messages; After the corresponding execution node configuration is completed, the process is released; the release process includes: verifying the availability of the flowchart; if the verification passes, the release is successful and a release version is generated; otherwise, the release fails and the reason for the process release failure is displayed. The same workflow has one edit version and one or more release versions. The edit version is used to configure the process. After all configurations are completed, one or more release versions are generated by verifying the availability of the flowchart. The release version is used to execute the process and restore historical versions. Editing does not affect processes that have already been executed. Receive the instruction to trigger the workflow, and determine whether the trigger conditions are met. If the trigger conditions are not met, the process ends. If the trigger conditions are met, the process is executed according to the nodes configured in the flowchart. During the execution process, after the data processing node performs addition, modification or deletion operations on the data, if the data after the operation meets the triggering conditions of another workflow, the other workflow is triggered, thereby forming a workflow triggering chain; in the triggering chain, when the data generated by the subsequently triggered workflow meets the triggering conditions of the workflow that has already been triggered in the triggering chain again, the workflow that has already been triggered will no longer be triggered, and the entire process ends. After the process is completed, the process execution log is saved, and the execution log supports filtering by time and status.

2. The workflow engine method based on a low-code platform as described in claim 1, characterized in that, The node execution process configured according to the flowchart includes: determining whether it is the end node; if not, continuing execution; if so, the process execution ends.

3. The workflow engine method based on a low-code platform as described in claim 1, characterized in that, The triggering chain includes: after the first workflow is triggered, the second workflow is triggered by the data added by the data processing node; after the second workflow is triggered, the third workflow is triggered by the data added by the data processing node; after the third workflow is triggered, the data added by the data processing node meets the triggering conditions of the first workflow, at which point the first workflow is no longer triggered, and the entire process ends.

4. The workflow engine method based on a low-code platform as described in any one of claims 1 to 3, characterized in that, The construction node includes a sub-process node, which is used to enter a sub-process and execute the relevant node configuration of the sub-process; the execution mode of the sub-process includes at least one of sequential execution and concurrent execution, wherein sequential execution is to wait for the sub-process to be completed before continuing execution, and concurrent execution is to execute the nodes after the sub-process while executing the sub-process.

5. A workflow engine system based on a low-code platform, which executes the workflow engine method based on a low-code platform as described in any one of claims 1 to 4, characterized in that, include: The configuration process module is used to configure the workflow execution flowchart through a visual web interface, including configuring the workflow triggering method and configuring the corresponding execution nodes; The execution process module is used to publish the process after the corresponding execution node is configured. Before publishing, it verifies the availability of the flowchart and generates a release version. Receive instructions to trigger a workflow, determine whether the trigger conditions are met, and if so, execute the workflow according to the nodes configured in the flowchart. In the triggering chain, when the data generated by a subsequently triggered workflow meets the triggering conditions of a workflow that has already been triggered in the triggering chain again, the workflow that has already been triggered will no longer be triggered. The execution log module is used to save the execution log of the process after the process is completed. The execution log supports filtering by time and status.

6. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the workflow engine method based on a low-code platform as described in any one of claims 1 to 4.

7. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the program is executed by the processor, it implements the workflow engine method based on a low-code platform as described in any one of claims 1 to 4.

Citation Information

Patent Citations

  • Low-code platform approval process configuration system

    CN109615334A

  • Multi-objective optimization platform based on low codes and establishment method thereof

    CN115328465A