WO2022068189A1 - 流程可视化监控方法、装置、计算机设备及存储介质 - Google Patents

流程可视化监控方法、装置、计算机设备及存储介质 Download PDF

Info

Publication number
WO2022068189A1
WO2022068189A1 PCT/CN2021/090307 CN2021090307W WO2022068189A1 WO 2022068189 A1 WO2022068189 A1 WO 2022068189A1 CN 2021090307 W CN2021090307 W CN 2021090307W WO 2022068189 A1 WO2022068189 A1 WO 2022068189A1
Authority
WO
WIPO (PCT)
Prior art keywords
node
nodes
current
flowchart
progress
Prior art date
Application number
PCT/CN2021/090307
Other languages
English (en)
French (fr)
Inventor
王振兴
Original Assignee
平安科技（深圳）有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 平安科技（深圳）有限公司 filed Critical 平安科技（深圳）有限公司
Publication of WO2022068189A1 publication Critical patent/WO2022068189A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/30—Creation or generation of source code
    • G06F8/34—Graphical or visual programming
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
    • G06Q10/063—Operations research, analysis or management
    • G06Q10/0633—Workflow analysis
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management
    • G06Q10/103—Workflow collaboration or project management
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
    • Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
    • Y02P90/30—Computing systems specially adapted for manufacturing

Definitions

  • the present application relates to the technical field of process node monitoring, and in particular, to a process visualization monitoring method, device, computer equipment and storage medium.
  • the current application system developed and applied by enterprises includes multiple process nodes, each process node corresponds to different processing personnel and processing deadlines.
  • the application system can be a project development system, and its corresponding business process includes process nodes such as pre-project approval, project development, and post-acceptance. If there is a lack of comprehensive and efficient monitoring, it will seriously affect the progress of project development.
  • the application system can be a financial system, and its financial actuarial business process includes process nodes such as accounting statistics, distribution, data retrieval, accounting, and certification. Without comprehensive and efficient monitoring, the smooth progress of the financial actuarial process cannot be guaranteed.
  • the application system can serve as a medical platform service system, and its corresponding business processes include process nodes such as registration, triage, consultation, medical report, drug collection, and rehabilitation guidance. Without comprehensive and efficient monitoring, platform development cannot be guaranteed. progress.
  • Embodiments of the present application provide a process visualization monitoring method, device, computer equipment, and storage medium to solve the problem that current application systems lack a comprehensive and efficient monitoring method and cannot dynamically and intuitively monitor the progress and abnormalities of process nodes.
  • a process visualization monitoring method comprising:
  • the visual monitoring task includes a business identifier and a process relationship mapping table, and the process relationship mapping table includes N process nodes, inter-node dependencies, and node attribute information;
  • a node event listener is formed based on the node attribute information corresponding to the process node, and the node event listener is embedded in the process node in the initial visualization flowchart to obtain the target visualization flowchart;
  • Acquire background data corresponding to the service identifier process the background data by using the node event listener, and update the node state of the process node in the target visualization flowchart in real time based on the processing result.
  • a process visualization monitoring device comprising:
  • a monitoring task obtaining module configured to obtain a visual monitoring task, where the visual monitoring task includes a business identifier and a process relationship mapping table, and the process relationship mapping table includes N process nodes, inter-node dependencies, and node attribute information;
  • an initial graph acquisition module configured to call a standard process service interface, process the N process nodes and the dependencies between the nodes, and acquire an initial visualized flowchart
  • a target graph acquisition module configured to form a node event listener based on the node attribute information corresponding to the process node, and embed the node event listener on the process node in the initial visualization flowchart to acquire the target visualization flowchart;
  • the real-time monitoring module is used to obtain the background data corresponding to the business identifier, use the node event listener to process the background data, and update the node status of the process nodes in the target visualization flowchart in real time based on the processing results .
  • a computer device comprising a memory, a processor, and computer-readable instructions stored in the memory and executable on the processor, wherein the processor implements the following steps when executing the computer-readable instructions:
  • the visual monitoring task includes a business identifier and a process relationship mapping table, and the process relationship mapping table includes N process nodes, inter-node dependencies, and node attribute information;
  • a node event listener is formed based on the node attribute information corresponding to the process node, and the node event listener is embedded in the process node in the initial visualization flowchart to obtain the target visualization flowchart;
  • Acquire background data corresponding to the service identifier process the background data by using the node event listener, and update the node state of the process node in the target visualization flowchart in real time based on the processing result.
  • One or more readable storage media having computer-readable instructions stored thereon, the computer-readable storage media having computer-readable instructions stored thereon, wherein the computer-readable instructions, when executed by one or more processors, cause all The one or more processors perform the following steps:
  • the visual monitoring task includes a business identifier and a process relationship mapping table, and the process relationship mapping table includes N process nodes, inter-node dependencies, and node attribute information;
  • a node event listener is formed based on the node attribute information corresponding to the process node, and the node event listener is embedded in the process node in the initial visualization flowchart to obtain the target visualization flowchart;
  • Acquire background data corresponding to the service identifier process the background data by using the node event listener, and update the node state of the process node in the target visualization flowchart in real time based on the processing result.
  • the above-mentioned process visualization monitoring method, device, computer equipment and storage medium after obtaining the visualization monitoring task, call the standard process service interface to process all process nodes and the dependencies between nodes, so as to obtain the initial visualized flow chart, and use the standard process service interface.
  • the visual flow chart provides the basis for the realization of dynamic and visual monitoring of the business process of the application system developed by the enterprise or the medical platform; the node event listener is used to process the background data corresponding to the business identifier, and the target visual flow chart is updated in real time based on the processing results.
  • the node status corresponding to the corresponding process node in the system can realize comprehensive and efficient monitoring of the business process, so as to dynamically and intuitively monitor the progress and abnormal conditions of each process node in the business process, so as to update the processing of the business process in time.
  • FIG. 1 is a schematic diagram of an application environment of a process visualization monitoring method in an embodiment of the present application
  • FIG. 2 is a flowchart of a process visualization monitoring method in an embodiment of the present application
  • FIG. 3 is another flowchart of a process visualization monitoring method in an embodiment of the present application.
  • FIG. 5 is another flowchart of a process visualization monitoring method in an embodiment of the present application.
  • FIG. 6 is another flowchart of a process visualization monitoring method in an embodiment of the present application.
  • FIG. 7 is another flowchart of a process visualization monitoring method in an embodiment of the present application.
  • FIG. 8 is a schematic diagram of a process visualization monitoring device in an embodiment of the present application.
  • FIG. 9 is a schematic diagram of a computer device in an embodiment of the present application.
  • the process visualization monitoring method provided by the embodiment of the present application can be applied in the application environment shown in FIG. 1 .
  • the process visualization monitoring method is applied in an application system, and is specifically applied to a business process including multiple process nodes.
  • the application system includes a client and a server as shown in FIG. 1 , and the client and the server communicate through the network. , which is used to realize the visual monitoring of the process by the application system, so that the user can dynamically and intuitively monitor the progress and abnormality of the process nodes in the business process, which helps to ensure the smooth progress of the business process.
  • the client also known as the client, refers to the program corresponding to the server and providing local services for the client.
  • Clients can be installed on, but not limited to, various personal computers, laptops, smartphones, tablets, and portable wearable devices.
  • the server can be implemented as an independent server or a server cluster composed of multiple servers.
  • a method for visual process monitoring is provided, and the method is applied to the server in FIG. 1 as an example for description, including the following steps:
  • S201 Obtain a visual monitoring task, where the visual monitoring task includes a business identifier and a process relationship mapping table, and the process relationship mapping table includes N process nodes, inter-node dependencies, and node attribute information.
  • the visual monitoring task is a task used to trigger visual process monitoring of a specific business process, that is, it is used to trigger real-time visual monitoring of the progress and anomalies of each process node of a specific business process, so that users can understand each process node in real time. the node state, and perform subsequent operations according to the node state.
  • a business identifier is an identifier used to uniquely identify a business process that needs to be monitored visually.
  • the process relationship mapping table is a data table used to reflect the node attribute information of each process node itself in a specific business process and the inter-node dependency relationship between multiple process nodes.
  • the process relationship mapping table not only records the number of process nodes included in the business process, but each business process includes N process nodes, where N ⁇ 2.
  • the process relationship mapping table also records the node attribute information corresponding to each process node, the node attribute information is the information corresponding to each process node and used to reflect the progress and abnormal conditions, including but not limited to trigger conditions, processing deadlines and Information related to process node progress and abnormal conditions, such as progress identifiers.
  • the process relationship mapping table also records the inter-node dependency relationship between two adjacent process nodes.
  • the five process nodes of accounting statistics, distribution, data acquisition, accounting and certification have dependencies, that is, the distribution process node depends on the accounting statistics process node, and the data acquisition process node depends on the accounting process node.
  • Statistics process node For example, in the business process of financial actuarial, the five process nodes of accounting statistics, distribution, data acquisition, accounting and certification have dependencies, that is, the distribution process node depends on the accounting statistics process node, and the data acquisition process node depends on the accounting process node.
  • Statistics process node For example, in the business process of financial actuarial, the five process nodes of accounting statistics, distribution, data acquisition, accounting and certification have dependencies, that is, the distribution process node depends on the accounting statistics process node, and the data acquisition process node depends on the accounting process node.
  • Statistics process node For example, in the business process of financial actuarial, the five process nodes of accounting statistics, distribution, data acquisition, accounting and certification have dependencies, that is, the distribution process node depends on the accounting statistics process
  • the server obtains the visual monitoring task triggered by the user through the client, so as to perform visual process monitoring on the business process corresponding to the business identifier according to the business identifier and the process relationship mapping table in the visual monitoring task.
  • S202 Invoke the standard process service interface, process the N process nodes and the dependencies between the nodes, and obtain an initial visual flow chart.
  • the standard process service interface is a pre-packaged interface that can realize process visualization monitoring.
  • the function of online editing and defining flowcharts can be realized by using the canvas drawing board technology of javascript, and this function can be encapsulated externally as a standard process service interface, so that the application system can connect and access the corresponding functions. That is, the application system encapsulates the functions of online editing and defining flowcharts in the canvas technology into an API interface, so that the functions of using the API interface can be accessed through http requests or https requests, and lightweight access is realized.
  • the initial visual flow chart is a visual flow chart obtained by using a standard process service interface to process the N process nodes and their inter-node dependencies, and does not include the node attribute information.
  • the initial visual flow chart can intuitively reflect the number of process nodes in the business process and the visual flow chart of the dependencies between the process nodes.
  • the server invokes a pre-packaged standard process service interface to process the N process nodes and the inter-node dependencies in the process relationship mapping table, to form a system including all process nodes in the business process and
  • the initial visual flow chart of the dependencies between nodes that is, the initial visual flow chart can connect all process nodes according to the inter-node dependencies, which provides a basis for visual monitoring of each process node in the business process.
  • S203 Form a node event listener based on the node attribute information corresponding to the process node, embed the node event listener on the process node in the initial visualization flowchart, and obtain the target visualization flowchart.
  • the server invokes a preconfigured event monitoring function to process the node attribute information corresponding to each process node to generate a node event listener corresponding to the process node.
  • the event listener function is a preconfigured function for generating node event listeners.
  • a node event listener is an event listener corresponding to a process node and used to monitor changes in the state of the node.
  • the node attribute information corresponding to each process node includes, but is not limited to, information related to the node status of the process node, such as trigger conditions, processing deadlines, and progress identifiers;
  • the event monitoring function can record the node attribute information corresponding to any process node The event monitoring function is passed as the actual parameter, and the actual parameter is replaced by the formal parameter to generate a node event listener corresponding to the process node, so as to use the node event listener to realize dynamic and visual monitoring of the business process.
  • the server embeds the node event listener into the corresponding process node in the initial visual flowchart, so that each process node in the initial visual flowchart They all contain the corresponding node event listeners, so as to obtain the target visual flow chart, and provide a basis for realizing the dynamic monitoring of each process node of the business process.
  • S204 Acquire background data corresponding to the service identifier, process the background data by using a node event listener, and update the node state of the process node in the target visualization flowchart in real time based on the processing result.
  • the server obtains the background data corresponding to the service identifier, and the background data may be background data formed during the execution of the business process by the application system, or may be formed during the execution of the business process by the associated system related to the application system. background data.
  • the background data can be embodied as data reflecting the processing progress of the business process, including but not limited to system logs and process progress data.
  • the server can obtain the background data corresponding to the business identifier in the preset collection period before the current time of the system, so as to process the incremental background data in the preset collection period before the current time of the system, which is helpful to reduce Data processing volume, improve data processing efficiency.
  • the server needs to use the node event listeners corresponding to each process node to process the background data, that is, the background data and the trigger conditions in the node event listeners corresponding to each process node,
  • the processing period and the progress indicator are compared and analyzed to obtain the processing result, which can effectively reflect whether the node status of the corresponding process node has changed; therefore, the target can be updated in real time according to the processing result of the background data by the node event listener.
  • the server updates the node status of the process nodes in the target visualization flowchart in real time based on the processing result, which specifically includes: updating the node color corresponding to each process node in the target visualization flowchart to the node color corresponding to the node status to
  • the node status of the process nodes can be dynamically and visually displayed in the target visualization flowchart.
  • the server can use the node event listener to process the background data corresponding to the service identifier to determine the node status corresponding to each process node.
  • the node status of the process node P2 in the real-time update target visualization flowchart is the execution success status, such as updating its node color to the node color corresponding to the execution success status, such as green or other preconfigured colors.
  • the standard process service interface is called to process all process nodes and the dependencies between nodes, so as to obtain the initial visualized flow chart, and the standard process service interface is used to realize light Quantify access, and use the initial visual flow chart to provide a visual basis for process visual monitoring; then form a node event listener based on the node attribute information corresponding to each process node, and embed it on the process node of the initial visual flow chart to form a target visualization process
  • the diagram provides a basis for realizing dynamic and visual monitoring of business processes; node event listeners are used to process the background data corresponding to the business identifiers, and based on the processing results, the node states corresponding to the corresponding process nodes in the target visualization flow chart are updated in real time, so as to realize the monitoring of the business process.
  • the process is comprehensively and efficiently monitored to dynamically and intuitively monitor the progress and abnormal conditions of each process node in the business process, so as to update the processing of the business process in time
  • step S202 namely calling a standard process service interface, processing N process nodes and the dependencies between the nodes, and obtaining an initial visual flow chart, includes the following steps:
  • S301 Obtain an interface call request, where the interface call request includes a flowchart generation mode.
  • the interface invocation request is a request for triggering the invocation of standard process service interfaces corresponding to different flow chart generation modes to generate flow charts, that is, for triggering invocation of standard process service interfaces corresponding to different flow chart generation modes for N process nodes and The dependencies between nodes are processed to obtain the request for the initial visual flow chart.
  • the flowchart generation mode is a mode used to generate an initial visual flowchart, including template mode and dynamic mode. This template mode is used when the business process is complex and the process nodes do not change frequently.
  • the process nodes and inter-node dependencies in the process relationship mapping table can be filled with the pre-configured configuration visualization template to generate the flow chart of the initial visual flow chart. model.
  • the dynamic mode is applied in the case where the business process is relatively simple or the process nodes change frequently, and the flow chart generation mode is to dynamically generate the initial visual flow chart according to the process nodes and the dependencies between the nodes in the process relationship mapping table.
  • the user can independently select and determine the flowchart generation mode according to the actual application scenario and trigger the interface invocation request, so that the standard process service interface corresponding to the flowchart generation mode can be subsequently called.
  • the standard process service interface corresponding to the template mode is a fixed process service interface.
  • the fixed process service interface is an interface used to generate a visual flowchart with a fixed size of process nodes and a fixed connection method. It is mainly used in complex business processes and In scenarios where process nodes do not change frequently.
  • a configuration visualization template is a template that pre-configures the size and connection method of process nodes.
  • the configuration visualization template in the fixed process service interface (that is, the standard process service interface corresponding to the template mode) is called, and the N process nodes and The inter-node dependencies are processed.
  • the configuration visualization template is filled with N process nodes and inter-node dependencies, so that the initial visualized flowchart can be quickly generated and the generation efficiency of the initial visualized flowchart can be guaranteed.
  • the standard process service interface corresponding to the dynamic mode is the dynamic process service interface.
  • the dynamic process service interface is an interface used to generate a visual flow chart with dynamic changes in the size and connection mode of the process nodes. It is mainly used in business process comparison. In simple or frequently changing scenarios.
  • the flowchart generation algorithm is a processing algorithm used to dynamically generate a flowchart, including but not limited to a point placement algorithm.
  • the preconfigured flowchart generation algorithm in the dynamic process service interface (that is, the standard process service interface corresponding to the dynamic mode) is invoked, and the N in the process relationship mapping table is called.
  • Each process node and the dependencies between nodes are processed to generate an initial visual flow chart, which ensures the diversity of the initial visual flow chart, meets the user's personalized design requirements, and improves the user experience.
  • the configuration visualization template in the fixed process service interface can be invoked, and the N process nodes and the dependencies between the nodes can be called.
  • process obtain the initial visual flow chart, and ensure the generation efficiency of the initial visual flow chart;
  • the flow chart generation mode in the interface call request is the dynamic mode, the flow chart generation algorithm in the dynamic process service interface can be called, and the flow chart generation algorithm in the dynamic process service interface can be called.
  • Process the dependencies between nodes to obtain the initial visual flow chart ensure the diversity of the initial visual flow chart, meet the user's personalized design requirements, and improve the user experience.
  • step S303 namely calling the flowchart generation algorithm in the dynamic process service interface, processing the N process nodes and the dependencies between the nodes, and obtaining the initial visualized flowchart, including the following steps: :
  • S401 Invoke the node positioning logic corresponding to the flowchart generation algorithm in the dynamic process service interface, process the N process nodes and the dependencies between the nodes, and determine the node positions of the N process nodes on the dynamic drawing board.
  • the flow chart generation algorithm is a processing algorithm for dynamically generating flow charts, including but not limited to a point placement algorithm.
  • the layout algorithm is an algorithm used to draw a network topology map in the process of data visualization, so as to realize the automatic layout of the network topology map.
  • the layout algorithm can be a force-directed graph drawing algorithm. Using the force-directed layout algorithm can generate a very beautiful network layout and fully display the overall structure of the network and its automorphic characteristics.
  • the node positioning logic corresponding to the flowchart generation algorithm is the processing logic preconfigured in the flowchart generation algorithm to realize automatic layout of the node positions of each process node during the visual flowchart drawing process.
  • the node positioning logic refers to processing logic generated based on a specific node positioning principle, the node positioning principle includes but is not limited to the principle of symmetry, the principle of orthogonality, the principle of maximizing the connection angle, the principle of minimizing the number of edge crossings, and the Straight edge principle.
  • the symmetry principle refers to the principle of balancing the layout of process nodes with the same structure around the center of the drawing during the process of drawing a visual flowchart.
  • the principle of orthogonality refers to the principle that in the process of drawing a visual flow chart, the grid is used as the background, and the process nodes are arranged at the intersection of the grid as much as possible, so that the edges can be drawn along the grid lines.
  • the principle of maximizing the connection angle refers to the principle of making the angle formed by any two edges of the same process node as large as possible.
  • the principle of minimum number of edge intersections refers to the principle that the number of intersecting edges should be minimized in the process of drawing a visual flowchart.
  • the straight-line edge principle refers to the principle that in the process of drawing a visual flowchart, try to ensure that the edge between two process nodes can go straight.
  • the server invokes the node positioning logic corresponding to the flowchart generation algorithm in the dynamic process service interface, processes the N process nodes and the dependencies between the nodes, and determines the node positions of the N process nodes on the dynamic drawing board, so as to realize Automatically position all process nodes to ensure that the positioning of all process nodes on the dynamic sketchpad conforms to specific node positioning principles, making the subsequent generated initial visual flow chart more aesthetically pleasing.
  • the node drawing logic corresponding to the flowchart generation algorithm is the processing logic used to draw process icons and process lines on the node positions already determined on the dynamic drawing board according to the N process nodes and the dependencies between the nodes.
  • the node drawing logic corresponding to the flowchart generation algorithm needs to take into account certain aesthetic standards during the configuration process to ensure the aesthetics of the drawn initialization flowchart. For example, when the process generation algorithm is a force-directed graph drawing algorithm, the node drawing logic needs to take into account the following formulas.
  • the server invokes the node drawing logic corresponding to the flowchart generation algorithm, and draws the process icons and process connections corresponding to the N process nodes on the dynamic drawing board according to the inter-node dependencies and the node positions of the N process nodes on the dynamic drawing board.
  • Line obtain the initial visual flow chart, complete the automatic drawing of the process icons of all process nodes and their process connections, and ensure that the initial visual flow chart can intuitively reflect the node relationship between all process nodes.
  • the node positioning logic corresponding to the flowchart generation algorithm is called first to process the N process nodes and the dependencies between the nodes, and the node position of each process node on the dynamic drawing board is determined to realize Automatic positioning of node positions; then call the node drawing logic corresponding to the flow chart generation algorithm, draw the corresponding process icons on the corresponding node positions of the dynamic sketchpad, and complete the drawing of all process connections according to the dependencies between nodes, so as to realize automatic The purpose of generating the initial visualization flowchart.
  • acquiring the background data corresponding to the service identifier in step S204 includes:
  • S501 Determine the data source corresponding to the data calling interface based on the data calling interface corresponding to the service identifier.
  • the data invocation interface corresponding to the service identifier is an interface for invoking data related to the business process corresponding to the service identifier.
  • the data source corresponding to the data calling interface is a system for calling data related to the business process corresponding to the business identifier.
  • the data sources corresponding to the data calling interface include a local system and an associated system, where the local system refers to an application system for executing the process visualization monitoring method.
  • Associated systems are systems that communicate with local systems for data interaction.
  • the server reads the data source in the data calling interface according to the preconfigured data calling interface corresponding to the service identifier, so as to perform different processing steps according to different data sources.
  • the system log refers to a log formed during the execution of the business process corresponding to the business identifier.
  • the system log may be an incremental log, that is, a log collected within a preset period before the current system time,
  • the data source corresponding to the data call interface is the local system
  • the business process is executed on the local system
  • the business process execution process will form a corresponding system log. Identify the corresponding system log, and determine the system log as the background data corresponding to the business identification, so as to update the node status of the process nodes in the target visualization flow chart based on the background data, so as to achieve dynamic visual monitoring of the progress and exceptions of the process nodes, etc. Condition.
  • the process progress data is the data used to reflect the execution progress of the business process corresponding to the business identifier, which can be understood as the data reflecting the processing progress and exceptions formed after the associated system analyzes and processes the system logs formed during the execution of the business process. .
  • the data source corresponding to the data calling interface is an associated system
  • Call the interface to obtain the process progress data corresponding to the business identifier fed back by the associated system, and determine the process progress data as the background data corresponding to the business identifier, so that the local system has the advantages of lightweight data and good coupling performance.
  • the data sources corresponding to the data calling interface include local systems and associated systems, so as to realize the diversity of data sources and improve the applicability of process visualization monitoring; when the data source is the local system, the The system log is determined as the background data; when the data source is the associated system, the process progress data is determined as the background data, so that the local system has the advantages of lightweight data and good coupling performance.
  • step S204 the node event listener is used to process the background data, and based on the processing result, the node state of the process node in the target visualization flowchart is updated in real time, including:
  • the server can visualize the flowchart according to the target corresponding to the current time of the system, which can quickly Determine its current process node, where the current process node is the current process node of the business process. Then, the server can call the node event listener corresponding to the current process node to process the system log to determine the current node progress corresponding to the current process node, and the current node progress is used to reflect the processing progress corresponding to the current process node.
  • the server can update the node state of the process node in the target visualization flowchart in real time according to the current node progress corresponding to the current process node. Specifically, it refers to determining the node state corresponding to the current process node according to the current node progress corresponding to the current process node.
  • Visual flow chart The node color corresponding to the current process node is updated to the node color corresponding to the node state, so that the node state of the process node can be dynamically and visually displayed in the target visual flow chart, so as to realize the dynamic operation of the business process executed by the local system. Visual monitoring.
  • S505 If the background data is process progress data, determine the current process node and the current node progress corresponding to the current process node according to the process progress data, and update the node state of the process node in the target visualization flowchart in real time based on the current node progress corresponding to the current process node .
  • the background data obtained by the data calling interface is the process progress data fed back by the associated system
  • the business process is executed on the associated system
  • the process visualization monitoring is executed on the application system
  • the process progress data is the associated system's feedback on the business process.
  • the system log formed during the process execution is analyzed and processed to reflect the processing progress and abnormal data. Therefore, when the server is monitoring the process visually, the acquired process progress data fed back by the associated system includes the current process node (ie, the process node currently executing the business process) and its corresponding current node progress.
  • the server can update the node state of the process node in the target visualization flow chart in real time according to the current node progress corresponding to the current process node, specifically refers to determining the node state corresponding to the current process node according to the current node progress corresponding to the current process node, and converting the target
  • the node color corresponding to the current process node in the visual flow chart is updated to the node color corresponding to the node state, so that the node state of the process node can be dynamically and intuitively displayed in the target visual flow chart, so as to realize the business process execution of the associated system. Dynamic visual monitoring.
  • the background data is the system log and the process progress data
  • different processing logics are used to process the system log and the process progress data respectively, so as to determine the current node progress corresponding to the current process node , so as to update the node status of the process nodes in the target visualization flowchart in real time according to the current node progress, so as to realize the dynamic visual monitoring of the current process nodes of the business process and ensure the comprehensiveness of the monitoring.
  • the node state of the process node in the target visualization flowchart is updated in real time based on the current node progress corresponding to the current process node, including:
  • the post-sequence process node refers to a process node that depends on the current process node, that is, one or more parallel process nodes that need to be executed after the current process node.
  • the server needs to update the node status of the current process node in the target visualization flow chart to the execution successful state based on the current node progress, that is, update the node color of the current process node to The node color corresponding to the successful execution state; and update the node state of the subsequent process node that depends on the current process node to the executing state, that is, update the node color of the subsequent process node to the executing state, so that the next dynamic visualization monitoring , and the subsequent process node in the executing state is determined as the current process node for monitoring.
  • a business process is a processing flow formed by multiple process nodes according to the execution order, when each current process node is successfully executed, it is necessary to determine whether there is a subsequent process node in the business process that depends on the current process node. If it exists, it is necessary to update the node state of the subsequent process node that depends on the current process node to the executing state, so as to achieve the purpose of dynamic visual monitoring.
  • the server It is only necessary to update the node status of the current process node in the target visualization flowchart in real time based on the current node progress corresponding to the current process node, that is, update the node color corresponding to the current process node to the node color of the node state corresponding to the current node progress. Dynamic visual monitoring of process nodes.
  • the process visualization monitoring method when the progress of the current node corresponding to the current process node is successfully executed, the node states of the current process node and the subsequent process node in the target visualization flowchart need to be updated at the same time.
  • the corresponding current node progress is not successfully executed, it is only necessary to update the node status of the current process node in the target visualization flowchart based on the current node progress, so as to realize the purpose of dynamic visual monitoring, so as to realize the application system developed by the enterprise or the medical platform.
  • step S504 the system log is processed by the node event listener corresponding to the current process node, and the current node progress corresponding to the current process node is obtained, including:
  • S701 Use the node event listener corresponding to the current process node to process the system log, and determine whether the system log contains the node log corresponding to the current process node.
  • the server may use the node event listener corresponding to the current process node to scan the system log, and determine whether the system log contains the node log corresponding to the current process node to reflect whether the current process node is executed.
  • the node log is the log formed during the execution of the current process node.
  • the server does not include the node log corresponding to the current process node in the system log, indicating that the node state corresponding to the current process node in the target visualization flowchart is the executing state, and the node state of the current process node is the executing state after the node state is the executing state.
  • the user has not executed the current process node.
  • the current node progress corresponding to the current process node is set to be executing by default, and the node state of the current process node in the target visualization flowchart is maintained as the executing state.
  • the node event listener corresponding to each process node in the target visualization flowchart is formed based on node attribute information such as trigger conditions, processing deadlines, and progress identifiers. If the trigger condition of any current process node is the successful execution of its predecessor process node , that is, when the pre-order process node is successfully executed, the node state of the current process node that depends on the pre-order process node is automatically triggered to be the executing state, and within the processing period after the node state changes to the executing state, the current process Nodes perform real-time dynamic monitoring.
  • node attribute information such as trigger conditions, processing deadlines, and progress identifiers.
  • S703 If the system log includes the node log corresponding to the current process node, determine the current node progress corresponding to the current process node according to the progress identifier in the node log.
  • the server when the server includes the node log corresponding to the current process node in the system log, it indicates that the user executes the current process node from the time when the node state of the current process node is the executing state to the current time of the system.
  • the node log corresponding to the current process node is extracted from the log, and the current node progress corresponding to the current process node is determined according to the progress identifier recorded in the node log, which can realize real-time dynamic monitoring of the current process node.
  • the progress indicator includes, but is not limited to, an in-execution indicator, an execution success indicator, an execution failure indicator, an execution timeout indicator, and an execution exception indicator.
  • the current node progress is set to be executing by default; when the system log contains the node log corresponding to the current process node , and automatically determine the corresponding current node progress according to the progress identifier recorded in the node log, so as to monitor the execution of the business process comprehensively and efficiently.
  • a process visualization monitoring device is provided, and the process visualization monitoring device is in one-to-one correspondence with the process visualization monitoring method in the above-mentioned embodiment.
  • the process visualization monitoring device includes a monitoring task acquisition module 801 , an initial map acquisition module 802 , a target map acquisition module 803 and a real-time monitoring module 804 .
  • the detailed description of each functional module is as follows:
  • the monitoring task obtaining module 801 is used for obtaining a visual monitoring task.
  • the visual monitoring task includes a business identifier and a process relationship mapping table, and the process relationship mapping table includes N process nodes, inter-node dependencies and node attribute information.
  • the initial graph obtaining module 802 is configured to call the standard process service interface, process the N process nodes and the dependencies between the nodes, and obtain the initial visualized flow chart.
  • the target graph acquiring module 803 is configured to form a node event listener based on the node attribute information corresponding to the process node, embed the node event listener on the process node in the initial visualization flowchart, and acquire the target visualization flowchart.
  • the real-time monitoring module 804 is used for acquiring the background data corresponding to the service identifier, processing the background data by using the node event listener, and updating the node status of the process nodes in the target visualization flowchart in real time based on the processing result.
  • the initial map acquisition module 802 includes:
  • the interface invocation unit is used to obtain an interface invocation request, where the interface invocation request includes a flow chart generation mode.
  • the template generation unit is used to call the configuration visualization template in the fixed process service interface if the flow chart generation mode is the template mode, process the N process nodes and the dependencies between the nodes, and obtain the initial visualized flow chart.
  • the dynamic generation unit is used to call the flowchart generation algorithm in the dynamic process service interface if the flowchart generation mode is the dynamic mode, process the N process nodes and the dependencies between the nodes, and obtain the initial visualized flowchart.
  • the dynamic generation unit includes:
  • the node positioning subunit is used to call the node positioning logic corresponding to the flowchart generation algorithm in the dynamic process service interface, process the N process nodes and the dependencies between the nodes, and determine the node positions of the N process nodes on the dynamic drawing board.
  • the process drawing subunit is used to call the node drawing logic corresponding to the flowchart generation algorithm in the dynamic process service interface, and draw N processes on the dynamic drawing board according to the dependencies between nodes and the node positions of the N process nodes on the dynamic drawing board.
  • the process icon corresponding to the node and the process connection are obtained to obtain the initial visual flowchart.
  • the real-time monitoring module 804 includes:
  • the data source determination unit is configured to determine the data source corresponding to the data invocation interface based on the data invocation interface corresponding to the business identifier.
  • the system log obtaining unit is used for obtaining the system log corresponding to the business identifier based on the data calling interface if the data source corresponding to the data calling interface is the local system, and determining the system log as the background data corresponding to the business identifier.
  • the progress data acquisition unit is used to obtain the process progress data corresponding to the business identifier fed back by the associated system based on the data call interface if the data source corresponding to the data calling interface is the associated system, and determine the process progress data as the corresponding business identifier. background data.
  • the real-time monitoring module 804 includes:
  • the log monitoring unit is used to process the system log using the node event listener corresponding to the current process node if the background data is the system log, obtain the current node progress corresponding to the current process node, and real-time based on the current node progress corresponding to the current process node. Update the node state of the process nodes in the target visualization flowchart.
  • the progress monitoring unit is used to determine the current process node and the current node progress corresponding to the current process node according to the process progress data if the background data is the process progress data, and update the process in the target visualization flowchart in real time based on the current node progress corresponding to the current process node The node state of the node.
  • the real-time monitoring module 804 includes:
  • the update unit is used to update the node status of the current process node in the target visualization flow chart based on the current node progress if the current node progress corresponding to the current process node is successfully executed, and update the nodes of the subsequent process nodes that depend on the current process node. state.
  • a separate update unit is used to update the node state of the current process node in the target visualization flow chart based on the current node progress if the current node progress corresponding to the current process node is not successfully executed.
  • the log monitoring unit includes:
  • the node log judgment subunit is used to process the system log by using the node event listener corresponding to the current process node, and determine whether the system log contains the node log corresponding to the current process node.
  • the first progress determination subunit is used for, if the system log does not contain the node log corresponding to the current process node, the current node progress corresponding to the current process node is in execution.
  • the second progress determination subunit is configured to determine the current node progress corresponding to the current process node according to the progress identifier in the node log if the system log contains the node log corresponding to the current process node.
  • Each module in the above-mentioned process visualization monitoring device may be implemented in whole or in part by software, hardware and combinations thereof.
  • the above modules can be embedded in or independent of the processor in the computer device in the form of hardware, or stored in the memory in the computer device in the form of software, so that the processor can call and execute the operations corresponding to the above modules.
  • a computer device is provided, and the computer device may be a server, and its internal structure diagram may be as shown in FIG. 9 .
  • the computer device includes a processor, memory, a network interface, and a database connected by a system bus. Among them, the processor of the computer device is used to provide computing and control capabilities.
  • the memory of the computer device includes a non-volatile storage medium, an internal memory.
  • the non-volatile storage medium stores an operating system, computer readable instructions and a database.
  • the internal memory provides an environment for the execution of the operating system and computer-readable instructions in the non-volatile storage medium.
  • the database of the computer device is used to store the data adopted or generated in the process of executing the process visualization monitoring method.
  • the network interface of the computer device is used to communicate with an external terminal through a network connection. When the computer readable instructions are executed by the processor, a process visualization monitoring method is implemented.
  • a computer device including a memory, a processor, and computer-readable instructions stored in the memory and executable on the processor, and the processor implements the processes in the foregoing embodiments when the processor executes the computer-readable instructions
  • Visual monitoring methods such as S201-S204 shown in FIG. 2 , or shown in FIG. 3 to FIG. 7 , are not repeated here to avoid repetition.
  • the processor executes the computer-readable instructions
  • the functions of each module/unit in this embodiment of the process visualization monitoring device are realized, for example, the monitoring task acquisition module 801, the initial map acquisition module 802, and the target map acquisition module shown in FIG. 8 803 and the functions of the real-time monitoring module 804 are not repeated here to avoid repetition.
  • one or more readable storage media storing computer readable instructions stored thereon, the computer readable instructions being processed by one or more
  • the one or more processors execute the computer-readable instructions to implement the process visualization monitoring method in the above embodiment, for example, S201-S204 shown in FIG. 2, or shown in FIG. 3 to FIG. 7, in order to avoid Repeat, and will not repeat them here.
  • the computer-readable instructions are executed by the processor, the functions of each module/unit in the embodiment of the above-mentioned process visualization monitoring device are realized, for example, the monitoring task acquisition module 801 shown in FIG.
  • the readable storage medium in this embodiment includes a non-volatile readable storage medium and a volatile readable storage medium.
  • Nonvolatile memory may include read only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory.
  • Volatile memory may include random access memory (RAM) or external cache memory.
  • RAM is available in various forms such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous chain Road (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), etc.

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Human Resources & Organizations (AREA)
  • Strategic Management (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Theoretical Computer Science (AREA)
  • Software Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Economics (AREA)
  • Operations Research (AREA)
  • Marketing (AREA)
  • General Engineering & Computer Science (AREA)
  • Quality & Reliability (AREA)
  • Tourism & Hospitality (AREA)
  • General Business, Economics & Management (AREA)
  • Educational Administration (AREA)
  • Game Theory and Decision Science (AREA)
  • Development Economics (AREA)
  • Data Mining & Analysis (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Debugging And Monitoring (AREA)

Abstract

一种流程可视化监控方法、装置、计算机设备及存储介质。该方法包括：获取可视化监控任务，可视化监控任务包括业务标识和流程关系映射表，流程关系映射表包括N个流程节点、节点间依赖关系和节点属性信息（S201）；调用标准流程服务接口，对N个流程节点和节点间依赖关系进行处理，获取初始可视化流程图（S202）；基于节点属性信息形成节点事件***并嵌入到初始可视化流程图中的流程节点上，获取目标可视化流程图（S203）；获取与业务标识相对应的后台数据，采用节点事件***对后台数据进行处理，基于处理结果实时更新目标可视化流程图中流程节点的节点状态（S204）。该方法可实现对企业开发或者医疗平台开发的应用***的业务流程全面高效监控，动态且直观地监听业务流程中每一流程节点的进度和异常情况。

Description

流程可视化监控方法、装置、计算机设备及存储介质
本申请以2020年9月30日提交的申请号为202011063771.7，名称为“流程可视化监控方法、装置、计算机设备及存储介质”的中国发明申请为基础，并要求其优先权。
技术领域
本申请涉及流程节点监控技术领域，尤其涉及一种流程可视化监控方法、装置、计算机设备及存储介质。
背景技术
当前企业开发和应用的应用***，包括多个流程节点，每个流程节点对应不同的处理人员和处理期限，发明人意识到当前应用***缺乏全面高效监控方式，无法动态且直观地监控流程节点的进度和异常情况。例如，该应用***可以为项目开发***，其对应的业务流程包括前期立项、项目开发和后期验收等流程节点，若缺乏全面高效的监控，会严重影响项目开发的进度。又例如，该应用***可以为财务***，其财务精算这一业务流程包括会计统计、分发、取数、核算和制证等流程节点，若缺乏全面高效的监控，无法保障财务精算过程的顺利进行。又例如，该应用***可以为医疗平台服务***，其对应的业务流程包括挂号、分诊、问诊、医疗报告、取药、康复指引等流程节点，若缺乏全面高效的监控，无法保障平台开发的进度。
发明内容
本申请实施例提供一种流程可视化监控方法、装置、计算机设备及存储介质，以解决当前应用***缺乏全面高效监控方式，无法动态且直观地监控流程节点的进度和异常的问题。
一种流程可视化监控方法，包括：
获取可视化监控任务，所述可视化监控任务包括业务标识和流程关系映射表，所述流程关系映射表包括N个流程节点、节点间依赖关系和节点属性信息；
调用标准流程服务接口，对N个所述流程节点和所述节点间依赖关系进行处理，获取初始可视化流程图；
基于所述流程节点对应的节点属性信息形成节点事件***，将所述节点事件***嵌入到所述初始可视化流程图中的流程节点上，获取目标可视化流程图；
获取与所述业务标识相对应的后台数据，采用所述节点事件***对所述后台数据进行处理，基于处理结果实时更新所述目标可视化流程图中流程节点的节点状态。
一种流程可视化监控装置，包括：
监控任务获取模块，用于获取可视化监控任务，所述可视化监控任务包括业务标识和流程关系映射表，所述流程关系映射表包括N个流程节点、节点间依赖关系和节点属性信息；
初始图获取模块，用于调用标准流程服务接口，对N个所述流程节点和所述节点间依赖关系进行处理，获取初始可视化流程图；
目标图获取模块，用于基于所述流程节点对应的节点属性信息形成节点事件***，将所述节点事件***嵌入到所述初始可视化流程图中的流程节点上，获取目标可视化流程图；
实时监控模块，用于获取与所述业务标识相对应的后台数据，采用所述节点事件监听 器对所述后台数据进行处理，基于处理结果实时更新所述目标可视化流程图中流程节点的节点状态。
一种计算机设备，包括存储器、处理器以及存储在所述存储器中并可在所述处理器上运行的计算机可读指令，其中，所述处理器执行所述计算机可读指令时实现下步骤：
获取可视化监控任务，所述可视化监控任务包括业务标识和流程关系映射表，所述流程关系映射表包括N个流程节点、节点间依赖关系和节点属性信息；
调用标准流程服务接口，对N个所述流程节点和所述节点间依赖关系进行处理，获取初始可视化流程图；
基于所述流程节点对应的节点属性信息形成节点事件***，将所述节点事件***嵌入到所述初始可视化流程图中的流程节点上，获取目标可视化流程图；
获取与所述业务标识相对应的后台数据，采用所述节点事件***对所述后台数据进行处理，基于处理结果实时更新所述目标可视化流程图中流程节点的节点状态。
一个或多个存储有计算机可读指令的可读存储介质，所述计算机可读存储介质存储有计算机可读指令，其中，所述计算机可读指令被一个或多个处理器执行时，使得所述一个或多个处理器执行如下步骤：
获取可视化监控任务，所述可视化监控任务包括业务标识和流程关系映射表，所述流程关系映射表包括N个流程节点、节点间依赖关系和节点属性信息；
调用标准流程服务接口，对N个所述流程节点和所述节点间依赖关系进行处理，获取初始可视化流程图；
基于所述流程节点对应的节点属性信息形成节点事件***，将所述节点事件***嵌入到所述初始可视化流程图中的流程节点上，获取目标可视化流程图；
获取与所述业务标识相对应的后台数据，采用所述节点事件***对所述后台数据进行处理，基于处理结果实时更新所述目标可视化流程图中流程节点的节点状态。
上述流程可视化监控方法、装置、计算机设备及存储介质，在获取可视化监控任务之后，调用标准流程服务接口对所有流程节点和节点间依赖关系进行处理，以获取初始可视化流程图，利用标准流程服务接口实现轻量化访问，且利用初始可视化流程图为流程可视化监控提供可视化基础；再基于每一流程节点对应的节点属性信息形成节点事件***，并嵌入到初始可视化流程图的流程节点上，形成目标可视化流程图，为实现对企业开发或者医疗平台开发的应用***的业务流程进行动态可视化监听提供基础；采用节点事件***对业务标识对应的后台数据进行处理，基于处理结果实时更新目标可视化流程图中相应流程节点对应的节点状态，实现对业务流程全面高效监控，以实现动态且直观地监听业务流程中每一流程节点的进度和异常情况，以便及时更新业务流程的处理。
附图说明
为了更清楚地说明本申请实施例的技术方案，下面将对本申请实施例的描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动性的前提下，还可以根据这些附图获得其他的附图。
图1是本申请一实施例中流程可视化监控方法的一应用环境示意图；
图2是本申请一实施例中流程可视化监控方法的一流程图；
图3是本申请一实施例中流程可视化监控方法的另一流程图；
图4是本申请一实施例中流程可视化监控方法的另一流程图；
图5是本申请一实施例中流程可视化监控方法的另一流程图；
图6是本申请一实施例中流程可视化监控方法的另一流程图；
图7是本申请一实施例中流程可视化监控方法的另一流程图；
图8是本申请一实施例中流程可视化监控装置的一示意图；
图9是本申请一实施例中计算机设备的一示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
本申请实施例提供的流程可视化监控方法，该流程可视化监控方法可应用如图1所示的应用环境中。具体地，该流程可视化监控方法应用在应用***中，具体应用在包含多个流程节点的业务流程上，该应用***包括如图1所示的客户端和服务器，客户端与服务器通过网络进行通信，用于实现应用***进行流程可视化监控，以使用户可动态且直观地监控业务流程中流程节点的进度和异常，有助于保障业务流程的顺利进行。其中，客户端又称为用户端，是指与服务器相对应,为客户提供本地服务的程序。客户端可安装在但不限于各种个人计算机、笔记本电脑、智能手机、平板电脑和便携式可穿戴设备上。服务器可以用独立的服务器或者是多个服务器组成的服务器集群来实现。
在一实施例中，如图2所示，提供一种流程可视化监控方法，以该方法应用在图1中的服务器为例进行说明，包括如下步骤：
S201：获取可视化监控任务，可视化监控任务包括业务标识和流程关系映射表，流程关系映射表包括N个流程节点、节点间依赖关系和节点属性信息。
其中，可视化监控任务是用于触发对特定业务流程进行流程可视化监控的任务，即用于触发对特定业务流程的各个流程节点的进度和异常进行实时可视化监控，以使用户可实时了解各个流程节点的节点状态，并根据节点状态执行后续的操作。业务标识是用于唯一识别需要进行流程可视化监控的业务流程的标识。
其中，流程关系映射表是用于反映特定业务流程中各个流程节点自身的节点属性信息以及多个流程节点之间的节点间依赖关系的数据表。本示例中，流程关系映射表不仅记录业务流程所包含流程节点的数量，每一业务流程包括N个流程节点，其中，N≧2。该流程关系映射表还记录每个流程节点对应的节点属性信息，该节点属性信息是与每一流程节点相对应的用于反映进度和异常情况的信息，包括但不限于触发条件、处理期限和进度标识等与流程节点进度和异常情况相关的信息。且该流程关系映射表还记录相邻两个流程节点之间的节点间依赖关系。例如，在财务精算这一业务流程中，会计统计、分发、取数、核算和制证这五个流程节点存在依赖关系，即分发流程节点依赖于会计统计流程节点，取数流程节点依赖于会计统计流程节点。
作为一示例，服务器获取用户通过客户端触发的可视化监控任务，以便根据可视化监控任务中的业务标识和流程关系映射表，对业务标识对应的业务流程进行流程可视化监控。
S202：调用标准流程服务接口，对N个流程节点和节点间依赖关系进行处理，获取初始可视化流程图。
其中，标准流程服务接口是预先封装可实现流程可视化监控的接口。作为一示例，可采用javascript的canvas画板技术实现在线编辑和定义流程图的功能，对外封装此功能为标准流程服务接口，以使应用***可对接和访问相应功能。即应用***将canvas画板技术中实现在线编辑和定义流程图的功能封装成API接口，以使通过http请求或者https请求等方式，访问使用API接口的功能，实现轻量化访问。
其中，初始可视化流程图是采用标准流程服务接口对N个流程节点和节点间依赖关系进行处理，所获取的未包含节点属性信息的可视化流程图。一般来说，该初始可视化流程图可直观反映业务流程中流程节点的数量以及流程节点之间的依赖关系的可视化流程图。
作为一示例，服务器在接收到可视化监控任务后，调用预先封装的标准流程服务接口，对流程关系映射表中的N个流程节点和节点间依赖关系进行处理，形成包含业务流程中所有流程节点以及节点间依赖关系的初始可视化流程图，即初始可视化流程图可依据节点间依赖关系将所有流程节点连线，为实现对业务流程中各个流程节点进行可视化监控提供基础。
S203：基于流程节点对应的节点属性信息形成节点事件***，将节点事件***嵌入到初始可视化流程图中的流程节点上，获取目标可视化流程图。
作为一示例，服务器调用预先配置的事件监听函数，对每个流程节点对应的节点属性信息进行处理，生成与流程节点相对应的节点事件***。该事件监听函数是预先配置的用于生成节点事件***的函数。节点事件***是与流程节点相对应的用于监听节点状态变化的事件***。本示例中，每个流程节点对应的节点属性信息包括但不限于触发条件、处理期限和进度标识等与流程节点的节点状态相关的信息；事件监听函数可将任一流程节点对应的节点属性信息作为实际参数传入事件监听函数，将实际参数替代形式参数，生成与该流程节点对应的节点事件***，以便利用该节点事件***实现对业务流程进行动态可视化监听。
作为一示例，服务器在生成每个流程节点对应的节点事件***之后，将该节点事件***嵌入到初始可视化流程图中相应的流程节点上，以使初始可视化流程图中的每个流程节点均包含与其相对应的节点事件***，从而获取目标可视化流程图，为实现将业务流程的各个流程节点进行动态监控提供基础。
S204：获取与业务标识相对应的后台数据，采用节点事件***对后台数据进行处理，基于处理结果实时更新目标可视化流程图中流程节点的节点状态。
作为一示例，服务器获取业务标识对应的后台数据，该后台数据可以是本应用***在执行业务流程过程中形成的后台数据，也可以为与本应用***相关的关联***在执行业务流程过程中形成的后台数据。本示例中，后台数据可以体现为反映业务流程处理进度的数据，包括但不限于***日志和流程进度数据。本示例中，服务器可获取***当前时间之前预设采集周期内的与业务标识相对应的后台数据，以实现对***当前时间之前预设采集周期内的增量后台数据进行处理，有助于减少数据处理量，提高数据处理效率。
作为一示例，服务器在获取业务标识对应的后台数据之后，需采用各个流程节点对应的节点事件***对后台数据进行处理，即将后台数据与每一流程节点对应的节点事件***中触发条件、处理期限和进度标识进行对比分析处理，以获取处理结果，该处理结果可以有效反映相应的流程节点的节点状态是否发生变化；因此，可以根据节点事件***对后台数据的处理结果，实时更新目标可视化流程图中的流程节点的节点状态。
作为一示例，服务器基于处理结果实时更新目标可视化流程图中流程节点的节点状态，具体包括：将目标可视化流程图中每个流程节点对应的节点颜色更新为与节点状态相对应的节点颜色，以使流程节点的节点状态可动态直观显示在目标可视化流程图中。
例如，若一业务流程包括P1、P2、P3和P4这几个流程节点，每个流程节点对应的处理期限为T1、T2、T3和T4；每个流程节点对应的节点状态包括执行中、执行成功、执行失败、执行超时和执行异常等节点进度，其对应的进度标识分别为S1、S2、S3、S4和S5。本示例中，服务器可采用节点事件***，对业务标识对应的后台数据进行处理，以确定每个流程节点对应的节点状态，例如，若节点事件***监听到后台数据中包括流程节点P2对应的进度标识S3，则实时更新目标可视化流程图中流程节点P2的节点状态为执行成功状态，如更新其节点颜色为执行成功状态对应的节点颜色，如绿色或者其他预先配置的颜色。
本实施例所提供的流程可视化监控方法中，在获取可视化监控任务之后，调用标准流程服务接口对所有流程节点和节点间依赖关系进行处理，以获取初始可视化流程图，利用 标准流程服务接口实现轻量化访问，且利用初始可视化流程图为流程可视化监控提供可视化基础；再基于每一流程节点对应的节点属性信息形成节点事件***，并嵌入到初始可视化流程图的流程节点上，形成目标可视化流程图，为实现对业务流程进行动态可视化监听提供基础；采用节点事件***对业务标识对应的后台数据进行处理，基于处理结果实时更新目标可视化流程图中相应流程节点对应的节点状态，实现对业务流程全面高效监控，以实现动态且直观地监听业务流程中每一流程节点的进度和异常情况，以便及时更新业务流程的处理。
在一实施例中，如图3所示，步骤S202，即调用标准流程服务接口，对N个流程节点和节点间依赖关系进行处理，获取初始可视化流程图，包括如下步骤：
S301：获取接口调用请求，接口调用请求包括流程图生成模式。
其中，接口调用请求是用于请求触发调用不同流程图生成模式对应的标准流程服务接口生成流程图的请求，即用于触发调用不同流程图生成模式对应的标准流程服务接口对N个流程节点和节点间依赖关系进行处理，获取初始可视化流程图的请求。流程图生成模式是用于生成初始可视化流程图的模式，具体包括模板模式和动态模式。该模板模式应用于业务流程较复杂且流程节点不经常变动的情况，可将流程关系映射表中的流程节点和节点间依赖关系填充预先配置的配置可视化模板以生成初始可视化流程图的流程图生成模式。该动态模式应用在业务流程较简单或者流程节点经常变动的情况，根据流程关系映射表中的流程节点和节点间依赖关系动态生成初始可视化流程图的流程图生成模式。
作为一示例，在调用标准流程服务接口过程中，用户可根据实际应用场景的不同，自主选择确定流程图生成模式并触发接口调用请求，以便后续调用与流程图生成模式相对应的标准流程服务接口进行处理，生成初始可视化流程图。
S302：若流程图生成模式为模板模式，则调用固定流程服务接口中的配置可视化模板，对N个流程节点和节点间依赖关系进行处理，获取初始可视化流程图。
其中，与模板模式相对应的标准流程服务接口为固定流程服务接口，该固定流程服务接口是用于生成流程节点大小和连线方式固定的可视化流程图的接口，主要应用在业务流程较复杂且流程节点不经常变动的场景下。配置可视化模板是预先配置好流程节点大小和连线方式的模板。
作为一示例，在流程图生成模式为模板模式，则调用固定流程服务接口(即与模板模式相对应的标准流程服务接口)中的配置可视化模板，对流程关系映射表中的N个流程节点和节点间依赖关系进行处理，具体是指将N个流程节点和节点间依赖关系填充在配置可视化模板，即可快速生成初始可视化流程图，保障初始可视化流程图的生成效率。
S303：若流程图生成模式为动态模式，则调用动态流程服务接口中的流程图生成算法，对N个流程节点和节点间依赖关系进行处理，获取初始可视化流程图。
相应地，与动态模式相对应的标准流程服务接口为动态流程服务接口，该动态流程服务接口是用于生成流程节点大小和连线方式动态变化的可视化流程图的接口，主要应用在业务流程较简单或者流程节点经常变动的场景下。流程图生成算法是用于动态生成流程图的处理算法，包括但不限于布点算法。
作为一示例，在流程图生成模式为动态模式时，则调用动态流程服务接口(即与动态模式相对应的标准流程服务接口)中预先配置的流程图生成算法，对流程关系映射表中的N个流程节点和节点间依赖关系进行处理，生成初始可视化流程图，保障初始可视化流程图的多样性，符合用户的个性化设计需求，提高用户体验。
本实施例所提供的流程可视化监控方法中，在接口调用请求中的流程图生成模式为模板模式时，可调用固定流程服务接口中的配置可视化模板，对N个流程节点和节点间依赖关系进行处理，获取初始可视化流程图，保障初始可视化流程图的生成效率；在接口调用请求中的流程图生成模式为动态模式时，可调用动态流程服务接口中的流程图生成算法， 对N个流程节点和节点间依赖关系进行处理，获取初始可视化流程图，保障初始可视化流程图的多样性，符合用户的个性化设计需求，提高用户体验。
在一实施例中，如图4所示，步骤S303，即调用动态流程服务接口中的流程图生成算法，对N个流程节点和节点间依赖关系进行处理，获取初始可视化流程图，包括如下步骤：
S401：调用动态流程服务接口中的流程图生成算法对应的节点定位逻辑，对N个流程节点和节点间依赖关系进行处理，确定N个流程节点在动态画板上的节点位置。
其中，流程图生成算法是用于动态生成流程图的处理算法，包括但不限于布点算法。该布点算法是在数据可视化过程中，用于绘制网络拓扑图的算法，以实现网络拓扑图的自动布局的算法。该布点算法可以为力导向绘图(Force-directed graph drawing)算法，利用力引导布局算法可以产生相当优美的网络布局，并充分展现网络的整体结构及其自同构特征。
其中，流程图生成算法对应的节点定位逻辑是流程图生成算法中，预先配置的用于实现在可视化流程图绘制过程中各个流程节点的节点位置进行自动布局的处理逻辑。一般来说，该节点定位逻辑是指基于特定的节点定位原则生成的处理逻辑，该节点定位原则包括但不限于对称性原则、正交性原则、连接角最大化原则、边交叉数量最小原则和直线边原则。该对称性原则是指绘制可视化流程图过程中，将具有相同结构的流程节点围绕绘图中心平衡布局的原则。正交性原则是指绘制可视化流程图过程中，以网格为背景，尽量将流程节点布局在网格交叉处，使边可以沿着网格线绘制的原则。连接角最大化原则是指使同一流程节点任意两条边形成的角度尽量大的原则。边交叉数量最小原则是指绘制可视化流程图过程中，应尽量减少相互交叉边的数量的原则。直线边原则是指绘制可视化流程图过程中，尽量保证两个流程节点之间的边可走直线的原则。
作为一示例，服务器调用动态流程服务接口中的流程图生成算法对应的节点定位逻辑，对N个流程节点和节点间依赖关系进行处理，确定N个流程节点在动态画板上的节点位置，以实现对所有流程节点进行自动定位，保障所有流程节点在动态画板的定位符合特定的节点定位原则，使得后续生成的初始可视化流程图更具有美观性。
S402：调用动态流程服务接口中的流程图生成算法对应的节点绘制逻辑，依据节点间依赖关系和N个流程节点在动态画板上的节点位置，在动态画板上绘制N个流程节点对应的流程图标和流程连线，获取初始可视化流程图。
其中，流程图生成算法对应的节点绘制逻辑是用于根据N个流程节点和节点间依赖关系，在动态画板已有确定的节点位置上绘制流程图标和流程连线的处理逻辑。一般来说，流程图生成算法对应的节点绘制逻辑在配置过程中，需兼顾一定的美学标准，以保证绘制的初始化流程图的美观性。例如，在流程生成算法为为力导向绘图(Force-directed graph drawing)算法时，其节点绘制逻辑需兼顾如下几个公式，在实现初始可视化流程图的自动化绘制过程中，确定每一流程节点的流程图标的图面积和流程连线的长度等，保证所绘制的初始可视化流程图的美观性：(1)边长偏差＝最大边长-最小边长/(平均边长*图的边数)；(2)节点分布偏差＝|最佳分布距离–最小节点距离|/图面积，其中：最佳分布距离＝图面积/图节点个数。
作为一示例，服务器调用流程图生成算法对应的节点绘制逻辑，依据节点间依赖关系和N个流程节点在动态画板上的节点位置，在动态画板上绘制N个流程节点对应的流程图标和流程连线，获取初始可视化流程图，完成所有流程节点的流程图标及其流程连线的自动绘制，保证初始可视化流程图可直观反映所有流程节点之间的节点关系。
本实施例所提供的流程可视化监控方法中，先调用流程图生成算法对应的节点定位逻辑对N个流程节点及节点间依赖关系进行处理，确定每一流程节点在动态画板上的节点位置，实现节点位置的自动定位；再调用流程图生成算法对应的节点绘制逻辑，在动态画板 相应的节点位置上绘制相应的流程图标，并依据节点间依赖关系，完成所有流程连线的绘制，从而实现自动生成初始可视化流程图的目的。
在一实施例中，如图5所示，步骤S204中的获取与业务标识相对应的后台数据，包括：
S501：基于业务标识对应的数据调用接口，确定数据调用接口对应的数据来源。
其中，与业务标识相对应的数据调用接口是用于调用与业务标识对应的业务流程相关的数据的接口。数据调用接口对应的数据来源是用于调用与业务标识相对应的业务流程相关的数据的***。一般来说，数据调用接口对应的数据来源包括本地***和关联***，其中，本地***是指用于执行该流程可视化监控方法的应用***。关联***是与本地***通信，以实现数据交互的***。
作为一示例，服务器根据预先配置的与业务标识相对应的数据调用接口，读取该数据调用接口中的数据来源，以便根据数据来源的不同，执行不同的处理步骤。
S502：若数据调用接口对应的数据来源为本地***，则基于数据调用接口，获取与业务标识相对应的***日志，将***日志确定为业务标识对应的后台数据。
其中，***日志是指业务标识对应的业务流程执行过程中形成的日志。作为一示例，该***日志可以为增量日志，即在***当前时间之前的预设期间内采集到的日志，
作为一示例，若数据调用接口对应的数据来源为本地***，则说明业务流程在本地***上执行，其业务流程执行过程会形成相应的***日志，因此，可通过数据调用接口，实时调用与业务标识相对应的***日志，将该***日志确定为与业务标识对应的后台数据，以便基于后台数据更新目标可视化流程图中的流程节点的节点状态，从而达到动态可视化监控流程节点的进度和异常等情况。
S503：若数据调用接口对应的数据来源为关联***，则基于数据调用接口，获取关联***反馈的与业务标识相对应的流程进度数据，将流程进度数据确定为业务标识对应的后台数据。
其中，流程进度数据是用于反映业务标识对应的业务流程执行进度的数据，可以理解为关联***对业务流程执行过程中形成的***日志进行分析处理后形成的反映处理进度和异常等情况的数据。
作为一示例，若数据调用接口对应的数据来源为关联***，则说明业务流程不在本地***上执行，只是通过本地***进行动态可视化监听业务流程对应的进度和异常等情况，此时，可通过数据调用接口，获取关联***反馈的与业务标识相对应的流程进度数据，将流程进度数据确定为业务标识对应的后台数据，使得本地***具有数据轻量化，且耦合性能良好的优点。
本实施例所提供的流程可视化监控方法中，数据调用接口对应的数据来源包括本地***和关联***，实现数据来源的多样性，提高流程可视化监控的适用性；在数据来源为本地***时，将***日志确定为后台数据；在数据来源为关联***时，将流程进度数据确定为后台数据，使得本地***具有数据轻量化和耦合性能良好的优点。
在一实施例中，如图5所示，步骤S204中的采用节点事件***对后台数据进行处理，基于处理结果实时更新目标可视化流程图中流程节点的节点状态，包括：
S504：若后台数据为***日志，则采用当前流程节点对应的节点事件***对***日志进行处理，获取当前流程节点对应的当前节点进度，基于当前流程节点对应的当前节点进度实时更新目标可视化流程图中流程节点的节点状态。
作为一示例，在数据调用接口获取的后台数据为***日志时，说明业务流程的执行和流程可视化监控均在本地***上执行，因此，服务器可根据***当前时间对应的目标可视化流程图，可快速确定其当前流程节点，该当前流程节点为业务流程当前执行的流程节点。接着，服务器可调用当前流程节点对应的节点事件***对***日志进行处理，以确定当 前流程节点对应的当前节点进度，该当前节点进度是用于反映当前流程节点对应的处理进度。最后，服务器可根据当前流程节点对应的当前节点进度实时更新目标可视化流程图中流程节点的节点状态，具体是指根据当前流程节点对应的当前节点进度，确定当前流程节点对应的节点状态，将目标可视化流程图当前流程节点对应的节点颜色更新为与节点状态相对应的节点颜色，以使流程节点的节点状态可动态直观显示在目标可视化流程图中，从而实现对本地***执行的业务流程进行动态可视化监控。
S505：若后台数据为流程进度数据，则根据流程进度数据确定当前流程节点和当前流程节点对应的当前节点进度，基于当前流程节点对应的当前节点进度实时更新目标可视化流程图中流程节点的节点状态。
作为一示例，在数据调用接口获取的后台数据为关联***反馈的流程进度数据时，说明业务流程在关联***上执行，而流程可视化监控在应用***上执行，该流程进度数据为关联***对业务流程执行过程中形成的***日志进行分析处理后形成的反映处理进度和异常等情况的数据。因此，服务器在流程可视化监控时，所获取的关联***反馈的流程进度数据包含当前流程节点(即业务流程当前执行的流程节点)以及其对应的当前节点进度。接着，服务器可根据当前流程节点对应的当前节点进度实时更新目标可视化流程图中流程节点的节点状态，具体是指根据当前流程节点对应的当前节点进度，确定当前流程节点对应的节点状态，将目标可视化流程图中当前流程节点对应的节点颜色更新为与节点状态相对应的节点颜色，以使流程节点的节点状态可动态直观显示在目标可视化流程图中，从而实现对关联***执行的业务流程进行动态可视化监控。
本实施例所提供的流程可视化监控方法中，在后台数据为***日志和流程进度数据时，采用不同处理逻辑对分别对***日志和流程进度数据进行处理，以确定当前流程节点对应的当前节点进度，以便根据当前节点进度实时更新目标可视化流程图中流程节点的节点状态，以实现对业务流程的当前流程节点进行动态可视化监控，保证监控的全面性。
在一实施例中，如图6所示，步骤S504和步骤S505中，基于当前流程节点对应的当前节点进度实时更新目标可视化流程图中流程节点的节点状态，包括：
S601：若当前流程节点对应的当前节点进度为执行成功，则基于当前节点进度更新目标可视化流程图中当前流程节点的节点状态，并更新依赖当前流程节点的后序流程节点的节点状态。
其中，后序流程节点是指依赖于当前流程节点的流程节点，即在当前流程节点之后需要执行的一个或者多个并列进行的流程节点。
作为一示例，若当前流程节点对应的当前节点进度为执行成功时，服务器需基于当前节点进度更新目标可视化流程图中当前流程节点的节点状态为执行成功状态，即将当前流程节点的节点颜色更新为与执行成功状态相对应的节点颜色；并更新依赖当前流程节点的后序流程节点的节点状态为执行中状态，即将后序流程节点的节点颜色更新为执行中状态，以便下一次动态可视化监控时，将该执行中状态的后序流程节点确定为当前流程节点进行监控。可以理解地，由于业务流程是由多个流程节点依据执行顺序形成的处理流程，每一当前流程节点在执行成功时，需判断业务流程中是否存在依赖该当前流程节点的后序流程节点，若存在，需同时将依赖当前流程节点的后序流程节点的节点状态更新为执行中状态，以达到动态可视化监听的目的。
S602：若当前流程节点对应的当前节点进度不为执行成功，则基于当前节点进度更新目标可视化流程图中当前流程节点的节点状态。
作为一示例，若当前流程节点对应的当前节点进度不为执行成功时，说明业务流程还处于当前流程节点的处理期限内，不会跳转到依赖当前流程节点的后序流程节点，因此，服务器只需基于当前流程节点对应的当前节点进度实时更新目标可视化流程图中当前流程节点的节点状态，即将当前流程节点对应的节点颜色更新为与当前节点进度对应的节点 状态的节点颜色，实现对当前流程节点的动态可视化监控。
本实施例所提供的流程可视化监控方法中，在当前流程节点对应的当前节点进度为执行成功时，需同时更新目标可视化流程图中当前流程节点和后序流程节点的节点状态，在当前流程节点对应的当前节点进度不为执行成功时，只需基于当前节点进度更新目标可视化流程图中当前流程节点的节点状态，以实现动态可视化监听的目的，以实现对企业开发或者医疗平台开发的应用***的全面高效监控业务流程的执行。
在一实施例中，如图7所示，步骤S504中，采用当前流程节点对应的节点事件***对***日志进行处理，获取当前流程节点对应的当前节点进度，包括：
S701：采用当前流程节点对应的节点事件***对***日志进行处理，判断***日志是否包含当前流程节点对应的节点日志。
作为一示例，服务器可采用当前流程节点对应的节点事件***对***日志进行扫描，判断***日志是否包含当前流程节点对应的节点日志，以反映当前流程节点是否被执行。该节点日志为当前流程节点在执行过程中形成的日志。
S702：若***日志中未包含当前流程节点对应的节点日志，则当前流程节点对应的当前节点进度为执行中。
作为一示例，服务器在***日志中未包含当前流程节点对应的节点日志，说明目标可视化流程图中当前流程节点对应的节点状态为执行中状态，且从当前流程节点的节点状态为执行中状态之后至***当前时间，用户未执行该当前流程节点，此时，将当前流程节点对应的当前节点进度默认设置为执行中，维持目标可视化流程图中当前流程节点的节点状态为执行中状态。
例如，目标可视化流程图中每一流程节点对应的节点事件***是基于触发条件、处理期限和进度标识等节点属性信息形成，若任一当前流程节点的触发条件为其前序流程节点执行成功，即在前序流程节点执行成功时，自动触发依赖该前序流程节点的当前流程节点的节点状态为执行中状态，从节点状态变更为执行中状态时起之后的处理期限内，对当前流程节点进行实时动态监控。
S703：若***日志中包含当前流程节点对应的节点日志，则依据节点日志中的进度标识，确定当前流程节点对应的当前节点进度。
作为一示例，服务器在***日志中包含当前流程节点对应的节点日志时，说明从当前流程节点的节点状态为执行中状态之后至***当前时间，用户执行该当前流程节点，此时，可从***日志中提取与当前流程节点相对应的节点日志，根据节点日志中记录的进度标识，确定当前流程节点对应的当前节点进度，可实现对当前流程节点进行实时动态监控。该进度标识包括但不限于执行中标识、执行成功标识、执行失败标识、执行超时标识和执行异常标识。
本实施例所提供的流程可视化监控方法中，在***日志未包含当前流程节点对应的节点日志时，将其当前节点进度默认设置为执行中；在***日志中包含当前流程节点对应的节点日志时，根据节点日志中记录的进度标识自动确定其对应的当前节点进度，以实现全面高效地监控业务流程的执行。
应理解，上述实施例中各步骤的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
在一实施例中，提供一种流程可视化监控装置，该流程可视化监控装置与上述实施例中流程可视化监控方法一一对应。如图8所示，该流程可视化监控装置包括监控任务获取模块801、初始图获取模块802、目标图获取模块803和实时监控模块804。各功能模块详细说明如下：
监控任务获取模块801，用于获取可视化监控任务，可视化监控任务包括业务标识和流程关系映射表，流程关系映射表包括N个流程节点、节点间依赖关系和节点属性信息。
初始图获取模块802，用于调用标准流程服务接口，对N个流程节点和节点间依赖关系进行处理，获取初始可视化流程图。
目标图获取模块803，用于基于流程节点对应的节点属性信息形成节点事件***，将节点事件***嵌入到初始可视化流程图中的流程节点上，获取目标可视化流程图。
实时监控模块804，用于获取与业务标识相对应的后台数据，采用节点事件***对后台数据进行处理，基于处理结果实时更新目标可视化流程图中流程节点的节点状态。
优选地，初始图获取模块802，包括：
接口调用单元，用于获取接口调用请求，接口调用请求包括流程图生成模式。
模板生成单元，用于若流程图生成模式为模板模式，则调用固定流程服务接口中的配置可视化模板，对N个流程节点和节点间依赖关系进行处理，获取初始可视化流程图。
动态生成单元，用于若流程图生成模式为动态模式，则调用动态流程服务接口中的流程图生成算法，对N个流程节点和节点间依赖关系进行处理，获取初始可视化流程图。
优选地，动态生成单元包括：
节点定位子单元，用于调用动态流程服务接口中的流程图生成算法对应的节点定位逻辑，对N个流程节点和节点间依赖关系进行处理，确定N个流程节点在动态画板上的节点位置。
流程绘制子单元，用于调用动态流程服务接口中的流程图生成算法对应的节点绘制逻辑，依据节点间依赖关系和N个流程节点在动态画板上的节点位置，在动态画板上绘制N个流程节点对应的流程图标和流程连线，获取初始可视化流程图。
优选地，实时监控模块804包括：
数据来源确定单元，用于基于业务标识对应的数据调用接口，确定数据调用接口对应的数据来源。
***日志获取单元，用于若数据调用接口对应的数据来源为本地***，则基于数据调用接口，获取与业务标识相对应的***日志，将***日志确定为业务标识对应的后台数据。
进度数据获取单元，用于若数据调用接口对应的数据来源为关联***，则基于数据调用接口，获取关联***反馈的与业务标识相对应的流程进度数据，将流程进度数据确定为业务标识对应的后台数据。
优选地，实时监控模块804包括：
日志监控单元，用于若后台数据为***日志，则采用当前流程节点对应的节点事件***对***日志进行处理，获取当前流程节点对应的当前节点进度，基于当前流程节点对应的当前节点进度实时更新目标可视化流程图中流程节点的节点状态。
进度监控单元，用于若后台数据为流程进度数据，则根据流程进度数据确定当前流程节点和当前流程节点对应的当前节点进度，基于当前流程节点对应的当前节点进度实时更新目标可视化流程图中流程节点的节点状态。
优选地，实时监控模块804包括：
同时更新单元，用于若当前流程节点对应的当前节点进度为执行成功，则基于当前节点进度更新目标可视化流程图中当前流程节点的节点状态，并更新依赖当前流程节点的后序流程节点的节点状态。
单独更新单元，用于若当前流程节点对应的当前节点进度不为执行成功，则基于当前节点进度更新目标可视化流程图中当前流程节点的节点状态。
优选地，日志监控单元包括：
节点日志判断子单元，用于采用当前流程节点对应的节点事件***对***日志进行处理，判断***日志是否包含当前流程节点对应的节点日志。
第一进度确定子单元，用于若***日志中未包含当前流程节点对应的节点日志，则当前流程节点对应的当前节点进度为执行中。
第二进度确定子单元，用于若***日志中包含当前流程节点对应的节点日志，则依据节点日志中的进度标识，确定当前流程节点对应的当前节点进度。
关于流程可视化监控装置的具体限定可以参见上文中对于流程可视化监控方法的限定，在此不再赘述。上述流程可视化监控装置中的各个模块可全部或部分通过软件、硬件及其组合来实现。上述各模块可以硬件形式内嵌于或独立于计算机设备中的处理器中，也可以以软件形式存储于计算机设备中的存储器中，以便于处理器调用执行以上各个模块对应的操作。
在一个实施例中，提供了一种计算机设备，该计算机设备可以是服务器，其内部结构图可以如图9所示。该计算机设备包括通过***总线连接的处理器、存储器、网络接口和数据库。其中，该计算机设备的处理器用于提供计算和控制能力。该计算机设备的存储器包括非易失性存储介质、内存储器。该非易失性存储介质存储有操作***、计算机可读指令和数据库。该内存储器为非易失性存储介质中的操作***和计算机可读指令的运行提供环境。该计算机设备的数据库用于存储执行流程可视化监控方法过程中采用或者生成的数据。该计算机设备的网络接口用于与外部的终端通过网络连接通信。该计算机可读指令被处理器执行时以实现一种流程可视化监控方法。
在一个实施例中，提供了一种计算机设备，包括存储器、处理器及存储在存储器上并可在处理器上运行的计算机可读指令，处理器执行计算机可读指令时实现上述实施例中流程可视化监控方法，例如图2所示S201-S204，或者图3至图7中所示，为避免重复，这里不再赘述。或者，处理器执行计算机可读指令时实现流程可视化监控装置这一实施例中的各模块/单元的功能，例如图8所示的监控任务获取模块801、初始图获取模块802、目标图获取模块803和实时监控模块804的功能，为避免重复，这里不再赘述。
在一实施例中，提供提供一个或多个存储有计算机可读指令的可读存储介质，所述计算机可读存储介质存储有计算机可读指令，所述计算机可读指令被一个或多个处理器执行时，使得所述一个或多个处理器执行计算机可读指令时实现上述实施例中流程可视化监控方法，例如图2所示S201-S204，或者图3至图7中所示，为避免重复，这里不再赘述。或者，该计算机可读指令被处理器执行时实现上述流程可视化监控装置这一实施例中的各模块/单元的功能，例如图8所示的监控任务获取模块801、初始图获取模块802、目标图获取模块803和实时监控模块804的功能，为避免重复，这里不再赘述。本实施例中的可读存储介质包括非易失性可读存储介质和易失性可读存储介质。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分流程，是可以通过计算机可读指令来指令相关的硬件来完成，该计算机可读指令可存储于一非易失性可读存储介质也可以存储在易失性可读存储介质中，该计算机可读指令在执行时，可包括如上述各方法的实施例的流程。其中，本申请所提供的各实施例中所使用的对存储器、存储、数据库或其它介质的任何引用，均可包括非易失性和/或易失性存储器。非易失性存储器可包括只读存储器(ROM)、可编程ROM(PROM)、电可编程ROM(EPROM)、电可擦除可编程ROM(EEPROM)或闪存。易失性存储器可包括随机存取存储器(RAM)或者外部高速缓冲存储器。作为说明而非局限，RAM以多种形式可得，诸如静态RAM(SRAM)、动态RAM(DRAM)、同步DRAM(SDRAM)、双数据率SDRAM(DDRSDRAM)、增强型SDRAM(ESDRAM)、同步链路(Synchlink)DRAM(SLDRAM)、存储器总线(Rambus)直接RAM(RDRAM)、直接存储器总线动态RAM(DRDRAM)、以及存储器总线动态RAM(RDRAM)等。
所属领域的技术人员可以清楚地了解到，为了描述的方便和简洁，仅以上述各功能单元、模块的划分进行举例说明，实际应用中，可以根据需要而将上述功能分配由不同的功能单元、模块完成，即将所述装置的内部结构划分成不同的功能单元或模块，以完成以上描述的全部或者部分功能。
以上实施例仅用以说明本申请的技术方案，而非对其限制。尽管参照前述实施例对本 申请进行了详细的说明，本领域的普通技术人员应当理解：其依然可以对前述各实施例所记载的技术方案进行修改，或者对其中部分技术特征进行等同替换；而这些修改或者替换，并不使相应技术方案的本质脱离本申请各实施例技术方案的精神和范围，均应包含在本申请的保护范围之内。

Claims (20)

  1. 一种流程可视化监控方法，其中，包括：
    获取可视化监控任务，所述可视化监控任务包括业务标识和流程关系映射表，所述流程关系映射表包括N个流程节点、节点间依赖关系和节点属性信息；
    调用标准流程服务接口，对N个所述流程节点和所述节点间依赖关系进行处理，获取初始可视化流程图；
    基于所述流程节点对应的节点属性信息形成节点事件***，将所述节点事件***嵌入到所述初始可视化流程图中的流程节点上，获取目标可视化流程图；
    获取与所述业务标识相对应的后台数据，采用所述节点事件***对所述后台数据进行处理，基于处理结果实时更新所述目标可视化流程图中流程节点的节点状态。
  2. 如权利要求1所述的流程可视化监控方法，其中，所述调用标准流程服务接口，对N个所述流程节点和所述节点间依赖关系进行处理，获取初始可视化流程图，包括：
    获取接口调用请求，所述接口调用请求包括流程图生成模式；
    若所述流程图生成模式为模板模式，则调用固定流程服务接口中的配置可视化模板，对N个所述流程节点和所述节点间依赖关系进行处理，获取初始可视化流程图；
    若所述流程图生成模式为动态模式，则调用动态流程服务接口中的流程图生成算法，对N个所述流程节点和所述节点间依赖关系进行处理，获取初始可视化流程图。
  3. 如权利要求2所述的流程可视化监控方法，其中，所述调用动态流程服务接口中的流程图生成算法，对N个所述流程节点和所述节点间依赖关系进行处理，获取初始可视化流程图，包括：
    调用动态流程服务接口中的流程图生成算法对应的节点定位逻辑，对N个所述流程节点和所述节点间依赖关系进行处理，确定N个所述流程节点在动态画板上的节点位置；
    调用动态流程服务接口中的流程图生成算法对应的节点绘制逻辑，依据所述节点间依赖关系和N个所述流程节点在动态画板上的节点位置，在所述动态画板上绘制N个流程节点对应的流程图标和流程连线，获取初始可视化流程图。
  4. 如权利要求1所述的流程可视化监控方法，其中，所述获取与所述业务标识相对应的后台数据，包括：
    基于所述业务标识对应的数据调用接口，确定所述数据调用接口对应的数据来源；
    若所述数据调用接口对应的数据来源为本地***，则基于所述数据调用接口，获取与所述业务标识相对应的***日志，将所述***日志确定为所述业务标识对应的后台数据；
    若所述数据调用接口对应的数据来源为关联***，则基于所述数据调用接口，获取所述关联***反馈的与所述业务标识相对应的流程进度数据，将所述流程进度数据确定为所述业务标识对应的后台数据。
  5. 如权利要求4所述的流程可视化监控方法，其中，所述采用所述节点事件***对所述后台数据进行处理，基于处理结果实时更新所述目标可视化流程图中流程节点的节点状态，包括：
    若所述后台数据为***日志，则采用当前流程节点对应的节点事件***对所述***日志进行处理，获取所述当前流程节点对应的当前节点进度，基于所述当前流程节点对应的当前节点进度实时更新所述目标可视化流程图中流程节点的节点状态；
    若所述后台数据为流程进度数据，则根据所述流程进度数据确定当前流程节点和所述当前流程节点对应的当前节点进度，基于所述当前流程节点对应的当前节点进度实时更新所述目标可视化流程图中流程节点的节点状态。
  6. 如权利要求5所述的流程可视化监控方法，其中，所述基于所述当前流程节点对应的当前节点进度实时更新所述目标可视化流程图中流程节点的节点状态，包括：
    若所述当前流程节点对应的当前节点进度为执行成功，则基于所述当前节点进度更新所述目标可视化流程图中当前流程节点的节点状态，并更新依赖所述当前流程节点的后序流程节点的节点状态；
    若所述当前流程节点对应的当前节点进度不为执行成功，则基于所述当前节点进度更新所述目标可视化流程图中当前流程节点的节点状态。
  7. 如权利要求5所述的流程可视化监控方法，其中，所述采用当前流程节点对应的节点事件***对所述***日志进行处理，获取所述当前流程节点对应的当前节点进度，包括：
    采用当前流程节点对应的节点事件***对所述***日志进行处理，判断所述***日志是否包含所述当前流程节点对应的节点日志；
    若所述***日志中未包含所述当前流程节点对应的节点日志，则所述当前流程节点对应的当前节点进度为执行中；
    若所述***日志中包含所述当前流程节点对应的节点日志，则依据所述节点日志中的进度标识，确定所述当前流程节点对应的当前节点进度。
  8. 一种流程可视化监控装置，其中，包括：
    监控任务获取模块，用于获取可视化监控任务，所述可视化监控任务包括业务标识和流程关系映射表，所述流程关系映射表包括N个流程节点、节点间依赖关系和节点属性信息；
    初始图获取模块，用于调用标准流程服务接口，对N个所述流程节点和所述节点间依赖关系进行处理，获取初始可视化流程图；
    目标图获取模块，用于基于所述流程节点对应的节点属性信息形成节点事件***，将所述节点事件***嵌入到所述初始可视化流程图中的流程节点上，获取目标可视化流程图；
    实时监控模块，用于获取与所述业务标识相对应的后台数据，采用所述节点事件***对所述后台数据进行处理，基于处理结果实时更新所述目标可视化流程图中流程节点的节点状态。
  9. 一种计算机设备，包括存储器、处理器以及存储在所述存储器中并可在所述处理器上运行的计算机可读指令，其中，所述处理器执行所述计算机可读指令时实现下步骤：
    获取可视化监控任务，所述可视化监控任务包括业务标识和流程关系映射表，所述流程关系映射表包括N个流程节点、节点间依赖关系和节点属性信息；
    调用标准流程服务接口，对N个所述流程节点和所述节点间依赖关系进行处理，获取初始可视化流程图；
    基于所述流程节点对应的节点属性信息形成节点事件***，将所述节点事件***嵌入到所述初始可视化流程图中的流程节点上，获取目标可视化流程图；
    获取与所述业务标识相对应的后台数据，采用所述节点事件***对所述后台数据进行处理，基于处理结果实时更新所述目标可视化流程图中流程节点的节点状态。
  10. 如权利要求9所述的计算机设备，其中，所述调用标准流程服务接口，对N个所述流程节点和所述节点间依赖关系进行处理，获取初始可视化流程图，包括：
    获取接口调用请求，所述接口调用请求包括流程图生成模式；
    若所述流程图生成模式为模板模式，则调用固定流程服务接口中的配置可视化模板，对N个所述流程节点和所述节点间依赖关系进行处理，获取初始可视化流程图；
    若所述流程图生成模式为动态模式，则调用动态流程服务接口中的流程图生成算法，对N个所述流程节点和所述节点间依赖关系进行处理，获取初始可视化流程图。
  11. 如权利要求10所述的计算机设备，其中，所述调用动态流程服务接口中的流程图生成算法，对N个所述流程节点和所述节点间依赖关系进行处理，获取初始可视化流程图， 包括：
    调用动态流程服务接口中的流程图生成算法对应的节点定位逻辑，对N个所述流程节点和所述节点间依赖关系进行处理，确定N个所述流程节点在动态画板上的节点位置；
    调用动态流程服务接口中的流程图生成算法对应的节点绘制逻辑，依据所述节点间依赖关系和N个所述流程节点在动态画板上的节点位置，在所述动态画板上绘制N个流程节点对应的流程图标和流程连线，获取初始可视化流程图。
  12. 如权利要求9所述的计算机设备，其中，所述获取与所述业务标识相对应的后台数据，包括：
    基于所述业务标识对应的数据调用接口，确定所述数据调用接口对应的数据来源；
    若所述数据调用接口对应的数据来源为本地***，则基于所述数据调用接口，获取与所述业务标识相对应的***日志，将所述***日志确定为所述业务标识对应的后台数据；
    若所述数据调用接口对应的数据来源为关联***，则基于所述数据调用接口，获取所述关联***反馈的与所述业务标识相对应的流程进度数据，将所述流程进度数据确定为所述业务标识对应的后台数据。
  13. 如权利要求12所述的计算机设备，其中，所述采用所述节点事件***对所述后台数据进行处理，基于处理结果实时更新所述目标可视化流程图中流程节点的节点状态，包括：
    若所述后台数据为***日志，则采用当前流程节点对应的节点事件***对所述***日志进行处理，获取所述当前流程节点对应的当前节点进度，基于所述当前流程节点对应的当前节点进度实时更新所述目标可视化流程图中流程节点的节点状态；
    若所述后台数据为流程进度数据，则根据所述流程进度数据确定当前流程节点和所述当前流程节点对应的当前节点进度，基于所述当前流程节点对应的当前节点进度实时更新所述目标可视化流程图中流程节点的节点状态。
  14. 如权利要求13所述的计算机设备，其中，所述基于所述当前流程节点对应的当前节点进度实时更新所述目标可视化流程图中流程节点的节点状态，包括：
    若所述当前流程节点对应的当前节点进度为执行成功，则基于所述当前节点进度更新所述目标可视化流程图中当前流程节点的节点状态，并更新依赖所述当前流程节点的后序流程节点的节点状态；
    若所述当前流程节点对应的当前节点进度不为执行成功，则基于所述当前节点进度更新所述目标可视化流程图中当前流程节点的节点状态。
  15. 一个或多个存储有计算机可读指令的可读存储介质，所述计算机可读存储介质存储有计算机可读指令，其中，所述计算机可读指令被一个或多个处理器执行时，使得所述一个或多个处理器执行如下步骤：
    获取可视化监控任务，所述可视化监控任务包括业务标识和流程关系映射表，所述流程关系映射表包括N个流程节点、节点间依赖关系和节点属性信息；
    调用标准流程服务接口，对N个所述流程节点和所述节点间依赖关系进行处理，获取初始可视化流程图；
    基于所述流程节点对应的节点属性信息形成节点事件***，将所述节点事件***嵌入到所述初始可视化流程图中的流程节点上，获取目标可视化流程图；
    获取与所述业务标识相对应的后台数据，采用所述节点事件***对所述后台数据进行处理，基于处理结果实时更新所述目标可视化流程图中流程节点的节点状态。
  16. 如权利要求15所述的可读存储介质，其中，所述调用标准流程服务接口，对N个所述流程节点和所述节点间依赖关系进行处理，获取初始可视化流程图，包括：
    获取接口调用请求，所述接口调用请求包括流程图生成模式；
    若所述流程图生成模式为模板模式，则调用固定流程服务接口中的配置可视化模板， 对N个所述流程节点和所述节点间依赖关系进行处理，获取初始可视化流程图；
    若所述流程图生成模式为动态模式，则调用动态流程服务接口中的流程图生成算法，对N个所述流程节点和所述节点间依赖关系进行处理，获取初始可视化流程图。
  17. 如权利要求16所述的可读存储介质，其中，所述调用动态流程服务接口中的流程图生成算法，对N个所述流程节点和所述节点间依赖关系进行处理，获取初始可视化流程图，包括：
    调用动态流程服务接口中的流程图生成算法对应的节点定位逻辑，对N个所述流程节点和所述节点间依赖关系进行处理，确定N个所述流程节点在动态画板上的节点位置；
    调用动态流程服务接口中的流程图生成算法对应的节点绘制逻辑，依据所述节点间依赖关系和N个所述流程节点在动态画板上的节点位置，在所述动态画板上绘制N个流程节点对应的流程图标和流程连线，获取初始可视化流程图。
  18. 如权利要求15所述的可读存储介质，其中，所述获取与所述业务标识相对应的后台数据，包括：
    基于所述业务标识对应的数据调用接口，确定所述数据调用接口对应的数据来源；
    若所述数据调用接口对应的数据来源为本地***，则基于所述数据调用接口，获取与所述业务标识相对应的***日志，将所述***日志确定为所述业务标识对应的后台数据；
    若所述数据调用接口对应的数据来源为关联***，则基于所述数据调用接口，获取所述关联***反馈的与所述业务标识相对应的流程进度数据，将所述流程进度数据确定为所述业务标识对应的后台数据。
  19. 如权利要求18所述的可读存储介质，其中，所述采用所述节点事件***对所述后台数据进行处理，基于处理结果实时更新所述目标可视化流程图中流程节点的节点状态，包括：
    若所述后台数据为***日志，则采用当前流程节点对应的节点事件***对所述***日志进行处理，获取所述当前流程节点对应的当前节点进度，基于所述当前流程节点对应的当前节点进度实时更新所述目标可视化流程图中流程节点的节点状态；
    若所述后台数据为流程进度数据，则根据所述流程进度数据确定当前流程节点和所述当前流程节点对应的当前节点进度，基于所述当前流程节点对应的当前节点进度实时更新所述目标可视化流程图中流程节点的节点状态。
  20. 如权利要求19所述的可读存储介质，其中，所述基于所述当前流程节点对应的当前节点进度实时更新所述目标可视化流程图中流程节点的节点状态，包括：
    若所述当前流程节点对应的当前节点进度为执行成功，则基于所述当前节点进度更新所述目标可视化流程图中当前流程节点的节点状态，并更新依赖所述当前流程节点的后序流程节点的节点状态；
    若所述当前流程节点对应的当前节点进度不为执行成功，则基于所述当前节点进度更新所述目标可视化流程图中当前流程节点的节点状态。
PCT/CN2021/090307 2020-09-30 2021-04-27 流程可视化监控方法、装置、计算机设备及存储介质 WO2022068189A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202011063771.7A CN112181397B (zh) 2020-09-30 2020-09-30 流程可视化监控方法、装置、计算机设备及存储介质
CN202011063771.7 2020-09-30

Publications (1)

Publication Number Publication Date
WO2022068189A1 true WO2022068189A1 (zh) 2022-04-07

Family

ID=73948450

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/090307 WO2022068189A1 (zh) 2020-09-30 2021-04-27 流程可视化监控方法、装置、计算机设备及存储介质

Country Status (2)

Country Link
CN (1) CN112181397B (zh)
WO (1) WO2022068189A1 (zh)

Cited By (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115150459A (zh) * 2022-06-30 2022-10-04 苏州浪潮智能科技有限公司 一种管理统一存储设备集群控制器节点的方法及***
CN116048490A (zh) * 2023-01-28 2023-05-02 广州钛动科技股份有限公司 业务事件处理方法、装置、计算机设备和存储介质
CN116071028A (zh) * 2023-03-07 2023-05-05 徐工汉云技术股份有限公司 设备监控流程图生成方法、装置、电子设备和存储介质
CN116449809A (zh) * 2023-06-16 2023-07-18 成都瀚辰光翼生物工程有限公司 一种故障处理方法、装置、电子设备及存储介质
CN116628351A (zh) * 2023-07-26 2023-08-22 安徽思高智能科技有限公司 基于节点依赖的流程图分支推荐方法、设备及存储设备
CN116680064A (zh) * 2023-08-03 2023-09-01 中航信移动科技有限公司 一种任务节点的管理方法、电子设备及存储介质
CN116700938A (zh) * 2023-08-07 2023-09-05 凯美瑞德（苏州）信息科技股份有限公司 一种交易审批业务的流程处理方法、电子设备及存储介质
CN116756233A (zh) * 2023-08-23 2023-09-15 博智安全科技股份有限公司 一种态势数据处理方法、装置、电子设备及存储介质
CN116882724A (zh) * 2023-07-13 2023-10-13 北京优特捷信息技术有限公司 一种业务流程优化方案的生成方法、装置、设备及介质
CN117411929A (zh) * 2023-12-14 2024-01-16 卓望数码技术（深圳）有限公司 业务流程监控方法、装置、设备及存储介质
CN117455419A (zh) * 2023-12-22 2024-01-26 江西五十铃汽车有限公司 一种整车项目管理方法及***

Families Citing this family (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112181397B (zh) * 2020-09-30 2023-10-13 平安科技（深圳）有限公司 流程可视化监控方法、装置、计算机设备及存储介质
CN113760641A (zh) * 2021-01-08 2021-12-07 北京沃东天骏信息技术有限公司 业务监控方法、装置、计算机***和计算机可读存储介质
CN112884427A (zh) * 2021-01-13 2021-06-01 中国建设银行股份有限公司 一种支持多服务来源的流程管理方法及装置
CN113283730B (zh) * 2021-05-17 2024-07-02 鲁班(北京)电子商务科技有限公司 一种通用的审批流程应用方法及装置
CN113221570A (zh) * 2021-05-31 2021-08-06 康键信息技术（深圳）有限公司 基于线上问诊信息的处理方法、装置、设备及存储介质
CN113312409B (zh) * 2021-06-07 2024-06-28 平安证券股份有限公司 任务监控方法、装置、电子设备及计算机可读存储介质
CN115526578A (zh) * 2021-11-26 2022-12-27 北京字跳网络技术有限公司 生成项目流的方法、装置、电子设备及存储介质
CN114706610A (zh) * 2022-03-30 2022-07-05 苏州峰之鼎信息科技有限公司 一种业务流程图生成方法、装置、设备及存储介质
CN115525796A (zh) * 2022-05-17 2022-12-27 北京字跳网络技术有限公司 视图生成方法、装置、电子设备及存储介质
CN115525371A (zh) * 2022-05-20 2022-12-27 北京字跳网络技术有限公司 图像语义对齐方法、装置、电子设备及存储介质
CN116307658A (zh) * 2023-01-10 2023-06-23 广东远景信息科技有限公司 应急流程管理方法、***、电子设备及存储介质
CN116755680A (zh) * 2023-08-17 2023-09-15 北京凯锐远景科技有限公司 一种可视化流程编辑方法、装置、存储介质及电子设备
CN117149887A (zh) * 2023-11-01 2023-12-01 建信金融科技有限责任公司 一种异常处理方法、装置、电子设备及计算机可读介质

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103617486A (zh) * 2013-11-21 2014-03-05 中国电子科技集团公司第十五研究所 一种复杂业务流程动态图形化监控的方法与***
US20140096058A1 (en) * 2012-09-28 2014-04-03 Oracle International Corporation Interactive topological views of combined hardware and software systems
CN104423960A (zh) * 2013-09-10 2015-03-18 阿里巴巴集团控股有限公司 一种项目持续集成的方法及***
CN109254901A (zh) * 2018-09-30 2019-01-22 北京九章云极科技有限公司 一种指标监测方法及***
CN111355802A (zh) * 2020-03-03 2020-06-30 中国邮政储蓄银行股份有限公司 信息推送方法和装置
CN111506359A (zh) * 2020-03-26 2020-08-07 平安普惠企业管理有限公司 可视化的业务配置方法、装置、设备及存储介质
CN112181397A (zh) * 2020-09-30 2021-01-05 平安科技（深圳）有限公司 流程可视化监控方法、装置、计算机设备及存储介质

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP5003084B2 (ja) * 2006-09-28 2012-08-15 日本電気株式会社 業務監視装置、業務監視システム、業務監視方法およびプログラム
CN103186834A (zh) * 2011-12-31 2013-07-03 阿里巴巴集团控股有限公司 业务流程配置方法和装置
CN107886242A (zh) * 2017-11-10 2018-04-06 平安科技（深圳）有限公司 数据监控方法、装置、计算机设备及存储介质
CN108897854B (zh) * 2018-06-29 2020-06-05 京东数字科技控股有限公司 一种超时任务的监控方法和装置
CN110599114A (zh) * 2019-08-15 2019-12-20 中国平安财产保险股份有限公司 业务流程处理方法、装置、设备及计算机可读存储介质
CN110852623A (zh) * 2019-11-12 2020-02-28 北京计算机技术及应用研究所 一种基于bpmn的指挥控制流程设计方法
CN111324629B (zh) * 2020-02-19 2023-08-15 望海康信(北京)科技股份公司 业务数据处理方法、装置、电子设备及计算机存储介质

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140096058A1 (en) * 2012-09-28 2014-04-03 Oracle International Corporation Interactive topological views of combined hardware and software systems
CN104423960A (zh) * 2013-09-10 2015-03-18 阿里巴巴集团控股有限公司 一种项目持续集成的方法及***
CN103617486A (zh) * 2013-11-21 2014-03-05 中国电子科技集团公司第十五研究所 一种复杂业务流程动态图形化监控的方法与***
CN109254901A (zh) * 2018-09-30 2019-01-22 北京九章云极科技有限公司 一种指标监测方法及***
CN111355802A (zh) * 2020-03-03 2020-06-30 中国邮政储蓄银行股份有限公司 信息推送方法和装置
CN111506359A (zh) * 2020-03-26 2020-08-07 平安普惠企业管理有限公司 可视化的业务配置方法、装置、设备及存储介质
CN112181397A (zh) * 2020-09-30 2021-01-05 平安科技（深圳）有限公司 流程可视化监控方法、装置、计算机设备及存储介质

Cited By (20)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115150459A (zh) * 2022-06-30 2022-10-04 苏州浪潮智能科技有限公司 一种管理统一存储设备集群控制器节点的方法及***
CN115150459B (zh) * 2022-06-30 2023-08-04 苏州浪潮智能科技有限公司 一种管理统一存储设备集群控制器节点的方法及***
CN116048490A (zh) * 2023-01-28 2023-05-02 广州钛动科技股份有限公司 业务事件处理方法、装置、计算机设备和存储介质
CN116071028A (zh) * 2023-03-07 2023-05-05 徐工汉云技术股份有限公司 设备监控流程图生成方法、装置、电子设备和存储介质
CN116071028B (zh) * 2023-03-07 2023-06-02 徐工汉云技术股份有限公司 设备监控流程图生成方法、装置、电子设备和存储介质
CN116449809A (zh) * 2023-06-16 2023-07-18 成都瀚辰光翼生物工程有限公司 一种故障处理方法、装置、电子设备及存储介质
CN116449809B (zh) * 2023-06-16 2023-09-05 成都瀚辰光翼生物工程有限公司 一种故障处理方法、装置、电子设备及存储介质
CN116882724B (zh) * 2023-07-13 2024-06-11 北京优特捷信息技术有限公司 一种业务流程优化方案的生成方法、装置、设备及介质
CN116882724A (zh) * 2023-07-13 2023-10-13 北京优特捷信息技术有限公司 一种业务流程优化方案的生成方法、装置、设备及介质
CN116628351A (zh) * 2023-07-26 2023-08-22 安徽思高智能科技有限公司 基于节点依赖的流程图分支推荐方法、设备及存储设备
CN116628351B (zh) * 2023-07-26 2023-10-20 安徽思高智能科技有限公司 基于节点依赖的流程图分支推荐方法、设备及存储设备
CN116680064B (zh) * 2023-08-03 2023-10-10 中航信移动科技有限公司 一种任务节点的管理方法、电子设备及存储介质
CN116680064A (zh) * 2023-08-03 2023-09-01 中航信移动科技有限公司 一种任务节点的管理方法、电子设备及存储介质
CN116700938A (zh) * 2023-08-07 2023-09-05 凯美瑞德（苏州）信息科技股份有限公司 一种交易审批业务的流程处理方法、电子设备及存储介质
CN116700938B (zh) * 2023-08-07 2023-10-27 凯美瑞德（苏州）信息科技股份有限公司 一种交易审批业务的流程处理方法、电子设备及存储介质
CN116756233A (zh) * 2023-08-23 2023-09-15 博智安全科技股份有限公司 一种态势数据处理方法、装置、电子设备及存储介质
CN116756233B (zh) * 2023-08-23 2023-11-07 博智安全科技股份有限公司 一种态势数据处理方法、装置、电子设备及存储介质
CN117411929A (zh) * 2023-12-14 2024-01-16 卓望数码技术（深圳）有限公司 业务流程监控方法、装置、设备及存储介质
CN117411929B (zh) * 2023-12-14 2024-03-15 卓望数码技术（深圳）有限公司 业务流程监控方法、装置、设备及存储介质
CN117455419A (zh) * 2023-12-22 2024-01-26 江西五十铃汽车有限公司 一种整车项目管理方法及***

Also Published As

Publication number Publication date
CN112181397A (zh) 2021-01-05
CN112181397B (zh) 2023-10-13

Similar Documents

Publication Publication Date Title
WO2022068189A1 (zh) 流程可视化监控方法、装置、计算机设备及存储介质
US11089115B2 (en) Discovery of cloud-based infrastructure and resources
JP6377113B2 (ja) Ｇｕｉナビゲーション、プロパティシート、およびオートタブコンプリーションを含むサーバ構成を管理するためのシステムおよび方法
CN109347663B (zh) 一种OpenStack云平台中资源可视化编排方法
US7975001B1 (en) Bi-directional communication in a parallel processing environment
JP2021515293A (ja) ブロックチェーン・ネットワークのインフラストラクチャのサービス・マネジメントのコンピュータ実装方法、システム、コンピュータ・プログラム、およびブロックチェーン・ネットワーク
JP2019534496A (ja) マネージクエリサービス
JP2019522846A (ja) データベースプロビジョニングのためのリソース配分
EP3032442B1 (en) Modeling and simulation of infrastructure architecture for big data
JP6663030B2 (ja) 自律サービス合成のための方法及び装置
US10929567B2 (en) Parallel access to running electronic design automation (EDA) application
US20220232101A1 (en) Virtual workspace experience visualization and optimization
KR101643436B1 (ko) 웹 기반 도표 시각화를 위한 확장성
US20180241644A1 (en) Server performance evaluation through single value server performance index
CN112860247B (zh) 一种模型组件的自定义生成方法、装置、设备及介质
US11620445B2 (en) System and method for implementing an automatic data collection and presentation generator module
US11902103B2 (en) Method and apparatus for creating a custom service
US11838248B2 (en) Managing and executing serverless function command sets in a messaging service
EP3567804B1 (en) Advanced insights explorer
JP2020502598A (ja) 業務システムとマルチアセンブリーとのやりとりを実現する方法、電子装置及び記憶媒体
US10917292B2 (en) Architectural design to enable bidirectional service registration and interaction among clusters
US20200218432A1 (en) Intelligent overflow menu
US20220201091A1 (en) Coordinating requests actioned at a scalable application
US10534626B2 (en) Methods for facilitating self-service automation utilities and devices thereof
US10949441B1 (en) Data center information retrieval system and method of operating the same

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21873852

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21873852

Country of ref document: EP

Kind code of ref document: A1