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

Abstract

The invention provides a global view generation method and device, a storage medium, a product and electronic equipment, and the method is applied to the technical field of computers, and comprises the steps: determining a scene node and an execution link node associated with the scene node, obtaining a component node associated with the execution link node, and generating a global view according to the component node, and in a decision management view window, performing associated display on the scene node, the execution link node and the component node.

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 a global view in the field of computer technology. Background Art

[0002] With the development of the Internet, more and more transactions and products can be processed on the Internet, providing convenience for staff and users. However, different transactions and products can be in different transaction scenarios, and different transaction scenarios can have different link processes for handling transactions. The programs and details used in different link processes are also different. As the scale of transactions continues to expand and the link processes become increasingly complex, it is difficult to control the overall process of transactions relying solely on human memory. There is a need to provide a method that can comprehensively display the transaction process. Summary of the Invention

[0003] Embodiments of this application provide a method, apparatus, storage medium, and electronic device for generating a global view. This method can associate and display transaction process nodes such as scenarios, instruction links, and components, thereby realizing the visualization of the overall transaction process, facilitating comprehensive analysis of all nodes and risk control.

[0004] In a first aspect, embodiments of this application provide a method for generating a global view, the method including:

[0005] Determine a scenario node and an execution link node associated with the scenario node;

[0006] Obtain a component node associated with the execution link node;

[0007] In a decision management view window, associate and display the scenario node, the execution link node, and the component node.

[0008] Through the above technical solution, it is possible to associate and display transaction process nodes such as scenarios, instruction links, and components, thereby realizing the visualization of the overall transaction process, facilitating comprehensive analysis of all nodes and risk control.

[0009] In combination with the first aspect, in some possible implementation manners, the determining a scenario node and an execution link node associated with the scenario node includes:

[0010] Determine a target product for which the user needs to perform decision management, and obtain a scenario node associated with the target product;

[0011] Obtain the execution link node involved in the scenario node, where the execution link node is used to represent the logical order of each operation step in the scenario node.

[0012] Through the above technical solution, relevant scenarios and execution links can be determined according to the target scenario, facilitating users to view the entire transaction process based on the product and improving the decision-making management efficiency.

[0013] Combined with the first aspect, in some possible implementation manners, the method further includes:

[0014] Receiving an information viewing instruction of the user for the execution link node in the decision-making management view window, and jumping to the link management page corresponding to the execution link node;

[0015] Displaying the link detail information of the execution link node in the link management page.

[0016] Through the above technical solution, the link detail information can be jumped and displayed according to the user instruction. While ensuring that the decision-making management view window is concise and clear, it meets the user's need to understand the execution link details, improves the adaptability and expandability of the decision-making management view, and improves the decision-making management efficiency.

[0017] Combined with the first aspect, in some possible implementation manners, the obtaining of the component nodes associated with the execution link node includes:

[0018] Obtaining the component category nodes associated with the execution link node, where the component category nodes include policy component nodes and / or non-policy component nodes;

[0019] Obtaining the component nodes associated with the execution link node under each component category node.

[0020] Combined with the first aspect, in some possible implementation manners, the associatively displaying the scenario node, the execution link node, and the component node in the decision-making management view window includes:

[0021] In the decision-making management view window, associatively displaying the scenario node and the execution link node;

[0022] Associatively displaying the execution link node and the component category node;

[0023] If there is the policy component node, associatively displaying the component nodes under the policy component node and the policy component node;

[0024] If there is the non-policy component node, associatively displaying the component nodes under the non-policy component node and the non-policy component node.

[0025] Through the above technical solution, it is possible to classify and display component nodes, reducing the complexity of the global view and improving the level of visual management.

[0026] In combination with the first aspect, in some possible implementation manners, the method further includes:

[0027] Obtain policy nodes associated with the component nodes, as well as the version information and online status of each of the policy nodes;

[0028] In the decision management view window, associate and display the policy nodes and the component nodes, and display the version information and online status of each of the policy nodes.

[0029] In combination with the first aspect, in some possible implementation manners, the associating and displaying the policy nodes and the component nodes in the decision management view window, and displaying the version information and online status of each of the policy nodes includes:

[0030] Receive a viewing instruction of a target component node in the decision management window, and determine a target policy node associated with the target component node;

[0031] Associate and display the target policy node and the target component node, and display the version information and online status of the target policy node.

[0032] Through the above technical solution, it is possible to facilitate the user to understand the historical versions and running conditions of the policies according to the association relationship between the display components and the policies, as well as the version information and online status of the policies, further improving the efficiency of decision management and maintaining the stability of the transaction system.

[0033] In a second aspect, an embodiment of the present application provides a global view generation device, where the device includes:

[0034] A scenario link association unit, configured to determine scenario nodes and execution link nodes associated with the scenario nodes;

[0035] A link component association unit, configured to obtain component nodes associated with the execution link nodes;

[0036] An association display unit, configured to associate and display the scenario nodes, the execution link nodes, and the component nodes in a decision management view window.

[0037] In a third aspect, an embodiment of the present application provides a computer storage medium, where the computer storage medium stores multiple instructions, and the instructions are suitable for being loaded and executed by a processor to perform the above method steps.

[0038] Fourthly, an embodiment of the present application provides a computer program product. The computer program product stores multiple instructions, and the instructions are adapted to be loaded and executed by a processor to perform the above method steps.

[0039] Fifthly, an embodiment of the present application provides an electronic device, which may include: a processor and a memory; wherein, the memory stores a computer program, and the computer program is adapted to be loaded and executed by the processor to perform the above method steps.

[0040] In one or more embodiments of the present application, a scenario node and an execution link node associated with the scenario node are determined, a component node associated with the execution link node is obtained, and in a decision management view window, the scenario node, the execution link node, and the component node are associated and displayed. By associating and displaying transaction process nodes such as scenarios, instruction links, components, etc., the visualization of the overall transaction process is realized, which is convenient for comprehensive analysis of all nodes and risk control. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the drawings required for use in the description of the embodiments or the prior art. Obviously, the drawings in the following description are only some embodiments of the present application. For those of ordinary skill in the art, without creative efforts, other drawings can be obtained based on these drawings.

[0042] Figure 1 is an example schematic diagram of a transaction system provided by an embodiment of the present application;

[0043] Figure 2 is a schematic flowchart of a global view generation method provided by an embodiment of the present application;

[0044] Figure 3 is a schematic flowchart of determining the association relationship between a scenario and an execution link provided by an embodiment of the present application;

[0045] Figure 4 is an example schematic diagram of scenario node jump provided by an embodiment of the present application;

[0046] Figure 5 is a schematic flowchart of link details display provided by an embodiment of the present application;

[0047] Figure 6 is an example schematic diagram of a link management page provided by an embodiment of the present application;

[0048] Figure 7 is a schematic flowchart of determining the association relationship between an execution link and a component provided by an embodiment of the present application;

[0049] Figure 8 It is a schematic flowchart of node association display provided by an embodiment of the present application;

[0050] Figure 9 It is an example schematic diagram of component category node display provided by an embodiment of the present application;

[0051] Figure 10 It is an example schematic diagram of node association display provided by an embodiment of the present application;

[0052] Figure 11 It is a schematic structural diagram of a global view generation device provided by an embodiment of the present application;

[0053] Figure 12 It is a schematic structural diagram of a global view generation device provided by an embodiment of the present application;

[0054] Figure 13 It is a schematic structural diagram of an electronic device provided by an embodiment of the present application. Detailed implementation manners

[0055] Next, the technical solutions in the embodiments of the present application will be clearly and completely described in conjunction with the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present application.

[0056] Different products developed by manufacturers and staff can be applied to different transaction scenarios. To solve the problems and situations that may occur in transaction scenarios, staff can write different execution chains according to product characteristics, manufacturer requirements, user requirements, etc. The execution chain can be a series of operation steps, tasks, or instructions arranged in a certain logical order, which can clarify the sequence and mutual relationship of each operation step in the transaction scenario. To complete various steps and tasks in the instruction chain, staff can develop different components. The component can be a software module that undertakes specific tasks and functions on the execution chain and is used to complete various operations. Since in the actual work scenario, determining the corresponding transaction scenario according to the product, writing the execution chain according to the scenario, and developing components according to the execution chain are often assigned to different staff. For example, the work of determining the corresponding transaction scenario according to the product can be responsible by the staff in charge of product marketing, and the work of developing components according to the execution chain can be responsible by the staff in charge of software development. Therefore, the operation of the transaction system often requires the cooperation of staff from multiple departments and multiple systems. So staff can only understand the association relationship under the work content they are responsible for, and cannot achieve a global control of the transaction system. Therefore, when it is necessary to prevent and control risks for the transaction system, it is difficult to judge its impact on the entire transaction system through changes at a certain node. And the embodiment of this application provides a global view generation device, which can integrate the association relationship among scenarios, execution chains, and components under the transaction system to generate a decision management view and display it on the decision management view window. The decision management view can include all scenarios, instruction chains, and components under the transaction system, so as to realize the visualization of the overall transaction process, facilitate staff to comprehensively analyze all nodes and control risks. The global view generation method provided by the embodiment of this application can be implemented depending on a computer program and can run on a global view generation device based on the von Neumann architecture. This computer program can be integrated in an application or run as an independent tool application.

[0057] Please refer to Figure 1, This is an example schematic diagram of a transaction system provided by an embodiment of the present application. The target product can be a product developed by a manufacturer or a staff member in the transaction system, which can be an electronic product, an application program, a network platform, a financial product, etc. The staff member can pre-define different transaction scenarios according to the target product characteristics, user requirements, historical experience, etc., such as Scenario A, Scenario B, and Scenario C. Different execution links may exist in different transaction scenarios, and the execution links can be reused, that is, one execution link can also be applied to different transaction scenarios. Therefore, both Scenario A and Scenario B can be associated with Execution Link A, and Scenario C can be associated with Execution Link B. Since the component can be a software module, the component can also be reused. There can be multiple components in one execution link, and the same component can also be applied to different execution links. Therefore, Execution Link A can be associated with Component A and Component B, and Execution Link B can be associated with Component C. The global view generation device in the embodiment of the present application can display the association relationships between the scenario and the execution link, and between the execution link and the component in the decision management view window, so as to realize the visualization of the overall transaction process.

[0058] The following will specifically describe the global view generation method provided by the present application with reference to specific embodiments.

[0059] Please refer to Figure 2 , This is a schematic flowchart of a global view generation method provided by an embodiment of the present application. As Figure 2 shown, the method of the embodiment of the present application may include the following steps S102-S106.

[0060] S102, Determine the scenario node and the execution link node associated with the scenario node.

[0061] Specifically, the global view generation device can determine the scenario node according to the pre-set transaction scenarios. The scenario node is the node representing the transaction scenario in the decision management view. Each scenario node can have a corresponding scenario name, which can be pre-set by the staff member to concisely describe the transaction scenario. After determining the scenario node, the global view generation device can determine the execution link node associated with the scenario node. The execution link node is the node representing the execution link in the decision management view. Each execution link node can have a corresponding link name, which can be pre-set by the staff member or automatically generated by the global view generation device. If the execution link is associated with the transaction scenario, the scenario node corresponding to the transaction scenario is associated with the execution link node corresponding to the execution link. For example, Execution Link A can be applied to Scenario A, that is, Scenario A is associated with Execution Link A, then the scenario node corresponding to Scenario A is also associated with the execution link node corresponding to Execution Link A.

[0062] S104. Obtain component nodes associated with the execution link nodes.

[0063] Specifically, the global view generation device can obtain component nodes associated with the execution link nodes. A component node is a node representing a component in the decision management view. Each component node can have a corresponding component name, which can be preset by the staff or automatically generated by the global view generation device. If a component is associated with an execution link, the corresponding component node of the component is also associated with the execution link node corresponding to the execution link. For example, there may be component A and component B in execution link A, that is, execution link A is associated with component A and component B. Then, the execution link node corresponding to execution link A is associated with the component node corresponding to component A and the component node corresponding to component B.

[0064] S106. In the decision management view window, associate and display the scenario nodes, execution link nodes, and component nodes.

[0065] Specifically, when a user or staff member needs to view and manage the transaction process in the transaction system, they can open the decision management view window. The global view generation device can display the decision management view in the decision management view window, that is, in the decision management view window, associate and display the scenario nodes, execution link nodes, and component nodes. For example, the global view generation device can use the connection lines between the nodes to indicate the association relationship between the nodes. The execution link nodes associated with the scenario nodes can be used as the child nodes of the scenario nodes. Similarly, the component nodes associated with the execution link nodes can be used as the child nodes of the execution link nodes.

[0066] In the embodiment of the present application, determine the scenario nodes and the execution link nodes associated with the scenario nodes, obtain the component nodes associated with the execution link nodes, and in the decision management view window, associate and display the scenario nodes, the execution link nodes, and the component nodes. By associating and displaying the transaction process nodes such as scenarios, instruction links, and components, the visualization of the overall transaction process is realized, which is convenient for comprehensive analysis of all nodes and risk control.

[0067] Please refer to Figure 3 , which provides a schematic flowchart of the process for determining the association relationship between scenarios and execution links in the embodiment of the present application. Step S102 may include the following steps:

[0068] S202. Determine the target product for which the user needs to perform decision management, and obtain the scenario nodes associated with the target product.

[0069] Specifically, the users faced by the global view generation device can be relevant staff under the transaction system or customers faced by the transaction system, etc. The user or staff can input the target product that requires decision-making management by the transaction system into the global view generation device, and the global view generation device can obtain the scenario nodes associated with the target product.

[0070] Optionally, the global view generation device can also determine a product node according to the target product. The product node is the node representing the target product in the decision-making management view. The product name of the target product can be included in the product node. The global view generation device can also associate and display the product node and the scenario node in the decision-making management view window, facilitating the user to quickly find the corresponding target product in the decision-making management view, so as to view the nodes and processes related to the target product.

[0071] Optionally, the transaction scenario associated with the target product can be set by the user or relevant staff. The global view generation device can generate scenario nodes according to the transaction scenario set by the user or relevant staff.

[0072] S204, obtain the execution link nodes involved in the scenario nodes.

[0073] Specifically, if a component is associated with an execution link, the component node corresponding to the component is also associated with the execution link node corresponding to the execution link. The global view generation device can obtain the execution links included in the scenario corresponding to the scenario node and generate execution link nodes according to these execution links.

[0074] Optionally, the execution link associated with the transaction scenario corresponding to the scenario node can be set by the user or relevant staff. The global view generation device can generate execution link nodes according to the execution link set by the user or relevant staff. Among them, the execution link node is used to represent the logical order of each operation step in the scenario node.

[0075] Optionally, the global view generation device may display product nodes in the decision management view window. The product nodes are the nodes used to represent products in the decision management view window. It can be understood that there are many scenario nodes in the decision management view. It is very difficult for users or staff to directly find the required scenario nodes, execution link nodes, etc. in the decision management view. Since the global view generation device determines the scenario nodes based on the product, the user can jump to the associated scenario nodes in the decision management view by clicking on the product nodes in the decision management view window. When the global view generation device receives a jump instruction for a target product node from the user, it can determine the target scenario node associated with the target product node and jump to the target scenario node for display. Herein, the target product node is the product node selected by the user, and the jump instruction may be a click instruction for the product node, etc.

[0076] Please also refer to Figure 4 , which provides an example schematic diagram of scenario node jump for an embodiment of the present application. When a user wants to view the transaction process of product B in the transaction system, the user can find the product node corresponding to product B in the decision management view window and click it, so as to send a jump instruction for the product node corresponding to product B to the global view generation device. After receiving the jump instruction, the global view generation device can find the associated scenario A of product B and determine the position of the scenario node corresponding to scenario A in the decision management view, so that the decision management view jumps to the scenario node corresponding to scenario A for display.

[0077] In the embodiment of the present application, the target product for which the user needs to perform decision management is determined, the scenario nodes associated with the target product are obtained, and the execution link nodes involved in the scenario nodes are obtained. Determining the relevant scenarios and execution links through the target scenario facilitates the user to view the entire transaction process according to the product and improves the decision management efficiency.

[0078] The components associated with each execution link can be displayed in the decision management view window. It can be understood that the execution link can represent the process and logic of each operation step. However, in order to make the decision management view more concise and clear, the order and association between the components are not directly shown in the decision management view window. In order to further meet the needs of users and staff to view the process, logic, and in-depth understanding of the decision management process in the transaction system of each operation step, the detailed content in the execution link can be displayed to the user according to the user's needs.

[0079] Please refer to Figure 5 , which provides a schematic flow diagram of link details display for an embodiment of the present application. The global view generation method may further include the following steps:

[0080] S302. Receive the user's information viewing instruction for the execution link node in the decision management view window, and jump to the link management page corresponding to the execution link node.

[0081] Specifically, when the user wants to view the detailed content in the execution link, the user can send an information viewing instruction for the execution link node to the global view generation device. For example, the information viewing instruction can be a click instruction for the execution link node in the decision management view window. After receiving the user's information viewing instruction for the execution link node in the decision management view window, the global view generation device can open the link management page corresponding to the execution link node and jump to the link management page for display. Among them, each execution link node can have a corresponding link management page. The link management page can be a sub-page in the decision management view window or can be opened in another window to display the link management page. Separating the decision management view reflecting the whole and the link management page and realizing the jump through the user instruction achieve modular design. Modular design not only improves the maintainability of the system but also facilitates the subsequent expansion and update of the link detail information without large-scale modification of the global decision management view, thus enhancing the adaptability and scalability of the decision management view.

[0082] S304. Display the link detail information of the execution link node in the link management page.

[0083] Specifically, the global view generation device can display the link detail information of the execution link node in the link management page. The link detail information is the information describing the detailed content in the execution link, which can include the order and logical relationship of the components corresponding to each execution step in the execution link, and can include link information, link lineage, and link details. Among them, the link information is the descriptive information for the execution link. For example, it can include the execution link name, execution link introduction, link status, etc. The execution link introduction can be preset by the user or relevant staff and is used to briefly summarize the function and role of the execution link. The link status is used to indicate whether the execution link is enabled and can include the enabled status and the disabled status. The enabled status indicates that the execution link is being used normally in the transaction system, and the disabled status indicates that the execution link is not being used in the transaction system, which may be due to reasons such as the execution link not being written yet, being under repair due to an error, or no longer meeting the current product requirements and transaction scenarios.

[0084] The link lineage is other nodes associated with the execution link node in the decision management view. The user can not only view the association relationship between all nodes in the decision management view window but also view the association relationship between the execution link node and other nodes in the link management page of the execution link node. The link details are used to represent the order and logical relationship of each execution step in the execution link and can be an execution flow chart representing each execution step.

[0085] Please also refer to Figure 6 , which provides an example schematic diagram of a link management page for the embodiments of the present application. For example, the transaction system can be the transaction system corresponding to financial products. The user can send an information viewing instruction for the execution link of "Pledge Scenario Quota - Scheduling Approval". The global view generation device can jump to the link management page as shown in Figure 6 for display, and display link information, link lineage, and link details in the link management page. The execution link name can include a Chinese name and an English name of the link. For example, the English name of the link can be pledge-fix-amt-adjust, which can be set by the user or relevant staff. The execution link brief introduction can be "Pledge Scenario Quota - Scheduling Approval". Since the execution link brief introduction is used to briefly summarize the functions and roles of the execution link, the execution link brief introduction can be the same as the Chinese name of the link. The Chinese name of the link can also be displayed on the execution link node, and the link status can be the enabled state. The link lineage can include other nodes associated with the execution link node. For example, it can include the scenario node "Pledge Scenario", as well as associated components A and B, etc. The link details can be an execution flow chart of the execution steps. After the execution link starts, it is necessary to first "query user information", and then judge the type of quota adjustment. If it is necessary to increase the quota, the steps of "Consumer Finance Feature Query" and obtaining the "quota increase limit" are executed. If it is necessary to decrease the quota, the steps of "Credit Product Agreement Query" and obtaining the "quota decrease limit" are executed, and then the execution link ends.

[0086] In the embodiments of the present application, upon receiving the user's information viewing instruction for the execution link node in the decision management view window, it jumps to the link management page corresponding to the execution link node, and displays the link detail information of the execution link node in the link management page. By jumping and displaying the link detail information through the user instruction, while ensuring that the decision management view window is concise and clear, it meets the user's need to understand the execution link details, improves the adaptability and expandability of the decision management view, and improves the decision management efficiency.

[0087] Please refer to Figure 7 , which provides a schematic flow diagram for determining the association relationship between an execution link and components for the embodiments of the present application. Step S104 can include the following steps:

[0088] S402, obtain the component category nodes associated with the execution link node, where the component category nodes include policy component nodes and / or non-policy component nodes.

[0089] Specifically, an execution link may be associated with multiple components, that is, an execution link node may be related to multiple component nodes. To make the decision management view more concise and clear and avoid messy association relationships, the global view generation device may classify the component nodes. Therefore, the global view generation device may determine the component categories of the components associated with the execution link, and then determine the component category nodes associated with the execution link nodes corresponding to the execution link according to the component categories. For example, the component category nodes may include policy component nodes and / or non-policy component nodes, where the policy component nodes are the nodes representing the policy component category on the decision management view, and the non-policy component nodes are the nodes representing the non-policy component category on the decision management view.

[0090] The components in the policy component category may be components containing decision logic, rules, or conditions, which are used to dynamically adjust the transaction process according to preset rules or conditions. They are usually used to handle complex transaction logics, such as conditional judgment, rule engines, decision trees, etc. They can make decisions based on input data or context information and guide the execution of subsequent steps. The components in the non-policy component category may be components that do not contain decision logic but focus on executing specific tasks or functions. They can be used to complete clear operations, such as data processing, file operations, system calls, etc., without involving complex rule or conditional judgments.

[0091] S404, obtain the component nodes associated with the execution link nodes under each component category node.

[0092] Specifically, after determining the component category nodes associated with the execution link nodes, the global view generation device may obtain the component nodes associated with the execution link nodes under each component category node. Through clear classification and association relationships, the complexity of the system is reduced.

[0093] In the embodiments of the present application, the component category nodes associated with the execution link nodes are obtained, where the component category nodes include policy component nodes and / or non-policy component nodes, and the component nodes associated with the execution link nodes under each component category node are obtained. By classifying the component nodes, the complexity of the global view is reduced and the visualization management level is improved.

[0094] Since the component nodes can be classified according to the component categories and the component category nodes of the execution link can be determined, the component category nodes can be displayed in the decision management view window.

[0095] Please refer to Figure 8 , which provides a schematic flow diagram of node association display for the embodiments of the present application. Step S106 may include the following steps:

[0096] S502. In the decision management view window, the scenario node and the execution link node are associated and displayed.

[0097] Specifically, when a user or staff member needs to view and manage the transaction process in the transaction system, the decision management view window can be opened. The global view generation device can display the decision management view in the decision management view window, and in the decision management view window, the scenario node and the execution link node can be associated and displayed. For example, the global view generation device can use the connection line between the nodes to indicate the existence of an association relationship between the nodes, and the execution link node associated with the scenario node can be used as the child node of the scenario node.

[0098] S504. The execution link node and the component category node are associated and displayed.

[0099] Specifically, then the execution link node and the component category node are associated and displayed. For example, the component category node can be used as the child node of the execution link node.

[0100] S506. If there is a policy component node, the component node under the policy component node is associated and displayed with the policy component node.

[0101] Specifically, if there is a component of the policy component category under the execution link, the execution link node is associated with the policy component node. The global view generation device can associate and display the component node under the policy component node with the policy component node, that is, the component node under the policy component node can be the child node of the policy component node.

[0102] S508. If there is a non-policy component node, the component node under the non-policy component node is associated and displayed with the non-policy component node.

[0103] Specifically, if there is a component of the non-policy component category under the execution link, the execution link node is associated with the non-policy component node. The global view generation device can associate and display the component node under the non-policy component node with the non-policy component node, that is, the component node under the non-policy component node can be the child node of the non-policy component node.

[0104] Please also refer to Figure 9, This application example provides a schematic diagram for demonstrating component category nodes. The scenario node corresponding to Scenario A and the execution link node corresponding to Execution Link A can be associated and displayed. If there are policy component categories and non-policy component categories under Execution Link A, then the policy component nodes and non-policy component nodes can be associated and displayed with the execution link node corresponding to Execution Link A. If Component A is a component associated with Execution Link A and belongs to a policy component category, and Component B and Component C are both components associated with Execution Link A and belong to non-policy component categories, then the component node corresponding to Component A can be associated and displayed with the policy component node, and Component B and Component C can be associated and displayed with the non-policy component node.

[0105] In the embodiment of this application, in the decision management view window, the scenario node and the execution link node are associated and displayed, and the execution link node and the component category node are associated and displayed. If there are policy component nodes, then the component nodes under the policy component node are associated and displayed with the policy component node. If there are non-policy component nodes, then the component nodes under the non-policy component node are associated and displayed with the non-policy component node. By classifying and displaying the component nodes, the complexity of the global view is reduced and the visualization management level is improved.

[0106] Component nodes, especially component nodes under the policy component category, may have policies associated with them. A policy can be a set of predefined rules, logics, or decision algorithms, which can be used to indicate how a component executes steps and implements functions in different situations. A policy can be a simple conditional judgment or a complex rule engine or machine learning model, and is written and set by users or relevant staff. To further enrich the decision management view and improve the risk control level, the global view generation device can display the policies associated with the components in the decision management view window.

[0107] Please refer to Figure 10 , This application example provides a schematic diagram of the process for node association display. The global view generation method may further include the following steps:

[0108] S602, Obtain the policy nodes associated with the component nodes, as well as the version information and online status of each policy node.

[0109] Specifically, the global view generation device can obtain the policies used in the component, that is, the policies associated with the component. Then, the component node corresponding to the component is associated with the policy node corresponding to the policy. The policy node is the node used to represent the policy in the decision management view. The policy node may contain a policy name, which can be pre-set by the staff or automatically generated by the global view generation device.

[0110] The policy can be written and set by the user or relevant staff. Due to reasons such as product updates and iterations, and changes in transaction scenarios, the user or relevant staff can update and iterate the policy, resulting in different versions of the policy. Therefore, the global view generation device can also obtain the version information and online status of each policy node. The version information can represent the historical records of policy development, update, and deployment, facilitating the management and troubleshooting of policy nodes. For example, the version information can be the version number of the policy. The online status is used to indicate whether the policy is running normally. For example, it can include two states: online and offline. Online means the policy is still in use in the transaction system, and offline means the transaction system is not using the policy.

[0111] S604. In the decision management view window, associate and display the policy nodes and component nodes, and display the version information and online status of each policy node.

[0112] Specifically, the global view generation device can associate and display the policy nodes and component nodes in the decision management view window. For example, the policy node can be a child node of the component node, and it can also display the version information and online status of each policy node. Displaying the association relationship between the policy node and the component node makes the system architecture and configuration clearer, facilitating users or relevant management personnel to quickly understand the operation logic of the system. Displaying the version information of the policy node can help users quickly identify which policies are the latest versions and which need to be updated, thus better maintaining the stability of the system. The display of the online status can help to understand the running situation of the policy node in real time and promptly discover abnormal offline nodes to ensure the normal operation of the system.

[0113] Optionally, for the simplicity of the decision management view, the policy nodes under the component node may not be displayed in the decision management window first. If the user wants to view the policy nodes under the target component node, a viewing instruction for the target component node can be sent to the global view generation device. Among them, the target component node can be any component node, and the viewing instruction can be a click instruction for the target component node. When receiving the viewing instruction from the user for the target component node in the decision management window, the target policy node associated with the target component node can be determined, and then the target policy node and the target component are associated and displayed in the decision management view window, and the version information and online status of the target policy node are displayed.

[0114] Optionally, the global view generation device can obtain the version information and online status of the latest version of each policy node, and display the version information and online status of the latest version of each policy node in the decision management view window.

[0115] Optionally, a policy may include at least one sub-policy, and the sub-policies are different versions under the same policy, so the version information of the sub-policies is different. If the user wants to further understand the development, update, and deployment history of the policy, that is, view the sub-policies under the policy, a sub-policy viewing instruction for the policy node can be sent to the global view generation device. Among them, the sub-policy viewing instruction can be a click instruction for the target component node. When receiving the user's sub-policy viewing instruction for the policy node in the decision management window, the sub-policy nodes associated with the policy node can be determined, and the version information and online status of each sub-policy node can be obtained. The sub-policy node is the node representing the sub-policy in the decision management view. Then, the policy node and the sub-policy nodes are associated and displayed in the decision management view window, and the version information and online status of each sub-policy node are displayed. By showing the version information and online status of each policy sub-node, it is convenient to record and audit the change history of the policy, and it is convenient for users or relevant staff to trace back and analyze when problems occur in the policy node.

[0116] Through the embodiments of the present application, the policy nodes associated with the component nodes, as well as the version information and online status of each policy node, are obtained. In the decision management view window, the policy nodes and the component nodes are associated and displayed, and the version information and online status of each policy node are displayed. By showing the association relationship between the components and the policies, as well as the version information and online status of the policies, it is convenient for users to understand the historical versions and running conditions of the policies, further improving the efficiency of decision management and maintaining the stability of the transaction system.

[0117] The following will combine with the attached Figure 11 - attached Figure 12 to introduce the global view generation device provided by the embodiments of the present application in detail. It should be noted that the global view generation device in the attached Figure 11 - attached Figure 12 is used to execute the method of the embodiments of the present application Figures 1 - 10 shown. For the convenience of description, only the parts related to the embodiments of the present application are shown. For the specific technical details not disclosed, please refer to the embodiments shown in the present application Figures 1 - 10 shown.

[0118] Please refer to Figure 11 , which shows a schematic structural diagram of a global view generation device provided by an exemplary embodiment of the present application. The global view generation device can be implemented as all or part of the device through software, hardware, or a combination of both. The device 1 includes a scenario link association unit 11, a link component association unit 12, and an association display unit 13.

[0119] The scenario link association unit 11 is used to determine the scenario node and the execution link node associated with the scenario node;

[0120] A link component association unit 12, configured to obtain component nodes associated with the execution link node;

[0121] An association display unit 13, configured to perform associated display of the scenario node, the execution link node, and the component node in a decision management view window.

[0122] In this embodiment, a scenario node and an execution link node associated with the scenario node are determined, component nodes associated with the execution link node are obtained, and the scenario node, the execution link node, and the component node are associated and displayed in a decision management view window. By associating and displaying transaction process nodes such as scenarios, instruction links, and components, visualization of the overall transaction process is achieved, facilitating comprehensive analysis of all nodes and risk control.

[0123] Please refer to Figure 12 , which shows a schematic structural diagram of a global view generation device provided by an exemplary embodiment of the present application. The global view generation device can be implemented as all or part of a device through software, hardware, or a combination of both. The device 1 includes a scenario link association unit 11, a link detail display unit 14, a link component association unit 12, an association display unit 13, and a component policy association unit 15.

[0124] A scenario link association unit 11, configured to determine a scenario node and an execution link node associated with the scenario node;

[0125] Optionally, the scenario link association unit 11 is specifically configured to determine a target product for which a user needs to perform decision management, and obtain a scenario node associated with the target product;

[0126] Obtain an execution link node involved in the scenario node, where the execution link node is used to represent the logical order of each operation step in the scenario node.

[0127] A link detail display unit 14, configured to receive an information viewing instruction of the user for the execution link node in the decision management view window, and jump to a link management page corresponding to the execution link node;

[0128] Display link detail information of the execution link node on the link management page.

[0129] A link component association unit 12, configured to obtain component nodes associated with the execution link node;

[0130] Optionally, the link component association unit 12 is specifically configured to obtain component category nodes associated with the execution link node, where the component category nodes include policy component nodes and / or non-policy component nodes;

[0131] Obtain component nodes associated with the execution link node under each component category node.

[0132] Optionally, the link component association unit 12 is specifically configured to associate and display the scenario node and the execution link node in the decision management view window;

[0133] Associate and display the execution link node and the component category node;

[0134] If there is the policy component node, associate and display the component nodes under the policy component node with the policy component node;

[0135] If there is the non-policy component node, associate and display the component nodes under the non-policy component node with the non-policy component node.

[0136] The association display unit 13 is configured to associate and display the scenario node, the execution link node, and the component node in the decision management view window.

[0137] The component policy association unit 15 is configured to obtain policy nodes associated with the component node, as well as the version information and online status of each of the policy nodes;

[0138] In the decision management view window, associate and display the policy node and the component node, and display the version information and online status of each of the policy nodes.

[0139] Optionally, the component policy association unit 15 is specifically configured to receive a viewing instruction from a user for a target component node in the decision management window, and determine a target policy node associated with the target component node;

[0140] Associate and display the target policy node and the target component node, and display the version information and online status of the target policy node.

[0141] In this embodiment, the target product for which the user needs to perform decision management is determined, the scenario nodes associated with the target product are obtained, the execution link nodes involved in the scenario nodes are obtained, and the relevant scenarios and execution links are determined through the target scenario, facilitating the user to view the entire transaction process according to the product and improving the decision management efficiency. The information viewing instruction for the execution link node in the decision management view window is received, and the page jumps to the link management page corresponding to the execution link node. The link detail information of the execution link node is displayed on the link management page. By jumping and displaying the link detail information through the user instruction, while ensuring that the decision management view window is concise and clear, the user's need to understand the execution link details is met, and the adaptability and expandability of the decision management view are improved, as well as the decision management efficiency. The component category nodes associated with the execution link node are obtained, where the component category nodes include policy component nodes and / or non-policy component nodes. The component nodes associated with the execution link node under each component category node are obtained. In the decision management view window, the scenario nodes and the execution link nodes are associated and displayed, and the execution link nodes and the component category nodes are associated and displayed. If there are policy component nodes, the component nodes under the policy component nodes are associated and displayed with the policy component nodes. If there are non-policy component nodes, the component nodes under the non-policy component nodes are associated and displayed with the non-policy component nodes. By classifying and displaying the component nodes, the complexity of the global view is reduced and the visualization management level is improved. The policy nodes associated with the component nodes, as well as the version information and online status of each policy node, are obtained. In the decision management view window, the policy nodes and the component nodes are associated and displayed, and the version information and online status of each policy node are displayed. By displaying the association relationship between the components and the policies, as well as the version information and online status of the policies, it is convenient for the user to understand the historical versions and running conditions of the policies, further improving the decision management efficiency and maintaining the stability of the transaction system.

[0142] It should be noted that when the global view generation device provided in the above embodiment executes the global view generation method, only the above division of each functional module is used for illustration. In practical applications, the above functions can be allocated to different functional modules according to needs, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above. In addition, the global view generation device provided in the above embodiment and the global view generation method embodiment belong to the same concept, and the implementation process is detailed in the method embodiment and will not be repeated here.

[0143] The serial numbers of the embodiments of the present application above are only for description and do not represent the advantages or disadvantages of the embodiments.

[0144] The embodiments of the present application also provide a computer storage medium, which can store multiple instructions. The instructions are suitable for being loaded and executed by a processor to perform the global view generation method of the embodiment as described above Figures 1 - 10 The specific execution process can be referred to the detailed description of the embodiment shown in Figures 1 - 10 and will not be elaborated here.

[0145] The present application also provides a computer program product, which stores at least one instruction. The at least one instruction is loaded and executed by the processor to perform the global view generation method of the embodiment as described above Figures 1 - 10 The specific execution process can be referred to the detailed description of the embodiment shown in Figures 1 - 10 and will not be elaborated here.

[0146] Please refer to Figure 13 , which shows a block diagram of the structure of an electronic device provided by an exemplary embodiment of the present application. The electronic device in the present application may include one or more of the following components: a processor 110, a memory 120, an input device 130, an output device 140, and a bus 150. The processor 110, the memory 120, the input device 130, and the output device 140 may be connected through the bus 150.

[0147] The processor 110 may include one or more processing cores. The processor 110 uses various interfaces and lines to connect various parts within the entire electronic device. By running or executing instructions, programs, code sets, or instruction sets stored in the memory 120, and by calling data stored in the memory 120, it executes various functions of the terminal 100 and processes data. Optionally, the processor 110 may be implemented in at least one hardware form of digital signal processing (DSP), field-programmable gate array (FPGA), or programmable logic array (PLA). The processor 110 may integrate a combination of one or more of a central processing unit (CPU), a graphics processing unit (GPU), and a modem. Among them, the CPU mainly processes the operating system, user interfaces, and application programs, etc.; the GPU is responsible for rendering and drawing display content; the modem is used to process wireless communications. It can be understood that the above modem may not be integrated into the processor 110 and may be implemented separately through a communication chip.

[0148] The memory 120 may include a Random Access Memory (RAM), and may also include a Read-Only Memory (ROM). Optionally, the memory 120 includes a Non-Transitory Computer-Readable Storage Medium. The memory 120 can be used to store instructions, programs, codes, code sets or instruction sets. The memory 120 may include a program storage area and a data storage area. Among them, the program storage area can store instructions for implementing an operating system, instructions for implementing at least one function (such as a touch function, a sound playback function, an image playback function, etc.), instructions for implementing the above various method embodiments, etc. The operating system can be an Android system, including a system developed based on the Android system in depth, an IOS system developed by Apple Inc., including a system developed based on the IOS system in depth, or other systems.

[0149] The memory 120 can be divided into an operating system space and a user space. The operating system runs in the operating system space, and native and third-party application programs run in the user space. In order to ensure that different third-party application programs can achieve better running effects, the operating system allocates corresponding system resources for different third-party application programs. However, there are also differences in the system resource requirements of different application scenarios in the same third-party application program. For example, in the local resource loading scenario, the third-party application program has a higher requirement for the disk reading speed; in the animation rendering scenario, the third-party application program has a higher requirement for the GPU performance. The operating system and the third-party application program are independent of each other, and the operating system often cannot timely perceive the current application scenario of the third-party application program, resulting in the operating system being unable to perform targeted system resource adaptation according to the specific application scenario of the third-party application program.

[0150] In order to enable the operating system to distinguish the specific application scenarios of third-party application programs, it is necessary to establish data communication between the third-party application programs and the operating system, so that the operating system can obtain the current scenario information of the third-party application programs at any time, and then perform targeted system resource adaptation based on the current scenario.

[0151] Among them, the input device 130 is used to receive input instructions or data. The input device 130 includes, but is not limited to, a keyboard, a mouse, a camera, a microphone or a touch device. The output device 140 is used to output instructions or data. The output device 140 includes, but is not limited to, a display device and a speaker, etc. In one example, the input device 130 and the output device 140 can be integrated, and the input device 130 and the output device 140 are a touch display screen.

[0152] The touch display screen can be designed as a full-screen, curved screen or irregular-shaped screen. The touch display screen can also be designed as a combination of a full-screen and a curved screen, or a combination of an irregular-shaped screen and a curved screen. The embodiments of the present application do not limit this.

[0153] In addition, those skilled in the art can understand that the structure of the electronic device shown in the above drawings does not limit the electronic device. The electronic device may include more or fewer components than shown in the drawings, or combine some components, or have different component arrangements. For example, the electronic device further includes components such as a radio frequency circuit, an input unit, a sensor, an audio circuit, a Wireless Fidelity (WiFi) module, a power supply, a Bluetooth module, etc., which will not be elaborated here.

[0154] In Figure 13 the electronic device shown, the processor 110 can be used to call the global view generation application program stored in the memory 120 and specifically perform the following operations:

[0155] Determine the scenario node and the execution link node associated with the scenario node;

[0156] Obtain the component node associated with the execution link node;

[0157] In the decision management view window, associate and display the scenario node, the execution link node and the component node.

[0158] In one embodiment, when the processor 110 executes the operation of determining the scenario node and the execution link node associated with the scenario node, it specifically performs the following operations:

[0159] Determine the target product that the user needs to perform decision management on, and obtain the scenario node associated with the target product;

[0160] Obtain the execution link node involved in the scenario node, and the execution link node is used to represent the logical order of each operation step in the scenario node.

[0161] In one embodiment, when the processor 110 executes the global view generation method, it further performs the following operations:

[0162] Receive the information viewing instruction of the user for the execution link node in the decision management view window, and jump to the link management page corresponding to the execution link node;

[0163] Display the link detail information of the execution link node on the link management page.

[0164] In one embodiment, when the processor 110 executes obtaining the component nodes associated with the execution link node, the following operations are specifically performed:

[0165] Obtain the component category nodes associated with the execution link node, where the component category nodes include policy component nodes and / or non-policy component nodes;

[0166] Obtain the component nodes associated with the execution link node under each component category node.

[0167] In one embodiment, when the processor 110 executes associatively displaying the scenario node, the execution link node, and the component node in the decision management view window, the following operations are specifically performed:

[0168] In the decision management view window, associatively display the scenario node and the execution link node;

[0169] Associatively display the execution link node and the component category node;

[0170] If there is the policy component node, associatively display the component nodes under the policy component node with the policy component node;

[0171] If there is the non-policy component node, associatively display the component nodes under the non-policy component node with the non-policy component node.

[0172] In one embodiment, when the processor 110 executes the global view generation method, the following operations are further performed:

[0173] Obtain the policy nodes associated with the component node, as well as the version information and online status of each of the policy nodes;

[0174] In the decision management view window, associatively display the policy node and the component node, and display the version information and online status of each of the policy nodes.

[0175] In one embodiment, when the processor 110 executes associatively displaying the policy node and the component node in the decision management view window, and displaying the version information and online status of each of the policy nodes, the following operations are specifically performed:

[0176] Receive a viewing instruction of a user for a target component node in the decision management window, and determine the target policy node associated with the target component node;

[0177] Associate and display the target policy node and the target component node, and display the version information and online status of the target policy node.

[0178] In this embodiment, determine the target product that the user needs to perform decision management on, obtain the scenario nodes associated with the target product, obtain the execution link nodes involved in the scenario nodes, and determine the relevant scenarios and execution links through the target scenario, which is convenient for the user to view the entire transaction process according to the product and improves the decision management efficiency. Receive the information viewing instruction of the execution link node in the decision management view window, jump to the link management page corresponding to the execution link node, and display the link detail information of the execution link node on the link management page. Jump and display the link detail information through the user instruction. While ensuring that the decision management view window is simple and clear, it meets the user's need to understand the execution link details, improves the adaptability and expandability of the decision management view, and improves the decision management efficiency. Obtain the component category nodes associated with the execution link nodes, where the component category nodes include policy component nodes and / or non-policy component nodes. Obtain the component nodes associated with the execution link nodes under each component category node. In the decision management view window, associate and display the scenario nodes and the execution link nodes, and associate and display the execution link nodes and the component category nodes. If there are policy component nodes, associate and display the component nodes under the policy component nodes with the policy component nodes. If there are non-policy component nodes, associate and display the component nodes under the non-policy component nodes with the non-policy component nodes. By classifying and displaying the component nodes, the complexity of the global view is reduced and the visualization management level is improved. Obtain the policy nodes associated with the component nodes, as well as the version information and online status of each policy node. In the decision management view window, associate and display the policy nodes and the component nodes, and display the version information and online status of each policy node. By displaying the association relationship between the components and the policies, as well as the version information and online status of the policies, it is convenient for the user to understand the historical versions and running conditions of the policies, further improves the decision management efficiency, and maintains the stability of the transaction system.

[0179] Those of ordinary skill in the art can understand that all or part of the processes of implementing the methods in the above embodiments can be completed by instructing relevant hardware through a computer program. The program can be stored in a computer-readable storage medium. When the program is executed, it can include the processes of the above method embodiments. Among them, the storage medium can be a magnetic disk, an optical disk, a read-only memory, or a random access memory, etc.

[0180] The above-disclosed are only the preferred embodiments of the present application. Of course, the scope of the rights of the present application cannot be limited thereby. Therefore, equivalent changes made according to the claims of the present application still fall within the scope covered by the present application.

[0181] It should be noted that the information (including but not limited to user device information, user personal information, etc.), data (including but not limited to data for analysis, stored data, displayed data, etc.) and signals involved in the embodiments of this specification are all authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data need to comply with the relevant laws, regulations and standards of relevant countries and regions. For example, the scenarios, execution links and policies involved in this specification are all obtained under full authorization.

Claims

1. A global view generation method, characterized in that: The method comprises: Determine a scene node and an execution link node associated with the scene node; Obtaining a component node associated with the execution link node; In the decision management view window, the scene node, the execution link node and the component node are displayed in association.

2. The method according to claim 1, characterized in that The determining of the scene node, and the execution link node associated with the scene node, comprises: Determine the target product that the user needs to perform decision management on, and obtain the scene node associated with the target product; An execution link node involved in the scene node is acquired, where the execution link node is used to represent the logical sequence of each operation step in the scene node.

3. The method according to claim 2, characterized in that The method further comprises: Receive a user's information viewing instruction for the execution link node in the decision management view window, and jump to a link management page corresponding to the execution link node; The link detail information of the execution link node is displayed in the link management page.

4. The method according to claim 1, characterized in that The obtaining of the component node associated with the execution link node comprises: Acquire a component category node associated with the execution link node, wherein the component category node includes a policy component node and / or a non-policy component node; Obtain the component nodes associated with the execution link node under each component category node.

5. The method according to claim 4, characterized in that The associated display of the scene node, the execution link node and the component node in the decision management view window includes: In the decision management view window, the scene node and the execution link node are displayed in association; Associating and displaying the execution link node and the component category node; If the policy component node exists, the component nodes under the policy component node are associated with the policy component node and displayed; If the non-strategy component node exists, the component nodes under the non-strategy component node are associated with the non-strategy component node and displayed.

6. The method according to claim 1, characterized in that The method further comprises: Acquire the policy nodes associated with the component nodes, as well as the version information and online status of each of the policy nodes; In the decision management view window, the policy nodes and the component nodes are displayed in association, and the version information and online status of each policy node are displayed.

7. The method according to claim 6, characterized in that In the decision management view window, the policy nodes and the component nodes are displayed in association, and the version information and online status of each policy node are displayed, including: receiving a user's viewing instruction for a target component node in the decision management window, and determining a target policy node associated with the target component node; The target policy node and the target component node are displayed in association, and the version information and online status of the target policy node are displayed.

8. A global view generation device, characterized in that: The device comprises: A scene link association unit, used to determine a scene node and an execution link node associated with the scene node; A link component association unit, used to obtain a component node associated with the execution link node; The association display unit is used to display the scene node, the execution link node and the component node in an association manner in a decision management view window.

9. A computer storage medium, characterized in that: The computer storage medium stores a plurality of instructions, and the instructions are suitable for being loaded by a processor and executing the method steps according to any one of claims 1 to 7.

10. A computer program product, wherein the computer program product stores a plurality of instructions, wherein the instructions are suitable for being loaded by a processor and executing the method steps according to any one of claims 1 to 7.

11. An electronic device, characterized in that: include: A processor and a memory; wherein the memory stores a computer program, and the computer program is suitable for being loaded by the processor and executing the method steps as claimed in any one of claims 1 to 7.

Images