CN113282444B - Visualization method and device for debugging business process - Google Patents
Visualization method and device for debugging business process Download PDFInfo
- Publication number
- CN113282444B CN113282444B CN202010104780.XA CN202010104780A CN113282444B CN 113282444 B CN113282444 B CN 113282444B CN 202010104780 A CN202010104780 A CN 202010104780A CN 113282444 B CN113282444 B CN 113282444B
- Authority
- CN
- China
- Prior art keywords
- message
- debugging
- sub
- parallel node
- page
- Prior art date
- Legal status (The legal status 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 status listed.)
- Active
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
- G06F11/3017—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system is implementing multitasking
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/32—Monitoring with visual or acoustical indication of the functioning of the machine
- G06F11/323—Visualisation of programs or trace data
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/451—Execution arrangements for user interfaces
Abstract
The invention discloses a visualization method and a visualization device for debugging a business process, and relates to the technical field of computers. The method comprises the following steps: responding to triggering operation of a user, creating a main debugger, and transmitting debugging configuration information of a business process to a debugging engine based on the main debugger; receiving a message returned by the debugging engine in the process of debugging the business process; and after the message is determined to be a first message for indicating the start of executing the parallel node, drawing and displaying a thread call tree in a first area of the page, and drawing and displaying a plurality of sub-flowcharts nested in the same tag page in a second area of the page according to the identification of the parallel node and the information of a plurality of threads for executing the parallel node. Through the steps, the problems that thread management is unclear, a father process cannot be positioned when a multi-thread Cheng Zhihang sub-process exists in the prior art can be solved, and therefore a developer can conveniently and rapidly debug a service process.
Description
Technical Field
The present invention relates to the field of computer technologies, and in particular, to a visualization method and apparatus for debugging a business process.
Background
The service flow is a directed graph which meets the specific service scene and consists of a start node and a series of service function nodes, and comprises the transmission of data flow, and describes the transition of data or state of specific service from start to end. Other business processes are supported and called in the business processes, so that a complex business scene is conveniently split into a plurality of small business processes, and meanwhile, the business processes are also conveniently multiplexed.
Before service online, a local early test is often needed to be performed on the service flow to detect whether the service flow meets service requirements, whether data conversion accords with expectations, and the like. In this process, the debugging functionality provided by the business process debugging system is particularly important. The debugging function can support the user to track the execution process of the business process, check the data change before and after a certain node in the execution business process, help the user to quickly locate the problem when the test result does not accord with the expectation, and the like.
Typically, the execution of a business process is unidirectional, i.e., a thread executes a process. However, some business scenarios require parallel processing of a flow, then merging the results of the parallel processing, and then continuing to execute subsequent flows. In this case, the debugging of the multi-threaded flow is involved. Most of the current business process debugging systems support multi-thread debugging, when a plurality of threads execute nodes in parallel in the same business process, most of the debugging systems show the currently running threads in a level display mode in a thread stack area, and provide thread switching and variable display and modification functions based on the threads.
In the process of implementing the invention, the inventor finds that the existing business process debugging system has at least the following problems in the process of visualization: first, thread management is unclear. Specifically, when debugging is performed on multiple threads, all threads are displayed in a level in a thread stack area, and the calling relationship among the threads cannot be known conveniently. Second, when executing child flows in parallel based on multithreading, it is impossible to locate its parent flow. Specifically, after the process is started, a flowchart is opened to display the execution process of the process; when the sub-flow call node is executed, the flow chart of the called sub-flow is opened again so as to display the execution process of the sub-flow; and when the sub-flow call node is in the parallel mode, a plurality of identical sub-flow charts are opened at the same time. Furthermore, when the current debugging is suspended in a certain sub-flow, it cannot be determined which flow the sub-flow is called by, and great inconvenience is brought to the debugging work of the business flow.
Disclosure of Invention
In view of this, the invention provides a visualization method and a device for debugging a business process, which can solve the problems that the existing visualization method for debugging a business process is unclear in thread management, a father process of the multi-thread Cheng Zhihang sub-process cannot be positioned, and the like, and is convenient for developers to quickly and conveniently debug the business process.
To achieve the above object, according to one aspect of the present invention, a visualization method for business process debugging is provided.
The visual method for user business process debugging comprises the following steps: responding to triggering operation of a user, creating a main debugger, and transmitting debugging configuration information of a business process to a debugging engine based on the main debugger so that the debugging engine can debug the business process according to the debugging configuration information; receiving a message returned by the debugging engine in the process of debugging the business process; after the message is determined to be the first message, drawing a thread call tree in a first area on a page and displaying the thread call tree, and drawing and displaying a plurality of sub-flowcharts nested in the same tag page in a second area on the page according to the identification of the parallel node and the information of a plurality of threads for executing the parallel node; wherein the first message is used for indicating that the parallel node starts to execute.
Optionally, the step of drawing the thread call tree in the first area on the page and displaying includes: after receiving a second message returned by the debug engine, creating a plurality of sub-debuggers of the current debugger according to the second message, and adding information of the plurality of sub-debuggers into a sub-debugger list of the current debugger; the second message is used for indicating that a plurality of threads for executing the parallel node are started, and the plurality of sub debuggers are in one-to-one correspondence with the plurality of threads for executing the parallel node; then, the thread call tree is drawn and displayed in a first area on the page according to the sub-debugger list of the current debugger.
Optionally, the step of drawing and displaying a plurality of sub-flowcharts nested in the same tag page in the second area on the page according to the identification of the parallel node and the information of the plurality of threads for executing the parallel node includes: creating a label page named by the parallel node in a second area of the page according to the identification of the parallel node carried by the first message, and then drawing and displaying a plurality of sub-flowcharts in the label page according to the information of a plurality of threads for executing the parallel node carried by the second message.
Optionally, the method further comprises: after receiving a third message returned by the debug engine, closing the plurality of sub-debuggers according to the third message, deleting the information of the plurality of sub-debuggers from a sub-debugger list of the current debugger, and updating the thread call tree and the plurality of sub-flowcharts nested in the same tag page; wherein the third message is used for indicating that the parallel node execution is finished.
Optionally, the method further comprises: after the message is determined to be a fourth message, determining a corresponding graph of the non-parallel node in the flow chart according to the flow mark and the non-parallel node mark carried by the fourth message, and rendering the corresponding graph into a to-be-executed state; after receiving the fifth message, determining a corresponding graph of the non-parallel node in the flow chart according to the flow mark and the non-parallel node mark carried by the fifth message, and rendering the corresponding graph into an execution completion state; the fourth message is used for indicating that the non-parallel node starts to execute, and the fifth message is used for indicating that the non-parallel node ends to execute.
To achieve the above object, according to another aspect of the present invention, there is provided a visualization apparatus for business process debugging.
The visualization device for debugging the business process of the invention comprises: the creating module is used for responding to the triggering operation of a user, creating a main debugger, and sending the debugging configuration information of the service flow to the debugging engine based on the main debugger so that the debugging engine can debug the service flow according to the debugging configuration information; the receiving module is used for receiving a message returned by the debugging engine in the process of debugging the business process; the drawing module is used for drawing and displaying a thread call tree in a first area on a page after determining that the message is a first message, and drawing and displaying a plurality of sub-flowcharts nested in the same tag page in a second area on the page according to the identification of the parallel node and the information of a plurality of threads for executing the parallel node; wherein the first message is used for indicating that the parallel node starts to execute.
Optionally, the drawing module draws a thread call tree in a first area on the page and displays the thread call tree including: after receiving a second message returned by the debug engine, creating a plurality of sub-debuggers of the current debugger according to the second message, and adding information of the plurality of sub-debuggers into a sub-debugger list of the current debugger; the second message is used for indicating that a plurality of threads for executing the parallel node are started, and the plurality of sub debuggers are in one-to-one correspondence with the plurality of threads for executing the parallel node; then, the thread call tree is drawn and displayed in a first area on the page according to the sub-debugger list of the current debugger.
Optionally, the drawing module draws, in a second area on a page, a plurality of sub-flowcharts nested in the same tag page according to the identification of the parallel node and information of a plurality of threads for executing the parallel node, and displays the sub-flowcharts including: and the drawing module creates a label page named by the parallel node in a second area of the page according to the identification of the parallel node carried by the first message, and then draws and displays a plurality of sub-flowcharts in the label page according to the information of a plurality of threads for executing the parallel node carried by the second message.
To achieve the above object, according to still another aspect of the present invention, there is provided an electronic apparatus.
The electronic device of the present invention includes: one or more processors; and a storage means for storing one or more programs; when the one or more programs are executed by the one or more processors, the one or more processors are caused to implement the visualization method for business process debugging of the present invention.
To achieve the above object, according to still another aspect of the present invention, a computer-readable medium is provided.
The computer readable medium of the present invention has stored thereon a computer program which, when executed by a processor, implements the visualization method for business process debugging of the present invention.
One embodiment of the above invention has the following advantages or benefits: the method comprises the steps of responding to triggering operation of a user, creating a master debugger, sending debugging configuration information of a business process to a debugging engine based on the master debugger, after receiving a first message which is returned by the debugging engine in the process of debugging the business process and is used for indicating to start executing a parallel node, drawing a thread call tree in a first area of a page and displaying the thread call tree, drawing a plurality of sub-flowcharts nested in the same label page in a second area of the page and displaying the sub-flowcharts according to the identification of the parallel node and the information of a plurality of threads used for executing the parallel node, and further facilitating a developer to quickly and conveniently debug the business process.
Further effects of the above-described non-conventional alternatives are described below in connection with the embodiments.
Drawings
The drawings are included to provide a better understanding of the invention and are not to be construed as unduly limiting the invention. Wherein:
FIG. 1 is a schematic flow diagram of a visualization method for business process debugging according to a first embodiment of the present invention;
FIG. 2 is a flow diagram of a visualization method for business process debugging in accordance with a second embodiment of the present invention;
FIG. 3 is a flow diagram of a visualization method for business process debugging in a third embodiment in accordance with the present invention;
FIG. 4a is a schematic diagram I of a visual interface in a business process debugging process according to a third embodiment of the present invention;
FIG. 4b is a second schematic diagram of a visual interface during business process debugging according to a third embodiment of the present invention;
FIG. 4c is a schematic diagram III of a visual interface during business process debugging according to a third embodiment of the present invention;
FIG. 4d is a schematic diagram IV of a visual interface in a business process debugging process according to a third embodiment of the present invention;
FIG. 4e is a schematic diagram fifth of a visual interface during business process debugging according to a third embodiment of the present invention;
FIG. 5 is a schematic diagram of main modules of a visualization apparatus for business process debugging according to a fourth embodiment of the present invention;
FIG. 6 is a schematic diagram of the main modules of a visualization system for business process debugging according to a fifth embodiment of the present invention;
FIG. 7 is an exemplary system architecture diagram in which embodiments of the present invention may be applied;
fig. 8 is a schematic diagram of a computer system suitable for use in implementing an embodiment of the invention.
Detailed Description
Exemplary embodiments of the present invention will now be described with reference to the accompanying drawings, in which various details of the embodiments of the present invention are included to facilitate understanding, and are to be considered merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the invention. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.
It is noted that embodiments of the invention and features of the embodiments may be combined with each other without conflict.
Fig. 1 is a schematic flow diagram of a visualization method for business process debugging according to a first embodiment of the present invention. The method of embodiments of the present invention may be performed by a visualization device (alternatively referred to as a "debug GUI") for business process debugging. As shown in fig. 1, a visualization method for business process debugging according to an embodiment of the present invention includes:
Step S101, a main debugger is created in response to the triggering operation of a user, and the debugging configuration information of the service flow is sent to a debugging engine based on the main debugger, so that the debugging engine carries out service flow debugging according to the debugging configuration information.
Illustratively, the triggering operation of the user may be: the user selects a business process on the software interface and then clicks the "start debug" button. In response to the trigger operation by the user, execution of step S101 is started.
In step S101, after creating the master debugger, the debug GUI may send debug configuration information to the debug engine based on the master debugger. The debugging configuration information can include information such as business process identification, content of a process file, breakpoints set by a user, positions of some dependent files used in the process, and the like.
After receiving the debugging configuration information, the debugging engine can perform debugging initialization work according to the debugging configuration information. The debugging initialization is mainly used for establishing a debugging environment of the current debugging. After the debugging initialization operation is completed, the debugging engine prepares to execute the business process and feeds back a message to the debugging GUI in the process of executing the business process.
Step S102, receiving a message returned by the debugging engine in the process of debugging the business process.
The message may be a first message indicating that execution of the parallel node is started, a fourth message indicating that execution of the non-parallel node is started, or other messages returned by the debug engine. In a business process, there are parallel nodes (alternatively referred to as "parallel call sub-process nodes") and non-parallel nodes. Where parallel nodes refer to nodes executed by multiple threads, and non-parallel nodes refer to nodes executed by a single thread.
Step S103, after the message is determined to be the first message, a thread call tree is drawn and displayed in a first area on the page, and a plurality of sub-flowcharts nested in the same tag page are drawn and displayed in a second area on the page according to the identification of the parallel node and the information of a plurality of threads for executing the parallel node.
Wherein the first message is used for indicating that the parallel node starts to execute. In particular, when the debug engine executes to the parallel node, a first message may be sent to the debug GUI, where the first message includes information such as a flow identifier and a parallel node identifier. After the debug GUI receives the first message, a thread call tree can be drawn in a first area (or referred to as a "thread stack area") on the page, so that the call relationship between multiple threads in the process of debugging the business process is clearly represented in a tree structure. And the debugging GUI can draw and display a plurality of sub-flowcharts nested in the same tag page in a second area on the page according to the identification of the parallel node and the information of a plurality of threads for executing the parallel node. By nesting a plurality of sub-flowcharts corresponding to parallel nodes in the same tag page, the sub-flowcharts can be conveniently and quickly positioned to the parent process.
In the embodiment of the invention, the problems that thread management is unclear, a father process cannot be positioned when the multi-thread Cheng Zhihang sub-process exists in the prior art are solved through the steps, and the like, so that a developer can conveniently and rapidly debug the business process.
Fig. 2 is a partial flow diagram of a visualization method for business process debugging in accordance with a second embodiment of the present invention. As shown in fig. 2, a visualization method for business process debugging according to an embodiment of the present invention includes:
step S201, a main debugger is created in response to the triggering operation of a user, and the debugging configuration information of the business process is sent to a debugging engine based on the main debugger, so that the debugging engine carries out the business process debugging according to the debugging configuration information.
Illustratively, the triggering operation of the user may be: the user selects a business process on the software interface and then clicks the "start debug" button. In response to the trigger operation by the user, execution of step S201 is started.
In step S201, after creating the master debugger, the debug GUI may send debug configuration information to the debug engine based on the master debugger. The debugging configuration information can include information such as business process identification, content of a process file, breakpoints set by a user, positions of some dependent files used in the process, and the like.
After receiving the debugging configuration information, the debugging engine can perform debugging initialization work according to the debugging configuration information. The debugging initialization is mainly used for establishing a debugging environment of the current debugging. After the debugging initialization operation is completed, the debugging engine prepares to execute the business process and feeds back a message to the debugging GUI in the process of executing the business process.
Wherein the message may include: a message indicating that execution of the flow is to begin, a first message indicating that execution of the parallel node is to begin, a fourth message indicating that execution of the non-parallel node is to begin, and other messages returned by the debug engine. For example, after the debug engine completes the debug initialization, it sends a "start execution flow" message to the debug GUI. After receiving the message of "start executing the flow", the debug GUI may find a flow file according to the flow identifier carried by the message, then create a tag page according to the second area (or referred to as "flow chart display area") of the flow file on the page, and display a flow chart (or referred to as main flow chart) corresponding to the flow file in the tag page.
Step S202, receiving a message returned by the debugging engine in the process of debugging the business process.
Step 203, when the message is a fourth message, determining a corresponding graph of the non-parallel node in the flow chart according to the flow identifier and the non-parallel node identifier carried by the fourth message, and then rendering the corresponding graph into a to-be-executed state.
In a business process, there are parallel nodes (alternatively referred to as "parallel call sub-process nodes") and non-parallel nodes. Where parallel nodes refer to nodes executed by multiple threads, and non-parallel nodes refer to nodes executed by a single thread.
In one example, the debug engine, upon execution to a common node (i.e. non-parallel node), may send a fourth message to the debug GUI indicating that execution of the non-parallel node is to begin, the fourth message containing the flow identification and the node identification. After the debug GUI receives the fourth message, the flow chart where the node is located can be determined according to the flow mark carried by the fourth message, then the corresponding graph of the node in the flow chart is determined according to the node mark, and then the corresponding graph is rendered into a to-be-executed state. For example, the color of the corresponding graphic may be rendered into a color that characterizes the state to be executed.
And step S204, when the message is a first message, creating a label page named by the parallel node in a second area of the page according to the identification of the parallel node carried by the first message. After step S204, step S205 to step S208 may be performed.
In one example, the debug engine, upon execution to one of the parallel nodes, may send a first message to the debug GUI indicating that execution of the parallel node is to begin, the first message containing a flow identification and a node identification. After the debug GUI receives the first message, a tab page named by the parallel node may be created at a position (e.g. the right side of the tab page where the main flow is located) in the second area of the page according to the node identifier carried by the first message, so as to display execution procedures of all sub-flows under the parallel node.
Step S205, receiving a second message returned by the debugging engine.
In one example, the debug engine may determine the number of threads to execute the parallel node based on the configuration information for the parallel node, then create and launch the threads, and send a second message to the debug GUI. Wherein the second message is used to indicate that a plurality of threads for executing the parallel node are started. The second message may include information such as a flow identification, a name of the new thread, an identification of a sub-flow to be executed by the new thread, and the like. After that, the debug GUI receives the second message.
In the implementation, after a thread for executing the parallel node is started, the debug engine may send a message for indicating that the thread is started to the debug GUI, that is, send starting messages of each thread in sequence; alternatively, the debug engine may send a message to the debug GUI indicating that all threads executing the parallel node are started after all threads executing the parallel node are started.
Step S206, creating a plurality of sub-debuggers of the current debugger according to the second message, and adding the information of the plurality of sub-debuggers to a sub-debugger list of the current debugger.
In one example, the debug GUI may create multiple sub-debuggers of the current debugger from the second message and save the information of the thread carried by the second message to each sub-debugger, and the debug GUI may add the information of each newly created sub-debugger to the sub-debugger list of the currently located debugger. The plurality of sub-debuggers are in one-to-one correspondence with a plurality of threads for executing the parallel nodes. In particular, the current debugger may be a main debugger or a sub-debugger. The main debugger and the sub debugger are both used for communicating with a debug engine.
Step S207, drawing a thread call tree in a first area on a page according to a sub-debugger list of the current debugger and displaying the thread call tree.
In the embodiment of the invention, because the structure of the current debugger reflects the calling relation between the father thread and the multiple threads (namely, the child threads) executing the parallel node, the thread calling tree can be drawn and displayed in the first area on the page according to the child debugger list of the current debugger.
And step S208, drawing and displaying a plurality of sub-flowcharts in the tag page according to the information, carried by the second message, of the plurality of threads for executing the parallel nodes.
In one example, the debug GUI may find a previously created tab page (e.g. tab page) named for the parallel node from the node identification carried by the second message, create a tab page in the tab page named for each thread executing the parallel node, and draw and display a sub-flowchart to be executed by the thread in the tab page named for each thread.
In the embodiment of the invention, the problems that the thread management is unclear, the father process can not be positioned when the multi-line Cheng Zhihang sub-process exists in the existing visualization method for debugging the business process can be solved through the steps, and the like, so that a developer can conveniently and rapidly debug the business process.
Fig. 3 is a flow diagram of a visualization method for business process debugging in a third embodiment of the present invention. The method of embodiments of the present invention may be performed jointly by a debug GUI (debug visualization component, also referred to as a "means for business process debugging") and a debug engine. As shown in fig. 3, a visualization method for business process debugging according to an embodiment of the present invention includes:
Step S301, the debugging GUI creates a main debugger and sends debugging configuration information of the business process to a debugging engine.
In this step, after creating the master debugger, the debug GUI may send debug configuration information to the debug engine based on the master debugger. The debugging configuration information can include information such as business process identification, content of a process file, breakpoints set by a user, positions of some dependent files used in the process, and the like.
Step S302, the debugging engine performs debugging initialization.
After receiving the debugging configuration information, the debugging engine can perform debugging initialization work according to the debugging configuration information. The debugging initialization is mainly used for establishing a debugging environment of the current debugging.
After the debugging initialization operation is completed, the debugging engine prepares to execute the business process and feeds back a message to the debugging GUI in the process of executing the business process. For example, after the debug engine completes the debug initialization, it sends a "start execution flow" message to the debug GUI. After receiving the message of "start executing the flow", the debug GUI may find a flow file according to the flow identifier carried by the message, then create a tag page according to the second area (or referred to as "flow chart display area") of the flow file on the page, and display a flow chart (or referred to as main flow chart) corresponding to the flow file in the tag page.
Step S303, the debugging engine sends a fourth message to the debugging GUI.
Wherein the fourth message is used to indicate that execution of the non-parallel node is to begin. In one example, the debug engine, when executing to a common node (i.e. non-parallel node), may send a fourth message to the debug GUI, which contains the flow identification and the node identification.
Step S304, the debugging GUI determines the corresponding graph of the non-parallel node in the affiliated flow chart according to the flow mark and the non-parallel node mark carried by the fourth message, and then the corresponding graph is rendered into a to-be-executed state.
In this step, after the debug GUI receives the fourth message, the flowchart in which the node is located may be determined according to the flow identifier carried by the fourth message, then the corresponding graph of the node in the flowchart to which the node belongs is determined according to the node identifier, and then the corresponding graph is rendered into the to-be-executed state. For example, the color of the corresponding graphic may be rendered into a color that characterizes the state to be executed.
Step S305, the debug engine sends a fifth message to the debug GUI.
Wherein the fifth message is used for indicating that the non-parallel node execution is finished. In one example, the debug engine may send a fifth message to the debug GUI when a common node is executed, the fifth message may contain information such as flow identification, node execution results, and the like. The node execution result may be indication information of execution success or execution failure.
Step S306, the debugging GUI determines the corresponding graph of the non-parallel node in the affiliated flow chart according to the flow mark and the non-parallel node mark carried by the fifth message, and then renders the corresponding graph into an execution completion state.
Wherein the execution completion status includes: an execution success state and an execution failure state. In this step, the debug GUI may determine, according to the flow identifier carried by the fifth message, a flow chart in which the node is located, then determine, according to the node identifier, a corresponding graph of the node in the flow chart to which the node belongs, and render, according to the result of executing the node, the corresponding graph into an execution success state or an execution failure state. For example, the debug GUI may render the corresponding graphics into a color for characterizing execution success or a color for characterizing execution failure based on the results of node execution. In addition, the debugging GUI can also find the identification of the last node according to the node execution linked list maintained internally, find the corresponding graph of the last node in the flow chart according to the identification of the last node, and render the directed line segment between the graphs corresponding to the two nodes in the flow chart into a color for representing successful execution or a color for representing failed execution.
Step S307, the debug engine sends a first message to the debug GUI.
Wherein the first message is used to indicate that execution of the parallel node is to begin. In this step, the debug engine, when executing to a parallel node, may send a first message to the debug GUI, the first message containing a flow identification and a node identification.
Step S308, the debugging GUI creates a label page named by the parallel node in a second area of the page according to the identification of the parallel node carried by the first message.
In this step, after the debug GUI receives the first message, a tab page named by the parallel node may be created at a position (e.g. the right of the tab page where the main flow is located) in the second area of the page according to the node identifier carried by the first message, so as to display execution procedures of all sub-flows under the parallel node.
Step S309, the debugging engine sends a second message to the debugging GUI.
Wherein the second message is used to indicate that a plurality of threads for executing the parallel node are started. In this step, the debug engine may determine the number of threads for executing the parallel node based on the configuration information of the parallel node, then create and start the threads, and send a second message to the debug GUI. Wherein the second message is used to indicate that a plurality of threads for executing the parallel node are started. The second message may include information such as a flow identification, a name of the new thread, an identification of a sub-flow to be executed by the new thread, and the like. After that, the debug GUI receives the second message.
Step S310, the debugging GUI creates a plurality of sub-debuggers of the current debugger according to the second message, adds the information of the plurality of sub-debuggers to a sub-debugger list of the current debugger, draws a thread call tree and displays the thread call tree in a first area on a page according to the sub-debugger list of the current debugger, and draws a plurality of sub-flowcharts and displays the sub-flowcharts in the tag page according to the information of a plurality of threads for executing the parallel node carried by the second message.
The plurality of sub-debuggers are in one-to-one correspondence with a plurality of threads for executing the parallel nodes. In particular, the current debugger may be a main debugger or a sub-debugger. The main debugger and the sub debugger are both used for communicating with a debug engine.
Step S311, the debugging engine sends a third message to the debugging GUI.
Wherein the third message is used for indicating that the parallel node execution is finished.
Step S312, the debug GUI closes the plurality of subdebuggers according to the third message, deletes the information of the plurality of subdebuggers from the subdebugger list of the current debugger, and updates the thread call tree and the plurality of sub-flowcharts nested in the same tag page.
In the embodiment of the invention, the problems that the thread management is unclear, the father process can not be positioned when the multi-line Cheng Zhihang sub-process exists in the existing visualization method for debugging the business process can be solved through the steps, and the like, so that a developer can conveniently and rapidly debug the business process.
Fig. 4a to 4e are schematic diagrams of a visual interface in a process of debugging a business process according to a third embodiment of the present invention. The changes in the visual interface during the business process debugging process are described below in connection with fig. 4 a-4 e.
FIG. 4a shows a business flow diagram in this example, including a start node, a data conversion node, a parallel sub-flow call node (i.e., a "parallel node"), and an end node.
The debug engine sends a first message to the debug GUI when executing to the parallel sub-flow call node. The debug GUI refreshes the page according to the first message, the refresh result is shown in FIG. 4 b. Specifically, the debugging GUI may create a tab page named by the parallel node on the right side of the tab page where the main flow is located according to the node identifier carried by the first message, so as to display execution processes of all sub-flows under the parallel node.
Next, the debug engine determines the number of threads for executing the parallel node based on the configuration information of the parallel node, then creates and starts the threads, and sends a second message to the debug GUI. The debug GUI refreshes the page according to the second message, and the refreshing result is shown in FIG. 4 c. Specifically, the debug GUI draws and displays a thread call tree in a first region (i.e. thread stack region) on a page, and draws and displays multiple sub-flowcharts nested in the same tab page in a second region on the page.
Then, when the parallel node execution ends, the debug engine sends a message to the debug GUI indicating that the parallel node execution ends. The debug GUI refreshes the page according to the message, with the refresh result shown in fig. 4 d. Specifically, the debug GUI updates the thread call tree in the first region of the page and updates the flow diagram in the second region of the page.
Next, when the execution of the flow ends, the debug engine sends a message to the debug GUI indicating the end of the execution of the flow. The debug GUI refreshes the page according to the message, with the refresh result shown in fig. 4 e.
Fig. 5 is a schematic diagram of main modules of a visualization apparatus for business process debugging according to a fourth embodiment of the present invention. As shown in fig. 5, a visualization device 500 for business process debugging according to an embodiment of the present invention includes: a creation module 501, a receiving module 502, and a drawing module 503.
The creating module 501 is configured to create a master debugger in response to a triggering operation of a user, and send debugging configuration information of a service flow to a debugging engine based on the master debugger, so that the debugging engine performs service flow debugging according to the debugging configuration information.
Illustratively, the triggering operation of the user may be: the user selects a business process on the software interface and then clicks the "start debug" button. In response to the trigger operation by the user, execution of step S101 is started.
In one example, after creating the master debugger, creation module 501 may send debug configuration information to the debug engine based on the master debugger. The debugging configuration information can include information such as business process identification, content of a process file, breakpoints set by a user, positions of some dependent files used in the process, and the like. After receiving the debugging configuration information, the debugging engine can perform debugging initialization work according to the debugging configuration information. The debugging initialization is mainly used for establishing a debugging environment of the current debugging. After the debug initialization process is complete, the debug engine prepares to execute the business process and feeds back messages to the visualization device (or "debug GUI") for the debugging of the business process during execution of the business process.
And the receiving module 502 is configured to receive a message returned by the debug engine in a process of performing service flow debugging.
Illustratively, the message received by the receiving module 502 may be a first message for indicating that execution of the parallel node is started, a fourth message for indicating that execution of the non-parallel node is started, or other messages returned by the debug engine. In a business process, there are parallel nodes (alternatively referred to as "parallel call sub-process nodes") and non-parallel nodes. Where parallel nodes refer to nodes executed by multiple threads, and non-parallel nodes refer to nodes executed by a single thread.
A drawing module 503, configured to draw and display a thread call tree in a first area on a page after determining that the message is a first message, and draw and display a plurality of sub-flowcharts nested in the same tag page in a second area on the page according to the identification of the parallel node and information of a plurality of threads for executing the parallel node; wherein the first message is used for indicating that the parallel node starts to execute.
Wherein the first message is used for indicating that the parallel node starts to execute. In particular, when the debug engine executes to the parallel node, a first message may be sent to the debug GUI, where the first message includes information such as a flow identifier and a parallel node identifier. After the debug GUI receives the first message, the thread call tree may be drawn by the drawing module 503 in a first area (or referred to as a "thread stack area") on the page, so that the call relationship between the multiple threads in the process of debugging the service flow is clearly represented in a tree structure. And, the drawing module 503 may draw and display multiple sub-flowcharts nested in the same tag page in the second area on the page according to the identification of the parallel node and the information of the multiple threads for executing the parallel node. By nesting a plurality of sub-flowcharts corresponding to parallel nodes in the same tag page, the sub-flowcharts can be conveniently and quickly positioned to the parent process.
In one alternative example, the drawing module 503 draws a thread call tree at a first region on a page and displaying may include: after receiving a second message returned by the debug engine, creating a plurality of sub-debuggers of the current debugger according to the second message, and adding information of the plurality of sub-debuggers into a sub-debugger list of the current debugger; the second message is used for indicating that a plurality of threads for executing the parallel node are started, and the plurality of sub debuggers are in one-to-one correspondence with the plurality of threads for executing the parallel node; then, the thread call tree is drawn and displayed in a first area on the page according to the sub-debugger list of the current debugger.
In an alternative example, the drawing module 503 draws, in a second area on the page, a plurality of sub-flowcharts nested in the same tag page and displays the sub-flowcharts including: the drawing module 503 creates a label page named by the parallel node in a second area of the page according to the identifier of the parallel node carried by the first message, and then draws and displays a plurality of sub-flowcharts in the label page according to the information of a plurality of threads for executing the parallel node carried by the second message.
In the embodiment of the invention, the problems that thread management is unclear, a father process cannot be positioned when the multi-thread Cheng Zhihang sub-process exists in the prior art are solved by the device, and the like, so that a developer can conveniently and rapidly debug the business process.
Fig. 6 is a schematic diagram of main modules of a visualization system for business process debugging according to a fifth embodiment of the present invention. As shown in fig. 6, a visualization system 600 for business process debugging according to an embodiment of the present invention includes: debug GUI601, debug engine 602.
The debug GUI601 is configured to create a master debugger in response to a triggering operation of a user, and send debug configuration information of a service flow to a debug engine based on the master debugger, so that the debug engine performs service flow debugging according to the debug configuration information; the debug GUI601 is further configured to receive a message returned by the debug engine during a process of performing a business process debugging; the debug GUI601 is further configured to draw and display a thread call tree in a first area on a page after determining that the message is a first message, and draw and display a plurality of sub-flowcharts nested in the same tag page in a second area on the page according to the identification of the parallel node and information of a plurality of threads for executing the parallel node; wherein the first message is used for indicating that the parallel node starts to execute.
The debug engine 602 is configured to perform a debug initialization operation according to the debug configuration information, execute a service flow after completing the debug initialization operation, and feed back a message to the debug GUI during execution of the service flow. Wherein the message may include: a message indicating that execution of the flow is to begin, a first message indicating that execution of the parallel node is to begin, a fourth message indicating that execution of the non-parallel node is to begin, and other messages returned by the debug engine. For example, after the debug engine completes the debug initialization, it sends a "start execution flow" message to the debug GUI. After receiving the message of "start executing the flow", the debug GUI may find a flow file according to the flow identifier carried by the message, then create a tag page according to the second area (or referred to as "flow chart display area") of the flow file on the page, and display a flow chart (or referred to as main flow chart) corresponding to the flow file in the tag page.
In the embodiment of the invention, the problems that thread management is unclear, a father process cannot be positioned when the multi-thread Cheng Zhihang sub-process exists in the prior art are solved through the system, and the like, so that a developer can conveniently and rapidly debug the business process.
FIG. 7 illustrates an exemplary system architecture 700 for a visualization method for business process debugging or a visualization device for business process debugging to which embodiments of the present invention may be applied.
As shown in fig. 7, a system architecture 700 may include terminal devices 701, 702, 703, a network 704, and a server 705. The network 704 is the medium used to provide communication links between the terminal devices 701, 702, 703 and the server 705. The network 704 may include various connection types, such as wired, wireless communication links, or fiber optic cables, among others.
A user may interact with the server 705 via the network 704 using the terminal devices 701, 702, 703 to receive or send messages or the like. Various communication client applications, such as a business process debugging class application, a shopping class application, a web browser application, a search class application, an instant messaging tool, a mailbox client, social platform software, and the like, can be installed on the terminal devices 701, 702, 703.
The terminal devices 701, 702, 703 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smartphones, tablets, laptop and desktop computers, and the like.
The server 705 may be a server providing various services, such as a background management server providing support for business process debugging class applications browsed by the user using the terminal devices 701, 702, 703. The background management server can analyze and process the received data such as the business process debugging request and the like, and feed back the processing result (such as the business process debugging result) to the terminal equipment.
It should be noted that, the visualization method for debugging a business process provided by the embodiment of the present invention is generally executed by a terminal device, and correspondingly, the visualization device for debugging a business process is generally disposed in the terminal device.
It should be understood that the number of terminal devices, networks and servers in fig. 7 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.
Referring now to FIG. 8, there is illustrated a schematic diagram of a computer system 800 suitable for use in implementing an electronic device of an embodiment of the present invention. The computer system shown in fig. 8 is merely an example, and should not be construed as limiting the functionality and scope of use of embodiments of the present invention.
As shown in fig. 8, the computer system 800 includes a Central Processing Unit (CPU) 801 that can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM) 802 or a program loaded from a storage section 808 into a Random Access Memory (RAM) 803. In the RAM 803, various programs and data required for the operation of the system 800 are also stored. The CPU 801, ROM 802, and RAM 803 are connected to each other by a bus 804. An input/output (I/O) interface 805 is also connected to the bus 804.
The following components are connected to the I/O interface 805: an input portion 806 including a keyboard, mouse, etc.; an output portion 807 including a display such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and a speaker; a storage section 808 including a hard disk or the like; and a communication section 809 including a network interface card such as a LAN card, a modem, or the like. The communication section 809 performs communication processing via a network such as the internet. The drive 810 is also connected to the I/O interface 805 as needed. A removable medium 811 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 810 as needed so that a computer program read out therefrom is mounted into the storage section 808 as needed.
In particular, according to embodiments of the present disclosure, the processes described above with reference to flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method shown in the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network via the communication section 809, and/or installed from the removable media 811. The above-described functions defined in the system of the present invention are performed when the computer program is executed by a Central Processing Unit (CPU) 801.
The computer readable medium shown in the present invention may be a computer readable signal medium or a computer readable storage medium, or any combination of the two. The computer readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples of the computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In the present invention, however, the computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, with the computer-readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.
The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The modules involved in the embodiments of the present invention may be implemented in software or in hardware. The described modules may also be provided in a processor, for example, as: a processor includes a creation module, a reception module, and a rendering module. The names of these modules do not constitute a limitation on the module itself in some cases, for example, the receiving module may also be described as "a module that receives a message returned by the debug engine".
As another aspect, the present invention also provides a computer-readable medium that may be contained in the apparatus described in the above embodiments; or may be present alone without being fitted into the device. The computer-readable medium carries one or more programs which, when executed by one of the devices, cause the device to perform the following: responding to triggering operation of a user, creating a main debugger, and transmitting debugging configuration information of a business process to a debugging engine based on the main debugger so that the debugging engine can debug the business process according to the debugging configuration information; receiving a message returned by the debugging engine in the process of debugging the business process; after the message is determined to be the first message, drawing a thread call tree in a first area on a page and displaying the thread call tree, and drawing and displaying a plurality of sub-flowcharts nested in the same tag page in a second area on the page according to the identification of the parallel node and the information of a plurality of threads for executing the parallel node; wherein the first message is used for indicating that the parallel node starts to execute.
The above embodiments do not limit the scope of the present invention. It will be apparent to those skilled in the art that various modifications, combinations, sub-combinations and alternatives can occur depending upon design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present invention should be included in the scope of the present invention.
Claims (8)
1. A visualization method for business process debugging, the method comprising:
responding to triggering operation of a user, creating a main debugger, and transmitting debugging configuration information of a business process to a debugging engine based on the main debugger so that the debugging engine can debug the business process according to the debugging configuration information;
receiving a message returned by the debugging engine in the process of debugging the business process;
after the message is determined to be the first message, drawing a thread call tree in a first area on a page and displaying the thread call tree, and drawing and displaying a plurality of sub-flowcharts nested in the same tag page in a second area on the page according to the identification of the parallel node and the information of a plurality of threads for executing the parallel node; wherein the first message is used for indicating that the parallel node starts to execute;
The step of drawing and displaying the thread call tree in the first area on the page comprises the following steps:
after receiving a second message returned by the debug engine, creating a plurality of sub-debuggers of the current debugger according to the second message, and adding information of the plurality of sub-debuggers into a sub-debugger list of the current debugger; the second message is used for indicating that a plurality of threads for executing the parallel node are started, and the plurality of sub debuggers are in one-to-one correspondence with the plurality of threads for executing the parallel node; then, the thread call tree is drawn and displayed in a first area on the page according to the sub-debugger list of the current debugger.
2. The method of claim 1, wherein the step of drawing and displaying a plurality of sub-flowcharts nested in the same tag page in a second area on the page according to the identification of the parallel node and information of a plurality of threads for executing the parallel node comprises:
creating a label page named by the parallel node in a second area of the page according to the identification of the parallel node carried by the first message, and then drawing and displaying a plurality of sub-flowcharts in the label page according to the information of a plurality of threads for executing the parallel node carried by the second message.
3. The method according to claim 2, wherein the method further comprises:
after receiving a third message returned by the debug engine, closing the plurality of sub-debuggers according to the third message, deleting the information of the plurality of sub-debuggers from a sub-debugger list of the current debugger, and updating the thread call tree and the plurality of sub-flowcharts nested in the same tag page; wherein the third message is used for indicating that the parallel node execution is finished.
4. The method according to claim 1, wherein the method further comprises:
after the message is determined to be a fourth message, determining a corresponding graph of the non-parallel node in the flow chart according to the flow mark and the non-parallel node mark carried by the fourth message, and rendering the corresponding graph into a to-be-executed state; after receiving the fifth message, determining a corresponding graph of the non-parallel node in the flow chart according to the flow mark and the non-parallel node mark carried by the fifth message, and rendering the corresponding graph into an execution completion state; the fourth message is used for indicating that the non-parallel node starts to execute, and the fifth message is used for indicating that the non-parallel node ends to execute.
5. A visualization apparatus for business process debugging, the apparatus comprising:
the creating module is used for responding to the triggering operation of a user, creating a main debugger, and sending the debugging configuration information of the service flow to the debugging engine based on the main debugger so that the debugging engine can debug the service flow according to the debugging configuration information;
the receiving module is used for receiving a message returned by the debugging engine in the process of debugging the business process;
the drawing module is used for drawing and displaying a thread call tree in a first area on a page after determining that the message is a first message, and drawing and displaying a plurality of sub-flowcharts nested in the same tag page in a second area on the page according to the identification of the parallel node and the information of a plurality of threads for executing the parallel node; wherein the first message is used for indicating that the parallel node starts to execute;
the drawing module draws a thread call tree in a first area on a page and displays the thread call tree including:
after receiving a second message returned by the debug engine, creating a plurality of sub-debuggers of the current debugger according to the second message, and adding information of the plurality of sub-debuggers into a sub-debugger list of the current debugger; the second message is used for indicating that a plurality of threads for executing the parallel node are started, and the plurality of sub debuggers are in one-to-one correspondence with the plurality of threads for executing the parallel node; then, the thread call tree is drawn and displayed in a first area on the page according to the sub-debugger list of the current debugger.
6. The apparatus of claim 5, wherein the rendering module renders and displays a plurality of sub-flowcharts nested in a same tag page in a second area on a page based on the identification of the parallel node and information for executing a plurality of threads of the parallel node, comprising:
and the drawing module creates a label page named by the parallel node in a second area of the page according to the identification of the parallel node carried by the first message, and then draws and displays a plurality of sub-flowcharts in the label page according to the information of a plurality of threads for executing the parallel node carried by the second message.
7. An electronic device, comprising:
one or more processors;
storage means for storing one or more programs,
when executed by the one or more processors, causes the one or more processors to implement the method of any of claims 1 to 4.
8. A computer readable medium on which a computer program is stored, characterized in that the program, when executed by a processor, implements the method according to any one of claims 1 to 4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010104780.XA CN113282444B (en) | 2020-02-20 | 2020-02-20 | Visualization method and device for debugging business process |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010104780.XA CN113282444B (en) | 2020-02-20 | 2020-02-20 | Visualization method and device for debugging business process |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113282444A CN113282444A (en) | 2021-08-20 |
| CN113282444B true CN113282444B (en) | 2023-09-22 |
Family
ID=77275139
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010104780.XA Active CN113282444B (en) | 2020-02-20 | 2020-02-20 | Visualization method and device for debugging business process |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113282444B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114706610A (en) * | 2022-03-30 | 2022-07-05 | 苏州峰之鼎信息科技有限公司 | Business flow chart generation method, device, equipment and storage medium |
| CN114781328A (en) * | 2022-06-21 | 2022-07-22 | 成都中科合迅科技有限公司 | Method for visually arranging business process based on plaintext file |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101208659A (en) * | 2005-04-15 | 2008-06-25 | 微软公司 | Method and apparatus for performance analysis on a software program |
| CN102169455A (en) * | 2010-02-26 | 2011-08-31 | 国际商业机器公司 | Debugging method and system for software performance test |
| WO2015027403A1 (en) * | 2013-08-28 | 2015-03-05 | Hewlett-Packard Development Company, L.P. | Testing multi-threaded applications |
| CN109345443A (en) * | 2018-10-19 | 2019-02-15 | 珠海金山网络游戏科技有限公司 | Data processing method and device calculate equipment and storage medium |
| CN110457277A (en) * | 2019-08-19 | 2019-11-15 | 北京博睿宏远数据科技股份有限公司 | Service process performance analysis method, device, equipment and storage medium |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20130055072A1 (en) * | 2011-08-24 | 2013-02-28 | Robert Douglas Arnold | Multi-Threaded Graphical Display System |
-
2020
- 2020-02-20 CN CN202010104780.XA patent/CN113282444B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101208659A (en) * | 2005-04-15 | 2008-06-25 | 微软公司 | Method and apparatus for performance analysis on a software program |
| CN102169455A (en) * | 2010-02-26 | 2011-08-31 | 国际商业机器公司 | Debugging method and system for software performance test |
| WO2015027403A1 (en) * | 2013-08-28 | 2015-03-05 | Hewlett-Packard Development Company, L.P. | Testing multi-threaded applications |
| CN109345443A (en) * | 2018-10-19 | 2019-02-15 | 珠海金山网络游戏科技有限公司 | Data processing method and device calculate equipment and storage medium |
| CN110457277A (en) * | 2019-08-19 | 2019-11-15 | 北京博睿宏远数据科技股份有限公司 | Service process performance analysis method, device, equipment and storage medium |
Non-Patent Citations (1)
| Title |
|---|
| 态势实时显示与回放系统的设计与实现;张明杰 等;指挥控制与仿真;第41卷(第1期);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113282444A (en) | 2021-08-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109145023B (en) | Method and apparatus for processing data | |
| CN107451062B (en) | User interface traversal test method, device, server and storage medium | |
| CN113934464A (en) | Method and device for starting android application in Linux system and electronic equipment | |
| CN113282444B (en) | Visualization method and device for debugging business process | |
| CN109582317B (en) | Method and apparatus for debugging hosted applications | |
| CN111400172B (en) | Program debugging method and device | |
| CN109634764A (en) | Work-flow control method, apparatus, equipment, storage medium and system | |
| WO2019075845A1 (en) | Construction method and device for link call relationship, computer device and storage medium | |
| CN110609755A (en) | Message processing method, device, equipment and medium for cross-block chain node | |
| CN112015654A (en) | Method and apparatus for testing | |
| CN113760488A (en) | Method, device, equipment and computer readable medium for scheduling task | |
| CN113419841B (en) | Message scheduling method and device, electronic equipment and computer readable medium | |
| CN112817562A (en) | Service processing method and device | |
| CN110807535A (en) | Construction method and construction device of unified reservation platform and unified reservation platform system | |
| CN111338928A (en) | Chrome-based browser testing method and device | |
| CN115454956A (en) | Log generation method and device, electronic equipment and storage medium | |
| CN113760487B (en) | Service processing method and device | |
| CN112947918A (en) | Data display method and device | |
| CN113704079A (en) | Interface testing method and device based on Protobuf | |
| CN113407329B (en) | Task execution method, device, equipment and storage medium | |
| CN110633197A (en) | Method and device for detecting excessive drawing | |
| CN110858240A (en) | Front-end module loading method and device | |
| CN111625442B (en) | Mock testing method and device | |
| CN116774996A (en) | Integrated development system, code processing method, electronic device, and storage medium | |
| CN117608798A (en) | Workflow scheduling method, device, equipment and medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |