Management view generation method and device, storage medium, product and electronic equipment

Abstract

This application provides a management view generation method, apparatus, storage medium, product, and electronic device. The method includes: responding to a first selection operation on a target configuration change record corresponding to a target service; determining a first timestamp corresponding to the target configuration change record; based on the first timestamp, searching for first snapshot data corresponding to the target service from a historical snapshot database, the historical snapshot database including historical snapshot data corresponding to the target service at different timestamps, each historical snapshot data being generated based on a changed configuration graph when such a graph has changed; the configuration graph representing the relationships between various decision element nodes during the decision execution process of the target service; and displaying the management view corresponding to the first snapshot data in a decision management view window. This method provides a visual management view of the historical management status of the target service, offering decision support for users in business management.

Description

Technical Field

[0001] This application relates to the field of computer technology, and more specifically, to a method, apparatus, storage medium, product, and electronic device for generating management views in the field of computer technology. Background Technology

[0002] With the rapid development of cutting-edge technologies such as big data, cloud computing, and artificial intelligence, many internet businesses have emerged. The strategic operation process of these internet businesses often requires risk control (referred to as risk management).

[0003] However, current risk decision-making systems mainly rely on running and setting risk control rules to make risk decisions. After the risk control decision-making system is developed, it is like a black box to non-system developers. Business personnel responsible for risk control have difficulty understanding the rule operation process and rule update process of the risk control decision-making system. As a result, business personnel responsible for risk control cannot fully understand the current situation of risk control and find it difficult to formulate comprehensive risk control strategies. Summary of the Invention

[0004] In view of this, this application provides a management view generation method, apparatus, storage medium, product, and electronic device. This method can visualize the historical management status of a target business, quickly help users clarify complex business relationships, and provide decision support for users to conduct business management.

[0005] Firstly, a management view generation method is provided, comprising: responding to a first selection operation on a target configuration change record corresponding to a target service, determining a first timestamp corresponding to the target configuration change record, wherein the target configuration change record is one of a plurality of configuration change records; based on the first timestamp, searching for first snapshot data corresponding to the target service from a historical snapshot database, wherein the historical snapshot database includes historical snapshot data corresponding to the target service at different timestamps, wherein each historical snapshot data is generated based on the changed configuration graph when the configuration graph is changed, the configuration graph being used to represent the association relationship between various decision element nodes in the decision execution process of the target service; and displaying the management view corresponding to the first snapshot data in a decision management view window.

[0006] In the above technical solution, the management view refers to a graphical representation of the configuration graph. Specifically, when the configuration graph corresponding to the target business changes, historical snapshot data is generated based on the changed configuration graph. Then, in subsequent business management processes, by selecting the target configuration change record and based on the first timestamp recorded in that record, the first snapshot data corresponding to that first timestamp can be found from the previously generated historical snapshot data. Based on this first snapshot data, the management view of the configuration graph at the time corresponding to that first timestamp is visually reconstructed. This allows users to intuitively understand the management status at that first timestamp and make current management decisions based on that status, improving the comprehensiveness, depth, and accuracy of management decisions, and ultimately enhancing the quality of management decisions.

[0007] In conjunction with the first aspect, in some possible implementations, the decision management view window displays the multiple configuration change records, which include a change timestamp indicating that the configuration map of the target service has changed; wherein, the first selection operation is the operation of determining the target configuration change record among the multiple configuration change records, and the first timestamp is the change timestamp included in the target configuration change record.

[0008] By visually displaying multiple configuration change records, users can intuitively view the historical evolution path of the target service's configuration graph. Based on the displayed configuration change records, users can select the target configuration change record through a first selection operation. Then, based on the change timestamp recorded in the target configuration change record, the corresponding first snapshot data can be found, thereby restoring the corresponding management view. This provides users with a visual interface for selecting a management view at a specific historical time point, simplifying the process of viewing historical management views, improving viewing efficiency, and enhancing the user experience.

[0009] In conjunction with the first aspect, in some possible implementations, displaying the multiple configuration change records as described above includes: identifying the target scenario element node among multiple scenario element nodes of the target service; obtaining multiple configuration change records associated with the target scenario element node; and displaying the multiple configuration change records associated with the target scenario element node according to the order of the change timestamps included in each configuration change record.

[0010] Through the above technical solution, when the target business corresponds to multiple scenario element nodes, the configuration change records related to the target scenario element node can be determined and displayed according to the target scenario element node selected by the user. This makes it convenient for the user to view the corresponding management view according to the scenario element node. In addition, these multiple configuration change records are sorted and displayed based on the change timestamp, which makes it convenient for the user to quickly search based on time sequence, further improving the user's operation efficiency and decision-making management efficiency.

[0011] In conjunction with the first aspect, in some possible implementations, the management view corresponding to the first snapshot data is displayed in the decision management view window, including: in the decision management view window, one or more of the scene element nodes, link element nodes, component category element nodes and component element nodes included in the first snapshot data are displayed in association.

[0012] In conjunction with the first aspect, in some possible implementations, the decision management view window may display one or more of the following in association: displaying the scene element node; if a link element node associated with the scene element node exists in the first snapshot data, displaying the scene element node and the link element node in association; if a component category element node associated with the link element node exists in the first snapshot data, displaying the link element node and the component category element node in association; if a component element node corresponding to the component category element node exists in the first snapshot data, displaying the component category element node and the component element node under the component category element node in association.

[0013] The above technical solution clarifies that the first snapshot data may include one or more of scene element nodes, link element nodes, component category element nodes, and component element nodes. Dynamic tree-like hierarchical display and categorized display based on the element nodes contained in the first snapshot data can reduce the complexity of the management view and improve the level of visualization management.

[0014] In conjunction with the first aspect, in some possible implementations, the method further includes: determining a second timestamp when displaying the management view corresponding to the first snapshot data; searching for the second snapshot data corresponding to the target business from the historical snapshot database based on the second timestamp; and comparing and displaying the management view corresponding to the first snapshot data and the management view corresponding to the second snapshot data in the decision management view window.

[0015] The above technical solution allows for the comparison and display of management views corresponding to different snapshot data in the decision management view window. This facilitates users in tracing back the change status of the configuration graph corresponding to the target business and improves the efficiency of users' understanding of the historical changes in the configuration graph of the target business.

[0016] In conjunction with the first aspect, in some possible implementations, determining the second timestamp includes: in response to a view comparison operation, displaying a snapshot selection control, the snapshot selection control including a plurality of snapshot identifiers, each of the snapshot identifiers being used to indicate historical snapshot data of the target service at different timestamps; and in response to a second selection operation for a target snapshot identifier among the plurality of snapshot identifiers, determining the timestamp indicated by the target snapshot identifier as the second timestamp.

[0017] Through the above technical solution, users can decide whether to compare different historical management views, and can select the historical snapshot data to be compared through the snapshot selection control, providing a visual comparison operation process and improving the user experience.

[0018] In conjunction with the first aspect, in some possible implementations, the management view corresponding to the first snapshot data includes multiple associated decision element nodes; the method further includes: in response to a details viewing operation for a target decision element node among the multiple associated decision element nodes, displaying a details management page corresponding to the target decision element node; wherein, the details management page includes: details information of the target decision element node, and the target decision element node is one of the following: scenario element node, link element node, component category element node, and component element node of the target business.

[0019] The above technical solution enables users to navigate to and view the details management page corresponding to the target decision element node based on their actions. While ensuring that the decision management view window is concise and clear, it meets the user's need to understand the details of the target decision element node, improves the adaptability and scalability of the decision management view, and enhances the efficiency of decision management.

[0020] Secondly, a management view generation apparatus is provided, comprising: a determining unit and a generating unit; the determining unit is configured to determine a first timestamp corresponding to a target configuration change record corresponding to a target service in response to a first selection operation on a target configuration change record corresponding to a target service, wherein the target configuration change record is one of a plurality of configuration change records; the determining unit is further configured to search for first snapshot data corresponding to the target service from a historical snapshot database based on the first timestamp, wherein the historical snapshot database includes historical snapshot data corresponding to the target service at different timestamps, wherein each historical snapshot data is generated based on the changed configuration map when the configuration map is changed, and the configuration map is used to represent the association relationship between various decision element nodes in the decision execution process of the target service; the generating unit is configured to display the management view corresponding to the first snapshot data in a decision management view window.

[0021] Thirdly, a computer-readable storage medium is provided that stores computer program code, which, when executed on a computer, causes the computer to perform the methods described in the first aspect or any possible implementation thereof.

[0022] Fourthly, a computer program product is provided, comprising: computer program code, which, when run on a computer, causes the computer to perform the methods described in the first aspect or any possible implementation thereof.

[0023] Fifthly, an electronic device is provided, comprising: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the methods as described in the first aspect or any one of the first aspects. Attached Figure Description

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

[0025] Figure 1 This is a schematic flowchart of a management view generation method provided in an embodiment of this application; Figure 2 This is a schematic diagram of an example configuration map provided in an embodiment of this application; Figure 3 This is an example of a display diagram showing multiple configuration change records provided in an embodiment of this application; Figure 4 This is a schematic diagram illustrating an example of generating historical snapshot data provided in an embodiment of this application; Figure 5 This is a schematic diagram of an example of the snapshot selection control provided in an embodiment of this application; Figure 6 This is a schematic diagram of an example display process of the view comparison window provided in an embodiment of this application; Figure 7 This is a schematic diagram illustrating an example of the display process of the details management page provided in an embodiment of this application; Figure 8 This is a schematic diagram of the structure of a management view generation device provided in an embodiment of this application; Figure 9 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0026] Many specific details are set forth in the following description to provide a full understanding of this application. However, this application can be implemented in many other ways different from those described herein, and those skilled in the art can make similar extensions without departing from the spirit of this application; therefore, this application is not limited to the specific embodiments disclosed below.

[0027] It should be noted that the terms "first," "second," "third," etc., in the claims, specification, and drawings of this application are used to distinguish similar objects and are not used to describe a specific order or sequence. Such data are interchangeable where appropriate so that the embodiments of this application described herein can be implemented in a sequence other than that shown or described herein. Furthermore, the terms "comprising," "having," and their variations are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that includes a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to these processes, methods, products, or apparatuses.

[0028] It should be understood that in the embodiments of this application, "at least one" refers to one or more, "several" refers to one or more, and "more than" refers to two or more. "And / or" is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. The character " / " generally indicates that the preceding and following related objects have an "or" relationship. "Contains A, B, and / or C" means containing any one, two, or three of A, B, and C.

[0029] It should be understood that in the embodiments of this application, "B corresponding to A", "B corresponding to A", "A corresponds to B" or "B corresponds to A" means that B is associated with A, and B can be determined based on A. Determining B based on A does not mean that B is determined solely based on A; B can also be determined based on A and / or other information.

[0030] With the rapid development of cutting-edge technologies such as big data, cloud computing, and artificial intelligence, many internet businesses have emerged. The strategic operation process of these internet businesses often requires risk control (referred to as risk management).

[0031] For example, in the context of online lending, online lending broadly refers to all lending activities conducted online and based on credit, including but not limited to personal loans, business loans, and credit card services. In the financial sector, credit refers to the act of a financial institution providing funds to a user, with the user promising to repay the principal and interest at a future point in time or within a specified period.

[0032] For the aforementioned online lending businesses, strict risk control is often required to mitigate various potential risks. Specifically, a series of strategies, methods, processes, and technologies are needed to identify, assess, monitor, and mitigate these risks. Currently, automated risk identification can be achieved based on developed risk decision-making systems, reducing manual review time, improving risk control efficiency, and mitigating human error and bias to some extent.

[0033] However, currently, after the risk control decision system is developed, it is essentially a black box for non-system developers (such as risk control rule makers and reviewers). Non-system developers cannot fully grasp the rule operation process and rule update process of the risk control decision system, which makes it difficult for them to fully understand the current status of risk control and to formulate more comprehensive and in-depth risk control strategies.

[0034] To address the aforementioned technical problems, this application provides a method for generating a management view. The executing entity of this method can be an electronic device with computing capabilities, including but not limited to smartphones, tablets, desktop computers, and servers. The following describes... Figure 1 The methods of the embodiments of this application are described in detail.

[0035] Figure 1 This is a schematic flowchart illustrating a management view generation method provided in an embodiment of this application. It should be noted that the steps shown may be executed in a logical order different from that shown in the flowchart. For example, as... Figure 1 As shown, the management view generation method may include the steps shown in S110 to S130 below.

[0036] S110, in response to the first selection operation of the target configuration change record corresponding to the target service, determine the first timestamp corresponding to the target configuration change record, wherein the target configuration change record is one of multiple configuration change records.

[0037] In this application, the target business is a business that requires risk control. For example, this target business may include, but is not limited to: credit risk control, supply chain risk control, payment and settlement risk control, insurance risk control, and securities trading risk control. In this application, the management view generation method provided will be described using credit risk control as an example.

[0038] The aforementioned configuration change log refers to the record entries made when the risk control decision configuration items of the target business change. Based on this configuration change log, the change process of the risk control decision configuration items of the target business can be traced, supporting troubleshooting, compliance checks, and configuration management.

[0039] Optionally, the configuration change record may record, but is not limited to, at least one of the following: the change timestamp of the target service's configuration graph, the version information of the changed configuration graph, the information of the person making the change, and the content of the change. For example, a configuration change record may specifically include the following content: "V5.4XX changed the configuration information of YY scenario on 2026-01-10 12:33:02", where V5.4 represents the version of the target service's configuration graph after the change, specifically version 5.4; XX represents the person who changed the configuration graph of the target service as XX; 2026-01-10 12:33:02 represents the change timestamp of the target service's change; and YY scenario represents the specific content of the change in the configuration graph of the target service.

[0040] The configuration graph represents the relationships between various decision-making element nodes in the risk control decision-making execution process of the target business. The decision-making element nodes corresponding to the target business refer to the nodes corresponding to the general visualized process elements pre-defined for the risk control decision-making execution process of the target business. These general visualized process elements may include, but are not limited to, scenario elements, link elements, strategy elements, and feature elements. In the configuration graph, core elements such as scenario elements, link elements, strategy elements, and feature elements (including online and offline feature elements) can be used as nodes, and the reference relationships between various decision-making elements can be used as edges to form the configuration graph. The edges of the configuration graph maintain the change timestamps when changes occur, i.e., the historical changes of the configuration graph are maintained through the edges.

[0041] The decision element node may include, but is not limited to, at least one of the following: scene element node, link element node, component category element node, and component element node.

[0042] Specifically, scenario element nodes refer to environmental nodes defined by the target business to achieve a certain business objective. For example, in credit risk control business, scenario element nodes may include, but are not limited to: pre-loan access credit granting scenario nodes, mid-loan credit limit increase scenario nodes, post-loan reserve fund restructuring nodes, and post-loan reserve fund renewal nodes.

[0043] Link element nodes are used to describe the logical sequence of each operation step in the corresponding scenario element node. Specifically, they can be defined by the combination of the corresponding scenario element node and link attributes. For example, for the pre-loan access credit granting scenario node, its corresponding link element node may include, but is not limited to: new signing link node, re-signing link node, simplified re-signing link node, simplified new signing link node, etc. For example, the new signing link node is used to describe the logical sequence of each operation step that needs to be performed to realize the pre-loan access credit granting for new customers.

[0044] The component category element node is used to classify the various component element nodes corresponding to the target business. For example, the component category element node may include strategy category element node and non-strategy category element node. The strategy category element node is used to classify component nodes that contain decision logic, rules or conditions, while the non-strategy category element node is used to classify component nodes that do not contain decision logic but focus on performing specific tasks or functions.

[0045] Component element nodes can include feature component nodes corresponding to each strategy component node. Here, a strategy component node is a collection of various decision logics, rules, or conditions, while a feature component node is a combination of various data that can be used by the strategy component nodes. For example, in credit risk control operations, this strategy component node may include, but is not limited to: credit access strategy nodes, temporary credit limit strategy nodes, and personal review protection strategy nodes; for a credit access strategy node, its corresponding feature component nodes may include, but are not limited to: customer profile data for credit access, and potential risk data corresponding to the customer.

[0046] Among them, link element nodes, component category element nodes, strategy element nodes, feature element nodes, etc. can be reused. Different scenario element nodes can correspond to different link element nodes or the same link element node. Different link element nodes can correspond to the same strategy element node or different strategy element nodes.

[0047] For example, refer to Figure 2 , Figure 2This is a schematic diagram of a configuration map provided in an embodiment of this application.

[0048] like Figure 2 As shown, Figure 2 The configuration graph shown includes: Scene Element A node, Scene Element B node, Link Element A node, Link Element B node, Policy Element node, Feature Element node, Non-Policy Element node, Online Feature Element node, and Offline Feature Element node. Specifically, Scene Element A node is associated with both Link Element A node and Link Element B node; Scene Element B node is associated with Link Element B node, meaning both Scene Element A node and Scene Element B node are associated with Link Element B node; Link Element A node and Link Element B node are associated with the same Policy Element; Policy Element nodes are associated with Feature Element nodes and Online Feature Element nodes, etc.

[0049] In some possible implementations, the risk control process of the target business can be modeled using a Geabase graph database to obtain the above configuration graph and store it. The Geabase graph database will not be described in detail here.

[0050] The aforementioned target configuration change record is a configuration change record selected by the user from multiple configuration change records based on the first selection operation. The user involved in this application refers to a non-system developer of the aforementioned risk decision management platform, and may include, but is not limited to: risk control decision makers, risk control decision reviewers, and personnel who propose risk control business requirements.

[0051] Specifically, the target configuration change record can be determined in the following way. In some possible implementations, the management view generation method provided in this application may also include the steps shown in S100 below.

[0052] S100, in the decision management view window, multiple configuration change records are displayed. The configuration change records include the change timestamps of the configuration map of the target service. The first selection operation is the operation of determining the target configuration change record among the multiple configuration change records. The first timestamp is the change timestamp included in the target configuration change record.

[0053] In this possible implementation, the management view generation method can be applied to a risk decision management platform in an electronic device. The decision management view window refers to the graphical user interface provided by the risk decision management platform for displaying the management view. Here, the management view refers to a graphical representation of the configuration graph provided to the user; for example, this graphical representation can be a tree-like hierarchical structure, which helps users quickly clarify the reference relationships in the configuration graph.

[0054] When multiple configuration change records are displayed in the decision management view window, the aforementioned first selection operation is the operation to determine the target configuration change record among the multiple configuration change records. This operation may include, but is not limited to, clicking, swiping, and pressing. The first timestamp is the change timestamp included in the target configuration change record selected by the first selection operation. As in the example above, this first timestamp could be: 2026-01-10 12:33:02.

[0055] In a possible specific implementation, the "displaying multiple configuration change records" in S100 above can be achieved through the steps shown in S101 to S103 below.

[0056] S101, determine the target scenario element node among multiple scenario element nodes of the target business.

[0057] S102, retrieve multiple configuration change records associated with the target scene element nodes.

[0058] S103, according to the order of the change timestamps included in each configuration change record, display multiple configuration change records associated with the target scene element nodes.

[0059] As mentioned above Figure 2 As the introduction shows, each target business can contain multiple scenario element nodes, and different scenario element nodes can correspond to multiple configuration change records, making it very difficult for users to directly find the configuration change record they need.

[0060] In this optional implementation, the target business and its corresponding scenario element nodes can be displayed together in the decision management view window, and the scenario element nodes and their associated configuration change records can be displayed together. This makes it easy for users to quickly find the corresponding target scenario element node in the decision management view based on the classification of the target business and the classification of the scenario element nodes, and further obtain multiple configuration change records associated with the target scenario element node.

[0061] Specifically, based on the scene element node selection operation performed by the user, the target scene element node can be determined from multiple displayed scene element nodes. Once the target scene element node is determined, only the configuration change records associated with the target scene element node are retrieved and displayed, thereby improving the user's search efficiency.

[0062] The sorting of the change timestamps mentioned above can include sorting from oldest to newest timestamps, or sorting from newest to oldest timestamps. Sort each configuration change record based on its change timestamps and display them sequentially, which can improve the efficiency of users finding the target configuration change record.

[0063] For example, refer to Figure 3 , Figure 3 This is an example of a display diagram showing multiple configuration change records provided in an embodiment of this application.

[0064] like Figure 3 As shown, in the decision management view window 200, business nodes such as business A, business B, and business C are displayed in window area 201. When a user wants to view the management view corresponding to business A, they can click on the display area of ​​business A to display the scene element nodes associated with business A in window area 201. For example, the scene element nodes associated with business A are scene A, scene B, and scene C. Furthermore, when a user wants to view the management view corresponding to scene A, they can click on the node display area corresponding to scene A to display multiple configuration change records associated with scene A in window area 202.

[0065] For example, the multiple configuration change records displayed in window area 202 are as follows: V5.4X1 2026-01-10 12:33:02 changed the configuration information of scenario A; V5.3X1 2026-01-10 10:27:01 changed the configuration information of scenario A; V5.2X2 2026-01-8 14:27:01 changed the configuration information of scenario A; V5.1X2 2026-01-8 14:27:01 changed the configuration information of scenario A; V5.0X2 2026-01-8 11:15:01 changed the configuration information of scenario A; V4.9X2 2026-01-7 15:44:01 changed the configuration information of scenario A. The multiple configuration change records are displayed from top to bottom in order of their change timestamps, from most recent to oldest. The specific information contained in each configuration record can be found in the previous description, and will not be repeated here.

[0066] Assuming the first selection operation is a click operation as an example, if the user clicks on the configuration change record "V5.4X1 2026-01-10 12:33:02 Change configuration information of scenario A" in the above-displayed configuration change records, this configuration change record can be identified as the target configuration change record, and the change timestamp 2026-01-10 12:33:02 included in the target configuration change record can be identified as the first timestamp.

[0067] Alternatively, in an optional implementation, based on the scene element selection operation performed by the user, after determining the target scene element node from among multiple displayed scene element nodes, the management view corresponding to the latest change timestamp of the target scene element node is displayed by default in the decision view window; and a change record control (such as...) is displayed in this decision view window. Figure 3 The change log control 204 shown displays multiple configuration change records associated with the target scene element node when the user clicks the change log control, such as... Figure 3 As shown, when the user clicks the change record control 204, multiple configuration change records are displayed in the window area 202.

[0068] S120, based on the first timestamp, retrieve the first snapshot data corresponding to the target business from the historical snapshot database. The historical snapshot database includes historical snapshot data corresponding to the target business under different timestamps. Each historical snapshot data is generated based on the changed configuration map when the configuration map changes. The configuration map is used to represent the relationship between various decision element nodes in the decision execution process of the target business.

[0069] In this application, the historical snapshot database is used to store historical snapshot data corresponding to multiple business operations requiring risk control at different timestamps, including historical snapshot data corresponding to the target business at different timestamps. It should be understood that in the historical snapshot database, each historical snapshot data corresponds to a unique timestamp.

[0070] Among them, the snapshot data corresponding to the target business refers to the complete status record of the configuration graph status of the target business at a specific point in time. Its core is to capture the static image of the configuration graph of the target business at a certain moment. Based on this historical snapshot data, the status of the configuration graph at that point in time can be restored, status changes can be compared, or data backup and recovery can be achieved.

[0071] The aforementioned first snapshot data is the historical snapshot data corresponding to the first timestamp in the historical snapshot database, that is, the historical snapshot data corresponding to the target configuration change record.

[0072] For example, refer to Figure 4 , Figure 4 This is a schematic diagram illustrating an example of generating historical snapshot data provided in an embodiment of this application.

[0073] like Figure 4As shown, at time T1, a new scene element node A is added to the configuration graph, and snapshot data corresponding to the configuration graph at time T1 is generated. This snapshot data stores the complete state record of the configuration graph at time T1. At time T2, a new link element node A is added to the configuration graph, and an association relationship is established between the scene element node A and the link element node A. This snapshot data corresponding to the configuration graph at time T2 is generated. This snapshot data stores the complete state record of the configuration graph at time T2. At time T3, compared to time T2, a new link element node B is added to the configuration graph, and an association relationship is established between the scene element node A and the link element node B. This snapshot data corresponding to the configuration graph at time T3 is generated. This snapshot data stores the complete state record of the configuration graph at time T3.

[0074] Therefore, after obtaining the first timestamp included in the target configuration change record, the corresponding historical snapshot data can be found in the historical snapshot database based on the first timestamp.

[0075] S130, Display the management view corresponding to the first snapshot data in the decision management view window.

[0076] After obtaining the first snapshot data corresponding to the target configuration change record, the management view corresponding to the configuration map of the target service under the first timestamp can be restored and displayed based on the first snapshot data.

[0077] In the above technical solution, when the configuration graph corresponding to the target business changes, historical snapshot data is generated based on the changed configuration graph. Then, in the subsequent risk control process, by selecting the target configuration change record and based on the first timestamp recorded in the target configuration change record, the first snapshot data corresponding to the first timestamp can be found from the previously generated historical snapshot data. Based on the first snapshot data, the management view of the configuration graph at the time corresponding to the first timestamp can be visually restored, allowing users to intuitively understand the management status at the first timestamp and make current management decisions based on the management status of the configuration graph corresponding to the first timestamp, thereby improving the comprehensiveness, depth, and accuracy of management decisions and enhancing the quality of management decisions.

[0078] In some possible implementations, the step of "displaying the management view corresponding to the first snapshot data in the decision management view window" in S130 can be specifically achieved through the steps shown in S131 below.

[0079] S131, in the decision management view window, display one or more of the scene element nodes, link element nodes, component category element nodes and component element nodes included in the first snapshot data.

[0080] Optionally, the decision element nodes included in the first snapshot data refer to the decision element nodes in the configuration graph that have changed at the first timestamp, as well as all decision element nodes generated before the first timestamp that are related to the target business. Optionally, the relevant data of all decision element nodes generated before the first timestamp that are related to the target business may not be actually stored in the first snapshot data, but rather the decision element nodes and their relationships generated before the first timestamp may be extracted from the configuration graph based on the first timestamp.

[0081] In this application, when different decision element nodes are included in the first snapshot data, the decision element nodes displayed in the management view will also be different, and there is no limitation on this.

[0082] In some possible specific implementations, the "associating and displaying one or more of the scene element nodes, link element nodes, component category element nodes and component element nodes included in the first snapshot data" in S131 above can be specifically implemented through the following steps S1310 to S1313.

[0083] S1310 displays scene element nodes.

[0084] S1311, if there is a link element node associated with the scene element node in the first snapshot data, display the scene element node and the link element node together.

[0085] S1312, if there is a component category element node associated with the link element node in the first snapshot data, display the link element node and the component category element node together.

[0086] S1313, if there is a component element node corresponding to the component category element node in the first snapshot data, display the component category element node and the component element node under the component category element node together.

[0087] It should be understood that when defining the configuration graph of the target business during the development phase, the scenario elements of the target business are usually defined first, that is, the first snapshot data usually includes scenario element nodes.

[0088] The above-mentioned association displays scene element nodes and link element nodes. For example, scene element nodes and their associated link element nodes can be connected by lines (lines with arrows or without arrows). That is, the connection by lines indicates that there is an association between scene element nodes and link element nodes, and link element nodes can be child nodes of scene element nodes.

[0089] The above-mentioned association displays link element nodes and component category element nodes. As described above, links element nodes and their associated component category element nodes can be connected by lines, and component category element nodes can be child nodes of links element nodes.

[0090] The above-mentioned association displays the component category element node and the component element nodes under the component category element node. As described above, the component category element node and the component element nodes under the component category element node can be connected by lines, that is, the component element node can be a child node of the component category element node.

[0091] In the above technical solution, a dynamic tree-like hierarchical display is performed based on the element nodes contained in the first snapshot data, and the component element nodes can be classified and displayed, which reduces the complexity of the management view and improves the level of visualization management.

[0092] Reference Figure 3 Following the example above, when the user selects the configuration change record of version V5.4 as the target configuration change record, based on the first timestamp included in it, 2026-01-10 12:33:02, the first snapshot data is found in the historical snapshot database, and the corresponding management view is displayed in the window area 203 of the decision management view window 200.

[0093] Specifically, the first snapshot data includes the following decision element nodes: scenario element node (scenario A), scenario element nodes (link A, link B, and link C), component category element components (strategy category components and non-strategy category components), strategy element components (strategy A and strategy B), and feature element components (feature V1.0 and feature V1.1). Then, in window area 203, the following associations are displayed: scenario A and link A; scenario A and link B; scenario A and link C; link A and strategy category components; link A and non-strategy category components; strategy category components and strategy A; strategy category components and strategy B; strategy A and feature V1.0; and strategy A and feature V1.1, to generate the management view corresponding to this first snapshot data.

[0094] Thus, with Figure 2 Compared to the underlying configuration map shown, this Figure 3 The tree-like hierarchical management view shown reduces the complexity of understanding the configuration map for users and improves the level of visual management.

[0095] In some possible implementations, the management view generation method provided in this application may also include the steps shown in S140 to S160 below.

[0096] S140, if the management view corresponding to the first snapshot data is displayed, determine the second timestamp.

[0097] In this implementation, the second timestamp is different from the first timestamp. Based on the different first and second timestamps, the configuration map of the target service under different states at different timestamps can be determined.

[0098] In a possible specific implementation, the second timestamp can be determined through the steps shown in S141~S142 below.

[0099] S141, in response to the view comparison operation, display a snapshot selection control. The snapshot selection control includes multiple snapshot identifiers, each of which is used to indicate the historical snapshot data of the target business under different timestamps.

[0100] In this implementation, the view comparison operation can be a shortcut key operation or the following operation: displaying a comparison control that is currently closed in the decision management view window. Based on this, the view comparison operation can be a user-triggered operation on the comparison control. In response to the triggered operation, the comparison control is changed from a closed state to an open state. When the comparison control is open, the decision management view window is controlled to enter the comparison mode. After entering the comparison mode, a snapshot selection control is displayed. The triggered operation on the view comparison control can include, but is not limited to, click operations, press operations, and swipe operations.

[0101] The snapshot selection control mentioned above can be a list control, drop-down control, or other controls, and there are no restrictions on this.

[0102] The snapshot identifiers mentioned above may include, but are not limited to: the version number, specific timestamp, and custom name corresponding to each historical snapshot data.

[0103] like Figure 3 As shown, the decision management view window 200 also displays a comparison control 205 that is currently closed. When the user applies a trigger operation to the comparison control 205, the content displayed in the decision management view window 200 can be changed from closed to open. Figure 3 The content shown has been switched to Figure 5 The content shown in (a) is as follows: Figure 5 This is a schematic diagram of an example of the snapshot selection control provided in the embodiments of this application.

[0104] like Figure 5As shown in (a), a view comparison window 206 is displayed in the decision management view window 200. This view comparison window 206 displays the currently selected 5.4 version management view and a snapshot selection control 207. The snapshot selection control 207 is a drop-down control; after the user clicks the snapshot selection control 207, options can be selected as follows: Figure 5 As shown in (b), the drop-down list 208 corresponding to the snapshot selection control 207 is displayed. The drop-down list 208 displays the version numbers corresponding to multiple historical snapshot data of scenario A, such as V5.4, V5.3, V5.2, V5.1, V5.0, etc.

[0105] S142, in response to a second selection operation for a target snapshot identifier among a plurality of snapshot identifiers, determines the timestamp indicated by the target snapshot identifier as a second timestamp.

[0106] The second selection operation mentioned above may include, but is not limited to, clicking, swiping, or pressing operations on a specific snapshot identifier among multiple snapshot identifiers. The snapshot identifier selected by the second selection operation is determined as the target snapshot identifier, and the change timestamp corresponding to the historical snapshot data of the target snapshot identifier is determined as the second timestamp.

[0107] For example, based on Figure 5 (b) shows multiple snapshot identifiers. Assuming the user selects snapshot identifier V5.0, the change timestamp corresponding to the historical snapshot data indicated by snapshot identifier V5.0 can be determined as the second timestamp. Continuing from the previous example, Figure 3 Among the multiple configuration change records displayed, the change timestamp corresponding to the snapshot identifier V5.0 is 2026-01-8 11:15:01, so the second timestamp can be determined to be 2026-01-8 11:15:01.

[0108] S150, based on the second timestamp, retrieves the second snapshot data corresponding to the target business from the historical snapshot database.

[0109] S160, in the decision management view window, compare and display the management view corresponding to the first snapshot data and the management view corresponding to the second snapshot data.

[0110] After retrieving the second snapshot data based on the second timestamp, the management view corresponding to the first snapshot data and the management view corresponding to the second snapshot data are compared and displayed in the decision management view window. This facilitates users in tracing the change status of the configuration graph corresponding to the target service, improving the efficiency of users' understanding of the historical changes in the configuration graph of the target service.

[0111] Reference Figure 6 , Figure 6This is a schematic diagram of an example display process of the view comparison window provided in an embodiment of this application.

[0112] like Figure 6 As shown, when the user selects snapshot identifier V5.0, the selected snapshot identifier V5.0 can be displayed in the snapshot selection control 207. Based on the second timestamp 2026-01-08 11:15:01 corresponding to snapshot identifier V5.0, the second snapshot data is searched, and in the view comparison window 206, the management view 211 corresponding to the current version V5.4 and the management view 212 corresponding to the second snapshot data of snapshot identifier V5.0 are displayed simultaneously. In this way, it can be seen intuitively that under the second timestamp 2026-01-08 11:15:01, the configuration view corresponding to scenario A only sets strategy A, and under the first timestamp 2026-01-10 12:33:02, the configuration view corresponding to scenario A adds strategy B, and simultaneously defines features V1.0 and V1.2 related to strategy A.

[0113] Based on the simultaneously displayed management view 211 and management view 212, users can compare the changes in the configuration graph corresponding to scenario A of the target business at different times, quickly understand the historical changes of the configuration graph corresponding to scenario A, improve the user's comprehensive understanding of the evolution path of the configuration graph, and provide support for subsequent business risk decision management.

[0114] In some possible implementations, such as Figure 6 As shown, when comparing and displaying the management view corresponding to the first snapshot data and the management view corresponding to the second snapshot data, the view comparison window 206 also displays a modification control 209 and a new control 210. The modification control 209 is used to control the view comparison window 206 to enter the modification mode. In the modification mode, the user can modify the management view 211 corresponding to the first snapshot data or the management view 212 corresponding to the second snapshot data. The new control 210 is used to add management views to participate in the comparison, so as to realize the simultaneous comparison of multiple versions. This will not be described in detail here.

[0115] In some possible implementations, as described above, the management view corresponding to the first snapshot data includes multiple associated decision element nodes; based on this, the management view generation method provided in this application may also include the steps shown in S170 below.

[0116] S170, in response to the operation of viewing details of a target decision element node among multiple associated display decision element nodes, the details management page corresponding to the target decision element node is displayed; wherein, the details management page includes: detailed information of the target decision element node, and the target decision element node is one of the following: scenario element node, link element node, component category element node, and component element node of the target business.

[0117] The detailed viewing operations mentioned above may include, but are not limited to, clicking, pressing, and swiping operations on the target decision element node. The detailed information of the target decision element node describes the detailed content of that target decision element node, and may include, but is not limited to, the node information, node lineage, and node details of the target decision element node.

[0118] The node information is a detailed description of the target decision element node, which may include, but is not limited to, the node name (including Chinese and English names), node description, node status, and the version number of the snapshot data to which the node is currently located. The node description can be pre-set by the user or relevant staff to briefly summarize the name, function, and role of the node. The node status indicates whether the node is being used normally. The node status can include "applied" and "not applied." The "applied" status indicates that the target decision element node is being used normally in the risk decision-making process of the target business. The "not applied" status indicates that the target decision element node is not being used in the risk decision-making process of the target business, which may be because the target decision element node has not been completed, has an error and is under repair, or no longer meets the current target project requirements or scenario requirements.

[0119] Node lineage is used to display other nodes in the management view that are associated with the target decision element node. Based on this node lineage, users can not only view the relationships between all nodes in the decision management view window, but also view other nodes that are only associated with the target decision element node in the details management page.

[0120] Node details are used to display the remaining related content of the target decision element node. For example, when the target decision element node is a link element node, the node details can be used to display the order and logical relationship of each execution step in the execution link corresponding to the link element node, and can be an execution flowchart representing each execution step.

[0121] Reference Figure 7 , Figure 7 This is a schematic diagram illustrating an example of a details management page provided in an embodiment of this application. For example... Figure 7As shown in (a), when a user double-clicks the scene element node - Scene A displayed in window area 203, it indicates that the user wants to view the scene details corresponding to Scene A; in response to this double-click operation, the displayed content in the decision management view window 200 can be moved from... Figure 7 The state shown in (a) is switched to Figure 7 The state shown in (b) is as follows: Figure 7 As shown in (b), the details management page 213 corresponding to scenario A is displayed in the decision management view window 200, and the scenario information and scenario lineage are displayed on the details management page 213.

[0122] The scenario information may include, but is not limited to: the version V5.4 of node A in scenario; the English name of the scenario, which is set by the user or other staff; the scenario description: business A credit access; and the node status: applied. Additionally, the scenario information may include a view comparison control 205. Based on this view comparison control 205, the decision management view window 200 can be controlled to enter view comparison mode. For details, please refer to the previous description; it will not be repeated here.

[0123] Scene lineage can include scene element nodes corresponding to scene A and other link nodes associated with that scene element node, such as link A, link B, and link C associated with scene A.

[0124] The above technical solution can display the detailed management page corresponding to the target decision element node according to the user's operation. While ensuring that the decision management view window is simple and clear, it meets the user's need to understand the detailed information of the target decision element node, helps the user to understand the details of each decision element node more clearly, improves the adaptability and scalability of the decision management view, and improves the efficiency of decision management.

[0125] This concludes the introduction to the management view generation method provided in this application. Based on the above method, the following beneficial effects can be achieved after implementing this method: visualization of the risk control process of the target business, traceability of changes in the risk control process, and improved operational efficiency. Specifically, the viewing time of the management view of the target business under different timestamps is shortened to about 5 seconds, the user's analysis efficiency of the risk control decision execution process of the target business is improved by about 6 times, the strategy defect detection rate of the risk control decision execution process is increased by about 75%, the failure rate of the risk control decision execution process of the target business is reduced to 0.3%, the strategy iteration cycle of the risk control decision of the target business is reduced, and the labor costs are also reduced accordingly.

[0126] Figure 8 This is a schematic diagram of the structure of a management view generation device provided in an embodiment of this application, which is exemplary, such as... Figure 8As shown, the device 300 includes: a determining unit 301 and a generating unit 302; The determining unit 301 is used to determine the first timestamp corresponding to the target configuration change record in response to the first selection operation of the target configuration change record corresponding to the target service, wherein the target configuration change record is one of a plurality of configuration change records. The determining unit 301 is further configured to search for the first snapshot data corresponding to the target service from the historical snapshot database based on the first timestamp. The historical snapshot database includes historical snapshot data corresponding to the target service under different timestamps. Each of the historical snapshot data is generated based on the changed configuration map when the configuration map changes. The configuration map is used to represent the relationship between the nodes of various decision elements in the decision execution process of the target service. The generation unit 302 is used to display the management view corresponding to the first snapshot data in the decision management view window.

[0127] In some possible implementations, the generation unit 302 is also used to display multiple configuration change records in the decision management view window. The configuration change records include change timestamps of changes to the configuration map of the target service. The first selection operation is the operation of determining the target configuration change record among the multiple configuration change records, and the first timestamp is the change timestamp included in the target configuration change record.

[0128] In some possible implementations, the generation unit 302 is also specifically used to determine the target scene element node among multiple scene element nodes of the target business; obtain multiple configuration change records associated with the target scene element node; and display the multiple configuration change records associated with the target scene element node according to the order of the change timestamps included in each configuration change record.

[0129] In some possible implementations, the generation unit 302 is specifically used to display one or more of the scene element nodes, link element nodes, component category element nodes, and component element nodes included in the first snapshot data in the decision management view window.

[0130] In some possible implementations, the generation unit 302 is also specifically used to display scene element nodes; if there are link element nodes associated with scene element nodes in the first snapshot data, the scene element nodes and link element nodes are displayed together; if there are component category element nodes associated with link element nodes in the first snapshot data, the link element nodes and component category element nodes are displayed together; if there are component element nodes corresponding to component category element nodes in the first snapshot data, the component category element nodes and component element nodes under the component category element nodes are displayed together.

[0131] In some possible implementations, the generation unit 302 is further configured to determine a second timestamp when displaying the management view corresponding to the first snapshot data; based on the second timestamp, search for the second snapshot data corresponding to the target business from the historical snapshot database; and compare and display the management view corresponding to the first snapshot data and the management view corresponding to the second snapshot data in the decision management view window.

[0132] In some possible implementations, the generation unit 302 is also configured to display a snapshot selection control in response to a view comparison operation. The snapshot selection control includes multiple snapshot identifiers, each of which is used to indicate historical snapshot data of the target service at different timestamps. In response to a second selection operation for the target snapshot identifier among the multiple snapshot identifiers, the timestamp indicated by the target snapshot identifier is determined as the second timestamp.

[0133] In some possible implementations, the management view corresponding to the first snapshot data includes multiple associated decision element nodes; the generation unit 302 is also used to respond to a detail viewing operation for a target decision element node among the multiple associated decision element nodes, and display the detail management page corresponding to the target decision element node; wherein, the detail management page includes: detail information of the target decision element node, and the target decision element node is one of the following: scenario element node, link element node, component category element node, and component element node of the target business.

[0134] It should be noted that the management view generation device provided in the above embodiments is only an example of the division of the above functional modules. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the computer device can be divided into different functional modules to complete all or part of the functions described above.

[0135] The device embodiments described above are merely illustrative. For example, the division of modules or units is only a logical functional division. In actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another device, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.

[0136] In addition, the apparatus provided in the embodiments of this application may specifically be a chip, component or module. The chip may include a connected processor and a memory. The memory is used to store instructions. When the processor calls and executes the instructions, the chip can execute a management view generation method provided in the above embodiments.

[0137] Furthermore, the management view generation apparatus and management view generation method embodiments provided in the above embodiments belong to the same concept, and their specific implementation process can be found in the method embodiments, which will not be repeated here. It should be understood that the apparatus provided in this embodiment is used to execute the above-described management view generation method, and therefore can achieve the same effect as the above-described implementation method.

[0138] This application also protects an electronic device that may include a memory and a processor, wherein the memory stores executable program code, and the processor is used to call and execute the executable program code to perform a management view generation method provided in this application.

[0139] like Figure 9 As shown, Figure 9 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application.

[0140] For example, such as Figure 9 As shown, the electronic device 400 includes a memory 401 and a processor 402, wherein the memory 401 stores executable program code 403, and the processor 402 is used to call and execute the executable program code 403 to perform a management view generation method.

[0141] Those skilled in the art will understand that Figure 9 This is merely an example of electronic device 400 and does not constitute a limitation on electronic device 400. It may include more or fewer components than shown, or combine certain components, or different components. For example, electronic device 400 may also include input / output devices, network access devices, buses, etc.

[0142] The processor 402 may be a Central Processing Unit (CPU), or it may be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), or field-programmable gate arrays (FPGAs). Programmable Gate Array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor can be a microprocessor or any conventional processor.

[0143] The memory 401 can be an internal storage unit of the electronic device 400, such as a hard disk or RAM of the electronic device 400. The memory 401 can also be an external storage device of the electronic device 400, such as a plug-in hard disk, Smart Media Card (SMC), Secure Digital (SD) card, or Flash Card equipped on the electronic device 400. Furthermore, the memory 401 can include both internal and external storage units of the electronic device 400. The memory 401 is used to store the computer program and other programs and data required by the terminal device. The memory 401 can also be used to temporarily store data that has been output or will be output.

[0144] This embodiment also provides a computer-readable storage medium storing computer program code. When the computer program code is run on a computer, the computer executes the aforementioned method steps to implement the management view generation method provided in the above embodiment.

[0145] The computer-readable storage medium can be volatile memory or non-volatile memory. The non-volatile memory can be read-only memory (ROM). Volatile memory can be ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. It can also be random access memory (RAM) used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), and enhanced synchronous dynamic random access memory.

[0146] This embodiment also provides a computer program product that, when run on a computer, causes the computer to perform the aforementioned steps to implement a management view generation method provided in the above embodiment.

[0147] In this embodiment, the apparatus, electronic device, computer-readable storage medium, computer program product or chip are all used to execute the corresponding methods provided above. Therefore, the beneficial effects that can be achieved can be referred to the beneficial effects of the corresponding methods provided above, and will not be repeated here.

[0148] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method of managing view generation, the method comprising: The method comprises: in response to a first selection operation on a target configuration change record corresponding to a target service, determining a first timestamp corresponding to the target configuration change record, the target configuration change record being one of a plurality of configuration change records; based on the first timestamp, finding first snapshot data corresponding to the target service from a historical snapshot database, the historical snapshot database including historical snapshot data corresponding to the target service at different timestamps respectively, each of the historical snapshot data being generated based on a changed configuration graph under the condition that the configuration graph is changed, the configuration graph being used to represent an association relationship between each decision element node of the target service in a decision execution process; displaying a management view corresponding to the first snapshot data in a decision management view window.

2. The method of claim 1, wherein, The method further comprises: in the decision management view window, displaying the plurality of configuration change records, the configuration change records including a change timestamp at which the configuration graph of the target service is changed, wherein the first selection operation is an operation of determining a target configuration change record from the plurality of configuration change records, and the first timestamp is the change timestamp included in the target configuration change record.

3. The method of claim 2, wherein, The displaying of the plurality of configuration change records comprises: determining a target scene element node from a plurality of scene element nodes of the target service; obtaining a plurality of configuration change records associated with the target scene element node; displaying the plurality of configuration change records associated with the target scene element node according to the sorting of the change timestamps included in each of the configuration change records.

4. The method of claim 1, wherein, The displaying of the management view corresponding to the first snapshot data in the decision management view window comprises: in the decision management view window, associatively displaying one or more of a scene element node, a link element node, a component category element node and a component element node included in the first snapshot data.

5. The method of claim 4, wherein, The associatively displaying of one or more of the scene element node, the link element node, the component category element node and the component element node in the decision management view window comprises: displaying the scene element node; in a case where there is a link element node associated with the scene element node in the first snapshot data, associatively displaying the scene element node and the link element node; in a case where there is a component category element node associated with the link element node in the first snapshot data, associatively displaying the link element node and the component category element node; in a case where there is a component element node corresponding to the component category element node in the first snapshot data, associatively displaying the component category element node and the component element node under the component category element node.

6. The method of claim 1, wherein, The method further comprises: in a case where the management view corresponding to the first snapshot data is displayed, determining a second timestamp; based on the second timestamp, finding second snapshot data corresponding to the target service from the historical snapshot database; In the decision management view window, the management view corresponding to the first snapshot data and the management view corresponding to the second snapshot data are displayed in comparison.

7. The method of claim 6, wherein, Determining the second timestamp includes: In response to a view comparison operation, a snapshot selection control is displayed. The snapshot selection control includes multiple snapshot identifiers, each of which is used to indicate the historical snapshot data of the target service at different timestamps. In response to a second selection operation for a target snapshot identifier among the plurality of snapshot identifiers, the timestamp indicated by the target snapshot identifier is determined as the second timestamp.

8. The method of claim 1, wherein, The management view corresponding to the first snapshot data includes multiple related decision element nodes; the method further includes: In response to a details viewing operation for a target decision element node among the multiple associated display decision element nodes, the details management page corresponding to the target decision element node is displayed; The details management page includes: detailed information of the target decision element node, wherein the target decision element node is one of the following: scenario element node, link element node, component category element node, and component element node of the target business.

9. A management view generating apparatus characterized by comprising: The device includes: a determining unit and a generating unit; The determining unit is configured to, in response to a first selection operation on a target configuration change record corresponding to a target service, determine a first timestamp corresponding to the target configuration change record, wherein the target configuration change record is one of a plurality of configuration change records. The determining unit is further configured to search for the first snapshot data corresponding to the target service from the historical snapshot database based on the first timestamp. The historical snapshot database includes historical snapshot data corresponding to the target service under different timestamps. Each of the historical snapshot data is generated based on the changed configuration map when the configuration map changes. The configuration map is used to represent the relationship between various decision element nodes in the decision execution process of the target service. The generation unit is used to display the management view corresponding to the first snapshot data in the decision management view window.

10. A computer storage medium, characterized in that, The computer storage medium stores a plurality of instructions, which are adapted to be loaded by a processor and executed as method steps as claimed in any one of claims 1 to 8.

11. A computer program product, characterised in that, The computer program product stores a plurality of instructions adapted for loading by a processor and executing the method steps as claimed in any one of claims 1 to 8.

12. An electronic device, comprising: include: A processor and a memory; wherein the memory stores a computer program adapted to be loaded by the processor and executed the method steps as claimed in any one of claims 1 to 8.

Images