Flow processing method and device, equipment, medium and program product

Abstract

The embodiment of the invention provides a process processing method and device, equipment, a medium and a program product. The method comprises the steps of determining a task type corresponding to a to-be-created task process in response to a creation trigger operation, and obtaining process general metadata corresponding to the task type; a pre-established task state machine corresponding to the task process and task metadata corresponding to the task process are obtained, the task state machine comprises at least one state machine node and a switching action corresponding to the state machine node, and the state machine node is associated with a task node in the task process; and creating the task process based on the process general metadata, the task state machine and the task metadata. According to the technical scheme, the method and the device are suitable for various task scenes, the task process corresponding to the task scene can be quickly generated, and the universality and the flexibility of the task process are improved.

Description

Technical Field

[0001] Embodiments of the present disclosure relate to computer technology, and in particular, to a process processing method, apparatus, device, medium, and program product. Background Art

[0002] In daily work, the concept of workflow often exists, that is, to complete a thing, the first step needs to be executed first, then the second step, then the third step, and finally the last step. Each step is often in series, requiring the previous step to be completed before proceeding further.

[0003] Currently, in various different task scenarios, it is often necessary to customize and design a set of process systems for a specific task scenario to control the promotion of the workflow and ensure that the pre - dependencies of each step are correctly executed. However, this process production method has technical problems of poor flexibility and low generality. Summary of the Invention

[0004] The present disclosure provides a process processing method, apparatus, device, medium, and program product to achieve relatively fast generation of corresponding task processes for different task scenarios, and improve the generality and flexibility of the task processes.

[0005] In a first aspect, an embodiment of the present disclosure provides a process processing method, which includes:

[0006] In response to a creation trigger operation, determine the task type corresponding to the task process to be created, and obtain the process general metadata corresponding to the task type;

[0007] Obtain the task state machine corresponding to the task process and the task metadata corresponding to the task process that are established in advance, where the task state machine includes at least one state machine node and a switching action corresponding to the state machine node, and the state machine node is associated with the task node in the task process;

[0008] Create the task process based on the process general metadata, the task state machine, and the task metadata.

[0009] In a second aspect, an embodiment of the present disclosure further provides a process processing apparatus, which includes:

[0010] A creation trigger module, configured to, in response to a creation trigger operation, determine the task type corresponding to the task process to be created, and obtain the process general metadata corresponding to the task type;

[0011] A data acquisition module, configured to acquire a pre-established task state machine corresponding to the task process and task metadata corresponding to the task process, wherein the task state machine includes at least one state machine node and a switching action corresponding to the state machine node, and the state machine node is associated with a task node in the task process;

[0012] A process creation module, configured to create the task process based on the process general metadata, the task state machine, and the task metadata.

[0013] In a third aspect, an embodiment of the present disclosure further provides an electronic device, which includes:

[0014] One or more processors;

[0015] A storage device, configured to store one or more programs,

[0016] When the one or more programs are executed by the one or more processors, the one or more processors are caused to implement the process processing method as described in any one of the embodiments of the present disclosure.

[0017] In a fourth aspect, an embodiment of the present disclosure further provides a storage medium containing computer-executable instructions, and the computer-executable instructions are used to execute the process processing method as described in any one of the embodiments of the present disclosure when executed by a computer processor.

[0018] In a fifth aspect, an embodiment of the present disclosure further provides a computer program product, which includes a computer program, and the computer program implements the process processing method as described in any one of the embodiments of the present disclosure when executed by a processor.

[0019] The technical solution of the embodiment of the present disclosure determines a task type corresponding to a task process to be created by responding to a creation trigger operation, and acquires process general metadata corresponding to the task type. In this technical solution, the task process is created through the process general metadata, which can improve the generality of the task process. The pre-established task state machine corresponding to the task process and the task metadata corresponding to the task process are acquired, wherein the task state machine includes at least one state machine node and a switching action corresponding to the state machine node, and the state machine node is associated with a task node in the task process. In this technical solution, the task process is created through the task state machine, which enriches the task scenarios of the task process. The task process is created based on the process general metadata, the task state machine, and the task metadata. The technical solution of the embodiment of the present disclosure realizes the relatively fast generation of corresponding task processes for different task scenarios, and improves the generality and flexibility of the task process. Description of the Drawings

[0020] In conjunction with the accompanying drawings and with reference to the following specific embodiments, the above and other features, advantages, and aspects of the various embodiments of the present disclosure will become more apparent. Throughout the drawings, the same or similar reference numerals denote the same or similar elements. It should be understood that the drawings are schematic and that the original and the elements are not necessarily drawn to scale.

[0021] Figure 1 A flowchart of a process processing method provided by an embodiment of the present disclosure;

[0022] Figure 2 An example diagram of a task state machine applicable to the process processing method provided by an embodiment of the present disclosure;

[0023] Figure 3 A flowchart of another process processing method provided by an embodiment of the present disclosure;

[0024] Figure 4 A flowchart of another process processing method provided by an embodiment of the present disclosure;

[0025] Figure 5 A schematic diagram of an optional embodiment of a process processing method provided by an embodiment of the present disclosure;

[0026] Figure 6 A flowchart of another process processing method provided by an embodiment of the present disclosure;

[0027] Figure 7 A flowchart of another process processing method provided by an embodiment of the present disclosure;

[0028] Figure 8 A schematic diagram of the structure of a process processing device provided by an embodiment of the present disclosure;

[0029] Figure 9 A schematic diagram of the structure of an electronic device provided by an embodiment of the present disclosure. Specific Embodiments

[0030] The embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although some embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure can be implemented in various forms and should not be construed as limited to the embodiments set forth herein. On the contrary, these embodiments are provided to more thoroughly and completely understand the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are only for exemplary purposes and are not used to limit the protection scope of the present disclosure.

[0031] It should be understood that the various steps recited in the method embodiments of the present disclosure may be executed in different orders and / or in parallel. In addition, the method embodiments may include additional steps and / or omit the steps shown. The scope of the present disclosure is not limited in this regard.

[0032] As used herein, the term "including" and its variations are open-ended, that is, "including but not limited to". The term "based on" means "at least partially based on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". The relevant definitions of other terms will be given in the following description.

[0033] It should be noted that the concepts such as "first" and "second" mentioned in the present disclosure are only used to distinguish different devices, modules or units, and are not used to limit the order of functions performed by these devices, modules or units or their interdependent relationships.

[0034] It should be noted that the modifications of "one" and "multiple" mentioned in the present disclosure are illustrative rather than restrictive. Those skilled in the art should understand that, unless otherwise clearly specified in the context, it should be understood as "one or more".

[0035] The names of the messages or information exchanged between multiple devices in the embodiments of the present disclosure are only for illustrative purposes and are not used to limit the scope of these messages or information.

[0036] It can be understood that before using the technical solutions disclosed in the embodiments of the present disclosure, the types, usage scopes, usage scenarios, etc. of the personal information involved in the present disclosure should be informed to the user and the user's authorization should be obtained in an appropriate manner in accordance with relevant laws and regulations.

[0037] For example, in response to receiving an active request from the user, a prompt message is sent to the user to clearly prompt the user that the operation requested by the user will require obtaining and using the user's personal information. Thus, the user can autonomously choose whether to provide personal information to software or hardware such as an electronic device, an application program, a server, or a storage medium that performs the operations of the technical solutions of the present disclosure according to the prompt message.

[0038] As an optional but non-limiting implementation manner, for example, the manner of sending a prompt message to the user in response to receiving an active request from the user may be in the form of a pop-up window, and the prompt message may be presented in text in the pop-up window. In addition, the pop-up window may also carry a selection control for the user to choose "agree" or "disagree" to provide personal information to the electronic device.

[0039] It can be understood that the above notification and the process of obtaining user authorization are only illustrative and do not limit the implementation manner of the present disclosure. Other manners that comply with relevant laws and regulations can also be applied to the implementation manner of the present disclosure.

[0040] It can be understood that the data involved in the present technical solution (including but not limited to the data itself, the acquisition or use of the data) should comply with the requirements of corresponding laws, regulations and related provisions.

[0041] Figure 1 FIG. is a schematic flowchart of a process processing method provided by an embodiment of the present disclosure. The embodiment of the present disclosure is applicable to the situation of processing a task flow. The method can be executed by a process processing device, and the device can be implemented in the form of software and / or hardware. Optionally, it is implemented by an electronic device, and the electronic device can be a mobile terminal, a PC or a server, etc.

[0042] As Figure 1 shown, the method of this embodiment may specifically include:

[0043] S110. In response to a creation trigger operation, determine a task type corresponding to a task flow to be created, and obtain process general metadata corresponding to the task type.

[0044] Among them, the creation trigger operation can be understood as a trigger operation for creating a task flow. The task type can be understood as the task type of the task flow. In the embodiment of the present disclosure, there are multiple ways to determine the task type corresponding to the task flow to be created. For example, at least one task type item for the task flow to be created can be displayed; after receiving a selection trigger operation acting on the task type item, determine the selected type item; use the task type corresponding to the selected task type item as the task type corresponding to the task flow to be created. Or, after receiving the creation trigger operation, a task type input box can be displayed, and after receiving the input task type based on the task input box, use the input task type as the task type corresponding to the task flow to be created. The correspondence between the task flow and the task type can be one-to-one or one-to-many.

[0045] In the embodiment of the present disclosure, metadata can be understood as information describing data attributes. Process general metadata can be understood as metadata shared by multiple task flows. In the embodiment of the present disclosure, obtaining the process general metadata corresponding to the task type may include: after determining the task type corresponding to the task flow to be created, determining the process general metadata corresponding to the task type according to the correspondence between the task type and the process general metadata.

[0046] In order to improve the generality and scalability of the task process, in the embodiments of the present invention, determining the process general metadata corresponding to the task type according to the correspondence between the task type and the process general metadata may include: determining a custom task class corresponding to the task type, where the custom task class defines private process general metadata; the custom task class inherits from a base task class, and the base task class defines public process general metadata; after determining the private process general metadata and the public process general metadata, the process general metadata corresponding to the task type may be obtained based on the private process general metadata and the public process general metadata.

[0047] Among them, the base task class can be understood as an abstract task class obtained by abstracting multiple task processes. The base task class defines public process general metadata. The custom task class can be understood as an entity task class obtained by inheriting the base task class according to a specific task. The custom task class defines private process general metadata.

[0048] S120. Obtain a pre-established task state machine corresponding to the task process and task metadata corresponding to the task process.

[0049] Among them, the task state machine can be a state machine pre-created for a certain task process. The task state machine may include at least one state machine node and a switching action corresponding to the state machine node. The state machine node is associated with a task node in the task process. Among them, the task node can be understood as the node corresponding to the task included in the task process. As Figure 2 shown, the state machine nodes in the task state machine include Step A, Step B, and Step C. Among them, the switching actions corresponding to Step A, Step B, and Step C can be query action, modification action, and continue processing action respectively. In the embodiments of the present disclosure, the task metadata can be understood as metadata with task differences, that is, task-differentiated data. Optionally, the task metadata may include at least one set of key-value pair structured data. In the case where the task metadata includes multiple sets of key-value pair structured data, the format of the task metadata may be in the format of JS key-value pair data (JavaScript Object Notation, JSON).

[0050] In the embodiments of the present disclosure, obtaining a pre-established task state machine corresponding to the task process may include: determining a storage location for storing the task state machine corresponding to the task process; reading the task state machine from the storage location, so as to obtain the task state machine corresponding to the task process.

[0051] In order to be able to determine relatively quickly the storage location for storing the task state machine corresponding to the task process, optionally, a list for storing the correspondence between the task process and the task state machine is created in advance. Among them, the information of the task process and the information of the task state machine in the list can be stored correspondingly.

[0052] In the embodiments of the present disclosure, obtaining the task metadata corresponding to the task process may include: determining a specific task class corresponding to the task process, where the data structure of the task metadata for the task process is defined in the specific task class. Among them, at least one task field is included in the data structure of the task metadata. The task metadata corresponding to the task process is obtained based on the at least one field.

[0053] S130. Create the task process based on the process general metadata, the task state machine, and the task metadata.

[0054] Specifically, in response to a creation trigger operation, the process general metadata, the task state machine, and the task metadata are used as actual parameters and passed to the formal parameters of a predefined task process creation interface. After the parameter passing is completed, by executing the task process creation interface, the task process is created based on the process general metadata, the task state machine, and the task metadata. Among them, the task process creation interface can be understood as a predefined interface for creating a task process.

[0055] Optionally, creating the task process based on the process general metadata, the task state machine, and the task metadata by executing the task process creation interface may include: passing the process general metadata, the task state machine, and the task metadata as actual parameters to the formal parameters of a task process creation method corresponding to the task process creation interface through the task process creation interface. The task process is created by executing the task process creation method. Among them, the task process creation method can be understood as a predefined method for implementing the function of creating a task process by the task process creation interface.

[0056] In the technical solution of the embodiment of the present disclosure, in response to a creation trigger operation, the task type corresponding to the task process to be created is determined, and the process general metadata corresponding to the task type is obtained. In this technical solution, the task process is created through the process general metadata, which can improve the generality of the task process. The task state machine corresponding to the task process established in advance and the task metadata corresponding to the task process are obtained, where the task state machine includes at least one state machine node and a switching action corresponding to the state machine node, and the state machine node is associated with the task node in the task process. In this technical solution, the task process is created through the task state machine, which enriches the task scenarios of the task process. The task process is created based on the process general metadata, the task state machine, and the task metadata. The technical solution of the embodiment of the present disclosure realizes generating corresponding task processes for different task scenarios relatively quickly, and improves the generality and flexibility of the task process.

[0057] Figure 3 It is a flowchart of another process processing method provided by the embodiment of the present disclosure. Based on the technical solution of the above embodiment, optionally, the process general metadata at least includes a task type field, a state machine node field, and a task context information field corresponding to the task process; the creating the task process based on the process general metadata, the task state machine, and the task metadata includes: assigning the task type corresponding to the task process to the task type field; determining state machine node parameters based on the state machine nodes included in the task state machine, and assigning the state machine node parameters to the state machine node field; assigning the task metadata corresponding to the task type to the task context information field; generating the task process based on the assigned process general metadata. The specific implementation can refer to the description of this embodiment. Among them, the technical features that are the same as or similar to the foregoing embodiments will not be described again.

[0058] As Figure 3 shown, the method of this embodiment may specifically include:

[0059] S210. In response to a creation trigger operation, determine the task type corresponding to the task process to be created, and obtain the process general metadata corresponding to the task type, where the process general metadata at least includes a task type field, a state machine node field, and a task context information field corresponding to the task process.

[0060] In the embodiments of the present disclosure, the task type field can be understood as a field for recording the task type of the task process. The state machine node field can be understood as a field for recording the state nodes of the task state machine corresponding to the task process. The task context information field can be understood as a field for recording the information obtained during the task processing. Optionally, the process general metadata may further include at least one of a process description field, a creator field, an authorization field, a creation time field, an update time field, and an error information field corresponding to the task process.

[0061] Among them, the process description field can be used to record the introduction and description information for the task process (for example, the applicable scenario). The creator field can be used to record the creator of the task process. The authorization field can be used to record the operator who has the permission to use the task process. The creation time field can be used to record the creation time of the task process. The update time field can be used to record the update time of the task process. The error information field can be used to record the error information of the task process.

[0062] S220. Obtain the pre-established task state machine corresponding to the task process and the task metadata corresponding to the task process, where the task state machine includes at least one state machine node and a switching action corresponding to the state machine node, and the state machine node is associated with a task node in the task process.

[0063] In the embodiments of the present disclosure, the task metadata may include task keyword fields corresponding to each of the state machine nodes and task running data corresponding to the task keyword fields, stored in the form of key-value pairs or JSON. Among them, the task keyword field can be a task field associated with a specific task, set for the task metadata of the specific task. The task running data can be understood as the field value corresponding to the task keyword field. It should be noted that the task keyword fields corresponding to different state machine nodes can be the same or different.

[0064] S230. Assign the task type corresponding to the task process to the task type field, determine the state machine node parameters based on the state machine nodes included in the task state machine, assign the state machine node parameters to the state machine node field, and assign the task metadata corresponding to the task type to the task context information field.

[0065] Among them, the state machine node parameters can be understood as the node information of the state machine nodes. In the embodiments of the present disclosure, determining the state machine node parameters based on the state machine nodes included in the task state machine and assigning the state machine node parameters to the state machine node fields may include: determining the state machine nodes included in the task state machine; obtaining the node parameters of the state machine nodes, that is, the state machine node parameters; and assigning the state machine node parameters to the state machine node fields.

[0066] Specifically, for the task type, assign the task type corresponding to the task process to the task type field. For the state machine nodes in the task state machine, the state machine nodes included in the task state machine can be analyzed to determine the current state machine node. Further, the node parameters of the current state machine node can be obtained, that is, the state machine node parameters are determined. Further, the state machine node parameters can be assigned to the state machine node fields. For the task metadata corresponding to the task type, the task metadata corresponding to the task type can be assigned to the task context information field.

[0067] S240. Generate the task process based on the assigned process general metadata.

[0068] Specifically, after the assignment of the process general metadata is completed, the assigned process general metadata can be obtained. The assigned process general metadata is passed as an actual parameter to the formal parameter of the task process method. After the parameter passing is completed, a task process is created according to the task process creation logic in the task process method.

[0069] In the embodiments of the present disclosure, after creating the task process based on the process general metadata, the task state machine, and the task metadata, it may further include: when detecting the switching action corresponding to the state machine node, updating the state machine node parameters to the target node parameters. Among them, the target state machine node parameters can be understood as the state machine node parameters of the next state machine node corresponding to the current state machine node parameters.

[0070] Specifically, after detecting the switching action for the state machine node, the next state machine node of the state machine node can be determined, the state machine node parameters of the next state machine node of the state machine node can be determined, and the state machine node parameters of the next state machine node of the state machine node are used as the current state machine node parameters.

[0071] Exemplarily, refer to Figure 2, after receiving the continue processing action for step A, the node parameters corresponding to step B can be obtained. At this time, the current state machine node parameters change from the node parameters corresponding to step A to the node parameters corresponding to step B. The purpose of such processing is to be able to continue the switching action processing based on step B to achieve the processing of the task flow.

[0072] To ensure that the switching action corresponding to the state machine node can be effectively executed, in the embodiments of the present disclosure, before updating the state machine node parameters to the target node parameters, it may further include: determining whether the state machine node parameters required by the next state machine node of the state machine node exist and are correct. If so, the switching action corresponding to the state machine node can be executed, that is, the next state machine node of the state machine node is used as the current state machine node, and the state machine node parameters are updated to the target node parameters.

[0073] In the embodiments of the present disclosure, the process general metadata may include a process running status field corresponding to the task flow. The process running status field can be understood as a field for recording the process running status. Exemplarily, the process running status may include running, running successfully, running failed, and running cancelled. Creating the task flow based on the process general metadata, the task state machine, and the task metadata may further include: obtaining a process running status parameter and assigning the process running status parameter to the process running status field.

[0074] In the embodiments of the present disclosure, after the task flow is successfully created, the process running status of the task flow can be set to running. After detecting that the task flow is executed, the process running status of the task flow can be modified to running successfully. After detecting that the task flow cannot be executed, the process running status can be running failed. After receiving a running cancellation operation for the task flow, the process running status of the task flow can be modified to running cancelled.

[0075] Based on the above embodiments, after creating the task flow based on the process general metadata, the task state machine, and the task metadata, it may further include: in the case where the process running status parameter is a preset running parameter, determining a task execution result corresponding to the state machine node parameter based on the task metadata and displaying the task execution result in a display area corresponding to the task flow. Wherein, the preset running parameter is a parameter for indicating that the task flow is in a running state.

[0076] Specifically, when the process running state parameter is a preset running parameter, the state machine node parameter can be determined. Further, according to the correspondence between the task metadata and the state machine node parameter, the task metadata corresponding to the state machine node parameter can be determined. At this time, it can be determined that the task metadata corresponding to the state machine node parameter is the task execution result corresponding to the state machine node parameter, that is, the task execution result corresponding to the state machine node parameter is obtained. Further, the task execution result can be displayed in the display area corresponding to the task process.

[0077] In the technical solution of the embodiment of the present disclosure, the task type corresponding to the task process is assigned to the task type field; the state machine node parameter is determined based on the state machine node included in the task state machine, and the state machine node parameter is assigned to the state machine node field; the task metadata corresponding to the task type is assigned to the task context information field; and the task process is generated based on the assigned process general metadata, realizing further refinement of the generation of the task process.

[0078] Figure 4 It is a flowchart of another process processing method provided by the embodiment of the present disclosure. Based on the above embodiment, optionally, after creating the task process based on the process general metadata, the task state machine, and the task metadata, the method further includes: in response to a modification trigger operation input for the task process, displaying the process general metadata corresponding to the task process; and in response to an editing trigger operation input for the process general metadata, updating the task process, where the editing trigger operation includes at least one of a metadata addition trigger operation, a metadata deletion trigger operation, and a metadata modification trigger operation. For specific implementation manners, reference can be made to the description of this embodiment. Among them, the same or similar technical features as those in the foregoing embodiments will not be described herein again.

[0079] As Figure 4 shown, the method of this embodiment may specifically include:

[0080] S310. In response to a creation trigger operation, determine the task type corresponding to the task process to be created, and obtain the process general metadata corresponding to the task type.

[0081] S320. Obtain the task state machine corresponding to the task process and the task metadata corresponding to the task process that are established in advance, where the task state machine includes at least one state machine node and a switching action corresponding to the state machine node, and the state machine node is associated with a task node in the task process.

[0082] S330. Create the task process based on the process general metadata, the task state machine, and the task metadata.

[0083] S340. In response to a modification trigger operation input for the task process, display the process general metadata corresponding to the task process.

[0084] Among them, the modification trigger operation can be understood as a trigger operation for modifying the process general metadata of the task process.

[0085] In an embodiment of the present invention, after receiving a modification trigger operation input for the task process, the selected task process can be determined. According to the correspondence between the task process and the process general metadata, the process general metadata corresponding to the task process can be determined. After determining the process general metadata corresponding to the task process, the process general metadata corresponding to the task process can be displayed.

[0086] Specifically, after receiving a modification trigger operation input for the task process, the identifier of the task process can be determined. The identifier of the task process can be used as an actual parameter and passed to the formal parameter of a predefined process general metadata acquisition method. After the parameter passing is completed, by executing the process general metadata acquisition method, the process general metadata corresponding to the task process can be determined. After determining the process general metadata, the process general metadata can be displayed. Among them, the process general metadata acquisition method can be understood as a method for acquiring process general metadata.

[0087] S350. In response to an edit trigger operation input for the process general metadata, update the task process.

[0088] Among them, the edit trigger operation can include at least one of a metadata addition trigger operation, a metadata deletion trigger operation, and a metadata modification trigger operation. The metadata addition trigger operation can be understood as a trigger operation for adding fields to the process general metadata. The metadata deletion trigger operation can be understood as a trigger operation for deleting fields in the process general metadata. The metadata modification trigger operation can be understood as a trigger operation for modifying fields in the process general metadata.

[0089] As an optional embodiment of the present disclosure, refer to Figure 5 , in response to a metadata addition trigger operation input for the process general metadata, updating the task process can include: after receiving a metadata addition trigger operation input for the process general metadata ( Figure 5In the creation operation), new fields set for the process general metadata can be obtained. Subsequently, the new fields can be used as actual parameters and passed to a predefined metadata addition interface ( Figure 5 the new data interface in). After the parameter passing is completed, based on the metadata addition interface, the new fields are added to the process general metadata. Subsequently, the task process can be updated based on the process general metadata with the added fields. Herein, the new fields can be understood as newly added fields in the process general metadata settings. The metadata addition interface can be a predefined interface for adding fields to the process general metadata.

[0090] As an optional embodiment of the present disclosure, in response to a metadata modification trigger operation input for the process general metadata, updating the task process may include: after receiving the metadata modification trigger operation ( Figure 5 the modification operation in), the fields to be modified in the process general metadata and the target fields corresponding to the fields to be modified can be determined. By calling a predefined metadata modification interface ( Figure 5 the modification record interface in), the fields to be modified in the process general metadata are modified to the target fields corresponding to the fields to be modified, so that the fields to be modified in the process general metadata become the target fields. After the modification is completed, the task process can be updated based on the process general metadata with the modified fields. Herein, the fields to be modified can be understood as the fields that need to be modified in the process general metadata. The target fields can be understood as the fields obtained after modifying the fields to be modified in the process general metadata. The metadata modification interface can be understood as a predefined interface for modifying the fields in the process general metadata.

[0091] As an optional embodiment of the present disclosure, in response to a metadata deletion trigger operation input for the process general metadata, updating the task process may include: after receiving the metadata deletion trigger operation input for the process general metadata, the fields to be deleted in the process general metadata can be determined. The status of the fields to be deleted can be set to an unavailable state by calling a predefined metadata modification interface, so that the fields to be deleted are in an invalid state, thereby achieving the deletion effect for the fields to be deleted. The task process is updated based on the fields in the process general metadata that are in an available state. Herein, the fields to be deleted can be understood as the fields that need to be deleted in the process general metadata.

[0092] In the embodiments of the present disclosure, by calling the metadata modification interface to delete fields in the process general metadata, the advantage of this is that if a field in an invalid state is used subsequently, the state of the field can be set to an available state so that the field in the process general metadata can be used, without the need to add the field again.

[0093] As an optional embodiment of the embodiments of the present disclosure, in response to a metadata deletion trigger operation input for the process general metadata, updating the task process may include: upon receiving a metadata deletion trigger operation input for the process general metadata ( Figure 5 the deletion operation in), the fields to be deleted in the process general metadata can be determined. By calling a predefined metadata deletion interface, the fields to be deleted in the process general metadata are deleted. Specifically, the fields to be deleted are used as actual parameters and passed to the formal parameters of the metadata deletion interface; after the parameter passing is completed, by executing the interface implementation method corresponding to the metadata deletion interface, the fields to be deleted in the process general metadata are deleted. Thus, the process general metadata with the deleted fields can be obtained. Furthermore, based on the process general metadata with the deleted fields, the task process can be updated. Among them, the metadata deletion interface can be understood as an interface for deleting fields in the process general metadata.

[0094] The technical solution of the embodiments of the present disclosure, after creating the task process based on the process general metadata, the task state machine, and the task metadata, by responding to a modification trigger operation input for the task process, displaying the process general metadata corresponding to the task process; and responding to an edit trigger operation input for the process general metadata, updating the task process, realizes the editing process of the process general metadata according to actual needs, thereby improving the flexibility and scalability of the task process.

[0095] Figure 6 It is a flowchart of another process processing method provided by the embodiments of the present disclosure. Based on the above embodiments, optionally, after creating the task process based on the process general metadata, the task state machine, and the task metadata, the method further includes: in response to a modification trigger operation for modifying task data input on the task operation interface, updating the task data on the task operation interface, and updating the task process based on the updated task data. The specific implementation can refer to the description of this embodiment. Among them, the technical features that are the same or similar to the foregoing embodiments will not be described again.

[0096] As Figure 6 shown, the method of this embodiment may specifically include:

[0097] S410. In response to a creation trigger operation, determine a task type corresponding to the task process to be created, and obtain process general metadata corresponding to the task type.

[0098] S420. Obtain a pre-established task state machine corresponding to the task process and task metadata corresponding to the task process, where the task state machine includes at least one state machine node and a switching action corresponding to the state machine node, and the state machine node is associated with a task node in the task process.

[0099] S430. Create the task process based on the process general metadata, the task state machine, and the task metadata.

[0100] S440. In response to a modification trigger operation for modifying task data input on a task operation interface, update the task data on the task operation interface, and update the task process based on the updated task data.

[0101] Among them, the task operation interface can be understood as an interface for controlling the execution logic of the task process. One or more task data can be displayed on the task operation interface. In practical applications, usually the number of task data displayed on the task operation interface is one or more.

[0102] Specifically, after receiving a modification trigger operation for modifying task data input on the task operation interface, the task data to be modified can be determined. After receiving modification data for the task data to be modified, the task data to be modified displayed on the task operation interface can be updated to the modification data to modify the task data displayed on the task operation interface. After the modification, the modified task data can be obtained from the task operation interface, that is, the updated task data can be obtained from the task operation interface. After obtaining the updated task data, the task process can be updated based on the updated task data.

[0103] The technical solution of the embodiments of the present disclosure, in response to a modification trigger operation for modifying task data input on a task operation interface, updates the task data on the task operation interface, and updates the task process based on the updated task data, achieving the technical effect of flexibly modifying task data in the task process.

[0104] Figure 7Schematic diagram of another process handling method provided by an embodiment of the present disclosure. Based on the technical solution of this embodiment on the basis of the above embodiment, optionally, the process general metadata at least includes a process record identification field of the task process; after creating the task process based on the process general metadata, the task state machine, and the task metadata, it further includes: in response to a data query trigger operation, obtaining a process record of the task process based on the process identifier in the process record identification field; determining target query data corresponding to the data query trigger operation based on the process record, and displaying the target query data. For specific implementation manners, reference may be made to the description of this embodiment. Among them, the same or similar technical features as those in the foregoing embodiments will not be described herein again.

[0105] As Figure 7 shown, the method of this embodiment may specifically include:

[0106] S510. In response to a creation trigger operation, determine a task type corresponding to a task process to be created, and obtain process general metadata corresponding to the task type, where the process general metadata at least includes a process record identification field of the task process.

[0107] Among them, the process record identification field may be used to record the record identifier of the task process. The data type of the process record identification field may be the bigint data type.

[0108] S520. Obtain a pre-established task state machine corresponding to the task process and task metadata corresponding to the task process, where the task state machine includes at least one state machine node and a switching action corresponding to the state machine node, and the state machine node is associated with a task node in the task process.

[0109] S530. Create the task process based on the process general metadata, the task state machine, and the task metadata.

[0110] S540. In response to a data query trigger operation, obtain a process record of the task process based on the process identifier in the process record identification field.

[0111] Among them, the data query trigger operation may be understood as a trigger operation for querying the process record of the task process. The process identifier may be used to distinguish different process records. The correspondence between the process identifier and the process record may be one-to-one. In other words, one process identifier corresponds to one process record.

[0112] As an optional embodiment in the embodiments of the present disclosure, in response to a data query trigger operation, obtaining a process record of the task process based on the process identifier in the process record identifier field may include: after receiving the data query trigger operation, reading the process identifier in the process record identifier field. After reading the process identifier, based on the correspondence between the process identifier and the process record, the process record corresponding to the process identifier, that is, the process record of the task process, may be determined.

[0113] Optionally, based on the correspondence between the process identifier and the process record, determining the process record corresponding to the process identifier may include: after reading the process identifier, the process identifier may be passed as an actual parameter to the formal parameter of a predefined first process record query interface; after the parameter passing is completed, based on the first process record query interface, the process record corresponding to the process identifier may be determined. Among them, the first process record query interface may be understood as an interface for querying a process record.

[0114] As another optional embodiment in the embodiments of the present disclosure, in response to a data query trigger operation, obtaining a process record of the task process based on the process identifier in the process record identifier field may include: after receiving the data query trigger operation, reading the process identifier from the process record identifier field. In the case where there is no specific streamline identifier in the process record identifier field, at this time, it may be defaulted that all process records to be queried are required. Further, all process records stored in the data table may be read from the data table for storing streamline records.

[0115] Optionally, in the case where there is no specific streamline identifier in the process record identifier field, reading all process records stored in the data table from the data table for storing streamline records may include: in the case where there is no specific streamline identifier in the process record identifier field, by calling a predefined second process record query interface, all process records stored in the data table are read from the data table for storing streamline records. Among them, the second process record query interface may be understood as a predefined interface for obtaining all process records.

[0116] S550. Determine target query data corresponding to the data query trigger operation based on the process record, and display the target query data.

[0117] Among them, the target query data may be understood as the data to be queried in the process record. Among them, the number of target query data may be one, two or more than two.

[0118] Specifically, after receiving a data query trigger operation, the fields to be queried corresponding to the data query trigger operation can be determined. After obtaining the process record, the field values corresponding to the fields to be queried can be determined from the process record, that is, the target query data. After determining the target query data, the target query data can be displayed.

[0119] Optionally, when the number of fields to be queried is multiple, the display arrangement order of each field to be queried can be preset in advance. Furthermore, based on the display sorting order, each of the fields to be queried can be displayed in sequence to improve the display effect of the page.

[0120] The technical solution of the embodiment of the present disclosure responds to a data query trigger operation, obtains the process record of the task process based on the process identifier in the process record identifier field; determines the target query data corresponding to the data query trigger operation based on the process record, and displays the target query data, achieving the technical effect of querying data from the process record according to the actual task requirements.

[0121] Figure 8 It is a schematic structural diagram of a process processing device provided by an embodiment of the present disclosure, as Figure 8 shown, the device includes: a creation trigger module 610, a data acquisition module 620, and a process creation module 630.

[0122] Among them, the creation trigger module 610 is configured to, in response to a creation trigger operation, determine the task type corresponding to the task process to be created, and obtain the process general metadata corresponding to the task type; the data acquisition module 620 is configured to acquire the task state machine established in advance corresponding to the task process and the task metadata corresponding to the task process, where the task state machine includes at least one state machine node and a switching action corresponding to the state machine node, and the state machine node is associated with the task node in the task process; the process creation module 630 is configured to create the task process based on the process general metadata, the task state machine, and the task metadata.

[0123] The technical solution of the embodiment of the present disclosure determines a task type corresponding to a task process to be created in response to a creation trigger operation, and obtains process general metadata corresponding to the task type. In this technical solution, creating a task process through the process general metadata can improve the generality of the task process, obtain a pre-established task state machine corresponding to the task process and task metadata corresponding to the task process, wherein the task state machine includes at least one state machine node and a switching action corresponding to the state machine node, and the state machine node is associated with a task node in the task process. In this technical solution, creating a task process through the task state machine enriches the task scenarios of the task process. The task process is created based on the process general metadata, the task state machine, and the task metadata. The technical solution of the embodiment of the present disclosure realizes generating corresponding task processes for different task scenarios relatively quickly, and improves the generality and flexibility of the task process.

[0124] Based on the above optional technical solutions, optionally, the process general metadata at least includes a task type field corresponding to the task process, a state machine node field, and a task context information field; the process creation module 630 is specifically configured to:

[0125] Assign the task type corresponding to the task process to the task type field;

[0126] Determine state machine node parameters based on the state machine nodes included in the task state machine, and assign the state machine node parameters to the state machine node field;

[0127] Assign the task metadata corresponding to the task type to the task context information field;

[0128] Generate the task process based on the assigned process general metadata.

[0129] Based on the above optional technical solutions, optionally, the process general metadata includes a process running status field corresponding to the task process; the process creation module 630 is further configured to:

[0130] Obtain a process running status parameter, and assign the process running status parameter to the process running status field.

[0131] Based on the above optional technical solutions, optionally, the process processing device further includes an execution result display module; the execution result display module is configured to:

[0132] After creating the task process based on the process general metadata, the task state machine, and the task metadata, when the process running state parameter is a preset running parameter, determine a task execution result corresponding to the state machine node parameter based on the task metadata, and display the task execution result in a display area corresponding to the task process, where the preset running parameter is a parameter used to indicate that the task process is in a running state.

[0133] Based on the above optional technical solutions, optionally, the process processing device further includes a state machine node parameter update module; the state machine node parameter update module is used for:

[0134] After creating the task process based on the process general metadata, the task state machine, and the task metadata, when detecting the switching action corresponding to the state machine node, update the state machine node parameter to a target node parameter, where the target state machine node parameter is the state machine node parameter of the next state machine node corresponding to the current state machine node parameter.

[0135] Based on the above optional technical solutions, optionally, the process general metadata further includes at least one of a process description field, a creator field, an authorization field, a creation time field, an update time field, and an error information field corresponding to the task process.

[0136] Based on the above optional technical solutions, optionally, the task metadata includes task keyword fields corresponding to each state machine node and task running data corresponding to the task keyword fields, stored in the form of key-value pairs or JSON.

[0137] Based on the above optional technical solutions, optionally, the process processing device further includes a metadata editing module; the metadata editing module is used for:

[0138] After creating the task process based on the process general metadata, the task state machine, and the task metadata, in response to a modification trigger operation input for the task process, display the process general metadata corresponding to the task process;

[0139] In response to an editing trigger operation input for the process general metadata, update the task process, where the editing trigger operation includes at least one of a metadata addition trigger operation, a metadata deletion trigger operation, and a metadata modification trigger operation.

[0140] Based on the above optional technical solutions, optionally, the process processing device further includes a task data modification module; the task data modification module is used for:

[0141] After creating the task process based on the process general metadata, the task state machine, and the task metadata, in response to a modification trigger operation for modifying task data input on the task operation interface, update the task data on the task operation interface, and update the task process based on the updated task data.

[0142] Based on the above optional technical solutions, optionally, the process general metadata at least includes a process record identification field of the task process; the process processing device further includes a data query module; the data query module is configured to:

[0143] After creating the task process based on the process general metadata, the task state machine, and the task metadata, in response to a data query trigger operation, obtain a process record of the task process based on the process identification in the process record identification field;

[0144] Determine target query data corresponding to the data query trigger operation based on the process record, and display the target query data.

[0145] The process processing device provided by the embodiments of the present disclosure can execute the process processing method provided by any embodiment of the present disclosure, and has corresponding functional modules and beneficial effects for executing the method.

[0146] It should be noted that the various units and modules included in the above device are only divided according to functional logic, but are not limited to the above division, as long as the corresponding functions can be realized; in addition, the specific names of the functional units are only for the convenience of mutual distinction and do not limit the protection scope of the embodiments of the present disclosure.

[0147] Figure 9 It is a schematic structural diagram of an electronic device provided by an embodiment of the present disclosure. The following refers to Figure 9 , which shows a schematic structural diagram of an electronic device (such as Figure 9 the terminal device or server) 500 suitable for implementing the embodiments of the present disclosure. The terminal device in the embodiments of the present disclosure may include, but is not limited to, mobile terminals such as mobile phones, laptop computers, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Tablet Computers), PMPs (Portable Multimedia Players), in-vehicle terminals (such as in-vehicle navigation terminals), etc., and fixed terminals such as digital TVs, desktop computers, etc. Figure 9 The electronic device shown is only an example and should not bring any limitation to the functions and usage scopes of the embodiments of the present disclosure.

[0148] Such as Figure 9As shown, the electronic device 500 may include a processing device (such as a central processing unit, a graphics processing unit, etc.) 501, which may perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 502 or a program loaded from a storage device 508 into a random access memory (RAM) 503. In the RAM 503, various programs and data required for the operation of the electronic device 500 are also stored. The processing device 501, the ROM 502, and the RAM 503 are connected to each other through a bus 504. An editing / output (I / O) interface 505 is also connected to the bus 504.

[0149] Generally, the following devices may be connected to the I / O interface 505: an input device 506 including, for example, a touch screen, a touchpad, a keyboard, a mouse, a camera, a microphone, an accelerometer, a gyroscope, etc.; an output device 507 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc.; a storage device 508 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 509. The communication device 509 may allow the electronic device 500 to communicate with other devices wirelessly or wiredly to exchange data. Although Figure 9 an electronic device 500 with various devices is shown, it should be understood that it is not required to implement or have all the shown devices. Instead, more or fewer devices may be implemented or had.

[0150] Specifically, according to an embodiment of the present disclosure, the process described above with reference to the flowchart may be implemented as a computer software program. For example, an embodiment of the present disclosure includes a computer program product, which includes a computer program carried on a non-transitory computer-readable medium, and the computer program includes program codes for performing the method shown in the flowchart. In such an embodiment, the computer program may be downloaded and installed from a network through the communication device 509, or installed from the storage device 508, or installed from the ROM 502. When the computer program is executed by the processing device 501, the above-mentioned functions defined in the method of the embodiment of the present disclosure are executed.

[0151] The names of the messages or information exchanged between multiple devices in the embodiments of the present disclosure are only for illustrative purposes and are not used to limit the scope of these messages or information.

[0152] The electronic device provided by the embodiment of the present disclosure and the process processing method provided by the above embodiment belong to the same inventive concept. Technical details not described in detail in this embodiment may be referred to the above embodiment, and this embodiment has the same beneficial effects as the above embodiment.

[0153] The embodiment of the present disclosure provides a computer storage medium, on which a computer program is stored, and when the program is executed by a processor, the process processing method provided by the above embodiment is implemented.

[0154] It should be noted that the above-mentioned computer-readable medium in the present disclosure may be a computer-readable signal medium, a computer-readable storage medium, or any combination of the two. A computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the above. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having 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 disclosure, a computer-readable storage medium may be any tangible medium that contains or stores a program, and this program can be used by or in conjunction with an instruction execution system, apparatus, or device. In the present disclosure, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, in which computer-readable program code is carried. Such a propagated data signal may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. A computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium, and this computer-readable signal medium can 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 a computer-readable medium can be transmitted by any appropriate medium, including but not limited to: wires, optical cables, RF (radio frequency), etc., or any suitable combination of the above.

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

[0156] The above-mentioned computer-readable medium may be included in the above-mentioned electronic device; or it may exist separately and not be assembled into the electronic device.

[0157] The above computer-readable medium carries one or more programs, which, when executed by the electronic device, cause the electronic device to: in response to a creation trigger operation, determine a task type corresponding to a task process to be created, and obtain process general metadata corresponding to the task type;

[0158] Obtain a pre-established task state machine corresponding to the task process and task metadata corresponding to the task process, where the task state machine includes at least one state machine node and a switching action corresponding to the state machine node, and the state machine node is associated with the task process;

[0159] Create the task process based on the process general metadata, the task state machine, and the task metadata.

[0160] Computer program code for performing the operations of the present disclosure may be written in one or more programming languages or combinations thereof. The programming languages include, but are not limited to, object-oriented programming languages such as Java, Smalltalk, C++, and also include conventional procedural programming languages such as the "C" language or similar programming languages. The program code may execute entirely on the user's computer, partially on the user's computer, as a stand-alone software package, partially on the user's computer and partially on a remote computer, or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through 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).

[0161] The flowcharts and block diagrams in the accompanying drawings illustrate the possible architectures, functions, and operations of systems, methods, and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagram may represent a module, a program segment, or a part of code that contains one or more executable instructions for implementing a specified logical function. It should also be noted that, in some alternative implementations, the functions marked in the blocks may occur in a different order than marked in the accompanying drawings. For example, two consecutive blocks shown may actually be executed substantially in parallel, and they may sometimes be executed in the reverse order, depending on the functions involved. It should also be noted that each block in the block diagram and / or flowchart, and combinations of blocks in the block diagram and / or flowchart, may be implemented by a dedicated hardware-based system for performing the specified functions or operations, or may be implemented by a combination of dedicated hardware and computer instructions.

[0162] The units involved in the embodiments of the present disclosure can be implemented in software or in hardware. Among them, the name of a unit does not constitute a limitation on the unit itself in certain cases. For example, the first acquisition unit can also be described as "the unit for acquiring at least two Internet protocol addresses".

[0163] The functions described above herein can be performed at least in part by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that can be used include: Field Programmable Gate Array (FPGA), Application Specific Integrated Circuit (ASIC), Application Specific Standard Product (ASSP), System on Chip (SOC), Complex Programmable Logic Device (CPLD), and so on.

[0164] In the context of the present disclosure, a machine-readable medium can be a tangible medium that can contain or store a program for use by or in connection with an instruction execution system, apparatus, or device. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium can include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on 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 Disc Read Only Memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0165] According to one or more embodiments of the present disclosure, [Example 1] provides a process processing method, including:

[0166] In response to a creation trigger operation, determine the task type corresponding to the task process to be created, and obtain the process general metadata corresponding to the task type;

[0167] Obtain the task state machine corresponding to the task process and the task metadata corresponding to the task process established in advance, where the task state machine includes at least one state machine node and a switching action corresponding to the state machine node, and the state machine node is associated with the task process;

[0168] Create the task process based on the process general metadata, the task state machine, and the task metadata.

[0169] According to one or more embodiments of the present disclosure, [Example 2] provides a process processing method, including:

[0170] The process general metadata at least includes a task type field, a state machine node field, and a task context information field corresponding to the task process;

[0171] Optionally, creating the task process based on the process general metadata, the task state machine, and the task metadata includes:

[0172] Assign the task type corresponding to the task process to the task type field;

[0173] Determine state machine node parameters based on the state machine nodes included in the task state machine, and assign the state machine node parameters to the state machine node field;

[0174] Assign the task metadata corresponding to the task type to the task context information field;

[0175] Generate the task process based on the process general metadata after assignment.

[0176] According to one or more embodiments of the present disclosure, [Example Three] provides a process processing method, including:

[0177] The process general metadata includes a process running status field corresponding to the task process;

[0178] Optionally, creating the task process based on the process general metadata, the task state machine, and the task metadata further includes:

[0179] Obtain a process running status parameter, and assign the process running status parameter to the process running status field.

[0180] According to one or more embodiments of the present disclosure, [Example Four] provides a process processing method, further including:

[0181] When the process running status parameter is a preset running parameter, determine a task execution result corresponding to the state machine node parameter based on the task metadata, and display the task execution result in a display area corresponding to the task process, where the preset running parameter is a parameter used to indicate that the task process is in a running state.

[0182] According to one or more embodiments of the present disclosure, [Example Five] provides a process processing method, further including:

[0183] When detecting the switching action corresponding to the state machine node, update the state machine node parameter to a target node parameter, where the target state machine node parameter is the state machine node parameter of the next state machine node corresponding to the current state machine node parameter.

[0184] According to one or more embodiments of the present disclosure, [Example Six] provides a process handling method, including:

[0185] The process general metadata further includes at least one of a process description field, a creator field, an authorization field, a creation time field, an update time field, and an error information field corresponding to the task process.

[0186] According to one or more embodiments of the present disclosure, [Example Seven] provides a process handling method, including:

[0187] The task metadata includes task keyword fields corresponding to each of the state machine nodes stored in a key-value pair form or a JSON form, and task running data corresponding to the task keyword fields.

[0188] According to one or more embodiments of the present disclosure, [Example Eight] provides a process handling method, further including:

[0189] In response to a modification trigger operation input for the task process, display the process general metadata corresponding to the task process;

[0190] In response to an edit trigger operation input for the process general metadata, update the task process, where the edit trigger operation includes at least one of a metadata addition trigger operation, a metadata deletion trigger operation, and a metadata modification trigger operation.

[0191] According to one or more embodiments of the present disclosure, [Example Nine] provides a process handling method, further including:

[0192] In response to a modification trigger operation input in the task operation interface for modifying task data, update the task data in the task operation interface, and update the task process based on the updated task data.

[0193] According to one or more embodiments of the present disclosure, [Example Ten] provides a process handling method, including:

[0194] The process general metadata at least includes a process record identification field of the task process;

[0195] Optionally, after creating the task process based on the process general metadata, the task state machine, and the task metadata, it further includes:

[0196] In response to a data query trigger operation, obtain a process record of the task process based on the process identification in the process record identification field;

[0197] Determine target query data corresponding to the data query trigger operation based on the process record, and display the target query data.

[0198] According to one or more embodiments of the present disclosure, [Example XI] provides a process processing apparatus, including:

[0199] A creation trigger module, configured to determine a task type corresponding to a task process to be created in response to a creation trigger operation, and obtain process general metadata corresponding to the task type;

[0200] A data acquisition module, configured to acquire a task state machine established in advance corresponding to the task process and task metadata corresponding to the task process, where the task state machine includes at least one state machine node and a switching action corresponding to the state machine node, and the state machine node is associated with the task process;

[0201] A process creation module, configured to create the task process based on the process general metadata, the task state machine, and the task metadata.

[0202] The above description is only a preferred embodiment of the present disclosure and an explanation of the applied technical principle. Those skilled in the art should understand that the scope of the disclosure involved in the present disclosure is not limited to the technical solution formed by the specific combination of the above technical features, and should also cover other technical solutions formed by any combination of the above technical features or their equivalent features without departing from the above disclosure concept. For example, a technical solution formed by mutually replacing the above features with technical features having similar functions disclosed in the present disclosure.

[0203] In addition, although the operations are depicted in a specific order, this should not be construed as requiring that the operations be performed in the specific order shown or in sequential order. In certain environments, multitasking and parallel processing may be advantageous. Similarly, although a number of specific implementation details are included in the above discussion, these should not be construed as limiting the scope of the present disclosure. Certain features described in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, the various features described in the context of a single embodiment may also be implemented separately or in any suitable sub-combination in multiple embodiments.

[0204] Although the subject matter has been described in language specific to structural features and / or methodological logical acts, it should be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. On the contrary, the specific features and acts described above are merely example forms of implementing the claims.

Claims

1. A process processing method, characterized in that: include: In response to a creation trigger operation, determining a task type corresponding to a task flow to be created, and acquiring process general metadata corresponding to the task type; Acquire a pre-established task state machine corresponding to the task flow and task metadata corresponding to the task flow, wherein the task state machine includes at least one state machine node and a switching action corresponding to the state machine node, and the state machine node is associated with a task node in the task flow; The task process is created based on the process general metadata, the task state machine and the task metadata.

2. The process processing method according to claim 1, characterized in that: The process general metadata includes at least a task type field, a state machine node field and a task context information field corresponding to the task process; The creating the task process based on the process general metadata, the task state machine and the task metadata includes: Assigning the task type corresponding to the task flow to the task type field; Determine a state machine node parameter based on the state machine node included in the task state machine, and assign the state machine node parameter to the state machine node field; Assigning the task metadata corresponding to the task type to the task context information field; The task process is generated based on the assigned process general metadata.

3. The process processing method according to claim 2, characterized in that: The process general metadata includes a process running status field corresponding to the task process; The step of creating the task process based on the process general metadata, the task state machine and the task metadata further includes: Obtain a process running state parameter, and assign the process running state parameter to the process running state field.

4. The process processing method according to claim 3, characterized in that: After creating the task process based on the process general metadata, the task state machine and the task metadata, the method further includes: When the process running state parameter is a preset running parameter, the task execution result corresponding to the state machine node parameter is determined based on the task metadata, and the task execution result is displayed in a display area corresponding to the task process, wherein the preset running parameter is a parameter used to indicate that the task process is in a running state.

5. The process processing method according to claim 2, characterized in that: After creating the task process based on the process general metadata, the task state machine and the task metadata, the method further includes: When the switching action corresponding to the state machine node is detected, the state machine node parameters are updated to target node parameters, wherein the target state machine node parameters are state machine node parameters of the next state machine node of the state machine node corresponding to the current state machine node parameters.

6. The process processing method according to claim 2, characterized in that: The process general metadata also includes at least one of a process description field, a creator field, an authorization field, a creation time field, an update time field, and an error information field corresponding to the task process.

7. The process processing method according to claim 2, characterized in that: The task metadata includes task key fields corresponding to each state machine node and task running data corresponding to the task key fields, which are stored in a key-value pair form or a JSON form.

8. The process processing method according to claim 1, characterized in that: After creating the task process based on the process general metadata, the task state machine and the task metadata, the method further includes: In response to a modification trigger operation input for the task process, displaying the process general metadata corresponding to the task process; In response to an edit trigger operation input for the process common metadata, the task process is updated, wherein the edit trigger operation includes at least one of a metadata adding trigger operation, a metadata deleting trigger operation, and a metadata modifying trigger operation.

9. The process processing method according to claim 1, characterized in that: After creating the task process based on the process general metadata, the task state machine and the task metadata, the method further includes: In response to a modification trigger operation inputted in a task operation interface for modifying task data, the task data in the task operation interface is updated, and the task flow is updated based on the updated task data.

10. The process processing method according to claim 1, characterized in that: The process general metadata at least includes a process record identification field of the task process; After creating the task process based on the process general metadata, the task state machine and the task metadata, the method further includes: In response to a data query trigger operation, acquiring a process record related to the task process based on the process identifier in the process record identifier field; The target query data corresponding to the data query trigger operation is determined based on the process record, and the target query data is displayed.

11. A process processing device, characterized in that: include: A creation trigger module, configured to determine, in response to a creation trigger operation, a task type corresponding to a task flow to be created, and obtain general flow metadata corresponding to the task type; A data acquisition module, used for acquiring a pre-established task state machine corresponding to the task flow and task metadata corresponding to the task flow, wherein the task state machine includes at least one state machine node and a switching action corresponding to the state machine node, and the state machine node is associated with a task node in the task flow; The process creation module is used to create the task process based on the process common metadata, the task state machine and the task metadata.

12. An electronic device, characterized in that: The electronic device comprises: one or more processors; a storage device for storing one or more programs, When the one or more programs are executed by the one or more processors, the one or more processors implement the process processing method as described in any one of claims 1-10.

13. A storage medium containing computer executable instructions, characterized in that: The computer executable instructions are used to execute the process processing method as described in any one of claims 1-10 when executed by a computer processor.

14. A computer program product, characterized in that The computer program product comprises a computer program, and when the computer program is executed by a processor, the computer program implements the process processing method according to any one of claims 1 to 10.

Images