Information processing methods, apparatus, electronic devices, storage media, and computer programs

Abstract

This disclosure provides information processing methods, apparatus, electronic devices, storage media, and program products. The method includes receiving a first operation on a first schedule, the first schedule comprising at least one first-level subnode and at least one second-level subnode, the second-level subnode being associated with at least one role, and displaying a swimlane view corresponding to the first schedule, the swimlane view displaying progress status information of at least one second-level subnode associated with at least one role.

Description

Technical Field

[0001] [Cross - reference to related applications] This application claims the priority of a Chinese patent application with an application number of 202410669261.6 and an invention title of "Information Processing Method, Apparatus, Electronic Device, Storage Medium and Program Product", which was filed with the China National Intellectual Property Administration on May 27, 2024, and all of its content is incorporated into this application by reference.

[0002] [Technical Field] This disclosure relates to the field of computer technology, and particularly to information processing methods, apparatuses, electronic devices, storage media and program products.

Background Art

[0003] With the development of computers, users can use electronic devices to realize various functions. For example, users can interact with other users through electronic devices and can also use electronic devices to promote work.

[0004] In some scenarios, by constructing a tool or platform based on data management (such as a project management system) and creating a standardized business process, the onlineization of projects can be accelerated and project risks can be avoided.

Summary of the Invention

Problems to be Solved by the Invention

[0005] In view of this, the purpose of this disclosure is to propose an information processing method, apparatus, electronic device, storage medium and program product.

Means for Solving the Problems

[0006] Based on the above objectives, the first aspect of this disclosure provides an information processing method, and this method is Receiving a first operation on a first schedule, wherein the first schedule includes at least one first-level subnode and at least one second-level subnode, and the second-level subnode is associated with at least one role. Displaying a swimlane view corresponding to the first schedule, wherein the swimlane view displays progress information for at least one second-level subnode associated with at least one role.

[0007] In some embodiments, displaying the swimlane view corresponding to the first schedule is: The functionality includes displaying a node subgraph region based on a role list, wherein the node graph blocks in the node subgraph region are configured to correspond to the second-level subnodes, and the node graph blocks corresponding to the second-level subnodes associated with the same role in the role list are located in the same swimlane in the swimlane view.

[0008] In some embodiments, the method is In response to the progress status of the second-level subnode being complete, the node graph block corresponding to the second-level subnode is marked with a first identifier, In response to the progress status of the second-level subnode being incomplete, the node graph block corresponding to the second-level subnode is marked with a second identifier, The further includes determining the progress status information of the second-level subnode based on the first identifier and the second identifier.

[0009] In some embodiments, the method is The method further includes displaying node information of a second-level subnode corresponding to the node graph block in response to a trigger operation on the node graph block, The node information includes at least one of the following: node name, progress status, associated user, scheduled start time, scheduled end time, actual start time, actual end time, and postponement time.

[0010] In some embodiments, the method herein displays the swimlane view corresponding to the first schedule, The flow subgraph region is displayed based on a time axis, wherein the subflow blocks in the flow subgraph region are set to correspond to the first level subnodes. The further includes setting the subflow block corresponding to the first-level subnode and the node graph block corresponding to at least one second-level subnode related to this first-level subnode in the same row or column.

[0011] In some embodiments, the method is The further includes displaying the node graph blocks in the node subgraph region based on the time axis.

[0012] In some embodiments, the method is The method further includes displaying the subflow block as a pre-configured graphic in response to a configuration operation on the subflow block in the flow subgraph region. The aforementioned pre-configured graphics include at least one of the following shapes: rectangle, trapezoid, funnel, triangle, and polygon.

[0013] In some embodiments, the method is In response to the progress status of the first-level subnode being completed or partially completed, the subflow block corresponding to the first-level subnode is marked with a third identifier, In response to the progress status of the first-level subnode being incomplete or partially incomplete, the subflow block corresponding to the first-level subnode is marked with a fourth identifier, The further includes determining the progress status information of the first-level subnode based on the third identifier and the fourth identifier.

[0014] In some embodiments, the method is In response to setting the first target node among the second-level subnodes as the first type node, the first node identifier corresponding to the first type node is displayed in the flow subgraph area, The method further includes at least one of the following: setting the second target node among the second level subnodes as a second type node, and displaying a second node identifier corresponding to the second type node in the flow subgraph region.

[0015] In some embodiments, the node graph block displayed in the node subgraph area by the first target node is the same as the first node identifier displayed in the flow subgraph area, and the node graph block displayed in the node subgraph area by the second target node is the same as the second node identifier displayed in the flow subgraph area.

[0016] In some embodiments, the method is In response to a trigger operation on the subflow block, the method further includes displaying node information of the first-level subnode corresponding to the subflow block, The node information includes at least one of the following: node name, progress status, scheduled start time, scheduled end time, actual start time, actual end time, delay time, included first type node, and included second type node.

[0017] In some embodiments, the method is In response to a trigger operation on the first node identifier, displaying node information of a first target node corresponding to the first node identifier, where the node information includes at least one of a node name, a progress status, a scheduled end time, an actual end time, a delay time, and a related user. Or, In response to a trigger operation on the second node identifier, displaying node information of a second target node corresponding to the second node identifier, where the node information further includes at least one of a node name, a progress status, a scheduled end time, an actual end time, a delay time, and a related user.

[0018] In some embodiments, the method includes Displaying a node form of the first type of node for performing a second operation on the first type of node in response to an expansion operation on the first type of node. Or, Further including displaying a node form of the second type of node for performing a third operation on the second type of node in response to an expansion operation on the second type of node.

[0019] In some embodiments, the method includes Further including displaying only the first type of node and / or the second type of node in response to a configuration operation on the swimlane view.

[0020] In some embodiments, the method includes Further including displaying or canceling the display of the dependency relationship between the second-level sub-nodes in response to a configuration operation on the swimlane view.

[0021] In some embodiments, the method includes In response to a step size switching operation based on the time axis, the lengths of the node graph block and the subflow block are modified, The further includes, at least one of displaying the node graph block and the subflow block for a time range corresponding to a time positioning operation based on a time axis, in response to the time positioning operation.

[0022] In some embodiments, the method is In response to the fourth operation on the first schedule, display only the flow subgraph area of ​​the swimlane view, The further includes displaying the swimlane view in response to a fifth operation on the flow subgraph region of the swimlane view.

[0023] A second aspect of this disclosure provides an information processing device, which is A receiving module configured to receive a first operation on a first schedule, wherein the first schedule includes at least one first-level subnode and at least one second-level subnode, and the second-level subnode is associated with at least one receiving module in a role. A display module configured to display a swimlane view corresponding to the first schedule, wherein the swimlane view includes a display module that displays progress status information for at least one second-level subnode associated with at least one role.

[0024] A third aspect of the present disclosure provides an electronic device comprising memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the method of the first aspect is realized when the processor executes the program.

[0025] A fourth aspect of the present disclosure provides a non-temporary computer-readable storage medium having computer instructions stored therein, which are used to cause the computer to perform the method described in the first aspect.

[0026] A fifth aspect of this disclosure provides a computer program product which includes computer program instructions, and when the computer program instructions are executed on a computer, the computer causes the computer to perform the method described in the first aspect. [Brief explanation of the drawing]

[0027] To more clearly illustrate the technical concepts in this disclosure or related technologies, the following briefly introduces the drawings that may be used in the examples or related technical descriptions. Obviously, the drawings in the following descriptions are merely examples of the disclosure, and those skilled in the art can obtain other drawings based on these drawings without any creative effort. [Figure 1] A flowchart of one exemplary method according to an embodiment of the present disclosure is shown. [Figure 2A] A schematic diagram of one exemplary page according to an embodiment of this disclosure is shown. [Figure 2B] A schematic diagram of one exemplary page according to an embodiment of this disclosure is shown. [Figure 2C] A schematic diagram of one exemplary page according to an embodiment of this disclosure is shown. [Figure 2D] A schematic diagram of one exemplary page according to an embodiment of this disclosure is shown. [Figure 2E] A schematic diagram of one exemplary page according to an embodiment of this disclosure is shown. [Figure 2F] A schematic diagram of one exemplary page according to an embodiment of this disclosure is shown. [Figure 2G] A schematic diagram of one exemplary page according to an embodiment of this disclosure is shown. [Figure 3] A schematic diagram of one exemplary apparatus according to an embodiment of the present disclosure is shown. [Figure 4] A schematic diagram of the hardware structure of an exemplary computer device according to an embodiment of this disclosure is shown. [Modes for carrying out the invention]

[0028] To make the purpose, technical proposal, and advantages of this disclosure clearer, the disclosure will be described in more detail below with reference to the drawings, along with specific examples.

[0029] Unless otherwise defined, technical or scientific terms used in the embodiments of this disclosure should have the general meaning understood by a person of general skill in the art to which this disclosure belongs. The terms “first,” “second,” and similar terms used in the embodiments of this disclosure do not indicate any order, number, or importance, but are used solely to distinguish different components. Similar terms such as “include” or “incorporate” mean that the element or substance appearing before it includes the enumerated elements or substances and their equivalents appearing after it, but do not exclude other elements or substances. Similar terms such as “connected” or “linked” are not limited to physical or mechanical connections, but may include electrical connections, whether direct or indirect. Terms such as “up,” “down,” “left,” and “right” are used solely to describe relative positional relationships, and these relative positional relationships change accordingly as the absolute position of the object being described changes.

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

[0031] For the sake of clarity, we will first introduce some concepts that may be relevant to this disclosure.

[0032] Space is the basic unit through which organizations collaborate, and it can be the management of a single project or the union of multiple projects.

[0033] A work item is a task that a team works on collaboratively, and may be the union of the components of a project. Work items vary in content and may be divided into different types, such as demand, defects, versions, iterations, and milestones.

[0034] A "feature" can refer to a software function that a user needs to solve a problem or achieve a goal, and it can help team members track specific, detailed issues.

[0035] A defect (issue) is when the system fails to meet the initially defined business requirements. For example, a pop-up window might not appear.

[0036] A view is a fixed collection of frequently focused work items within a team, queried by a dimension, and may also be called a view dual item. Views can have various types, such as tables, lists, signs, Gantt charts, and metrics. A table may be a permutation combination of field information that arranges data in cell mode. A Gantt chart can display project progress in a time dimension using bar charts. Metrics are an ongoing quantification process that defines, collects, and analyzes data for software development projects, processes, and their products. Examples include demand throughput, quality, cycle, and manpower score. Source data is data that measures the entire work item in a directional manner. For example, source data may include work items, such as demand, defects, versions, and iterations. Source data may also include view data, such as ongoing demand pools, defects to be handled, and personally customized view names. Source data may also include a single instance, for example, a data range that is a specific demand, defect, version, and iteration.

[0037] A "role" refers to the various roles involved in a project, and a single project requires the cooperation and support of people in different roles.

[0038] A work plan, also known as a WBS (Work Breakdown Structure) plan, allows you to define work items as nodes, flows, or tasks. Schedules and scores can be set for each node or task.

[0039] The schedule may include a start time and an end time. The length of the schedule may be called the project duration. The score may be the personnel allocation, calculated, for example, in units of people / day (i.e., one person per day).

[0040] Currently, the data management tools or platforms are unable to meet user needs based on their current view displays.

[0041] Based on the background technology description, current project management systems generally use a node-based flow query method for viewing projects. However, in some scenarios, such as Integrated Product Development (IPD), the number of project nodes is large, and displaying views based on nodes can interfere with the user experience to a relatively large extent, thus failing to meet user needs.

[0042] In view of this, the embodiments of the present disclosure can be presented based on different roles, thereby providing an information processing method that allows users with different roles in the project progress process to view relevant content and gain an overall understanding of project progress.

[0043] As shown in Figure 1, the information processing method includes the following:

[0044] Step S101, a first operation is received on a first schedule, the first schedule including at least one first-level subnode and at least one second-level subnode, the second-level subnode being associated with at least one role.

[0045] Here, the first plan may be a plan corresponding to a first project in a first system, and the first system may be, for example, a project management system. The first plan includes at least one first-level subnode and at least one second-level subnode, where each first-level subnode may be associated with one or more second-level subnodes, for example, one first-level subnode may include one or more second-level subnodes, or a first-level subnode may not include any second-level subnodes, and this embodiment is not limited thereto.

[0046] In some embodiments, the first-level subnodes may be nodes representing the state or stage of a first project, such as the conceptual stage, planning stage, development stage, verification stage, and delivery stage. The second-level subnodes are nodes representing the specific content of the first-level node to which they belong, such as specific work items, tasks, matters, or milestones, and this embodiment is not limited to these.

[0047] In this embodiment, the execution body of the information processing method (e.g., a server and / or terminal equipment) can perform a first operation on the first schedule at the schedule presentation interface of the first system. The first operation on the first schedule may be a view display operation on the first schedule, for example, an operation to open a view display page for the first schedule, and this embodiment is not limited thereto.

[0048] In some embodiments, a swimlane view corresponding to a first schedule may be displayed on the view display page of the first schedule by a configuration operation of a first type of user of the first system. The first type of user may be an administrator of the first system, a flow configurator, etc. This view display page may be, for example, a pre-configured location on the instance details page of the first schedule, or the flowchart tab page of the instance details page of the first schedule, and this embodiment is not limited thereto.

[0049] In some embodiments, a configuration operation by a first type of user of the first system causes the swimlane view corresponding to the first schedule to be displayed by default on the view display page of the first schedule. Alternatively, a second type of user of the first system (e.g., an instance-side user, i.e., a user corresponding to the relevant role of each node in the first schedule) may configure whether or not to display this swimlane view on the view display page of the first schedule, and this embodiment is not limited to this.

[0050] In some embodiments, a configuration operation by a first type of user of the first system may cause the view display page of the first schedule to default to displaying the swimlane view corresponding to the first schedule, and other types of views such as tables, lists, signs, and Gantt charts of the first schedule to not be displayed. Alternatively, a configuration operation by a first type of user of the first system may allow users corresponding to the relevant roles of each node in the first schedule to switch between the swimlane view and other types of views such as tables, lists, signs, and Gantt charts, and this embodiment is not limited to these.

[0051] In this embodiment, a second-level subnode may be associated with at least one role, that is, one or more roles may be configured for a second-level subnode so that a user corresponding to this role can have the relevant permissions for that second-level subnode. Here, these permissions may be, for example, viewing permissions, editing permissions, and progress modification permissions, and this embodiment is not limited thereto.

[0052] Step S103, a swimlane view corresponding to the first schedule is displayed, and the swimlane view is used to display progress status information of at least one second-level subnode associated with at least one role.

[0053] In this embodiment, the execution unit can display a swimlane view corresponding to the first schedule in the schedule presentation interface in response to a first operation on the first schedule. For example, based on an operation to open the view display page for the first schedule, the swimlane view corresponding to the first schedule is displayed on the view display page of the first schedule.

[0054] In this embodiment, based on the first operation, progress information for at least one second-level subnode associated with at least one role is displayed in the swimlane view corresponding to the first schedule. That is, in this embodiment, each second-level subnode can be arranged based on different roles, and second-level subnodes related to the same role can be aggregated and displayed, so that the user can view second-level subnodes associated with different roles.

[0055] Simultaneously, when a second-level subnode is displayed, progress information for each second-level subnode is also displayed, allowing the user to view the progress status of each second-level subnode when viewing the associated second-level subnode. Here, the progress status may include, but is not limited to, completed, incomplete, in progress, etc.

[0056] In this embodiment, a first operation on a first schedule table displays a swimlane view corresponding to the first schedule table. The first schedule table includes first-level subnodes and second-level subnodes, and the second-level subnodes are associated with roles. By displaying the progress status information of the second-level subnodes associated with a role in this swimlane view based on the role, it is possible to arrange each second-level subnode based on different roles and aggregate and display second-level subnodes associated with the same role. In this way, users can view second-level subnodes and their progress status information based on different roles, satisfying the usage needs of users with different role types and improving the user experience.

[0057] In some embodiments, displaying the swimlane view corresponding to the first schedule in step S103 includes displaying a node subgraph region based on a role list, wherein the node graph blocks in the node subgraph region are configured to correspond to the second-level subnodes, and the node graph blocks corresponding to the second-level subnodes associated with the same role in the role list are located in the same swimlane of the swimlane view.

[0058] As shown in Figures 2A and 2B, the swimlane view 100 corresponding to the first schedule displays a role list 101 and a node subgraph area 104. Here, the role list 101 is used to display all or some of the roles associated with each node in the first schedule, and may include, for example, role A, role B, role C, etc.

[0059] The node subgraph area 104 is used to display node graph blocks 1041 corresponding to second-level subnodes, where the node graph blocks 1041 may be displayed in a one-to-one correspondence with the second-level subnodes.

[0060] In this embodiment, node graph blocks 1041 corresponding to second-level subnodes associated with the same role are located in the same swimlane. As shown in Figure 2B, nodes A, B, and C are all associated with role A and are therefore displayed in the swimlane where role A is located; nodes 11, 12, 13, 14, 17, 21, 23, 24, 25, 32, 33, 34, 41, and 42 are all associated with role B and are therefore displayed in the swimlane where role B is located; and nodes 15, D, 16, 22, E, 31, F, and G are all associated with role C and are therefore displayed in the swimlane where role C is located.

[0061] Here, when the role list 101 is displayed as the vertical axis, node graph blocks corresponding to second-level subnodes related to the same role are located in the same horizontal swimlane, and when the role list 101 is displayed as the horizontal axis, node graph blocks corresponding to second-level subnodes related to the same role are located in the same vertical swimlane.

[0062] In this embodiment, each second-level subnode can be arranged based on different roles, and second-level subnodes related to the same role can be displayed in the same swimlane in the swimlane view. In this way, users can view second-level subnodes related to roles based on different roles, satisfying the usage needs of users with different role types and improving the user experience.

[0063] In some embodiments, the method further includes marking the node graph block corresponding to the second-level subnode by a first identifier in response to the progress status of the second-level subnode being complete, marking the node graph block corresponding to the second-level subnode by a second identifier in response to the progress status of the second-level subnode being incomplete, and determining the progress status information of the second-level subnode based on the first identifier and the second identifier.

[0064] In this embodiment, in the node subgraph area 104, node graph blocks 1041 corresponding to second-level subnodes having different progress states are marked with different types of marks, making it easier to distinguish between second-level subnodes in different progress states and facilitating users to view progress status information of second-level subnodes based on their roles. For example, node graph blocks corresponding to second-level subnodes with a completed progress state are marked and identified by a first identifier, and node graph blocks corresponding to second-level subnodes with an incomplete progress state are marked with a second identifier. If other types of progress states exist, for example, if the progress state is in progress, node graph blocks corresponding to second-level subnodes in a state such as "in progress" are marked with identifiers different from the first and second identifiers, thus representing the progress status information of second-level subnodes based on different identifiers such as the first and second identifiers.

[0065] In some embodiments, different identifiers, such as a first identifier and a second identifier, may be colored differently. For example, a node graph block corresponding to a second-level subnode with a progress status of "completed" may be set to green, a node graph block corresponding to a second-level subnode with a progress status of "incomplete" may be set to gray, and a node graph block corresponding to a second-level subnode with a progress status of "in progress" may be set to red. This embodiment is not limited to these examples.

[0066] In some embodiments, different identifiers such as the first identifier and the second identifier may have different shapes or patterns, for example, adding a rectangle to the node graph block corresponding to a second-level subnode whose progress is complete, adding a triangle to the node graph block corresponding to a second-level subnode whose progress is incomplete, and adding a circle to the node graph block corresponding to a second-level subnode whose progress is in progress, and this embodiment is not limited thereto.

[0067] In this embodiment, the node subgraph area 104 of the swimlane view 100 corresponding to the first schedule displays not only node graph blocks corresponding to second-level subnodes whose progress status is completed, but also node graph blocks corresponding to second-level subnodes whose progress status is incomplete, in progress, etc. This allows users with different roles to view not only the progress that has already been completed, but also the progress that is incomplete or in progress, thereby providing an overall view of the progress status of the first project, meeting the usage needs of users with different roles, and improving the user experience.

[0068] In some embodiments, the method further includes, in response to a trigger operation on the node graph block, displaying node information for a second-level subnode corresponding to the node graph block, wherein the node information includes a node name, a progress status, an associated user, a scheduled start time, a scheduled end time, an actual start time, an actual end time, and a delay time.

[0069] As shown in Figure 2C, when a user performs a trigger operation on any one of the node graph blocks 1041 in the node subgraph area 104, for example by clicking on this node graph block 1041 or hovering the mouse over this node graph block 1041, a first window 1042 may appear, and in this first window 1042, node information of the second-level subnode corresponding to this node graph block 1041 may be displayed. Here, this node information may include the node name, progress status, associated user (user corresponding to the associated role, e.g., assignee), scheduled start time, scheduled end time, actual start time, actual end time, and delay time.

[0070] In this embodiment, the user can view the node information of any one second-level subnode by triggering an operation on any one node graph block 1041 in the node subgraph area 104.

[0071] In some embodiments, displaying the swimlane view corresponding to the first schedule in step S103 means displaying a flow subgraph region based on a time axis, wherein the subflow blocks in the flow subgraph region are set up corresponding to the first level subnodes, and further includes setting up the subflow block corresponding to the first level subnode and the node graph block corresponding to at least one second level subnode associated with this first level subnode in the same row or column.

[0072] As shown in Figures 2A and 2B, the swimlane view 100 corresponding to the first schedule further displays a time axis 102 and a flow subgraph area 103, where the flow subgraph area 103 is used to display subflow blocks 1031 corresponding to first-level subnodes, and a one-to-one correspondence is set between the subflow blocks 1031 and the first-level subnodes.

[0073] In this embodiment, the flow subgraph area 103 is displayed based on the time axis 102, that is, each subflow block 1031 in the flow subgraph area 103 is displayed in accordance with the time shown on the time axis 102 based on the start and end times of the first-level subnodes, thereby allowing the user to view the time range of the stage corresponding to each first-level subnode based on the time shown on the time axis 103.

[0074] In some embodiments, the node graph blocks 1041 in the node subgraph area 104 are also displayed based on a time axis, that is, the node graph blocks 1041 in the node subgraph area 104 are displayed in accordance with the time shown on the time axis 102 based on the start and end times of the second-level subnodes, thereby allowing the user to view the time range of the stages corresponding to each second-level subnode based on the time shown on the time axis 103.

[0075] As shown in Figure 2B, since the first-level subnodes and the second-level subnodes are related, for example, if the first-level subnode is the first stage, then the second-level subnodes, namely nodes 11, 12, 13, 14, 17, 15, D, and 16, all belong to this first stage. Therefore, by setting the node graph block 1041 corresponding to nodes 11, 12, 13, 14, 17, 15, D, and 16 and the subflow block 1031 corresponding to the first stage in the same row or column, the user can understand the relationship between each second-level subnode and each first-level subnode, making it easier for the user to use and improving the user experience.

[0076] Here, if the time axis 102 is displayed as the horizontal axis and the role list 101 is displayed as the vertical axis, the subflow block 1031 corresponding to the first-level subnode and the node graph block 1042 corresponding to the second-level subnode related to this first-level subnode are set in the same column. If the time axis 102 is displayed as the vertical axis and the role list 101 is displayed as the horizontal axis, the subflow block 1031 corresponding to the first-level subnode and the node graph block 1042 corresponding to the second-level subnode related to this first-level subnode are set in the same row.

[0077] In some embodiments, the method further includes displaying the subflow block as a pre-configured graphic in response to a configuration operation on the subflow block in the flow subgraph region, wherein the pre-configured graphic includes at least one of a rectangle, a trapezoid, a funnel, a triangle, and a polygon.

[0078] In this embodiment, configuration operations on subflow blocks in the flow subgraph area of ​​a first type of user of the first system display the subflow blocks in pre-defined graphics such as rectangles, trapezoids, funnels, triangles, and polygons.

[0079] As shown in Figure 2B, the first pre-set number of sub-flow blocks in the flow subgraph area may be set to a trapezoid shape, with the bases of two adjacent trapezoidal sub-flow blocks facing each other and of the same size, while the remaining sub-flow blocks in the flow subgraph area may be set to rectangles.

[0080] For example, the relatively short base of the trapezoid of the sub-flow block corresponding to the first stage is the same length as the relatively long base of the trapezoid of the sub-flow block corresponding to the second stage and is set opposite; the relatively short base of the trapezoid of the sub-flow block corresponding to the second stage is the same length as the relatively long base of the trapezoid of the sub-flow block corresponding to the third stage and is set opposite; and the relatively short base of the trapezoid of the sub-flow block corresponding to the third stage is the same length as the rectangular side of the sub-flow block corresponding to the fourth stage and is set opposite.

[0081] In some embodiments, the method further includes marking the subflow block corresponding to the first-level subnode by a third identifier in response to the progress status of the first-level subnode being complete or partially complete; marking the subflow block corresponding to the first-level subnode by a fourth identifier in response to the progress status of the first-level subnode being incomplete or partially incomplete; and determining the progress status information of the first-level subnode based on the third identifier and the fourth identifier.

[0082] In this embodiment, in the flow subgraph area 103, subflow blocks 1031 corresponding to first-level subnodes having different progress states are marked with different types of marks, making it easier to distinguish between first-level subnodes in different progress states and facilitating users to view progress status information of first-level subnodes based on their roles. For example, a third identifier is used to mark and identify subflow blocks 1031 corresponding to first-level subnodes whose progress state is completed or partially completed, and a fourth identifier is used to mark subflow blocks 1031 corresponding to first-level subnodes whose progress state is incomplete or partially incomplete.

[0083] In some embodiments, different identifiers, such as a third identifier and a fourth identifier, may be used to determine the progress status information of the first-level subnodes based on the third identifier and the fourth identifier of different colors. For example, as shown in Figure 2B, a subflow block 1031 corresponding to a first-level subnode whose progress status is complete may be set to purple, for example, the subflow block 1031 corresponding to the first and second stages; a subflow block 1031 corresponding to a first-level subnode whose progress status is incomplete may be set to gray, for example, the subflow block 1031 corresponding to the fourth stage; and a subflow block 1031 corresponding to a first-level subnode whose progress status is partially complete and partially incomplete may have its completed portion set to purple and its incomplete portion set to gray, for example, the subflow block 1031 corresponding to the third stage, and this embodiment is not limited thereto.

[0084] In this embodiment, the flow subgraph area 103 of the swimlane view 100 corresponding to the first schedule displays not only subflow blocks 1031 corresponding to first-level subnodes whose progress status is completed, but also subflow blocks 1031 corresponding to first-level subnodes whose progress status is incomplete, and partially completed and partially incomplete. This allows users with different roles to view not only already completed progress, but also incomplete or ongoing progress, thereby providing an overall view of the progress status of the first project, meeting the usage needs of users with different roles, and improving the user experience.

[0085] In some embodiments, the method further includes at least one of the following: displaying a first node identifier corresponding to the first type node in the flow subgraph region in response to setting a first target node among the second level subnodes as a first type node; and displaying a second node identifier corresponding to the second type node in the flow subgraph region in response to setting a second target node among the second level subnodes as a second type node.

[0086] In this embodiment, the second-level subnodes may be of various types, for example, a first-type node, a second-type node, and a general node. The first-type node and the second-type node may be displayed not only in the node subgraph area 104 but also in the flow subgraph area 103, thereby providing different displays based on different types of nodes. The general node may be displayed only in the node subgraph area 104.

[0087] Here, the first type node may be, for example, a step milestone, and the second type node may be, for example, a critical milestone.

[0088] In some embodiments, the second level of subnodes can be configured as more types of nodes, allowing for different displays based on different node types to meet user needs.

[0089] As shown in Figure 2B, if the first target nodes among the second-level subnodes, for example nodes A, B, and C, are set as the first type nodes, these first target nodes may be displayed not only in the node subgraph area 104 but also in the flow subgraph area 103. If the second target nodes among the second-level subnodes, for example nodes D, E, F, and G, are set as the second type nodes, these second target nodes may be displayed not only in the node subgraph area 104 but also in the flow subgraph area 103.

[0090] In this embodiment, the first target node is displayed on one side of each subflow block 1031 in the flow subgraph area 103, and the second target node is displayed on the other side of each subflow block 1031 in the flow subgraph area 103; however, this embodiment is not limited to this.

[0091] In some embodiments, the node graph block displayed in the node subgraph area by the first target node is the same as the first node identifier displayed in the flow subgraph area, and the node graph block displayed in the node subgraph area by the second target node is the same as the second node identifier displayed in the flow subgraph area.

[0092] As shown in Figure 2B, for the first target nodes, such as Node A, Node B, and Node C, the shape, color, and included identifiers of the node graph block 1041 displayed in the node subgraph area 104 and the first node identifier 1032 displayed in the flow subgraph area 103 are all the same. Similarly, for the second target nodes, such as Node D, Node E, Node F, and Node G, the shape, color, and included identifiers of the node graph block 1041 displayed in the node subgraph area 104 and the second node identifier 1033 displayed in the flow subgraph area 103 are all the same. This ensures that the same nodes are consistently displayed in the swimlane view 100, facilitating user use and improving the user experience.

[0093] In some embodiments, the method further includes, in response to a trigger operation on the subflow block, displaying node information for a first-level subnode corresponding to the subflow block, wherein the node information includes at least one of a node name, a progress status, a scheduled start time, a scheduled end time, an actual start time, an actual end time, a delay time, a first type node to be included, and a second type node to be included.

[0094] As shown in Figure 2D, when a user performs a trigger operation on any of the subflow blocks 1031 in the flow subgraph area 103, for example by clicking on the subflow block 1031 or hovering the mouse over the subflow block 1031, a second window 1034 may appear, in which the node information of the first-level subnode corresponding to the subflow block 1031 may be displayed. Here, the node information may include at least one of the following: node name, progress status, scheduled start time, scheduled end time, actual start time, actual end time, delay time, included first type node, and included second type node.

[0095] In this embodiment, the user can view the node information of any one of the first-level subnodes by triggering an operation on any one of the subflow blocks 1031.

[0096] In some embodiments, the method further includes, in response to a trigger operation on the first node identifier, displaying node information for a first target node corresponding to the first node identifier, wherein the node information includes at least one of the node name, progress status, scheduled completion time, actual completion time, deferred time, and associated role.

[0097] In this embodiment, when a user performs a trigger operation on any one of the first node identifiers 1032 in the flow subgraph area 103, for example by clicking on the first node identifier 1032 or hovering the mouse over the first node identifier 1032, a third window may be displayed, and in this third window, node information of the first target node corresponding to the first node identifier 1032 may be displayed. Here, this node information may include at least one of the following: node name, progress status, scheduled completion time, actual completion time, delay time, and associated user.

[0098] In some embodiments, the method further includes, in response to a trigger operation on the second node identifier, displaying node information for a second target node corresponding to the second node identifier, wherein the node information includes at least one of the node name, progress status, scheduled completion time, actual completion time, deferred time, and associated role.

[0099] In this embodiment, as shown in Figure 2E, when a user performs a trigger operation on any of the second node identifiers 1033 in the flow subgraph area 103, for example node D, for example by clicking on this second node identifier 1033 or hovering the mouse over this second node identifier 1033, a fourth window 1035 may be displayed, and in this fourth window 1035, node information of the second target node corresponding to this second node identifier 1033 may be displayed. Here, this node information may include at least one of the following: node name, progress status, scheduled completion time, actual completion time, delay time, and associated user.

[0100] In this embodiment, the user can satisfy their usage needs and improve their user experience by viewing the node information of either one of the first type nodes or the second type node through a trigger operation on either one of the first node identifiers 1032 or the second node identifier 1033 in the flow subgraph area 103.

[0101] In some embodiments, the method further includes displaying the node form of the second type node for performing a second operation on the second type node in response to an expansion operation on the second type node.

[0102] In this embodiment, as shown in Figure 2F, when a user performs an expand operation on a first node identifier 1032 or node graph block corresponding to any one of the first type nodes, a fifth window 1036 may be displayed, and the node form of this first type node may be displayed in this fifth window 1036. This node form may display some node information of this first type node, and a second operation may be performed on this first type node based on this node form. Here, the second operation may include, but is not limited to, modifying the progress status of this first type node (for example, modifying the node progress status to complete using a completion control), adding a new task to this first type node, adding a new dependency item to this first type node, or adding a new effort to this first type node.

[0103] In some embodiments, the method further includes displaying the node form of the second type node for performing a third operation on the second type node in response to an expansion operation on the second type node.

[0104] In this embodiment, when a user performs an expand operation on a second node identifier or node graph block corresponding to any one of the second type nodes, the node form of this second type node may be displayed. This node form may display some node information of this second type node, and a third operation may be performed on this second type node based on this node form. Here, the third operation may include, but is not limited to, modifying the progress status of this first type node, adding a new task to this first type node, adding a new dependency item to this first type node, or adding a new effort to this first type node.

[0105] In some embodiments, the method further includes displaying only the first type node and / or the second type node in response to a configuration operation on the swimlane view.

[0106] As shown in Figure 2B, the swimlane view 100 includes a first configuration control 1052, and when a configuration operation is performed on the swimlane view based on the first configuration control 1052, only the first type node and / or the second type node may be displayed.

[0107] In some embodiments, the method further includes displaying dependencies between the second-level subnodes or canceling the display of dependencies between the second-level subnodes in response to a configuration operation on the swimlane view.

[0108] As shown in Figures 2B and 2G, the swimlane view 100 includes a second configuration control 1051. When a configuration operation is performed on the swimlane view using the second configuration control 1051, dependencies between second-level subnodes may be displayed, as shown in Figure 2G, or the display of dependencies between second-level subnodes may be canceled when a configuration operation is performed on the swimlane view using the second configuration control 1051, as shown in Figure 2B.

[0109] In some embodiments, the method further includes modifying the lengths of the node graph block and the subflow block in response to a step size switching operation based on the time axis.

[0110] In this embodiment, as shown in Figure 2B, the time axis has various step sizes such as days, months, quarters, and years. Therefore, the lengths of the node graph block 1041 and subflow block 1031 can be modified based on the step size selected by the user, enabling zooming of the swimlane view 100 and meeting the user's needs.

[0111] In some embodiments, the method further includes displaying the node graph block and the subflow block for a time range corresponding to a time positioning operation based on a time axis in response to the time positioning operation.

[0112] In this embodiment, as shown in Figure 2B, if the time positioning operation based on the time axis can be anchored to "today," another specified date, or a specified time range, the node information for today, another specified date, or a specified time range may be highlighted on the current view page, or the content displayed on the current view page may be switched left or right based on the time axis, and this embodiment is not limited thereto.

[0113] In some embodiments, the method further includes displaying only the flow subgraph region of the swimlane view in response to a fourth operation on the first schedule, and displaying the swimlane view in response to a fifth operation on the flow subgraph region of the swimlane view.

[0114] In this embodiment, in some interfaces, for example, at the top of the instance details page, only the timely axis 102 of the flow subgraph area 103 of the swimlane view 100 may be displayed first. For a fifth operation on this flow subgraph area, if the fifth operation may be, for example, a full-screen operation, the complete swimlane view 100 is displayed.

[0115] Before using any of the technical solutions in each embodiment of this disclosure, it is understood that the user will be informed in an appropriate manner of the type of personal information involved, the scope of use, and the circumstances of use, and that the user's permission will be obtained.

[0116] For example, when responding to a user's voluntary request, prompt information is sent to the user to clearly prompt the user that it is necessary to obtain and use the user's personal information in order to perform the requested operation. This allows the user to autonomously choose whether or not to provide personal information to software or hardware such as electronic devices, application programs, servers, or storage media that perform the operation of the proposed technical method of this disclosure based on the prompt information.

[0117] As a selective but non-restrictive implementation, a method for sending prompt information to a user in response to receiving a voluntary request from the user may be, for example, a pop-up window, in which case the prompt information may be presented in text format. The pop-up window may also include selection controls for the user to choose whether to "agree" or "disagree" to providing personal information to the electronic device.

[0118] The above notice and user permission acquisition process are general in nature and do not limit the forms in which this disclosure may be implemented. It should be understood that other methods that comply with applicable laws and regulations may also be applicable to the implementation of this disclosure.

[0119] The methods of the embodiments of this disclosure may be performed by a single device, such as a single computer or server. The methods of the embodiments may also be used in a distributed scenario in which multiple devices cooperate to complete the process. In such a distributed scenario, one of these multiple devices may perform only one or more steps of the methods of the embodiments of this disclosure, and these multiple devices may interact with each other to complete the method.

[0120] The above describes some embodiments of this disclosure. Other embodiments are within the scope of the appended claims. In some cases, the operations or steps described in the claims may be performed in a different order than those in the embodiments above, and the desired results can still be achieved. Furthermore, the processes depicted in the drawings do not necessarily require a specific order or sequence shown to achieve the desired results. In some embodiments, multitasking and parallel processing are possible or may be advantageous.

[0121] Based on the same inventive concept, and corresponding to the methods of any of the above embodiments, the present disclosure further provides an information processing apparatus.

[0122] Referring to Figure 3, the device, A receiving module 11 configured to receive a first operation on a first schedule, wherein the first schedule includes at least one first-level subnode and at least one second-level subnode, and the second-level subnode is associated with at least one role, A display module 13 configured to display a swimlane view corresponding to the first schedule, wherein the swimlane view includes a display module 13 that displays progress status information for at least one second-level subnode associated with at least one role.

[0123] In some embodiments, the display module 13 is The system is configured to display a node subgraph region based on a role list, where node graph blocks in the node subgraph region are set to correspond to the second-level subnodes, and the node graph blocks corresponding to the second-level subnodes associated with the same role in the role list are located in the same swimlane in the swimlane view.

[0124] In some embodiments, the apparatus further, In response to the progress status of the second-level subnode being complete, the node graph block corresponding to the second-level subnode is marked by a first identifier, In response to the progress status of the second-level subnode being incomplete, the node graph block corresponding to the second-level subnode is marked with a second identifier. The system is configured to determine the progress status information of the second-level subnode based on the first identifier and the second identifier.

[0125] In some embodiments, the apparatus further, It is configured to display node information of the second-level subnodes corresponding to the node graph block in response to a trigger operation on the node graph block. The node information includes at least one of the following: node name, progress status, associated user, scheduled start time, scheduled end time, actual start time, actual end time, and postponement time.

[0126] In some embodiments, the display module 13 is The flow subgraph region is displayed based on a time axis, wherein the subflow blocks in the flow subgraph region are set to correspond to the first level subnodes. The configuration involves setting the subflow block corresponding to the first-level subnode and the node graph block corresponding to at least one second-level subnode related to this first-level subnode in the same row or column.

[0127] In some embodiments, the apparatus further, The node graph blocks in the node subgraph region are configured to be displayed based on the time axis.

[0128] In some embodiments, the apparatus further, In response to configuration operations on subflow blocks in the flow subgraph region, the system is configured to display the subflow blocks as pre-configured graphics. The aforementioned pre-configured graphics include at least one of the following shapes: rectangle, trapezoid, funnel, triangle, and polygon.

[0129] In some embodiments, the apparatus further, In response to the progress status of the first-level subnode being complete or partially complete, the subflow block corresponding to the first-level subnode is marked with a third identifier. In response to the progress status of the first-level subnode being incomplete or partially incomplete, the subflow block corresponding to the first-level subnode is marked with a fourth identifier. The system is configured to determine the progress status information of the first-level subnode based on the third identifier and the fourth identifier.

[0130] In some embodiments, the apparatus further, In response to setting the first target node among the second-level subnodes as the first type node, the first node identifier corresponding to the first type node is displayed in the flow subgraph area, The system comprises at least one of the following: setting the second target node among the second level subnodes as a second type node, and displaying a second node identifier corresponding to the second type node in the flow subgraph region.

[0131] In some embodiments, the node graph block displayed in the node subgraph area by the first target node is the same as the first node identifier displayed in the flow subgraph area, and the node graph block displayed in the node subgraph area by the second target node is the same as the second node identifier displayed in the flow subgraph area.

[0132] In some embodiments, the apparatus further, In response to a trigger operation on the subflow block, it is configured to display node information of the first-level subnode corresponding to the subflow block. The node information includes at least one of the following: node name, progress status, scheduled start time, scheduled end time, actual start time, actual end time, delay time, included first type node, and included second type node.

[0133] In some embodiments, the apparatus further, In response to a trigger operation on the first node identifier, the node information of the first target node corresponding to the first node identifier is displayed, wherein the node information includes at least one of the following: node name, progress status, scheduled completion time, actual completion time, delay time, and associated user. Or, In response to a trigger operation on the second node identifier, the node information of the second target node corresponding to the second node identifier is displayed, wherein the node information includes at least one of the following: node name, progress status, scheduled completion time, actual completion time, delay time, and associated user.

[0134] In some embodiments, the apparatus further, In response to an expansion operation on the first type node, the node form of the first type node is displayed for performing a second operation on the first type node. Or, It is configured to display the node form of the second type node in order to perform a third operation on the second type node in response to an expansion operation on the second type node.

[0135] In some embodiments, the apparatus further, In response to a configuration operation on the swimlane view, it is configured to display only the first type node and / or the second type node.

[0136] In some embodiments, the apparatus further, In response to a configuration operation on the swimlane view, it is configured to either display the dependencies between the second-level subnodes or to cancel the display of the dependencies between the second-level subnodes.

[0137] In some embodiments, the apparatus further, In response to a step size switching operation based on the time axis, the lengths of the node graph block and the subflow block are modified. The system is configured to display the node graph block and the subflow block for the time range corresponding to a time positioning operation based on a time axis in response to the time positioning operation.

[0138] In some embodiments, the apparatus further, In response to the fourth operation on the first schedule, only the flow subgraph area of ​​the swimlane view is displayed. The system is configured to display the swimlane view in response to a fifth operation on the flow subgraph region of the swimlane view.

[0139] For the sake of convenience in description, the above device will be described by dividing it into various modules according to its function. Of course, when implementing this disclosure, the functions of each module may be implemented in the same or multiple software and / or hardware.

[0140] The apparatus of the above embodiment is used to implement the method in any one of the embodiments described above, and has the beneficial effects of the embodiment of the method in question, and will not be described further here.

[0141] Based on the same inventive concept and corresponding to the method of any of the above embodiments, the present disclosure further provides an electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor, upon executing the program, implements the method of any one of the above embodiments.

[0142] Figure 4 shows a schematic diagram of the hardware structure of a more specific electronic device according to this embodiment, which may include a processor 1010, a memory 1020, an input / output interface 1030, a communication interface 1040, and a bus 1050. Here, the processor 1010, the memory 1020, the input / output interface 1030, and the communication interface 1040 communicate with each other via the bus 1050.

[0143] The processor 1010 may be implemented in the form of a general-purpose CPU (Central Processing Unit), a microprocessor, an Application Specific Integrated Circuit (ASIC), or one or more integrated circuits, for executing the associated program and realizing the technical proposal according to the embodiments herein.

[0144] Memory 1020 may be implemented in the form of ROM (Read Only Memory), RAM (Random Access Memory), static storage, dynamic storage, etc. Memory 1020 can store the operating system and other application programs, and when the technical proposal according to the embodiments herein is implemented by software or firmware, the relevant program code is stored in memory 1020 and called and executed by processor 1010.

[0145] The input / output interface 1030 is used to connect input / output modules to enable the input and output of information. The input / output modules may be configured as components in the device (not shown) or may be connected externally to the device to provide the corresponding functions. Here, input devices may include keyboards, mice, touchscreens, microphones, various sensors, etc., and output devices may include displays, speakers, vibrators, indicator lights, etc.

[0146] The communication interface 1040 is used to connect a communication module (not shown) to enable communication interaction between this device and other devices. Here, the communication module may implement communication using a wired method (e.g., USB, network cable, etc.) or a wireless method (e.g., mobile network, Wi-Fi, Bluetooth®, etc.).

[0147] Bus 1050 includes paths for transmitting information between the various components of the device (e.g., processor 1010, memory 1020, input / output interface 1030, and communication interface 1040).

[0148] Although the above-mentioned equipment only shows the processor 1010, memory 1020, input / output interface 1030, communication interface 1040, and bus 1050, in a specific implementation process, this equipment may further include other components necessary to achieve normal operation. Furthermore, those skilled in the art will understand that the above-mentioned equipment may include only the components necessary to implement the embodiment described herein, and does not necessarily need to include all the components shown in the figures.

[0149] The electronic devices of the above embodiments are used to implement the applicable method in any one of the embodiments described above, and have the beneficial effects of the applicable method embodiment, which will not be described further here.

[0150] Based on the same inventive concept and corresponding to the method of any of the above embodiments, the present disclosure further provides a non-temporary computer-readable storage medium which stores computer instructions for causing the computer to perform the method of any one of the above embodiments.

[0151] The computer-readable media of this embodiment include persistent and non-persistent, removable and non-removable media, and information can be stored by any method or technique. The information may be computer-readable instructions, data structures, program modules, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random-access memory (SRAM), dynamic random-access memory (DRAM), other types of random-access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, read-only disk memory (CD-ROM), digital multipurpose disk (DVD) or other optical storage, magnetic cassette, magnetic tape, magnetic disk storage or other magnetic storage devices or any other non-transmission media that may be used to store information accessible by computing equipment.

[0152] The computer instructions stored in the storage medium of the above embodiment are used to cause the computer to execute the method of any one of the above embodiments, and have the beneficial effects of the embodiment of the corresponding method, which will not be described further here.

[0153] Based on the same inventive concept, and corresponding to the data processing method described in any of the above embodiments, the present disclosure further provides a computer program product including computer program instructions. In some embodiments, the computer program instructions may be executed by one or more processors of the computer to cause the computer and / or the processor to execute the data processing method. Corresponding to the execution body corresponding to each step in each embodiment of the data processing method, the processor that executes the corresponding step may belong to the corresponding execution body.

[0154] The computer program product of the above embodiment is used to cause the computer and / or the processor to execute the method described in any one of the above embodiments, and has the beneficial effects of the embodiment of the applicable method, which will not be described further here.

[0155] Those skilled in the art will understand that the consideration of the above-described examples is illustrative and not intended to imply that the scope of the Disclosure (including the claims) is limited to these examples, that in the spirit of the Disclosure, technical features in the above-described examples or different examples can be combined, that the steps can be carried out in any order, and that many other variations of different embodiments of the embodiments of the Disclosure described above exist, which are not provided in detail for the sake of simplicity.

[0156] Furthermore, in order to simplify the explanation and discussion, and to avoid making it difficult to understand the embodiments of this disclosure, the provided drawings may or may not show known power / ground connections of integrated circuit (IC) chips and other components. Also, in order to avoid making it difficult to understand the embodiments of this disclosure, the apparatus may be shown in the form of a block diagram, taking into consideration the following fact: the details of the embodiments of the apparatus in these block diagrams depend heavily on the platform on which the embodiments of this disclosure are carried out (i.e., these details should be fully within the understanding of those skilled in the art). Where specific details (e.g., circuits) are described to describe exemplary embodiments of this disclosure, it will be obvious to those skilled in the art that the embodiments of this disclosure can be carried out even if these specific details are absent or changed. Therefore, these descriptions should be considered descriptive, not restrictive.

[0157] Although this disclosure has been described in conjunction with specific embodiments thereof, many substitutions, modifications, and variations of these embodiments will be apparent to those skilled in the art as described herein. For example, other memory architectures (e.g., dynamic RAM (DRAM)) may be used in the embodiments discussed.

[0158] The embodiments of this disclosure are intended to include all such substitutions, modifications, and variations that fall within the broad scope of the appended claims. Therefore, any omissions, modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the embodiments of this disclosure should be included within the scope of protection of this disclosure.

Claims

1. Information processing method, Receiving a first operation on a first schedule, wherein the first schedule includes at least one first-level subnode and at least one second-level subnode, and the second-level subnode is associated with at least one role. Information processing method comprising displaying a swimlane view corresponding to the first schedule, wherein the swimlane view displays progress status information for at least one second-level subnode associated with at least one role.

2. Displaying the swimlane view corresponding to the first schedule mentioned above is: The method according to claim 1, comprising displaying a node subgraph region based on a role list, wherein the node graph blocks in the node subgraph region are configured to correspond to the second-level subnodes, and the node graph blocks corresponding to the second-level subnodes associated with the same role in the role list are located in the same swimlane in the swimlane view.

3. In response to the progress status of the second-level subnode being complete, the node graph block corresponding to the second-level subnode is marked with a first identifier, In response to the progress status of the second-level subnode being incomplete, the node graph block corresponding to the second-level subnode is marked with a second identifier, The method according to claim 2, further comprising determining progress status information of the second-level subnode based on the first identifier and the second identifier.

4. The method further includes displaying node information of a second-level subnode corresponding to the node graph block in response to a trigger operation on the node graph block, The method according to claim 2, wherein the node information includes at least one of the following: node name, progress status, associated user, scheduled start time, scheduled end time, actual start time, actual end time, and postponement time.

5. Displaying the swimlane view corresponding to the first schedule mentioned above is: The flow subgraph region is displayed based on a time axis, wherein the subflow blocks in the flow subgraph region are set to correspond to the first level subnodes. The method of claim 2, further comprising setting the subflow block corresponding to the first-level subnode and the node graph block corresponding to at least one second-level subnode related to the first-level subnode in the same row or column.

6. The method according to claim 5, further comprising displaying the node graph block in the node subgraph region based on the time axis.

7. The method further includes displaying the subflow block as a pre-configured graphic in response to a configuration operation on the subflow block in the flow subgraph region. The method according to claim 5, wherein the pre-configured graphics include at least one of a rectangle, a trapezoid, a funnel, a triangle, and a polygon.

8. In response to the progress status of the first-level subnode being completed or partially completed, the subflow block corresponding to the first-level subnode is marked with a third identifier, In response to the progress status of the first-level subnode being incomplete or partially incomplete, the subflow block corresponding to the first-level subnode is marked with a fourth identifier, The method according to claim 5, further comprising determining the progress status information of the first-level subnode based on the third identifier and the fourth identifier.

9. In response to setting the first target node among the second-level subnodes as the first type node, the first node identifier corresponding to the first type node is displayed in the flow subgraph area, The method of claim 5, further comprising at least one of the following: setting a second target node among the second level subnodes as a second type node, and displaying a second node identifier corresponding to the second type node in the flow subgraph region.

10. The method according to claim 9, wherein the node graph block displayed in the node subgraph area by the first target node is the same as the first node identifier displayed in the flow subgraph area, and the node graph block displayed in the node subgraph area by the second target node is the same as the second node identifier displayed in the flow subgraph area.

11. In response to a trigger operation on the subflow block, the method further includes displaying node information of the first-level subnode corresponding to the subflow block, The method according to claim 9, wherein the node information includes at least one of the following: node name, progress status, scheduled start time, scheduled end time, actual start time, actual end time, delay time, included first type node, and included second type node.

12. In response to a trigger operation on the first node identifier, the node information of the first target node corresponding to the first node identifier is displayed, wherein the node information includes at least one of the following: node name, progress status, scheduled completion time, actual completion time, delay time, and associated user. Or, The method according to claim 9, wherein, in response to a trigger operation on the second node identifier, node information of a second target node corresponding to the second node identifier is displayed, the node information further comprising at least one of the following: node name, progress status, scheduled completion time, actual completion time, delay time, and associated user.

13. Displaying the node form of the first type node in order to perform a second operation on the first type node in response to an expansion operation on the first type node, Or, The method of claim 9, further comprising displaying the node form of the second type node for performing a third operation on the second type node in response to an expansion operation on the second type node.

14. The method according to claim 9, further comprising displaying only the first type node and / or the second type node in response to a configuration operation on the swimlane view.

15. The method according to claim 1, further comprising displaying or canceling the display of dependencies between the second-level subnodes in response to a configuration operation on the swimlane view.

16. In response to a step size switching operation based on the time axis, the lengths of the node graph block and the subflow block are modified, The method according to claim 5, further comprising at least one of displaying the node graph block and the subflow block for a time range corresponding to a time positioning operation based on a time axis in response to the time positioning operation.

17. In response to the fourth operation on the first schedule, display only the flow subgraph area of ​​the swimlane view, The method according to claim 5, further comprising displaying the swimlane view in response to a fifth operation on the flow subgraph region of the swimlane view.

18. An information processing device, A receiving module configured to receive a first operation on a first schedule, wherein the first schedule includes at least one first-level subnode and at least one second-level subnode, and the second-level subnode is associated with at least one receiving module in a role. An information processing device comprising a display module configured to display a swimlane view corresponding to the first schedule, wherein the swimlane view includes a display module that displays progress status information of at least one second-level subnode associated with at least one role.

19. Electronic device comprising memory, a processor, and a computer program stored in memory and executable on the processor, wherein when the processor executes the program, the method according to any one of claims 1 to 17 is realized.

20. A non-temporary computer-readable storage medium, wherein computer instructions are stored in the non-temporary computer-readable storage medium, and the computer instructions are used to cause the computer to perform the method according to any one of claims 1 to 17.

21. A computer program product comprising a computer program instruction, wherein when the computer program instruction is executed on a computer, the computer causes the computer to perform the method according to any one of claims 1 to 17.

Images