CN118427413A

CN118427413A - Flow aggregation method, apparatus, readable storage medium and program product

Info

Publication number: CN118427413A
Application number: CN202410529489.5A
Authority: CN
Inventors: 刘海波; 李冰; 石娇; 侯金甫; 刘名一
Original assignee: Kingdee Software China Co Ltd
Current assignee: Kingdee Software China Co Ltd
Priority date: 2024-04-28
Filing date: 2024-04-28
Publication date: 2024-08-02

Abstract

The present application relates to a process aggregation method, apparatus, computer device, computer readable storage medium and computer program product. The method comprises the following steps: acquiring at least two business documents to be processed; for each business document, acquiring a structural tree of the business document, wherein the structural tree comprises a plurality of flow nodes and connection relations thereof; carrying out flow merging on the structure trees of at least two business documents to obtain an aggregation structure tree of at least two business documents; and converting the aggregation structure tree into a renderable format file, wherein the renderable format file is used for rendering and generating an aggregation flow chart of at least two business documents on the visual interface. By adopting the method, the business processes of at least two business documents can be checked in one aggregation flow chart without checking one by one, and the reading efficiency of the processes is improved.

Description

Flow aggregation method, apparatus, readable storage medium and program product

Technical Field

The present application relates to the field of computer technology, and in particular, to a flow aggregation method, a flow aggregation apparatus, a computer device, a computer readable storage medium, and a computer program product.

Background

A business process is a collection of related structured actions or activities that have a specific purpose to produce a specific service or product to meet the needs of a user. With the development of information technology, more and more enterprises improve product and service quality by managing business processes.

Through managing the business process, the enterprise can check the execution path of the business process, and conveniently know the actual execution process of the business process, so as to analyze, evaluate, improve and the like the execution condition of the business process. However, when managing the business processes, the processes of different businesses need to be checked respectively, which results in low process review efficiency.

Disclosure of Invention

In view of the foregoing, it is desirable to provide a flow aggregation method, apparatus, computer device, computer-readable storage medium, and computer program product that can improve the efficiency of flow review.

The application provides a flow polymerization method, which comprises the following steps:

Acquiring at least two business documents to be processed;

For each business document, acquiring a structural tree of the business document, wherein the structural tree comprises a plurality of flow nodes and connection relations thereof;

carrying out flow merging on the structure trees of at least two business documents to obtain an aggregation structure tree of at least two business documents;

And converting the aggregation structure tree into a renderable format file, wherein the renderable format file is used for rendering and generating an aggregation flow chart of at least two business documents on the visual interface.

The application also provides a flow aggregation device, which comprises:

the first acquisition module is used for acquiring at least two business documents to be processed;

The second acquisition module is used for acquiring a structural tree of each business document, wherein the structural tree comprises a plurality of flow nodes and connection relations thereof;

The flow aggregation module is used for carrying out flow combination on the structure trees of the at least two business documents to obtain an aggregated structure tree of the at least two business documents;

The structure conversion module is used for converting the aggregation structure tree into a renderable format file, and the renderable format file is used for rendering and generating an aggregation flow chart of at least two business documents on the visual interface.

A computer device comprising a memory storing a computer program and a processor implementing the steps of the above-described flow aggregation method when the processor executes the computer program.

A computer readable storage medium having stored thereon a computer program which when executed by a processor performs the steps of the above-described flow aggregation method.

A computer program product comprising a computer program which, when executed by a processor, implements the steps of the above-described flow aggregation method.

The flow aggregation method, the flow aggregation device, the computer equipment, the computer readable storage medium and the computer program product acquire at least two business documents to be processed; for each business document, acquiring a structural tree of the business document, wherein the structural tree comprises a plurality of flow nodes and connection relations thereof; carrying out flow merging on the structure trees of at least two business documents to obtain an aggregation structure tree of at least two business documents; and converting the aggregation structure tree into a renderable format file, wherein the renderable format file is used for rendering and generating an aggregation flow chart of at least two business documents on the visual interface. In this way, the at least two business documents are combined in the process of the structure tree, so that the aggregation of the processes is realized, the aggregated structure tree obtained by the combination is further converted into the renderable format file, and the business processes of the at least two business documents can be rendered into the same aggregated flow chart when the renderable format file converted from the aggregated structure tree is subsequently used for rendering. Therefore, the business processes of at least two business documents can be checked in one aggregation flow chart without checking one by one, and the process reading efficiency is improved.

Drawings

FIG. 1 is a diagram of an application environment for a flow aggregation method in one embodiment;

FIG. 2 is a flow diagram of a flow aggregation method in one embodiment;

FIG. 3 is a schematic diagram of a virtual node in one embodiment;

FIG. 4 is a schematic diagram of node morphology in one embodiment;

FIG. 5 is a schematic diagram of a node model in one embodiment;

FIG. 6 is a flow diagram illustration of one embodiment;

FIG. 7 is an illustration of an aggregate flow diagram in one embodiment;

FIGS. 8 and 9 are flow add-drop comparison diagrams of an aggregate flow chart in one embodiment;

FIG. 10 is an architecture diagram of a flow aggregation display system in one embodiment;

FIG. 11 is a data flow diagram of a flow aggregation presentation system in one embodiment;

FIG. 12 is a block diagram of a flow aggregation device in one embodiment;

FIG. 13 is a block diagram of a flow aggregation apparatus according to another embodiment;

FIG. 14 is an internal block diagram of a computer device in one embodiment;

fig. 15 is an internal structural view of a computer device in another embodiment.

Detailed Description

The present application will be described in further detail with reference to the drawings and examples, in order to make the objects, technical solutions and advantages of the present application more apparent. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the application.

Referring to fig. 1, fig. 1 is an application environment diagram of a flow aggregation method in one embodiment. The flow aggregation method provided by the embodiment of the application can be applied to an application environment shown in figure 1. Wherein the terminal 102 communicates with the server 104 via a network. The data storage system may store data that the server 104 needs to process. The data storage system may be integrated on the server 104 or may be located on the cloud or other servers.

The terminal 102 may be a smart phone, a tablet computer, a notebook computer, a desktop computer, a smart speaker, a smart watch, an internet of things device, and a portable wearable device, and the internet of things device may be a smart speaker, a smart television, a smart air conditioner, and a smart vehicle device. The portable wearable device may be a smart watch, smart bracelet, headset, or the like.

The server 104 may be a separate physical server or may be a service node in a blockchain system, where a Peer-To-Peer (P2P) network is formed between service nodes, and the P2P protocol is an application layer protocol that runs on top of a transmission control protocol (TCP, transmission Control Protocol) protocol. The server 104 may be a server cluster formed by a plurality of physical servers, and may be a cloud server providing cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content delivery networks (Content Delivery Network, CDN), and basic cloud computing services such as big data and artificial intelligence platforms.

The terminal 102 and the server 104 may be connected by a communication connection manner such as bluetooth, USB (Universal Serial Bus ) or a network, which is not limited in this disclosure.

Both the terminal and the server can be used separately to execute the flow aggregation method provided in the embodiment of the application.

For example, the server obtains at least two business documents to be processed, and for each business document, obtains a structure tree of the business document. The structure tree comprises a plurality of flow nodes and connection relations thereof. And the server performs flow merging on the structure trees of the at least two business documents to obtain an aggregation structure tree of the at least two business documents, and converts the aggregation structure tree into a renderable format file. The renderable format file is used for rendering and generating an aggregation flow chart of at least two business documents on the visual interface. The server receives the renderable format file, renders the renderable format file according to preset rendering parameters, generates an aggregation flow chart of at least two business documents, and displays the aggregation flow chart on a visual interface.

The servers may include a front-end server and a back-end server, which cooperate to perform the flow aggregation method provided in the embodiments of the present application.

For example, the backend server obtains at least two business documents to be processed, and for each business document, obtains a structural tree of the business document. And the back-end server performs flow merging on the structure trees of the at least two business documents to obtain an aggregation structure tree of the at least two business documents, and converts the aggregation structure tree into a renderable format file. The backend server may send the renderable format file to the front-end server. The front-end server receives the renderable format file, renders the renderable format file according to preset rendering parameters, generates an aggregation flow chart of at least two business documents, and displays the aggregation flow chart on a visual interface.

In addition, the terminal and the server may also cooperate to perform the flow aggregation method provided in the embodiment of the present application.

For example, the server obtains at least two business documents to be processed, and for each business document, obtains a structure tree of the business document. And the server performs flow merging on the structure trees of the at least two business documents to obtain an aggregation structure tree of the at least two business documents, and converts the aggregation structure tree into a renderable format file. The server may send the renderable format file to the terminal. The terminal receives the renderable format file, renders the renderable format file according to preset rendering parameters, generates an aggregation flow chart of at least two business documents, and displays the aggregation flow chart on a visual interface.

Referring to fig. 2, fig. 2 is a flow chart illustrating a flow aggregation method in an embodiment. In one embodiment, as shown in fig. 2, a flow aggregation method is provided, which is illustrated by way of example by the server in fig. 1, and includes the following steps:

step S202, at least two business documents to be processed are acquired.

The bill is a carrier for carrying service data, and the service bill refers to a bill with a specific service type, for example, a purchase management, a management payable, a cost association, a compensation bill, a job title, and the like.

In the practical application process, in order to meet business requirements of enterprises or institutions, many different types of business documents are usually generated, and the different types of business documents reflect business information of the enterprises. When business data of an enterprise or an enterprise needs to be managed, a business document to be processed of the enterprise or the enterprise can be obtained, so that the business condition of the enterprise or the enterprise can be known by analyzing the business document to be processed of the enterprise or the enterprise.

The service document to be processed may be a service document submitted by a user, or may be a service document called from a service document library according to a file identifier included in the reference instruction. The business document to be processed can be an electronic version document, or can be a document processed by electronization according to a paper document, and the embodiment of the application is not limited in any way. In addition, the embodiment of the application does not limit the specific number of the acquired business documents to be processed. Based on the actual demands of the users, two or more business documents to be processed can be acquired.

Further, the review instructions may be triggered by the user. For example, when a user wants to review at least two business documents simultaneously, the corresponding review option in the terminal may be clicked. And the terminal generates a reference instruction for at least two business documents according to clicking operation of a user, and sends the reference instruction to the server. The server responds to the reference instruction of at least two business documents to obtain at least two business documents to be processed, wherein the business documents to be processed comprise a series of business processes.

Step S204, for each business document, obtaining a structural tree of the business document.

The structure tree is also called tree, is a nonlinear data structure, and is a set of n (n > =0) finite nodes with hierarchical relationship. The tree includes a parent node, a child node, and a root node. Parent and child nodes are relative concepts. A parent node refers to a node at a higher level in the tree that may have zero or more child nodes. Child nodes refer to nodes located at lower levels in the tree. The parent nodes and child nodes are connected by connecting lines (also called edges) to form a hierarchical structure of the tree. The root node is the starting node of the tree, which has no parent node, and all other nodes are directly or indirectly connected with the root node through edges.

And for each business document, acquiring a structural tree of the business document. The structure tree in the embodiment of the application refers to a set of a plurality of process nodes existing in a tree structure, wherein the set comprises a plurality of process nodes and connection relations thereof, and specifically comprises a plurality of process nodes arranged in sequence, and represents specific execution steps of a service flow in a service bill. Two adjacent flow nodes in the structure tree represent the execution sequence of corresponding execution steps, and in the structure tree of the business document, the father node of each flow node represents the previous execution step of the flow node in the business flow.

For example, for a business document of a job appoint and remove, the structural tree may include a plurality of flow nodes such as democracy recommendation, investigation scheme, discussion decision, public disclosure, etc. The process nodes are arranged in sequence, and each process node is connected with the previous process node through an edge to form a structural tree of the job appoint and remove business document.

The generated structure tree can be stored in a log file or a database of the service system, and the generated structure tree can be taken from the log file or the database of the service system.

It will be appreciated that for each business document, one structural tree may be obtained, and for at least two business documents, at least two structural trees may be obtained.

And S206, carrying out flow combination on the structure trees of the at least two business documents to obtain an aggregation structure tree of the at least two business documents.

When the structure trees of at least two business documents are subjected to flow merging, a merging strategy to be executed can be selected from a plurality of merging strategies, and the structure trees of the at least two business documents are subjected to flow merging, so that an aggregation structure tree of the at least two business documents is obtained.

For example, a plurality of different merging strategies may be preset, and a flow merging manner may be set in the merging strategies, for example, only the root nodes of different structure trees are merged, or merging is started from the first same flow node in different structure trees until the flow nodes do not stop merging at the same time, and so on.

It will be appreciated that the merge strategy to be performed may be more than one, and the aggregate structure tree obtained may be more than one. For example, when the service document to be processed includes the service document A, B, C, D, the first merging policy and the second merging policy may be determined as the merging policy to be executed, the first merging policy is executed on the structure tree of the service document a and the service document B to obtain an aggregate structure tree of the service document a and the service document B, and the second merging policy is executed on the structure tree of the service document C and the service document D to obtain an aggregate structure tree of the service document C and the service document D. Or the first merging strategy can be executed on the structural trees of the service bill A and the service bill B to obtain a first aggregation result, the first merging strategy is executed on the structural trees of the service bill C and the service bill D to obtain a second aggregation result, and the second merging strategy is executed on the first aggregation result and the second aggregation result to obtain the aggregation structural tree of the service bill A, B, C, D.

When the flow combination is carried out on the structure tree, the same flow nodes in different structure trees are determined first. Combining the flow nodes in the structure tree based on the same flow node, and combining the connection relation of the flow nodes in the structure tree based on the same flow node to obtain the aggregation structure tree.

Further, after combining the flow nodes in the structure tree, a combining result is obtained, and the same flow node in the combining result only appears once; when the connection relations of the flow nodes are combined, for each structure tree, the connection relations of the same flow node and other flow nodes are analyzed, and according to the connection relations of the same flow node and other flow nodes in each structure tree, the connection relations of the same flow node and other flow nodes in a combination result are generated, so that an aggregation structure tree is obtained.

For example, the flow nodes a, b, c1, and d1 are included in the structure tree 1, and the flow nodes a, b, c2, and d2 are included in the structure tree 2. When the flows of the structure tree 1 and the structure tree 2 are combined, determining the flow nodes existing in the structure tree 1 and the structure tree 2 as the same flow nodes, namely a and b. When the flow nodes in the structure tree 1 and the structure tree 2 are combined, only one flow node a is reserved, only one flow node b is reserved, and combining results a, b, c1, d1, c2 and d2 of the flow nodes are obtained. When the connection relations of the flow nodes in the structure tree 1 and the structure tree 2 are combined, the connection relations of a, b and c1 and d1 in the structure tree 1 and the connection relations of a, b and c2 and d2 in the structure tree 2 are analyzed, so that the connection relations of a, b and c1, d1, c2 and d2 are generated, and an aggregation structure tree is obtained. In the aggregation structure tree, a is connected to b, b is connected to c1, c2, c1 is connected to d1, and c2 is connected to d2.

It will be appreciated that the aggregate structural tree has and has only one root node, which is the origin of all flow nodes in the aggregate structural tree. The parent nodes of each flow node in the aggregated structural tree are consistent with the parent nodes in the original structural tree. The original structure tree refers to the structure tree generated according to step S204 and participating in the merging of the flow nodes in step S206.

Step S208, converting the aggregation structure tree into a renderable format file.

The renderable format file refers to a file which can be used for rendering and generating visual elements such as graphics, colors and the like on a visual interface, and is used for rendering and generating an aggregation flow chart of at least two business documents on the visual interface. The format may be HTML format, CSS format, JSON format, etc. For example, the renderable format file may be a JSON format string.

The renderable format file is converted from an aggregate structure tree, and contains basic rendering data and structure data of each flow node in the aggregate structure tree. The basic rendering data of the flow node includes node information and node state information of the flow node. For example, the node information may include a name of the flow node, and the node status information may include an approval status of the flow node, such as approved and not approved. For flow nodes that have been approved and not approved, different node states may be identified to render to different colors when rendered. The structure data of the flow node may include node shapes of the flow node, and different node shapes may be represented by different identifiers.

In an embodiment, after the renderable format file is obtained, the renderable format file is sent to a front end, such as a front end server, a terminal, and the like. The front end comprises a visual interface such as a browser, a client and an applet, and according to different built-in renderers, renderable format files can be rendered into aggregation flow charts with different expression forms on the visual interface, so that interaction between users and the visual interface is supported.

The aggregate flow chart may also be referred to as an aggregate flow design chart, an aggregate business flow chart, etc. After the aggregation flow chart is generated, the service flow of at least two service documents can be displayed, and the related functions of the at least two service documents, such as leave-check approval, job task free and the like, are realized.

The number of the polymerization flow charts may be one, two or a plurality. Specifically, the number of aggregation flow diagrams may depend on the number of aggregation structure trees. For example, an aggregate structural tree may be converted into a renderable format file that may be used to render on the visualization interface to generate an aggregate flow chart.

In the flow aggregation method, at least two business documents to be processed are obtained, and the targets required to be subjected to flow aggregation can be accurately positioned according to the consulting requirements. Further, for each business document, a structural tree of the business document is obtained, and the flow nodes and the execution sequence of the business flow in the business document can be accurately determined through a plurality of flow nodes and connection relations thereof contained in the structural tree, so that preparation is made for executing flow merging. And then, the process combination is carried out on the structure tree of the at least two business documents to obtain an aggregation structure tree of the at least two business documents, and the aggregation structure tree comprises the combined process nodes and the connection relations of the at least two business documents, so that the aggregation of the process is finished at the stage of the process nodes, a plurality of flowcharts are not required to be repeatedly rendered for the at least two business documents, the calculation resources can be saved, and the rendering efficiency of the flowcharts of the plurality of business documents is improved. Finally, the aggregation structure tree is converted into a renderable format file, and the renderable format file can render and generate an aggregation flow chart of at least two business documents on a visual interface, so that the business flow of the at least two business documents is rendered into the same flow chart, the business flow of the at least two business documents can be read in one aggregation flow chart without reading one by one, and the reading efficiency of the flow is improved.

In one embodiment, obtaining a structural tree of business documents includes:

determining the service type of the service bill, and inquiring and acquiring a standard structure tree of the service type; matching a service instance corresponding to the service bill from the service instance library, and inquiring and acquiring a flow node to be displayed corresponding to the service instance as the flow node to be displayed of the service bill; and processing the standard structure tree according to the to-be-displayed flow node of the business document to obtain the structure tree of the business document.

In the practical application process, the business types of different enterprises or units are different, and the same enterprise or unit can have various types of business, so that the business types of business documents are various. By way of example, the business document may specifically include: reimbursement sheets, borrowing sheets, expense certification sheets, purchase sheets, sales sheets, job approval sheets, job free approval sheets, personnel scheduling sheets, and the like. Wherein, reimbursement, purchase, sale, position appoint and remove, personnel movement and the like are the service types of the service bill.

Optionally, a standard structure tree of each service type is preset in the server, and the standard structure tree contains all flow nodes of the service type and connection relations thereof. When the structure tree of the service bill is obtained, the service type of the service bill can be determined, the standard structure tree of the service type can be inquired and obtained, and the standard structure tree of the service type is processed to obtain the structure tree of the service bill.

By way of example, the service type to which the service document belongs may be determined from keywords extracted from the service document. For example, "job talking" is a keyword specific to job appoint and remove, and thus, when the keyword of "job talking" is included in the service document, the service type of the service document may be determined to be job appoint and remove; for another example, the "post adjustment" is a document type specific to the manual adjustment, and when the business document contains a keyword of the "post adjustment", the business type of the business document can be determined to be the manual adjustment.

Optionally, keywords characterizing the business document may be extracted from the business document by Optical Character Recognition (OCR) technology and/or Nature Language Processing (NLP) technology; and determining the bill type of the business bill based on the keywords.

In the step, the image data of the business bill can be extracted through OCR technology, the image data can be, for example, a photo or screenshot of the business bill or a video containing the business bill, and the like, then the NLP technology is adopted to analyze the bill image data extracted from the business bill, and the keywords used for representing the characteristics of the business bill are determined; finally, the service type of the service bill can be determined according to the extracted keywords; here, the OCR technology is used to identify image-type business documents, such as pictures, videos, etc., so if the acquired business documents are images, the document image data can be extracted from the business documents by the OCR technology, that is, the information in the business documents is converted from the format of the images into the data and/or text format, and then the keywords can be extracted by the NLP technology; if the acquired business document is in the format of data and/or text, the OCR technology is not needed to identify the business document, and the keywords can be directly extracted through the NLP technology.

For example, a server may have multiple service instances stored therein. The service instance describes basic service information of the service bill and a specific flow to be executed, including a flow node included in the specific flow to be executed. The service instance may be pre-stored in a service instance repository of the server. For example, preprocessing a service bill in advance, analyzing flow nodes contained in the service bill, generating a service instance corresponding to the service bill, and storing the service instance in a service instance library.

When the standard structure tree of the service type is processed, a service instance corresponding to the service bill is matched from a service instance library, a to-be-displayed flow node corresponding to the service instance is inquired and obtained and used as the to-be-displayed flow node of the service bill, and the standard structure tree is processed according to the to-be-displayed flow node of the service bill to obtain the structure tree of the service bill.

The process nodes to be displayed corresponding to the service instance, namely the process nodes included in the process to be executed by the service bill, can be queried and obtained from the service instance library together when the service instance is matched. The obtained flow node to be displayed of the service instance is the flow node to be displayed of the service receipt.

Further, when the standard structure tree is processed according to the flow nodes to be displayed of the service bill, the flow nodes to be displayed of the service bill can be compared with all flow nodes of the service type, the flow nodes to be deleted are determined from all flow nodes according to the comparison result, and the flow nodes to be deleted in the standard structure tree are deleted, so that the structure tree of the service bill is obtained.

In one embodiment, the process of merging the structure tree of at least two business documents to obtain an aggregate structure tree of at least two business documents includes:

Determining the service type of each service bill; and executing a first merging strategy on the structure tree of the business documents with the same business type, and executing a second merging strategy on the structure tree of the business documents with different business types to obtain an aggregation structure tree of at least two business documents.

It can be understood that at least two business documents participating in aggregation can be business documents of the same business type, can be business documents of different business types, can also comprise business documents of the same business type, and also comprise business documents of different types. Specifically, a first merge policy may be executed on the structure tree of service documents of the same service type, and a second merge policy may be executed on the structure tree of service documents of different service types.

Wherein the first merge policy may be different from the second merge policy, and the different merge policies may be performed by invoking merge interfaces of different parameters. For example, a first merge policy may be to begin merging from a first identical flow node in a different structure tree until the flow nodes do not cease merging at the same time, and a second merge policy may be to merge only the root node of the different structure tree.

When at least two business documents participating in aggregation include both business documents of the same business type and business documents of different types, a first merging strategy can be executed on the structure tree of the business documents of the same business type to obtain a plurality of merging results which belong to different business types. Optionally, the multiple merging results may be used as multiple aggregation structure trees of at least two service documents, and the second merging policy may be further executed on the multiple merging results to obtain one aggregation structure tree of at least two service documents.

In the above embodiment, the probability that the service documents of the same service type contain the same flow node is higher, that is, there may be more flow nodes combined. The business types are divided for the business documents, different merging strategies are executed based on the business types, and the accuracy of flow aggregation can be effectively improved. For business documents of the same business type, combining as many flow nodes as possible, simplifying the data to be rendered, and improving the rendering efficiency; and for different business documents, the root nodes of the business documents can be combined so that the follow-up rendering can be combined and displayed, and the business documents cannot be excluded because of different business types, so that a user can synchronously review the business processes of different business types.

In one embodiment, converting the aggregate structural tree into a renderable format file includes:

adding virtual nodes in the aggregation structure tree; generating a two-dimensional array of the aggregation structure tree according to the flow nodes and the virtual nodes of the aggregation structure tree; and converting the two-dimensional array of the aggregation structure tree into a renderable format file.

In order to correspond the structure of the aggregation structure tree to the two-dimensional array, virtual nodes are added in the aggregation structure tree. The virtual nodes reflect the structure of the aggregate structure tree and the connection relationship between the flow nodes, for example, the virtual nodes may be necessary lines connecting the flow nodes, and are used to correctly display the nodes in the longitudinal and transverse directions of the flow. Optionally, when the virtual node does not include any line, the virtual node is a blank node.

Referring to fig. 3, fig. 3 is a schematic diagram of a virtual node in one embodiment. For example, the structure analysis may be performed on the aggregate structure tree shown in fig. 3 (a), to obtain the node structure shown in fig. 3 (b), where the flow nodes are parallel to each other and have no intersection. Further, virtual nodes are added to the aggregated structural tree such that the node structure shown in fig. 3 (b) is laterally and longitudinally patched into a structure tree box of m×n (m, n are integers) nodes (flow nodes or virtual nodes), as shown in fig. 3 (c). In 3 (c), the solid line represents a flow node, and the broken line represents an added virtual node.

Further, different identifiers may be used to identify node configurations of the flow nodes and the virtual nodes, as shown in fig. 3 (d), so as to generate a two-dimensional array of the aggregated structural tree according to the identifiers of the flow nodes and the virtual nodes.

The identifier may be designed to contain a plurality of identifications, each of which corresponds one-to-one with a constituent part of the node morphology. For each identifier in the identifier, when the identifier is a first character, the existence of the component corresponding to the identifier is indicated, and when the identifier is a second character, the non-existence of the component corresponding to the identifier is indicated, so that various node forms of the flow node and the virtual node can be identified by the identifier, a node model is generated, and the node model is stored in a server. Alternatively, the first character and the second character may be designed as binary 0 and 1. For example, the first character may be 1 and the second character may be 0.

Referring to fig. 4, fig. 4 is a schematic diagram of node configuration in one embodiment. As shown in fig. 4, the identifier is designed to contain seven identifications of k1, k2, k3, k4, k5, k6, k 7. The correspondence between each identifier and the component of the node configuration is shown in fig. 4. Where k4 represents a specific execution step. If the component corresponding to the identifier exists and the component corresponding to the identifier does not exist and the component corresponding to the identifier is represented by 1, then:

When k4 is 1, the identifier indicates the node shape of the flow node, including specific execution steps. At this time, k3 indicates that the flow node is connected to the parent node, k1 and k2 indicate that the flow node is connected to the plurality of parent nodes, respectively, k5 indicates that the flow node is connected to the child node, and k6 and k7 indicate that the flow node is connected to the plurality of child nodes, respectively.

When k4 is 0, the identifier indicates the node morphology of the virtual node, and no specific execution steps are included. At this time, k1 to k7 represent only the form trend of the virtual nodes.

Optionally, a node model is preset in the server, and the corresponding relation between each node form and the identifier is stored in the node model. Referring to fig. 5, fig. 5 is a schematic diagram of a node model in one embodiment. The node model shown in fig. 5 can be designed by combining the correspondence between each identifier shown in fig. 4 and the component parts of the node form, and using identifiers composed of 0 and 1 to identify various node forms.

In fig. 5, the solid line box includes one node form of the flow node, and the dotted line includes one node form of the virtual node. For example, when k1 to k7 are each 0, the identifier 000000 indicates the node shape of the blank node, i.e., the node shape No. 0 in fig. 5. When k1, k2, k6, k7 are 0, k3, k4, k5 are 1, the identifier 0011100 represents a node configuration of the flow node, which includes specific execution steps and is connected to a child node and a parent node, i.e., node configuration No. 1 in fig. 5. For another example, the node number 16 modality with identifier 0001100 and the node number 18 modality with identifier 0001111 are two possible node modalities of the root node.

Further, a two-dimensional array of the aggregated structural tree is generated based on identifiers of the flow nodes and the virtual nodes. Each array element in the two-dimensional array reflects the position and node morphology of a flow node or virtual node in the aggregate structural tree. For example, when the third row and first column of the two-dimensional array contains the identifier 0011111, it is reflected that a flow node exists in the third row and first column of the aggregation structure tree, and the flow node is a root node connected to two child nodes.

In one embodiment, generating a two-dimensional array of an aggregated structural tree from flow nodes and virtual nodes of the aggregated structural tree comprises:

Determining dimension information to be displayed of the aggregation structure tree according to the flow nodes and the virtual nodes of the aggregation structure tree; and generating a two-dimensional array of the aggregation structure tree according to the flow nodes, the virtual nodes and the dimension information of the aggregation structure tree.

Wherein the dimension information to be displayed includes a height and a width. For example, the height (4) and width (8) of the structure tree box shown in fig. 3 (c) are the height and width to be displayed by the aggregation structure tree in fig. 3 (a).

And determining parent nodes and child nodes corresponding to each flow node by recursively traversing the aggregation structure tree, so as to determine dimension information to be displayed by the aggregation structure tree. The application is not limited to the recursive traversal method, and may be a preamble traversal, a follow-up traversal, or other non-exemplified recursive traversal methods.

In an embodiment, determining the width of the aggregated structure tree to be displayed according to the flow node and the virtual node of the aggregated structure tree may include: setting the initial recursion layer number of recursion traversal to be 1, and setting the recursion layer number to be +1 when traversing to the next child node; and when no next child node can traverse, ending the recursion traversal, and taking the number of recursion layers ending the recursion traversal as the width to be displayed of the aggregation structure tree.

In one embodiment, determining the height of the aggregate structural tree to be displayed according to the flow nodes and the virtual nodes of the aggregate structural tree includes:

determining a flow node with a plurality of sub-nodes in the aggregation structure tree as a merging node; for each structural branch, determining the maximum parallel number of the structural branches according to the flow nodes, the merging nodes and the virtual nodes in the structural branches; and taking the sum of the maximum parallel numbers of all the structural branches in the aggregation structural tree as the height to be displayed by the aggregation structural tree.

Wherein the merge node indicates a collection location of a plurality of parallel flow nodes. By recursively traversing the aggregate structure tree, a flow node where multiple child nodes exist can be determined as a merge node.

It will be appreciated that the aggregate structural tree includes a number of structural branches, with different structural branches reflecting different directions of extension of the same parent node. The plurality of structural branches may be partitioned according to an extension direction of a first merging node in the aggregated structural tree, the first merging node having a plurality of extension directions to partition a plurality of structural branches.

Further, for each structural branch, a maximum number of parallel of the structural branch may be determined according to the flow node, the merge node, and the virtual node in the structural branch. And for the structural branches with merging nodes, taking the number of lines occupied by other flow nodes and virtual nodes except the merging nodes in the structural branches as the maximum parallel number of the structural branches.

In some structure trees with more branches, the father node of one merging node may be another merging node, and the application excludes the parallel nodes when calculating the maximum parallel tree, so that the repeated calculation of the number of lines on the same node in the situation can be avoided.

Taking fig. 3 (a) as an example, the aggregation structure tree shown in fig. 3 (a) includes two structure branches. Wherein the first structural branch starts from the "meeting" flow node and extends to "incumbent talk", "texting", "upper level talk"; the second structural branch starts from the "discussion decision" flow node to the "texting" flow node.

For the first structural branch, the merging nodes 'investigation scheme' and 'before-any public representation' exist, so that when the maximum parallel tree of the first structural branch is calculated, only the number of lines occupied by the child nodes of the 'investigation scheme' and the 'before-any public representation' are calculated, namely the maximum parallel number of the first structural branch is recorded as 3. For the second structural branch, where there is no merge node, the maximum parallel tree for the second structural branch is noted as 1. Thus, the height to be displayed for the polymeric structure tree in fig. 3 (a) is 3+1=4.

Further, a two-dimensional array of the aggregation structure tree is generated according to the flow nodes, the virtual nodes and the dimension information of the aggregation structure tree. The array width of the two-dimensional array is equal to the width to be displayed of the aggregation structure tree, and the array height of the two-dimensional array is equal to the height to be displayed of the aggregation structure tree.

In the above embodiment, by adding the virtual nodes, the original irregular aggregation structure tree is complemented into the regular node structure of m×n nodes, and the node structure of m×n nodes can further generate a two-dimensional array corresponding to the node structure of m×n nodes, where the two-dimensional array contains array elements of integer rows and integer columns, so that the computer equipment can conveniently and quickly read the two-dimensional array in an orderly manner. And the complex graph in the node form is converted into a simple computer binary language, so that the processing efficiency of the computer is effectively improved.

In one embodiment, converting the two-dimensional array of the aggregated structural tree into a renderable format file includes:

And converting the two-dimensional array of the aggregation structure tree into a renderable format file by combining node information and node state information of each flow node in the aggregation structure tree.

For each business document, besides obtaining the structural tree of the business document, node information and node state information of each flow node in the structural tree of the business document can be obtained, and the node information and the node state information of each flow node are converted into a renderable format file together with the two-dimensional array. The node information and the node state information of the flow node can be defined manually in advance and can be synchronously acquired when the structural tree of the business document is acquired, or can be acquired after the structural tree of the business document is acquired, and the application is not limited to the above. The node information may include, for example, a node name, a node description, etc. of the flow node, and the node status information may include, for example, an approval status, such as approved or unapproved, of the flow node.

It can be appreciated that each flow node in the aggregated structure tree has a corresponding array element in the two-dimensional array, and the position of the corresponding array element in the two-dimensional array can be determined according to the position of the flow node in the aggregated structure tree. And determining corresponding array elements in the two-dimensional array for the flow node for which the node information and/or the node state information are acquired, adding the node information and/or the node state information of the flow node to corresponding positions in the two-dimensional array when the two-dimensional array is converted into the renderable format file, and converting the two-dimensional array of the aggregation structure tree into the renderable format file.

The renderable format file not only contains the position, the form and the connection relation of the flow nodes, but also contains some basic information and approval states of the flow nodes, so that differentiated rendering of different approval states is supported. For example, for flow nodes that have been approved and not approved, they may be rendered in different colors.

In the above embodiment, the renderable format file is converted according to the two-dimensional array, wherein array elements of the integer rows and the integer columns are in one-to-one correspondence with the flow nodes and virtual nodes in the supplemented aggregation structure tree, and include a plurality of pieces of information of the aggregation structure tree, the information of the aggregation structure tree is normalized and reduced through the two-dimensional array, the two-dimensional array further combines the node information and the state information to generate the renderable format file, and the front end can read the plurality of pieces of information of the aggregation structure tree only through the renderable file, and distinguish the states of the flow nodes, so that the differentiated rendering of the flow nodes with different state information is supported, and the usability after the flow aggregation is higher.

Referring to fig. 6, fig. 6 is a flow chart diagram of one embodiment. FIG. 7 is an illustration of an aggregation flow diagram in this embodiment.

Generally, when the flow chart is rendered, for the business processes of different business documents, the flow chart 6 (a) and the flow chart 6 (b) shown in fig. 6 are rendered, that is, one flow chart is rendered for each business document, a plurality of work processes are independently displayed, and flow nodes (dashed hatched box parts in the figure) to be skipped are displayed.

The renderable format file obtained by the flow aggregation method of the application can directly generate an aggregation structure diagram as shown in fig. 7 on a visual interface during subsequent rendering. The business processes of different business documents are combined and displayed in the aggregation flow chart by realizing structural branches. The user can read the business processes of different business documents at the same time, effectively improves the reading efficiency of the user, and is convenient for realizing business process comparison among different business documents.

In one embodiment, after the renderable format file is used to render the aggregated flow chart that generates at least two business documents on the visualization interface, further comprising:

Responding to a flow adding and deleting instruction aiming at an aggregation flow chart, and determining a target flow node indicated by the flow adding and deleting instruction and a target service instance corresponding to the target flow node; updating the flow nodes to be displayed corresponding to the target service instance according to the flow adding and deleting instruction, and returning to execute the step of acquiring the structural tree of the service document.

After the aggregation flow chart is rendered, the flow nodes in the aggregation structure tree can be added and deleted rapidly by receiving a user instruction. Referring to fig. 8 and fig. 9 together, fig. 8 and fig. 9 are flow addition and deletion comparison diagrams of an aggregation flow chart in one embodiment.

Alternatively, on the visual interface, all the flow nodes of the service types to which each service document belongs and the flow nodes currently displayed by each service document may be displayed in a discrete form, as shown in fig. 8. The user enters a process add-delete interface named "modify process" as shown in fig. 8 by operating the aggregate flow chart on the visualization interface. The process adding and deleting interface displays the process nodes of the 'job receipt' and the 'job-free receipt' which belong to the 'job appoint and remove' business type. The method comprises the steps that a dark background color is used for representing flow nodes to be displayed, namely, flow nodes to be executed by business documents; and the flow nodes which are not displayed, namely the flow nodes which are not needed to be executed by the business document, are represented by light background colors.

When a user wishes to add or delete a flow in the aggregation structure tree, a flow adding/deleting instruction is issued at the front end through interactive operations such as clicking or touch control, and the flow adding/deleting instruction is used for indicating adding or deleting a target flow node. The front end responds to the flow adding and deleting instruction, and changes the background color of the target flow node in the flow adding and deleting interface so as to inform the user that the instruction is successfully received. And the front end sends the flow adding and deleting instruction to the server, the server receives and responds to the flow adding and deleting instruction, determines a target flow node indicated by the flow adding and deleting instruction and a target service instance corresponding to the target flow node, and updates the flow node to be displayed corresponding to the target service instance in the service instance library according to the target flow node. Specifically, when the flow adding and deleting instruction is a flow adding instruction, adding the target flow node as a flow node to be displayed corresponding to the target service instance; and deleting the target flow node from the flow nodes to be displayed corresponding to the target service instance when the flow deleting instruction is the flow deleting instruction, so as to update the flow nodes to be displayed corresponding to the target service instance. After the update is completed, the step of executing the structure tree for acquiring the business document is returned, i.e. the steps of repeating steps S204 to S208. And further, a new renderable format file is obtained, and a new renderable format file user renders and generates a new aggregation flow chart on the visual interface.

With continued reference to fig. 8, the user may select "announce" in the optional document and the job-free document through a click operation in the process add-delete interface, the front end generates a process add instruction in response to the click operation, sends the process add instruction to the server, and changes the background color of the "announce" node from light to dark, where the modified process add-delete interface is shown in fig. 9 (a). The server receives a flow adding instruction, and in response to the flow adding instruction, adds an 'announced' node to the flow nodes to be displayed of the incumbent document and the job-free document, and finally generates the rendering effect of the new renderable format file at the front end as shown in fig. 9 (b), and the 'announced' node is newly added to two structural branches of the aggregation flow chart.

In the above embodiment, the service instance can be directly adjusted in response to the flow adding and deleting instruction of the user, the node can be visually added and deleted according to the change of the requirement, the adjustment node can be lightened as required, and the aggregation flow chart can be validated and updated immediately after adjustment, so that the active node control of different service scenes is realized.

In one embodiment, after converting the aggregation structure tree into a renderable format file, rendering the renderable format file according to preset rendering parameters, generating an aggregation flow chart of at least two business documents, and displaying the aggregation flow chart on a visual interface.

Wherein the preset rendering parameters may be included in the rendering control, such as encapsulating the preset rendering parameters into the rendering control using vue components. And after receiving the renderable format file, directly calling the rendering control to render the renderable format file, and analyzing the renderable format file to obtain the position, form, node information, node state information and other data of the flow nodes in the aggregation structure tree, and generating the flow nodes corresponding to the node form at the corresponding positions.

The renderable format file comprises information of the business flow of the business bill, and preset rendering parameters are used for determining the display form of the aggregation flow chart. The preset rendering parameters are different, and the display forms of the business processes in the rendered aggregation flow chart are also different. The preset rendering parameters may be user-defined.

Specifically, the preset rendering parameters may include a font style and font size of text, a rendering parameter of a node frame of a flow node, a rendering parameter of a connection stripe for connecting each node frame, a rendering parameter of an arrow for indicating an execution order between node frames, and the like. The rendering parameters of the node frame can comprise background color of the node frame, whether to draw the frame, frame drawing color, frame drawing thickness and the like; rendering parameters of the connection stripes can comprise line drawing colors, line drawing lengths, line drawing thicknesses and the like; the rendering parameters of the arrows may include arrow drawing size, arrow drawing color, arrow drawing style, and the like.

In some cases, the renderable format file includes node state information of the flow node, where the node state information protects an approval state of the flow node, such as approved or not approved. In the preset rendering parameters, different node state information can be designed differently. For example, for an approved flow node, its node box is set to a first background color, and for an unapproved flow node, its node box is set to a second background color that is different from the first background color. The approval states of all the flow nodes are obtained through analyzing the renderable format file, and the flow nodes in different approval states are rendered into different background colors by combining rendering parameters which are designed for different approval states, so that the approval states of the flow nodes are intuitively distinguished.

According to a series of preset rendering parameters, the renderable format file can be rendered, and an aggregation flow chart of at least two business documents is drawn.

The computer device may be configured with a visual interface that graphically presents the functions and operations of the computer program to a user, allowing the user to manipulate icons or menu options on the screen using an input device such as a mouse to select commands, invoke files, launch programs, or perform some other task.

The rendered aggregation flow chart is displayed on a visual interface, so that the execution path of the business flow can be visually displayed, the actual execution process of the business flow can be conveniently known, and the analysis, evaluation and improvement of the execution condition of the business flow can be conveniently carried out. While a general flow chart can only compare different execution paths of the same business document, the aggregate flow chart of the application can compare the execution paths of different business documents.

Through the aggregation flow chart displayed on the visual interface, a user can intuitively review and operate the aggregation flow chart, so that the correlation between business documents can be conveniently known, and the business flows of different business documents can be compared and analyzed.

In the embodiment, the business processes of at least two business documents are rendered on the visual interface in the form of a flow chart, so that the visual display of the business processes can be realized. Furthermore, the renderable format file is converted from an aggregation structure tree, and the aggregation structure tree aggregates the service flows of at least two service documents, so that the renderable format file can display the service flows of at least two service documents in the same aggregation flow chart after rendering. Therefore, the business processes of at least two business documents can be checked in one aggregation flow chart without checking one by one, and the process reading efficiency is improved.

In one embodiment, after the aggregation flow diagram is presented on the visual interface, the method further comprises:

when the adjustment operation for the aggregation flow chart is identified, the preset rendering parameters are updated, and the step of rendering the renderable format file according to the preset rendering parameters is performed back based on the updated preset rendering parameters.

It can be appreciated that the preset rendering operation may be customized by the user in advance, or may be modified by the user in real time. For example, when an adjustment is required to be made to the aggregation flow chart, the user can input an adjustment operation for the position to be adjusted on the visual interface in real time. Adjustment operations include, but are not limited to: clicking, dragging and long-pressing operations on the aggregation flow chart, editing operations on texts in the aggregation flow chart and the like.

For example, the user feels that the node frames in the aggregation flow chart are too small, clicks on corners of the node frames to drag outwards, the terminal identifies a drag operation, updates the length and the width of the node frames in preset rendering parameters in response to the drag operation, re-renders the node frames based on the updated length and width, and generates and displays an aggregation flow chart with larger node frames.

While the general flow chart only supports user viewing, the aggregate flow chart provided by the above embodiment of the application supports user interaction therewith. The aggregation flow chart displayed on the visual interface can receive the adjustment operation of the user in real time, and timely update the preset rendering parameters in response to the adjustment operation, so that the rendering effect is ensured to meet the user requirement. And re-rendering is carried out according to the updated preset rendering parameters, so that the display effect of modulation and modulation is achieved, and the usability of the aggregation flow chart is improved.

When the preset operation for the jump node in the aggregation flow chart is identified, determining the jump link corresponding to the jump node, and displaying the target page corresponding to the jump link on the visual interface.

The jump node is a flow node associated with a jump link.

In some cases, there are some information related to the flow nodes in the aggregation flow chart, which is inconvenient to directly show in the aggregation flow chart, and the information can be saved as a target page, and a jump link is set to be associated with the corresponding flow nodes, and the flow nodes are jump nodes.

Further, a hint may be set for the jumping nodes where a jumping link exists. For example, when the user moves the mouse to the position of the jump node, the mouse cursor morphology changes, or the network address of the jump link is directly displayed.

Alternatively, the preset operation may be a click operation. When the user clicks the jump node, the terminal confirms and identifies the preset operation on the jump node, so as to determine the jump link corresponding to the jump node, and the target page corresponding to the jump link is displayed on the visual interface.

In the above embodiment, the jump link may be associated in the aggregation flowchart, and the information associated with the flow node may be stored in the target interface and associated in the aggregation flowchart in the form of the jump link. Therefore, more information can be fused in the aggregation flow chart, so that the concise display of the aggregation flow chart is realized, and the richness and diversity of the information are ensured.

In a specific embodiment, the method of the present application may be applied in the scene of job appoint and remove. In the prior art, the different position appoint and remove processes can only independently generate the flow chart, and the review and modification are very inconvenient. The application provides a flow aggregation display system which can support aggregation display and instant adjustment of a flow chart.

Referring to fig. 10, fig. 10 is a block diagram of a flow aggregation display system in one embodiment. The architecture of the system comprises three parts, namely a presentation layer, a service layer and a data layer.

The presentation layer can be arranged on the terminal, the service layer and the data layer can be arranged on the server, the data layer can be various databases, and the service layer is provided with bottom data. The service layer relies on the underlying data provided by the data layer to implement flow aggregation. The flow aggregation result is transmitted to a display layer, and is rendered into a flow chart at the display layer, so that visual display is carried out and visual adjustment is supported.

The service layer provides four services including a structure tree arrangement service, a flow merging service, a flow chart data structure conversion service and a flow chart instance modification service:

(1) Structural tree orchestration service:

Referring to fig. 11, fig. 11 is a data flow chart of a flow aggregation display system according to an embodiment.

Taking a business document to be processed as an example of the business document with two positions appoint and remove, when the two business documents are submitted, the service layer firstly executes structure tree arrangement service on each business document to obtain a structure tree of each business document.

The structure tree arrangement service also comprises a query workflow node service and an activity configuration scheme instance query service. The query workflow process node service can query all process nodes of the job position appoint and remove, node information of the process nodes and node approval states, and all the process nodes of the job position appoint and remove form a standard structure tree of the job position appoint and remove. The service for inquiring the instance of the active configuration scheme comprises a service instance matching service which can match the flow nodes to be displayed of the current service document to be processed.

Further, the structural tree arrangement service compares the flow nodes to be displayed of the business document with all the flow nodes of the positions appoint and remove, and performs node deleting operation on the standard structural tree of the position appoint and remove according to the comparison result to obtain the structural tree of the business document. Therefore, the structural tree of two business documents can be obtained through the structural tree arrangement service, and result data is provided for the flow merging service.

(2) Flow combining service:

And after the structural tree arrangement service acquires the structural trees of the two business documents, executing the flow merging service. The flow merging service calls a merging interface, and performs flow merging on the structure tree of the two business documents in a mode of merging the same nodes and stopping merging when meeting different nodes or branches to obtain an aggregation structure tree of the two business documents.

(3) Flow chart data structure conversion service:

The flow chart data structure conversion service can perform structured data conversion on the aggregation structure tree, and convert the aggregation structure tree into a JSON format file which can be directly used by the custom control. JSON format files may be used to render the aggregate flow graph at the presentation layer.

The JSON format file obtained after the service layer executes the flow chart data structure conversion service can be sent to the front-end display layer. The presentation layer comprises a flow custom control rendering module and a flow node visualization adjustment module. The flow custom control rendering module is used for defining the appearance and interaction logic of the flow chart through the custom control packaged by vue, realizing the custom control rendering of the flow chart, obtaining an aggregation flow chart, and carrying out visual display on the aggregation flow chart. In the aggregate flow chart, colors may be used to distinguish approval states of flow nodes. The flow node visual adjustment module can realize zooming and dragging of the aggregation flow chart on a visual interface, associate jump links for the flow nodes, add the flow nodes to expand business information of the aggregation flow chart and the like.

(4) Service instance modification service:

The process nodes in the aggregate flow chart can be dynamically adjusted through the service instance modification service. According to the operation of a user, generating a flow adding and deleting instruction at a display layer, sending the flow adding and deleting instruction to a service layer, calling a service instance modification service by the service layer in response to the flow adding and deleting instruction, and adding or deleting a target flow node indicated by the flow adding and deleting instruction from flow nodes to be displayed of the service instance. The modification of the service instance can affect the query result of the query service of the instance of the active configuration scheme, and after the service instance modification service is executed, a series of steps such as the structure tree arrangement service, the flow merging service, the flow chart data structure conversion service and the like are re-executed until a new aggregation flow chart is rendered, so that the instant adjustment of the flow nodes is realized.

The service layer calls the bottom data in the data layer in the process of providing the service. The data layer provides data support for the service layer in a plurality of links such as inquiring workflow flow nodes, inquiring workflow approval records, matching service instances, modifying service instances and the like.

The parts of the process aggregation display system that are not described in detail can refer to the descriptions in the foregoing process aggregation method, and are not described in detail herein.

According to the flow aggregation display system, the service layer is used for realizing the visual aggregation of the service flows, the display layer is used for realizing the visual display of the aggregation result, and the service flows of different service documents are aggregated into one aggregation structure diagram, so that the progress of the service flows is intuitively tracked, and the rapid comparison and the processing of the service are facilitated. The service support flow node visual adjustment is modified through the service instance to adapt to the service, so that the actual service activities of the flow node and the service document displayed by the aggregation structure diagram are consistent, the accuracy of flow aggregation display is ensured, and the expandability and the adaptation degree of the aggregation flow diagram are improved. The visual adjustment module of the flow node is used for realizing the instant adjustment of the appearance of lines, fonts and the like, and the readability and operability of the aggregation flow chart are improved. For business process processing under multi-company, multi-department, multi-person, multi-post and multi-business scenes, especially for group-type companies and sub-companies, the business is various, and the respective requirements can be well met. The display layer and the service layer can be respectively packaged in the API interface, and the visual aggregation display and the visual adjustment of the service flow can be realized for different service documents by directly calling the API interface, so that the universality is strong.

It should be understood that, although the steps in the flowcharts related to the above embodiments are sequentially shown as indicated by arrows, these steps are not necessarily sequentially performed in the order indicated by the arrows. The steps are not strictly limited to the order of execution unless explicitly recited herein, and the steps may be executed in other orders. Moreover, at least some of the steps in the flowcharts described in the above embodiments may include a plurality of steps or a plurality of stages, which are not necessarily performed at the same time, but may be performed at different times, and the order of the steps or stages is not necessarily performed sequentially, but may be performed alternately or alternately with at least some of the other steps or stages.

Based on the same inventive concept, the embodiment of the application also provides a flow aggregation device for realizing the above related flow aggregation method. The implementation of the solution provided by the apparatus is similar to the implementation described in the above method, so the specific limitation in one or more embodiments of the flow aggregation apparatus provided below may refer to the limitation of the flow aggregation method hereinabove, and will not be repeated herein.

In one embodiment, as shown in fig. 12, there is provided a flow aggregation apparatus, including: a first acquisition module 1201, a second acquisition module 1202, a flow aggregation module 1203, and a structure conversion module 1204, wherein:

A first obtaining module 1201, configured to obtain at least two business documents to be processed;

A second obtaining module 1202, configured to obtain, for each service document, a structure tree of the service document, where the structure tree includes a plurality of flow nodes and connection relationships thereof;

The flow aggregation module 1203 is configured to perform flow merging on the structure trees of the at least two service documents to obtain an aggregated structure tree of the at least two service documents;

The structure conversion module 1204 is configured to convert the aggregate structure tree into a renderable format file, where the renderable format file is configured to render an aggregate flowchart that generates at least two business documents on the visual interface.

In one embodiment, the second acquisition module 1202 is further configured to:

determining the service type of the service bill, inquiring a standard structure tree for acquiring the service type, wherein the standard structure tree comprises all flow nodes of the service type and connection relations of all flow nodes;

matching a service instance corresponding to the service bill from the service instance library, and inquiring and acquiring a flow node to be displayed corresponding to the service instance as the flow node to be displayed of the service bill;

And processing the standard structure tree according to the to-be-displayed flow node of the business document to obtain the structure tree of the business document.

In one embodiment, after the renderable format file is used to render an aggregate flow chart that generates at least two business documents on the visualization interface, the second acquisition module 1202 is further configured to:

Responding to a flow adding and deleting instruction aiming at an aggregation flow chart, and determining a target flow node indicated by the flow adding and deleting instruction and a target service instance corresponding to the target flow node;

Updating the flow nodes to be displayed corresponding to the target service instance according to the flow adding and deleting instruction, and returning to execute the step of acquiring the structural tree of the service document.

In one embodiment, the flow aggregation module 1203 is further configured to:

determining the service type of each service bill;

Executing a first merging strategy on the structure tree of the business documents with the same business type, and executing a second merging strategy on the structure tree of the business documents with different business types to obtain an aggregation structure tree of at least two business documents;

wherein the first merge policy is different from the second merge policy.

In one embodiment, the fabric conversion module 1304 is further configured to:

Adding virtual nodes in the aggregation structure tree, wherein the virtual nodes reflect the structure of the aggregation structure tree and the connection relation among all flow nodes;

Generating a two-dimensional array of the aggregation structure tree according to the flow nodes and the virtual nodes of the aggregation structure tree, wherein each array element in the two-dimensional array reflects the position and the node form of one flow node or virtual node in the aggregation structure tree;

And converting the two-dimensional array of the aggregation structure tree into a renderable format file.

In one embodiment, the structural conversion module 1204 is further configured to:

Determining dimension information to be displayed of the aggregation structure tree according to the flow nodes and the virtual nodes of the aggregation structure tree, wherein the dimension information comprises height and width;

Generating a two-dimensional array of the aggregation structure tree according to the flow node, the virtual node and the dimension information of the aggregation structure tree, wherein the array width of the two-dimensional array is equal to the width to be displayed of the aggregation structure tree, and the array height of the two-dimensional array is equal to the height to be displayed of the aggregation structure tree.

In one embodiment, the aggregation structure tree includes a plurality of structure branches, where different structure branches reflect different extension directions of the same parent node, and the structure conversion module 1204 is further configured to:

Determining a flow node with a plurality of sub-nodes in the aggregation structure tree as a merging node, wherein the merging node indicates the aggregation position of a plurality of parallel flow nodes;

for each structural branch, determining the maximum parallel number of the structural branches according to the flow nodes, the merging nodes and the virtual nodes in the structural branches;

And taking the sum of the maximum parallel numbers of all the structural branches in the aggregation structural tree as the height to be displayed by the aggregation structural tree.

In one embodiment, the second acquisition module 1202 is further configured to:

for each business document, acquiring node information and node state information of each flow node in a structural tree of the business document, wherein the node information comprises names and states of the flow nodes, and the node state information comprises approval information of the flow nodes;

the structure conversion module 1203 is further configured to:

In the flow aggregation device, at least two business documents to be processed are obtained, and the targets required to be subjected to flow aggregation can be accurately positioned according to the consulting requirements. Further, for each business document, a structural tree of the business document is obtained, and the flow nodes and the execution sequence of the business flow in the business document can be accurately determined through a plurality of flow nodes and connection relations thereof contained in the structural tree, so that preparation is made for executing flow merging. And then, the process combination is carried out on the structure tree of the at least two business documents to obtain an aggregation structure tree of the at least two business documents, and the aggregation structure tree comprises the combined process nodes and the connection relations of the at least two business documents, so that the aggregation of the process is finished at the stage of the process nodes, a plurality of flowcharts are not required to be repeatedly rendered for the at least two business documents, the calculation resources can be saved, and the rendering efficiency of the flowcharts of the plurality of business documents is improved. Finally, the aggregation structure tree is converted into a renderable format file, and the renderable format file can render and generate an aggregation flow chart of at least two business documents on a visual interface, so that the business flow of the at least two business documents is rendered into the same flow chart, the business flow of the at least two business documents can be read in one aggregation flow chart without reading one by one, and the reading efficiency of the flow is improved.

In one embodiment, as shown in fig. 13, the flow aggregation apparatus may further include: a render presentation module 1205, a flow adjustment module 1206, and a link jump module 1207, wherein:

The rendering display module 1205 is configured to render the renderable format file according to preset rendering parameters, generate an aggregate flow chart of the at least two service documents, and display the aggregate flow chart on the visual interface;

a flow adjustment module 1206, configured to update the preset rendering parameters when an adjustment operation for the aggregate flow chart is identified, and return to perform the step of rendering the renderable format file according to the preset rendering parameters based on the updated preset rendering parameters;

And the link skip module 1207 is configured to determine a skip link corresponding to a skip node in the aggregate flow chart when a preset operation for the skip node is identified, and display a target page corresponding to the skip link on the visual interface, where the skip node is a flow node associated with the skip link.

According to the flow display device, the first acquisition module 1201 acquires at least two business documents to be processed, and can accurately position the target to be subjected to flow aggregation according to the reference requirement. Further, the second obtaining module 1202 obtains, for each service document, a structure tree of the service document, and can accurately determine a flow node and an execution sequence of a service flow in the service document through a plurality of flow nodes and connection relations thereof included in the structure tree, so as to prepare for executing flow merging. Furthermore, the flow aggregation module 1203 performs flow merging on the structure tree of the at least two service documents to obtain an aggregated structure tree of the at least two service documents, where the aggregated structure tree includes the flow nodes and the connection relations after the merging of the at least two service documents, so that the aggregation of the flow is completed at the stage of the flow nodes, and multiple flow charts do not need to be repeatedly rendered for the at least two service documents, so that computing resources can be saved, and the rendering efficiency of the flow charts of the multiple service documents can be improved. Finally, the structure conversion module 1204 converts the aggregation structure tree into a renderable format file, and the renderable format file can render and generate an aggregation flow chart of at least two business documents on the visual interface, so that the business processes of the at least two business documents are rendered into the same flow chart, the business processes of the at least two business documents can be read in one aggregation flow chart without reading one by one, and the reading efficiency of the processes is improved.

The respective modules in the above-described flow aggregation apparatus may be implemented in whole or in part by software, hardware, and combinations thereof. The above modules may be embedded in hardware or may be independent of a processor in the computer device, or may be stored in software in a memory in the computer device, so that the processor may call and execute operations corresponding to the above modules.

The various modules in the flow display apparatus described above may be implemented in whole or in part by software, hardware, and combinations thereof. The above modules may be embedded in hardware or may be independent of a processor in the computer device, or may be stored in software in a memory in the computer device, so that the processor may call and execute operations corresponding to the above modules.

In one embodiment, a computer device is provided, which may be a server, and the internal structure of which may be as shown in fig. 14. The computer device includes a processor, a memory, an Input/Output interface (I/O) and a communication interface. The processor, the memory and the input/output interface are connected through a system bus, and the communication interface is connected to the system bus through the input/output interface. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, computer programs, and a database. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The database of the computer equipment is used for storing data such as service examples, approval records, node models and the like. The input/output interface of the computer device is used to exchange information between the processor and the external device. The communication interface of the computer device is used for communicating with an external terminal through a network connection. The computer program is executed by a processor to implement a flow aggregation method.

In one embodiment, a computer device is provided, which may be a terminal, and an internal structure diagram thereof may be as shown in fig. 15. The computer device includes a processor, a memory, an input/output interface, a communication interface, a display unit, and an input means. The processor, the memory and the input/output interface are connected through a system bus, and the communication interface, the display unit and the input device are connected to the system bus through the input/output interface. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The input/output interface of the computer device is used to exchange information between the processor and the external device. The communication interface of the computer device is used for carrying out wired or wireless communication with an external terminal, and the wireless mode can be realized through WIFI, a mobile cellular network, NFC (near field communication) or other technologies. The computer program is executed by a processor to implement a flow aggregation method. The display unit of the computer equipment is used for forming a visual picture, and can be a display screen, a projection device or a virtual reality imaging device, wherein the display screen can be a liquid crystal display screen or an electronic ink display screen, the input device of the computer equipment can be a touch layer covered on the display screen, can also be a key, a track ball or a touch pad arranged on a shell of the computer equipment, and can also be an external keyboard, a touch pad or a mouse and the like.

It will be appreciated by persons skilled in the art that the structures shown in fig. 14 and 15 are merely block diagrams of portions of structures associated with aspects of the present application and are not intended to limit the computer apparatus to which aspects of the present application may be applied, and that a particular computer apparatus may include more or less components than those shown, or may combine some of the components, or have a different arrangement of components.

In an embodiment, there is also provided a computer device comprising a memory and a processor, the memory having stored therein a computer program, the processor implementing the steps of the method embodiments described above when the computer program is executed.

In one embodiment, a computer-readable storage medium is provided, storing a computer program which, when executed by a processor, implements the steps of the method embodiments described above.

In an embodiment, a computer program product is provided, comprising a computer program which, when executed by a processor, implements the steps of the method embodiments described above.

It should be noted that, the user information (including but not limited to user equipment information, user personal information, etc.) and the data (including but not limited to data for analysis, stored data, presented data, etc.) related to the present application are information and data authorized by the user or sufficiently authorized by each party, and the collection, use and processing of the related data need to comply with the related laws and regulations and standards of the related country and region.

Those skilled in the art will appreciate that implementing all or part of the above-described methods in accordance with the embodiments may be accomplished by way of a computer program stored on a non-transitory computer readable storage medium, which when executed may comprise the steps of the embodiments of the methods described above. Any reference to memory, database, or other medium used in embodiments provided herein may include at least one of non-volatile and volatile memory. The nonvolatile Memory may include Read-Only Memory (ROM), magnetic tape, floppy disk, flash Memory, optical Memory, high density embedded nonvolatile Memory, resistive random access Memory (ReRAM), magneto-resistive random access Memory (Magnetoresistive Random Access Memory, MRAM), ferroelectric Memory (Ferroelectric Random Access Memory, FRAM), phase change Memory (PHASE CHANGE Memory, PCM), graphene Memory, and the like. Volatile memory can include random access memory (Random Access Memory, RAM) or external cache memory, and the like. By way of illustration, and not limitation, RAM can be in various forms such as static random access memory (Static Random Access Memory, SRAM) or dynamic random access memory (Dynamic Random Access Memory, DRAM), etc. The databases referred to in the embodiments provided herein may include at least one of a relational database and a non-relational database. The non-relational database may include, but is not limited to, a blockchain-based distributed database, and the like. The processor referred to in the embodiments provided in the present application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic unit, a data processing logic unit based on quantum computing, or the like, but is not limited thereto.

The technical features of the above embodiments may be arbitrarily combined, and all possible combinations of the technical features in the above embodiments are not described for brevity of description, however, as long as there is no contradiction between the combinations of the technical features, they should be considered as the scope of the description.

The foregoing examples illustrate only a few embodiments of the application, which are described in detail and are not to be construed as limiting the scope of the application. It should be noted that it will be apparent to those skilled in the art that several variations and modifications can be made without departing from the spirit of the application, which are all within the scope of the application. Accordingly, the scope of the application should be assessed as that of the appended claims.

Claims

1. A process polymerization method, the method comprising:

Acquiring at least two business documents to be processed;

carrying out flow merging on the structure trees of the at least two business documents to obtain an aggregation structure tree of the at least two business documents;

And converting the aggregation structure tree into a renderable format file, wherein the renderable format file is used for rendering and generating an aggregation flow chart of the at least two business documents on a visual interface.

2. The method of claim 1, wherein the obtaining the structural tree of the business document comprises:

Determining the service type of the service bill, inquiring and obtaining a standard structure tree of the service type, wherein the standard structure tree comprises all flow nodes of the service type and connection relations of all flow nodes;

Matching a service instance corresponding to the service bill from a service instance library, inquiring and acquiring a flow node to be displayed corresponding to the service instance as the flow node to be displayed of the service bill;

And processing the standard structure tree according to the flow node to be displayed of the business document to obtain the structure tree of the business document.

3. The method of claim 2, wherein after the renderable format file is used to render the aggregated flow diagram that generated the at least two business documents on a visualization interface, the method further comprises:

responding to a flow adding and deleting instruction aiming at the aggregation flow chart, and determining a target flow node indicated by the flow adding and deleting instruction and a target service instance corresponding to the target flow node;

And updating the flow nodes to be displayed corresponding to the service instance according to the flow adding and deleting instruction, and returning to execute the step of acquiring the structural tree of the service document.

4. The method of claim 1, wherein the merging the structure tree of the at least two business documents to obtain the aggregated structure tree of the at least two business documents comprises:

determining the service type of each service bill;

Executing a first merging strategy on the structure tree of the business documents with the same business type, and executing a second merging strategy on the structure tree of the business documents with different business types to obtain an aggregation structure tree of the at least two business documents;

wherein the first merge policy is different from the second merge policy.

5. The method of claim 1, wherein the converting the aggregate structural tree into a renderable format file comprises:

and converting the two-dimensional array of the aggregation structure tree into the renderable format file.

6. The method of claim 5, wherein generating a two-dimensional array of the aggregated structural tree from flow nodes and virtual nodes of the aggregated structural tree comprises:

determining dimension information to be displayed of the aggregation structure tree according to the flow node and the virtual node of the aggregation structure tree, wherein the dimension information comprises height and width;

7. The method of claim 6, wherein the aggregate structural tree includes a plurality of structural branches, different structural branches reflect different extending directions of a same parent node, and determining, according to flow nodes and virtual nodes of the aggregate structural tree, a height to be displayed by the aggregate structural tree includes:

for each structural branch, determining the maximum parallel number of the structural branch according to a flow node, a merging node and a virtual node in the structural branch;

And taking the sum of the maximum parallel rows of all the structural branches in the aggregation structural tree as the height to be displayed of the aggregation structural tree.

8. The method of claim 5, wherein the method further comprises:

for each business bill, acquiring node information and node state information of each flow node in a structural tree of the business bill, wherein the node information comprises names and states of the flow nodes, and the node state information comprises approval information of the flow nodes;

The converting the two-dimensional array of the aggregated structural tree into the renderable format file includes:

And converting the two-dimensional array of the aggregation structure tree into the renderable format file by combining node information and node state information of each flow node in the aggregation structure tree.

9. The method of any of claims 1-8, wherein after converting the aggregated structural tree to a renderable format file, the method further comprises:

rendering the renderable format file according to preset rendering parameters, generating an aggregation flow chart of the at least two business documents, and displaying the aggregation flow chart on the visual interface;

When the adjustment operation for the aggregation flow chart is identified, updating the preset rendering parameters, and returning to execute the step of rendering the renderable format file according to the preset rendering parameters based on the updated preset rendering parameters;

When the preset operation for the jump node in the aggregation flow chart is identified, determining the jump link corresponding to the jump node, and displaying a target page corresponding to the jump link on the visual interface, wherein the jump node is a flow node associated with the jump link.

10. A flow aggregation apparatus, the apparatus comprising:

The structure conversion module is used for converting the aggregation structure tree into a renderable format file, and the renderable format file is used for rendering and generating an aggregation flow chart of the at least two business documents on the visual interface.

11. A computer device comprising a memory and a processor, the memory storing a computer program, characterized in that the processor implements the steps of the method of any one of claims 1 to 9 when the computer program is executed.

12. A computer readable storage medium, on which a computer program is stored, characterized in that the computer program, when being executed by a processor, implements the steps of the method of any of claims 1 to 9.

13. A computer program product comprising a computer program, characterized in that the computer program, when being executed by a processor, implements the steps of the method of any one of claims 1 to 9.