Methods, apparatus, devices, and storage media for processing data tables.

Abstract

The present invention relates to a method, apparatus, device, and storage medium for processing data tables. The method includes, in response to receiving a request to add a target field to a data table, presenting a configuration interface for a target field, the target field being used to indicate the state of a flow corresponding to a data entry in the data table (410); obtaining node configuration information for a set of state nodes corresponding to the flow via the configuration interface, the node configuration information indicating at least a set of fields associated with the completion of the state node in question (420); and adding the target field to the data table based on the node configuration information (430).

Description

Technical Field

[0001] (Cross - reference to Related Applications) This application claims the priority of a Chinese invention patent application titled "Method, Apparatus, Device, and Storage Medium for Processing Data Tables" with an application number of 202311117211.9, filed on August 31, 2023. All the contents of this application are incorporated herein by reference.

[0002] (Field of the Invention) Exemplary embodiments of the present disclosure generally relate to the field of computers, and particularly to methods, apparatuses, devices, and computer - readable storage media for processing data tables.

Background Art

[0003] With the development of computer technology, data tables have already become one of the important tools for people to manage and store data. Users can intuitively obtain data in different fields by using data tables.

[0004] For example, people can use data tables to achieve management for tasks. However, conventional data tables cannot support the control of flow node transfer by users.

Summary of the Invention

Means for Solving the Problems

[0005] A first aspect of this disclosure provides a method for processing a data table. The method includes, in response to receiving a request to add a target field to a data table, presenting a configuration interface for a target field, the target field being used to indicate the state of a flow corresponding to a data entry in the data table; obtaining node configuration information for a set of state nodes corresponding to the flow via the configuration interface, the node configuration information indicating at least a set of fields associated with the completion of the state node in question; and adding the target field to the data table based on the node configuration information.

[0006] A second aspect of the present disclosure provides a method for processing a data table, the method comprising: receiving a request to view a target data entry in a data table, the data table including a target field, the target field being used to indicate the state of a flow corresponding to the target data entry; presenting a first interface associated with the target data entry, the first interface presenting at least a set of fields associated with the current state node of a flow, the current state node being one of a set of state nodes set for the flow; and changing the state of the flow corresponding to the target data entry to indicate that the target state node has been completed, in response to receiving a first pre-configured operation in the first interface.

[0007] A third aspect of the present disclosure provides an apparatus for processing a data table. The apparatus comprises a first presentation module configured to present a configuration interface for a target field in response to receiving a request to add a target field to a data table, the target field being used to indicate the state of a flow corresponding to a data entry in the data table; an information retrieval module configured to retrieve node configuration information for a set of state nodes corresponding to a flow via the configuration interface, the node configuration information being an information retrieval module indicating at least a set of fields associated with the completion of the state node in question; and a field addition module configured to add the target field to the data table based on the node configuration information.

[0008] A fourth aspect of the present disclosure provides an apparatus for processing a data table. The apparatus includes a request receiving module configured to receive a request for viewing a target data entry in a data table, the data table including a target field, the target field being used to indicate the state of a flow corresponding to a target data entry; a second presentation module configured to present a first interface associated with a target data entry, the first interface presenting at least a set of fields associated with the current state node of a flow, the current state node being one of a set of state nodes set for the flow; and a state update module configured to change the state of the flow corresponding to the target data entry in response to receiving a first pre-configured operation in the first interface, to indicate that the target state node has been completed.

[0009] A fifth aspect of the present disclosure provides an electronic device comprising at least one processing unit and at least one memory, the at least one memory being coupled to the at least one processing unit and storing instructions to be executed by the at least one processing unit. When instructions are executed by the at least one processing unit, the device is made to perform a method according to the first or second aspect.

[0010] A sixth aspect of this disclosure provides a computer-readable storage medium in which a computer program is stored, and which can be executed by a processor to implement the method of the first or second aspect.

[0011] The content described in this section is not intended to limit any essential or important features of the embodiments of this disclosure, nor to limit the scope of this disclosure. It should be understood that other features of this disclosure are made clearer by the following description. [Brief explanation of the drawing]

[0012] The above and other features, advantages and aspects of each embodiment of this disclosure will become more apparent by referring to the following detailed description in conjunction with the drawings. In the drawings, the same or similar reference numerals represent the same or similar elements, where, [Figure 1] A schematic diagram of an exemplary environment in which the embodiments described herein can be implemented is shown. [Figure 2A] The following are illustrative interfaces based on several embodiments of the present disclosure. [Figure 2B] The following are illustrative interfaces based on several embodiments of the present disclosure. [Figure 2C] The following are illustrative interfaces based on several embodiments of the present disclosure. [Figure 2D] The following are illustrative interfaces based on several embodiments of the present disclosure. [Figure 2E]An exemplary interface according to some embodiments of the present disclosure is shown. [Figure 2F] An exemplary interface according to some embodiments of the present disclosure is shown. [Figure 2G] An exemplary interface according to some embodiments of the present disclosure is shown. [Figure 2H] An exemplary interface according to some embodiments of the present disclosure is shown. [Figure 3A] An exemplary interface according to some other embodiments of the present disclosure is shown. [Figure 3B] An exemplary interface according to some other embodiments of the present disclosure is shown. [Figure 3C] An exemplary interface according to some other embodiments of the present disclosure is shown. [Figure 3D] An exemplary interface according to some other embodiments of the present disclosure is shown. [Figure 3E] An exemplary interface according to some other embodiments of the present disclosure is shown. [Figure 3F] An exemplary interface according to some other embodiments of the present disclosure is shown. [Figure 4A] A flowchart of an exemplary process for processing a data table according to some embodiments of the present disclosure is shown. [Figure 4B] A flowchart of an exemplary process for processing a data table according to some embodiments of the present disclosure is shown. [Figure 5A] A schematic structural block diagram of an apparatus for processing a data table according to some embodiments of the present disclosure is shown. [Figure 5B] A schematic structural block diagram of an apparatus for processing a data table according to some embodiments of the present disclosure is shown. [Figure 6] A block diagram of an electronic device capable of implementing multiple embodiments of the present disclosure is shown.

Mode for Carrying Out the Invention

[0013] Hereinafter, embodiments of the present disclosure will be described in more detail while referring to the drawings. Although some embodiments of the present disclosure are shown in the drawings, the present disclosure can be realized in various forms and should not be construed as being limited to the embodiments described herein. Rather, it should be understood that these embodiments are provided to more clearly and completely understand the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are merely exemplary and not intended to limit the protection scope of the present disclosure.

[0014] It should be noted that the headings of any section / subsection in this specification are not limiting. In this specification, various embodiments are described throughout, and any type of embodiment may be included in any section / subsection. Additionally, the embodiments described in any one section / subsection can be combined with any other embodiments described in the same section / subsection and / or different sections / subsections in any manner.

[0015] In the description of the embodiments of the present disclosure, the term "comprising" and its similar terms should be understood as non-limiting "comprising", that is, "including but not limited to". The term "based on" should be understood as "at least partially based on". The term "one embodiment" or "this embodiment" should be understood as "at least one embodiment". The term "some embodiments" should be understood as "at least some embodiments". There may also be other explicit or implicit definitions hereinafter. Terms such as "first", "second", etc. may refer to different or the same objects. There may also be other explicit or implicit definitions hereinafter.

[0016] The embodiments of this disclosure may involve user data, data acquisition, and / or use. All of these must comply with applicable laws, regulations, and related provisions. In the embodiments of this disclosure, all data collection, acquisition, processing, manipulation, transfer, and use are contingent on user awareness and consent. Accordingly, when implementing each embodiment of this disclosure, the user should be informed in an appropriate manner, in accordance with applicable laws and regulations, of the type of data or information involved, the scope of use, and the usage scenarios, and permission should be obtained from the user. The specific method of notification and / or permission may vary depending on the actual situation and application scenario, and the scope of this disclosure is not limited in this respect.

[0017] The methods described herein and in the examples, when involving the processing of personal information, are based on a lawful foundation (e.g., obtaining the consent of the data subject or being essential for contractual performance) and are processed only within the specified or agreed-upon scope. Users can refuse the processing of personal information other than that necessary for basic functions, and this will not affect their use of basic functions.

[0018] As briefly mentioned above, data tables have already become an important format for people to manage and organize data. Traditional data tables can help users improve the efficiency of data retrieval, data processing, and other related tasks.

[0019] In some scenarios, people can use data tables, for example, to control and manage flow events (e.g., tasks). However, traditional data tables cannot support the automatic transfer of different node components of a flow, so when people use data tables to control and manage such events, they need to manually manage and control the node state of the flow.

[0020] Embodiments of this disclosure propose a scheme for processing a data table. According to this scheme, in response to receiving a request to add a target field to a data table, a configuration interface for the target field can be presented, where the target field is used to indicate the state of a flow corresponding to a data entry in the data table. Furthermore, node configuration information for a set of state nodes corresponding to the flow can be obtained via the configuration interface, where the node configuration information indicates at least a set of fields associated with the completion of the state node in question. Accordingly, the target field is added to the data table based on the node configuration information.

[0021] Based on the above method, embodiments of the present disclosure can support users adding fields to a data table to characterize the flow state and can support custom control of state transitions. Thereafter, the data table of the present disclosure can support setting flow types, thereby improving processing efficiency by automatically managing switching between different state nodes of the flow.

[0022] Below, we will describe in detail various exemplary implementations of this plan, while further linking them with drawings.

[0023] Figure 1 shows a schematic diagram of an exemplary environment 100 that can realize an embodiment of the present disclosure. In environment 100, an application 120 is installed on a terminal device 110. A user 140 can interact with the application 120 via the terminal device 110 and / or an attached device of the terminal device 110. The application 120 may be a data table application, a table application, a document application, a database application, a flow management application, etc. Alternatively, the application 120 may be a browser that can provide the ability to access and process data tables via, for example, a web page.

[0024] In the environment 100 of Figure 1, when application 120 is active, terminal device 110 can present the interface 150 of application 120. Interface 150 may include various interfaces that application 120 can provide, such as data table editing pages and management pages.

[0025] Although Figure 1 shows that application 120 is included in terminal device 110, it should be understood that some of the processing power of application 120 may be based, for example, at least partially on server 130.

[0026] In some embodiments, terminal device 110 communicates with server 130 to provide services for application 120. Terminal device 110 may be any type of mobile terminal, fixed terminal or portable terminal, and includes mobile phones, desktop computers, laptop computers, notebook computers, netbook computers, tablet PCs, media computers, multimedia tablets, personal communication system (PCS) equipment, personal navigation equipment, personal digital assistants (PDAs), audio / video players, digital cameras / cameras, positioning equipment, television receivers, radio broadcast receivers, e-book equipment, game equipment, or any combination of the foregoing, components and peripherals of these devices, or any combination thereof. In some embodiments, terminal device 110 may also support any type of interface to the user (e.g., “wearable” circuitry). Server 130 may be any type of computing system / server capable of providing computing power, including, but not limited to, mainframes, edge computing nodes, and computing equipment in a cloud environment.

[0027] The structure and function of each element in Environment 100 are described for illustrative purposes only, and should be understood that this does not imply any limitation on the scope of this disclosure.

[0028] Hereinafter, several exemplary embodiments of this disclosure will be described with reference to the drawings.

[0029] The following describes exemplary processes for adding target fields according to some embodiments of the present disclosure with reference to Figures 2A to 2H. Figure 2A shows an exemplary interface 200A according to some embodiments of the present disclosure. Interface 200A may be provided, for example, by terminal equipment 110 shown in Figure 1.

[0030] As shown in Figure 2A, interface 200A represents the editing interface for data table 202. Using Figure 2A as an example, data table 202 may include multiple fields, such as "Task Description," "Task Performer," and "Progress."

[0031] Additionally, data table 202 may further contain one or more data entries, each of which may be a data row in the data table and correspond to a single row of data. Using Figure 2A as an example, data table 202 may contain three data entries corresponding to "Task 1," "Task 2," and "Task 3," describing multi-dimensional information for the respective tasks.

[0032] In some embodiments, the terminal device 110 can receive requests, for example, for adding a target field from the user. For example, the user can select a "flow" field 204 from one or more fields that can be added to the listed data table 202 by clicking the add control "+".

[0033] It should be understood that terminal device 110 may allow adding a target field, such as the "flow" field 204, to an empty data table (i.e., a data table that does not contain any data entries).

[0034] In some embodiments, the "flow" field 204 may be used to indicate the state of the flow corresponding to a data entry in the data table 202. For example, the "flow" field 204 may indicate the state of the task flow corresponding to a data entry that corresponds to a different task.

[0035] Furthermore, after receiving the selection of the "flow" field 204, the terminal device 110 may present, for example, the interface 200B shown in Figure 2B. In interface 200B, the terminal device 110 may present a configuration window 206 (also called a configuration interface) to obtain configuration information regarding this field 204.

[0036] As shown in Figure 2B, in the configuration window 206, the terminal device 110 may present a set of initial state nodes, for example, state node 208, state node 210, and state node 212. Such state nodes 208-212 may be presented in a predetermined order to indicate that the initial transfer order in the flow of state nodes 208-212 is state node 208, state node 210, and then state node 212.

[0037] Furthermore, as shown in Figure 2B, the terminal device 110 can, for example, receive a selection of a state node 208 by the user and present a set of editing options associated with it, such as "background color," "rename," "insert node to left," "insert node to right," and "delete."

[0038] For example, a user can modify the color identifier of state node 208 by clicking the editing option "Background Color". For example, a user can select a color identifier for this state node from a set of candidate color identifiers.

[0039] As another example, a user can modify the text identifier (also called the node name) of state node 208 by, for example, clicking the edit option "Rename". For example, the initial node name of state node 208 is "Create New Task", and the user can enter any custom and appropriate node name.

[0040] As another example, a user can also insert one or more nodes into this pair of initial state nodes by clicking, for example, the editing options "Insert node on the left" and "Insert node on the right".

[0041] As another example, the user can also remove state node 208 from the initial state nodes of this pair by clicking, for example, the "Delete" option.

[0042] In some embodiments, the terminal device 110 can receive edit operations from the user, for example, regarding adjustments to the order of the initial state nodes in this set. For example, the user can change the transfer order of state node 208 and state node 210 in the flow by dragging state node 208 to the right of state node 210.

[0043] The specific interaction methods described above for editing the initial state nodes of this set are merely illustrative, and other suitable interaction methods for performing editing operations such as adding, removing, modifying, and adjusting are also possible, and this disclosure is not intended to limit them.

[0044] As another example, as shown in Figure 2C, the terminal device 110 provides an editing control 214 to support the user in editing the state node 208 currently selected by the editing control 214. For example, the editing control 214 may be used to edit the node identifier of the state node 208, which may include, but is not limited to, text identifiers, color identifiers, and image identifiers. For example, in addition to modifying the node name and background color, the terminal device 110 may also support the user in customizing the graphics or picture corresponding to this state node.

[0045] Additionally, as shown in Figure 2D, the terminal device 110 may also provide an edit control 216 to support the user in entering descriptive information about users who have permission to complete the state node 208. For example, the user may select "Anyone who can edit the current field" to indicate that any user who has permission to edit this field has permission to complete this state node 208.

[0046] As another example, the user may select, for instance, "Specify Field Personnel." Accordingly, terminal device 110 can present a set of personnel fields corresponding to data table 202. Using Figure 2D as an example, this set of personnel fields may include a single personnel field called "Task Performer." It should be understood that if other personnel fields are defined in data table 202, those other personnel fields may be presented as candidates accordingly.

[0047] For example, a user can select the personnel field "Task Performer" to indicate that only the user corresponding to this personnel field "Task Performer" in data table 202 has the authority to complete this state node 208.

[0048] Using data table 202 as an example, as shown in Figure 2A, for the data entry corresponding to "Task 1", the value of the "Task Executor" field is "User A". Therefore, if it is selected that only the "Task Executor" has the authority to complete state node 208, only "User A" will have the authority to complete state node 208, "Create New Task," in the flow corresponding to "Task 1".

[0049] Furthermore, as shown in Figure 2E, the terminal device 110 can also support the user in setting a set of fields associated with the completion of the status node 208. Exemplaryly, the user can trigger a presentation of a set of candidate fields, such as "Task Description," "Task Performer," "Progress," and "Start Date," by clicking the control "Add Field" 218.

[0050] In some embodiments, such a set of candidate fields may correspond to one or more fields in a data entry corresponding to a target field in data table 202, for example. Furthermore, the user can indicate that these two fields should be presented and / or filled in when completing state node 208 by selecting, for example, the "Task Description" field and the "Progress" field.

[0051] Furthermore, as shown in Figure 2F, after selecting the "Task Description" field and the "Progress" field, the user can also indicate whether the corresponding fields are required fields to complete the state node 208 using controls 222 and 224. Using Figure 2F as an example, the "Progress" field may be set by the user as a required field to complete the state node 208.

[0052] In this example, a user authorized to complete state node 208 (e.g., user A) can complete state node 208, so that the flow moves to the next state node only if the "Progress" state has already been filled in.

[0053] This approach allows the embodiments of the present disclosure to improve the efficiency of managing flows using data tables by supporting customization of the state node transfer process in the flow.

[0054] Exemplary, as shown in Figure 2G, a user can determine, for example, by editing initial state nodes 208-212, that the flow corresponding to this data table 202 includes state nodes 226, 228, 230, and 232, and that the transfer order is state node 226, state node 228, state node 230, and state node 232.

[0055] Additionally, terminal device 110 can also receive a first input, for example, by inputting control 234. This first input may indicate state information (e.g., all complete) presented by the target field (e.g., flow field) when all state nodes in this flow (e.g., state nodes 226 to 232) have been completed.

[0056] Additionally, terminal device 110 can receive a second input, for example, by inputting control 236. The second input may indicate state information (e.g., completed) presented by a target field (e.g., flow field) when the flow is terminated, for example, before all state nodes of this flow are completed.

[0057] As a result, using Figure 2G as an example, for a particular data entry, if its current flow state is a state node in the flow, the value of the target field (for example, for the flow field) can indicate the node identifier of the current state node (e.g., text identifier, color identifier, and / or image identifier). If the flow state is a flow completed state, the value of the target field can indicate "All done". If the flow state is a flow terminated state, the value of the target field can indicate "Terminated".

[0058] This allows users to intuitively understand the flow state corresponding to each data entry through the target field.

[0059] In some embodiments, the terminal device 110 may also support, for example, the user setting check information associated with each state node. This check information may be used to indicate, for example, whether the state node satisfies completion conditions based on a set of specified fields in a data table.

[0060] For example, terminal device 110 can support, for instance, a user setting logical decision conditions as check information, such as the value of the field "Actual Completion Date" being earlier than a specific date. That is, when a user requests completion of a particular state node, it can determine, based on the check information, whether the current state node satisfies the completion condition indicated by the check information.

[0061] This method allows the embodiments of the present disclosure to further guarantee the reliability of flow transfer.

[0062] Furthermore, after the user has completed setting the target field (e.g., the flow field) based on the process shown in Figures 2A to 2G, the terminal device 110 and / or server 130 may add the target field to the data table 202. For example, as shown in Figure 2H, the terminal device 110 may display field 204 to indicate that the "flow" field has been added to the data table 202.

[0063] The above describes an exemplary process for adding a target field with reference to Figures 2A to 2H. However, please understand that the specific data information listed in the figures is illustrative and not intended to limit this disclosure.

[0064] The following describes an exemplary interaction process for a data table after adding a target field, with reference to Figures 3A to 3G. Figure 3A shows an exemplary interface 300A according to some embodiments of this disclosure. Interface 300A may be provided, for example, by the terminal device 110 shown in Figure 1.

[0065] As shown in Figure 3A, interface 300A may be, for example, an editing interface for data table 302. Data table 302 may include fields 304 (e.g., flow fields) that have been set up based on the field addition process described above.

[0066] Furthermore, this data table 302 may include, for example, three data entries 306, 308, and 310, which correspond to "Task 1," "Task 2," and "Task 3," respectively, and may be called task entries.

[0067] For example, as shown in Figure 3A, the current state node of the flow corresponding to data entry 306 is "Create New Task," the current state node of the flow corresponding to data entry 308 is "Complete Task," and the current state node of the flow corresponding to data entry 310 is "Following Up."

[0068] Furthermore, the terminal device 110 can receive a request to view data entry 308 and present interface 300B accordingly. As shown in Figure 3B, interface 300B may include a state window 312 to present the flow state of data entry 308 and indicate that the current state node 314 of that flow is "Task Completed".

[0069] Furthermore, the terminal device 110 may provide an entry point 316 for completing the current state node 314 in the state window 312. In some embodiments, the terminal device 110 displays this entry point 316 only if the current user is a user who has the authority to complete the current state node 314 (e.g., user B). The interface having this entry point 316 may be called the first interface.

[0070] Conversely, if the current user does not have the authority to complete the current state node 314, the terminal device 110 does not need to present the entry point 316, and the corresponding browsing interface may be called a second interface.

[0071] As shown in Figure 3B, the state window 312 may present a set of fields 316 corresponding to the current state node 314, such as "Task Description," "Task Performer," and "Progress." It should be understood that such a set of fields 316 may be determined based on the field setting process discussed above, and this will not be explained further here.

[0072] In some embodiments, the set of fields 316 may further include at least one required field 318, for example, a “progress” field, which is set according to the process considered above. If the required field 318 is left blank, the entry point 316 cannot be activated or realized, i.e., the user cannot complete the current state node 314.

[0073] In some embodiments, the values ​​of this pair of fields 316 in the status window 312 may originate from the corresponding fields in the data entry 308 in the data table 302. The user may enter the value of field 318, for example, by input control 320, or the user may return to editing interface 300A, for example, and enter the value of the “Progress” field.

[0074] In some embodiments, the user can trigger the completion of the current state node 314 by clicking the entry point 316. Alternatively, if check information is also set for the current state node 314, the terminal device 110 and / or server 130 may also retrieve the check information corresponding to the current state node 314, which may be used to indicate, for example, whether the current state node 314 satisfies the completion conditions based on a set of specified fields in a data table.

[0075] Furthermore, if it is determined that the current state node 314 satisfies the completion condition, the terminal device 110 can support controlling the process so that the current state node is completed, for example by the user clicking the entry point 316, and the flow automatically moves to the next state node. Conversely, if the current state node 314 does not satisfy the completion condition, the terminal device 110 may, for example, not provide the entry point 316 or set the entry point 316 to an ininteraction-free state.

[0076] For example, after completing the current state node, terminal device 110 may present interface 300C as shown in Figure 3C. In interface 300C, the information 320 in the "Progress" field has already been entered and is, for example, "Completed". Accordingly, terminal device 110 may present the node state 322 of the current state node 314, for example, "Completed".

[0077] Furthermore, after completing the current state node 314, the terminal device 110 can update the "flow" field 304 in the data entry 308, for example, because all state nodes for this data item have already been completed. As shown in Figure 3F, the "flow" field 304 in the data entry 308 may be updated to at least present first state information (e.g., "all complete") corresponding to the configured flow completion state.

[0078] Continuing to refer to Figure 3D, the terminal device 110 can also support, for example, the user terminating the flow corresponding to the current data entry 308. Exemplarily, the user can terminate the flow corresponding to data entry 308 by a pre-configured operation in the interface (for example, clicking the terminate option 324).

[0079] Furthermore, after the flow has ended, the terminal device 110 may present an interface 300E, for example, as shown in Figure 3E. As shown in Figure 3E, the terminal device 110 may indicate that the flow state of the current flow is the flow end state. Furthermore, the terminal device 110 may provide an entry point 326 for recovering the flow.

[0080] After receiving the selection of entry point 326, terminal device 110 may recover the terminated flow and may present interface 300B, for example, as shown in Figure 3B, to support the continued transfer of the flow.

[0081] The above describes the flow transfer process for data entry 308 in data table 302, which allows all flows to be completed, for example, based on the user completing the current state node (task completed).

[0082] As shown in Figure 3E, as another example, for data entry 306, the user may, for example, terminate the corresponding flow. Accordingly, field 304 in this data entry 306 may indicate that the corresponding flow status is "completed".

[0083] As another example, for data entry 310, the user may complete, for example, the state node "Following Up". Since the corresponding flow includes the next state node "Task Completed" after this state node "Following Up", the terminal device 110 may automatically update field 304 in data entry 310 to indicate the node identifier corresponding to this next state node, for example, "Task Completed".

[0084] In another example, when the flow moves to the next state node, the terminal device 110 may trigger sending a reminder message to a user who has permission to complete the next state node (e.g., complete task) to indicate that the state node for this data entry has already been transferred to this user.

[0085] In some embodiments, as shown in Figure 3F, the data item corresponding to field 304 in data entries 306, 308, and 310 may indicate the node identifier (e.g., node name) of the current state node of the corresponding flow.

[0086] In some other embodiments, the terminal device 110 may indicate, for example, the user identifier of the user authorized to complete the current state node by a data item corresponding to field 304. Taking data entry 310 as an example, the value of its field 304 may be, for example, "Complete Task@UserC" to indicate that the user processing the current state node "Complete Task".

[0087] This method allows the embodiments of the present disclosure to improve the efficiency of flow management by further recognizing the flow transfer status to the user.

[0088] Figure 4A shows a flowchart of an exemplary process 400A for processing a data table according to some embodiments of the present disclosure. Process 400A may be implemented in terminal equipment 110, server 130, and / or a combination thereof. Process 400A will be described below with reference to Figure 1.

[0089] As shown in Figure 4A, in response to receiving a request to add a target field to the data table, block 410 presents a configuration interface for the target field, which is used to indicate the flow state corresponding to a data entry in the data table.

[0090] In block 420, node configuration information for a set of state nodes corresponding to a flow is obtained via the configuration interface, and the node configuration information indicates at least a set of fields associated with the completion of the relevant state node.

[0091] In block 430, the target field is added to the data table based on the node configuration information.

[0092] In some embodiments, the node configuration information further indicates whether at least one of a set of fields is a required field to complete the corresponding state node.

[0093] In some embodiments, the node configuration information further provides descriptive information about the user authorized to complete the corresponding state node.

[0094] In some embodiments, obtaining descriptive information via a configuration interface here includes presenting a set of personnel fields corresponding to a data table, receiving a selection of a target personnel field in the set of personnel fields, and indicating that the user corresponding to the target personnel field has the authority to complete the relevant state node.

[0095] In some embodiments, the node configuration information further indicates the node identifiers of a set of state nodes, the node identifiers include text identifiers, color identifiers and / or image identifiers.

[0096] In some embodiments, process 400A further includes receiving a first input via a configuration interface, the first input indicating first state information presented by a target field when a set of state nodes of the flow has been completed, and / or receiving a second input via a configuration interface, the second input indicating second state information presented by a target field when the flow has been terminated before a set of state nodes of the flow has been completed.

[0097] In some embodiments, process 400A further includes presenting a set of initial state nodes arranged in an initial order to a configuration interface, and receiving at least one edit operation on the set of initial state nodes to determine a set of state nodes corresponding to a flow.

[0098] In some embodiments, at least one editing operation includes at least one of the following: adding at least one state node to a set of initial state nodes; removing at least one state node from a set of initial state nodes; modifying the node identifier of at least one node in a set of initial state nodes; and adjusting the initial order of a set of initial state nodes.

[0099] In some embodiments, the node configuration information further indicates check information to show whether the corresponding state node satisfies the completion condition based on a set of specified fields in the data table.

[0100] In some embodiments, a set of fields includes one or more fields in a data entry corresponding to a target field.

[0101] Figure 4B shows a flowchart of an exemplary process 400B for processing a data table according to some embodiments of the present disclosure. Process 400B may be implemented in terminal equipment 110, server 130, and / or a combination thereof. Process 400B will be described below with reference to Figure 1.

[0102] In block 440, a request to view a target data entry in a data table is received. The data table includes a target field, which is used to indicate the flow state corresponding to the target data entry.

[0103] Block 450 presents a first interface associated with a target data entry, the first interface presents at least a set of fields associated with the current state node of the flow, the current state node being one of a set of state nodes set for the flow.

[0104] In block 460, in response to receiving the first pre-configured operation within the first interface, the flow state corresponding to the target data entry is changed to indicate that the target state node has been completed.

[0105] In some embodiments, a set of fields includes at least one required field to complete the current state node.

[0106] In some embodiments, process 400B further includes obtaining check information corresponding to the current state node, the check information indicating whether the current state node satisfies a completion condition based on a set of specified fields of a target data entry, and presenting a first entry to a first interface for completing the target state node in response to the determination that the current state node satisfies a completion condition based on the set of specified fields of the target data entry.

[0107] In some embodiments, presenting a first interface associated with a target data entry includes determining whether the target user responding to a viewing request is authorized to complete the current state condition, and, in response to determining that the target user is authorized, presenting the first interface associated with the target data entry.

[0108] In some embodiments, process 400B further includes presenting a second interface associated with a target data entry in response to determining that the target user has the authority to complete the current state condition, the second interface not providing an entry point for completing the target state node.

[0109] In some embodiments, process 400B further includes updating the target field in a data entry to at least provide the node identifier of the next state node in response to the flow containing the next state node of the target state node, or updating the target field in a data entry to at least provide first state information in response to a set of state nodes in the flow having already completed.

[0110] In some embodiments, process 400B further includes sending a reminder message to a user authorized to complete the next state node in response to the flow containing the next state node after the target state node.

[0111] In some embodiments, process 400B further includes updating a target field in a data entry in response to receiving a second pre-configured operation within a first interface, thereby presenting at least second state information, the second state information indicating that the flow corresponding to the target data entry has been terminated.

[0112] In some embodiments, process 400B further includes providing a second entry point for recovering flows terminated in the first interface.

[0113] In some embodiments, the data item corresponding to the target field in the target data entry indicates at least the node identifier of the flow's current state node and / or the user identifier of the user authorized to complete the current state node.

[0114] The embodiments of this disclosure further provide applicable apparatus for implementing the above method or process.

[0115] Figure 5A shows a schematic structural block diagram of a device 500A for processing data tables according to some embodiments of the present disclosure. The device 500A may be implemented as a terminal device 110 and / or a server 130, or may be included therein. Each module / assembly in the device 500A may be implemented by hardware, software, firmware, or any combination thereof.

[0116] As shown in Figure 5A, the device 500A comprises a first presentation module 510 configured to present a configuration interface for a target field in response to receiving a request to add a target field to a data table, wherein the target field is used to indicate the state of a flow corresponding to a data entry in the data table; a configuration acquisition module 520 configured to acquire node configuration information for a set of state nodes corresponding to the flow via the configuration interface, wherein the node configuration information indicates at least a set of fields associated with the completion of the state node in question; and a field addition module 530 configured to add the target field to the data table based on the node configuration information.

[0117] In some embodiments, the node configuration information further indicates whether at least one of a set of fields is a required field to complete the corresponding state node.

[0118] In some embodiments, the node configuration information further provides descriptive information about the user authorized to complete the corresponding state node.

[0119] In some embodiments, obtaining descriptive information via a configuration interface here includes presenting a set of personnel fields corresponding to a data table, receiving a selection of a target personnel field in the set of personnel fields, and indicating that the user corresponding to the target personnel field has the authority to complete the relevant state node.

[0120] In some embodiments, the node configuration information further indicates the node identifiers of a set of state nodes, the node identifiers include text identifiers, color identifiers and / or image identifiers.

[0121] In some embodiments, the device 500A may further include an input module configured to receive a first input via a configuration interface, the first input indicating first state information presented by a target field when a set of state nodes of the flow has been completed, and / or receive a second input via a configuration interface, the second input indicating second state information presented by a target field when the flow has been terminated before a set of state nodes of the flow has been completed.

[0122] In some embodiments, the device 500A further comprises an editing module configured to present a set of initial state nodes arranged in an initial order to a configuration interface, and to receive at least one editing operation on the set of initial state nodes to determine a set of state nodes corresponding to a flow.

[0123] In some embodiments, at least one editing operation includes at least one of the following: adding at least one state node to a set of initial state nodes; removing at least one state node from a set of initial state nodes; modifying the node identifier of at least one node in a set of initial state nodes; and adjusting the initial order of a set of initial state nodes.

[0124] In some embodiments, the node configuration information further indicates check information to show whether the corresponding state node satisfies the completion condition based on a set of specified fields in the data table.

[0125] In some embodiments, a set of fields includes one or more fields in a data entry corresponding to a target field.

[0126] Figure 5B shows a schematic structural block diagram of a device 500B for processing data tables according to some embodiments of the present disclosure. The device 500B may be implemented as a terminal device 110 and / or a server 130, or may be included therein. Each module / assembly in the device 500B may be implemented by hardware, software, firmware, or any combination thereof.

[0127] As shown in Figure 5B, the device 500B comprises a request receiving module 540 configured to receive a request to view a target data entry in a data table, the data table including a target field, the target field being used to indicate the state of a flow corresponding to the target data entry; a second presentation module 550 configured to present a first interface associated with the target data entry, the first interface presenting at least a set of fields associated with the current state node of the flow, the current state node being one of a set of state nodes set for the flow; and a state update module 560 configured to change the state of the flow corresponding to the target data entry in response to receiving a first pre-configured operation in the first interface, to indicate that the target state node has been completed.

[0128] In some embodiments, a set of fields includes at least one required field to complete the current state node.

[0129] In some embodiments, the device 500B further comprises a check module that acquires check information corresponding to the current state node, the check information indicating whether to determine whether the current state node satisfies a completion condition based on a set of designated fields of a target data entry, and presenting a first entry to a first interface for completing the target state node in response to the determination that the current state node satisfies a completion condition based on the set of designated fields of the target data entry.

[0130] In some embodiments, presenting a first interface associated with a target data entry includes determining whether the target user responding to a viewing request is authorized to complete the current state condition, and, in response to determining that the target user is authorized, presenting the first interface associated with the target data entry.

[0131] In some embodiments, the device 500B further comprises an authorization determination module configured to present a second interface associated with a target data entry in response to a determination that the target user has the authority to complete the current state condition, the second interface not providing an entry point for completing the target state node.

[0132] In some embodiments, the device 500B further comprises a first update module configured to update a target field in a data entry to at least present the node identifier of the next state node in response to the flow including the next state node of a target state node, or to update a target field in a data entry to at least present first state information in response to a set of state nodes in the flow having already been completed.

[0133] In some embodiments, the device 500B further comprises a reminder module configured to send a reminder message to a user authorized to complete the next state node in response to the flow containing the next state node after the target state node.

[0134] In some embodiments, the device 500B further comprises a second update module configured to update a target field in a data entry in response to receiving a second pre-configured operation within a first interface, thereby providing at least second status information, which indicates that the flow corresponding to the target data entry has been terminated.

[0135] In some embodiments, the device 500B further comprises an inlet providing module configured to provide a second inlet for recovering flows terminated at the first interface.

[0136] In some embodiments, the data item corresponding to the target field in the target data entry indicates at least the node identifier of the flow's current state node and / or the user identifier of the user authorized to complete the current state node.

[0137] Figure 6 shows a block diagram of an electronic device 600 that can implement one or more embodiments of the present disclosure. It should be understood that the electronic device 600 shown in Figure 6 is illustrative and does not imply any limitation on the functionality and scope of the embodiments described herein. The electronic device 600 shown in Figure 6 may be used to implement the terminal device 110 and / or server 130 of Figure 1.

[0138] As shown in Figure 6, the electronic device 600 is a general-purpose electronic device. The components of the electronic device 600 may include, but are not limited to, one or more processors or processing units 610, memory 620, storage devices 630, one or more communication units 640, one or more input devices 650, and one or more output devices 660. The processing unit 610 may be an actual or virtual processor and can perform various processes based on a program stored in memory 620. In a multiprocessor system, multiple processing units execute computer-executable instructions in parallel to improve the parallel processing capability of the electronic device 600.

[0139] The electronic device 600 generally includes multiple computer storage media. Such media may be any obtainable media accessible to the electronic device 600, and may include, but are not limited to, volatile and non-volatile media, and removable and non-removable media. Memory 620 may be volatile memory (e.g., registers, caches, random access memory (RAM)), non-volatile memory (e.g., read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory), or any combination thereof. Storage device 630 may be removable or non-removable media, and may include machine-readable media, such as flash memory drives, magnetic disks, or any other media, which can be used to store information and / or data and are accessible within the electronic device 600.

[0140] The electronic device 600 may further include other removable / non-removable, volatile / non-volatile storage media. Not shown in Figure 6, a magnetic disk drive for reading from or writing to removable, non-volatile magnetic disks (e.g., “floppy disks”) and an optical disk drive for reading from or writing to removable, non-volatile optical disks may be provided. In these cases, each drive may be connected to a bus (not shown) by one or more data media interfaces. The memory 620 may also include a computer program product 625, which includes one or more program modules, these program modules configured to perform various methods or operations of various embodiments of the present disclosure.

[0141] The communication unit 640 enables communication with other electronic devices via a communication medium. Additionally, the functions of the components of the electronic device 600 can be implemented by a single computing cluster or multiple computing machines, which can communicate via a communication connection. Therefore, the electronic device 600 can operate in a network environment using logical connections with one or more other servers, network personal computers (PCs), or other network nodes.

[0142] The input device 650 may be one or more input devices, such as a mouse, keyboard, or trackball. The output device 660 may be one or more output devices, such as a display, speaker, or printer. The electronic device 600 may further communicate with one or more external devices (not shown), such as a storage device or display device, via the communication unit 640 as needed, with one or more devices for user interaction with the electronic device 600, or with any devices (e.g., a network card or modem) for communication between the electronic device 600 and one or more other electronic devices. Such communication may be performed via an input / output (I / O) interface (not shown).

[0143] An exemplary embodiment of the present disclosure provides a computer-readable storage medium in which computer-executable instructions are stored, wherein the computer-executable instructions implement a method that is executed by a processor and described above. An exemplary embodiment of the present disclosure further provides a computer program product which includes computer-executable instructions that are tangibly stored in a non-temporary computer-readable medium, wherein the computer-executable instructions implement a method that is executed by a processor and described above.

[0144] Herein, each aspect of the disclosure is described with reference to flowcharts and / or block diagrams of methods, apparatus, devices, and computer program products implemented pursuant to the disclosure. It should be understood that each block in the flowcharts and / or block diagrams, and each combination of blocks in the flowcharts and / or block diagrams, can be implemented by computer-readable program instructions.

[0145] By providing these computer-readable program instructions to the processing units of a general-purpose computer, a dedicated computer, or other programmable data processing device, a machine can be generated, thereby generating a device that, when these instructions are executed by the processing units of the computer or other programmable data processing device, implements the functions / operations defined in one or more blocks in a flowchart and / or block diagram. These computer-readable program instructions may be stored in a computer-readable storage medium, and by using these instructions to operate a computer, programmable data processing device, and / or other device in a specific manner, the computer-readable medium storing the instructions will contain a product containing instructions that implement various modes of the functions / operations defined in one or more blocks in a flowchart and / or block diagram.

[0146] Computer-readable program instructions may be loaded into a computer, other programmable data processing device, or other device, thereby generating a process implemented by the computer by executing a series of operational steps on the computer, other programmable data processing device, or other device, and thereby the instructions executed on the computer, other programmable data processing device, or other device implement the functions / operations defined in one or more blocks in a flowchart and / or block diagram.

[0147] The flowcharts and block diagrams in the drawings illustrate the implementable system architectures, functions, and operations of systems, methods, and computer program products in multiple implementations of the present disclosure. In this regard, each block in a flowchart or block diagram may represent a module, program segment, or part of an instruction, and a module, program segment, or part of an instruction may contain one or more executable instructions for implementing a defined logical function. In some implementations as replacements, the functions described in a block may occur in a different order than those shown in the drawings. For example, two consecutive blocks may actually be executed essentially in parallel, or in reverse order depending on the function. Note that each block in a block diagram and / or flowchart, and combinations of blocks in a block diagram and / or flowchart, may be implemented by a dedicated hardware-based system that performs the defined function or operation, or by a combination of dedicated hardware and computer instructions.

[0148] The above descriptions of the various realizations of this disclosure are illustrative, not exhaustive, and not limited to the realizations disclosed. Many modifications and changes will be apparent to those skilled in the art without departing from the scope and spirit of the realizations described. The choice of terms used herein is intended to best interpret the principles of each realization, actual applications, or improvements in the technology in the market, or to enable those other skilled in the art to understand each realization disclosed herein.

Claims

1. In response to receiving a request to add a target field to a data table, the system presents a configuration interface for the target field, wherein the target field is used to indicate the flow state corresponding to a data entry in the data table. Obtaining node configuration information for a set of state nodes corresponding to the flow via the configuration interface, wherein the node configuration information indicates at least a set of fields associated with the completion of the corresponding state node, This includes adding the target field to the data table based on the node configuration information, How to process a data table.

2. The node configuration information is, The method according to claim 1, further indicating whether at least one of the set of fields is a required field for completing the corresponding state node.

3. The node configuration information is, The method according to claim 1, further providing descriptive information about a user who has the authority to complete the corresponding state node.

4. Obtaining the descriptive information via the aforementioned configuration interface means that To present a set of personnel fields corresponding to the aforementioned data table, The method according to claim 3, comprising receiving the selection of a target personnel field in the set of personnel fields and indicating that the user corresponding to the target personnel field has the authority to complete the corresponding state node.

5. Node configuration information is, The method according to claim 1, further indicating the node identifiers of the set of state nodes, wherein the node identifiers include a text identifier, a color identifier and / or an image identifier.

6. Receiving a first input via the configuration interface, wherein the first input indicates first state information presented by the target field when the set of state nodes in the flow is completed, and / or The method according to claim 1, further comprising receiving a second input via the configuration interface, the second input indicating a second state information presented by the target field when the flow is terminated before the set of state nodes of the flow is completed.

7. The configuration interface presents a set of initial state nodes arranged in an initial order, The method according to claim 1, further comprising receiving at least one edit operation relating to the set of initial state nodes and determining the set of state nodes corresponding to the flow.

8. The aforementioned at least one editing operation is, Adding at least one state node to the aforementioned set of initial state nodes, Removing at least one state node from the aforementioned set of initial state nodes, Modify the node identifier of at least one node among the set of initial state nodes, The method according to claim 7, comprising at least one of adjusting the initial order of the set of initial state nodes.

9. The node configuration information is, The method according to claim 1, further providing check information to indicate whether the corresponding state node satisfies a completion condition based on a set of specified fields in the data table.

10. The method according to claim 1, wherein the set of fields includes one or more fields in a data entry corresponding to the target field.

11. Receiving a request to view a target data entry in a data table, wherein the data table includes a target field, and the target field is used to indicate the flow state corresponding to the target data entry. Presenting a first interface associated with the target data entry, wherein the first interface presents at least a set of fields associated with the current state node of the flow, and the current state node is one of a set of state nodes set for the flow. This includes, in response to receiving a first pre-configured operation within the first interface, changing the state of the flow corresponding to the target data entry to indicate that the target state node has been completed, How to process a data table.

12. The method according to claim 11, wherein the set of fields includes at least one required field to complete the current state node.

13. Obtaining check information corresponding to the current state node, wherein the check information indicates whether the current state node satisfies the completion condition based on a set of specified fields of the target data entry. The method according to claim 11, further comprising presenting a first entry point to the first interface for completing the target state node in response to the determination that the current state node satisfies the completion condition by the set of designated fields of the target data entry.

14. Presenting the first interface associated with the aforementioned target data entry is: Determining whether the target user corresponding to the viewing request has the authority to complete the current state conditions, The method according to claim 11, further comprising presenting the first interface associated with the target data entry in response to the determination that the target user has the authority.

15. The method of claim 14, further comprising presenting a second interface associated with the target data entry in response to the determination that the target user has the authority to complete the current state condition, wherein the second interface does not provide an entry point for completing the target state node.

16. In response to the flow including the next state node of the target state node, update the target field in the data entry to at least indicate the node identifier of the next state node, or The method according to claim 11, further comprising updating the target field in a data entry to present at least first state information in response to the completion of the set of state nodes in the flow.

17. The method according to claim 16, further comprising sending a reminder message to a user authorized to complete the next state node in response to the flow including the next state node of the target state node.

18. The method according to claim 11, further comprising updating the target field in a data entry in response to receiving a second pre-configured operation in the first interface to present at least second state information, the second state information indicating that the flow corresponding to the target data entry has been terminated.

19. The method according to claim 18, further comprising providing a second entry point for recovering the flow terminated in the first interface.

20. The data item corresponding to the target field in the target data entry is: The node identifier of the current state node of the flow, and / or The method according to claim 11, wherein at least the user identifier of a user who has the authority to complete the current state node is indicated.

21. A first presentation module configured to present a configuration interface for a target field in response to receiving a request to add a target field to a data table, wherein the target field is used to indicate the flow state corresponding to a data entry in the data table. An information acquisition module configured to acquire node configuration information for a set of state nodes corresponding to the flow via the configuration interface, wherein the node configuration information includes an information acquisition module that indicates at least a set of fields associated with the completion of the state node, The system includes a field addition module configured to add the target field to the data table based on the node configuration information, A device for processing data tables.

22. A request receiving module configured to receive a request to view a target data entry in a data table, wherein the data table includes a target field, and the target field is used to indicate the flow state corresponding to the target data entry. A second presentation module configured to present a first interface associated with the target data entry, wherein the first interface presents at least a set of fields associated with the current state node of the flow, and the current state node is one of a set of state nodes set for the flow. The system includes a state update module configured to change the state of the flow corresponding to the target data entry in response to receiving a first pre-configured operation within the first interface, to indicate that the target state node has been completed. A device for processing data tables.

23. At least one processing unit, An electronic device comprising at least one memory, wherein the at least one memory is coupled to the at least one processing unit and stores instructions to be executed by the at least one processing unit, and when the instructions are executed by the at least one processing unit, the electronic device is made to perform the method according to any one of claims 1 to 10 or 11 to 20. electronic equipment.

24. A computer program is stored which is executed by a processor and which can implement the method described in any one of claims 1 to 10 or 11 to 20. Computer-readable storage medium.

Images