Method and apparatus for processing table-based workflow, electronic device, and storage medium

Abstract

Disclosed is a method for processing a table-based workflow, comprising: displaying a target table project in a spreadsheet, the target table project comprising at least one item of tabular data; in response to a first operation instruction, creating, in the target table project, a first task flow corresponding to a table workflow, the first task flow comprising at least two task nodes executed in sequence, the task nodes binding to the at least one item of tabular data in the target table project, and the task nodes being configured for executing, on the basis of the tabular data, a table function constituting the table workflow; and triggering the first task flow so as to execute the table workflow. The method implements a corresponding table function by means of task nodes flexibly bound to tabular data within a table project, and constructs a task flow corresponding to a table workflow.

Description

Processing methods, devices, electronic equipment, and storage media for workflows within tables

[0001] Cross-reference to related applications

[0002] This application claims priority to Chinese Patent Application No. 202411224401.5, filed on September 2, 2024, entitled “Method, Apparatus, Electronic Device and Storage Medium for Processing Workflow in a Table”, the entire contents of which are incorporated herein by reference. Technical Field

[0003] This disclosure relates to the field of Internet technology, and in particular to a method, apparatus, electronic device, and storage medium for processing workflows within a table. Background Technology

[0004] Currently, in data and business management applications, users can create data tables to store tabular data. At the same time, they can create workflows to automate the triggering of tabular functions, thereby improving the efficiency of business management. Summary of the Invention

[0005] This disclosure provides a task execution method, apparatus, electronic device, and storage medium.

[0006] In a first aspect, embodiments of this disclosure provide a method for processing workflows within a table, including:

[0007] Display a target table item within the project operation area of ​​the spreadsheet. The target table item contains at least one piece of table data. In response to a first operation instruction, create a first task flow corresponding to a table workflow within the target table item. The first task flow includes at least two ordered task nodes. The task nodes are bound to at least one piece of table data within the target table item. The task nodes are used to execute table functions constituting the table workflow based on the table data. Trigger the first task flow to execute the table workflow.

[0008] Secondly, embodiments of this disclosure provide a processing apparatus for in-table workflows, including:

[0009] The display module is used to display a target table item in the project operation area of ​​the spreadsheet, wherein the target table item contains at least one piece of table data.

[0010] A processing module is configured to respond to a first operation instruction and create a first task flow within the target table item. The first task flow includes at least two ordered task nodes. The task nodes are bound to at least one piece of table data within the target table item. The task nodes are configured to execute corresponding table functions based on the table data.

[0011] An execution module is used to trigger the first task flow to execute the table workflow.

[0012] Thirdly, embodiments of this disclosure provide an electronic device, including: a processor and a memory;

[0013] The memory stores computer-executed instructions;

[0014] The processor executes computer execution instructions stored in the memory, causing the at least one processor to perform the in-table workflow processing method described in the first aspect and various possible designs of the first aspect.

[0015] Fourthly, embodiments of this disclosure provide a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, implement the table workflow processing method described in the first aspect and various possible designs of the first aspect.

[0016] Fifthly, embodiments of this disclosure provide a computer program product, including a computer program that, when executed by a processor, implements the table workflow processing method described in the first aspect and various possible designs of the first aspect.

[0017] The table workflow processing method, apparatus, electronic device, and storage medium provided in this embodiment display a target table item within the project operation area of ​​a spreadsheet. The target table item contains at least one piece of table data. In response to a first operation instruction, a first task flow corresponding to the table workflow is created within the target table item. The first task flow includes at least two sequentially executed task nodes. Each task node is bound to at least one piece of table data within the target table item, and the task node is used to execute table functions constituting the table workflow based on the table data. The first task flow is then triggered to execute the table workflow. This method decomposes the table workflow into multiple table functions and implements the corresponding table functions through task nodes flexibly bound to table data within the table item. A task flow corresponding to the table workflow is then constructed, and subsequently triggered. Attached Figure Description

[0018] To more clearly illustrate the technical solutions in the embodiments of this disclosure or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of this disclosure. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0019] Figure 1 is a schematic diagram of an application scenario for creating a workflow in the prior art provided by an embodiment of this disclosure;

[0020] Figure 2 is a flowchart illustrating the method for processing workflows within a table according to an embodiment of this disclosure.

[0021] Figure 3 is a schematic diagram of an application interface of a spreadsheet provided in an embodiment of this disclosure;

[0022] Figure 4 is a flowchart of the specific implementation of step S102 in the embodiment shown in Figure 2;

[0023] Figure 5 is a schematic diagram of a process for generating a first task flow according to an embodiment of this disclosure;

[0024] Figure 6 is a schematic diagram of a first task flow provided in an embodiment of this disclosure;

[0025] Figure 7 is a schematic diagram of another first task flow provided in an embodiment of this disclosure;

[0026] Figure 8 is a schematic flowchart of the table workflow processing method provided in this embodiment of the present disclosure;

[0027] Figure 9 is a schematic diagram of another process for creating a first task flow provided in an embodiment of this disclosure;

[0028] Figure 10 is a flowchart of the specific implementation of step S206 in the embodiment shown in Figure 8;

[0029] Figure 11 is a structural block diagram of the processing device for in-table workflows provided in an embodiment of this disclosure;

[0030] Figure 12 is a schematic diagram of the structure of an electronic device provided in an embodiment of this disclosure;

[0031] Figure 13 is a schematic diagram of the hardware structure of the electronic device provided in an embodiment of this disclosure. Detailed Implementation

[0032] To make the objectives, technical solutions, and advantages of the embodiments of this disclosure clearer, the technical solutions of the embodiments of this disclosure will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this disclosure, and not all embodiments. Based on the embodiments of this disclosure, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this disclosure.

[0033] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this disclosure are all information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, use and processing of the relevant data must comply with the relevant laws, regulations and standards of the relevant countries and regions, and corresponding operation portals are provided for users to choose to authorize or refuse.

[0034] Existing solutions for creating and executing workflows within an application suffer from problems such as complex workflow creation processes and a lack of flexibility in adjusting workflows after generation, which affect the application's interaction and execution efficiency.

[0035] The application scenarios of the embodiments of this disclosure are explained below:

[0036] Figure 1 is a schematic diagram of an application scenario for creating a workflow in the prior art provided by an embodiment of this disclosure. The workflow processing method within a table provided by this embodiment can be applied to applications (APPs) with data and business management functions, such as project management applications and electronic document applications. More specifically, it can be applied to application scenarios where workflows are created within an application. The executing entity in this embodiment can be a terminal device running the aforementioned application with data and business management functions, a server deploying the server-side corresponding to the aforementioned application, or other electronic devices that perform similar functions. When the executing entity is a server, the server-side of the aforementioned application with data and business management functions runs on the server, and the method provided in this embodiment is executed on the server side. The terminal device runs the client of the application, and communication between the server and the terminal device is based on server-client communication, thereby enabling the terminal device to obtain the execution result of the method provided in this embodiment and display it as needed.

[0037] In some embodiments, the terminal device or server can implement the workflow processing method within the table provided in this application by running various computer-executable instructions or computer programs. For example, computer-executable instructions can be program-level commands, machine instructions, or software instructions. Computer programs can be native programs or software modules in an operating system; they can be local applications, i.e., programs that need to be installed in the operating system to run, or small programs embedded in any APP, i.e., programs that run based on a browser environment. In summary, the aforementioned computer-executable instructions can be any form of instruction, and the aforementioned computer programs can be any form of application, module, or plugin; the specific implementation can be configured as needed. Further, in some embodiments, the server can be an independent physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing basic cloud computing services such as cloud services, cloud storage, cloud communication, cloud databases, cloud computing, cloud functions, network services, middleware services, domain name services, security services, content delivery networks (CDNs), and big data and artificial intelligence platforms. The cloud services can be interactive processing services that can be invoked by the terminal device.

[0038] Referring to Figure 1, taking a terminal device (such as a personal computer) as an example, after running the spreadsheet, the terminal device will display a specific business interface, such as a data interface. The data interface displays specific table data (e.g., table data D1, table data D2, table data D3, etc.) in tabular form to achieve basic data management functions. In addition, the spreadsheet also provides workflow components for creating workflows. When the user clicks on a workflow component, they are redirected to the workflow interface. Within this interface, a workflow containing multiple work nodes can be created, such as Workflow_1 shown in the figure, which includes work nodes P1, P2, and P3. Simultaneously, the workflow interface can also display existing workflows (e.g., Workflow_2, Workflow_3, etc.). The completed workflow is then saved in the spreadsheet, and triggering the workflow will automatically execute the corresponding process.

[0039] In existing technologies, the workflow creation process described above lacks a direct connection to the tabular data. That is, the work nodes within the workflow do not utilize the tabular data or are constructed by statically inputting information into them. This leads to several problems. First, because the work nodes require additional data and information, the workflow creation process becomes complex, resulting in large data volumes and low execution efficiency. Second, when modifications to the workflow are needed, each work node's data and information must be modified individually, increasing the cost of workflow adjustments and ultimately impacting the application's interaction and execution efficiency.

[0040] This disclosure provides a method, apparatus, electronic device, and storage medium for processing workflows within tables to solve the above-mentioned problems.

[0041] Referring to Figure 2, Figure 2 is a schematic flowchart of a table-based workflow processing method provided in this embodiment of the present disclosure. The method of this embodiment can be applied to terminal devices or servers, and the table-based workflow processing method includes:

[0042] Step S101: Display the target table item in the project operation area of ​​the spreadsheet. The target table item contains at least one piece of table data.

[0043] Step S102: In response to the first operation instruction, create a first task flow corresponding to the table workflow within the target table item. The first task flow includes at least two ordered task nodes. The task nodes are bound to at least one piece of table data within the target table item. The task nodes are used to execute table functions that constitute the table workflow based on the table data.

[0044] For example, this embodiment describes the scenario where a terminal device is the execution subject. Specifically, a spreadsheet program runs on the terminal device. This spreadsheet program is, for example, an application with data and business management functions as described in the above scenario. Then, specific table items are displayed within the spreadsheet, including the target table item to be processed. Further, displaying the target table item in this embodiment means displaying the identifier of the target table item, such as its name or icon. Specific implementations of displaying the table items include, for example, displaying "Table Item A," "Table Item B," or "Business Management Item A," "Business Follow-up Item B," etc., within the spreadsheet. Each target table item contains at least one piece of table data, which is data related to the target table item. This data can be business-related data bound during the creation of the target table item, such as sales data, material management data, personnel information data, etc. For example, during the display of the target table item, the content or name of the corresponding table data is simultaneously displayed.

[0045] In one possible implementation, the target table item is displayed as a multi-level directory, with each subdirectory containing the corresponding table data. Of course, in other possible implementations, the target table item can also be displayed in other forms, such as a tree diagram, where the target table item name is the root node and its corresponding table data is the leaf node, and so on. The display method of the target table item in the spreadsheet can be designed as needed; no specific restrictions are imposed here.

[0046] Furthermore, after displaying the target table item in the spreadsheet, the user can create an automatically executing table workflow for the target table item by performing a creation operation within the spreadsheet. This table workflow can include multiple work steps, such as data processing steps, information push steps, and so on. Specifically, after receiving the first operation instruction generated based on the aforementioned creation operation, the terminal device will create a task flow within the target table item to implement the table workflow, i.e., a first task flow. This first task flow is a data body used to implement the table workflow. After generating the first task flow, it is displayed in the spreadsheet. The first task flow includes at least two sequentially executed task nodes. Each task node is bound to at least one piece of table data within the target table item, and the task node is used to execute the table functions constituting the table workflow based on the table data. The table data refers to the data related to the target table item, logically stored within the target table item, as described in previous sections and will not be repeated here. A task node being bound to at least one item of table data within a target table item means that a task node in the first task flow maps to a specific piece of table data and uses that bound table data to execute the corresponding table function. The table function is a task performed by calling functions within a spreadsheet, such as data search or message push. In practice, the binding of a task node to at least one item of table data within a target table item can be determined by the visual appearance of the task node within the first task flow; for example, the bound table data can be displayed within the icon corresponding to the task node.

[0047] Further, in one possible implementation, the target table project has a first subdirectory and a second subdirectory. The directory entries of the first subdirectory are used to represent table data, and the directory entries of the second subdirectory are used to represent task flows. The identifier of the first task flow is the directory entry of the second subdirectory. Figure 3 is a schematic diagram of an application interface of a spreadsheet provided in an embodiment of this disclosure. As shown in Figure 3, exemplarily, in the project management interface within the spreadsheet, a project operation area is set on the left (exemplarily). In this project operation area, table projects are loaded, such as project A, project B, project C, etc., as shown in the figure. Among them, project B is, for example, the target table project. Under project B, it can include two types of subdirectories, namely the first subdirectory and the second subdirectory. For example, as shown in the figure, data table #1 and data table #2 are both directory entries belonging to the first subdirectory. In response to the first operation instruction for project B, an identifier for task flow L1 is created under project B. This task flow L_1 is the directory entry belonging to the second subdirectory, which is also the identifier of the first task flow. In one possible scenario, for example, under project B, an existing second subdirectory may be included. After responding to the first operation command for project B, the terminal device adds a task flow identifier, i.e., the identifier of the first task flow, to the second subdirectory of project B. In this case, the second subdirectory contains at least two task flow identifiers. In another possible scenario, for example, project B may not initially include a second subdirectory. After responding to the first operation command for project B, the terminal device adds a second subdirectory under project B, which includes a task flow identifier, i.e., the identifier of the first task flow. For example, the first and second subdirectories under a table item can be distinguished by corresponding icons. For instance, data table #1, data table #2, etc., under project B correspond to one type of icon (represented by a square icon in the figure), while task flow L0, task flow L1, etc., under project B correspond to another type of icon (represented by a circular icon in the figure).

[0048] Further, as shown in Figure 4, exemplarily, step S102 is specifically implemented as follows:

[0049] Step S1021: In response to the first operation instruction, create at least one upstream task node in the spreadsheet and configure the table data corresponding to the upstream task node;

[0050] Step S1022: Automatically generate downstream task nodes for upstream task nodes based on the table functions executed by upstream task nodes and the corresponding table data;

[0051] Step S1023: Generate the first task flow based on the upstream task node and the downstream task node.

[0052] Figure 5 is a schematic diagram of a process for generating a first task flow according to an embodiment of this disclosure. The process will be described below with reference to Figure 5. For example, referring to the application interface diagram shown in Figure 3, firstly, after triggering the creation process of the first task flow L0, icons corresponding to task nodes are added in the spreadsheet (e.g., the task flow editing area on the right side of the project management interface). For example, task node P1 shown in the figure is the upstream task node. The upstream task node can be added automatically or manually, without restriction. Then, the user can edit the above task node to determine its specific functional logic (e.g., add functional logic Log_1). After that, the table data corresponding to the upstream task node is configured. The table data corresponding to the upstream task node is the table data under the target table item. For example, data table #1 is bound (manually configured) to task node P1. After the functional logic and corresponding table data of the upstream task node are configured, the configuration process of the upstream task node is completed. Then, the terminal device automatically generates at least one downstream task node, such as task node P2, according to the table function executed by the upstream task node and the corresponding table data. Task node P2 is the task node to be executed after task node P1 has finished executing. More specifically, for example, based on the functional logic and table data of task node P1, if task node P1 is used to execute a table function that calls specific high-privilege data, then according to the preset task node automatic generation model, a task node P2 is automatically generated after task node P1. Task node P2 is used to execute a table function that sends an approval request to a specific high-privilege user. The mapping logic of automatically executing the table function corresponding to task node P2 after the table function corresponding to task node P1 is stored in the task node automatic generation model. The task node automatic generation model also includes the mapping logic of other continuously executed table functions, which can be set as needed and will not be elaborated here. Afterwards, the user can further add downstream adjacent task nodes of task node P1 or task node P2 as needed and configure them, and so on, until all task nodes are created. Finally, all task nodes, including the above upstream and downstream task nodes, are used to generate the first task flow.

[0053] In this embodiment, a scheme for automatically generating task nodes to construct a first task flow is provided. By automatically generating downstream task nodes for the configured task nodes based on their functional logic and configuration data, the generation efficiency of the first task flow is improved.

[0054] Step S103: Trigger the first task flow to execute the table workflow.

[0055] Furthermore, after creating the first task flow, it is displayed in the spreadsheet. The first task flow describes the specific execution steps of the spreadsheet workflow through multiple sequentially executed task nodes. Based on this, the user can further modify and adjust the first task flow as needed. Then, by triggering the first task flow, the corresponding spreadsheet workflow is executed. Figure 6 is a schematic diagram of a first task flow provided by an embodiment of this disclosure. As shown in Figure 6, the first task flow includes four sequentially executed task nodes: task node P1, task node P2, task node P3, and task node P4. Task node P1 is bound to data table #1, task node P2 is bound to data table #2, and task nodes P3 and P4 are all bound to data table #3. According to the spreadsheet workflow described by this first task flow, after the first task flow is triggered, task node P1 is executed first. Task node P1 uses data table #1 to perform corresponding spreadsheet functions, such as calculating the average value of the Value_1 column in data table #1. Next, task node P2 is executed. Task node P2 uses data table #2 to perform the corresponding table functions. Then, task nodes P3 and P4 are executed, and the specific execution process is similar, so it will not be described again. After task nodes P3 and P4 are completed, the first task flow is completed, and the table workflow is automated.

[0056] Furthermore, in one possible implementation, a task node includes a functional node and a logical node. The functional node represents the content of the table function being performed, and each logical node connects to at least two adjacent downstream functional nodes, representing the selection strategy of those adjacent downstream functional nodes. Here, a functional node is the node used to execute a specific table function, while a logical node is the node used to perform logical judgments. The first task flow, constructed by the combination of functional nodes and logical nodes, can achieve more complex workflow logic. For example, a functional node contains execution information, which represents at least one of the following: the execution time of the functional node, the table data corresponding to the functional node, and the modification time of the functional node.

[0057] Figure 7 is a schematic diagram of another first task flow provided in an embodiment of this disclosure. As shown in Figure 7, the first task flow includes one root task node P0 and four sequentially executed task nodes, namely functional node P1, logical node P2, logical node P3, and functional node P4. Task nodes P1 and P3 are bound to data table #1, task node P2 is bound to data table #2, and task node P4 is bound to data table #3. According to the table workflow described in this first task flow, after the first task flow is triggered, the root task node P0 is executed first. The root task node P0 is used to characterize the triggering condition of the first task flow. For example, the triggering condition represented by the root task node P0 is: "Daily 12:00 timed trigger" (shown in the figure as T = 12:00?). That is, when the terminal device detects that the system time is 12:00, the task nodes in this first task flow will be executed. Subsequently, when the root task node meets the triggering condition, according to the structure of the first task flow, functional node P1 is executed first. Functional node P1 is used to perform corresponding table functions using data table #1, such as calculating the average value of value_1 in data table #1 to obtain mean_1. Then, logical node P2 is executed. Logical node P2 is used to judge the mean_1 output by functional node P1 based on a certain value in data table #2 as a judgment threshold_1 (shown in the diagram as mean_1>threshold_1?). If mean_1 is greater than the judgment threshold_1, then functional node P3 is executed; or if mean_1 is less than or equal to the judgment threshold_1, then functional node P4 is executed. For example, functional node P3 is used to calculate the average value of value_2 in data table #1 (mean_2) based on data table #1; functional node P4 is used to send a prompt message to a specific user based on data table #3. Through the first task flow composed of functional nodes and logical nodes, more complex workflow logic can be implemented, achieving a higher degree of automation in the workflow.

[0058] In this embodiment, a target table item containing at least one piece of table data is displayed within a spreadsheet. In response to a first operation instruction, a first task flow corresponding to a table workflow is created within the target table item. This first task flow includes at least two sequentially executed task nodes, each bound to at least one piece of table data within the target table item. The task nodes are used to execute table functions constituting the table workflow based on the table data. The first task flow is then triggered to execute the table workflow. By decomposing the table workflow into multiple table functions and implementing the corresponding table functions through task nodes flexibly bound to the table data within the table item, and then constructing a task flow corresponding to the table workflow, the execution of the table workflow is achieved by triggering the task flow. This realizes a dynamic association between the table workflow and the table data, improving the efficiency of creating and executing the table workflow, reducing the cost of later adjustments to the workflow, and thus improving the interaction and execution efficiency of the application.

[0059] Referring to Figure 8, which is a schematic flowchart of the table workflow processing method provided in this embodiment, this embodiment further refines steps S102 and S103 based on the embodiment shown in Figure 2. The table workflow processing method includes:

[0060] Step S201: Display the target table item in the project operation area of ​​the spreadsheet. The target table item contains at least one piece of table data.

[0061] Step S202: In response to the second operation instruction, create an associated task flow within the target table item, wherein the associated task flow includes at least two ordered sub-task nodes, and the sub-task nodes are used to perform at least one execution step of the table function.

[0062] For example, referring to the application interface diagram of the spreadsheet shown in Figure 3, a target spreadsheet project can be loaded in the project operation area within the spreadsheet's project management interface. Based on this, a related task flow can be created within the target spreadsheet project through a second operation command. This related task flow can be regarded as a task flow called by the first task flow, and it is essentially a data body similar to the first task flow. For example, when the first task flow is used to implement a target function, the related task flow is used to implement the sub-functions in the target function. Specifically, when the spreadsheet function executed by the task node in the first task flow consists of multiple execution steps, the related task flow can be bound to the task node in the first task flow, thereby enabling the task node in the first task flow to implement more complex spreadsheet functions. The at least two ordered sub-task nodes in the related task flow are used to execute at least one execution step of the spreadsheet function.

[0063] The creation process for associated task flows is similar to that of the first task flow. For example, execution steps are added progressively, and the execution logic for each step is set. Optionally, the creation process for associated task flows may also include binding corresponding table data to the associated task flow. This allows the execution steps in the associated task flow to be executed based on the bound table data. The specific creation process for associated task flows can be understood by referring to the creation process of the first task flow, and will not be repeated here.

[0064] Furthermore, for example, since the created associated task flow is also a task flow, it can be marked with the same icon as the first task flow. Of course, different icons can also be used to distinguish between the two, as needed, which will not be elaborated here.

[0065] Step S203: In response to the first operation instruction, based on the associated task flow and table data, create and display the first task flow corresponding to the table workflow within the target table item.

[0066] For example, subsequently, in response to the first operation instruction, a first task flow corresponding to the table workflow is created based on the associated task flow and table data, and the creation process and result are displayed in the spreadsheet. Figure 9 is a schematic diagram of another process for creating a first task flow provided by an embodiment of this disclosure. The creation process of the first task flow will be described below with reference to Figure 9. Referring to Figure 5, firstly, after triggering the creation process of the first task flow L1, icons corresponding to task nodes are added in the spreadsheet (e.g., in the task flow editing area on the right side of the project management interface), such as task node P1, task node P2, etc., as shown in the figure. The specific function of the task node can be determined by editing the above task nodes, such as setting the task node as a functional node or a logical node, and setting the specific functional implementation method or logical judgment method. Then, the table data in the target table project can be bound to it to complete the configuration of the task node. For example, for task node P1, the functional logic Log_1 and data table #1 are manually configured to complete the configuration process of task node P1. On the other hand, associated task flows within the target table item can also be directly bound to task nodes to complete the configuration of that task node. For example, for task node P2, the generated task flow L0 (associated task flow) can be manually configured to task node P2, so that task node P2 executes the steps corresponding to task flow L0. Then, optionally, the terminal device can add downstream adjacent nodes to any of the above task nodes through automatic generation or manual configuration, thereby expanding the workflow. For manual configuration, for example, clicking the "+" icon shown in the figure adds a downstream task node P3 to task node P2, and then configuring task node P3 based on the above method until the construction of the first task flow is completed.

[0067] Step S204: Display the table data page, which is used to display the target table data bound to the task node.

[0068] For example, on the other hand, for the tabular data used in the first task flow, one possible implementation is to trigger a directory item in the first subdirectory under the target tabular item, such as clicking on the specific tabular data name, to display the tabular data page in the spreadsheet. Based on the specific data format of the target tabular data, the tabular data page includes, for example, data tables, text strings, etc., which are the contents of the target tabular data.

[0069] Another possible implementation involves displaying the table data page in response to a fourth operation command for a target task node within the first task flow. Specifically, referring to the first task flow shown in Figure 9, after the first task flow is constructed (or during its construction), the terminal device can display the table data page of the target table data bound to that task node by responding to a fourth operation command input by the user, such as an operation command for a task node. The content of the table data page is consistent with the content of the table data page described above and will not be repeated. This method enables rapid location, display, and modification of the table data used by the task node, improving the interactive efficiency of constructing and adjusting the first task flow.

[0070] Step S205: In response to the third operation instruction for the table data page, modify the target table data to obtain the modified target table data;

[0071] Step S206: Based on the modified target table data, update the first task flow to obtain the second task flow.

[0072] For example, further, after expanding the table data page, the user can further modify the target table data within the table data page by inputting a third operation command to obtain the modified target table data. Then, in some possible implementations, since the downstream task node is generated based on the table data of the upstream task node, after the target table data corresponding to the upstream task node changes, the terminal device will automatically modify the first task flow according to the modified target table data to obtain an automatically synchronized second task flow, thereby completing the dynamic update of the first task flow. In one possible implementation, the updated second task flow adds at least one new task node compared to the first task flow, or removes at least one task node compared to the first task flow.

[0073] For example, as shown in FIG10, the specific implementation of step S206 includes:

[0074] Step S2061: Based on the modified target table data, update the downstream task nodes of the target task node in the first task flow to obtain the updated downstream task nodes.

[0075] Step S2062: Generate a second task flow based on the updated downstream task nodes.

[0076] For example, firstly, after the target table data is modified, based on the modified target table data and the functional logic of the target task node, the task node's automatically generated model is queried to determine the corresponding table functions that need to be executed continuously. Then, based on the table functions, the downstream task nodes of the target task node are updated. Specifically, this may include generating a new downstream task node, deleting the original downstream task node, or adjusting the table data corresponding to the downstream task node to obtain the updated downstream task node. Then, based on the updated downstream task node, a second task flow is generated, which is the updated first task flow.

[0077] In this embodiment, after updating the target table data, the terminal device automatically updates the downstream task nodes of the target task node according to the binding relationship between the target table data and the task node, thereby realizing the automatic update of the first task flow without requiring manual synchronization adjustment by the user. This achieves dynamic binding and linkage between table data and task flow, improving interaction efficiency.

[0078] Optionally, this embodiment also includes:

[0079] Step S207: Receive modification instructions from at least two target users and modify the task nodes in the first task flow;

[0080] Step S208: Display the user identifier corresponding to each target user within the task node.

[0081] For example, after the first task flow is created (or during its creation), the solution provided in this embodiment enables simultaneous modification by multiple users. This involves storing the data corresponding to the first task flow in the cloud, receiving modification instructions from multiple target users through the cloud, and modifying the first task flow. For instance, modifications can be made to the functional logic of task nodes in the first task flow, the table data bound to the task nodes, and the upstream and downstream connections between task nodes. Simultaneously, after the first task flow is modified, a corresponding modification marker, i.e., the user identifier of the target user, will be displayed on the terminal device, thereby identifying the user who modified the aforementioned task flow, further improving the efficiency of task flow creation and modification, as well as the efficiency of multi-user interaction in the spreadsheet.

[0082] In this embodiment, the implementation of step S201 is the same as that of step S101 in the embodiment shown in FIG2 of this disclosure, and will not be described in detail here.

[0083] Corresponding to the table-based workflow processing method in the above embodiments, Figure 11 is a structural block diagram of the table-based workflow processing device provided in this disclosure embodiment. The method described in the above embodiments can be executed by the table-based workflow processing device, which can be implemented by software and / or hardware, and can be integrated into an electronic device with certain data processing capabilities. The electronic device can include, but is not limited to, mobile terminals with big data processing capabilities, and fixed terminals with big data processing capabilities such as desktop computers and supercomputers.

[0084] For ease of explanation, only the parts relevant to embodiments of this disclosure are shown. Referring to FIG11, the processing device 3 for the workflow in the table includes:

[0085] Display module 31 is used to display target table items in a spreadsheet, wherein the target table items contain at least one piece of table data;

[0086] Processing module 32 is used to respond to the first operation instruction to create a first task flow corresponding to the table workflow within the target table item. The first task flow includes at least two ordered task nodes. The task nodes are bound to at least one piece of table data within the target table item. The task nodes are used to execute the table functions that constitute the table workflow based on the table data.

[0087] Execution module 33 is used to trigger the first task flow to execute the table workflow.

[0088] According to one or more embodiments of this disclosure, a target table item has a first subdirectory and a second subdirectory, the directory entries of the first subdirectory are used to characterize table data, the directory entries of the second subdirectory are used to characterize task flow, and the identifier of the first task flow is the directory entry of the second subdirectory.

[0089] According to one or more embodiments of this disclosure, the processing module 32 is specifically configured to: in response to a first operation instruction, create at least one upstream task node in a spreadsheet and configure the table data corresponding to the upstream task node; automatically generate a downstream task node of the upstream task node based on the table function performed by the upstream task node and the corresponding table data; and generate a first task flow based on the upstream task node and the downstream task node.

[0090] According to one or more embodiments of this disclosure, a task node includes a functional node and a logical node. The functional node is used to characterize the content of the table function being performed. The logical node is connected to at least two adjacent downstream functional nodes, and the logical node is used to characterize the selection strategy of the adjacent downstream functional nodes.

[0091] According to one or more embodiments of this disclosure, a functional node includes execution information, which is used to characterize at least one of the following: the execution time of the functional node, the table data corresponding to the functional node, and the modification time of the functional node.

[0092] According to one or more embodiments of this disclosure, the table workflow includes a target table function consisting of multiple execution steps. The execution module 33 is specifically used to: obtain an associated task flow by executing the target function node in the first task flow, the associated task flow including at least two ordered sub-task nodes, the sub-task nodes being used to execute at least one execution step of the table function; and trigger the associated task flow to execute the target table function.

[0093] According to one or more embodiments of this disclosure, the processing module 32 is further configured to: in response to a second operation instruction, create an associated task flow within a target table item, and / or bind corresponding table data to the associated task flow.

[0094] According to one or more embodiments of this disclosure, the display module 31 is further configured to: display a table data page, the table data page being used to display target table data bound to a task node; the processing module 32 is further configured to: in response to a third operation instruction for the table data page, modify the target table data to obtain modified target table data; and update the first task flow based on the modified target table data to obtain a second task flow.

[0095] According to one or more embodiments of this disclosure, the display module 31 is further configured to: display a first task flow; when displaying a table data page, the display module 31 is specifically configured to: display a table data page of the target task node in response to a fourth operation instruction for the target task node in the first task flow; when the processing module 32 updates the first task flow based on the modified target table data to obtain a second task flow, it is specifically configured to: update the downstream task nodes of the target task node in the first task flow based on the modified target table data to obtain updated downstream task nodes; and generate a second task flow based on the updated downstream task nodes.

[0096] According to one or more embodiments of this disclosure, the processing module 32 is further configured to: receive modification instructions sent by at least two target users and modify the task nodes in the first task flow; the display module 31 is further configured to: display the user identifier corresponding to each target user in the task node.

[0097] According to one or more embodiments of this disclosure, the first task flow includes at least one root task node, which is used to characterize the triggering conditions of the first task flow; the execution module 33 is specifically used to: when the root task node meets the triggering conditions, sequentially execute the downstream task nodes of the root task node to execute the table workflow.

[0098] The display module 31, processing module 32, and execution module 33 are connected in sequence. The table workflow processing device 3 provided in this embodiment can execute the technical solution of the above method embodiment, and its implementation principle and technical effect are similar, so it will not be described again here.

[0099] Figure 12 is a schematic diagram of the structure of an electronic device provided in an embodiment of this disclosure. As shown in Figure 12, the electronic device 4 includes:

[0100] Processor 41, and memory 42 communicatively connected to processor 41;

[0101] Memory 42 stores instructions executed by the computer;

[0102] The processor 41 executes computer execution instructions stored in the memory 42 to implement the table workflow processing method in the embodiments shown in Figures 2-10.

[0103] Optionally, the processor 41 and the memory 42 are connected via a bus 43.

[0104] The relevant explanations can be understood by referring to the descriptions and effects of the steps in the embodiments corresponding to Figures 2-10, which will not be elaborated on here.

[0105] This disclosure provides a computer-readable storage medium storing computer-executable instructions. When executed by a processor, these instructions are used to implement the table workflow processing method provided in any of the embodiments corresponding to Figures 2-10 of this disclosure.

[0106] This disclosure provides a computer program product, including a computer program that, when executed by a processor, implements the table workflow processing method provided in any of the embodiments corresponding to Figures 2-10 of this disclosure.

[0107] To implement the above embodiments, this disclosure also provides an electronic device.

[0108] Referring to Figure 13, a schematic diagram of the structure of an electronic device 900 suitable for implementing embodiments of the present disclosure is shown. The electronic device 900 can be a terminal device or a server. The terminal device can include, but is not limited to, mobile terminals such as mobile phones, laptops, digital broadcast receivers, personal digital assistants (PDAs), portable Android devices (PADs), portable media players (PMPs), and in-vehicle terminals (e.g., in-vehicle navigation terminals), as well as fixed terminals such as digital TVs and desktop computers. The electronic device shown in Figure 13 is merely an example and should not be construed as limiting the functionality and scope of the embodiments of the present disclosure.

[0109] As shown in Figure 13, the electronic device 900 may include a processing unit (e.g., a central processing unit, a graphics processing unit, etc.) 901, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 902 or a program loaded from a storage device 908 into a random access memory (RAM) 903. The RAM 903 also stores various programs and data required for the operation of the electronic device 900. The processing unit 901, ROM 902, and RAM 903 are interconnected via a bus 904. An input / output (I / O) interface 905 is also connected to the bus 904.

[0110] Typically, the following devices can be connected to I / O interface 905: input devices 906 including, for example, touchscreens, touchpads, keyboards, mice, cameras, microphones, accelerometers, gyroscopes, etc.; output devices 907 including, for example, liquid crystal displays (LCDs), speakers, vibrators, etc.; storage devices 908 including, for example, magnetic tapes, hard disks, etc.; and communication devices 909. Communication device 909 allows electronic device 900 to communicate wirelessly or wiredly with other devices to exchange data. Although Figure 13 shows electronic device 900 with various devices, 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.

[0111] 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 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 909, or installed from a storage device 908, or installed from a ROM 902. When the computer program is executed by a processing device 901, it performs the functions defined in the methods of embodiments of this disclosure.

[0112] 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 connection 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.

[0113] 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.

[0114] The aforementioned computer-readable medium carries one or more programs, which, when executed by the electronic device, cause the electronic device to perform the methods shown in the above embodiments.

[0115] Computer program code for performing the operations of this disclosure can be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, and C++, and 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).

[0116] 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.

[0117] The units or modules described in the embodiments of this disclosure can be implemented in software or hardware. The names of the units or modules do not necessarily limit the specific unit itself.

[0118] 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 Standard Products (ASSPs), System-on-Chip (SoCs), Complex Programmable Logic Devices (CPLDs), and so on.

[0119] 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.

[0120] In a first aspect, according to one or more embodiments of this disclosure, a method for processing workflows within a table is provided, comprising:

[0121] Display a target table item within the project operation area of ​​the spreadsheet. The target table item contains at least one piece of table data. In response to a first operation instruction, create a first task flow corresponding to a table workflow within the target table item. The first task flow includes at least two ordered task nodes. The task nodes are bound to at least one piece of table data within the target table item. The task nodes are used to execute table functions constituting the table workflow based on the table data. Trigger the first task flow to execute the table workflow.

[0122] According to one or more embodiments of this disclosure, the target table item has a first subdirectory and a second subdirectory, the directory entries of the first subdirectory are used to characterize the table data, the directory entries of the second subdirectory are used to characterize the task flow, and the identifier of the first task flow is the directory entry of the second subdirectory.

[0123] According to one or more embodiments of this disclosure, the task node includes a functional node and a logical node, the functional node being used to characterize the content of the table function being performed, and the logical node being connected to at least two adjacent downstream functional nodes, the logical node being used to characterize the selection strategy of the adjacent downstream functional nodes.

[0124] According to one or more embodiments of this disclosure, the functional node includes execution information, which is used to characterize at least one of the following: the execution time of the functional node, the table data corresponding to the functional node, and the modification time of the functional node.

[0125] According to one or more embodiments of this disclosure, the table workflow includes a target table function consisting of multiple execution steps. Triggering the first task flow to execute the table workflow includes: obtaining an associated task flow by executing the target function node within the first task flow, the associated task flow including at least two ordered sub-task nodes, the sub-task nodes being used to execute at least one execution step of the table function; and triggering the associated task flow to execute the target table function.

[0126] According to one or more embodiments of this disclosure, the method further includes: in response to a second operation instruction, creating the associated task flow within the target table item, and / or binding corresponding table data to the associated task flow.

[0127] According to one or more embodiments of this disclosure, the method further includes: displaying a table data page, the table data page being used to display target table data bound to the task node; modifying the target table data in response to a third operation instruction for the table data page to obtain modified target table data; and updating the first task flow based on the modified target table data to obtain a second task flow.

[0128] According to one or more embodiments of this disclosure, the method further includes: displaying the first task flow; the displaying of the table data page includes: in response to a fourth operation instruction for a target task node within the first task flow, displaying the table data page of the target task node; the updating of the first task flow based on the modified target table data to obtain a second task flow includes: based on the modified target table data, updating the downstream task nodes of the target task node in the first task flow to obtain updated downstream task nodes; and generating the second task flow based on the updated downstream task nodes.

[0129] According to one or more embodiments of this disclosure, the step of creating a first task flow corresponding to a table workflow within the target table item in response to a first operation instruction includes: creating at least one upstream task node within the spreadsheet in response to the first operation instruction, and configuring table data corresponding to the upstream task node; automatically generating a downstream task node of the upstream task node based on the table function performed by the upstream task node and the corresponding table data; and generating the first task flow based on the upstream task node and the downstream task node.

[0130] According to one or more embodiments of this disclosure, the method further includes: receiving modification instructions sent by at least two target users, modifying the task node in the first task flow; and displaying user identifiers corresponding to each target user in the task node.

[0131] According to one or more embodiments of this disclosure, the first task flow includes at least one root task node, which is used to characterize the triggering conditions of the first task flow; triggering the first task flow to execute the table workflow includes: when the root task node meets the triggering conditions, sequentially executing the downstream task nodes of the root task node to execute the table workflow.

[0132] Secondly, according to one or more embodiments of this disclosure, an apparatus for processing in-table workflows is provided, comprising:

[0133] The display module is used to display a target table item in the project operation area of ​​the spreadsheet, wherein the target table item contains at least one piece of table data.

[0134] The processing module is configured to respond to a first operation instruction and create a first task flow corresponding to a table workflow within the target table item. The first task flow includes at least two ordered task nodes. The task nodes are bound to at least one piece of table data within the target table item. The task nodes are configured to execute table functions constituting the table workflow based on the table data.

[0135] An execution module is used to trigger the first task flow to execute the table workflow.

[0136] According to one or more embodiments of this disclosure, the target table item has a first subdirectory and a second subdirectory, the directory entries of the first subdirectory are used to characterize the table data, the directory entries of the second subdirectory are used to characterize the task flow, and the identifier of the first task flow is the directory entry of the second subdirectory.

[0137] According to one or more embodiments of this disclosure, the processing module is specifically configured to: in response to a first operation instruction, create at least one upstream task node in the spreadsheet and configure the table data corresponding to the upstream task node; automatically generate a downstream task node of the upstream task node based on the table function performed by the upstream task node and the corresponding table data; and generate the first task flow based on the upstream task node and the downstream task node.

[0138] According to one or more embodiments of this disclosure, the task node includes a functional node and a logical node, the functional node being used to characterize the content of the table function being performed, and the logical node being connected to at least two adjacent downstream functional nodes, the logical node being used to characterize the selection strategy of the adjacent downstream functional nodes.

[0139] According to one or more embodiments of this disclosure, the functional node includes execution information, which is used to characterize at least one of the following: the execution time of the functional node, the table data corresponding to the functional node, and the modification time of the functional node.

[0140] According to one or more embodiments of this disclosure, the table workflow includes a target table function consisting of multiple execution steps. The execution module is specifically used to: obtain an associated task flow by executing the target function node within the first task flow, the associated task flow including at least two ordered sub-task nodes, the sub-task nodes being used to execute at least one execution step of the table function; and trigger the associated task flow to execute the target table function.

[0141] According to one or more embodiments of this disclosure, the processing module is further configured to: in response to a second operation instruction, create the associated task flow within the target table item, and / or bind corresponding table data to the associated task flow.

[0142] According to one or more embodiments of this disclosure, the display module is further configured to: display a table data page, the table data page being used to display target table data bound to the task node; the processing module is further configured to: modify the target table data in response to a third operation instruction for the table data page, to obtain modified target table data; and update the first task flow based on the modified target table data to obtain a second task flow.

[0143] According to one or more embodiments of this disclosure, the display module is further configured to: display the first task flow; when displaying the table data page, the display module is specifically configured to: display the table data page of the target task node in response to a fourth operation instruction for the target task node in the first task flow; when the processing module updates the first task flow based on the modified target table data to obtain a second task flow, it is specifically configured to: update the downstream task node of the target task node in the first task flow based on the modified target table data to obtain an updated downstream task node; and generate the second task flow based on the updated downstream task node.

[0144] According to one or more embodiments of this disclosure, the processing module is further configured to: receive modification instructions sent by at least two target users, and modify the task node in the first task flow; the display module is further configured to: display the user identifier corresponding to each target user in the task node.

[0145] According to one or more embodiments of this disclosure, the first task flow includes at least one root task node, which is used to characterize the triggering conditions of the first task flow; the execution module is specifically used to: when the root task node meets the triggering conditions, sequentially execute the downstream task nodes of the root task node to execute the table workflow.

[0146] Thirdly, according to one or more embodiments of the present disclosure, an electronic device is provided, comprising: at least one processor and a memory;

[0147] The memory stores computer-executed instructions;

[0148] The at least one processor executes the computer execution instructions stored in the memory, causing the at least one processor to perform the in-table workflow processing method described in the first aspect and various possible designs of the first aspect.

[0149] Fourthly, according to one or more embodiments of the present disclosure, a computer-readable storage medium is provided, wherein computer-executable instructions are stored therein, and when a processor executes the computer-executable instructions, the table workflow processing method described in the first aspect and various possible designs of the first aspect is implemented.

[0150] Fifthly, according to one or more embodiments of this disclosure, a computer program product is provided, including a computer program that, when executed by a processor, implements the in-table workflow processing method described in the first aspect and various possible designs of the first aspect.

[0151] 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.

[0152] 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.

[0153] 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 examples of implementing the claims.

Claims

1. A method for processing workflows within a table, comprising: Display the target table item in the project operation area of ​​the spreadsheet, wherein the target table item contains at least one piece of table data; In response to a first operation instruction, a first task flow corresponding to a table workflow is created within the target table item. The first task flow includes at least two task nodes that are executed in an orderly manner. The task nodes are bound to at least one piece of table data within the target table item. The task nodes are used to execute table functions that constitute the table workflow based on the table data. The first task flow is triggered to execute the table workflow.

2. The method according to claim 1, wherein the target table project within the project operation area has a first subdirectory and a second subdirectory, the directory entries of the first subdirectory are used to characterize the table data, the directory entries of the second subdirectory are used to characterize the task flow, and the identifier of the first task flow is the directory entry of the second subdirectory.

3. The method according to claim 1, wherein the task node includes a functional node and a logical node, the functional node is used to characterize the content of the table function being performed, the logical node is connected to at least two adjacent downstream functional nodes, and the logical node is used to characterize the selection strategy of the adjacent downstream functional nodes.

4. The method according to claim 3, wherein the functional node includes execution information, the execution information being used to characterize at least one of the following: The execution time of the functional node, the table data corresponding to the functional node, and the modification time of the functional node.

5. The method according to claim 3, wherein the table workflow includes a target table function consisting of multiple execution steps, and triggering the first task flow to execute the table workflow includes: By executing the target function node within the first task flow, an associated task flow is obtained. The associated task flow includes at least two ordered sub-task nodes, and the sub-task nodes are used to execute at least one execution step of the table function. The associated task flow is triggered to execute the target table function.

6. The method according to claim 5, wherein the method further comprises: In response to the second operation instruction, the associated task flow is created within the target table item, and / or, the corresponding table data is bound to the associated task flow.

7. The method according to claim 1, wherein the method further comprises: A table data page is displayed within the task flow editing area of ​​the spreadsheet. The table data page is used to display the target table data bound to the task node. In response to a third operation instruction for the table data page, the target table data is modified to obtain the modified target table data; Based on the modified target table data, the first task flow is updated to obtain the second task flow.

8. The method according to claim 7, wherein the method further comprises: The first task flow is displayed in the task flow editing area of ​​the spreadsheet; The page displaying table data includes: In response to a fourth operation command for a target task node within the first task flow, the table data page of the target task node is displayed; The step of updating the first task flow based on the modified target table data to obtain the second task flow includes: Based on the modified target table data, update the downstream task nodes of the target task node in the first task flow to obtain the updated downstream task nodes; The second task flow is generated based on the updated downstream task nodes.

9. The method according to claim 1, wherein creating a first task flow corresponding to a table workflow within the target table item in response to a first operation instruction comprises: In response to the first operation instruction, at least one upstream task node is created in the spreadsheet, and the table data corresponding to the upstream task node is configured. Based on the table function executed by the upstream task node and the corresponding table data, the downstream task node of the upstream task node is automatically generated. The first task flow is generated based on the upstream task node and the downstream task node.

10. The method of claim 1, wherein the method further comprises: Receive modification instructions from at least two target users and modify the task nodes within the first task flow; The user identifier corresponding to each target user is displayed within the task node.

11. The method according to claim 1, wherein the first task flow includes at least one root task node, the root task node being used to characterize the triggering conditions of the first task flow; Triggering the first task flow to execute the table workflow includes: When the root task node meets the triggering condition, the downstream task nodes of the root task node are executed sequentially to execute the table workflow.

12. A processing device for a workflow within a table, comprising: The display module is used to display a target table item in the project operation area of ​​the spreadsheet, wherein the target table item contains at least one piece of table data. The processing module is configured to respond to a first operation instruction and create a first task flow corresponding to a table workflow within the target table item. The first task flow includes at least two ordered task nodes. The task nodes are bound to at least one piece of table data within the target table item. The task nodes are configured to execute table functions constituting the table workflow based on the table data. An execution module is used to trigger the first task flow to execute the table workflow.

13. An electronic device, comprising: Processor and memory; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory, causing the processor to perform the in-table workflow processing method as described in any one of claims 1 to 11.

14. A computer-readable storage medium storing computer-executable instructions that, when executed by a processor, implement the table workflow processing method as described in any one of claims 1 to 11.

15. A computer program product comprising a computer program that, when executed by a processor, implements the in-table workflow processing method as described in any one of claims 1 to 11.

Images