Workflow verification method, device, medium, equipment and program product in table

Abstract

A table workflow checking method, device, medium, equipment and program product, relating to the technical field of computer, can realize small range checking of the workflow in the database table, and improve the checking efficiency of the workflow. The table workflow checking method comprises: in response to a node configuration operation of the workflow, determining a configured first node, the workflow being an automated process created in the table, and the node of the workflow being used for processing data of the table; determining a second node having a dependency relationship with an output parameter of the first node according to node dependency information of the workflow, wherein the node dependency information represents the dependency relationship between the input parameters and the output parameters of different nodes in the workflow; and checking the second node according to the node dependency information to obtain a first checking result, wherein the first checking result represents whether the output parameter dependent on the input parameter of the second node is consistent with the node dependency information.

Description

Technical Field

[0001] This disclosure relates to the field of computer technology, and more specifically, to a method, apparatus, medium, device, and program product for verifying workflows in a table. Background Technology

[0002] Workflow systems are widely used for business process automation and typically consist of multiple nodes that can exchange data and parameters. As workflows become more complex, the references and dependencies between nodes become more intricate, necessitating effective validation of the validity of references between nodes within the workflow.

[0003] In related technologies, the validity of node references in workflow systems is usually implemented by global refresh detection, which leads to a large number of detection logics being executed repeatedly, resulting in a lot of redundant calculations. Summary of the Invention

[0004] This summary section is provided to briefly introduce the concepts, which will be described in detail in the detailed description section below. This summary section is not intended to identify key or essential features of the claimed technical solution, nor is it intended to limit the scope of the claimed technical solution.

[0005] Firstly, this disclosure provides a method for validating workflows in a table, the method comprising:

[0006] In response to a node configuration operation on a workflow, a first node to be configured is determined, wherein the workflow is an automated process created in a table, and the nodes of the workflow are used to process the data in the table;

[0007] Based on the node dependency information of the workflow, a second node that has a dependency relationship with the output parameters of the first node is determined, wherein the node dependency information represents the dependency relationship between the input parameters and output parameters of different nodes in the workflow;

[0008] Based on the node dependency information, the second node is verified to obtain a first verification result, wherein the first verification result indicates whether the output parameters on which the input parameters of the second node depend are consistent with the node dependency information.

[0009] Secondly, this disclosure provides a device for validating workflows in a table, the device comprising:

[0010] The response module is configured to respond to a node configuration operation on a workflow, and to determine the first node to be configured, wherein the workflow is an automated process created in a table, and the nodes of the workflow are used to process the data in the table;

[0011] The execution module is configured to determine a second node that has a dependency relationship with the output parameters of the first node based on the node dependency information of the workflow, wherein the node dependency information represents the dependency relationship between the input parameters and output parameters of different nodes in the workflow;

[0012] The verification module is configured to verify the second node based on the node dependency information to obtain a first verification result, wherein the first verification result indicates whether the output parameters on which the input parameters of the second node depend are consistent with the node dependency information.

[0013] Thirdly, this disclosure provides a computer-readable medium having a computer program stored thereon, which, when executed by a processing device, implements the method described in the first aspect.

[0014] Fourthly, this disclosure provides an electronic device, comprising:

[0015] A storage device on which computer programs are stored;

[0016] A processing device for executing the computer program in the storage device to implement the method described in the first aspect.

[0017] Fifthly, this disclosure provides a computer program product, including a computer program that, when executed by a processor, implements the method described in the first aspect.

[0018] The above technical solution, in response to the node configuration operation of the workflow, determines the first configured node, and based on the node dependency information of the workflow, determines the second node that depends on the output parameters of the first node. Therefore, when a node in the workflow changes, the node whose output parameters may change can be quickly and accurately identified based on the node dependency information. Subsequently, the second node can be validated based on the node dependency information. Since the validation is performed on nodes whose output parameters may change, a small-scale validation of the workflow in the database table can be achieved, reducing redundant calculations during the validation process and thus improving the efficiency of workflow validation.

[0019] Other features and advantages of this disclosure will be described in detail in the following detailed description section. Attached Figure Description

[0020] The above and other features, advantages, and aspects of the embodiments of this disclosure will become more apparent from the accompanying drawings and the following detailed description. Throughout the drawings, the same or similar reference numerals denote the same or similar elements. It should be understood that the drawings are schematic, and the originals and elements are not necessarily drawn to scale. In the drawings:

[0021] Figure 1 This is a flowchart illustrating a method for validating a workflow in a table according to an exemplary embodiment of this disclosure.

[0022] Figure 2 This is a schematic diagram illustrating a method for verifying workflows in a table according to an exemplary embodiment of this disclosure.

[0023] Figure 3 This is a schematic diagram of a dependency tree for a workflow in a table, according to an exemplary embodiment of this disclosure.

[0024] Figure 4 This is a schematic diagram of the structure of an output parameter according to an exemplary embodiment of the present disclosure.

[0025] Figure 5 This is another flowchart illustrating a method for validating a workflow in a table according to an exemplary embodiment of this disclosure.

[0026] Figure 6 This is another flowchart illustrating a method for validating a workflow in a table according to an exemplary embodiment of the present disclosure.

[0027] Figure 7 This is a block diagram illustrating a verification apparatus for a workflow in a table according to an exemplary embodiment of the present disclosure.

[0028] Figure 8 This is a block diagram of an electronic device according to an exemplary embodiment of the present disclosure. Detailed Implementation

[0029] Embodiments of this disclosure will now be described in more detail with reference to the accompanying drawings. While some embodiments of this disclosure are shown in the drawings, it should be understood that this disclosure can be implemented in various forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided to provide a more thorough and complete understanding of this disclosure. It should be understood that the accompanying drawings and embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of protection of this disclosure.

[0030] It should be understood that the steps described in the method embodiments of this disclosure may be performed in different orders and / or in parallel. Furthermore, the method embodiments may include additional steps and / or omit the steps shown. The scope of this disclosure is not limited in this respect.

[0031] The term "comprising" and its variations as used herein are open-ended inclusions, meaning "including but not limited to". The term "based on" means "at least partially based on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". Definitions of other terms will be given in the description below.

[0032] It should be noted that the concepts of "first" and "second" mentioned in this disclosure are used only to distinguish different devices, modules or units, and are not used to limit the order of functions performed by these devices, modules or units or their interdependencies.

[0033] It should be noted that the terms "a" and "a plurality of" used in this disclosure are illustrative rather than restrictive, and those skilled in the art should understand that, unless otherwise expressly indicated in the context, they should be understood as "one or more".

[0034] The names of messages or information exchanged between multiple devices in the embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of such messages or information.

[0035] It is understood that before using the technical solutions disclosed in the various embodiments of this disclosure, users should be informed of the types, scope of use, and usage scenarios of the personal information involved in this disclosure in an appropriate manner in accordance with relevant laws and regulations, and user authorization should be obtained.

[0036] For example, upon receiving a user's active request, a prompt message is sent to the user to explicitly inform them that the requested operation will require the acquisition and use of the user's personal information. This allows the user to independently choose whether to provide personal information to the software or hardware, such as the electronic device, application, server, or storage medium performing the operations of this disclosed technical solution, based on the prompt message.

[0037] As an optional but non-limiting implementation, in response to a user's active request, sending a prompt message to the user can be done via a pop-up window, where the prompt message can be presented in text format. Furthermore, the pop-up window can also include a selection control allowing the user to choose "agree" or "disagree" to provide personal information to the electronic device.

[0038] It is understood that the above notification and user authorization process are merely illustrative and do not constitute a limitation on the implementation of this disclosure. Other methods that comply with relevant laws and regulations may also be applied to the implementation of this disclosure.

[0039] Meanwhile, it is understood that the data involved in this technical solution (including but not limited to the data itself, the acquisition or use of the data) shall comply with the requirements of relevant laws, regulations and related provisions.

[0040] It should be understood that workflow systems are widely used for business process automation. Workflow systems typically consist of multiple nodes that can exchange data and parameters. Because variables passed between nodes in a workflow have reference relationships, dependencies exist between them. As workflows become more complex, the variable references and dependencies between nodes also become more complex, thus requiring effective validation of the validity of references between nodes in the workflow.

[0041] In view of this, the present disclosure provides a method, apparatus, medium, equipment and program product for verifying workflows in a table, in order to solve some or all of the above-mentioned technical problems.

[0042] The embodiments of this disclosure will be further explained below with reference to the accompanying drawings.

[0043] Figure 1 This is a flowchart illustrating a method for validating a workflow in a table according to an exemplary embodiment of this disclosure, with reference to... Figure 1 The validation method for the workflow in this table may include the following steps:

[0044] In step S11, in response to the node configuration operation of the workflow, the first node to be configured is determined. The workflow is an automated process created in a table, and the nodes of the workflow are used to process the data in the table.

[0045] In step S12, a second node that has a dependency relationship with the output parameters of the first node is determined based on the node dependency information of the workflow. The node dependency information represents the dependency relationship between the input parameters and output parameters of different nodes in the workflow.

[0046] In step S13, the second node is verified according to the node dependency information to obtain a first verification result, wherein the first verification result indicates whether the output parameter on which the input parameter of the second node depends is consistent with the node dependency information.

[0047] In this embodiment, node configuration operations include, but are not limited to, deleting nodes in the workflow, adding nodes in the workflow, and changing the output parameters of nodes in the workflow. This disclosure does not limit these operations.

[0048] For example, such as Figure 2 As shown, the order processing workflow includes node 1 (order receiving node), node 2 (order review node), node 3 (shipping node), and node 4 (confirmation of receipt node). See also Figure 2Change the output parameter of node 2 in the order processing workflow from "Approved" to "Approved". Switch the order processing workflow from scenario one to scenario two. Node 2 is now configured in the workflow, based on the node dependency information of the order workflow (see...). Figure 3 ), determine the node that has a dependency relationship with the output parameters of node 2 as node 3, based on the node dependency information (see Figure 3 ), and perform verification on node 3 respectively to obtain the first verification result.

[0049] The above technical solution, in response to the node configuration operation of the workflow, determines the first configured node, and based on the node dependency information of the workflow, determines the second node that depends on the output parameters of the first node. Therefore, when a node in the workflow changes, the node whose output parameters may change can be quickly and accurately identified based on the node dependency information. Then, the second node can be validated based on the node dependency information. Since the validation is performed on nodes whose output parameters may change, it achieves minimal validation of the workflow in the database table, reducing redundant calculations during the validation process and thus improving the efficiency of workflow validation.

[0050] To facilitate understanding of the workflow validation methods in the tables provided in this disclosure, the possible implementation methods of this disclosure are described below.

[0051] Among possible methods, the validation methods for workflows in tables may also include:

[0052] The system responds to input parameter configuration operations for each node in the workflow, determines the input parameters for each node in the workflow based on the input parameter configuration operations, and stores the input parameters through the model layer.

[0053] The view layer generates an interactive interface based on the input parameters of each node in the model layer, and displays the interactive interface. The interactive interface is used to display the input parameters and allow the user to edit the input parameters.

[0054] In this embodiment, the input parameter configuration operation includes, but is not limited to, modifying, deleting, and adding the output parameters of other nodes referenced by the input parameters, and this disclosure does not limit this.

[0055] In the above technical solution, the model layer and the view layer are decoupled and separated. Users can customize the input parameters of each node in the workflow and adjust the input parameters in real time according to the interactive interface. This enables the customization of the input parameters of each node in the workflow, which can improve the flexibility and maintainability of the workflow system.

[0056] In some possible ways, the input parameters of nodes in the workflow may include a reference identifier field and a reference type field;

[0057] The reference identifier field indicates whether the input parameters of a node support referencing the output parameters of other nodes, where other nodes are nodes in the workflow other than this node;

[0058] The reference type field indicates the type of output parameters that this node supports referencing.

[0059] In this embodiment, in response to the input parameter configuration operation for each node in the workflow, the following type-defined code block is executed to determine the input parameters for each node in the workflow:

[0060] enum InputValueType {

[0061] CONSTANT = 'constant', / / Represents a constant value for the input parameter.

[0062] VARIABLE = 'variable', / / Represents the output parameter of another node referenced by the input parameter.

[0063] };

[0064] interface NodeInputDefinition {

[0065] id: string; / / A unique identifier representing the input parameter

[0066] valueType: InputValueType; / / Represents the numeric type of the input parameter.

[0067] dataType: string; / / Indicates the data type of the input parameter

[0068] allowReference: boolean; / / Indicates whether the input parameters of this node support referencing the output parameters of other nodes.

[0069] compatibleTypes: string[]; / / Indicates the types of output parameters that this node supports referencing.

[0070] };

[0071] In this embodiment, the design of the type definition code block allows input parameters to be freely customized at the view layer, while supporting precise dependency validation through explicit type definitions. Specifically, the `id` field can be used with path notation to locate the specific attribute of the input parameter, such as locating the element within the input parameter. Users can also define the input parameters of nodes in the workflow through the `NodeInputDefinition` interface in the code above, supporting precise type validation of input parameters. For example, through the `allowReference` and `compatibleTypes` attributes, the workflow system can precisely control the types of input parameters and output parameters that can be referenced.

[0072] In the above technical solution, by decoupling and separating the model layer and the view layer and defining the type of input parameters, the verification logic of the model layer and the view layer is unified, ensuring the consistency of input parameter references during the workflow node verification process and reducing verification errors caused by logical inconsistencies.

[0073] In the most probable ways, the data structure of the output parameters of nodes in the workflow is the same.

[0074] The above technical solution unifies the data structure of output parameters for different types of nodes, enabling verification of different types of workflows and expanding the applicable scenarios for workflow verification.

[0075] In some possible ways, the output parameters of nodes in a workflow may include child node fields;

[0076] The child node field represents the type of the second parameter corresponding to the first parameter in the hierarchical relationship of the node's output parameters. The first parameter is the parent parameter of the second parameter in the hierarchical relationship.

[0077] For example, such as Figure 4 As shown, the output parameter of node 1 in the order processing workflow is order information, which includes the order amount, and hierarchical order numbers and customer information. Based on the child node fields of the order information, the data types of order numbers 1 and 2 corresponding to the order numbers in the order information, as well as the data types of the address and contact information corresponding to the customer information in the order information, can be determined.

[0078] In the above technical solution, the output parameters of each node adopt a tree structure and are stored hierarchically. The output parameters of each node can be efficiently read and updated according to the child node fields in the output parameters. Moreover, the hierarchical relationship can clearly define the subordinate relationship of each parameter in the output data, thereby realizing the orderly management of the output parameters.

[0079] In some possible ways, the output parameters of nodes in the workflow may also include configuration fields and constraint fields;

[0080] The configuration fields include a first configuration field and a second configuration field. The first configuration field is used to determine whether the output parameters of a node contain a formula, and the second configuration field is used to determine whether the output parameters of a node are a set.

[0081] The constraint fields include a first constraint field and a second constraint field. The first constraint field represents the types of triggers allowed by the node, and the second constraint field represents the nodes in the workflow that are allowed to reference the output parameters of the node.

[0082] In this embodiment, the output parameters of different types of nodes can be standardized using the following format:

[0083] interface NodeOutputDefinition {

[0084] id: string; / / A unique identifier representing the output parameter

[0085] dataType?: string; / / Indicates the data type of the output parameter

[0086] name: string; / / Represents the name of the output parameter.

[0087] format?: string; / / Data structure representing the output parameters

[0088] subItems: NodeOutputDefinition[]; / / Represents the type of the second parameter corresponding to the first parameter in the hierarchical relationship of the output parameters of the child node.

[0089] options?: { / / Represents configuration options

[0090] allowFormulas?: boolean; / / Indicates whether the output parameters support formulas.

[0091] isCollection?: boolean; / / Indicates whether the output parameter is a collection type.

[0092] };

[0093] constraints?: { / / Represents constraints

[0094] allowedTriggers?: string[]; / / Represents the types of triggers allowed by the node.

[0095] allowedNodeTypes?: object[]; / / Represents nodes in the workflow that are allowed to reference the output parameters of other nodes.

[0096] };

[0097] };

[0098] In this embodiment, the output parameters of different types of nodes can be standardized through the aforementioned standardized code block. These different types of nodes include: workflow-based table product operation nodes, non-workflow-based table product operation nodes, plugin nodes, and special logic nodes. Specifically, workflow-based table product operation nodes can add record triggers through the standardized code block, enabling them to output data including all fields in the table, the trigger timestamp, and a single record. Non-workflow-based table product operation nodes can output various types of values ​​after parsing the response data based on HTTP requests, and also support nested objects and array structures. Plugin nodes can generate corresponding output parameter lists based on the plugin's defined output through the standardized code block. Special logic nodes can be loop nodes, which can output data including the current loop data and the loop iteration number through the standardized code block.

[0099] In the above technical solution, the NodeOutputDefinition interface design can unify key attributes such as id, dataType, name, and subItems of the output parameters of different nodes. In addition, other attributes of the output parameters can be extended through options and constraints, so that the NodeOutputDefinition interface can support complex scenario requirements.

[0100] The aforementioned technical solution establishes clear definitions of the input and output of workflow nodes. When adding a new node type to the workflow, it is only necessary to define the input and output of the new node according to the corresponding specifications, and the new node can be automatically integrated into the dependency verification mechanism. Moreover, the standardized structure of the input and output of each node facilitates AI recognition and analysis, laying the foundation for subsequent intelligent optimization of the workflow.

[0101] In one possible way, the node dependency information of the workflow can be obtained in the following manner:

[0102] In response to the first trigger operation of the workflow, a depth-first traversal of the workflow nodes is performed, starting from the root node of the workflow.

[0103] For each node traversed, the node data of the node is used to determine the third output parameter information of the node. The third output parameter information includes node information and input parameter information that are dependent on the output parameters of the node.

[0104] Based on the third output parameter information of each node in the workflow, the node dependency information of the workflow is generated.

[0105] In this embodiment, the dependency relationships between the input and output parameters of different nodes in the workflow can be filled into the empty dependency tree based on the output parameter information of each node when the workflow is first triggered, thus obtaining the node dependency information of the workflow. Alternatively, historical node dependency information corresponding to the workflow can be constructed based on the preset values ​​of the input and output data of each node in the workflow. Then, when the workflow is first triggered, the dependency relationships in the historical node dependency information are updated based on the output parameter information of each node in the workflow to obtain the node dependency information of the workflow.

[0106] For example, such as Figure 2 As shown, when the order processing workflow is executed for the first time, a depth-first traversal is performed on the nodes of the order processing workflow, starting from node 1. When traversing to node 1, the node data of node 1 is obtained, which includes the node's input and output parameters. Based on the node data of node 1, the output parameter information of node 1 is determined. The traversal continues to node 2, and the node data of node 2 is obtained. Based on the node data of node 2, the output parameter information of node 2 is determined. This process continues until all nodes of the order processing workflow have been traversed, obtaining the output parameter information of nodes 1, 2, 3, and 4. The empty dependency tree is filled with the output parameter information of the four nodes to generate the dependency information of the order processing workflow.

[0107] In the above technical solution, node dependency information of the workflow can be generated when the workflow is triggered, ensuring the timeliness of the node dependency information and thus improving the accuracy and reliability of the node dependency information.

[0108] Among possible methods, the validation methods for workflows in tables may also include:

[0109] For each node traversed, the next node is determined in the workflow, and the next node is verified according to the third output parameter information to obtain the second verification result. The second verification result indicates whether the output parameter on which the input parameter of the next node depends is consistent with the third output parameter information.

[0110] The second verification result indicates that the output parameters on which the input parameters of the next node depend are inconsistent with the third output parameter information, and an error reference is marked on the next node.

[0111] For example, such as Figure 2As shown, when the order processing workflow is executed for the first time, a depth-first traversal is performed on the nodes of the order processing workflow, starting from node 1. When traversing to node 1, the node data of node 1 is obtained. The node data includes the node's input parameters and output parameters. Based on the node data of node 1, the output parameter information of node 1 is determined, and node 2 is validated based on the output parameter information of node 1. If the output parameter on which the input parameters of node 2 depend is inconsistent with the output parameter information of node 1, node 2 is marked with an error reference flag. The traversal continues to node 2 until all nodes of the order processing workflow have been traversed.

[0112] In this embodiment, when the workflow is first triggered, the next node of each node can be verified based on its output parameter information upon traversing that node, thereby marking nodes where dependencies have changed. This allows for workflow verification based on node tracking and supports the detection of output changes in nodes within the workflow.

[0113] like Figure 5 As shown below, a complete embodiment will be used to illustrate the interaction between the user, workflow editing interface, workflow manager, dependency tree manager, and node manager to explain the first-time trigger operation workflow.

[0114] 1. When a user opens the workflow editing interface, the workflow editing interface sends an initialization workflow command to the workflow manager; the workflow manager responds to the initialization workflow command and sends an initialization dependency tree command to the dependency tree manager.

[0115] II. The workflow manager sends a root node retrieval command to the node manager. The node manager responds to the root node retrieval command and returns the workflow manager as the root node.

[0116] III. The workflow manager performs a depth-first traversal of all nodes in the workflow based on the root node, and performs the following steps for each node:

[0117] 1. The workflow manager sends the current node to the node manager, and the node manager returns the node data to the workflow manager;

[0118] 2. The workflow manager sends a command to the node manager to calculate the parameter list based on the node data, and the node manager returns the parameter list to the workflow manager.

[0119] 3. The workflow manager sends an update command to the dependency tree manager based on the output parameter list. The dependency tree manager responds to the update command, updates the node dependency information, and sends the update completion information back to the workflow manager. The workflow manager then performs the following steps for the subsequent nodes of the current node.

[0120] 4. After receiving the update completion information, the workflow manager performs the following steps for subsequent nodes of the current node:

[0121] a. The workflow manager sends an analysis input parameter reference instruction to the node manager, and the node manager returns the reference information to the workflow manager;

[0122] b. The workflow manager compares the reference information with the dependency information in the dependency tree manager to check the validity of the references and obtain the check results:

[0123] i. The check result indicates that the reference is valid, and the dependency tree manager returns a valid status to the workflow manager;

[0124] ii. If the check result indicates that the reference is invalid, the dependency tree manager marks the node with an incorrect reference flag and returns a valid status to the workflow manager;

[0125] IV. After the workflow manager completes a depth-first traversal of all nodes in the workflow, it sends a command to the dependency tree manager to complete the generation of dependency information. The dependency tree manager then sends back a confirmation message that the dependency relationship has been completed to the workflow manager.

[0126] V. The workflow manager sends a notification to the workflow editing interface that the workflow initialization is complete;

[0127] VI. Workflow Editing Interface: Display the workflow editing interface to the user.

[0128] In the above technical solution, upon initial workflow triggering, a depth-first traversal is performed on all nodes in the workflow. During this traversal, the dependencies of each node in the dependency information are updated, and the next node of that node is verified based on its output parameters, marking nodes whose dependencies have changed. This approach ensures the reliability of node dependency information while enabling dependency node tracking, workflow verification, and supports output change detection and dependency node tracking.

[0129] In possible ways, determining the first node to be configured in response to a node configuration operation on the workflow may include:

[0130] In response to a node configuration operation on the workflow, the first output parameter information and the second output parameter information of the workflow are obtained. The first output parameter information represents the output parameter information of the node in the workflow before the node configuration operation, and the second output parameter information represents the output parameter information of the node in the workflow after the node configuration operation.

[0131] The first output parameter information is compared with the second output parameter information to obtain the output parameter change information;

[0132] Based on the changes in the output parameters, determine the first node to be configured.

[0133] For example, such as Figure 2 As shown, the first output parameter information in Scenario 1 of the order processing workflow, namely "order number, customer information, order amount", "approved", "shipped", and "received", is obtained, as well as the second output parameter information in Scenario 2 of the order processing workflow, namely "order number, customer information, order amount", "approved but not approved", "not shipped", and "not received". The first and second output parameter information are compared, and the output parameter change information is obtained: "approved" changes to "approved but not approved", "shipped" changes to "not shipped", and "received" changes to "not received". Based on the output parameter change information, the configured node in the order processing workflow is determined to be node 2.

[0134] In the above technical solution, the configured node is determined based on the changes in the node's output parameters before and after the node configuration operation. When an anomaly occurs in the workflow, the specific node can be quickly located without blindly troubleshooting in a complex workflow, thus achieving rapid location.

[0135] In one possible approach, determining the second node that is dependent on the output parameters of the first node, based on the node dependency information of the workflow, may include:

[0136] Based on the workflow dependency tree, determine the second node that has a dependency relationship with the output parameter of the first node. There is a one-to-one correspondence between the nodes in the dependency tree and the nodes in the workflow. The nodes in the dependency tree are attached with key-value pair dependency information. The key information in the key-value pair dependency information represents the output parameter of the node, and the value information in the key-value pair dependency information represents the node information that depends on the corresponding output parameter.

[0137] In this embodiment, the dependency tree adopts a node-level dependency approach, and its data structure design is as follows:

[0138] type NodeDependencyMap = Record<string, id="VTywC" string[]=""> ;

[0139] Here, Key represents the output parameter of the current node, and Value is an array of node IDs that depend on the corresponding output parameter. Each node in the dependency tree carries key-value pairs (KV), which can be used to further understand the dependencies between nodes. The dependency record structure is built through the NodeDependencyMap interface, which allows tracking dependencies at the node level, balancing implementation complexity and update efficiency.

[0140] For example, such as Figure 3As shown, based on the dependency tree of the order processing workflow, the nodes that are dependent on the output parameters of node 2 are identified as nodes 3 and 4.

[0141] In the above scheme, nodes in the dependency tree correspond one-to-one with nodes in the workflow. Based on the dependencies attached to nodes in the dependency tree, it's possible to identify which subsequent nodes depend on the output data of each node in the workflow, enabling more efficient change detection and updates to the workflow implementation. Furthermore, while a dependency tree using input-level dependencies allows for finer-grained updates, it requires each input component to independently listen for changes and update, resulting in higher implementation complexity. This disclosure, however, uses a node-level dependency tree, which significantly reduces unnecessary rendering while maintaining simplicity, thus optimizing performance.

[0142] In possible approaches, when there are multiple second nodes, the second nodes are validated based on node dependency information to obtain a first validation result, which may include:

[0143] Based on the node dependency information, the third node in the second node that has a direct dependency relationship with the first node is verified to obtain the first intermediate verification result;

[0144] When the third node has downstream nodes, the downstream nodes are verified according to the node dependency information to obtain the second intermediate verification result. The first verification result includes the first intermediate verification result and the second intermediate verification result.

[0145] For example, such as Figure 3 As shown, based on the node dependency information of the order processing workflow, node 3, which has a direct dependency relationship with node 2, is verified to obtain the first intermediate verification result. If node 3 has a subordinate node 4, node 4 is verified based on the node dependency information to obtain the second intermediate verification result. The first verification result includes the first intermediate verification result and the second intermediate verification result.

[0146] In the above technical solution, the dependency relationship can be tracked at the node level according to the node dependency information, and the affected nodes can be verified to achieve the minimum range verification of the workflow in the database table, thereby improving the verification efficiency of the workflow.

[0147] Among possible methods, the validation methods for workflows in tables may also include:

[0148] If the output parameters, which represent the input parameters of the second node, are inconsistent with the node dependency information, the second node is marked with an error reference flag; or,

[0149] If the first verification result indicates that the output parameters dependent on the input parameters of the second node are consistent with the node dependency information, the node state of the second node is updated to the target state. The target state indicates that the output parameters dependent on the input parameters of the second node are normal.

[0150] In the above technical solution, nodes whose dependencies have changed are marked, and the node status of nodes whose dependencies have not changed is updated. This avoids unnecessary operations on nodes whose dependencies have not changed, reduces problems caused by misoperation or misconfiguration, and improves the efficiency and performance of workflow verification.

[0151] Among possible methods, the validation methods for workflows in tables may also include:

[0152] By listening to nodes marked with error references using the listener component, the changed nodes can be obtained. The listener component is used to monitor the status of nodes in the workflow.

[0153] Render the changed nodes.

[0154] In this embodiment, on-demand updates are achieved by modifying the connect layer of the front-end framework. This is done by adding a node listening higher-order component to replace the original workflow listening higher-order component, or by using the workflow listening higher-order component to listen for nodes with incorrect references in the workflow. The process has been changed from re-rendering all nodes during workflow to re-rendering only nodes whose dependencies have changed.

[0155] In the above technical solution, when the output parameters of a node change, only the nodes directly dependent on those output parameters are re-rendered, achieving on-demand updates. Compared to related technologies, where any change in the workflow triggers a re-rendering of all nodes regardless of whether they depend on the changed node, this disclosure only re-renders nodes whose dependencies have changed, significantly improving system response speed. In extreme cases (such as when there are 100 nodes that do not reference each other), the workflow system's response time can be reduced by 100 times. When nodes are completely independent, only the directly related nodes need to be updated, avoiding a large amount of redundant computation. Furthermore, since nodes whose dependencies have not changed do not need to be re-rendered, the workflow system's response performance is improved exponentially.

[0156] like Figure 6 As shown below, a complete embodiment is used to illustrate the workflow node configuration operation through the interaction between the user, workflow editor, modified node, dependency tree, and affected node.

[0157] I. Users can modify node configurations through the workflow editing interface;

[0158] II. The workflow editing interface triggers an update of the node content to the modified node;

[0159] III. The modified node calculates the latest output parameter list and compares it with the output parameter list before configuration to determine the output parameter change information.

[0160] IV. When the output parameter change information indicates that the node has undergone a type change, the node has been deleted, or a new node has been added, the modified node sends a query dependency relationship instruction to the dependency tree, and the dependency tree returns a list of nodes that depend on the node.

[0161] V. The modified node sends a notification to the affected nodes based on the node list. Each affected node performs the following steps:

[0162] 1. This node re-validates the validity of the input parameter references, obtains the check results, and feeds back the dependency relationships to the dependency tree so that the dependency tree can update the dependency information based on the dependency relationships. The check results are as follows:

[0163] i. The inspection result indicates that the reference is valid, and the node updates its state to show that the output parameters on which the node's input parameters depend are normal;

[0164] ii. If the check result indicates that the reference is invalid, the node is marked with an incorrect reference identifier, and it is checked whether there are downstream nodes;

[0165] 2. If a node has downstream nodes, send a query command to the dependency tree so that the dependency tree can query the dependencies of downstream nodes according to the query command and return a list of downstream nodes to the node.

[0166] VI. Affected nodes report verification completion information to the workflow editor;

[0167] VII. The workflow editor only re-renders the changed nodes and updates the IU (interactive interface).

[0168] In the above technical solution, when a user modifies the node configuration, the affected nodes are found based on the dependency information, the legality of the references to the affected nodes is verified, and the nodes whose dependencies have changed are re-rendered. On-demand updates are achieved based on the dependency relationship, realizing minimal-range rendering and re-detection. Incremental verification and dependency updates can be performed when the node content changes, making the workflow system respond faster and operate more smoothly, especially in complex workflow scenarios.

[0169] In summary, the workflow validation method provided in this disclosure simplifies the development and maintenance complexity of workflow nodes by clearly defining the interface definitions and dependencies of the input and output parameters of the nodes in the workflow. Based on solving the efficiency and consistency problems of variable validation in existing workflow systems, it lays the foundation for the future expansion and intelligent upgrade of workflow systems by standardizing the data structure of workflow nodes.

[0170] Based on the same concept, this disclosure also provides a validation device for workflows in tables, such as... Figure 7 As shown, the workflow verification device 700 in this table includes:

[0171] The response module 701 is configured to, in response to a node configuration operation on a workflow, determine a first node to be configured, wherein the workflow is an automated process created in a table, and the nodes of the workflow are used to process data in the table;

[0172] The execution module 702 is configured to determine a second node that has a dependency relationship with the output parameters of the first node based on the node dependency information of the workflow, wherein the node dependency information represents the dependency relationship between the input parameters and output parameters of different nodes in the workflow;

[0173] The verification module 703 is configured to verify the second node based on the node dependency information to obtain a first verification result, wherein the first verification result indicates whether the output parameters on which the input parameters of the second node depend are consistent with the node dependency information.

[0174] The above technical solution, in response to the node configuration operation of the workflow, determines the first configured node, and based on the node dependency information of the workflow, determines the second node that depends on the output parameters of the first node. Therefore, when a node in the workflow changes, the node whose output parameters may change can be quickly and accurately identified based on the node dependency information. Then, the second node can be validated based on the node dependency information. Since the validation is performed on nodes whose output parameters may change, it achieves minimal validation of the workflow in the database table, reducing redundant calculations during the validation process and thus improving the efficiency of workflow validation.

[0175] Furthermore, the response module 701 is configured to, in response to a node configuration operation on the workflow, acquire first output parameter information and second output parameter information of the workflow, wherein the first output parameter information represents the output parameter information of the nodes in the workflow before the node configuration operation, and the second output parameter information represents the output parameter information of the nodes in the workflow after the node configuration operation.

[0176] The first output parameter information is compared with the second output parameter information to obtain the output parameter change information;

[0177] Based on the output parameter change information, the first node to be configured is determined.

[0178] Furthermore, the execution module 702 is configured to determine a second node that has a dependency relationship with the output parameters of the first node based on the dependency tree of the workflow, wherein the nodes in the dependency tree have a one-to-one correspondence with the nodes in the workflow, and the nodes in the dependency tree are attached with key-value pair dependency information, wherein the key information in the key-value pair dependency information represents the output parameters of the node, and the value information in the key-value pair dependency information represents the node information that depends on the corresponding output parameters.

[0179] Furthermore, the verification module 703 is configured to verify the third node in the second node that has a direct dependency relationship with the first node based on the node dependency information, and obtain a first intermediate verification result.

[0180] In the case that the third node has downstream nodes, the downstream nodes are verified according to the node dependency information to obtain a second intermediate verification result. The first verification result includes the first intermediate verification result and the second intermediate verification result.

[0181] Furthermore, the verification module 703 is also configured to mark the second node with an error reference flag if the output parameter, which represents the input parameter dependency of the second node, is inconsistent with the node dependency information; or,

[0182] If the first verification result indicates that the output parameters dependent on the input parameters of the second node are consistent with the node dependency information, the node state of the second node is updated to the target state, which indicates that the output parameters dependent on the input parameters of the second node are normal.

[0183] Furthermore, the workflow verification device 700 in the table also includes a rendering module, which is further configured to listen to the nodes marked with the error reference identifier through a listening component to obtain the changed nodes. The listening component is used to listen to the node status in the workflow.

[0184] The changed node is rendered.

[0185] Furthermore, the node dependency information of the workflow is obtained in the following way:

[0186] In response to the first trigger operation of the workflow, a depth-first traversal of the nodes of the workflow is performed, starting from the root node of the workflow;

[0187] For each node traversed, obtain the node data of the node, and determine the third output parameter information of the node based on the node data. The third output parameter information includes node information and input parameter information that are dependent on the output parameters of the node.

[0188] Based on the third output parameter information of each node in the workflow, the node dependency information of the workflow is generated.

[0189] Furthermore, the response module 701 is also configured to determine the next node of each traversed node in the workflow, and to verify the next node according to the third output parameter information to obtain a second verification result, wherein the second verification result characterizes whether the output parameter on which the input parameter of the next node depends is consistent with the third output parameter information.

[0190] If the second verification result indicates that the output parameter on which the input parameter of the next node depends is inconsistent with the third output parameter information, then the next node is marked with an error reference identifier.

[0191] Furthermore, the response module 701 is also configured to respond to input parameter configuration operations for each node in the workflow, determine the input parameters for each node in the workflow based on the input parameter configuration operations, and store the input parameters through the model layer;

[0192] The view layer generates an interactive interface based on the input parameters of each node in the model layer, and displays the interactive interface, which is used to display the input parameters and allow the user to edit the input parameters.

[0193] Furthermore, the input parameters of the nodes in the workflow include a reference identifier field and a reference type field;

[0194] The reference identifier field indicates whether the input parameters of the node support referencing the output parameters of other nodes, wherein the other nodes are nodes in the workflow other than the node itself.

[0195] The reference type field indicates the type of output parameters that the node supports referencing.

[0196] Furthermore, the data structure of the output parameters of the nodes in the workflow is the same.

[0197] Furthermore, the output parameters of the nodes in the workflow include child node fields;

[0198] The child node field represents the type of the second parameter corresponding to the first parameter in the hierarchical relationship of the output parameters of the node, where the first parameter is the upper-level parameter of the second parameter in the hierarchical relationship.

[0199] Furthermore, the output parameters of the nodes in the workflow also include configuration fields and constraint fields;

[0200] The configuration fields include a first configuration field and a second configuration field. The first configuration field is used to determine whether the output parameters of the node contain a formula, and the second configuration field is used to determine whether the output parameters of the node are a set.

[0201] The constraint fields include a first constraint field and a second constraint field. The first constraint field represents the trigger types allowed by the node, and the second constraint field represents the nodes in the workflow that are allowed to reference the output parameters of the node.

[0202] The specific methods by which each module performs operations in the workflow verification device 700 in the table of the above embodiments have been described in detail in the embodiments of the relevant method, and will not be elaborated here.

[0203] Based on the same concept, embodiments of this disclosure also provide a computer-readable medium having a computer program stored thereon, which, when executed by a processing device, implements the verification method for the workflow in any of the above-described tables.

[0204] Based on the same concept, this disclosure also provides an electronic device that may include:

[0205] A storage device on which computer programs are stored;

[0206] A processing device for executing the computer program in the storage device to implement the workflow verification method in any of the above tables.

[0207] Based on the same concept, embodiments of this disclosure also provide a computer program product, including a computer program that, when executed by a processor, implements the verification method for the workflow in any of the above-described tables.

[0208] The following is for reference. Figure 8 This diagram illustrates a structural schematic of an electronic device 800 suitable for implementing embodiments of the present disclosure. The terminal devices in the embodiments of the present disclosure may include, but are not limited to, mobile terminals such as mobile phones, laptops, digital broadcast receivers, PDAs (personal digital assistants), PADs (tablet computers), PMPs (portable multimedia players), in-vehicle terminals (e.g., in-vehicle navigation terminals), and fixed terminals such as digital TVs and desktop computers. Figure 8 The electronic device shown is merely an example and should not be construed as limiting the functionality and scope of the embodiments disclosed herein.

[0209] like Figure 8As shown, the electronic device 800 may include a processing device (e.g., a central processing unit, a graphics processor, etc.) 801, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 802 or a program loaded from a storage device 808 into a random access memory (RAM) 803. The RAM 803 also stores various programs and data required for the operation of the electronic device 800. The processing device 801, ROM 802, and RAM 803 are interconnected via a bus 804. An input / output (I / O) interface 805 is also connected to the bus 804.

[0210] Typically, the following devices can be connected to I / O interface 805: input devices 806 including, for example, touchscreens, touchpads, keyboards, mice, cameras, microphones, accelerometers, gyroscopes, etc.; output devices 807 including, for example, liquid crystal displays (LCDs), speakers, vibrators, etc.; storage devices 808 including, for example, magnetic tapes, hard disks, etc.; and communication devices 809. Communication device 809 allows electronic device 800 to communicate wirelessly or wiredly with other devices to exchange data. Although Figure 8 An electronic device 800 with various devices is shown; however, it should be understood that it is not required to implement or possess all of the devices shown. More or fewer devices may be implemented or possessed alternatively.

[0211] In particular, according to embodiments of this disclosure, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of this disclosure include a computer program product comprising a computer program carried on a non-transitory computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via a communication device 809, or installed from a storage device 808, or installed from a ROM 802. When the computer program is executed by a processing device 801, it performs the functions defined in the methods of embodiments of this disclosure.

[0212] It should be noted that the computer-readable medium described in this disclosure can be a computer-readable signal medium or a computer-readable storage medium, or any combination thereof. A computer-readable storage medium can be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this disclosure, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In this disclosure, a computer-readable signal medium can include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A computer-readable signal medium can be any computer-readable medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to: wires, optical fibers, RF (radio frequency), etc., or any suitable combination thereof.

[0213] In some implementations, communication can be conducted using any currently known or future-developed network protocol such as HTTP (Hypertext Transfer Protocol), and can be interconnected with digital data communication (e.g., communication networks) of any form or medium. Examples of communication networks include local area networks (“LANs”), wide area networks (“WANs”), the Internet (e.g., the Internet of Things), and end-to-end networks (e.g., ad hoc end-to-end networks), as well as any currently known or future-developed networks.

[0214] The aforementioned computer-readable medium may be included in the aforementioned electronic device; or it may exist independently and not assembled into the electronic device.

[0215] The aforementioned computer-readable medium carries one or more programs that, when executed by the electronic device, cause the electronic device to: determine a first node to be configured in response to a node configuration operation on a workflow, wherein the workflow is an automated process created in a table, and the nodes of the workflow are used to process data in the table; determine a second node that has a dependency relationship with the output parameters of the first node based on node dependency information of the workflow, wherein the node dependency information characterizes the dependency relationship between the input parameters and output parameters of different nodes in the workflow; and verify the second node based on the node dependency information to obtain a first verification result, wherein the first verification result characterizes whether the output parameters on which the input parameters of the second node depend are consistent with the node dependency information.

[0216] Computer program code for performing the operations of this disclosure can be written in one or more programming languages ​​or a combination thereof, including but not limited to object-oriented programming languages ​​such as Java, Smalltalk, and C++, as well as conventional procedural programming languages ​​such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0217] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0218] The modules described in the embodiments of this disclosure can be implemented in software or hardware. The names of the modules are not, in some cases, intended to limit the functionality of the module itself.

[0219] The functions described above in this document can be performed at least in part by one or more hardware logic components. For example, exemplary types of hardware logic components that can be used, without limitation, include: field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), system-on-a-chip (SoCs), complex programmable logic devices (CPLDs), and so on.

[0220] In the context of this disclosure, a machine-readable medium can be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, apparatus, or device. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium can be, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0221] The above description is merely a preferred embodiment of this disclosure and an explanation of the technical principles employed. Those skilled in the art should understand that the scope of this disclosure is not limited to technical solutions formed by specific combinations of the above-described technical features, but should also cover other technical solutions formed by arbitrary combinations of the above-described technical features or their equivalents without departing from the above-described concept. For example, technical solutions formed by substituting the above features with (but not limited to) technical features disclosed in this disclosure that have similar functions.

[0222] Furthermore, while the operations are described in a specific order, this should not be construed as requiring these operations to be performed in the specific order shown or in a sequential order. In certain environments, multitasking and parallel processing may be advantageous. Similarly, while several specific implementation details are included in the above discussion, these should not be construed as limiting the scope of this disclosure. Certain features described in the context of individual embodiments may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments.

[0223] Although the subject matter has been described using language specific to structural features and / or methodological logic, it should be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or actions described above. Rather, the specific features and actions described above are merely illustrative forms of implementing the claims. Regarding the apparatus in the above embodiments, the specific manner in which the various modules perform their operations has been described in detail in the embodiments relating to the method, and will not be elaborated upon here.

Claims

1. A method for validating workflows in a table, characterized in that, The validation methods for the workflow in the table include: In response to a node configuration operation on a workflow, a first node to be configured is determined, wherein the workflow is an automated process created in a table, and the nodes of the workflow are used to process the data in the table; Based on the node dependency information of the workflow, a second node that has a dependency relationship with the output parameters of the first node is determined, wherein the node dependency information represents the dependency relationship between the input parameters and output parameters of different nodes in the workflow; Based on the node dependency information, the second node is verified to obtain a first verification result, wherein the first verification result characterizes whether the output parameters on which the input parameters of the second node depend are consistent with the node dependency information; The step of determining a second node that has a dependency relationship with the output parameters of the first node based on the node dependency information of the workflow includes: Based on the dependency tree of the workflow, a second node that has a dependency relationship with the output parameters of the first node is determined. The nodes in the dependency tree have a one-to-one correspondence with the nodes in the workflow, and the nodes in the dependency tree are attached with key-value pair dependency information. The key information in the key-value pair dependency information represents the output parameters of the node, and the value information in the key-value pair dependency information represents the node information that depends on the corresponding output parameters. The validation method for the workflow in the table also includes: If the output parameters, which indicate that the input parameters of the second node depend on the first verification result, are inconsistent with the node dependency information, then the second node is marked with an error reference identifier; or... If the first verification result indicates that the output parameters dependent on the input parameters of the second node are consistent with the node dependency information, the node state of the second node is updated to the target state, which indicates that the output parameters dependent on the input parameters of the second node are normal.

2. The method for validating workflows in a table according to claim 1, characterized in that, The step of determining the first node to be configured in response to a node configuration operation on the workflow includes: In response to a node configuration operation on a workflow, the system obtains first output parameter information and second output parameter information of the workflow, wherein the first output parameter information represents the output parameter information of the nodes in the workflow before the node configuration operation, and the second output parameter information represents the output parameter information of the nodes in the workflow after the node configuration operation. The first output parameter information is compared with the second output parameter information to obtain the output parameter change information; Based on the output parameter change information, the first node to be configured is determined.

3. The method for validating workflows in a table according to claim 1, characterized in that, The second node is multiple, and the step of verifying the second node according to the node dependency information to obtain a first verification result includes: Based on the node dependency information, the third node in the second node that has a direct dependency relationship with the first node is verified to obtain the first intermediate verification result; In the case that the third node has downstream nodes, the downstream nodes are verified according to the node dependency information to obtain a second intermediate verification result. The first verification result includes the first intermediate verification result and the second intermediate verification result.

4. The method for validating workflows in a table according to claim 1, characterized in that, The validation method for the workflow in the table also includes: The changed nodes are obtained by listening to the nodes marked with the error reference identifier by the listening component. The listening component is used to listen to the node status in the workflow. The changed node is rendered.

5. The method for validating workflows in a table according to any one of claims 1-4, characterized in that, The node dependency information of the workflow is obtained in the following way: In response to the first trigger operation of the workflow, a depth-first traversal of the nodes of the workflow is performed, starting from the root node of the workflow; For each node traversed, obtain the node data of the node, and determine the third output parameter information of the node based on the node data. The third output parameter information includes node information and input parameter information that are dependent on the output parameters of the node. Based on the third output parameter information of each node in the workflow, the node dependency information of the workflow is generated.

6. The method for validating workflows in a table according to claim 5, characterized in that, The validation method for the workflow in the table also includes: For each node traversed, the next node of the node is determined in the workflow, and the next node is verified according to the third output parameter information to obtain a second verification result, wherein the second verification result characterizes whether the output parameter on which the input parameter of the next node depends is consistent with the third output parameter information. If the second verification result indicates that the output parameter on which the input parameter of the next node depends is inconsistent with the third output parameter information, then the next node is marked with an error reference identifier.

7. The method for validating workflows in a table according to any one of claims 1-4, characterized in that, The validation method for the workflow in the table also includes: In response to input parameter configuration operations for each node in the workflow, the input parameters for each node in the workflow are determined based on the input parameter configuration operations, and the input parameters are stored through the model layer; The view layer generates an interactive interface based on the input parameters of each node in the model layer, and displays the interactive interface, which is used to display the input parameters and allow the user to edit the input parameters.

8. The method for validating workflows in a table according to any one of claims 1-4, characterized in that, The input parameters for nodes in the workflow include a reference identifier field and a reference type field; The reference identifier field indicates whether the input parameters of the node support referencing the output parameters of other nodes, wherein the other nodes are nodes in the workflow other than the node itself. The reference type field indicates the type of output parameters that the node supports referencing.

9. The method for validating workflows in a table according to any one of claims 1-4, characterized in that, The output parameters of the nodes in the workflow have the same data structure.

10. The method for validating workflows in a table according to claim 9, characterized in that, The output parameters of nodes in the workflow include child node fields; The child node field represents the type of the second parameter corresponding to the first parameter in the hierarchical relationship of the output parameters of the node, where the first parameter is the upper-level parameter of the second parameter in the hierarchical relationship.

11. The method for validating workflows in a table according to claim 10, characterized in that, The output parameters of the nodes in the workflow also include configuration fields and constraint fields; The configuration fields include a first configuration field and a second configuration field. The first configuration field is used to determine whether the output parameters of the node contain a formula, and the second configuration field is used to determine whether the output parameters of the node are a set. The constraint fields include a first constraint field and a second constraint field. The first constraint field represents the trigger types allowed by the node, and the second constraint field represents the nodes in the workflow that are allowed to reference the output parameters of the node.

12. A device for verifying workflows in a table, characterized in that, The workflow verification device in the table includes: The response module is configured to respond to a node configuration operation on a workflow, and to determine the first node to be configured, wherein the workflow is an automated process created in a table, and the nodes of the workflow are used to process the data in the table; The execution module is configured to determine a second node that has a dependency relationship with the output parameters of the first node based on the node dependency information of the workflow, wherein the node dependency information represents the dependency relationship between the input parameters and output parameters of different nodes in the workflow; The verification module is configured to verify the second node based on the node dependency information to obtain a first verification result, wherein the first verification result indicates whether the output parameters on which the input parameters of the second node depend are consistent with the node dependency information; The execution module is further configured to determine a second node that has a dependency relationship with the output parameters of the first node based on the dependency tree of the workflow, wherein the nodes in the dependency tree have a one-to-one correspondence with the nodes in the workflow, and the nodes in the dependency tree are attached with key-value pair dependency information, wherein the key information in the key-value pair dependency information represents the output parameters of the node, and the value information in the key-value pair dependency information represents the node information that depends on the corresponding output parameters; The verification module is further configured to mark the second node with an error reference identifier if the first verification result indicates that the output parameters on which the input parameters of the second node depend are inconsistent with the node dependency information; or, if the first verification result indicates that the output parameters on which the input parameters of the second node depend are consistent with the node dependency information, update the node state of the second node to a target state, wherein the target state indicates that the output parameters on which the input parameters of the second node depend are normal.

13. A computer-readable medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processing device, it implements the method according to any one of claims 1-11.

14. An electronic device, characterized in that, include: A storage device on which computer programs are stored; A processing device for executing the computer program in the storage device to implement the method of any one of claims 1-11.

15. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the method of any one of claims 1-11.

Images