CN117472988A

CN117472988A - Log checking method, device and equipment for process instance and readable medium

Info

Publication number: CN117472988A
Application number: CN202311459434.3A
Authority: CN
Inventors: 潘咪
Original assignee: Shanghai Pengxi Semiconductor Co ltd
Current assignee: Shanghai Pengxi Semiconductor Co ltd
Priority date: 2023-11-03
Filing date: 2023-11-03
Publication date: 2024-01-30

Abstract

The application provides a log viewing method, device and equipment of a flow instance and a readable medium. The method comprises the following steps: obtaining a design result of a flow template in a visual canvas; the flow template consists of flow nodes and sequential flows connected among the flow nodes; executing the flow template, generating a flow instance, and recording according to preset record information in the process of generating the flow instance to obtain an operation log; and marking and displaying the running log in a flow template in the visual canvas by a preset mark. According to the technical scheme, the acquired operation log can be displayed in the flow template in the visual canvas according to a certain mode, so that the operation log is more visual to view, and workers can conveniently locate the abnormal position and analyze the reasons of the abnormality.

Description

Log checking method, device and equipment for process instance and readable medium

Technical Field

The present disclosure relates to the field of computer technologies, and in particular, to a method, an apparatus, a device, and a readable medium for checking logs of a process instance.

Background

In recent years, with rapid development of the technology level, process planning has been widely used. In the process of organizing the circulation among the multiparty members according to the business process, the process template design can help the enterprise information transfer, and the automation level of the enterprise is improved. And a large amount of log data can be generated in the process of running the flow, and the log data can be checked to help a worker locate the abnormal position and the abnormal reason in the process of running the flow, so that the abnormal data can be obtained. For some complex flow templates, the number of flow nodes is large, the circulation times of each node is large, a large amount of log data is caused, and great difficulty is caused to the checking of the log data and the positioning of abnormality.

However, the inventors found that there are at least the following technical problems in the related art:

firstly, logs in the running process are displayed in a text mode, the readability is poor, the correlation of running of different nodes is difficult to learn, and the carding is complicated and the efficiency is low. Secondly, all operation examples are tiled and unfolded under the condition of multiple execution such as circulation and the like, all operation conditions can be displayed, but the display content is inconsistent with the original design drawing, the experience of staff is affected, and the viewing is not visual enough.

Disclosure of Invention

An object of the present application is to provide a method, an apparatus, a device and a readable medium for checking logs of a process instance, at least to solve the problems of poor log data readability and insufficient visual observation. The purpose of the present application is: a new log viewing method for process instances is provided. According to the method, after the running log is obtained comprehensively, the running log is displayed in a visual canvas in a correlated manner with the flow template, so that the readability of the running log can be improved, log data can be visually watched, and the complexity of processing the flow log by workers is reduced.

To achieve the above object, some embodiments of the present application provide the following aspects:

in a first aspect, some embodiments of the present application further provide a log viewing method of a flow instance, where the method includes:

obtaining a design result of a flow template in a visual canvas; the flow template consists of flow nodes and sequential flows connected among the flow nodes;

executing the flow template, generating a flow instance, and recording according to preset record information in the process of generating the flow instance to obtain an operation log;

And marking and displaying the running log in a flow template in the visual canvas by a preset mark.

In a second aspect, some embodiments of the present application further provide a log viewing apparatus of a flow instance, where the apparatus includes:

the flow template acquisition module is used for acquiring the design result of the flow template in the visual canvas; the flow template consists of flow nodes and sequential flows connected among the flow nodes;

the operation log recording module is used for executing the flow template, generating a flow instance, and recording according to preset recording information in the process of generating the flow instance to obtain an operation log;

and the operation log display module is used for displaying the operation log in a preset mark in a flow template in the visual canvas.

In a third aspect, some embodiments of the present application further provide a computer apparatus, the apparatus comprising:

one or more processors; and

a memory storing computer program instructions that, when executed, cause the processor to perform a log view method of a flow instance as described above.

In a fourth aspect, some embodiments of the present application also provide a computer readable medium having stored thereon computer program instructions executable by a processor to implement a log view method of a flow instance as described above.

Compared with the prior art, in the scheme provided by the embodiment of the application, the design result of the flow template in the visual canvas is obtained; the flow template consists of flow nodes and sequential flows connected among the flow nodes; executing the flow template, generating a flow instance, and recording according to preset record information in the process of generating the flow instance to obtain an operation log; and marking and displaying the running log in a flow template in the visual canvas by a preset mark. The acquired running log is displayed in the flow template in the visual canvas in a certain mode, so that the running log is more visual to view, and workers can conveniently locate the abnormal position and analyze the reasons of the abnormality.

Drawings

Fig. 1 is a flow diagram of a log viewing method of a flow example provided in an embodiment of the present application;

FIG. 2 is a schematic diagram of the design results of a flow template in a visualization canvas provided in accordance with an embodiment of the present application;

FIG. 3 is a diagram illustrating the effect of log markup of a flow template in a visualization canvas according to an embodiment of the present application;

fig. 4 is a flow diagram of a log viewing method of a flow example provided in the second embodiment of the present application;

FIG. 5 is a schematic diagram of a log of a process node according to a second embodiment of the present disclosure;

FIG. 6 is a schematic diagram showing a differential display of a running route according to a second embodiment of the present application;

fig. 7 is a flow diagram of a log viewing method of a flow example provided in the third embodiment of the present application;

FIG. 8 is a log diagram of a sequential flow provided in embodiment III of the present application;

FIG. 9 is a schematic view showing the effect of the cyclic process according to the embodiment of the present application;

fig. 10 is a schematic structural diagram of a log viewing device of a flow example provided in the fourth embodiment of the present application;

fig. 11 is a schematic structural diagram of a computer device provided in a fifth embodiment of the present application.

Detailed Description

For the purposes of making the objects, technical solutions and advantages of the embodiments of the present application more clear, the technical solutions of the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be made by one of ordinary skill in the art based on the embodiments herein without making any inventive effort, are intended to be within the scope of the present application.

The technical scheme provided by the embodiment of the application is described in detail through specific embodiments and application scenes thereof with reference to the accompanying drawings.

Example 1

Fig. 1 is a flowchart of a log viewing method of a flowchart example provided in an embodiment of the present application. As shown in fig. 1, the method specifically comprises the following steps: the process comprises the following steps:

step S101, obtaining a design result of a flow template in a visual canvas; the flow template consists of flow nodes and sequence flows connected among the flow nodes.

The visual canvas can be a canvas for showing the design result of the flow template in the process of designing the flow template. FIG. 2 is a schematic diagram of the design results of a flow template in a visualization canvas provided in accordance with an embodiment of the present application. As shown in fig. 2, the flow template may be composed of flow nodes and sequential flows connected between the flow nodes. It is understood that different flow nodes may have different names, such as StartEvent_1 and EFFP_1.

Step S102, executing the flow template, generating a flow instance, and recording according to preset recording information in the process of generating the flow instance to obtain an operation log.

In this solution, the flow templates are executed, i.e. the flow nodes are executed one by one according to the sequential flow in the flow templates. And generating a flow instance, namely, an instance of completing the processing of a task by using the flow template of the case number. Specifically, in the process of executing the flow template, each time triggering generates a flow instance, each time the flow node executes, a node instance is generated. Each node instance log is stored.

In the scheme, in the process of generating the flow instance, the running log is obtained by recording according to preset recording information. The preset record information may include each flow node: node instance ID, flow template version ID, flow instance ID, main flow instance ID, node name, node type, last node instance ID, last node ID, flow operation start time stamp (accurate to ms), flow operation end time stamp (accurate to ms), flow operation duration (accurate to ms), node specific information, operation exception information, node start time context and task operation status (0: to schedule, 1: in process, 2: waiting, 3: done, -1: failed), etc.

After the above information is recorded for each flow node, the recording of the log of the entire flow instance may be completed.

And step S103, marking and displaying the running log in a flow template in the visual canvas by a preset mark.

Among the information included in the running log, since the label is displayed in the flow template, the context information, the previous flow node, the next flow node, and the like may not be directly displayed, but the running state information of the flow node, such as running success or running failure, needs to be displayed. In addition, the circulation times of each flow node are displayed in the scheme, so that the flow nodes are recorded.

FIG. 3 is a diagram illustrating the effect of running log markup of a flow template in a visualization canvas according to an embodiment of the present application. As shown in fig. 3, a square mark may be displayed on the upper left of each flow node, where the mark may represent different states of operation of the flow node by different colors, and a number may be shown in the mark, to represent the number of cycles of the flow node in the flow instance.

In this scheme, executing the flow template, generating a flow instance, and recording according to preset recording information to obtain an operation log in the process of generating the flow instance, including:

executing the flow template to generate a flow instance ID of the current execution process;

acquiring the circulation times and the circulation types of all flow nodes in the current execution process;

if the first circulation type is the first circulation type, generating a flow node instance ID for each circulation of the flow node, carrying out association record by combining the flow node ID and the flow node instance ID with the flow instance ID, and recording the same upstream flow node ID and the same upstream flow node instance ID of each circulation of the flow node in each circulation;

if the flow node is of the second cycle type, generating a flow node instance ID for each cycle of the flow node, carrying out association record by combining the flow node ID and the flow node instance ID with the flow instance ID, and recording the upstream flow node ID and the upstream flow node instance ID triggered by all the cycles of the flow node outside each cycle.

The Process Template (Process Template) is a model of the workflow, and defines elements such as steps, participants, conditions, rules and the like in the workflow. It is a generic description of a workflow and can be instantiated as a specific workflow instance. The flow template defines the structure and behavior of the workflow, and provides a reusable template that allows similar workflows to be used in different scenarios. The execution is a process of processing data once according to a predetermined branch or a task requirement of configuration, and the execution may be a concept of a certain path formed by a plurality of nodes or a concept of a certain node.

A Process Instance (Process Instance) may be a specific, executable Process created from a Process template. It represents instantiation of a flow template at a particular point in time, by which the abstract flow template is converted into an actual flow that is operational. The flow instance contains all relevant information for executing a particular flow, including the state of the current flow, participants, activity status, data, and execution paths, etc. Each flow instance is independent, has independent execution context and data, and can perform state tracking and control during flow execution.

A process Node (Workflow Node) may be a specific step or activity in a Workflow. Each flow node represents a task, decision point, or event that needs to be performed by a participant or system. The flow nodes may include performing certain operations, waiting for external input, or triggering other related flow nodes. Together they form the execution path and logic of the workflow.

The process node ID is the number of the process node, and as long as the node is unchanged, the process node ID is unchanged.

The process node instance ID is the actual content of each execution of the process node, and each time the process node executes, a process node instance ID is generated.

In this scheme, the loops are divided into two types, one type is a first loop type and the other type is a second loop type. For the first loop type, taking the flow node a and the flow node B as examples, the upstream node instance of each execution instance of the flow node B is a certain execution instance of the flow node a. In this case, the same upstream flow node ID, upstream flow node instance ID for each cycle may be recorded within each cycle.

For the second loop type, taking the flow node a and the flow node B as examples, the first execution instance of the flow node B is a certain execution instance of the flow node a, and then the upstream of each loop execution instance of the flow node B is the last loop execution instance of the flow node B. In this case, the upstream flow node ID and the upstream flow node instance ID triggered by all loops of the flow node may be recorded outside each loop.

According to the scheme, different types of circulation can be distinguished by providing different recording modes for the operation logs of the different types of circulation, so that different operation logs are obtained, different modes of display are carried out based on the logs, and a worker can more intuitively and clearly see the whole process of flow operation.

In this scheme, marking and displaying the running log in the process template in the visual canvas with a preset mark includes:

marking and displaying the running log in a square shape at a preset position of each flow node of the flow template in the visual canvas; wherein, at least two colors of the square mark are used for showing the task running state of the flow node; the numbers in the square marks are used to show the number of cycles of the flow node in the entire flow instance.

Wherein, the square marks can have different colors for representing different running states. For example, each flow node displays its execution state and execution times, and the sequential flow also identifies its execution state, and blocks with different colors represent node states, such as blue represents execution end, red represents exception, etc., so that the execution result is clear at a glance. The number of loops can be displayed directly in the middle of the square mark, or can be displayed by hovering a mouse cursor over the square mark.

Through such setting for the circulation number and the running state of every flow node demonstrate more directly perceivedly, the staff of being convenient for observes, for example when running state is failure, can show as red, then can discover very easily that the unusual flow node appears in operation is which, improves staff's log data analysis efficiency.

Example two

Fig. 4 is a flow chart of a log checking method of a flow example provided in the second embodiment of the present application. As shown in fig. 4, the method specifically comprises the following steps:

step S401, obtaining a design result of a flow template in a visual canvas; the flow template consists of flow nodes and sequential flows connected among the flow nodes;

step S402, executing the flow template, generating a flow instance, and recording according to preset recording information to obtain an operation log in the process of generating the flow instance;

step S403, marking and displaying the running log in a flow template in the visual canvas by a preset mark;

step S404, responding to the checking operation of the running log of the target flow node, and acquiring the target flow node log;

in this scheme, the view operation of the target flow node may be a double-click operation performed on any flow node in the flow Cheng Moban. After the double-click operation, the log of the target flow node, that is, the running log of the target flow node, may be obtained.

Step S405, identifying the data content of each data item in the target process node log, and displaying the data content of each data item according to a preset format.

The data items may include information such as the number of loops, the start time and the end time of operation, and whether the node is running abnormally.

Fig. 5 is a schematic diagram of an operation log of a flow node according to a second embodiment of the present application. As shown in fig. 5, the log is entered by double clicking on the flow node. The node log records the starting time, the ending time, the operation time, the variable, the operation state and the like of the node, if the node is abnormal, the reasons of the abnormal printing are printed. For the flow nodes executed for a plurality of times, a plurality of pieces of data are recorded in the node operation records, and if the data are circulated, each circulation has an operation record.

The embodiment provides a method for checking log data of a target flow node on the basis of the embodiment, which is simple and convenient to operate, can call out a corresponding interface by double-clicking the flow node, is visual in content display, and can comprise a state, a circulation number, a starting time, an ending time, a source node name, an operation duration, an operation state and the like. Through the arrangement, the log data of the flow node can be checked according to the demands of staff, and the problem of poor readability of the display of the text form is avoided.

In some embodiments of the present application, the preset format further includes a backtracking key that is operated by the target flow node each time;

correspondingly, after the data content of each data item is displayed according to a preset format, the method further comprises the steps of:

and responding to the triggering operation of the backtracking key, and performing differential display on the route of the current operation of the target flow node according to the current operation flow instance of the target flow node by using a flow template in the visual canvas.

In combination with the above example, it can be seen that the log data of the illustrated target flow node further includes an operation column, where a backtracking key is displayed in the operation column, that is, after the backtracking key is triggered, the route currently operated by the target flow node may be displayed differently by using the flow template in the visual canvas. The manner of differentiated display can be thickening processing of the flow lines, coloring processing of other colors, flashing processing of other colors, and the like.

Fig. 6 is a schematic diagram showing a differential display of a running route according to the second embodiment of the present application. As shown in fig. 6, the route of the target flow node may be subjected to a thickening process, and/or other routes than the route may be subjected to a process of lightening, for example, a transparency set to 50%, or the like.

By means of the arrangement, the single line running for the target flow node can be displayed in a differentiated mode in a complex flow template, so that a worker can more intuitively determine the specific flow running for the line, and the analysis of the running log is facilitated.

Example III

Fig. 7 is a flow chart of a log viewing method of a flow example provided in the third embodiment of the present application. As shown in fig. 7, the method specifically comprises the following steps:

step S701, obtaining a design result of a flow template in a visualization canvas; the flow template consists of flow nodes and sequential flows connected among the flow nodes;

step S702, executing the flow template, generating a flow instance, and recording according to preset recording information to obtain an operation log in the process of generating the flow instance;

step S703, marking and displaying the running log in a flow template in the visual canvas by a preset mark;

step S704, responding to the checking operation of the target sequential flow operation log, and acquiring the target sequential flow log according to the flow node attached to the target sequential flow;

in this scheme, the viewing operation of the target sequential flow may be a double-click operation performed on any one sequential flow in the streams Cheng Moban. After the double-click operation, the operation log of the target sequential flow can be fetched according to the flow node attached to the target sequential flow.

Step S705, identifying the data content of each data item in the target sequential stream log, and displaying the data content of each data item according to a preset format.

Fig. 8 is a schematic diagram of a log of a sequential flow provided in embodiment three of the present application. As shown in fig. 8, the log is entered by double clicking on the sequential stream. The node log records the start time, running state, etc. of the node, if the node is abnormal, the reasons for the abnormal printing are recorded. For the flow nodes executed for a plurality of times, a plurality of pieces of data are recorded in the node operation records, and if the data are circulated, each circulation has an operation record.

The embodiment provides a method for checking the operation log of the sequential flow on the basis of the embodiment, and the method can provide the log information of the sequential flow for the staff based on the simple operation of the staff, so that the staff can check the operation condition of the sequential flow more intuitively.

In some embodiments of the present application, the preset format further includes a backtracking key that is operated by the target sequential flow each time;

And responding to the triggering operation of the backtracking key, and performing differentiated display on the route of the current running of the target sequence flow according to the current running flow instance of the target sequence flow in the visual canvas.

In combination with the above example, it can be seen that the log data of the displayed target sequential flow further includes an operation column, and a backtracking key is displayed in the operation column, that is, after the backtracking key is triggered, the current running route of the target sequential flow can be displayed in a differentiated manner by using a flow template in the visual canvas. The manner of differentiated display can be thickening processing of the sequential flow process line, coloring processing of other colors, flashing processing of other colors, and the like.

By means of the arrangement, the single line running for the target sequential flow can be displayed in a differentiated mode in a complex flow template, so that a worker can more intuitively determine the specific flow operated by the single line, and the analysis of the operation log is facilitated.

PREFERRED EMBODIMENTS

The present application further provides a preferred embodiment in order to enable a person skilled in the relevant art to more clearly understand the technical solution of the present application.

The invention aims to facilitate staff to acquire data including normal and abnormal information during the operation of a flow instance, so that when the flow instance operates or is simulated to be in error, the current execution circulation route is traced back through the context of each node, the error cause is checked, the flow template design is optimized and the like.

The global execution condition (execution times and states) of each node is displayed in a visual mode, the node dimension is summarized for multiple times, the display form and the flow template are designed to be the same, and the current circulation condition can be backtracked and reproduced according to a certain execution. The process running log is refined to each node, and meanwhile, the attribute of each node can be conveniently compared, so that a worker can obtain the process running state and log data from a plurality of dimensions of whole and local, static and dynamic more completely.

In order to solve the technical problems in the background art, the invention introduces a multi-execution retrospective flow instance log viewing mode which is applied to the flow instance log. The innovation point of the invention is that: the logs are summarized in a canvas form, and the execution times and the states are visually displayed; collecting and layering the running logs for a plurality of times by using nodes; backtracking the travel path by a single execution is supported.

The logs are summarized in a canvas form, and the execution times and the states are visually displayed:

the invention displays the log in the canvas form, and simultaneously displays the execution times and the execution state, thereby more clearly positioning the execution error node.

Summarizing and hierarchically displaying a plurality of operation logs by nodes:

the invention can hierarchically display the logs of the node running for many times and can check the key information of the running time such as the above executed each time.

Supporting backtracking of a path of travel by a single execution

The invention supports to check the execution result of a single route from a certain node, and can accurately locate and eliminate the influence interference of irrelevant paths.

S1: integral flow

S2: flow instance log acquisition step example

Wherein, in step S1:

s11: recording log data;

in the process of executing the flow template, each time triggering generates a flow instance, each time the flow node executes, a node instance is generated. Each node instance log is stored. The detailed storage information is shown in the table.

Node instance running log table

Recording data information
	Node instance ID
Flow template ID
	Flow template version ID
Flow instance ID
	Main flow instance ID
Node ID
	Node name
Node type
	Last node instance ID
Last node ID
	Flow run start time stamp (accurate to ms)
Flow run end timestamp (accurate to ms)
	Flow run time (accurate to ms)
Node specific information
	Operational anomaly information
Node start runtime context
	Task running status (0: to be scheduled, 1: in process, 2: waiting, 3: completed, -1: failed)

S12: a flow instance playback flow;

s1201: entering flow instance playback

When a playback button in the flow instance operation is clicked, the flow instance entire canvas playback information query is executed. The node information list, the sequential flow information list, canvas information, etc. are returned by the flow instance ID request.

The return node information list includes a flow node ID, a flow node name, a status statistic (number of completed states, number of failed states, number of states to be scheduled, number of in-progress states, number of waiting states).

The sequence flow information list includes sequence flow ID, attached flow node ID, whether it is completed.

S1202: checking the state and the execution times;

the flow node status and the number of executions and the sequential flow status can be viewed in the playback page. The status and the number of executions are identified by the return node information list and the sequential flow information list.

S1203: checking execution records

In a single flow node or sequential flow, its execution record may be viewed. Each execution or cycle has a record.

(1) Flow node

And returning multi-cycle instance information, node starting time stamp and sub-instance array information through the flow instance ID and the node ID request. The child instance array information comprises a node instance ID, a node start time stamp, a flow running state and the number of loops.

(2) Sequential flow

And returning the node instance ID, the node start time stamp and the running state through the flow instance ID and the node ID request attached to the sequence flow.

Fig. 9 is a schematic view showing the effect of the circulation process according to the embodiment of the present application. As shown in fig. 9, in the log scenario where the multiple hierarchical exhibition node runs multiple times, if the upstream node of a specific flow node executes multiple times, resulting in multiple execution of a selected flow node, if the flow node itself has multiple instance loops, each run of the flow node triggers a loop. If the loops are in parallel state, the node instances of each loop have the same upstream node instance, and if the loops are in serial state, the whole loop of the flow node can be connected in series through the last upstream node instance.

For example, when the flow node a executes for the first time, b is triggered to execute for the first time, and b performs multi-instance circulation, n execution results are generated. According to different circulation modes, upstream nodes corresponding to multiple node instances of b are different. b, if the loop is parallel, a node instance ID on each node instance of the loop is the node instance generated by the a node; in the tandem process, the last node instance is the node instance of the last flow node b executed in the cyclic order.

S1204: checking the details of each running log;

in a single flow node or sequential flow, its travel log is viewed.

(1) Flow node

And returning flow variable information, additional information and public logs through the flow instance ID request. The public log comprises a node start time stamp, a node end time stamp, the node running time, a source node (last node) name, a flow running state, a flow sequence flow state, a host name, error information and node attribute information.

(2) Sequential flow

And returning flow variable information, a public log and an expression analysis result through the flow instance ID and the node ID request attached to the sequence flow. The public log comprises the end time of the last node attached, the name of the source node (the last node), the running state of the flow, the state of the flow sequence flow, the host name and error information.

S1205: backtracking is performed by a single time;

and returning a flow node information list and a sequence flow information list through the node instance ID request, wherein list information takes the flow instance ID as an end point in the case, passes through the last node instance ID until the last node instance ID is not available, and represents the flow node information list as a starting node if the last node instance ID is not available. The upstream node instance ID of each node is found through the last node instance ID and the last node ID, so that the searching of the whole workflow is completed, and the backtracking function is realized. For example, there are flow nodes a and b, and when performing flow backtracking, the last node instance ID of b is associated with node ID and a, and the node to which the flow node 1 is attached is a, so as to implement backtracking. If there are multiple loops in the flow node, when backtracking a loop, the node instance ID of the loop is used as an entry.

Wherein, in step S2:

s21: designing a flow template;

and the process manager designs a process template by defining process nodes such as events, gateways, activities and the like, and models a complex business process.

S22: generating a flow instance;

after the process template design is completed, a process instance is generated by actually or simulatively executing the process template. Each time a process instance is run, the process instance ID, the process name, the version number, the start time, the end time, the run duration, the status, etc. can be viewed.

S23: viewing global pattern logs

S2301: through the flow instance data line, its playback page is entered.

The page and the flow template design remain consistent, including flow nodes and sequential flows. Each flow node displays its execution state and execution times, the sequence flow also identifies its execution state, and blocks with different colors represent node states, such as blue represents execution end, red represents exception, etc., so that the execution result is clear.

S2302: checking a flow node log;

and entering the operation log by double-clicking the flow node. The node log records the starting time, the ending time, the operation time, the variable, the operation state and the like of the node, if the node is abnormal, the reasons of the abnormal printing are printed. For the flow nodes executed for a plurality of times, a plurality of pieces of data are recorded in the node operation records, and if the data are circulated, each circulation has an operation record.

S2303: viewing the sequential flow log;

the double-click sequence streamline is used for checking the running log, including the starting time, the running state and the like, and if the running state is abnormal, the reasons of the abnormality are printed.

S24: checking a backtracking log;

s2401: entering backtracking mode

And entering a backtracking mode through a backtracking button in the operation of the flow node operation record or the sequential flow operation record, and checking the path execution condition before entering the flow node in the mode.

S2402: checking the log;

by checking the logs of the flow nodes or the sequential flows in the mode, the logs are more refined in the mode, and only the logs under the path are displayed, so that the flow manager can check the execution condition or troubleshoot the abnormal problems.

S2403: exiting the backtracking mode;

the global mode can be returned through the exit function to check the overall running condition.

The invention intuitively and vividly displays the execution result of the flow template, is convenient for a flow manager to check the operation log and match the log check and the flow template functions, and a business person can intuitively check the execution result of each flow node and sequence flow in the flow template design, and the operation log of the flow nodes is expanded and displayed, thereby being convenient for inquiring and locating business abnormal data. The execution record for checking the single-path log is provided, the interference of irrelevant paths can be accurately positioned and eliminated, the positioning of abnormal data is more accurate, and the problem positioning efficiency is improved.

Example IV

Fig. 10 is a schematic structural diagram of a log viewing device of a flow example provided in the fourth embodiment of the present application. As shown in fig. 10, the method specifically includes the following steps:

a flow template obtaining module 1010, configured to obtain a design result of a flow template in the visualization canvas; the flow template consists of flow nodes and sequential flows connected among the flow nodes;

The operation log recording module 1020 is configured to execute the flow template, generate a flow instance, and record according to preset recording information in the process of generating the flow instance to obtain an operation log;

and the running log display module 1030 is used for displaying the running log in a preset mark in a flow template in the visual canvas.

The log viewing device of the flow example in the embodiment of the present application may be a device, or may be a component, an integrated circuit, or a chip in a terminal. The device may be a mobile electronic device or a non-mobile electronic device. By way of example, the mobile electronic device may be a cell phone, tablet computer, notebook computer, palm computer, vehicle-mounted electronic device, wearable device, ultra-mobile personal computer (ultra-mobile personal computer, UMPC), netbook or personal digital assistant (personal digital assistant, PDA), etc., and the non-mobile electronic device may be a server, network attached storage (Network Attached Storage, NAS), personal computer (personal computer, PC), television (TV), teller machine or self-service machine, etc., and the embodiments of the present application are not limited in particular.

The log viewing device of the flow instance in the embodiment of the present application may be a device with an operating system. The operating system may be an Android operating system, an iOS operating system, or other possible operating systems, which are not specifically limited in the embodiments of the present application.

The log checking device for the flow example provided in the embodiment of the present application can implement each process implemented by the above method embodiment, and in order to avoid repetition, a description is omitted here.

Example five

In addition, the embodiment of the application also provides a computer device, and fig. 11 is a schematic structural diagram of the computer device provided in the fifth embodiment of the application. The arrangement of the device is shown in fig. 11, the device comprising a memory 111 for storing computer readable instructions and a processor 112 for executing the computer readable instructions, wherein the computer readable instructions when executed by the processor trigger the processor to execute the method.

The methods and/or embodiments of the present application may be implemented as a computer software program. 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 flowcharts. The above-described functions defined in the method of the present application are performed when the computer program is executed by a processing unit.

It should be noted that, the computer readable medium described in the present application may be a computer readable signal medium or a computer readable storage medium, or any combination of the two. The computer readable 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 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 application, however, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, with 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.

Computer program code for carrying out operations of the present application may be written in one or more programming languages, including an object oriented programming language such as Java, smalltalk, C ++ and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the staff computer, partly on the staff computer, as a stand-alone software package, partly on the staff computer and partly on a remote computer or entirely on the remote computer or server. In the case of remote computers, the remote computer may be connected to the personal computer through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computer (for example, through the Internet using an Internet service provider).

The flowchart or block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of devices, methods and computer program products according to various embodiments of the present application. 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 and/or flowchart illustration, and combinations of blocks in the block diagrams and/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.

As another aspect, the present application also provides a computer-readable medium, which 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 computer readable instructions executable by a processor to implement the steps of the methods and/or techniques of the various embodiments of the present application described above.

In a typical configuration of the present application, the terminals, the devices of the services network each include one or more processors (CPUs), input/output interfaces, network interfaces, and memory.

The memory may include volatile memory in a computer-readable medium, random Access Memory (RAM) and/or nonvolatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of computer-readable media.

Computer-readable media include both permanent and non-permanent, removable and non-removable media, and information storage may be implemented by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of storage media for a computer include, but are not limited to, phase change memory (PRAM), static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape disk storage or other magnetic storage devices, or any other non-transmission medium which can be used to store information that can be accessed by a computing device.

In addition, the embodiment of the application also provides a computer program which is stored in the computer equipment, so that the computer equipment executes the method for executing the control code.

It should be noted that the present application may be implemented in software and/or a combination of software and hardware, for example, using Application Specific Integrated Circuits (ASIC), a general purpose computer or any other similar hardware device. In some embodiments, the software programs of the present application may be executed by a processor to implement the above steps or functions. Likewise, the software programs of the present application (including associated data structures) may be stored on a computer readable recording medium, such as RAM memory, magnetic or optical drive or diskette and the like. In addition, some steps or functions of the present application may be implemented in hardware, for example, as circuitry that cooperates with the processor to perform various steps or functions.

It will be evident to those skilled in the art that the present application is not limited to the details of the foregoing illustrative embodiments, and that the present application may be embodied in other specific forms without departing from the spirit or essential characteristics thereof. The present embodiments are, therefore, to be considered in all respects as illustrative and not restrictive, the scope of the application being indicated by the appended claims rather than by the foregoing description, and all changes which come within the meaning and range of equivalency of the claims are therefore intended to be embraced therein. Any reference sign in a claim should not be construed as limiting the claim concerned. Furthermore, it is evident that the word "comprising" does not exclude other elements or steps, and that the singular does not exclude a plurality. A plurality of units or means recited in the apparatus claims can also be implemented by means of one unit or means in software or hardware. The terms first, second, etc. are used to denote a name, but not any particular order.

Claims

1. A method for viewing a log of a process instance, the method comprising:

2. The method of claim 1, wherein after exposing the travel log in a process template in the visualization canvas with a preset markup, the method further comprises:

responding to the checking operation of the target process node operation log, and acquiring the target process node log;

and identifying the data content of each data item in the target process node log, and displaying the data content of each data item according to a preset format.

3. The method of claim 2, wherein the preset format further includes a backtracking key that is operated by the target flow node each time;

4. The method of claim 1, wherein after exposing the travel log in a process template in the visualization canvas with a preset markup, the method further comprises:

responding to the checking operation of the target sequential flow operation log, and acquiring the target sequential flow log according to the flow node attached to the target sequential flow;

and identifying the data content of each data item in the target sequential stream log, and displaying the data content of each data item according to a preset format.

5. The method of claim 4, wherein the preset format further includes a backtracking key for each operation of the target sequential stream;

6. The method according to claim 1, wherein executing the flow template, generating a flow instance, and recording according to preset recording information to obtain a running log during the process of generating the flow instance, includes:

7. The method of claim 1, wherein the running log is presented in a process template in the visualization canvas with a preset markup, comprising:

8. A log viewing device for a process instance, the device comprising:

9. A computer device, the device comprising:

one or more processors; and

a memory storing computer program instructions that, when executed, cause the processor to perform the log view method of a flow instance of any of claims 1-7.

10. A computer readable medium having stored thereon computer program instructions executable by a processor to implement a log view method of a flow instance according to any of claims 1-7.