Process editing method and device, equipment and storage medium

Abstract

The invention discloses a process editing method, device and equipment and a storage medium which are applied to the technical field of computers, and in the method, a target process including a first process type node is edited in a process editing page by utilizing a low-code platform. The first process type node belongs to the first process type. And after obtaining an adding instruction for the second process type node, adding the second process type node in the target process. The second process type node belongs to a second process type. The second process type is different from the first process type. A low-code platform can be utilized to edit nodes of various flow types respectively belonging to different flow processing logics, and combination of the nodes of various flow types in one flow can be realized. A user does not need to use various flow editing products to edit flows of different flow types. The process is edited by using a low-code platform, so that the editing cost of editing the process involving various process type nodes can be reduced, and the efficiency of editing the process is improved.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a process editing method, device, equipment and storage medium. Background Art

[0002] Process editing products are commonly used software products. Users can use process editing products to design, edit, run, analyze and optimize processes. Based on process editing products, the cost of process editing can be reduced and the efficiency of business management can be improved.

[0003] In business scenarios, there are many types of processes involved. For example, business processes and approval processes. Business processes mainly involve capabilities such as data processing and logical judgment, which are used to implement business management. Approval processes mainly involve capabilities such as personnel selection and approval result processing, which are used to implement the approval of projects and requests. Different types of processes involve different capabilities and processing logic.

[0004] At present, process editing products can usually only implement the editing of one type of process, that is, they support the editing of nodes of one type of process. In the process of achieving comprehensive management of the business, users need to use multiple process editing products to edit different types of processes respectively. The process of using multiple process editing products to edit processes separately is relatively complicated, and the cost of editing multiple types of processes is high. Summary of the invention

[0005] In view of this, the present application provides a process editing method, apparatus, device and storage medium, which can realize the editing of nodes of various process types based on a low-code platform and reduce the cost of editing the process.

[0006] The technical solutions provided by this application are as follows:

[0007] In a first aspect, the present application provides a process editing method, which is applied to a low-code platform, and the method includes: displaying a process editing page, the process editing page is used to edit a target process, the target process includes a first process type node; in response to obtaining an add instruction for a second process type node, adding a second process type node to the target process, the second process type to which the second process type node belongs is different from the first process type to which the first process type node belongs, and the first process type and the second process type are determined based on the process processing logic.

[0008] In one possible implementation, in response to obtaining an add instruction for a second process type node, adding a second process type node in the target process includes: in response to obtaining an add instruction for a second process type node, adding a to-be-edited node of the second process type in the target process; in response to obtaining a configuration instruction for the node to be edited, configuring node parameters of the node to be edited according to configuration parameters included in the configuration instruction to obtain a second process type node, wherein the type of the node parameters is related to the second process type.

[0009] In one possible implementation, in response to obtaining an add instruction for a node of the second process type, adding a node to be edited of the second process type in the target process includes: in response to obtaining an insert instruction generated by a trigger for an insert control, displaying a node selection control, the node selection control being used to select a corresponding node of the second process type, the insert control being connected to at least one node included in the target process; in response to triggering a node selection control, adding a node to be edited of the second process type corresponding to the node selection control in the target process, the node to be edited being connected to the node connected to the insert control.

[0010] In a possible implementation, the second process type node is an integration node, and the displaying of a node selection control in response to obtaining an insertion instruction generated by a trigger for inserting a control includes: in response to obtaining an insertion instruction generated by a trigger for inserting a control, displaying at least one connector identifier, each of the connector identifiers corresponding to a category of connectors, the connectors being used to establish a connection relationship between the target process and an application corresponding to the connector, the application being built based on the low-code platform, or supporting connection with the low-code platform;

[0011] In response to triggering a node selection control, adding a node to be edited of a second process type corresponding to the node selection control in the target process, including: in response to triggering a selection instruction for a target connector identifier, adding a node to be edited of an integration process type corresponding to the target connector identifier in the target process, the node to be edited of the integration process type being used to call the connector corresponding to the target connector identifier.

[0012] In a possible implementation, the second process type node is an integration node, and the displaying of the node selection control in response to obtaining the insertion instruction generated by the trigger for inserting the control includes: displaying a connector editing control in response to obtaining the insertion instruction generated by the trigger for inserting the control;

[0013] In response to triggering a node selection control, adding a node to be edited of a second process type corresponding to the node selection control in the target process, including: in response to obtaining a trigger instruction for a connector editing control, displaying a custom connector editing page; creating a target connector through a connector creation instruction obtained through the custom connector editing page; adding a node to be edited of an integration process type in the target process, wherein the node to be edited of the integration process type is used to call the target connector.

[0014] In a possible implementation, the second process type node is a business node, and in response to obtaining an insert instruction generated by a trigger for inserting a control, displaying a node selection control includes: in response to obtaining an insert instruction generated by a trigger for inserting a control, displaying at least one business node identifier, each of the business node identifiers corresponding to a category of business operations;

[0015] In response to triggering a node selection control, adding a node to be edited of a second process type corresponding to the node selection control in the target process includes: in response to triggering a selection instruction for a target business node identifier, adding a node to be edited of a business process type corresponding to the target business node identifier in the target process.

[0016] In a possible implementation, the second process type node is an approval node, and the displaying of the node selection control in response to obtaining the insertion instruction generated by the trigger for the insertion control includes: displaying the approval node identifier in response to obtaining the insertion instruction generated by the trigger for the insertion control;

[0017] In response to triggering a node selection control, adding a node to be edited of a second process type corresponding to the node selection control in the target process includes: in response to triggering a selection instruction for an approval node identifier, adding a node to be edited of an approval process type corresponding to the approval node identifier in the target process.

[0018] In a possible implementation, the first process type node is a business node, and the second process type node is an approval node or an integration node.

[0019] In the second aspect, the present application provides a process editing device, which is applied to a low-code platform, and the device includes: a display unit, used to display a process editing page, the process editing page is used to edit a target process, the target process includes a first process type node; an adding unit, used to add a second process type node to the target process in response to obtaining an add instruction for a second process type node, the second process type to which the second process type node belongs is different from the first process type to which the first process type node belongs, and the first process type and the second process type are determined based on the process processing logic.

[0020] In a possible implementation, the adding unit is configured to add a second process type node to the target process in response to acquiring an adding instruction for the second process type node, including:

[0021] An adding unit is used to, in response to obtaining an adding instruction for a node of a second process type, add a node to be edited of the second process type in the target process; in response to obtaining a configuration instruction for the node to be edited, configure the node parameters of the node to be edited according to the configuration parameters included in the configuration instruction to obtain a node of the second process type, wherein the type of the node parameters is related to the second process type.

[0022] In a possible implementation, the adding unit is configured to add a node to be edited of the second process type in the target process in response to obtaining an adding instruction for a node of the second process type, including:

[0023] The adding unit is used to display a node selection control in response to obtaining an insert instruction generated by a trigger for an insert control, wherein the node selection control is used to select a corresponding second process type node, and the insert control is connected to at least one node included in the target process; in response to triggering the node selection control, a node to be edited of the second process type corresponding to the node selection control is added to the target process, and the node to be edited is connected to the node connected to the insert control.

[0024] In a possible implementation, the second process type node is an integration node, and the adding unit is used to display a node selection control in response to obtaining an insertion instruction generated by a trigger for inserting a control, including: the adding unit is used to display at least one connector identifier in response to obtaining an insertion instruction generated by a trigger for inserting a control, each of the connector identifiers corresponds to a category of connectors, the connectors are used to establish a connection relationship between the target process and an application corresponding to the connector, and the application is built based on the low-code platform or supports connection with the low-code platform;

[0025] The adding unit is used to add a node to be edited of the second process type corresponding to the node selection control in the target process in response to triggering a node selection control, including: the adding unit is used to add a node to be edited of the integration process type corresponding to the target connector identifier in the target process in response to triggering a selection instruction for the target connector identifier, and the node to be edited of the integration process type is used to call the connector corresponding to the target connector identifier.

[0026] In a possible implementation, the second process type node is an integration node, and the adding unit is used to display a node selection control in response to obtaining an insertion instruction generated by a trigger for inserting a control, including: the adding unit is used to display a connector editing control in response to obtaining an insertion instruction generated by a trigger for inserting a control;

[0027] The adding unit is used to respond to the triggering node selection control and add a node to be edited of the second process type corresponding to the node selection control in the target process, including: the adding unit is used to display a custom connector editing page in response to obtaining a trigger instruction for the connector editing control; create a target connector through the connector creation instruction obtained by the custom connector editing page; add a node to be edited of an integration process type in the target process, and the node to be edited of the integration process type is used to call the target connector.

[0028] In a possible implementation, the second process type node is a business node, and the adding unit is used to display a node selection control in response to obtaining an insertion instruction generated by a trigger for inserting a control, including: the adding unit is used to display at least one business node identifier in response to obtaining an insertion instruction generated by a trigger for inserting a control, each of the business node identifiers corresponding to a category of business operations;

[0029] The adding unit is used to add a node to be edited of the second process type corresponding to the node selection control in the target process in response to triggering a node selection control, including: the adding unit is used to add a node to be edited of the business process type corresponding to the target business node identifier in the target process in response to triggering a selection instruction for the target business node identifier.

[0030] In a possible implementation, the second process type node is an approval node, and the adding unit is used to display a node selection control in response to obtaining an insertion instruction generated by a trigger for an insert control, including: the adding unit is used to display an approval node identifier in response to obtaining an insertion instruction generated by a trigger for an insert control;

[0031] The adding unit is used to add a node to be edited of a second process type corresponding to the node selection control in the target process in response to triggering a node selection control, including: the adding unit is used to add a node to be edited of an approval process type corresponding to the approval node identifier in the target process in response to triggering a selection instruction for the approval node identifier.

[0032] In a possible implementation, the first process type node is a business node, and the second process type node is an approval node or an integration node.

[0033] In a third aspect, the present application provides an electronic device, including:

[0034] one or more processors;

[0035] a storage device having one or more programs stored thereon,

[0036] When the one or more programs are executed by the one or more processors, the one or more processors implement any method described in the first aspect.

[0037] In a fourth aspect, the present application provides a computer-readable medium having a computer program stored thereon, wherein when the program is executed by a processor, any method described in the first aspect is implemented.

[0038] In a fifth aspect, the present application provides a computer program product, which, when executed on a device, enables the device to execute the method described in the first aspect.

[0039] It can be seen that this application has the following beneficial effects:

[0040] The present application provides a process editing method, apparatus, device and storage medium, in which a target process including a first process type node is edited in a process editing page using a low-code platform. The first process type node belongs to the first process type. After obtaining an add instruction for the second process type node, a second process type node is added to the target process. The second process type node belongs to the second process type. The second process type is different from the first process type. The first process type and the second process type are divided based on process processing logic. In this way, editing nodes of multiple process types in one process is achieved, and process nodes of multiple process processing logics can be uniformly edited to achieve the combination of nodes of multiple process types in one process. Users do not need to use multiple process editing products to edit nodes of different process types separately and build different types of processes. Using a low-code platform to edit processes can reduce the editing cost of editing processes involving multiple process type nodes and further improve the efficiency of editing processes. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] Figure 1 A schematic diagram of an exemplary application scenario provided in an embodiment of the present application;

[0042] Figure 2 A schematic diagram of another exemplary application scenario provided in an embodiment of the present application;

[0043] Figure 3 A schematic diagram of another exemplary application scenario provided in an embodiment of the present application;

[0044] Figure 4 A flowchart of a process editing method provided in an embodiment of the present application;

[0045] Figure 5 A page schematic diagram provided for an embodiment of the present application;

[0046] Figure 6 Another page schematic diagram provided for an embodiment of the present application;

[0047] Figure 7 A schematic diagram of another page provided in an embodiment of the present application;

[0048] Figure 8 Another page schematic diagram provided for an embodiment of the present application;

[0049] Fig. 9 A schematic diagram of the structure of a process editing device provided in an embodiment of the present application;

[0050] Fig.10 A schematic diagram of the basic structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0051] In order to facilitate the understanding and explanation of the technical solutions provided by the embodiments of the present application, the background technology of the present application will be described below.

[0052] For enterprises, in the process of managing business, many types of processes are involved. At present, according to the process processing logic, processes are divided into three types: business process type, approval process type and integrated process type. Different types of processes have different logics for processing data. For example, the processing logic corresponding to the business process type mainly includes obtaining business data and analyzing business data. The processing logic corresponding to the approval process type mainly includes approval logic. For example, the leave approval process and the on-the-job approval process belong to the approval process type. The processing logic corresponding to the integrated process type mainly includes the interconnection between multiple business systems or applications. For example, the interaction process between the data processing system and the message system belongs to the integrated process type.

[0053] Users can use process editing products to edit processes. However, the process engines that current process editing products are based on usually only support the orchestration of processes of one process type. Taking the above three process types as an example, for example, process editing product A supports editing business process types, process editing product B supports editing approval process types, and process editing product C supports editing integration process types. In the process of managing business, users need to use multiple process editing products to edit processes of the process types supported by the products. For example, users use process editing product A to edit processes of business process types, use process editing product B to edit processes of approval process types, and use process editing product C to edit processes of integration process types. In this way, users need to be familiar with the use of process editing product A, process editing product B, and process editing product C respectively, and the cost for users to learn and adapt to the use of the products is high.

[0054] In addition, for business scenarios that require joint processing of multiple types of processes, it is also necessary to establish associations between processes of multiple process types. For example, for business scenarios of business data acquisition and approval, it is necessary to edit the business process for acquiring and processing business data, as well as the approval process for approving business data. In addition, it is necessary to establish an association between business processes and approval processes so that the approval process can be automatically triggered during the operation of the business process. Since the processing logic of different types of processes is different, a process engine usually supports the editing and running of a specific type of process. There is business isolation between process editing products, and it is difficult to directly configure processes edited by other process editing products during the use of process editing products. Users are required to combine processes of different process types by writing code to achieve comprehensive management of the business. The operation of users combining processes of different process types is relatively complicated, and the cost of writing code is high, resulting in low efficiency of combining processes of different process types.

[0055] Based on this, an embodiment of the present application provides a process editing method. The method is applied to a low-code platform. On the process editing page of the low-code platform, a user can edit a target process including a first process type node and a second process type node. Specifically, for a target process including a first process type node, an add instruction for a second process type node is triggered, and a second process type node is added to the target process. The first process type node and the second process type node belong to different process types. The process type is divided based on process processing logic. By editing nodes of multiple process types in the target process, multiple types of processes can be combined. The low-code platform supports users to edit multiple types of processes, and supports users to combine multiple types of processes to achieve hyper-automation. In this way, users do not need to use multiple process editing products to edit different types of processes separately and combine them, which reduces the cost of users learning and adapting to multiple process editing products, and does not require users to manually write code to combine multiple types of processes, further reducing the cost of users editing processes and improving the efficiency of users editing processes.

[0056] In order to facilitate understanding of a process editing method provided in an embodiment of the present application, a process editing method provided in an embodiment of the present application is described below in conjunction with the accompanying drawings. Figure 1-Figure 3 See the example scenario shown in the figure. Figure 1-Figure 3 As shown, the figure is a scene diagram of an exemplary application scenario provided in an embodiment of the present application.

[0057] Low-code platform is a rapid application development technology platform. Low-code platforms have low-code or zero-code features and can provide users with elements and modules for creating applications. Users can create applications by simply "dragging, pulling, and dropping" the elements or modules they need to select. Low-code platforms can also provide users with process editing functions. Users can edit and apply processes on low-code platforms. Low-code platforms are, for example, application platform as a service (aPaaS) platforms.

[0058] The client of the low-code platform displays a process editing page for the user to edit the process. The process editing page includes a canvas area where the user can edit the process. For example, see Figure 1 As shown, the user edits the target process in the canvas area. The target process includes a first process type node. As an example, the first process type node is a business node, including a business data acquisition node and a data analysis node. The user can add a second process type node in the target process. The process type to which the second process type node belongs is different from the process type to which the first process type node belongs.

[0059] As a possible implementation, the second process type node is an approval node. The approval node pair belongs to the approval process type. The user triggers an add instruction for the approval node. For example, see Figure 2 As shown, the user adds an approval node between the business data acquisition node and the data analysis node. The user can configure the node parameters of the approval node to configure the approval process corresponding to the approval node. Add an approval node in the target process to combine the target process with the approval process. In the process of running the target process, when the approval node is executed, the approval information is sent to the approval application associated with the approval node. The approval information is determined based on the node parameters of the approval node. The approver can view the approval content, perform approval operations, and generate approval results through the approval application. The approval application feeds back the approval results to the low-code platform so that the target process can continue to run based on the approval results. In addition, the approval application can also send approval reminder messages to the approver to remind the approver to view the approval content and perform approval operations in a timely manner.

[0060] As another possible implementation, the second process type node is an integration node. The integration node is used to trigger the connector. The connector is used to connect the corresponding application to achieve interaction between the low-code platform and the application. The integration node belongs to the integration process type. The user triggers the addition instruction for the integration node. For example, see Figure 3 As shown, the user adds an integration node after the data analysis node, such as a message system-message reminder node. The user can configure the node parameters of the integration node to configure the data interaction process with the application. Add an integration node in the target process to combine the target process with the integration process. In the process of running the target process, when the integration node is executed, it will automatically trigger the call of the connector to connect the application and interact with the application for data. Taking the above-mentioned message system-message reminder node as an example, when running the message system-message reminder node, data interaction is realized with the message system through the connector, and reminder information is sent to the message recipient based on the message system so that the message recipient can view the relevant messages of the data analysis.

[0061] Those skilled in the art will understand that Figure 1-Figure 3 The schematic diagram of the scene shown is only an example in which the implementation of the present application can be implemented. The scope of application of the implementation of the present application is not limited by any aspect of the scene.

[0062] In order to facilitate understanding of the technical solution provided in the embodiment of the present application, the process editing method provided in the embodiment of the present application is described below with reference to the accompanying drawings.

[0063] See also Figure 4 As shown in FIG. 1 , this figure is a schematic diagram of a process editing method provided in an embodiment of the present application, such as Figure 4As shown, the method may include S401-S402:

[0064] S401: Display the process editing page.

[0065] The process editing page is a page for editing processes provided by the low-code platform. Users can edit the target process in the process editing page using the process editing function provided by the low-code platform. The low-code platform supports business processes that are linked to the front and back ends and are triggered by user configuration pages or user interface (User Interface) events, including logic such as conditional branches and loops, as well as data processing capabilities such as creation, update, and deletion. The low-code platform also supports users to configure back-end business processes, such as scheduled tasks, data changes, or external event triggers. In addition, the low-code platform also provides capabilities such as permission management and editing cloud functions.

[0066] The target process includes a first process type node. The first process type node belongs to the first process type. As an example, the first process type is a business process type, and the first process type node is a business node. Alternatively, the first process type is an approval process type, and the first process type node is an approval node. Alternatively, the first process type is an integration process type, and the first process type node is an integration node.

[0067] The first process type node may be generated in advance by adding a node in the process editing page. The first process type node may also be determined by selecting the basic process type of the target process. For example, when creating a target process, the basic process type of the target process is selected as the business process type, and the business node to be edited is displayed in the process editing page for the user to edit.

[0068] S402: In response to obtaining an add instruction for a second process type node, a second process type node is added to the target process, the second process type to which the second process type node belongs is different from the first process type to which the first process type node belongs, and the first process type and the second process type are determined based on the process processing logic.

[0069] In the target process, a second process type node belonging to a process type other than the first process type can be added. The second process type to which the second process type node belongs is different from the first process type to which the first process type node belongs. Figure 2 Taking the scenario shown as an example, the target process includes a business node belonging to the business process type, and an approval node belonging to the approval process type can be added to the target process.

[0070] As an example, the second process type node is a business node, an approval node, or an integration node.

[0071] The user can trigger an add instruction for the second process type node in the process editing page. In response to obtaining the add instruction for the second process type node, the second process type node is added to the target process.

[0072] After adding the second process type node, the target process includes nodes of at least two process types, realizing comprehensive editing of multiple types of processes. The low-code platform supports editing nodes of multiple process types in one process. For example, the low-code platform supports the business process management (BPM) method, and by editing business nodes and approval nodes within the process, the business process and approval process can be combined. Based on the universal editing capabilities of the low-code platform for each process type, it expands support for various process scenarios, realizes unified editing of business processes, approval processes, and integrated processes, meets users' needs for process editing of multiple process types, and realizes hyper-automation.

[0073] In some possible implementations, in response to the add instruction, the second process type node added to the target process is a node that has been configured, and the user does not need to perform initial configuration on the node parameters of the second process type node.

[0074] In some other possible implementations, after obtaining the instruction to add the second process type node, first add the second process type node to be edited in the target process, and then generate the second process type node based on the editing instruction for the node to be edited. As an example, an embodiment of the present application provides a possible implementation method for adding a second process type node to the target process in response to obtaining the instruction to add the second process type node, including the following two steps:

[0075] A1: In response to obtaining an add instruction for a node of the second process type, a node to be edited of the second process type is added to the target process.

[0076] The node to be edited of the second process type is a node of the second process type that requires a user to configure node parameters. As an example, the node to be edited of the second process type includes fixed node parameters and node parameters to be edited. The fixed node parameters are node parameters that do not need to be edited corresponding to the second process type. The node parameters to be edited are node parameters that need to be edited corresponding to the second process type.

[0077] As an example, for the node to be edited of the approval process type, the fixed node parameter is the node name. The node name is "approval node". The node parameters to be edited include node parameters such as approval content, approver, and approval method. The approval node can be used to implement approval operations such as approval process arrangement, rule engine, process processing, and exception handling.

[0078] As another example, for a node to be edited of an integration process type, the node parameters to be edited include node parameters such as execution operation and connection configuration.

[0079] A2: In response to obtaining a configuration instruction for the node to be edited, configure node parameters of the node to be edited according to configuration parameters included in the configuration instruction to obtain a second process type node.

[0080] The nodes to be edited of the second process type added in the target process can be displayed in an editable form. The user can directly edit the nodes to be edited to generate configuration instructions. Alternatively, after selecting the node to be edited, the user edits the node to be edited in the editing area of ​​the process editing page to generate configuration instructions. In addition, the nodes to be edited of the second process type added in the target process can be displayed in a prompt form to remind the user that editing is required. After the user completes editing the node to be edited, the nodes of the second process type are displayed in a normal form.

[0081] The configuration instruction includes configuration parameters. According to the configuration parameters included in the configuration instruction, the node parameters of the node to be edited are configured. Based on the configuration instruction, the configuration of the node to be edited is completed to obtain a second process type node.

[0082] It should be noted that the embodiment of the present application does not limit the time for configuring the node to be edited. As an example, after adding a node to be edited of the second process type in the target process, the user can directly edit the node to be edited to generate a configuration instruction. As another example, the user can edit the node to be edited after editing other nodes of the target process to generate a configuration instruction.

[0083] After configuring the node parameters, a second process type node is obtained. The second process type node can be run and perform corresponding operations. In addition, the user can also adjust the node parameters included in the second process type node, which is not limited in the embodiment of the present application.

[0084] In this way, unified modeling of nodes of various process types is achieved, and users can edit nodes of various process types, which is convenient for users to edit nodes and reduces the adaptation cost of users' editing operations on nodes of different process types.

[0085] The embodiments of the present application do not limit the triggering method of adding instructions. As an example, a control for adding nodes is included in the edit bar of the process editing page. By triggering the control for adding nodes, the process type selection control for displaying nodes is triggered. Then, through the process type selection control, a second process type is selected, and an adding instruction for the second process type node is generated. As another example, an insert control is provided on the connecting line between nodes in the canvas area of ​​the process editing page. By triggering the insert control, an adding instruction for the second process type node is generated.

[0086] As an example, an embodiment of the present application provides a possible implementation method for adding a node to be edited of the second process type in the target process in response to obtaining an add instruction for a node of the second process type, including the following two steps:

[0087] B1: In response to obtaining an insert instruction generated by a trigger for an insert control, a node selection control is displayed, the node selection control is used to select a corresponding second process type node, and the insert control is connected to at least one node included in the target process.

[0088] See also Figure 5 As shown, the insert control is located on the connection line between the nodes included in the target process. The insert control is connected to at least one node. As an example, the insert control has two display forms. When the distance between the operating control and the insert control is greater than or equal to the distance threshold, the insert control adopts a hidden display form. When the distance between the operating control and the insert control is less than the distance threshold, the insert control adopts a marked display form. In other words, when the operating control is close to the insert control, the insert control is displayed in a marked display form. In this way, the insert control is displayed according to the needs of the user's operation, which can reduce the display content of the target process when the user is not operating, reduce the complexity of the target process display, improve the aesthetics of the display, and facilitate user operation and viewing.

[0089] The insert control is used to insert a node at the location of the control. The user generates an insert instruction by triggering the insert control. In response to obtaining the insert instruction, the node selection control is displayed. The node selection control is used to select the node to be inserted.

[0090] In one possible implementation, see Figure 6 As shown, in response to obtaining the insertion instruction, the process editor is displayed. The process editor includes a search control, a type selection control, and a node selection control. The search control is used to search and display the corresponding node selection control based on the purpose and name of the node. The type selection control is used to display the node selection control of the type in the process editor. The node selection control is used for the corresponding second process type node. Figure 6 For example, the type selection control is displayed in the form of text. Type selection controls include connector controls, manual task controls, data controls, logic controls, and other controls. By clicking a type selection control, the node selection controls belonging to the type are displayed in the process editor, making it easier for users to find the node selection control they want to select.

[0091] The node selection control is displayed in the form of a node identifier. The node identifier includes an image identifier and a text identifier. The image identifier is, for example, an image that reflects the function of the second process type node. The text identifier is, for example, the name of the second process type node. The user can click to trigger the node selection control through the process editor to select the second process type node corresponding to the node selection control.

[0092] B2: In response to triggering the node selection control, a to-be-edited node of the second process type corresponding to the node selection control is added to the target process, and the to-be-edited node is connected to the node connected to the insert control.

[0093] Based on the triggered node selection control, determine to add a node selection control corresponding to the second process type to be edited in the target process. The position of the node to be edited of the second process type in the target process is the same as the position of the insert control. The node to be edited of the second process type is connected to the node connected to the insert control. In this way, the insertion position of the node to be edited of the second process type can be quickly located based on the insert control. The user can understand the insertion position of the node based on the displayed position of the insert control, thereby improving the user operation experience.

[0094] With the above Figure 5 and Figure 6 Taking the target process diagram shown in the figure as an example, the insert control is located on the connection line between the obtain business data node and the data analysis node. That is, the insert control is connected to the obtain business data node and the data analysis node respectively. Figure 6 After the node selection control is triggered in the process editor as shown, see Figure 7 As shown, a node to be edited of the approval process type is added between the node to obtain business data and the node to analyze data. The node to be edited of the approval process type is connected to the node to obtain business data and the node to analyze data, respectively. The node to be edited of the approval process type is displayed in bold to remind the user to configure the node parameters.

[0095] For the second process type nodes belonging to different process types, the displayed node selection controls are different. The following describes the displayed node selection controls for the second process type nodes belonging to different process types.

[0096] The first type: The second process type node is an integration node.

[0097] In a possible implementation, in response to obtaining an insert instruction, Figure 8For example, at least one connector identifier is displayed. Each connector identifier corresponds to a category of connectors. The connector corresponding to the connector identifier is a connector that has been edited. The connector is used to establish a connection relationship between the target process and the application corresponding to the connector. The connector can implement the call of the application programming interface (Application Programming Interface, API) of the corresponding application to realize data interaction with the application. In addition, the connector can also be used to implement other platforms or systems to call the process edited by the low-code platform. A category of connector corresponds to an application. The embodiment of the present application does not limit the construction method of the application. As an example, the application is built based on the low-code platform. In this way, the connection between the target process running on the low-code platform and the application can be realized. As another example, the application is built by a third-party application provider. The application supports connection with the low-code platform. The user can select the required target connector identifier from at least one connector identifier to trigger the selection instruction for the target connector identifier. In this way, it is convenient for users to select suitable connectors, establish corresponding integration nodes, and reduce the cost of users editing integration nodes.

[0098] In response to the acquisition selection instruction, a node to be edited of the integration process type corresponding to the target connector identifier is added to the target process. The node to be edited of the integration process type is used to call the connector corresponding to the target connector identifier.

[0099] The above is an introduction to the selection process of an existing connector. In other possible implementations, a new connector can be created.

[0100] In response to obtaining an insert instruction generated by a trigger for an insert control, a connector editing control is displayed. The connector editing control is used to edit a user-defined connector. In response to obtaining a trigger instruction for a connector editing control, a custom connector editing page is displayed. The connector editing page displays the parameters of the connector. Users can trigger a connector creation instruction through the connector editing page. The connector creation instruction includes configuration parameters of the connector. Based on the connector creation instruction, a target connector is created. A node to be edited of the integration process type is added to the target process. The node to be edited of the integration process type is used to call the target connector. Users can configure connectors at a low cost through custom connectors, which is convenient for users to flexibly configure integration nodes.

[0101] By adding integration nodes to the process, during the process running, it is possible to call a wider range of other applications and the process can be called through connectors. In this way, the low-code platform can open APIs to achieve a wider range of integration and integration, improving the integration capabilities of the low-code platform.

[0102] The second type: The second process type node is a business node.

[0103] Business nodes also have multiple categories. For example, they include data nodes and logic nodes. Data nodes are used to perform data processing. Logic nodes are used to execute processing logic. Data nodes and logic nodes can also include multiple categories of nodes. For example, data nodes include acquisition record nodes, update record nodes, etc. Logic nodes include logic component nodes and assistant nodes, etc.

[0104] In response to obtaining the insertion instruction, at least one service node identifier is displayed. Each service node identifier corresponds to a category of service operations. The user can select the required target service node identifier from the at least one service node identifier, triggering a selection instruction for the target service node identifier, making it easier for the user to select a suitable service node and reducing the difficulty of creating a new service node for the user.

[0105] In response to triggering a selection instruction for a target business node identifier, a node to be edited of a business process type corresponding to the target business node identifier is added to the target process.

[0106] The third type: The second process type node is an approval node.

[0107] In response to obtaining the insertion instruction, the approval node identifier is displayed. Figure 6 As shown, the approval node identifier is displayed in the process editor.

[0108] In response to triggering a selection instruction for the approval node identifier, a to-be-edited node of the approval process type corresponding to the approval node identifier is added to the target process.

[0109] Based on a process editing method provided by the above method embodiment, the embodiment of the present application also provides a process editing device, which will be described below in conjunction with the accompanying drawings.

[0110] See also Fig. 9 As shown in FIG. 1 , this figure is a schematic diagram of the structure of a process editing device provided in an embodiment of the present application. The device is applied to a low-code platform. Fig. 9 As shown, the process editing device includes:

[0111] A display unit 901 is used to display a process editing page, where the process editing page is used to edit a target process, where the target process includes a first process type node;

[0112] An adding unit 902 is used to add a second process type node in the target process in response to obtaining an adding instruction for a second process type node, wherein the second process type to which the second process type node belongs is different from the first process type to which the first process type node belongs, and the first process type and the second process type are determined based on the process processing logic.

[0113] In a possible implementation, the adding unit 902 is configured to add a second process type node to the target process in response to acquiring an adding instruction for the second process type node, including:

[0114] An adding unit 902 is used to, in response to obtaining an adding instruction for a node of a second process type, add a node to be edited of the second process type in the target process; in response to obtaining a configuration instruction for the node to be edited, configure the node parameters of the node to be edited according to the configuration parameters included in the configuration instruction to obtain a node of the second process type, wherein the type of the node parameters is related to the second process type.

[0115] In a possible implementation, the adding unit 902 is configured to add a node to be edited of the second process type in the target process in response to obtaining an adding instruction for a node of the second process type, including:

[0116] The adding unit 902 is used to display a node selection control in response to obtaining an insert instruction generated by a trigger for an insert control, wherein the node selection control is used to select a corresponding second process type node, and the insert control is connected to at least one node included in the target process; in response to triggering the node selection control, a node to be edited of the second process type corresponding to the node selection control is added to the target process, and the node to be edited is connected to the node connected to the insert control.

[0117] In a possible implementation, the second process type node is an integration node, and the adding unit 902 is configured to display a node selection control in response to acquiring an insert instruction generated by a trigger for inserting a control, including:

[0118] The adding unit 902 is used to display at least one connector identifier in response to obtaining an insertion instruction generated by a trigger for inserting a control, each connector identifier corresponding to a category of connectors, the connectors being used to establish a connection relationship between the target process and an application corresponding to the connector, the application being built based on the low-code platform or supporting connection with the low-code platform;

[0119] The adding unit 902 is used to add a node to be edited of the second process type corresponding to the node selection control in the target process in response to triggering the node selection control, including:

[0120] The adding unit 902 is used to respond to triggering a selection instruction for a target connector identifier and add a node to be edited of an integration process type corresponding to the target connector identifier in the target process, wherein the node to be edited of the integration process type is used to call the connector corresponding to the target connector identifier.

[0121] In a possible implementation, the second process type node is an integration node, and the adding unit 902 is configured to display a node selection control in response to acquiring an insert instruction generated by a trigger for inserting a control, including:

[0122] The adding unit 902 is used to display the connector editing control in response to obtaining the insertion instruction generated by the trigger for inserting the control;

[0123] The adding unit 902 is used to add a node to be edited of the second process type corresponding to the node selection control in the target process in response to triggering the node selection control, including:

[0124] The adding unit 902 is used to display a custom connector editing page in response to obtaining a trigger instruction for a connector editing control; create a target connector through a connector creation instruction obtained through the custom connector editing page; and add a node to be edited of an integration process type in the target process, wherein the node to be edited of the integration process type is used to call the target connector.

[0125] In a possible implementation, the second process type node is a business node, and the adding unit 902 is configured to display a node selection control in response to acquiring an insert instruction generated by a trigger for inserting a control, including:

[0126] The adding unit 902 is used to display at least one business node identifier in response to obtaining an insert instruction generated by a trigger for inserting a control, each of the business node identifiers corresponding to a category of business operations;

[0127] The adding unit 902 is used to add a node to be edited of the second process type corresponding to the node selection control in the target process in response to triggering the node selection control, including:

[0128] The adding unit 902 is configured to add a node to be edited of a business process type corresponding to the target business node identifier in the target process in response to triggering a selection instruction for the target business node identifier.

[0129] In a possible implementation, the second process type node is an approval node, and the adding unit 902 is configured to display a node selection control in response to acquiring an insert instruction generated by a trigger for an insert control, including:

[0130] The adding unit 902 is used to display the approval node identifier in response to obtaining the insertion instruction generated by the trigger for inserting the control;

[0131] The adding unit 902 is used to add a node to be edited of the second process type corresponding to the node selection control in the target process in response to triggering the node selection control, including:

[0132] The adding unit 902 is used to add a node to be edited of the approval process type corresponding to the approval node identifier in the target process in response to triggering a selection instruction for the approval node identifier.

[0133] In a possible implementation, the first process type node is a business node, and the second process type node is an approval node or an integration node.

[0134] Based on a process editing method provided in the above method embodiment, the present application also provides an electronic device, including: one or more processors; a storage device, on which one or more programs are stored, when the one or more programs are executed by the one or more processors, the one or more processors implement the process editing method as described in any of the above embodiments.

[0135] Reference below Fig.10 , which shows a schematic diagram of the structure of an electronic device 1000 suitable for implementing the embodiment of the present application. The terminal device in the embodiment of the present application may include but is not limited to mobile terminals such as mobile phones, laptop computers, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (portable android devices), PMPs (Portable Media Players), vehicle-mounted terminals (such as vehicle-mounted navigation terminals), etc., and fixed terminals such as digital TVs (televisions), desktop computers, etc. Fig.10 The electronic device shown is merely an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0136] like Fig.10 As shown, the electronic device 1000 may include a processing device (e.g., a central processing unit, a graphics processing unit, etc.) 1001, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 1002 or a program loaded from a storage device 1008 into a random access memory (RAM) 1003. In the RAM 1003, various programs and data required for the operation of the electronic device 1000 are also stored. The processing device 1001, the ROM 1002, and the RAM 1003 are connected to each other via a bus 1004. An input / output (I / O) interface 1005 is also connected to the bus 1004.

[0137] Typically, the following devices may be connected to the I / O interface 1005: input devices including, for example, a touch screen, a touch pad, a keyboard, a mouse, a camera, a microphone, an accelerometer, a gyroscope, etc.; output devices 1007 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc.; storage devices 1008 including, for example, a magnetic tape, a hard disk, etc.; and communication devices 1009. The communication devices 1009 may allow the electronic device 1000 to communicate with other devices wirelessly or by wire to exchange data. Although Fig.10 The electronic device 1000 is shown with various devices, but it should be understood that it is not required to implement or possess all the devices shown. More or fewer devices may be implemented or possessed instead.

[0138] In particular, according to an embodiment of the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, an embodiment of the present application includes a computer program product, which includes a computer program carried on a non-transitory computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from the network through the communication device 1009, or installed from the storage device 1008, or installed from the ROM 1002. When the computer program is executed by the processing device 1001, the above-mentioned functions defined in the method of the embodiment of the present application are executed.

[0139] The electronic device provided in the embodiment of the present application and the process editing method provided in the above embodiment belong to the same inventive concept. The technical details not fully described in this embodiment can be referred to the above embodiment, and this embodiment has the same beneficial effects as the above embodiment.

[0140] Based on a process editing method provided in the above method embodiment, an embodiment of the present application provides a computer storage medium on which a computer program is stored, wherein when the program is executed by a processor, the process editing method as described in any of the above embodiments is implemented.

[0141] It should be noted that the computer-readable medium mentioned above in the present application may be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present application, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, device or device. In the present application, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, which carries a computer-readable program code. This propagated data signal may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. The computer readable signal medium may also be any computer readable medium other than a computer readable storage medium, which may send, propagate or transmit a program for use by or in conjunction with an instruction execution system, apparatus or device. The program code contained on the computer readable medium may be transmitted using any suitable medium, including but not limited to: wires, optical cables, RF (radio frequency), etc., or any suitable combination of the above.

[0142] In some embodiments, the client and the server may communicate using any currently known or future developed network protocol such as HTTP (Hyper Text Transfer Protocol), and may be interconnected with any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include a local area network ("LAN"), a wide area network ("WAN"), an internet (e.g., the Internet), and a peer-to-peer network (e.g., an ad hoc peer-to-peer network), as well as any currently known or future developed network.

[0143] The computer-readable medium may be included in the electronic device, or may exist independently without being incorporated into the electronic device.

[0144] The computer-readable medium carries one or more programs. When the one or more programs are executed by the electronic device, the electronic device executes the process editing method.

[0145] Computer program code for performing the operations of the present application may be written in one or more programming languages ​​or a combination thereof, including, but not limited to, object-oriented programming languages, such as Java, Smalltalk, C++, and conventional procedural programming languages, such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving a remote computer, the remote computer may be connected to the user's computer via any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0146] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present application. In this regard, each square box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two square boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0147] The units involved in the embodiments described in this application may be implemented by software or hardware. The name of a unit / module does not limit the unit itself in some cases. For example, a voice data acquisition module may also be described as a "data acquisition module".

[0148] The functions described above herein may be performed at least in part by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), complex programmable logic devices (CPLDs), and the like.

[0149] In the context of the present application, a machine-readable medium may be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, device, or equipment. A machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or equipment, or any suitable combination of the foregoing. A more specific example of a machine-readable storage medium may include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0150] It should be noted that the various embodiments in this specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments, and the same or similar parts between the various embodiments can be referred to each other. For the system or device disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple, and the relevant parts can be referred to the method part description.

[0151] It should be understood that in the present application, "at least one (item)" means one or more, and "plurality" means two or more. "And / or" is used to describe the association relationship of associated objects, indicating that three relationships may exist. For example, "A and / or B" can mean: only A exists, only B exists, and A and B exist at the same time, where A and B can be singular or plural. The character " / " generally indicates that the objects associated before and after are in an "or" relationship. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, c can be single or multiple.

[0152] It should also be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the presence of other identical elements in the process, method, article or device including the elements.

[0153] The above description of the disclosed embodiments enables those skilled in the art to implement or use the present application. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present application. Therefore, the present application will not be limited to the embodiments shown herein, but will conform to the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A process editing method, characterized in that: The method is applied to a low-code platform, and the method includes: Displaying a process editing page, wherein the process editing page is used to edit a target process, wherein the target process includes a first process type node; In response to obtaining an add instruction for a second process type node, a second process type node is added to the target process, the second process type to which the second process type node belongs is different from the first process type to which the first process type node belongs, and the first process type and the second process type are determined based on the process processing logic.

2. The method according to claim 1, characterized in that: In response to acquiring an add instruction for a second process type node, adding a second process type node in the target process includes: In response to obtaining an add instruction for a node of the second process type, adding a node to be edited of the second process type in the target process; In response to obtaining a configuration instruction for the node to be edited, node parameters of the node to be edited are configured according to configuration parameters included in the configuration instruction to obtain a second process type node, wherein the type of the node parameters is related to the second process type.

3. The method according to claim 2, characterized in that In response to obtaining an instruction to add a node of the second process type, adding a node to be edited of the second process type in the target process includes: In response to acquiring an insert instruction generated by a trigger for an insert control, displaying a node selection control, the node selection control being used to select a corresponding second process type node, the insert control being connected to at least one node included in the target process; In response to triggering the node selection control, a to-be-edited node of the second process type corresponding to the node selection control is added to the target process, and the to-be-edited node is connected to the node connected to the insert control.

4. The method according to claim 3, characterized in that: The second process type node is an integration node, and the step of displaying a node selection control in response to acquiring an insertion instruction generated by a trigger for an insertion control includes: In response to obtaining an insertion instruction generated by a trigger for inserting a control, displaying at least one connector identifier, each of the connector identifiers corresponding to a category of connectors, the connectors being used to establish a connection relationship between the target process and an application corresponding to the connector, the application being built based on the low-code platform or supporting connection with the low-code platform; In response to triggering the node selection control, adding a node to be edited of the second process type corresponding to the node selection control in the target process includes: In response to triggering a selection instruction for a target connector identifier, a to-be-edited node of an integration process type corresponding to the target connector identifier is added to the target process, and the to-be-edited node of the integration process type is used to call a connector corresponding to the target connector identifier.

5. The method according to claim 3, characterized in that: The second process type node is an integration node, and the step of displaying a node selection control in response to acquiring an insertion instruction generated by a trigger for an insertion control includes: In response to obtaining an insertion instruction generated by a trigger for inserting a control, displaying a connector edit control; In response to triggering the node selection control, adding a node to be edited of the second process type corresponding to the node selection control in the target process includes: In response to obtaining a trigger instruction for a connector editing control, displaying a custom connector editing page; Create a target connector using the connector creation instruction obtained from the custom connector editing page; A node to be edited of an integrated process type is added to the target process, and the node to be edited of the integrated process type is used to call the target connector.

6. The method according to claim 3, characterized in that The second process type node is a business node, and the step of displaying a node selection control in response to acquiring an insertion instruction generated by a trigger for an insertion control includes: In response to acquiring an insertion instruction generated by a trigger for inserting a control, displaying at least one business node identifier, each of the business node identifiers corresponding to a category of business operations; In response to triggering the node selection control, adding a node to be edited of the second process type corresponding to the node selection control in the target process includes: In response to triggering a selection instruction for a target service node identifier, a node to be edited of a service process type corresponding to the target service node identifier is added to the target process.

7. The method according to claim 3, characterized in that The second process type node is an approval node, and the step of displaying a node selection control in response to acquiring an insertion instruction generated by a trigger for an insertion control includes: In response to obtaining an insert instruction generated by a trigger for inserting a control, displaying an approval node identifier; In response to triggering the node selection control, adding a node to be edited of the second process type corresponding to the node selection control in the target process includes: In response to triggering a selection instruction for an approval node identifier, a to-be-edited node of an approval process type corresponding to the approval node identifier is added to the target process.

8. The method according to claim 1, characterized in that: The first process type node is a business node, and the second process type node is an approval node or an integration node.

9. A process editing device, characterized in that: The device is applied to a low-code platform, and the device includes: A display unit, used to display a process editing page, wherein the process editing page is used to edit a target process, wherein the target process includes a first process type node; An adding unit is used to add a second process type node in the target process in response to obtaining an adding instruction for a second process type node, wherein the second process type to which the second process type node belongs is different from the first process type to which the first process type node belongs, and the first process type and the second process type are determined based on the process processing logic.

10. An electronic device, characterized in that: include: one or more processors; A storage device having one or more programs stored thereon, when the one or more programs are executed by the one or more processors, the one or more processors implement the method according to any one of claims 1-8.

11. A computer readable medium, characterized in that A computer program is stored thereon, wherein when the program is executed by a processor, the method according to any one of claims 1 to 8 is implemented.

Images