Data processing method and device, electronic equipment and storage medium

Abstract

The present disclosure relates to a data processing method and device, electronic equipment and storage medium. The method comprises: obtaining process arrangement data of a business process; the process arrangement data is used to describe upstream and downstream relationships of sub-processes in the business process; determining business logic information of the business process according to the process arrangement data; extracting an arrangement structure of sub-processes in the business process from the business logic information, and rendering a process framework diagram recording the arrangement structure; determining connection relationships between sub-processes of the business process according to the business logic information; and performing a relationship filling operation on sub-processes with the connection relationships in the rendered process framework diagram to generate a process diagram of the business process. The method can improve the efficiency of process diagram editing.

Description

Technical Field

[0001] This disclosure relates to the field of computer technology, and more particularly to a data processing method, apparatus, electronic device, storage medium, and computer program product. Background Technology

[0002] With the development of computer technology, process orchestration technology has emerged; for example, by writing corresponding business processes through code, process orchestration data can be obtained to realize the corresponding business logic.

[0003] In related technologies, since business process diagrams cannot be directly obtained from process orchestration data, they are usually manually edited based on the process orchestration data. However, if the process orchestration data involves many nodes, the process of editing the flowchart can be cumbersome, resulting in low efficiency. Summary of the Invention

[0004] This disclosure provides a data processing method, apparatus, electronic device, storage medium, and computer program product to at least solve the problem of low editing efficiency of flowcharts in related technologies. The technical solution of this disclosure is as follows:

[0005] According to a first aspect of the present disclosure, a data processing method is provided, comprising:

[0006] Obtain the process orchestration data of the business process; the process orchestration data is used to describe the upstream and downstream relationships of the sub-processes in the business process;

[0007] Based on the process orchestration data, determine the business logic information of the business process;

[0008] Extract the arrangement structure of sub-processes in the business process from the business logic information, and render a process framework diagram that records the arrangement structure.

[0009] Based on the business logic information, determine the connection relationships between the sub-processes of the business process;

[0010] In the rendered process framework diagram, the sub-processes with the connection relationship are populated to generate the flowchart of the business process.

[0011] In an exemplary embodiment, extracting the arrangement structure of sub-processes in the business process from the business logic information includes:

[0012] Based on the business logic information, determine the initial sub-process of the business process;

[0013] Query the business logic information to determine the downstream sub-process of the initial sub-process, and delete the logic information in the business logic information that takes the initial sub-process as the upstream sub-process, to obtain the deleted business logic information;

[0014] The steps of taking the deleted business logic information as business logic information and taking the downstream sub-process as the initial sub-process, jumping to querying the business logic information, determining the downstream sub-process of the initial sub-process, and deleting the logic information in the business logic information that takes the initial sub-process as the upstream sub-process, to obtain the deleted business logic information, continue until the deleted business logic information is empty.

[0015] Each identified sub-process is treated as a sub-process layer, and the arrangement structure of the sub-processes in the business process is determined based on each sub-process layer.

[0016] In an exemplary embodiment, determining the initial sub-process of the business process based on the business logic information includes:

[0017] Iterate through each piece of the business logic information;

[0018] If the downstream sub-process of the business logic information does not include the upstream sub-process of the currently traversed logic information, the upstream sub-process of the currently traversed logic information is identified as the initial sub-process of the business process; the downstream sub-process of the business logic information includes the downstream sub-process of each piece of logic information of the business logic information.

[0019] In an exemplary embodiment, rendering the flowchart recording the arrangement structure includes:

[0020] Based on the arrangement structure, the position information of the sub-processes in the business process is identified, and the configuration information of the sub-processes in the business process is extracted from the business logic information.

[0021] Based on the location and configuration information of the sub-processes in the business process, the sub-processes in the business process are rendered to obtain a process framework diagram that records the arrangement structure.

[0022] In an exemplary embodiment, identifying the position information of sub-processes in the business process based on the arrangement structure includes:

[0023] By querying the arrangement structure, the layers corresponding to the sub-processes in the business process and the distribution information of the sub-processes in the corresponding layers are obtained.

[0024] The vertical coordinate of the layer corresponding to the sub-process in the business process is identified as the vertical coordinate of the sub-process in the business process, and the horizontal coordinate that matches the distribution information is identified as the horizontal coordinate of the sub-process in the business process.

[0025] The position information of the sub-processes in the business process is obtained by combining the vertical and horizontal coordinates of the sub-processes in the business process.

[0026] In an exemplary embodiment, determining the connection relationship between the sub-processes of the business process based on the business logic information includes:

[0027] Extract the relationships between the sub-processes of the business process from the business logic information;

[0028] The relationships between the sub-processes of the business process are identified as the connection relationships between the sub-processes of the business process.

[0029] In an exemplary embodiment, determining the business logic information of the business process based on the process orchestration data includes:

[0030] From each orchestration data of the process orchestration data, extract the first logical information and the second logical information of the business process; each orchestration data includes at least the configuration information of the upstream sub-process and all downstream sub-processes of the upstream sub-process, the first logical information includes at least the upstream sub-process and a downstream sub-process associated with the upstream sub-process, and the second logical information includes at least the configuration information of the corresponding sub-process;

[0031] The first and second logical information of the business process are combined to obtain the business logic information of the business process.

[0032] According to a second aspect of the present disclosure, a data processing apparatus is provided, comprising:

[0033] The data acquisition unit is configured to acquire process orchestration data of a business process; the process orchestration data is used to describe the upstream and downstream relationships of sub-processes in the business process.

[0034] The information determination unit is configured to execute data orchestration based on the process to determine the business logic information of the business process;

[0035] The structure extraction unit is configured to extract the arrangement structure of the sub-processes in the business process from the business logic information and render a process framework diagram that records the arrangement structure.

[0036] The relationship determination unit is configured to determine the connection relationship between the sub-processes of the business process based on the business logic information.

[0037] The relationship filling unit is configured to perform a relationship filling operation on the sub-processes with the connection relationship in the rendered process framework diagram to generate the flowchart of the business process.

[0038] In an exemplary embodiment, the structure extraction unit is further configured to perform the following steps: determining the initial sub-process of the business process based on the business logic information; querying the business logic information to determine the downstream sub-process of the initial sub-process, and deleting the logic information in the business logic information that has the initial sub-process as its upstream sub-process, to obtain deleted business logic information; using the deleted business logic information as business logic information, and using the downstream sub-process as the initial sub-process, and jumping to the steps of querying the business logic information, determining the downstream sub-process of the initial sub-process, and deleting the logic information in the business logic information that has the initial sub-process as its upstream sub-process, to obtain deleted business logic information, until the deleted business logic information is empty; and treating each determined sub-process as a layer of sub-processes, and determining the arrangement structure of sub-processes in the business process based on each layer of sub-processes.

[0039] In an exemplary embodiment, the structure extraction unit is further configured to traverse each piece of the business logic information; if the downstream sub-process of the business logic information does not include the upstream sub-process of the currently traversed logic information, the upstream sub-process of the currently traversed logic information is identified as the initial sub-process of the business process; the downstream sub-process of the business logic information includes the downstream sub-process of each piece of the business logic information.

[0040] In an exemplary embodiment, the structure extraction unit is further configured to perform actions such as identifying the position information of sub-processes in the business process based on the arrangement structure, extracting configuration information of sub-processes in the business process from the business logic information, and rendering sub-processes in the business process based on the position information and configuration information of sub-processes in the business process to obtain a process framework diagram recording the arrangement structure.

[0041] In an exemplary embodiment, the structure extraction unit is further configured to query the arrangement structure to obtain the layer corresponding to the sub-process in the business process, and the distribution information of the sub-process in the business process in the corresponding layer; identify the vertical coordinate of the layer corresponding to the sub-process in the business process as the vertical coordinate of the sub-process in the business process, and identify the horizontal coordinate matching the distribution information as the horizontal coordinate of the sub-process in the business process; combine the vertical coordinate and horizontal coordinate of the sub-process in the business process to obtain the position information of the sub-process in the business process.

[0042] In an exemplary embodiment, the relationship determination unit is further configured to extract the association relationship between the sub-processes of the business process from the business logic information; and identify the association relationship between the sub-processes of the business process as the connection relationship between the sub-processes of the business process.

[0043] In an exemplary embodiment, the information determining unit is further configured to extract first logical information and second logical information of the business process from each orchestration data of the process orchestration data; each orchestration data includes at least configuration information of an upstream sub-process and all downstream sub-processes of the upstream sub-process; the first logical information includes at least an upstream sub-process and a downstream sub-process associated with the upstream sub-process; the second logical information includes at least configuration information of the corresponding sub-process; and the first logical information and second logical information of the business process are combined to obtain the business logic information of the business process.

[0044] According to a third aspect of the present disclosure, an electronic device is provided, comprising:

[0045] processor;

[0046] Memory used to store the processor's executable instructions;

[0047] The processor is configured to execute the instructions to implement the data processing method as described in any of the preceding claims.

[0048] According to a fourth aspect of the present disclosure, a computer-readable storage medium is provided that, when instructions in the computer-readable storage medium are executed by a processor of an electronic device, enables the electronic device to perform the data processing method as described in any of the preceding claims.

[0049] According to a fifth aspect of the present disclosure, a computer program product is provided, the computer program product including instructions that, when executed by a processor of an electronic device, enable the electronic device to perform the data processing method as described in any of the preceding claims.

[0050] The technical solutions provided by the embodiments of this disclosure have at least the following beneficial effects:

[0051] By acquiring the workflow orchestration data of a business process and determining its business logic information based on this data, the workflow orchestration data describes the upstream and downstream relationships of sub-processes within the business process. Next, the arrangement structure of the sub-processes is extracted from the business logic information, and a flowchart containing this arrangement structure is rendered. Then, based on the business logic information, the connection relationships between the sub-processes are determined. Finally, in the rendered flowchart, relationships are filled in for connected sub-processes to generate the flowchart of the business process. In this way, the business logic information of the business process is automatically determined based on the workflow orchestration data, and a flowchart containing the arrangement structure of the sub-processes is rendered based on this information. Relationship filling is then performed on connected sub-processes in the rendered flowchart, resulting in a flowchart corresponding to the business process. This achieves the goal of automatically generating flowcharts without requiring manual editing, thus simplifying the flowchart editing process and improving editing efficiency.

[0052] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this disclosure. Attached Figure Description

[0053] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure, and are not intended to unduly limit this disclosure.

[0054] Figure 1 This is a flowchart illustrating a data processing method according to an exemplary embodiment.

[0055] Figure 2 This is a schematic diagram of a flowchart according to an exemplary embodiment.

[0056] Figure 3 This is a flowchart illustrating the steps of extracting the arrangement structure of sub-processes in a business process according to an exemplary embodiment.

[0057] Figure 4 This is a flowchart illustrating the steps of determining the location information of a subprocess in a business process according to an exemplary embodiment.

[0058] Figure 5 This is a flowchart illustrating another data processing method according to an exemplary embodiment.

[0059] Figure 6 This is a block diagram illustrating a data processing apparatus according to an exemplary embodiment.

[0060] Figure 7This is a block diagram illustrating an electronic device according to an exemplary embodiment. Detailed Implementation

[0061] To enable those skilled in the art to better understand the technical solutions of this disclosure, the technical solutions in the embodiments of this disclosure will be clearly and completely described below with reference to the accompanying drawings.

[0062] It should be noted that the terms "first," "second," etc., used in the specification, claims, and accompanying drawings of this disclosure are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this disclosure described herein can be implemented in orders other than those illustrated or described herein. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this disclosure. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this disclosure as detailed in the appended claims.

[0063] It should also be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for display, data used for analysis, etc.) involved in this disclosure are all information and data authorized by the user or fully authorized by all parties.

[0064] Figure 1 This is a flowchart illustrating a data processing method according to an exemplary embodiment, such as... Figure 1 As shown, this data processing method is used in a terminal; it is understood that this method can also be applied to a server, and can also be applied to a system including a terminal and a server, and is implemented through interaction between the terminal and the server. The terminal can be, but is not limited to, various personal computers, laptops, smartphones, tablets, etc. The server can be implemented using a standalone server or a server cluster composed of multiple servers. In this exemplary embodiment, the method includes the following steps:

[0065] In step S110, process orchestration data of the business process is obtained; the process orchestration data is used to describe the upstream and downstream relationships of sub-processes in the business process.

[0066] Among them, business processes refer to the processes that enable the corresponding business, such as merchant screening processes, product recall review processes, project review processes, video screening processes, etc.

[0067] In this context, process orchestration data refers to the code data that implements the process orchestration function of a business process, such as DSL (Domain Specific Language) data. Specifically, process orchestration data is used to describe the upstream and downstream relationships of sub-processes within a business process using a preset programming language, which is the DSL.

[0068] It should be noted that the process orchestration data includes multiple orchestration data. Each orchestration data includes at least the configuration information of the upstream subprocess (such as the subprocess identifier and subprocess name) and all the downstream subprocesses of the upstream subprocess. For example, Node_1 (subprocess 1): {display_name (display name): 'Auto-orchestration start node', downstream_processor (downstream subprocess): [['Node_2' (subprocess 2)], ['Node_3' (subprocess 3)]],}.

[0069] The business process includes multiple sub-processes, such as sub-process A, sub-process B, sub-process C, etc. Each sub-process is equivalent to a node. Figure 2 The data includes metrics such as "activity coefficient greater than 0.5" and "online duration greater than 12 hours". Process orchestration data is mainly used to describe the upstream and downstream relationships of sub-processes in a business process. For example, if sub-process A is an upstream sub-process, and sub-processes B and C are downstream sub-processes of sub-process A, it indicates that there is an upstream and downstream relationship between sub-process A and sub-processes B and C.

[0070] It should be noted that the business process involved in this disclosure refers to a business process with one in-degree and multiple out-degrees, that is, except for the initial node and the end node, other nodes have one in-degree port and multiple out-degree ports.

[0071] Specifically, in response to a flowchart editing request for a business process, the terminal retrieves the process orchestration data of that business process from the database, so that a flowchart corresponding to that business process can be automatically generated based on the process orchestration data.

[0072] For example, on a page displaying multiple business processes, the current user selects one of them, such as the merchant selection process, and clicks the edit button. The terminal responds to the current user's operation by generating a flowchart editing request for the business process selected by the current user, and retrieves the process orchestration data of the business process from the database based on the flowchart editing request.

[0073] In step S120, the business logic information of the business process is determined based on the process orchestration data.

[0074] The business logic information is used to record the relationships between sub-processes of a business process. These relationships indicate which sub-process's out-degree port is connected to which sub-process's in-degree port.

[0075] The business logic information includes multiple first logical information pieces and multiple second logical information pieces. Each first logical information piece includes at least an upstream sub-process and a downstream sub-process associated with the upstream sub-process. Each second logical information piece includes at least the configuration information of the corresponding sub-process (such as sub-process identifier, sub-process name, and port information). Therefore, the relationship between two sub-processes can be determined through one first logical information piece, and the relationship between sub-processes of the business process can be determined through multiple first logical information pieces. For example, for the first logical information {source(source sub-process): 'Node_1'(sub-process 1), target(target sub-process): 'Node_2'(sub-process 2), inputPortId(in-degree port identifier): 'Node_2_in_1'(in-degree port 1 of sub-process 2), outputPortId(out-degree port identifier): 'Node_1_out_1'(out-degree port 1 of sub-process 1)}, it can be determined that there is a relationship between Node_1 (sub-process 1) and Node_2 (sub-process 2). In practical scenarios, the first logical information refers to edge information, specifically the edge information between sub-processes in the business process. This includes the source sub-process, the target sub-process, the in-degree port identifier of the target sub-process, and the out-degree port identifier of the source sub-process. For example, the first logical information could be {source(source sub-process): 'Node_1'(sub-process 1), target(target sub-process): 'Node_2'(sub-process 2), inputPortId(in-degree port identifier): 'Node_2_in_1'(in-degree port 1 of sub-process 2), outputPortId(out-degree port identifier): 'Node_1_out_1'(out-degree port 1 of sub-process 1)}, indicating that there is an edge between Node_1 (sub-process 1) and Node_2 (sub-process 2), and that Node_1 (sub-process 1) points to Node_2 (sub-process 2).

[0076] In practical scenarios, the second logical information refers to the sub-process port information, specifically the sub-process port information of the sub-process in the business process, which includes the sub-process identifier, sub-process name, in-degree port identifier, and out-degree port identifier of the corresponding sub-process. For example, the second logical information is {id (subprocess identifier): 'Node_3' (subprocess 3), name (subprocess name): 'Online duration greater than 12 hours', inputPortId (in-degree port identifier): ['Node_3_in_1' (in-degree port 1 of subprocess 3)], outputPortId (out-degree port identifier): ['Node_3_out_1' (out-degree port 1 of subprocess 3), 'Node_3_out_2' (out-degree port 2 of subprocess 3)]}, indicating that the subprocess identifier of the corresponding subprocess is Node_3 (subprocess 3), the subprocess name is online duration greater than 12 hours, the in-degree port identifier is Node_3_in_1 (in-degree port 1 of subprocess 3), and the out-degree port identifiers are Node_3_out_1 (out-degree port 1 of subprocess 3) and Node_3_out_2 (out-degree port 2 of subprocess 3).

[0077] Specifically, the terminal identifies each piece of orchestration data in the process orchestration data to obtain the configuration information (such as subprocess identifier and subprocess name) of all downstream subprocesses and upstream subprocesses of the upstream subprocess; based on the configuration information of all downstream subprocesses and upstream subprocesses of the upstream subprocess, it confirms the relationship between subprocesses in the business process, as well as the configuration information of each subprocess in the business process; based on the relationship between subprocesses in the business process, it confirms multiple first logical information; based on the configuration information of each subprocess in the business process, it confirms multiple second logical information; and combines the multiple first logical information and the multiple second logical information to obtain the business logic information of the business process.

[0078] In step S130, the arrangement structure of sub-processes in the business process is extracted from the business logic information, and a process framework diagram recording the arrangement structure is rendered.

[0079] The arrangement of sub-processes in the business process describes the topological relationship of the sub-processes. Specifically, the first-level sub-process is the starting sub-process of the automatic orchestration, the second-level sub-process is the downstream sub-process of the starting sub-process, the third-level sub-process is the downstream sub-process of the second-level sub-process, and so on, with the last-level sub-process being the ending sub-process of the automatic orchestration. For example, refer to... Figure 2The first-level sub-process is the automatic arrangement start sub-process; the second-level sub-process is "activity coefficient greater than 0.5" and "online duration greater than 12 hours"; the third-level sub-process is the AB experiment (control experiment) operator, grayscale operator, full volume operator and skip operator; the fourth-level sub-process is the review failure and review approval; the fifth-level sub-process is the automatic arrangement end sub-process.

[0080] Among them, the flowchart with the arrangement structure refers to the flowchart where there are no connections between sub-processes, such as removing... Figure 2 The flowchart is obtained by connecting the lines in the diagram. By recording the arranged flowchart framework, the location and configuration information of each sub-process can be clearly seen.

[0081] The first logical information in the business logic information is mainly used to determine the arrangement structure of sub-processes in the business process, and then to determine the position information of the sub-processes in the business process; the second logical information in the business logic information is mainly used to determine the configuration information of the sub-processes in the business process; based on the position information and configuration information of the sub-processes in the business process, the sub-processes in the business process can be rendered on the page.

[0082] Specifically, the terminal determines the hierarchical relationship of the sub-processes in the business process from the business logic information used to record the relationships between the sub-processes in the business process, and determines the arrangement structure of the sub-processes in the business process based on the hierarchical relationship of the sub-processes in the business process; then, according to the arrangement structure, it determines the position information of the sub-processes in the business process, and extracts the configuration information of the sub-processes in the business process from the business logic information; finally, according to the position information of the sub-processes in the business process, it draws the sub-processes at the corresponding positions on the page, and draws the sub-process name, in-degree port and out-degree port of the sub-processes based on the configuration information of the sub-processes in the business process, thereby rendering each sub-process in the business process, and thus obtaining a process framework diagram with a recorded arrangement structure.

[0083] In step S140, the connection relationships between the sub-processes of the business process are determined based on the business logic information.

[0084] The connection relationship between sub-processes in a business process indicates which sub-process is connected to which sub-process in the business process, that is, which sub-process points to which sub-process.

[0085] Specifically, the terminal identifies the relationships between sub-processes of the business process from the business logic information, and uses these relationships as the connection relationships between the sub-processes of the business process.

[0086] In step S150, in the rendered process framework diagram, the sub-processes with connection relationships are populated to generate a flowchart of the business process.

[0087] Among them, a business process flowchart refers to a visual flowchart composed of sub-processes within a business process, such as... Figure 2 The flowchart shown.

[0088] Specifically, based on the connection relationships between sub-processes of the business process, the terminal performs connection operations on sub-processes with corresponding connections in the rendered process framework diagram, thereby obtaining the flowchart of the business process. For example, if there is a connection relationship between the out-degree port of the automatic orchestration starting sub-process and the in-degree port of the sub-process with "online duration greater than 12 hours", then a line is drawn between the out-degree port of the automatic orchestration starting sub-process and the in-degree port of the sub-process with "online duration greater than 12 hours", and then an arrow is drawn at the in-degree port of the sub-process with "online duration greater than 12 hours"; and so on, to obtain... Figure 2 The flowchart shown.

[0089] For example, in a video filtering process, not all videos meet the requirements. A series of conditions must be considered before selecting the videos that meet the criteria, such as video duration, video type, video quality, video recommendation rate, and video popularity. These conditions may involve union or intersection operations, and each condition can be considered a sub-process. After processing through a specified process, only a portion of the videos meet the conditions. If there are multiple conditions (e.g., 1000), manually drawing a flowchart for the video filtering process is extremely difficult. Therefore, this disclosure proposes a data processing method for automatically generating flowcharts. First, the terminal obtains the flow arrangement data (e.g., DSL data) of the video filtering process. This flow arrangement data records the upstream and downstream relationships of the sub-processes in the video filtering process, such as determining video duration first, then video type, and then video quality. Then, the terminal identifies the business logic information from the flow arrangement data used to record the relationships between the sub-processes in the video filtering process, such as which sub-process's out-degree port is connected to which sub-process's in-degree port. Next, the terminal determines the hierarchical relationship of the sub-processes in the video filtering process from the business logic information used to record the relationships between sub-processes in the video filtering process, and determines the arrangement structure of the sub-processes in the video filtering process based on the hierarchical relationship. According to the arrangement structure, it determines the position information (such as horizontal and vertical coordinates) of the sub-processes in the video filtering process, and extracts the configuration information (such as sub-process identifier, sub-process name, port information, etc.) of the sub-processes in the video filtering process from the business logic information. Finally, based on the position information of the sub-processes in the video filtering process, it draws the sub-processes at the corresponding positions on the page, and based on the view... The configuration information of the sub-processes in the video filtering process is used to draw the sub-process name, in-degree port, and out-degree port of each sub-process, thereby rendering each sub-process in the video filtering process and obtaining a process framework diagram that records the arrangement structure of the video filtering process. From the business logic information used to record the relationship between the sub-processes in the video filtering process, the relationship between the sub-processes in the video filtering process is extracted as the connection relationship between the sub-processes in the video filtering process. Based on the connection relationship between the sub-processes in the video filtering process, the sub-processes with corresponding connection relationships are connected in the rendered process framework diagram to obtain the flowchart of the video filtering process.

[0090] In the above data processing method, the business process orchestration data is acquired, and the business logic information of the business process is determined based on the orchestration data. The orchestration data describes the upstream and downstream relationships of sub-processes in the business process. Then, the arrangement structure of the sub-processes in the business process is extracted from the business logic information, and a flowchart recording the arrangement structure is rendered. Next, the connection relationships between the sub-processes of the business process are determined based on the business logic information. Finally, in the rendered flowchart, relationship filling operations are performed on the sub-processes with connection relationships to generate the flowchart of the business process. In this way, the business logic information of the business process is automatically determined based on the orchestration data, and a flowchart recording the arrangement structure of the sub-processes in the business process is rendered based on the business logic information. Relationship filling operations are then performed on the sub-processes with connection relationships in the rendered flowchart, thereby obtaining a flowchart corresponding to the business process. This achieves the goal of automatically generating flowcharts, and the entire process does not require manual editing of the flowchart, thus simplifying the flowchart editing process and improving the efficiency of flowchart editing.

[0091] In one exemplary embodiment, such as Figure 3 As shown, in step S130, the arrangement structure of sub-processes in the business process is extracted from the business logic information, which can be achieved through the following steps:

[0092] In step S310, the initial sub-process of the business process is determined based on the business logic information.

[0093] In step S320, the business logic information is queried to determine the downstream sub-process of the initial sub-process, and the logic information in the business logic information that takes the initial sub-process as the upstream sub-process is deleted, so as to obtain the deleted business logic information.

[0094] In step S330, the business logic information after deletion is used as the business logic information, and the downstream sub-process is used as the initial sub-process. The process jumps to query the business logic information, determines the downstream sub-process of the initial sub-process, and deletes the logic information in the business logic information that takes the initial sub-process as the upstream sub-process, thus obtaining the business logic information after deletion. This process continues until the business logic information after deletion is empty.

[0095] In step S340, each determined sub-process is taken as a layer of sub-process, and the arrangement structure of sub-processes in the business process is determined according to each layer of sub-process.

[0096] In this context, the initial sub-process in the business process refers to the automatically orchestrated starting sub-process.

[0097] The business logic information includes multiple first logic information and multiple second logic information. Each first logic information includes at least an upstream sub-process and a downstream sub-process associated with the upstream sub-process. Therefore, querying business logic information here specifically refers to querying the first logic information in the business logic information, and deleting business logic information specifically refers to deleting the first logic information.

[0098] Specifically, the terminal queries the first logical information in the business logic information, which can be represented as [upstream sub-process, downstream sub-process]. If the upstream sub-process in the current first logical information does not exist in any downstream sub-processes in the first logical information, then the upstream sub-process in the current first logical information is identified as the initial sub-process of the business process. Next, the terminal queries the first logical information in the business logic information, identifies the downstream sub-process in the first logical information with the initial sub-process as the upstream sub-process as the downstream sub-process of the initial sub-process, and deletes the first logical information with the initial sub-process as the upstream sub-process, i.e., [initial sub-process, downstream sub-process]. The first logical information after deletion is obtained; the first logical information after deletion is used as the first logical information in the business logic information, and the downstream sub-process is used as the initial sub-process. The query of the first logical information in the business logic information is repeated. The downstream sub-process in the first logical information with the initial sub-process as the upstream sub-process is identified as the downstream sub-process of the initial sub-process, and the first logical information with the initial sub-process as the upstream sub-process in the first logical information is deleted to obtain the first logical information after deletion, until the first logical information after deletion is empty; each determined sub-process is used as a layer of sub-process to obtain each layer of sub-process, and the arrangement structure of sub-processes in the business process is determined according to each layer of sub-process.

[0099] For example, suppose the business logic information includes six first logical pieces of information: [Subprocess A, Subprocess B], [Subprocess A, Subprocess C], [Subprocess A, Subprocess D], [Subprocess B, Subprocess E], [Subprocess C, Subprocess E], and [Subprocess C, Subprocess E]. The terminal iterates through these six first logical pieces of information. If it finds that none of the downstream subprocesses of subprocess A in these six first logical pieces of information exist, it identifies subprocess A as the initial subprocess. Then, it continues to iterate through these six first logical pieces of information, selecting the first logical piece of information with subprocess A as the upstream subprocess. The downstream sub-processes are identified as downstream sub-processes of sub-process A, thus obtaining sub-processes B, C, and D as downstream sub-processes of sub-process A. The first logical information that identifies sub-process A as an upstream sub-process among these six first logical information entries is deleted, namely [sub-process A, sub-process B], [sub-process A, sub-process C], and [sub-process A, sub-process D], resulting in the deleted first logical information, namely [sub-process B, sub-process E], [sub-process C, sub-process E], and [sub-process D, sub-process E]. Then, sub-processes B, C, and D are respectively used as initial sub-processes, and the deleted sub-processes are... The first logical information is used as the first logical information to be queried. The above process is repeated. The downstream sub-processes in the first logical information to be queried, which have sub-processes B, C, and D as upstream sub-processes respectively, are identified as the downstream sub-processes of sub-processes B, C, and D respectively. Thus, the downstream sub-process of sub-process B is sub-process E, the downstream sub-process of sub-process C is sub-process E, and the downstream sub-process of sub-process D is sub-process E. The first logical information to be queried, which has sub-processes B, C, and D as upstream sub-processes respectively, is deleted. That is, [ Subprocesses B, C, D, and E are used to obtain the first logical information after deletion. If the first logical information after deletion is empty, the query stops. Each determined subprocess is taken as a layer of subprocesses, resulting in layers of subprocesses: subprocess A, subprocess B, subprocess C, subprocess D, and subprocess E. The arrangement of subprocesses in the business process is determined based on each layer of subprocesses: the first layer is subprocess A, the second layer is subprocess B, subprocess C, subprocess D, and the third layer is subprocess E.

[0100] In a real-world scenario, multiple first-level logical information pieces within the business logic information are treated as a set of edge information. The terminal then queries this set. If a source node in an edge information piece does not have a target node in any of the edge information pieces within the set, the source node in that edge information piece is identified as the initial node in the business process. The query continues, identifying the target nodes in edge information pieces with the initial node as the source node as downstream nodes of the initial node, and deleting edge information pieces with the initial node as the source node. This process is repeated, using the deleted edge information set as the final set of edge information, and the downstream nodes as the initial nodes. The process continues until the deleted edge information set is empty. Each identified node is treated as a layer of nodes, allowing for the determination of the node arrangement structure in the business process based on these layers. For example, refer to... Figure 2 If the first node identified is the start node of the automatic orchestration, then the start node of the automatic orchestration will be designated as the first-level node; if the second node identified is "activity coefficient greater than 0.5" or "online duration greater than 12 hours", then the nodes of "activity coefficient greater than 0.5" and "online duration greater than 12 hours" will be designated as the second-level node; if the third node identified is the AB experiment operator, grayscale operator, full volume operator, or skip operator, then the nodes of the AB experiment operator, grayscale operator, full volume operator, and skip operator will be designated as the third-level node; if the fourth node identified is the review failure or review approval, then the nodes of the review failure or review approval will be designated as the fourth-level node; if the fifth node identified is the automatic orchestration end node, then the automatic orchestration end node will be designated as the fifth-level node.

[0101] For example, the terminal can obtain the arrangement structure of nodes in the business process through the following steps: (1) The terminal declares an array of final results, result(result) = [], and each item in result(result) is also an array. (2) The terminal iterates through linkList(edge ​​information set). Assuming the current traversal item is item(item), if the source(source node) of item(item) does not exist in the target(target node) of linkList(edge ​​information set), then the node is identified as the initial node. When an initial node is found, the traversal can be stopped. Therefore, at this time, the initial node can be obtained as: Node_1(subprocess 1), and the starting node is added to the result(result) array, that is: result(result) = [['Node_1'(subprocess 1)]]. (3) The terminal starts traversing the linkList (edge ​​information set) again. If the source (source subprocess) of the current traversed item is the same as the ID (identifier) ​​of the starting node: Node_1 (subprocess 1), it is necessary to determine whether the second item of result exists, i.e., whether result[1] (result 1) exists. If it exists, the target (target subprocess) needs to be added to the second item, i.e., result[1].push(target) (meaning to add the target subprocess to the second item of the array). If it does not exist, the target (target subprocess) item is assigned to the second item array, i.e., result[1] = [target] (meaning to assign the target subprocess item to the second item array). At the same time, the found item is deleted from the linkList (edge ​​information set). At this time, result = [['Node_1' (subprocess 1)], ['Node_2' (subprocess 2), 'Node_3' (subprocess 3)] is obtained.Next, iterate through the second array in result, i.e., result[1] (result 1) = ['Node_2' (subprocess 2), 'Node_3' (subprocess 3)]. Iterate through each item in linkList (edge ​​information collection). If the source (source subprocess) of the item is the same as the value of the currently traversed item (assuming the current traversed item is item and the index value is index), then according to the above rules, determine whether result[index+1] (representing the "index value + 1" item of the result) exists; if it exists, then target (target subprocess) needs to be added to the next item, i.e.: result[index+1].push(target) (meaning add the target subprocess to the next item of the result); if it does not exist, then target (target subprocess) needs to be added to the next item. The process is assigned to the next item array, that is: result[index+1] = [target] (meaning that the target subprocess is assigned to the next item array of the result); at the same time, the found item is deleted from the linkList (edge ​​information set); in turn, the last item in the result is traversed, that is, result[result.length-1] (meaning the last item in the result), and the source (source subprocess) item with the same value is found in the LinkList (edge ​​information set), and inserted into the result according to the principle in step (3), and the deletion operation is completed in the linkList (edge ​​information set). When the linkList (edge ​​information set) is empty, it means that all nodes have been processed. (4) After the above operations, the arrangement structure of the nodes in the business process can be obtained.

[0102] The technical solution provided in this disclosure extracts the arrangement structure of sub-processes in the business process from business logic information. This facilitates the automatic rendering of a process framework diagram recording the arrangement structure based on the arrangement structure of the sub-processes in the business process. Combined with the connection relationship between the sub-processes of the business process, the flowchart of the business process is automatically generated. The entire process can achieve automatic generation of the flowchart of the business process without manual intervention, thereby improving the efficiency of flowchart editing.

[0103] In an exemplary embodiment, in step S310, the initial sub-process of the business process is determined based on the business logic information, specifically including the following: traversing each piece of business logic information; if the downstream sub-process of the business logic information does not include the upstream sub-process of the currently traversed logic information, the upstream sub-process of the currently traversed logic information is identified as the initial sub-process of the business process; the downstream sub-process of the business logic information includes the downstream sub-process of each piece of business logic information.

[0104] Specifically, traversing each piece of business logic information refers to traversing each first piece of business logic information.

[0105] Specifically, the terminal sequentially traverses each first logical information in the business logic information; if the downstream sub-processes in each first logical information do not include the upstream sub-processes in the currently traversed first logical information, the upstream sub-processes in the currently traversed first logical information are identified as the initial sub-processes of the business process.

[0106] For example, the terminal sequentially traverses each edge in the edge information set. If the source node in the currently traversed edge does not have a target node in the edge information set, the source node in the currently traversed edge, such as node A, is identified as the initial node in the business process.

[0107] Furthermore, the terminal can sequentially traverse each node port information in the node port information set; if the in-degree port identifier in the currently traversed node port information is empty, the node corresponding to the node identifier in the currently traversed node port information is identified as the initial node in the business process.

[0108] The technical solution provided in this disclosure obtains the initial sub-process of the business process by traversing the business logic information. This facilitates the subsequent traversal of the business logic information based on the initial sub-process of the business process to obtain the arrangement structure of the sub-processes in the business process. The entire process does not require manual viewing of the process arrangement data to determine the arrangement structure of the sub-processes in the business process, thereby simplifying the flowchart editing process and improving the efficiency of flowchart editing.

[0109] In an exemplary embodiment, step S130 renders a process framework diagram with a recorded arrangement structure, specifically including the following: based on the arrangement structure, identifying the position information of sub-processes in the business process, and extracting the configuration information of sub-processes in the business process from the business logic information; based on the position information and configuration information of sub-processes in the business process, rendering the sub-processes in the business process to obtain a process framework diagram with a recorded arrangement structure.

[0110] The location information of a subprocess in a business process refers to the location information of the subprocess in the final generated flowchart, specifically including the horizontal and vertical axes.

[0111] The configuration information of sub-processes in the business process includes, in particular, the sub-process identifier, sub-process name, and port information of the sub-process in the business process.

[0112] Specifically, the terminal determines the horizontal and vertical coordinates of the sub-processes in the business process based on the hierarchical relationship between them, thus obtaining the position information of the sub-processes. Simultaneously, the terminal extracts configuration information from the business logic information that matches the configuration information identifier of the sub-processes, using this as the configuration information of the sub-processes. For example, the terminal extracts the second logic information of the sub-processes from the business logic information, and then extracts the configuration information of the sub-processes from the second logic information. Finally, based on the position information of the sub-processes, the terminal draws the sub-processes at the corresponding positions on the page, and based on the configuration information of the sub-processes, draws their names, in-degree ports, and out-degree ports on the page, thus rendering each sub-process in the business process and obtaining a process framework diagram recording the arrangement structure. Figure 2 The flowchart after removing the connections.

[0113] In real-world scenarios, the terminal identifies edge information from the edge information set to obtain the hierarchical relationship of nodes in the business process. Based on this hierarchical relationship, it determines the arrangement structure of nodes within the business process. Then, based on this arrangement structure, it determines the x and y coordinates of each node, thus obtaining their position information. Simultaneously, based on the node port information from the node port information set, it determines the node port information. Finally, based on the node position information, it draws the nodes at the corresponding locations on the page, for example... Figure 2 The system uses metrics such as "activity coefficient greater than 0.5" and "online duration greater than 12 hours" to indicate activity levels. Based on the node port information of nodes in the business process, the system draws the in-degree and out-degree ports of the node on the page, thereby rendering each node in the business process.

[0114] For example, the terminal renders a graph based on the set of edge information and the set of node port information, such as... Figure 2 The nodes shown are as follows: the first-level node is the automatic orchestration start sub-process; the second-level node is the activity coefficient greater than 0.5 and the online time greater than 12 hours; the third-level node is the AB experiment operator, grayscale operator, full volume operator, and skip operator; the fourth-level node is the review failure and review approval; and the fifth-level node is the automatic orchestration end sub-process.

[0115] The technical solution provided in this disclosure determines the position information of sub-processes in a business process based on the arrangement structure, and extracts the configuration information of the sub-processes in the business process from the business logic information; and renders the sub-processes in the business process based on the position information and configuration information of the sub-processes in the business process to obtain a process framework diagram with the arrangement structure recorded. In this way, the process framework diagram with the arrangement structure recorded is automatically rendered based on the arrangement structure of the sub-processes in the business process and the business logic information of the business process, without the need for manual editing, thereby shortening the editing time of the process framework diagram and improving the efficiency of process diagram editing.

[0116] In one exemplary embodiment, such as Figure 4 As shown, based on the arrangement structure, the location information of sub-processes in the business process is identified, which is specifically achieved through the following steps:

[0117] In step S410, the arrangement structure is queried to obtain the layer corresponding to the sub-process in the business process, and the distribution information of the sub-process in the business process in the corresponding layer.

[0118] The layer corresponding to a sub-process in a business process refers to the level at which the sub-process resides within the business process. For example, refer to... Figure 2 The sub-process "Online time exceeds 12 hours" is at the second level of the business process, and the sub-process "Approved" is at the fourth level of the business process.

[0119] The distribution information of sub-processes within the business process at their corresponding layers describes the layout of these sub-processes within those layers; for example, refer to... Figure 2 The second layer of the business process includes two sub-processes, with "online time exceeding 12 hours" listed second.

[0120] In step S420, the vertical coordinate of the layer corresponding to the sub-process in the business process is identified as the vertical coordinate of the sub-process in the business process, and the horizontal coordinate that matches the distribution information is identified as the horizontal coordinate of the sub-process in the business process.

[0121] Each layer has a default ordinate, which is determined by the layer in which the subprocess is located. Additionally, if a layer contains only one subprocess, its abscissa is set to 0. If a layer contains multiple subprocesses, the number of subprocesses arranged on each side of the central axis is first determined, and then the abscissa of each subprocess is obtained by multiplying by a fixed horizontal spacing (which can be freely set). In other words, the abscissa of the subprocess within the business process, matching its distribution information within the corresponding layer, is used as the abscissa of the subprocess within the business process.

[0122] In step S430, the vertical and horizontal coordinates of the sub-processes in the business process are combined to obtain the position information of the sub-processes in the business process.

[0123] Specifically, the terminal determines the layer corresponding to each sub-process in the business process and the distribution information of the sub-processes within that layer based on the arrangement structure of the sub-processes in the business process; based on the layer corresponding to each sub-process, it queries the correspondence between the layer number and the vertical axis to obtain the vertical axis of the sub-process in the business process; simultaneously, based on the distribution information of the sub-processes within the corresponding layers, it queries the correspondence between the distribution information and the horizontal axis to obtain the horizontal axis of the sub-process in the business process; and based on the vertical and horizontal axes of the sub-processes in the business process, it determines the position information (horizontal axis, vertical axis) of the sub-processes in the business process.

[0124] In a real-world scenario, the terminal iterates through each item in the result array. If the nth item in the array contains only one node, that node is placed at the x-coordinate of 0. If the item has m elements, m / 2 is used to determine how many nodes are arranged on each side of the central axis. Then, by multiplying by a fixed horizontal spacing (which can be freely set), the x-coordinate of each node is obtained. The y-coordinate is the y-coordinate of the node that has been arranged before the nth item. This process is repeated to obtain the x and y coordinates of all nodes in the multiple connecting lines according to the above rules.

[0125] The technical solution provided in this disclosure obtains the layer corresponding to the sub-process in the business process and the distribution information of the sub-process in the corresponding layer by querying the arrangement structure. Then, the vertical coordinate of the layer corresponding to the sub-process in the business process is identified as the vertical coordinate of the sub-process in the business process, and the horizontal coordinate matching the distribution information is identified as the horizontal coordinate of the sub-process in the business process. Finally, the vertical and horizontal coordinates of the sub-process in the business process are combined to obtain the position information of the sub-process in the business process. This facilitates the accurate rendering of the sub-process in the business process based on the position information, making the final flowchart layout more aesthetically pleasing and improving the display effect of the flowchart.

[0126] In an exemplary embodiment, in step S140, the connection relationship between the sub-processes of the business process is determined according to the business logic information, specifically including the following: extracting the association relationship between the sub-processes of the business process from the business logic information; and identifying the association relationship between the sub-processes of the business process as the connection relationship between the sub-processes of the business process.

[0127] Among them, the association relationship is used to indicate which upstream subprocess is associated with which downstream subprocess, and the connection relationship is used to indicate which upstream subprocess is connected to which downstream subprocess.

[0128] Specifically, the terminal extracts first logical information from the business logic information, including at least an upstream sub-process and a downstream sub-process associated with the upstream sub-process; it extracts the association relationship between the sub-processes of the business process from the first logical information, and uses the association relationship between the sub-processes of the business process as the connection relationship between the sub-processes of the business process; for example, the first logical information [sub-process A, sub-process B] indicates that sub-process A is associated with sub-process B, and sub-process A is an upstream sub-process, and sub-process B is a downstream sub-process, thus indicating that sub-process A and sub-process B have a connection relationship.

[0129] Furthermore, in practical scenarios, the terminal can also traverse the edge information in the edge information set and the node port information in the node port information set; if the out-degree port identifier of the source node in the currently traversed edge information is the same as the out-degree port identifier in the first node port information in the node port information set, and the in-degree port identifier of the target node in the currently traversed edge information is the same as the in-degree port identifier in the second node port information in the node port information set, it is determined that there is a connection relationship between the nodes involved in the first node port information and the nodes involved in the second node port information. For example, the terminal sequentially traverses each edge in the edge information set and each node port in the node port information set; if the out-degree port identifier of the source node in the currently traversed edge information is the same as the out-degree port identifier in the first node port information in the node port information set, then the node port information set is traversed again; if the in-degree port identifier of the target node in the currently traversed edge information is the same as the in-degree port identifier in the second node port information in the node port information set, it is determined that there is a connection relationship between the nodes involved in the first node port information and the nodes involved in the second node port information, and the nodes involved in the first node port information point to the nodes involved in the second node port information.

[0130] For example, after the nodes are rendered, the terminal iterates through all edges and all nodes. If the out-degree port of node A matches the outputPortId (out-degree port identifier) ​​of the edge, and the in-degree port of node B matches the inputPortId (in-degree port identifier) ​​of the edge, then a line is drawn between node A and node B, and an arrow is drawn at the in-degree port of node B. This process continues until the entire flowchart is constructed, as shown in the example. Figure 2 As shown.

[0131] The technical solution provided in this disclosure extracts the relationships between sub-processes of a business process from business logic information; identifies these relationships as connection relationships between sub-processes; thus, by comprehensively considering the relationships between sub-processes of a business process, it is beneficial to improve the accuracy of determining the connection relationships between sub-processes, and further improves the accuracy of flowchart editing.

[0132] In an exemplary embodiment, in step S120, the business logic information of the business process is determined based on the process orchestration data, specifically including the following: extracting first logic information and second logic information of the business process from each orchestration data; each orchestration data includes at least the configuration information of the upstream sub-process and all downstream sub-processes of the upstream sub-process, the first logic information includes at least the upstream sub-process and one downstream sub-process associated with the upstream sub-process, and the second logic information includes at least the configuration information of the corresponding sub-process; combining the first logic information and the second logic information of the business process to obtain the business logic information of the business process.

[0133] Specifically, the terminal extracts the configuration information of the upstream sub-process and all downstream sub-processes of the upstream sub-process from each orchestration data of the process orchestration data; based on all downstream sub-processes of the upstream sub-process, it determines each upstream sub-process and one downstream sub-process associated with each upstream sub-process, and then determines multiple first logical information based on each upstream sub-process and one downstream sub-process associated with each upstream sub-process; simultaneously, based on the configuration information of the upstream sub-process, it determines the configuration information of each sub-process, and then determines multiple second logical information based on the configuration information of each sub-process; the multiple first logical information and the multiple second logical information are combined to obtain the business logic information of the business process.

[0134] Furthermore, the terminal can determine each edge information and each node port information in the business process based on each piece of data in the process orchestration data. Each piece of data includes at least the configuration information of the upstream node and the downstream node of the upstream node. Each edge information includes at least the source node, the target node, the out-degree port identifier of the source node, and the in-degree port identifier of the target node. Each node port information includes at least the configuration information, the in-degree port identifier, and the out-degree port identifier of the corresponding node. Based on each edge information in the business process, a set of edge information in the business process is constructed, and based on each node port information in the business process, a set of node port information in the business process is constructed.

[0135] The configuration information of the upstream node includes the node identifier (such as node ID) and node name. The format of each data item in the process orchestration data is as follows: Node_1 (subprocess 1): {display_name (display name): 'auto-orchestration start node', downstream_processor (downstream subprocess): [['Node_2' (subprocess 2)], ['Node_3' (subprocess 3)]],}.

[0136] In each edge information, the out-degree port identifier refers to the out-degree port ID, such as outputPortId (out-degree port identifier); the in-degree port identifier refers to the in-degree port ID, such as inputPortId (in-degree port identifier). The format of each edge information is as follows: {source(source subprocess): 'Node_1' (subprocess 1), target(target subprocess): 'Node_2' (subprocess 2), inputPortId(in-degree port identifier): 'Node_2_in_1' (in-degree port 1 of subprocess 2), outputPortId(out-degree port identifier): 'Node_1_out_1' (out-degree port 1 of subprocess 1)}.

[0137] In this context, the configuration information for each node's port information refers to the node identifier (e.g., node ID) and node name; the in-degree port identifier and out-degree port identifier for each node's port information also refer to the in-degree port ID (i.e., inputPortId) and out-degree port ID (i.e., outputPortId). The format of each node's port information is as follows: {id (subprocess identifier): 'Node_1' (subprocess 1), name (subprocess name): 'auto-orchestration start node', inputPortId (in-degree port identifier): [], outputPortId (out-degree port identifier): ['Node_1_out_1' (out-degree port 1 of subprocess 1), 'Node_1_out_2' (out-degree port 2 of subprocess 1)]}.

[0138] Specifically, the terminal identifies each piece of data in the process orchestration data to obtain the configuration information of the upstream node and the downstream node of the upstream node; based on the configuration information of the upstream node and the downstream node of the upstream node, it determines the source node, the target node, the out-degree port identifier of the source node and the in-degree port identifier of the target node, as well as the configuration information, in-degree port identifier and out-degree port identifier of the node; based on the source node, the target node, the out-degree port identifier of the source node and the in-degree port identifier of the target node, it determines the edge information; based on the configuration information, in-degree port identifier and out-degree port identifier of the node, it determines the node port information; finally, based on the edge information of each edge in the business process, it constructs the edge information set in the business process, and based on the node port information of each node in the business process, it constructs the node port information set in the business process.

[0139] For example, the edge information is obtained through the following steps: (1) The terminal traverses each node, such as traversing each item in the downstream_processor field; first, each item is named parent (representing the parent process), because parent (representing the parent process) is also an array type. Therefore, when traversing parent (representing the parent process), each item is named children (child processes). After obtaining the children (child processes) of each item, the data is reassigned and added to the linkList (edge ​​information collection) array. Declare an object linkItem (edge ​​item), whose structure is as follows: linkItem (edge ​​item) = {source (source subprocess): '', target (target subprocess): '', inputPortId (in-degree port identifier): '', outputPortId (out-degree port identifier): ''}. Before starting the assignment, first define a set of rules: a node has only 1 in-degree port; the number of out-degree ports = the length of the downstream_processor field of the source node. (2) Assign values ​​to each field of the above objects. Assuming that the children (representing subprocesses) being traversed is Node_2 (subprocess 2), the assignment logic for linkItem (edge ​​item) is as follows: source (source subprocess): source node ID (source node identifier), which is Node_1 (subprocess 1); target (target subprocess): children's id (subprocess identifier), which is Node_2 (subprocess 2); inputPortId (in-degree port identifier): the in-degree port ID of the node where the children's id (subprocess identifier) ​​is located; outputPortId (out-degree port identifier): the combination of the source node id and the index value of the children (subprocesses) in the parent (parent process) plus 1. (3) Based on the above rules and examples, process the original data and add each piece of data to linkList (edge ​​information set) to finally obtain the edge information set in the business process.

[0140] For example, node port information is obtained through the following steps: (1) The terminal traverses each node and declares an object NodeItem = {id (identifier): '', name (name): '', inputPortId (in-degree port identifier): [], outputPortId (out-degree port identifier): []}. Before assigning values, a set of rules is defined: the in-degree port ID of the starting node is empty, and the out-degree port ID of the ending node is empty. (2) Assign values ​​to each field of the above objects. Assuming that the item being traversed is Node_1 (subprocess 1), the assignment logic of NodeItem (node ​​item) is as follows: id (identifier): source node ID, which is: Node_1 (subprocess 1); name (name): source node display_name (display name), which is: node 1; inputPortId (in-degree port identifier): the combination of source node ID and in_1 (in-degree port 1), which is: Node_1_in_1 (in-degree port 1 of subprocess 1); outputPortId (out-degree port identifier): assuming that the length of the downstream_processor (downstream subprocess) array is 2, then the outputPortId (out-degree port identifier) ​​is: [Node_1_out_1 (out-degree port 1 of subprocess 1), Node_1_out_2 (out-degree port 2 of subprocess 1)]. (3) Based on the above rules and examples, process the raw data and add each piece of data to nodeList (a collection of node port information) to finally obtain the collection of node port information in the business process.

[0141] The technical solution provided in this disclosure extracts the first and second logical information of the business process from each arrangement data of the process arrangement data, and combines the first and second logical information of the business process to obtain the business logic information of the business process. This facilitates the automatic rendering of the flowchart corresponding to the business process based on the business logic information of the business process. The entire editing process is implemented in an automated manner, without the need for manual editing, thereby shortening the flowchart editing time and further improving the flowchart editing efficiency.

[0142] Figure 5 This is a flowchart illustrating another data processing method according to an exemplary embodiment, such as... Figure 5 As shown, this data processing method is used in a terminal and includes the following steps:

[0143] In step S510, process orchestration data of the business process is obtained; the process orchestration data is used to describe the upstream and downstream relationships of sub-processes in the business process.

[0144] In step S520, the first logical information and the second logical information of the business process are extracted from each orchestration data of the process orchestration data; the first logical information and the second logical information of the business process are combined to obtain the business logic information of the business process.

[0145] Each orchestration data includes at least the configuration information of the upstream subprocess and all downstream subprocesses of the upstream subprocess. The first logical information includes at least the upstream subprocess and one downstream subprocess associated with the upstream subprocess. The second logical information includes at least the configuration information of the corresponding subprocess.

[0146] In step S530, each piece of business logic information is traversed; if the downstream sub-process of the business logic information does not include the upstream sub-process of the currently traversed logic information, the upstream sub-process of the currently traversed logic information is identified as the initial sub-process of the business process.

[0147] Among them, the downstream sub-processes of business logic information include the downstream sub-processes of each piece of business logic information.

[0148] In step S540, the business logic information is queried to determine the downstream sub-process of the initial sub-process, and the logic information in the business logic information that takes the initial sub-process as the upstream sub-process is deleted, so as to obtain the deleted business logic information.

[0149] In step S550, the deleted business logic information is used as the business logic information, and the downstream sub-process is used as the initial sub-process, and the process jumps to step S540 until the deleted business logic information is empty.

[0150] In step S560, each determined sub-process is taken as a layer of sub-process, and the arrangement structure of sub-processes in the business process is determined according to each layer of sub-process.

[0151] In step S570, based on the arrangement structure, the position information of the sub-processes in the business process is identified, and the configuration information of the sub-processes in the business process is extracted from the business logic information; based on the position information and configuration information of the sub-processes in the business process, the sub-processes in the business process are rendered to obtain a process framework diagram with the arrangement structure recorded.

[0152] In step S580, the relationships between sub-processes of the business process are extracted from the business logic information; the relationships between sub-processes of the business process are identified as connection relationships between sub-processes of the business process.

[0153] In step S590, in the rendered process framework diagram, the relationship filling operation is performed on the sub-processes with connection relationships to generate the business process flowchart.

[0154] In the above data processing method, the business logic information of the business process is automatically determined based on the process arrangement data of the business process. Based on the business logic information, a process framework diagram that records the arrangement structure of the sub-processes in the business process is rendered. In the rendered process framework diagram, the relationship filling operation is performed on the sub-processes with connection relationships, thereby obtaining a flowchart corresponding to the business process. This achieves the purpose of automatically generating flowcharts, and the whole process does not require manual editing of the flowchart, thus simplifying the flowchart editing process and improving the editing efficiency of the flowchart.

[0155] To more clearly illustrate the data processing method provided in this disclosure, a specific embodiment is described below. In one embodiment, this disclosure also provides an automatic orchestration method for single-in-degree and multi-out-degree nodes. The terminal obtains the number and name of the out-degree ports of a node based on the downstream node information; obtains the edge information between nodes based on the downstream node information; determines the topological structure relationship of the node arrangement based on the edge relationship; dynamically allocates the node position information based on the topological structure relationship; and connects the nodes, with connections only drawn when the port ID and the connection ID are completely identical; wherein the out-degree ports can be freely expanded. Specifically, this includes the following:

[0156] Step 1: Identify the raw DSL data to obtain edge information.

[0157] Step 2: Identify the raw DSL data to obtain node port information.

[0158] Step 3: Traverse the edge information to determine the initial nodes; and traverse the edge information again to obtain the topological structure relationship of the node arrangement.

[0159] Step 4: Dynamically allocate node position information based on the topological relationship of the node arrangement.

[0160] Step 5: Render the node on the page based on its location and port information.

[0161] Step 6: Render the connections between nodes to obtain the corresponding flowchart, for example... Figure 2 .

[0162] The above-mentioned automatic orchestration method for single-in-degree and multi-out-degree nodes can achieve the following technical effects: (1) It provides a complete solution for the transformation from topological relationship data to the information required for UI (User Interface) rendering: the backend does not need to provide any UI information, and can display the original data in the UI through automatic orchestration capability. Then, the UI information obtained by automatic orchestration capability can be displayed on any page, without having to directly modify the data by looking at tens of thousands of lines of code; (2) The multi-out-degree port processing scheme is closer to the real business scenario: in the real process orchestration scenario, a node must have a corresponding logical relationship in it, and these logical relationships cannot give people an intuitive concept by relying on only one out-degree port. The introduction of multiple ports can use different ports to express the next operation under different business logic results, which is closer to the real business scenario; (3) It supports the custom expansion of the number of out-degree ports: at present, this scheme can be applied to the automatic orchestration scheme of nodes with different numbers of out-degree ports, and can be displayed as a very beautiful UI diagram.

[0163] It should be understood that although the steps in the flowcharts of the embodiments described above are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the embodiments described above may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages of other steps.

[0164] It is understood that the same / similar parts between the various embodiments of the methods described above in this specification can be referred to each other. Each embodiment focuses on the differences from other embodiments, and relevant parts can be referred to the description of other method embodiments.

[0165] Based on the same inventive concept, this disclosure also provides a data processing apparatus for implementing the data processing method described above.

[0166] Figure 6 This is a block diagram illustrating a data processing apparatus according to an exemplary embodiment. (Refer to...) Figure 6 The device includes a data acquisition unit 610, an information determination unit 620, a structure extraction unit 630, a relationship determination unit 640, and a relationship filling unit 650.

[0167] The data acquisition unit 610 is configured to acquire process orchestration data of the business process; the process orchestration data is used to describe the upstream and downstream relationships of sub-processes in the business process.

[0168] The information determination unit 620 is configured to execute data orchestration based on the process to determine the business logic information of the business process.

[0169] The structure extraction unit 630 is configured to extract the arrangement structure of sub-processes in the business process from the business logic information and render a process framework diagram that records the arrangement structure.

[0170] The relationship determination unit 640 is configured to determine the connection relationships between sub-processes of a business process based on business logic information.

[0171] The relationship filling unit 650 is configured to perform relationship filling operations on sub-processes with connection relationships in the rendered process framework diagram to generate a flowchart of the business process.

[0172] In an exemplary embodiment, the structure extraction unit 630 is further configured to perform the following steps: determining the initial sub-process of the business process based on business logic information; querying the business logic information to determine the downstream sub-process of the initial sub-process, and deleting the logic information in the business logic information that has the initial sub-process as its upstream sub-process, to obtain the deleted business logic information; using the deleted business logic information as the business logic information, and using the downstream sub-process as the initial sub-process, and jumping to querying the business logic information to determine the downstream sub-process of the initial sub-process, and deleting the logic information in the business logic information that has the initial sub-process as its upstream sub-process, to obtain the deleted business logic information, until the deleted business logic information is empty; and treating each determined sub-process as a layer of sub-process, and determining the arrangement structure of the sub-processes in the business process based on each layer of sub-processes.

[0173] In an exemplary embodiment, the structure extraction unit 630 is further configured to perform traversal of each piece of business logic information; if the downstream subprocess of the business logic information does not include the upstream subprocess of the currently traversed logic information, the upstream subprocess of the currently traversed logic information is identified as the initial subprocess of the business process; the downstream subprocess of the business logic information includes the downstream subprocess of each piece of business logic information.

[0174] In an exemplary embodiment, the structure extraction unit 630 is further configured to perform the following: determine the position information of the sub-processes in the business process based on the arrangement structure; extract the configuration information of the sub-processes in the business process from the business logic information; and render the sub-processes in the business process based on the position information and configuration information of the sub-processes in the business process to obtain a process framework diagram with the arrangement structure recorded.

[0175] In an exemplary embodiment, the structure extraction unit 630 is further configured to perform a query arrangement structure to obtain the layer corresponding to the sub-process in the business process, and the distribution information of the sub-process in the business process in the corresponding layer; identify the vertical coordinate of the layer corresponding to the sub-process in the business process as the vertical coordinate of the sub-process in the business process, and identify the horizontal coordinate matching the distribution information as the horizontal coordinate of the sub-process in the business process; combine the vertical coordinate and horizontal coordinate of the sub-process in the business process to obtain the position information of the sub-process in the business process.

[0176] In an exemplary embodiment, the relationship determination unit 640 is further configured to extract the association relationship between the sub-processes of the business process from the business logic information; and identify the association relationship between the sub-processes of the business process as the connection relationship between the sub-processes of the business process.

[0177] In an exemplary embodiment, the information determination unit 620 is further configured to extract first logical information and second logical information of the business process from each orchestration data of the process orchestration data; each orchestration data includes at least configuration information of an upstream subprocess and all downstream subprocesses of the upstream subprocess; the first logical information includes at least an upstream subprocess and a downstream subprocess associated with the upstream subprocess; the second logical information includes at least configuration information of the corresponding subprocess; the first logical information and the second logical information of the business process are combined to obtain the business logic information of the business process.

[0178] Regarding the apparatus in the above embodiments, the specific manner in which each module performs its operation has been described in detail in the embodiments related to the method, and will not be elaborated upon here.

[0179] Each module in the aforementioned data processing device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in a computer device, or stored in the memory of a computer device as software, so that the processor can call and execute the operations corresponding to each module.

[0180] Figure 7 This is a block diagram illustrating an electronic device 700 for implementing a data processing method according to an exemplary embodiment. For example, the electronic device 700 may be a mobile phone, computer, digital broadcasting terminal, messaging device, game console, tablet device, medical device, fitness equipment, personal digital assistant, etc.

[0181] Reference Figure 7The electronic device 700 may include one or more of the following components: processing component 702, memory 704, power supply component 706, multimedia component 708, audio component 710, input / output (I / O) interface 712, sensor component 714, and communication component 716.

[0182] Processing component 702 typically controls the overall operation of electronic device 700, such as operations associated with display, telephone calls, data communication, camera operation, and recording operations. Processing component 702 may include one or more processors 720 to execute instructions to complete all or part of the steps of the methods described above. Furthermore, processing component 702 may include one or more modules to facilitate interaction between processing component 702 and other components. For example, processing component 702 may include a multimedia module to facilitate interaction between multimedia component 708 and processing component 702.

[0183] Memory 704 is configured to store various types of data to support the operation of electronic device 700. Examples of such data include instructions for any application or method operating on electronic device 700, contact data, phonebook data, messages, pictures, videos, etc. Memory 704 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, optical disk, or graphene memory.

[0184] Power supply component 706 provides power to various components of electronic device 700. Power supply component 706 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to electronic device 700.

[0185] Multimedia component 708 includes a screen that provides an output interface between the electronic device 700 and the user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touchscreen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensors may sense not only the boundaries of the touch or swipe action but also the duration and pressure associated with the touch or swipe operation. In some embodiments, multimedia component 708 includes a front-facing camera and / or a rear-facing camera. When the electronic device 700 is in an operating mode, such as a shooting mode or a video mode, the front-facing camera and / or the rear-facing camera may receive external multimedia data. Each front-facing camera and rear-facing camera may be a fixed optical lens system or have focal length and optical zoom capabilities.

[0186] Audio component 710 is configured to output and / or input audio signals. For example, audio component 710 includes a microphone (MIC) configured to receive external audio signals when electronic device 700 is in an operating mode, such as call mode, recording mode, and voice recognition mode. The received audio signals may be further stored in memory 704 or transmitted via communication component 716. In some embodiments, audio component 710 also includes a speaker for outputting audio signals.

[0187] I / O interface 712 provides an interface between processing component 702 and peripheral interface modules, such as keyboards, click wheels, buttons, etc. These buttons may include, but are not limited to, home buttons, volume buttons, power buttons, and lock buttons.

[0188] Sensor assembly 714 includes one or more sensors for providing state assessments of various aspects of electronic device 700. For example, sensor assembly 714 can detect the on / off state of electronic device 700, the relative positioning of components such as the display and keypad of electronic device 700, changes in position of electronic device 700 or its components, the presence or absence of user contact with electronic device 700, orientation or acceleration / deceleration of device 700, and temperature changes of electronic device 700. Sensor assembly 714 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. Sensor assembly 714 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, sensor assembly 714 may also include an accelerometer, gyroscope, magnetometer, pressure sensor, or temperature sensor.

[0189] Communication component 716 is configured to facilitate wired or wireless communication between electronic device 700 and other devices. Electronic device 700 can access wireless networks based on communication standards, such as WiFi, carrier networks (such as 2G, 3G, 4G, or 5G), or combinations thereof. In one exemplary embodiment, communication component 716 receives broadcast signals or broadcast-related information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, communication component 716 also includes a near-field communication (NFC) module to facilitate short-range communication. For example, the NFC module may be implemented based on radio frequency identification (RFID) technology, Infrared Data Association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.

[0190] In an exemplary embodiment, the electronic device 700 may be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components to perform the methods described above.

[0191] In an exemplary embodiment, a computer-readable storage medium including instructions is also provided, such as a memory 704 including instructions, which can be executed by a processor 720 of an electronic device 700 to perform the above-described method. For example, the computer-readable storage medium may be a ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, and optical data storage device, etc.

[0192] In an exemplary embodiment, a computer program product is also provided, which includes instructions that can be executed by a processor 720 of an electronic device 700 to perform the above-described method.

[0193] It should be noted that the above-mentioned apparatus, electronic equipment, computer-readable storage medium, computer program product, etc., may also include other implementation methods according to the description of the method embodiments. For specific implementation methods, please refer to the description of the relevant method embodiments, which will not be elaborated here.

[0194] Other embodiments of this disclosure will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of this disclosure that follow the general principles of this disclosure and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this disclosure are indicated by the claims.

[0195] It should be understood that this disclosure is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this disclosure is limited only by the appended claims.

Claims

1. A data processing method, characterized in that, include: Obtain the workflow orchestration data for the business process; The process orchestration data is used to describe the upstream and downstream relationships of sub-processes in the business process; Based on the process orchestration data, the business logic information of the business process is determined, including: extracting first logic information and second logic information of the business process from each orchestration data of the process orchestration data; each orchestration data includes at least configuration information of an upstream sub-process and all downstream sub-processes of the upstream sub-process, the first logic information includes at least an upstream sub-process and a downstream sub-process associated with the upstream sub-process, and the second logic information includes at least configuration information of the corresponding sub-process; the first logic information and second logic information of the business process are combined to obtain the business logic information of the business process; Extract the arrangement structure of sub-processes in the business process from the business logic information, and render a process framework diagram that records the arrangement structure. Based on the business logic information, determine the connection relationships between the sub-processes of the business process; In the rendered process framework diagram, the sub-processes with the connection relationship are populated to generate the flowchart of the business process.

2. The method according to claim 1, characterized in that, The step of extracting the arrangement structure of sub-processes in the business process from the business logic information includes: Based on the business logic information, determine the initial sub-process of the business process; Query the business logic information to determine the downstream sub-process of the initial sub-process, and delete the logic information in the business logic information that takes the initial sub-process as the upstream sub-process, to obtain the deleted business logic information; The steps of taking the deleted business logic information as business logic information and taking the downstream sub-process as the initial sub-process, jumping to querying the business logic information, determining the downstream sub-process of the initial sub-process, and deleting the logic information in the business logic information that takes the initial sub-process as the upstream sub-process, to obtain the deleted business logic information, continue until the deleted business logic information is empty. Each identified sub-process is treated as a sub-process layer, and the arrangement structure of the sub-processes in the business process is determined based on each sub-process layer.

3. The method according to claim 2, characterized in that, The step of determining the initial sub-process of the business process based on the business logic information includes: Iterate through each piece of the business logic information; If the downstream sub-process of the business logic information does not include the upstream sub-process of the currently traversed logic information, the upstream sub-process of the currently traversed logic information is identified as the initial sub-process of the business process; the downstream sub-process of the business logic information includes the downstream sub-process of each piece of logic information of the business logic information.

4. The method according to claim 1, characterized in that, The rendering of the flowchart recording the arrangement structure includes: Based on the arrangement structure, the position information of the sub-processes in the business process is identified, and the configuration information of the sub-processes in the business process is extracted from the business logic information. Based on the location and configuration information of the sub-processes in the business process, the sub-processes in the business process are rendered to obtain a process framework diagram that records the arrangement structure.

5. The method according to claim 4, characterized in that, The step of identifying the position information of sub-processes in the business process based on the arrangement structure includes: By querying the arrangement structure, the layers corresponding to the sub-processes in the business process and the distribution information of the sub-processes in the corresponding layers are obtained. The vertical coordinate of the layer corresponding to the sub-process in the business process is identified as the vertical coordinate of the sub-process in the business process, and the horizontal coordinate that matches the distribution information is identified as the horizontal coordinate of the sub-process in the business process. The position information of the sub-processes in the business process is obtained by combining the vertical and horizontal coordinates of the sub-processes in the business process.

6. The method according to claim 1, characterized in that, Determining the connection relationship between the sub-processes of the business process based on the business logic information includes: Extract the relationships between the sub-processes of the business process from the business logic information; The relationships between the sub-processes of the business process are identified as the connection relationships between the sub-processes of the business process.

7. A data processing apparatus, characterized in that, include: The data acquisition unit is configured to acquire the process orchestration data of the business process; The process orchestration data is used to describe the upstream and downstream relationships of sub-processes in the business process; The information determination unit is configured to execute data orchestration based on the process to determine the business logic information of the business process; The structure extraction unit is configured to extract the arrangement structure of the sub-processes in the business process from the business logic information and render a process framework diagram that records the arrangement structure. The relationship determination unit is configured to determine the connection relationship between the sub-processes of the business process based on the business logic information. The relationship filling unit is configured to perform a relationship filling operation on the sub-processes with the connection relationship in the rendered process framework diagram to generate the flowchart of the business process; The information determination unit is further configured to extract first logical information and second logical information of the business process from each orchestration data of the process orchestration data; Each orchestration data includes at least the configuration information of the upstream subprocess and all downstream subprocesses of the upstream subprocess. The first logical information includes at least the upstream subprocess and one downstream subprocess associated with the upstream subprocess. The second logical information includes at least the configuration information of the corresponding subprocess. The first and second logical information of the business process are combined to obtain the business logic information of the business process.

8. The apparatus according to claim 7, characterized in that, The structure extraction unit is further configured to perform the following steps: determining the initial sub-process of the business process based on the business logic information; querying the business logic information to determine the downstream sub-process of the initial sub-process, and deleting the logic information in the business logic information that has the initial sub-process as its upstream sub-process, to obtain the deleted business logic information; using the deleted business logic information as the business logic information, and using the downstream sub-process as the initial sub-process, and jumping to the steps of querying the business logic information, determining the downstream sub-process of the initial sub-process, and deleting the logic information in the business logic information that has the initial sub-process as its upstream sub-process, to obtain the deleted business logic information, until the deleted business logic information is empty; and treating each determined sub-process as a layer of sub-processes, and determining the arrangement structure of the sub-processes in the business process based on each layer of sub-processes.

9. An electronic device, characterized in that, include: processor; Memory used to store the processor's executable instructions; The processor is configured to execute the instructions to implement the data processing method as described in any one of claims 1 to 6.

10. A computer-readable storage medium, characterized in that, When the instructions in the computer-readable storage medium are executed by the processor of the electronic device, the electronic device is able to perform the data processing method as described in any one of claims 1 to 6.

Images