Process recipe editing method based on low-code flow engine of internet of things operating system

Abstract

The application relates to a process formula editing method based on an Internet of Things operating system low-code process engine, wherein a process engine is deployed as a flow conversion engine service for underlying process formula process editing; a process formula editor is used to configure corresponding process formula processes for upper-layer business applications, and process relationship of the configured process formula processes is stored in the process engine; a back-end service of the process formula editor is used to perform business encapsulation on the upper-layer business applications and the process engine; the process engine is started to execute corresponding process formula processes. In the field of industrial digitization, a configurable process formula editor can be established through the process engine, system flexibility and work efficiency are improved, process maintainability is improved, and the cost of later iteration is reduced. Under the industrial digitization construction, the process specification of a process workshop is improved, and the process efficiency of the process workshop is improved.

Description

TECHNICAL FIELD

[0001] The present disclosure relates to the technical field of industrial digitization, and in particular to a process recipe editing method, device and control system based on a low-code process engine of an Internet of Things operating system. BACKGROUND

[0002] With the rise of industrial Internet of Things and the popularization of the concept of Industry 4.0, industrial digitization reform has penetrated into every factory.

[0003] In a traditional industrial production process system, the system is developed in a customized manner. When the process flow changes or other production processes are added, it needs to be redeveloped, and the maintenance and development costs are relatively high. Due to the development in a customized manner, the system is not flexible enough to adapt to the rapidly changing market demand.

[0004] In addition, the process recipe editing facility is developed in a customized manner, which is low in work efficiency and cannot adapt to the rapid changes in market demand.

[0005] Therefore, a process recipe editor system is needed to manage the production line and uniformly maintain and manage the entire process flow. SUMMARY

[0006] To solve the above problems, the present application provides a process recipe editing method, device and control system based on a low-code process engine of an Internet of Things operating system.

[0007] In one aspect of the present application, a process recipe editing method based on a low-code process engine of an Internet of Things operating system is provided, comprising the following steps:

[0008] Deploying a process engine as a bottom process recipe flow editing flow engine service;

[0009] Through a process recipe editor, configuring a corresponding process recipe flow for an upper-layer business application, and storing the flow relationship of the configured process recipe flow in the process engine;

[0010] Using the backend service of the process recipe editor, business encapsulation is performed on the upper-layer business application and the process engine;

[0011] Starting the process engine to execute the corresponding process recipe flow.

[0012] As an optional embodiment of the present application, the process engine is deployed as a bottom process flow editing flow engine service, which comprises:

[0013] Presetting process engine adaptation rules;

[0014] According to the process engine adaptation rule, the process engine is deployed into the backend service system, and communication between the process engine and the backend service system is established.

[0015] The communication protocol between the process engine and the backend service system adopts a BPMN communication protocol.

[0016] As an optional embodiment of the present application, the process recipe editor optionally includes the following functions:

[0017] The system operation and maintenance module is configured to operate and maintain the process recipe editor between the process engine and the backend service system.

[0018] The basic data module is configured to store the process recipe flow configured by the user for the upper-layer business application, and to build the form data of each process recipe flow in advance through the bottom code form.

[0019] The recipe management module is configured to configure the process recipe according to the form data, and to associate each step of the configured process recipe flow.

[0020] The log management module is configured to record the operation and maintenance data of the process recipe editor.

[0021] The task management module is configured to establish a process recipe editing task and to perform management on the task.

[0022] As an optional embodiment of the present application, the process recipe editor is used to configure a corresponding process recipe flow for the upper-layer business application, and the process relationship of the configured process recipe flow is stored in the process engine, including:

[0023] Obtaining the process recipe requirement of the upper-layer business application;

[0024] Configuring a corresponding process recipe flow for the upper-layer business application by using the process recipe editor according to the requirement;

[0025] Entering the configured process recipe flow into the basic data, and building the form data of each process recipe flow in advance through the bottom code form;

[0026] Associating each process step in the configured form data according to the upper-layer business attribute, and storing the corresponding process relationship in the process engine.

[0027] As an optional embodiment of the present application, after the upper-layer business application and the process engine are encapsulated, the following steps are further included:

[0028] The encapsulated upper-layer business application and the process engine are sent to the backend service system by using the backend service of the process recipe editor.

[0029] The administrator of the back-end service system receives the encapsulated data and initiates a request to the corresponding process engine according to the process engine adaptation of the encapsulated data;

[0030] The process engine receives the request and waits for a start instruction from the upper-layer business application.

[0031] As an optional embodiment of the present application, the process engine is started, and the corresponding process recipe process is executed, including:

[0032] The back-end service system receives a start instruction from the upper-layer business application;

[0033] According to the start instruction, the corresponding process engine is started;

[0034] The started process engine is transferred to the corresponding node according to the process relationship of the process recipe process configured by the system and executes the corresponding task.

[0035] As an optional embodiment of the present application, after the process engine is started and the corresponding process recipe process is executed, it further includes:

[0036] The process engine is transferred to the corresponding node according to the configured logical editing process, reads the operation information of the current node, and sends the operation information of the current node to the back-end service system;

[0037] The back-end service system receives and forwards the operation information to the upper-layer business application, and the upper-layer business application notifies the corresponding operation user of the operation information through the process agency notice mode.

[0038] As an optional embodiment of the present application, after the process engine is started and the corresponding process recipe process is executed, it further includes:

[0039] The operation user receives the operation information and executes the corresponding process operation according to the operation information;

[0040] When the process execution is passed, the operation user fills in the form data on the system and passes through the process node;

[0041] When all the process nodes are executed and passed, the process engine judges the end node and issues an end notification, and records the corresponding execution data.

[0042] Another aspect of the present application also proposes a device for implementing the process recipe editing method of the low-code process engine based on the Internet of Things operating system, including:

[0043] A deployment module is configured to deploy the process engine as a bottom-layer process recipe process editing transfer engine service;

[0044] A process editing module is configured to configure a corresponding process recipe flow for an upper-layer business application through a process recipe editor, and store a flow relationship of the configured process recipe flow in the flow engine;

[0045] An encapsulation module is configured to encapsulate the upper-layer business application and the flow engine through a back-end service of the process recipe editor;

[0046] A starting module is configured to start the flow engine to execute the corresponding process recipe flow.

[0047] Another aspect of the present application also provides a control system, comprising:

[0048] A processor;

[0049] A memory for storing processor-executable instructions;

[0050] When the processor is configured to execute the executable instructions, the process recipe editing method based on the low-code flow engine of the Internet of Things operating system is implemented.

[0051] Technical effects of the present application:

[0052] The present application deploys a flow engine as a bottom-layer process recipe flow editing flow transfer engine service, configures a corresponding process recipe flow for an upper-layer business application through a process recipe editor, and stores a flow relationship of the configured process recipe flow in the flow engine, encapsulates the upper-layer business application and the flow engine through a back-end service of the process recipe editor, and starts the flow engine to execute the corresponding process recipe flow. In the field of industrial digitization, a configurable process recipe editor can be established through the flow engine, system flexibility and work efficiency are improved, process maintainability is improved, and the cost of later iteration is reduced.

[0053] The present application improves the process standardization of a process workshop and improves the process efficiency of the process workshop under the industrial digitization construction, and solves the technical defects that the system is not flexible and cannot adapt to the rapidly changing market demand due to the development in a customized manner in traditional industrial development.

[0054] Other features and aspects of the present disclosure will become apparent from the following detailed description of exemplary embodiments with reference to the drawings. BRIEF DESCRIPTION OF DRAWINGS

[0055] The accompanying drawings, which are incorporated in and constitute a part of the specification, illustrate exemplary embodiments, features, and aspects of the present disclosure and serve to explain the principles of the present disclosure.

[0056] Figure 1 A flowchart of the flow engine flowable of the present application is shown.

[0057] Figure 2 The figure shows the architecture diagram of the application system of the present application;

[0058] Figure 3 The figure shows the implementation flow diagram of the method of the present application;

[0059] Figure 4 The figure shows the application function composition diagram of the recipe editor model of the present application. DETAILED DESCRIPTION

[0060] Various exemplary embodiments, features, and aspects of the present disclosure will be described in detail below with reference to the accompanying drawings. The same reference numbers in the drawings represent elements or components having the same function or similar functions. Although various aspects of the embodiments are illustrated in the drawings, the drawings are not necessarily drawn to scale unless specifically indicated.

[0061] The word "exemplary" is used herein to mean "serving as an example, instance, or illustration." Any implementation described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other implementations.

[0062] In addition, for the purpose of better illustrating the present disclosure, numerous specific details are given in the following detailed description. Those skilled in the art will understand that the present disclosure can be practiced without certain specific details. In some instances, methods, means, elements and circuits well known to those skilled in the art are not described in detail in order to highlight the principles of the present disclosure.

[0063] The present method can edit process flow or edit recipe process, as long as the method with flow logic can be adopted.

[0064] The present application mainly adopts flowable 6.5.0 as the basis to uniformly maintain and manage the entire process flow. Through the establishment of a configurable process recipe editor in the field of industrial digitization by combining the flow engine, the system flexibility and work efficiency are improved, the maintainability is improved, and the cost of later iteration is reduced.

[0065] The working principle of the flow engine flowable is as shown in Figure 1 The flow engine will perform tasks according to the configured process flow, and will flow to each node to perform tasks according to the flow relationship in the flowchart. As shown in the accompanying Figure 1The credit approval process shown in the middle, the task starts, the first node first capture details; after capture, enter the next node, credit advice; according to the specific credit advice, select the loan, loan review; after submitting the loan review, get the following different situations: accept, inform the acceptance of loan review; reject, inform the rejection of loan review; if it needs to be upgraded (escalated loan review), the loan review is escalated to the superior (escalated), which also has the process of accept and reject; the process ends. Note: here the word is independent of the case in Figure 1 .

[0066] As shown in Figure 2 , it is a schematic diagram of the application architecture function. It mainly includes upper business application (business api display layer), back-end service system (back-end service layer) and process engine (process engine layer), wherein:

[0067] The upper business application corresponds to each process administrator and operator, which can edit process recipe, manage process logic and notification management, etc. by using the upper business application (such as mobile APP or other);

[0068] The back-end service system is used to provide back-end service, which mainly uses the service function of the back-end server to process and schedule data. The back-end service layer provides recipe model for user selection, can save each edited process example, perform data mapping, establish task queue for task allocation, and notify the upper business application of the process execution information of the process engine;

[0069] The process engine layer mainly provides an engine for executing process tasks, starts the process according to the received production command, and begins to execute the corresponding node task; it has the functions of data caching and storing process data, and is configured with an engine model for user selection, and an engine executor for executing the process task.

[0070] In a business process editing, the user can select an engine model to execute a certain task, a certain node process step; through the adaptation selection of the back-end, a communication based on the BPMN2.0 protocol can be established between the back-end and the adapted engine model.

[0071] Next, the implementation process of the method will be described in detail.

[0072] Example 1

[0073] As Figure 3 shown, one aspect of the present application proposes a process recipe editing method based on a low-code process engine of an Internet of Things operating system, comprising the following steps:

[0074] 1. Deploy the process engine as a flow engine service for underlying process recipe flow editing;

[0075] First, the back-end developer needs to deploy the process engine into the back-end service system by introducing the jar package of java, as a flow engine service for underlying process flow editing. The process recipe editor back-end service encapsulates the upper-layer business application and the process engine.

[0076] As an optional embodiment of the present application, the process engine is deployed as a flow engine service for underlying process flow editing, comprising:

[0077] presetting process engine adaptation rules;

[0078] deploying the process engine into the back-end service system according to the process engine adaptation rules, and establishing communication between the process engine and the back-end service system;

[0079] The communication protocol between the process engine and the back-end service system adopts the BPMN communication protocol.

[0080] The specific application of the process engine will be adapted in the back-end service. The back-end service layer has a process engine adaptation layer, on which specific process engine adaptation rules (user-defined) are configured, so as to adapt the corresponding process engine model according to the encapsulation information when executing specific process tasks.

[0081] Although the process engine is deployed into the back-end service system, when a specific task is executed, the corresponding process engine model needs to be adapted according to the process engine properties selected when the process is edited, the communication between the process engine and the back-end service system is established, and then the encapsulated business process information and process engine adaptation information can be sent to the process engine layer for specific execution.

[0082] This embodiment adopts the process engine flowable, is based on the BPMN2.0 protocol, adopts the business process engine developed by java, and the process engine can make the process planned in advance execute through the execution engine to each process according to certain rules.

[0083] 2. Configure the corresponding process recipe flow for the upper-layer business application through the process recipe editor, and store the process relationship of the configured process recipe flow in the process engine;

[0084] The process recipe editor is mainly used by the user administrator to edit the process flow according to the production task, and each process flow can be freely combined by using various application components in the process recipe editor through dragging, deleting, adjusting and the like. When a new production line and process flow are added or the process steps are modified, the related logic can also be adjusted through simple dragging.

[0085] The process recipe editor can be implemented by using an editor commonly used in the industry.

[0086] As an optional embodiment of the present application, the process recipe editor can include the following functions:

[0087] The system operation and maintenance module is used to operate and maintain the process recipe editor between the process engine and the background service system.

[0088] The basic data module is used to store the process recipe flow configured by the user for the upper-layer business application, and the form data of each process recipe flow is built in advance through the bottom code form.

[0089] The recipe management module is used to configure the process recipe according to the form data, and associate each step of the configured process recipe flow.

[0090] The log management module is used to record the operation and maintenance data of the process recipe editor.

[0091] The task management module is used to establish the process recipe editing task and perform the management of the task.

[0092] As shown in Figure 4 The embodiment is deployed with a process recipe editor (recipe editor model) on the background server, and has five functions of system operation and maintenance, basic data, recipe management, log management and task management.

[0093] The application mode of each function module is a common application scheme and technical principle in the field, which is not described herein.

[0094] When a production line needs to be configured, the system administrator enters the production line process flow steps into the basic data in advance, and builds the form data of each process flow step through the bottom code form in advance.

[0095] The system administrator can associate the previously configured process steps by dragging, and the associated process relationship is stored in the process engine.

[0096] As an optional embodiment of the present application, the process recipe editor is used to configure the corresponding process recipe flow for the upper-layer business application, and the process relationship of the configured process recipe flow is stored in the process engine, including:

[0097] Obtaining process recipe requirements of the upper business application;

[0098] According to the requirements, a corresponding process recipe process is configured for the upper business application by using a process recipe editor;

[0099] The configured process recipe process is entered into the basic data, and the form data of each process recipe process is built in advance through a bottom code form;

[0100] According to the upper business attribute, each process step in the configured form data is associated, and the corresponding process relationship is stored in the process engine.

[0101] When a production line needs to be configured, the specific process recipe requirements to be produced are obtained through the upper business application (each business port such as an api port), and the process information of each application node can be obtained, so as to facilitate process editing according to the obtained node process.

[0102] The system administrator logs in to the background according to the process recipe requirements, and configures a corresponding process recipe process for the upper business application by using the deployed process recipe editor; the process recipe process can be configured as required. For specific functions, refer to the application description of the above function framework.

[0103] When the system administrator receives a task, the steps of configuring the process recipe process are as follows:

[0104] 1). Configure the process recipe process: when a production line needs to be configured, the previously configured process steps are associated by dragging. The process engine stores the corresponding process relationship.

[0105] 2). Start the process flow: when receiving a factory production command, the operator starts the corresponding process flow in the system, at which time the process engine is started and flows to the corresponding node.

[0106] 3). Process assignment notification: when the process engine is started, it will automatically flow to the corresponding node according to the logic arrangement, and the process engine will read the current node operator and notify the corresponding worker of the production line.

[0107] 4). Process execution through: after the corresponding worker of the production line is notified, the worker operates the corresponding process and fills in the form data in the system and passes through the process node after completing the operation.

[0108] 5). Process end notification: until all process nodes are executed and passed, the process engine judges the end node, notifies the production line that the process execution is ended through a message, and records the corresponding completion data.

[0109] When configuring the process procedure for each node, user variable parameters can be added in the specific process node, different user variable parameters can be used in each process handling node, and a set of user variable parameters can be transmitted before the process is started, so that the same process recipe can be processed by different personnel, and dynamic personnel transformation can be performed on the node that has not been executed, and the process recipe is mapped to the actual production link process recipe with different shift personnel processing.

[0110] 3. Using the backend service of the process recipe editor, the upper-layer business application and the process engine are encapsulated for business;

[0111] After the task flow is edited by using the process recipe editor, the edited information and the selected process engine information are encapsulated and published in the background, and the background performs data operation and task management and execution.

[0112] As an optional embodiment of the present application, after the upper-layer business application and the process engine are encapsulated for business, the following steps are further included:

[0113] Using the backend service of the process recipe editor, the encapsulated upper-layer business application and the process engine are sent to the backend service system;

[0114] The administrator of the backend service system receives the encapsulated data, and performs process engine adaptation according to the encapsulated data, and initiates a request to the corresponding process engine;

[0115] The process engine receives the request and waits for the start instruction issued by the upper-layer business application.

[0116] When the task flow is edited by using the process recipe editor, a specific process instance is generated in the background server, a corresponding engine model is selected through data mapping, and the process flow is executed. After the encapsulated information is received by the background administrator, the encapsulated data is unpacked, and the engine model is selected according to the engine model configuration information in the unpacked data, and the like. The process is not within the protection scope of the present application, and will not be described here.

[0117] 4. Starting the process engine and executing the corresponding process recipe flow.

[0118] After the system administrator issues a task start command such as a production command from the upper-layer business application end, the operator starts the corresponding process flow in the system, at this time the process engine is started, and is transferred to the corresponding node, and executes the task according to the edited flow logic.

[0119] As an optional embodiment of the present application, the process engine is started, and the corresponding process recipe flow is executed, including:

[0120] The backend service system receives the start instruction issued by the upper-layer business application;

[0121] According to the start instruction, the corresponding process engine is started;

[0122] The started process engine is transferred to the corresponding node according to the process relationship of the process recipe configured by the system and performs the corresponding task.

[0123] The backend service system sends a start request to the corresponding process engine model and issues a task according to the task queue in the backend service system; the process engine is started according to the instruction and is transferred to each node according to the process logic; and the operators of each node operate according to the execution result of the task of the node.

[0124] As an optional embodiment of the present application, after starting the process engine and executing the corresponding process recipe, the following steps are further included:

[0125] The process engine is transferred to the corresponding node according to the configured logic editing process, reads the operation information of the current node, and sends the operation information of the current node to the backend service system;

[0126] The backend service system receives and forwards the operation information to the upper-layer business application; and the upper-layer business application notifies the corresponding operation user of the operation information through a process agency notice.

[0127] The process engine reads the current node operator and notifies the corresponding worker of the production line. The task execution result of each node is returned to the backend service system in real time, enters the backend service system, and returns to the corresponding node application. The upper-layer business application notifies the corresponding operation user of the operation information through a process agency notice; and the operator of each node receives the operation information and performs specific operation.

[0128] As an optional embodiment of the present application, after starting the process engine and executing the corresponding process recipe, the following steps are further included:

[0129] The operation user receives the operation information and performs the corresponding process operation according to the operation information;

[0130] When the process execution is passed, the operation user fills in the form data on the system and passes the process node;

[0131] When all the process nodes are executed and passed, the process engine judges the end node and sends an end notification, and records the corresponding execution data.

[0132] Each node operator performs the operation of the operation information, and after the corresponding worker of the production line is notified and the corresponding process is completed, the worker fills in the form data on the system and passes through the process node. Until all process process nodes are executed and passed, the process engine judges the end node, notifies the production line that the process flow execution is completed through the message, and records the corresponding completion data.

[0133] Therefore, the present application improves the flexibility and work efficiency of the system, improves the maintainability, and reduces the cost of later iteration by establishing a configurable process recipe editor through the process engine in the field of industrial digitization.

[0134] It should be noted that although the above process execution engine is introduced as an example of the flowable process engine, those skilled in the art can understand that the present disclosure should not be limited thereto. In fact, the user can flexibly set the process execution engine according to the actual application scene, as long as the technical function of the present application can be realized according to the above technical method.

[0135] Obviously, those skilled in the art should understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing related hardware through a computer program. The program can be stored in a computer-readable storage medium, and the program can include the processes of the above-mentioned embodiment of the control method when executed. Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing related hardware through a computer program. The program can be stored in a computer-readable storage medium, and the program can include the processes of the above-mentioned embodiment of the control method when executed. The storage medium can be a magnetic disk, an optical disk, a read-only memory (ROM), a random access memory (RAM), a flash memory, a hard disk drive (HDD) or a solid state drive (SSD), etc. The storage medium can also include a combination of the above-mentioned types of memories.

[0136] Embodiment 2

[0137] Based on the implementation principle of embodiment 1, another aspect of the present application also provides an apparatus for implementing the process recipe editing method based on the low-code process engine of the Internet of Things operating system, comprising:

[0138] The deployment module is configured to deploy the process engine as a flow engine service for editing the bottom process recipe flow;

[0139] The process editing module is configured to configure a corresponding process recipe flow for the upper-layer business application through a process recipe editor, and store a flow relationship of the configured process recipe flow in the flow engine.

[0140] The packaging module is configured to package the upper-layer business application and the flow engine through a back-end service of the process recipe editor.

[0141] The starting module is configured to start the flow engine to execute the corresponding process recipe flow.

[0142] The functions and interaction principles of the above modules can be found in the description of Embodiment 1, and thus will not be repeated here.

[0143] The modules or steps of the present application described above can be realized by a general computing device, which can be concentrated on a single computing device or distributed on a network composed of multiple computing devices. Alternatively, the modules or steps can be realized by program codes executable by a computing device, so that they can be stored in a storage device and executed by a computing device, or they can be respectively manufactured into individual integrated circuit modules, or multiple modules or steps among them can be manufactured into a single integrated circuit module. Thus, the present application is not limited to any specific combination of hardware and software.

[0144] Embodiment 3

[0145] Further, another aspect of the present application also proposes a process recipe editing method based on a low-code flow engine of an Internet of Things operating system, which comprises:

[0146] A processor;

[0147] A memory for storing executable instructions of the processor;

[0148] The processor is configured to implement the process recipe editing method based on the low-code flow engine of the Internet of Things operating system when executing the executable instructions.

[0149] The control system of the present embodiment comprises a processor and a memory for storing executable instructions of the processor. The processor is configured to implement the process recipe editing method based on the low-code flow engine of the Internet of Things operating system when executing the executable instructions.

[0150] Here, it should be pointed out that the number of processors can be one or more. Meanwhile, the control system of the present embodiment can also comprise an input device and an output device. The processor, the memory, the input device and the output device can be connected through a bus or through other means, which is not limited here.

[0151] The memory, as a computer readable storage medium, can be used to store software programs, computer executable programs and various modules, such as programs or modules corresponding to the process recipe editing method based on the low-code flow engine of the Internet of Things operating system of the embodiments of the present disclosure. The processor executes various function applications and data processing of the control system by running the software programs or modules stored in the memory.

[0152] The input device can be used to receive input numbers or signals. Among them, the signal can be a key signal related to the user settings and function control of the device / terminal / server. The output device can include a display device such as a display screen.

[0153] The above has described the embodiments of the present disclosure, and the above description is exemplary, not exhaustive, and is not limited to the disclosed embodiments. Many modifications and changes are obvious to those skilled in the art without departing from the scope and spirit of the described embodiments. The selection of the terms used herein is intended to best explain the principles, practical applications or technical improvements of the technology in the market of the embodiments, or to enable other ordinary skilled persons in the art to understand the embodiments disclosed herein.

Claims

1. A process recipe editing method based on a low-code workflow engine of an IoT operating system, used to improve the process standardization and efficiency of the process shop, characterized in that... Includes the following steps: Deploy the process engine as a flow engine service for editing the underlying process recipe process. By introducing the Java JAR package, the process engine is deployed to the backend service system as a flow engine service for editing the underlying process process. When executing a specific task, it is necessary to adapt the corresponding process engine model according to the process engine attribute selected when editing the process, and establish communication between the process engine and the backend service system in order to send the encapsulated business process information and process engine adaptation information to the process engine layer for specific execution. The process recipe editor is used to configure corresponding process recipe flows for upper-level business applications, and the flow relationships of the configured process recipe flows are stored in the process engine. This includes: obtaining the process recipe requirements of upper-level business applications; configuring corresponding process recipe flows for upper-level business applications using the process recipe editor according to the requirements; entering the configured process recipe flows into the basic data, and building the form data for each process recipe flow in advance through the underlying code form; associating the various process steps in the configured form data according to the upper-level business attributes, and storing the corresponding flow relationships in the process engine. When the system administrator receives the task, the steps for configuring the process recipe flow are roughly as follows: 1) Configure the process recipe flow: When a production line needs to be configured, the previously configured process recipe flow is configured by dragging and dropping. 1) Configured process steps are linked together, and the process engine stores the corresponding process relationships; 2) Start the process flow: When a production order is received from the factory, the operator starts the corresponding process flow in the system. At this time, the process engine will start and flow to the corresponding node; 3) Process assignment notification: After the process engine starts, it will automatically flow to the corresponding node according to the logical arrangement. The process engine will read the operator of the current node and notify the corresponding worker on the production line; 4) Process execution passed: After the corresponding worker on the production line is notified, the worker completes the corresponding process operation, fills in the form data on the system, and passes the process node; 5) Process end notification: Until all process nodes have been executed, the process engine determines the end node, notifies the production line of the end of the process flow through a message, and records the corresponding completion data; Using the backend service of the process recipe editor, the upper-layer business application and process engine are encapsulated. The encapsulated upper-layer business application and process engine are then sent to the backend service system. The administrator of the backend service system receives the encapsulated data, adapts the process engine according to the encapsulated data, and sends a request to the corresponding process engine. The process engine receives the request and waits for the start command issued by the upper-layer business application. Start the process engine and execute the corresponding process formula flow.

2. The process recipe editing method based on a low-code workflow engine of an IoT operating system according to claim 1, characterized in that, Deploy the workflow engine, which serves as the underlying process flow editing engine service, including: Preset process engine adaptation rules; According to the process engine adaptation rules, the process engine is deployed to the backend service system, and communication between the process engine and the backend service system is established. The communication protocol between the process engine and the backend service system adopts the BPMN communication protocol.

3. The process recipe editing method based on a low-code workflow engine of an IoT operating system according to claim 1, characterized in that, The process recipe editor includes the following functions: The system operation and maintenance module is used to maintain the process recipe editor between the process engine and the back-end service system. The basic data module is used to store the process formula flow that users enter and configure for the upper-layer business application, and to build the form data of each process formula flow in advance through the underlying code form. The formula management module is used to configure the formula process based on form data and associate the various steps of the configured process formula flow. The log management module is used to record the operation and maintenance data of the process recipe editor; The task management module is used to create process recipe editing tasks and manage their execution.

4. The process recipe editing method based on a low-code workflow engine of an IoT operating system according to claim 1, characterized in that, Start the process engine and execute the corresponding process formula flow, including: The backend service system receives the start command from the upper-layer business application; The corresponding process engine is started according to the startup command; The running process engine, based on the process flow relationships configured in the system, will flow to the corresponding nodes and execute the corresponding tasks.

5. The process recipe editing method based on a low-code workflow engine of an IoT operating system according to claim 4, characterized in that, After starting the process engine and executing the corresponding process formula flow, the following is also included: The process engine edits the process according to the configured logic, flows to the corresponding node, reads the operation information of the current node, and sends the operation information of the current node to the backend service system; The backend service system receives and forwards the operation information to the upper-layer business application. The upper-layer business application then notifies the corresponding user of the operation information via a process delegation notification.

6. The process recipe editing method based on an IoT operating system low-code workflow engine according to claim 5, characterized in that, After starting the process engine and executing the corresponding process formula flow, the following is also included: The user receives the operation information and performs the corresponding process operation according to the operation information; Once the process is completed, the user fills in form data on the system and passes through that process node; Once all process nodes have been successfully executed, the process engine determines the end node, issues an end notification, and records the corresponding execution data.

7. An apparatus for implementing the process recipe editing method based on an IoT operating system low-code workflow engine as described in any one of claims 1 to 6, characterized in that, include: The deployment module is used to deploy the process engine, which serves as the flow engine service for editing the underlying process recipe process; The process editing module is used to configure corresponding process recipe processes for upper-layer business applications through the process recipe editor, and store the process relationship of the configured process recipe processes in the process engine. The encapsulation module is used to encapsulate the upper-layer business applications and process engine using the backend service of the process recipe editor. The startup module is used to start the process engine and execute the corresponding process formula process.

8. A control system, characterized in that, include: processor; Memory used to store processor-executable instructions; The processor is configured to implement the process recipe editing method based on the low-code process engine of the Internet of Things operating system as described in any one of claims 1 to 6 when executing the executable instructions.

Images