Data processing method and device, equipment and storage medium

The method and apparatus generate and display customizable instance data topology diagrams based on user-defined business objects, addressing flexibility and efficiency issues in data management systems.

JP2026502893APending Publication Date: 2026-01-27BEIJING ZITIAO NETWORK TECH CO LTD
View PDF 7 Cites 0 Cited by

Patent Information

Application Number
JP2025537570
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-02-02
Filing Date
2024-02-02
Publication Date
2026-01-27

AI Technical Summary

Technical Problem

Current data management systems lack flexibility in tree configuration and display, limiting the efficiency and variety of data presentation in software project development and management.

Method used

A data processing method and apparatus that generates and displays an instance data topology diagram based on a user-defined business object topology diagram, incorporating target instance data and relationships, allowing for customizable hierarchies and reduced data processing.

Benefits of technology

Improves data display flexibility and reduces data processing volume by displaying only required data, enhancing the efficiency and security of software project management.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2026502893000001_ABST
    Figure 2026502893000001_ABST
Patent Text Reader

Abstract

A data processing method, apparatus, device, and storage medium, the method includes: receiving a target business object topology diagram set by a user, where the target business object topology diagram includes target business objects at multiple hierarchies (S110); determining target instance data relationship information corresponding to the target business object topology diagram, where the target instance data relationship information includes target instance data corresponding to the target business object topology diagram and association relationships between the target instance data (S120); generating an instance data topology diagram based on the target instance data relationship information (S130); and displaying the instance data topology diagram (S140).
Need to check novelty before this filing date? Find Prior Art

Description

[Technical Field]

[0001] [CROSS-REFERENCE TO RELATED APPLICATIONS] This application is based on and claims priority from a Chinese application entitled "Data Processing Method and Apparatus, Device and Storage Medium" filed on February 2, 2023, Application No. 202310118084.8, the disclosure of which is hereby incorporated in its entirety into this application.

[0002] TECHNICAL FIELD The embodiments of the present disclosure relate to the technical field of data processing, and in particular to a data processing method and apparatus, a device, and a storage medium. [Background technology]

[0003] In the process of software project development and management, a large amount of business data related to the software project is usually generated, and managing these business data in an efficient manner can greatly improve the efficiency of software project development and management, so effective management of business data is particularly important.

[0004] Currently, managing business data in a tree view manner is widely used. Summary of the Invention

[0005] The embodiments of the present disclosure provide a data processing method, apparatus, device, and storage medium that can display data through a topology diagram set by a user, thereby improving the flexibility of data display.

[0006] In a first aspect, an embodiment of the present disclosure provides a data processing method, the method comprising: receiving a target business object topology diagram set by a user, wherein the target business object topology diagram includes target business objects of multiple hierarchies; determining target instance data relationship information corresponding to the target business object topology diagram, where the target instance data relationship information includes target instance data corresponding to the target business object topology diagram and association relationships between target instance data; The aforementioned target generating an instance data topology diagram based on the instance data relationship information; and displaying the instance data topology diagram.

[0007] In a second aspect, an embodiment of the present disclosure further provides a data processing apparatus, the apparatus comprising: a target business object topology diagram setting module for receiving a target business object topology diagram set by a user, where the target business object topology diagram includes target business objects of multiple hierarchies; a target instance data relationship information determining module for determining target instance data relationship information corresponding to the target business object topology diagram, wherein the target instance data relationship information includes target instance data corresponding to the target business object topology diagram and association relationships between target instance data; The aforementioned target an instance data topology diagram generating module for generating an instance data topology diagram based on the instance data relationship information; and a display module for displaying the instance data topology diagram.

[0008] In a third aspect, an embodiment of the present disclosure further provides an electronic device, the electronic device comprising: one or more processors; a storage device for storing one or more programs; When the one or more programs are executed by the one or more processors, the one or more processors implement the data processing method described in the embodiments of the present disclosure.

[0009] In a fourth aspect, an embodiment of the present disclosure further provides a storage medium comprising computer-executable instructions for performing a data processing method according to an embodiment of the present disclosure when executed by a computer processor. [Brief explanation of the drawings]

[0010] These and other features, advantages, and aspects of the embodiments of the present disclosure will become more apparent by reference to the following detailed description taken in conjunction with the drawings. In all figures, the same or similar reference numerals represent the same or similar elements. It should be understood that the drawings are schematic and that elements and components are not necessarily drawn to scale.

[0011] [Figure 1] 1 is a schematic flow diagram of a data processing method according to an embodiment of the present disclosure. [Figure 2a] FIG. 2 illustrates an example of an original business object topology diagram according to an embodiment of the present disclosure. [Figure 2b] FIG. 10 illustrates an example of a settings page according to an embodiment of the present disclosure. [Figure 2c] FIG. 1 is a structural schematic diagram of a target business object topology diagram according to an embodiment of the present disclosure; [Figure 3a] FIG. 2 illustrates an example of an instance data topology diagram according to an embodiment of the present disclosure. [Figure 3b] FIG. 2 illustrates an example of an instance data topology diagram according to an embodiment of the present disclosure. [Figure 4] FIG. 10 illustrates an example of a cropped instance data topology diagram according to an embodiment of the present disclosure. [Figure 5] FIG. 10 illustrates an example of displaying instance data according to an embodiment of the present disclosure. [Figure 6] 1 is a structural schematic diagram of a data processing device according to an embodiment of the present disclosure; [Figure 7] 1 is a structural schematic diagram of an electronic device according to an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0012] Hereinafter, the embodiments of the present disclosure will be described in more detail with reference to the drawings. Although the drawings show several embodiments of the present disclosure, it should be understood that the present disclosure can be realized in various forms and should not be construed as being limited to the embodiments described herein. On the contrary, the examples are provided for a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are for illustrative purposes only and do not limit the scope of protection of the present disclosure.

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

[0014] As used herein, the term "comprises" and variations thereof are open-ended, i.e., "including, but not limited to." The term "based on" means "based at least in part on." The term "one embodiment" means "at least one embodiment," the term "another embodiment" means "at least one other embodiment," and the term "some embodiments" means "at least some embodiments." Relevant definitions of other terms are provided below.

[0015] It should be noted that the concepts of "first," "second," etc. referred to in this disclosure are merely intended to distinguish between different devices, modules, or units, and are not intended to limit the order or interdependence of functions performed by these devices, modules, or units.

[0016] It should be noted that the modifications "one" and "multiple" referred to in this disclosure are exemplary and not limiting, and should be understood to mean "one or more" unless the context clearly indicates otherwise, as will be understood by one of ordinary skill in the art.

[0017] The names of messages or information interacting between devices in the embodiments of the present disclosure are for illustrative purposes only and are not intended to limit the scope of these messages or information.

[0018] As can be understood, before using the technical solutions disclosed in each embodiment of the present disclosure, the type, scope of use, and usage scenarios of the personal information related to the present disclosure should be properly informed to the user in accordance with relevant laws and regulations, and authorization should be obtained from the user.

[0019] For example, in response to receiving a user's voluntary request, prompt information is sent to the user to clearly prompt the user that the requested operation requires the acquisition and use of the user's personal information, so that the user can choose for himself or herself whether to provide personal information to software or hardware, such as an electronic device, an application program, a server, or a storage medium, that performs the operation of the technical solution of the present disclosure based on the prompt information.

[0020] As an optional but non-limiting embodiment, the method of sending prompt information to the user in response to receiving a voluntary request from the user may be, for example, a pop-up window, or the prompt information may be presented in text form in the pop-up window, which may further include a selection control for allowing the user to select whether to "agree" or "disagree" to providing personal information to the electronic device.

[0021] As can be understood, the above notification and user permission acquisition process is merely a rough outline and does not limit the implementation of the present disclosure, and other methods that comply with relevant laws and regulations can also be applied to the implementation of the present disclosure.

[0022] As can be understood, the data related to the technical proposal (including but not limited to the data itself, the acquisition or use of the data) should comply with the requirements of applicable laws, regulations and related provisions.

[0023] The tree view functions of previous products are all simple. For example, they only have predefined types and hierarchies, and can only expand data hierarchically. They lack flexibility in tree configuration and tree result display.

[0024]

[0013] The embodiments of the present disclosure disclose a data processing method, apparatus, device, and storage medium, which receive a target business object topology diagram set by a user, where the target business object topology diagram includes target business objects at multiple hierarchical levels; determine target instance data relationship information corresponding to the target business object topology diagram, where the target instance data relationship information includes target instance data corresponding to the target business object topology diagram and association relationships between the target instance data; generate an instance data topology diagram based on the instance data relationship information and display the instance data topology diagram. The data processing method disclosed in the embodiments of the present disclosure generates a corresponding instance data topology diagram based on the target business object topology diagram set by the user, displays the instance data topology diagram, and only needs to display the instance data required by the user, which not only significantly reduces the amount of data processing but also improves the variety and flexibility of data display.

[0025] FIG. 1 is a flow diagram of a data processing method according to an embodiment of the present disclosure, which is applied to a data processing scenario, and the method can be executed by a data processing device, which can be realized in the form of software and / or hardware, and optionally realized by an electronic device, which can be a mobile terminal, a personal computer (PC), a server, etc.

[0026] As shown in FIG. 1, the method includes steps S110 to S140, In step S110, the target business object topology diagram set by the user is received.

[0027] Here, the target business object topology diagram includes multiple hierarchies of target business objects. The target business objects may be business objects selected by a user from among the original business objects. The original business objects may be predefined business objects for a business project or business objects configured by a user according to business needs (i.e., customized original business objects). The business objects may also be referred to as work item types. In this embodiment, the configuration method of the original business objects is not limited. For example, for a business in a system development process, predefined original business objects may include "needs," "defects," "tasks," "plans," "risks," etc. The target business object topology diagram may be understood as a topology structure diagram composed of multiple target business objects, including multiple hierarchies, each of which includes at least one target business object. In this embodiment, the topology diagram may be a tree structure diagram including a root node, intermediate nodes, and leaf nodes.

[0028] In some embodiments, the process of receiving the target business object topology diagram set by the user jumps to a setting page corresponding to the target business object based on a setting operation triggered by the user for the target business object selected by the user, and displays the Selected receiving a user selection operation for a sub-target business object expanded in at least one hierarchy of the target business object; Selected Alternatively, the target business object topology diagram may be obtained with the target business object as the root node.

[0029] Here, a configuration operation triggered on a user-selected target business object can be understood as a configuration operation triggered on a view of the selected target business object. Selected Any sub-target business object that is expanded at least one level in the target business object must be expanded at least one level in the topology tree of the original business object. Selected The target business object can be understood to be deployed.

[0030] A settings page may contain a resource panel and a settings panel. The resource panel and the settings panel are in different areas. The settings panel is Selected The resource panel is used to receive a user's selection operation for at least one hierarchically expanded sub-target business object of the target business object, and is used to display the target business object selected by the user in the setting panel and its attribute information. In the resource panel, the target business objects are displayed in the form of a list in the order of their hierarchical relationship. In this embodiment, the attribute information is provided so that the user can drag and select.

[0031] In this embodiment, when a user needs to configure a target business object topology diagram, they first click the Settings button in the view of the selected target business object to enter the settings page, which displays the selected target business object in the Resources panel and Settings panel. If the selected target business object has sub-target business objects, a drop-down button is provided for the target business object. Clicking this drop-down button displays the sub-target business objects of this target business object, allowing the user to select one or more sub-target business objects. If the selected sub-target business object still has sub-target business objects, the drop-down button remains set for the user to pull down and select, continuing in this manner until a leaf node is selected, thereby selecting multiple target business objects with a hierarchical relationship. All selected target business objects constitute the target business object topology diagram.

[0032] For example, FIG. 2a shows an example of an original business object topology diagram in this embodiment. As shown in FIG. 2a, the original business objects include "Needs," "Versions," "Defects," "Plans," and "Risks." "Needs" is in the first hierarchy, "Versions" is in the second hierarchy, "Plans" and other "Needs" are in the third hierarchy, and "Risks" is in the fourth hierarchy. Here, "Needs" is the root node, "Versions" is a subnode of "Needs," "Plans" and other "Needs" are both subnodes of "Versions," and "Risks" is a subnode of "Needs." FIG. 2b shows an example of a setting page in this embodiment. As shown in FIG. 2b, the left area is a resource panel that displays selected target business objects in a list. The setting panel can receive setting operations triggered by the user. As shown in FIG. 2b, the resource panel can also display attribute information for each target business object. "Needs" includes attributes a1, a2, and a3, and "Versions" includes attributes b1 and b2. b2, and the attribute information for "Plan," "Defect," and "Risk" is not expanded. In this embodiment, the resource panel provides an expand / hide button for each original business object. The user can click this expand / hide button to expand or hide the attribute information of the original business object. As shown in FIG. 2b, if the target business object selected in the view is "Needs" and the subnode of "Needs" includes "Version," a drop-down button is provided for "Needs." The user clicks this drop-down button to display "Version." Since "Version" has subnodes, a drop-down button is also provided for "Version." Following this analogy, in the settings panel, the target business object selected by the user includes two "Needs," one "Version," and one "Plan," of which one "Needs" is in the first hierarchy, another "Needs" is in the third hierarchy, "Version" is in the second hierarchy, and "Plan" is in the third hierarchy. Figure 2c is a structural schematic diagram of the target business object topology diagram in this embodiment. As shown in Figure 2c, this topology diagram is configured based on the user's settings in Figure 2b. As shown in Figure 2c, one of them, "Needs", is the root node, "Version" is a subnode of "Needs", and another, "Needs" and "Plan", are both subnodes of "Version".

[0033] In this embodiment, users can configure the target business object topology diagram according to business needs in the front-end interface, and can freely adjust the hierarchy of business objects to improve the configuration flexibility.

[0034] In S120, the target instance data relationship information corresponding to the target business object topology diagram is determined.

[0035] Here, the target instance data relationship information includes target instance data corresponding to the target business object topology diagram and the association relationship between the target instance data. The target instance data may be understood as specific data of the target business object, the target business object may be understood as a variable, and the target instance data may be understood as the specific value of this variable. In this embodiment, the target instance data relationship information includes an instance data identifier (identity document, ID), an association relationship ID, and the instance data ID that establishes this association relationship with the target instance data. For example, the following is the relationship information for "Instance Data 1", "Instance Data 1": [{Association Relationship ID: "123", Instance Data ID: ["A", "B"]}, {Association Relationship ID: "456", Instance Data ID: ["C", "D"]}]. In the above example, it can be understood that "Instance Data 1" and "Instance Data A" have a relationship of "123", "Instance Data 1" and "Instance Data B" have a relationship of "123", "Instance Data 1" and "Instance Data C" have a relationship of "456", and "Instance Data 1" and "Instance Data D" have a relationship of "456".

[0036] In this embodiment, the method for determining the target instance data relationship information corresponding to the target business object topology diagram may be to obtain the original instance data relationship information corresponding to the original business object set, and then filter the original instance data relationship information according to the target business object topology diagram to obtain the target instance data relationship information.

[0037] Here, the set of original business objects may include multiple original business objects, and the multiple original business objects may form a topology structure diagram, i.e., there is a hierarchical relationship between the original business objects. The original instance data relationship information may be information pre-stored in a database, or may be the entire amount of instance data relationship information corresponding to the set of original business objects. In some embodiments, the process of filtering the original instance data relationship information based on the target business object topology diagram may first extract instance data corresponding to each target business object based on identifier information of each target business object, further filter the extracted instance data based on the association relationships corresponding to the extracted instance data and the hierarchical relationships in the target business object topology diagram, and determine the relationship information corresponding to the filtered instance data as the target instance data relationship information.

[0038] In some embodiments, the method of filtering the original instance data relationship information to obtain the target instance data relationship information based on the target business object topology diagram includes traversing the target business object topology diagram to obtain a plurality of candidate instance data corresponding to the traversed target business object, obtaining target instance data of the parent node of the traversed target business object, and selecting from the plurality of candidate instance data those instances that have an association relationship with the target instance data of the parent node. candidate Filters the instance data and returns it as the target instance data of the traversed target business object. The obtained candidate instance data The association relationship corresponding to the target instance data may be determined and its hierarchical information may be recorded.

[0039] Here, the hierarchical information is hierarchical information in which there is a target business object corresponding to the target instance data, and the manner of traversing the target business object topology diagram may be to start from the root node and traverse until all target business objects in the target business object topology diagram have been traversed.

[0040] In this embodiment, the original instance data relationship information further includes identifier information of the business object corresponding to the current instance data. The method for obtaining multiple candidate instance data corresponding to the traversed target business object may be to extract multiple candidate instance data corresponding to the traversed target business object from the original instance data relationship information based on the identifier information of the traversed target business object. If the traversed target business object is a root node, all of the extracted candidate instance data are used as target instance data. If the traversed target business object is not a root node, the target instance data of the parent node of the traversed target business object is obtained, and the multiple candidate instance data are selected to be those that have a relationship with the target instance data of the parent node. candidate Filters the instance data and returns it as the target instance data of the traversed target business object. The obtained candidate instance data Confirm.

[0041] For example, for the target business object topology diagram in FIG. 2c, start traversing this target business object topology diagram from the root node, first traverse the root node “Needs”, and based on the identifier information of “Needs”, obtain its candidate instance data, which are instance data A1, instance data A2, instance data A3, and instance data A4 respectively. Since this “Needs” is the root node, all of these four instance data are the target instance data of “Needs”, and then create a hierarchy of these four instance data. informationis recorded as the first layer, then traverses "Version" and obtains its candidate instance data, which are instance data B1, instance data B2, and instance data B3, respectively, based on the identifier information of "Version", where instance data B1 has an association relationship with instance data A1 and instance data A3, and instance data B3 has an association relationship with instance data A4, the target instance data of "Version" are instance data B1 and instance data B3, and the hierarchical information of these two instance data is recorded as the second layer, then traverses "Plan" and obtains its candidate instance data, which are instance data C1, instance data C2, and instance data C3, respectively, based on the identifier information of "Plan". The "Plan" retrieves instance data, where instance data C1 has a relationship with instance data B1, and the target instance data of the "Plan" is instance data C1, and the hierarchical information of this instance data is recorded as the third tier. The "Needs" is then traversed, and its candidate instance data, which are instance data A1, instance data A2, instance data A3, and instance data A4, are retrieved based on the identifier information of the "Needs." Where instance data A2 and instance data A3 both have a relationship with instance data B1, the target instance data of the "Needs" are instance data A2 and instance data A3, and the hierarchical information of these two instance data is recorded as the third tier. In this embodiment, recording the hierarchical information of each instance data is advantageous for accurately generating the instance data topology diagram later.

[0042] In this embodiment, the original instance data relationship information is filtered based on the association relationship and the target business object topology diagram, thereby improving the efficiency and accuracy of obtaining the relationship information.

[0043] Select from multiple candidate instance data that have a relationship with the target instance data of the parent node candidate After filtering the instance data, the method further includes obtaining a filtering condition set by a user for the traversed target business object, and further filtering the target instance data based on the filtering condition.

[0044] Here, the filtering conditions are set by the user for the target business object according to business needs. Further filtering of the target instance data based on the filtering conditions can be understood as retaining target instance data that meets the filtering conditions. In this embodiment, after the user sets the filtering conditions, the system jumps to a filtering condition setting page. On this page, a filtering box is set for each target business object. The user triggers and clicks on the filtering box to display the filtering range of the target business object. The user then selects a subrange from the filtering range, thereby obtaining the filtering conditions for the target business object. For example, if the filtering condition for a target business object is P0, then only the instance data with the value P0 for the target business object will be included. In this embodiment, the target instance data is further filtered based on the filtering conditions set by the user, reducing the amount of data and thereby improving data processing efficiency.

[0045] In S130, an instance data topology diagram is generated based on the target instance data relationship information.

[0046] Here, the target instance data relationship information includes association relationship and hierarchy information corresponding to each target instance data, so that an instance data topology diagram can be generated based on the target instance data relationship information.

[0047] In some embodiments, the method for generating an instance data topology diagram based on target instance data relationship information may include grouping the target instance data based on association relationships, sorting the grouped target instance data according to hierarchical information, establishing topology connections for the sorted target instance data, and generating an instance data topology diagram corresponding to each group.

[0048] Here, the process of grouping the target instance data based on the association relationships may involve obtaining target instance data that can form an association relationship chain, and dividing the target instance data in the same association relationship chain into one group, where the association relationship chain has branches. Based on the above example, the target instance data corresponding to the target business object topology diagram of Figure 2c includes instance data A1, instance data A2, instance data A3, instance data A4, instance data B1, instance data B3, instance data C1, instance data A2, and instance data A3. The formed association relationship chain includes instance data A1~instance data B1~(instance data C1, instance data A2) and instance data A3~instance data B1~(instance data C1, instance data A3). After obtaining two association relationship chains, the target instance data can be divided into two groups.

[0049] Here, the method for sorting the grouped target instance data according to the hierarchical information is to sort the target instance data of each group in order from high to low in the hierarchy, i.e., the higher the hierarchy, the higher it is sorted to the top, same The target instance data in the hierarchy may be sorted in the same order. Based on the above embodiment, the results of sorting the target instance data of two groups, instance data A1~instance data B1~(instance data C1, instance data A2) and instance data A3~instance data B1~(instance data C1, instance data A3), are (1) instance data A1, (2) instance data B1, (3) instance data C1 and instance data A2, and (1) instance data A3, (2) instance data B1, (3) instance data C1 and instance data A3.

[0050] In some embodiments, the process of performing topological connections on the sorted target instance data may involve connecting target instance data that are adjacent in order and have an associated relationship to obtain an instance data topology diagram corresponding to each group. Based on the above embodiment, if the target instance data is divided into two groups, two instance data topology diagrams can be obtained. For example, FIGS. 3a and 3b show examples of instance data topology diagrams in this embodiment. As shown in FIG. 3a, FIG. 3a is obtained by performing topological connections on target instance data in the group consisting of (1) instance data A1, (2) instance data B1, (3) instance data C1, and instance data A2. As shown in FIG. 3b, FIG. 3b is obtained by performing topological connections on target instance data in the group consisting of (1) instance data A3, (2) instance data B1, and (3) instance data C1 and instance data A3.

[0051] In this embodiment, the target instance data is grouped, then sorted, and finally connected to the topology, thereby improving the accuracy of the generated instance data topology diagram.

[0052] Selectable, target After generating the instance data topology diagram based on the instance data relationship information, it further includes the steps of obtaining user authority information, and trimming the instance data topology diagram based on the authority information to obtain a final instance data topology diagram.

[0053] Here, the user's authority information may be set in advance based on the user identifier, and this authority information includes the range of instance data that the user can access.

[0054] In some embodiments, the process of trimming the instance data topology diagram based on the permission information may be to first determine the target instance data to which the user does not have access permission based on the permission information, and then trim the topology sub-diagram of the instance data with the target instance data as the root node in the instance data topology diagram, thereby obtaining the final instance data topology diagram. For example, Figure 4 is a diagram showing an example of trimming the instance data topology diagram in this embodiment. As shown in Figure 4, the left side is target The instance data topology diagram is generated based on the instance data relationship information. If the user does not have access rights to the instance data C, the instance topology subdiagram in the instance data topology diagram is Mu and Then, we need to trim the topology subdiagram of the instance data to obtain the final instance data topology diagram on the right.

[0055] In this embodiment, the instance data topology diagram is trimmed based on the authority information, which not only further reduces the amount of data but also improves the security of the data.

[0056] In S140, the instance data topology diagram is displayed.

[0057] Here, the instance data consists of an instance data identifier and attribute information of the instance data, and displaying the instance data topology diagram can be understood as displaying the determined target instance data in the form of a topology diagram.

[0058] In some embodiments, the manner of displaying the instance data topology diagram may be to obtain the instance data and hierarchical information of each node in the instance data topology diagram, and display the instance data of each node in the form of a list based on the hierarchical information.

[0059] Here, the list format can be understood as one instance data occupying one row or one instance data occupying one column, and the instance data identifier and the attribute information of the instance data are displayed in a certain order in the corresponding column or row. In this embodiment, the instance data identifier can be placed at the top. In order to match the displayed data with the topology diagram, different levels are displayed in different indices. To Corresponding and indentical To The hierarchical information has an inverse proportional relationship, that is, the higher the hierarchical level, the smaller the indentation information, and the lower the hierarchical level, the larger the indentation information. In this embodiment, the hierarchical level where the root node is located is the highest.

[0060] In this embodiment, the process of displaying the instance data of each node in the form of a list based on the hierarchical information may involve determining the position information of the cell where the instance data of each node is located based on the hierarchical information, and displaying the instance data of each node in the form of a list based on the position information.

[0061] Here, the cells are column cells or row cells, and the position information includes indentation information.

[0062] In some embodiments, if a cell is a row cell, the indentation information is the horizontal indentation size, and the row height of the row cell needs to be set. The process of determining the position information of a cell containing instance data for each node based on the hierarchical information may involve first determining the sorting of the instance data for that node based on the hierarchical information, then determining the ordinate of the corresponding cell based on the sorting and the row height, and then determining the horizontal indentation size of that cell based on the hierarchical information, and determining the abscissa based on the horizontal indentation size, where the abscissa and ordinate constitute the cell position information. After obtaining the position information for each cell, the instance data is rendered into the corresponding cell for display.

[0063] In some embodiments, if a cell is a column cell, the indentation information is the vertical indentation size, and the column width of the column cell needs to be set. The process of determining the position information of the cell containing the instance data of each node based on the hierarchical information may be to first determine the sorting of the instance data of this node based on the hierarchical information, then determine the horizontal coordinate of the corresponding cell based on the sorting and the column width and height, and then determine the vertical indentation size of this cell based on the hierarchical information, and determine the vertical coordinate, horizontal coordinate, and vertical coordinate position information of the process cell based on the vertical indentation size. After obtaining the position information of each cell, the instance data is rendered and displayed in the corresponding cell.

[0064] For example, Figure 5 is a diagram showing an example of displaying instance data in an embodiment of the present invention. As shown in Figure 5, Figure 5 is a schematic diagram displaying instance data corresponding to Figures 3a and 3b. As shown in Figure 5, the displayed instance data is indented differently relative to the target instance data according to different hierarchies so that they have a hierarchical relationship.

[0065] In this embodiment, the instance data of each node is displayed in the form of a list based on the hierarchical information, and the displayed instance data conforms to the topology structure, thereby improving the diversity of data display.

[0066] In the technical solutions of the embodiments of the present disclosure, a target business object topology diagram set by a user is received, where the target business object topology diagram includes target business objects of multiple hierarchies; and target instance data relationship information corresponding to the target business object topology diagram is determined, where the target instance data relationship information includes target instance data corresponding to the target business object topology diagram and association relationships between the target instance data; target An instance data topology diagram is generated based on the instance data relationship information, and the instance data topology diagram is displayed. The data processing method disclosed in the embodiments of the present disclosure displays the instance data topology diagram based on the instance data topology diagram corresponding to the target business object topology diagram set by the user, and only needs to display the instance data required by the user, which not only greatly reduces the amount of data processing but also improves the variety and flexibility of data display.

[0067] FIG. 6 is a structural schematic diagram of a data processing device according to an embodiment of the present disclosure. As shown in FIG. 6, the device includes: a target business object topology diagram setting module 610 for receiving a target business object topology diagram set by a user, where the target business object topology diagram includes target business objects of multiple hierarchies; a target instance data relationship information determination module 620 for determining target instance data relationship information corresponding to the target business object topology diagram, where the target instance data relationship information includes target instance data corresponding to the target business object topology diagram and association relationships between the target instance data; target an instance data topology diagram generation module 630 for generating an instance data topology diagram based on the instance data relationship information; and a display module 640 for displaying the instance data topology diagram.

[0068] Optionally, the target business object topology diagram setting module 610 further includes: Jump to a configuration page corresponding to the target business object based on the configuration operation triggered by the user for the target business object selected; In the settings page Selected The target business object topology diagram is used to receive a user's selection operation on a sub-target business object expanded in at least one hierarchy of the target business object, and to obtain a target business object topology diagram with the target business object as the root node.

[0069] Optionally, the target instance data relationship information determination module 620 further: Obtain original instance data relationship information corresponding to the original business object set; It is used to filter the original instance data relationship information to obtain the target instance data relationship information based on the target business object topology diagram.

[0070] Optionally, the target instance data relationship information determination module 620 further: traverse the target business object topology diagram and obtain a plurality of candidate instance data corresponding to the traversed target business object; Gets the target instance data of the parent node of the traversed target business object, Multiple candidate instance data have an association with the target instance data of the parent node candidate Filters the instance data and returns it as the target instance data of the traversed target business object. The obtained candidate instance data Confirmed, It is used to record the association relationship corresponding to the target instance data and its hierarchical information, where the hierarchical information is the hierarchical information of the target business object corresponding to the instance data. the law of nature, Selectable, and more Obtaining the filtering conditions set by the user for the traversed target business object; A filtering module is included for further filtering the target instance data based on the filtering conditions.

[0071] Optionally, the instance data topology diagram generation module 630 further comprises: Groups target instance data based on association relationships, Sorting the grouped target instance data according to hierarchical information, The sorted target instance data is connected to a topology and used to generate an instance data topology diagram corresponding to each group.

[0072] Selectable, and more Get user permission information, The system further includes an instance data topology diagram cropping module for cropping the instance data topology diagram based on the authority information to obtain a final instance data topology diagram.

[0073] Optionally, the display module 640 further includes: Retrieve the instance data and hierarchy information of each node in the instance data topology diagram, It is used to display the instance data of each node in list form based on hierarchical information.

[0074] Optionally, the display module 640 further includes: Determine position information of a cell having instance data of each node based on the hierarchy information, where the cell is a column cell or a row cell, and the position information includes indentation information; It is used to display the instance data of each node in list form based on its location information.

[0075] A data processing device according to the embodiments of the present disclosure can execute the data processing method according to any embodiment of the present disclosure, and has corresponding functional modules and beneficial effects for executing the method.

[0076] Note that each unit and module included in the above device is simply divided according to functional logic, but is not limited to the above division, as long as it can realize the corresponding function. Furthermore, the specific names of each functional unit are simply used to distinguish them from each other, and are not intended to limit the scope of protection of the embodiments of the present disclosure.

[0077] FIG. 7 is a structural schematic diagram of an electronic device according to an embodiment of the present disclosure. Reference will now be made to FIG. 7, which illustrates a structural schematic diagram of an electronic device (e.g., a terminal device or server in FIG. 7) 500 suitable for implementing an embodiment of the present disclosure. The terminal device in the embodiment of the present disclosure may include, but is not limited to, mobile terminals such as mobile phones, notebook computers, digital broadcast receivers, personal digital assistants (PDAs), tablet computers (PADs), portable multimedia players (PMPs), and in-vehicle terminals (e.g., in-vehicle navigation terminals), as well as fixed terminals such as digital TVs and desktop computers. The electronic device illustrated in FIG. 7 is merely an example and does not impose any limitations on the functionality and scope of use of the embodiment of the present disclosure.

[0078] 7, electronic device 500 may include a processing unit (e.g., a central processing unit, an image processing unit, etc.) 501, which may perform various appropriate operations and processes based on programs stored in read-only memory (ROM) 502 or programs loaded from storage device 508 into random access memory (RAM) 503. RAM 503 also stores various programs and data required for the operation of electronic device 500. Processing unit 501, ROM 502, and RAM 503 are connected to one another via bus 504. Input / output (I / O) interface 505 is also connected to bus 504.

[0079] Typically, devices such as input devices 506 including a touch screen, touch pad, keyboard, mouse, camera, microphone, accelerometer, gyroscope, etc., output devices 507 including a liquid crystal display (LCD), speaker, vibrator, etc., storage devices 508 including magnetic tape, hard disk, etc., and communication devices 509 may be connected to the I / O interface 505. The communication devices 509 may enable the electronic device 500 to communicate wirelessly or via wires with other devices to exchange data. While FIG. 7 illustrates the electronic device 500 with various devices, it should be understood that it is not required to implement or include all of the devices shown. More or fewer devices may alternatively be implemented or included.

[0080] In particular, according to embodiments of the present disclosure, the processes described with reference to the flowcharts above may be implemented as a computer software program. For example, embodiments of the present disclosure include a computer program product including a computer program carried on a non-transitory computer-readable medium, the computer program including program code for performing the methods illustrated in the flowcharts. In such embodiments, the computer program may be downloaded and installed from a network via the communication device 509, or may be installed from the storage device 508, or may be installed from the ROM 502. When the computer program is executed by the processing device 501, the functions described above, which are specific to the methods of the embodiments of the present disclosure, are performed.

[0081] The names of messages or information interacting between devices in the embodiments of the present disclosure are for illustrative purposes only and are not intended to limit the scope of these messages or information.

[0082] The electronic device according to the embodiment of the present disclosure belongs to the same inventive concept as the data processing method according to the above embodiment, and the technical details not described in detail in this embodiment can be referred to the above embodiment, and this embodiment has the same beneficial effects as the above embodiment.

[0083] An embodiment of the present disclosure provides a computer storage medium having a computer program stored thereon, which, when executed by a processor, implements the data processing method according to the embodiment.

[0084] It should be noted that the computer-readable medium described in this disclosure may be a computer-readable signal medium, a computer-readable storage medium, or any combination of the above. The computer-readable storage medium may be, for example, but is not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of the computer-readable storage medium may include, but are not limited to, an electrical connection having one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc-read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In this disclosure, a computer-readable storage medium may be any tangible medium that contains or stores a program, which may be used by or in combination with an instruction execution system, apparatus, or device. In this disclosure, a computer-readable signal medium may include a propagated data signal, either in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals may take various forms, including, but not limited to, electromagnetic signals, optical signals, or any suitable combination of the above. A computer-readable signal medium may be any computer-readable medium other than a computer-readable storage medium, which is capable of transmitting, propagating, or transporting a program used by or in connection with an instruction execution system, apparatus, or device. The program code contained in the computer-readable medium may be transmitted over any suitable medium, including, but not limited to, electrical wire, optical cable, radio frequency (RF), or the like, or any suitable combination of the above.

[0085] In some embodiments, clients and servers may communicate using any network protocol now known or hereafter developed, such as HTTP (HyperText Transfer Protocol), and may be interconnected (e.g., a communications network) to communicate digital data in any form or medium. Examples of communications networks include local area networks (LANs), wide area networks (WANs), internetworks (e.g., the Internet), and end-to-end networks (e.g., ad hoc networks), as well as any networks now known or hereafter developed.

[0086] The computer-readable medium may be included in the electronic device, or may exist independently of the electronic device.

[0087] The computer-readable medium carries one or more programs, and when the one or more programs are executed by the electronic device, the electronic device: The computer-readable medium carries one or more programs, and when the one or more programs are executed by the electronic device, the electronic device receives a target business object topology diagram set by a user, where the target business object topology diagram includes target business objects at multiple hierarchies; determines target instance data relationship information corresponding to the target business object topology diagram, where the target instance data relationship information includes target instance data corresponding to the target business object topology diagram and association relationships between the target instance data; generates an instance data topology diagram based on the target instance data relationship information; and displays the instance data topology diagram.

[0088] Computer program code for carrying out the operations of the present disclosure can be written in one or more programming languages, or a combination thereof, including, but not limited to, object-oriented programming languages ​​such as Java, Smalltalk, C++, and the like, as well as conventional procedural programming languages ​​such as "C" or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. When referring to a remote computer, the remote computer may be connected to the user's computer via any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet Service Provider).

[0089] The flowcharts and block diagrams in the drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowcharts or block diagrams may represent a module, program segment, or portion of code, including one or more executable instructions for implementing a given logical function. It should be noted that in some alternative implementations, the functions marked in the blocks may be implemented in an order different from that shown in the drawings. For example, two successively shown blocks may actually be executed essentially in parallel, or some functions may be executed in the reverse order. It should be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, may be implemented in a dedicated hardware-based system that performs a given function or operation, or in a combination of dedicated hardware and computer instructions.

[0090] The units described in the embodiments of the present disclosure may be realized in the form of software or hardware. Here, the names of the units may not necessarily limit the units themselves. do not have.

[0091] The functionality described herein above may be performed, at least in part, by one or more hardware logic elements. For example, without limitation, typical types of hardware logic elements that may be used include Field-Programmable Gate Arrays (FPGAs), Application Specific Integrated Circuits (ASICs), Application Specific Standard Products (ASSPs), Systems on a Chip (SOCs), Complex Programmable Logic Devices (CPLDs), etc.

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

[0093] According to one or more embodiments of the present disclosure, there is provided a data processing method, the method comprising: receiving a target business object topology diagram set by a user, wherein the target business object topology diagram includes target business objects of multiple hierarchies; determining target instance data relationship information corresponding to the target business object topology diagram, where the target instance data relationship information includes target instance data corresponding to the target business object topology diagram and association relationships between target instance data; generating an instance data topology diagram based on the target instance data relationship information; and displaying the instance data topology diagram.

[0094] Further, receiving the target business object topology diagram set by the user includes: Jumping to a setting page corresponding to a target business object selected by a user based on a setting operation triggered by the user for the target business object; In the setting page Selected The method includes receiving a user selection operation on a sub-target business object expanded in at least one hierarchy of a target business object, and obtaining a target business object topology diagram with the target business object as the root node.

[0095] Furthermore, determining target instance data relationship information corresponding to the target business object topology diagram includes: obtaining original instance data relationship information corresponding to the original set of business objects; filtering the original instance data relationship information to obtain target instance data relationship information based on the target business object topology diagram.

[0096] Furthermore, filtering the original instance data relationship information to obtain target instance data relationship information based on the target business object topology diagram includes: traversing the target business object topology diagram to obtain a plurality of candidate instance data corresponding to the traversed target business object; Obtaining target instance data of the parent node of the traversed target business object; The plurality of candidate instance data have an association relationship with the target instance data of the parent node. candidate Filters the instance data and returns it as the target instance data of the traversed target business object. The obtained candidate instance data To confirm and and recording hierarchy information, which is hierarchy information in which an association relationship corresponding to the target instance data and a target business object corresponding to the target instance data are present.

[0097] Furthermore, the plurality of candidate instance data are associated with the target instance data of the parent node. candidate After filtering the instance data, Obtaining a filtering condition set by a user for the traversed target business object; Further filtering the target instance data based on the filtering condition.

[0098] Further, generating an instance data topology diagram based on the target instance data relationship information includes: grouping the target instance data based on the association relationships; sorting the grouped target instance data according to the hierarchical information; and performing topology connections on the sorted target instance data to generate instance data topology diagrams corresponding to each group.

[0099] Furthermore, the above target After generating an instance data topology diagram based on the instance data relationship information, obtaining authorization information of the user; The method further includes trimming the instance data topology diagram based on the authority information to obtain a final instance data topology diagram.

[0100] Further, displaying the instance data topology diagram includes: Obtaining instance data and hierarchy information for each node in the instance data topology diagram; and displaying the instance data of each node in the form of a list based on the hierarchical information.

[0101] Furthermore, displaying the instance data of each node in the form of a list based on the hierarchical information includes: Determining position information of a cell where instance data of each node is located based on the hierarchical information, where the cell is a column cell or a row cell, and the position information includes indentation information; and displaying the instance data of each node in the form of a list based on the position information.

[0102] The above description merely describes the preferred embodiments of the present disclosure and the technical principles used. As will be understood by those skilled in the art, the scope of disclosure covered by the present disclosure is not limited to the technical solution consisting of a specific combination of the above technical features, but should also encompass other technical solutions formed by any combination of the above technical features or their equivalent features without departing from the concept of the above disclosure. For example, it should also encompass technical solutions formed by mutually replacing the above features with (but not limited to) technical features having similar functions disclosed in the present disclosure.

[0103] Also, although operations are described using a particular order, this should not be understood as requiring that these operations be performed in the particular order shown or in a sequential order. In certain environments, multitasking and parallel processing may be advantageous. Similarly, although the above discussion includes several specific implementation details, these should not be construed as limitations on the scope of the disclosure. Some features that are described in the context of separate embodiments may also be combined and implemented in a single embodiment. Conversely, various features that are described in the context of a single embodiment may also be implemented in multiple embodiments individually or in any suitable subcombination.

[0104] Although the present subject matter has been described employing language specifying structural features and / or methodological logic operations, it should be understood that the subject matter defined in the appended claims is not limited to the specific features or operations described above. Rather, the specific features and operations described above are merely example forms of implementing the claims.

Claims

1. 1. A data processing method comprising: receiving a target business object topology diagram set by a user, wherein the target business object topology diagram includes target business objects of multiple hierarchies; determining target instance data relationship information corresponding to the target business object topology diagram, where the target instance data relationship information includes target instance data corresponding to the target business object topology diagram and association relationships between target instance data; generating an instance data topology diagram based on the target instance data relationship information; and displaying the instance data topology diagram.

2. receiving a target business object topology diagram set by a user; Jumping to a setting page corresponding to a target business object selected by a user based on a setting operation triggered by the user for the target business object; 2. The method of claim 1, further comprising: receiving a user selection operation on a sub-target business object expanded in at least one hierarchy of the target business object within the setting page; and obtaining a target business object topology diagram with the target business object as a root node.

3. determining target instance data relationship information corresponding to the target business object topology diagram; Obtaining original instance data relationship information corresponding to the original set of business objects; and filtering the original instance data relationship information to obtain target instance data relationship information based on the target business object topology diagram.

4. filtering the original instance data relationship information to obtain target instance data relationship information based on the target business object topology diagram; traversing the target business object topology diagram to obtain a plurality of candidate instance data corresponding to the traversed target business object; Obtaining target instance data of the parent node of the traversed target business object; filtering instance data that has a relationship with the target instance data of the parent node from the plurality of candidate instance data, and determining the filtered instance data as target instance data of the traversed target business object; and recording an association relationship corresponding to the target instance data and its hierarchy information, wherein the hierarchy information is hierarchy information in which a target business object corresponding to the target instance data exists.

5. After filtering the instance data that has a relationship with the target instance data of the parent node from the plurality of candidate instance data, Obtaining a filtering condition set by a user for the traversed target business object; The method of claim 4 , further comprising: further filtering the target instance data based on the filtering condition.

6. generating an instance data topology diagram based on the target instance data relationship information, grouping the target instance data based on the association relationships; sorting the grouped target instance data according to the hierarchical information; 5. The method of claim 4, further comprising: performing topology connections on the sorted target instance data to generate instance data topology diagrams corresponding to each group.

7. After generating an instance data topology diagram based on the target instance data relationship information, obtaining authorization information of the user; The method of claim 1 , further comprising: cropping the instance data topology diagram based on the authority information to obtain a final instance data topology diagram.

8. Displaying the instance data topology diagram includes: Obtaining instance data and hierarchy information for each node in the instance data topology diagram; and displaying the instance data of each node in the form of a list based on the hierarchical information.

9. Displaying the instance data of each node in the form of a list based on the hierarchical information determining position information of a cell where instance data of each node is located based on the hierarchy information, where the cell is a column cell or a row cell, and the position information includes indentation information; and displaying the instance data of each node in the form of a list based on the location information.

10. 1. A data processing device, comprising: a target business object topology diagram setting module for receiving a target business object topology diagram set by a user, where the target business object topology diagram includes target business objects of multiple hierarchies; a target instance data relationship information determining module for determining target instance data relationship information corresponding to the target business object topology diagram, where the instance data relationship information includes target instance data corresponding to the target business object topology diagram and association relationships between target instance data; an instance data topology diagram generation module for generating an instance data topology diagram based on the target instance data relationship information; a display module for displaying the instance data topology diagram.

11. An electronic device, one or more processors; a storage device for storing one or more programs; An electronic device that, when the one or more programs are executed by the one or more processors, causes the one or more processors to implement the data processing method according to any one of claims 1 to 9.

12. A storage medium containing computer-executable instructions for performing the data processing method of any one of claims 1 to 9 when executed by a computer processor.

Citation Information

Patent Citations

  • Topological diagram display method and device, storage medium and equipment

    CN112579558A

  • Method and device for configuring network

    CN115277428A

  • Topological map presentation system, topological map presentation method, and computer program

    JP2020177581A

  • Topology information system for a managed world

    US20040059812A1

  • Hierarchy manager for master data management

    US20100088334A1