Data processing method and device, storage medium and electronic device

By obtaining and orchestrating the functional requirements information and preset execution parameters of the target task node in the workflow system, the problems of poor reusability and low flexibility of the data processing method of the automation node are solved, and efficient and rapid automated execution logic adjustment is achieved.

CN119556915APending Publication Date: 2025-03-04GUANGZHOU BOGUAN TELECOMM TECH LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411563586.2
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-11-04
Publication Date
2025-03-04

AI Technical Summary

Technical Problem

In the prior art, the data processing method of automated nodes in the workflow system has problems such as poor reusability and low flexibility.

Method used

By obtaining the functional requirements information of the target task node and preset execution parameters, the target action unit is determined, and orchestrated it, an action unit flow is created, and finally the action unit flow is executed based on the preset execution parameters to realize automated tasks.

Benefits of technology

In different scenarios, the automation execution logic is adjusted efficiently, quickly and on demand, improving the reusability and flexibility of automation nodes.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119556915A_ABST
    Figure CN119556915A_ABST
Patent Text Reader

Abstract

The invention discloses a data processing method and device, a storage medium and an electronic device. The method comprises the steps of obtaining function demand information and preset execution parameters of a target task node; determining a target action unit based on the function demand information; arranging the target action unit, and creating an action unit flow corresponding to the target task node; and executing the action unit flow based on a preset execution parameter to obtain an instance execution result. The technical problems of poor reusability and low flexibility of a data processing method provided in related technologies are solved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

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

[0002] The core of the workflow system, as a key tool for organizing and managing complex business processes, is to accurately describe and control the dependencies and execution order between tasks through a directed graph model composed of multiple task nodes and directed edges, thereby realizing process automation and data processing, and improving work efficiency and quality. In the workflow system, task nodes are divided into manual nodes and automated nodes. Manual nodes such as "approval" and "confirmation" require users to manually trigger execution; automated nodes do not require manual operation, and can automatically execute their logic for data processing through preset programs or scripts. The existing technology generally uses container images as execution carriers to realize automated nodes. However, the data processing methods provided in the related art have the problems of poor reusability and low flexibility.

[0003] To address the above-mentioned problems, no effective solution has been proposed yet. Summary of the invention

[0004] At least some embodiments of the present application provide a data processing method, device, storage medium and electronic device to at least solve the technical problems of poor reusability and low flexibility of the data processing methods provided in the related art.

[0005] According to one embodiment of the present application, a data processing method is provided, including: obtaining functional requirement information and preset execution parameters of a target task node, wherein the functional requirement information is used to determine the function to be deployed corresponding to the target task node, and the preset execution parameters are used to represent the instance execution parameters of the function to be deployed; determining a target action unit based on the functional requirement information, wherein the target action unit includes: a first action unit and a second action unit, the first action unit is used to represent a built-in action unit associated with the function to be deployed, and the second action unit is used to represent a mirror action unit associated with the function to be deployed; orchestrating the target action unit to create an action unit flow corresponding to the target task node, wherein the action unit flow is used to represent a process execution template corresponding to the function to be deployed; executing the action unit flow based on the preset execution parameters to obtain an instance execution result, wherein the instance execution result is used to perform functional verification on the action unit flow.

[0006] According to one embodiment of the present application, a data processing device is also provided, including: an acquisition module, used to acquire functional requirement information and preset execution parameters of a target task node, wherein the functional requirement information is used to determine the function to be deployed corresponding to the target task node, and the preset execution parameters are used to represent the instance execution parameters of the function to be deployed; a determination module, used to determine the target action unit based on the functional requirement information, wherein the target action unit includes: a first action unit and a second action unit, the first action unit is used to represent the built-in action unit associated with the function to be deployed, and the second action unit is used to represent the mirror action unit associated with the function to be deployed; a creation module, used to orchestrate the target action unit and create an action unit flow corresponding to the target task node, wherein the action unit flow is used to represent the process execution template corresponding to the function to be deployed; an execution module, used to execute the action unit flow based on the preset execution parameters to obtain the instance execution result, wherein the instance execution result is used to perform functional verification on the action unit flow.

[0007] According to one embodiment of the present application, a computer-readable storage medium is further provided, in which a computer program is stored, wherein the computer program is configured to execute the above-mentioned data processing method in each embodiment of the present application when running.

[0008] According to one embodiment of the present application, an electronic device is also provided, including a memory and a processor, wherein a computer program is stored in the memory, and the processor is configured to run the computer program to execute the above-mentioned data processing method in each embodiment of the present application.

[0009] According to another aspect of the embodiments of the present application, a computer program product is also provided, including a computer program, and when the computer program is executed by a processor, the above-mentioned data processing method in each embodiment of the present application is implemented.

[0010] According to another aspect of an embodiment of the present application, a computer program product is also provided, including a non-volatile computer-readable storage medium, wherein the non-volatile computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the above-mentioned data processing method in each embodiment of the present application is implemented.

[0011] According to another aspect of the embodiments of the present application, a computer program is also provided. When the computer program is executed by a processor, the above-mentioned data processing method in each embodiment of the present application is implemented.

[0012] In at least some embodiments of the present application, by obtaining the functional requirement information and preset execution parameters of the target task node, and determining the target action unit based on the functional requirement information, the target action unit is then orchestrated and processed, and an action unit flow corresponding to the target task node is created. Finally, the action unit flow is executed based on the preset execution parameters to obtain an instance execution result, thereby achieving the purpose of efficiently, quickly and on-demand adjustment of the automation execution logic in different scenarios, thereby achieving the technical effect of improving the reusability and flexibility of the automation nodes, and thus solving the technical problems of poor reusability and low flexibility of the data processing methods provided in the relevant technologies. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0014] Figure 1 It is a hardware structure block diagram of a mobile terminal of a data processing method according to an embodiment of the present application;

[0015] Figure 2 is a flow chart of a data processing method according to one embodiment of the present application;

[0016] Figure 3 is a schematic diagram of a workflow system according to one embodiment of the present application;

[0017] Figure 4 is a schematic diagram of a data processing method according to one embodiment of the present application;

[0018] Figure 5 is a schematic diagram of a data processing method according to one embodiment of the present application;

[0019] Figure 6 is a structural block diagram of a data processing device according to one optional embodiment of the present application;

[0020] Figure 7 is a schematic diagram of an electronic device according to an embodiment of the present application. DETAILED DESCRIPTION

[0021] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present application.

[0022] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0023] The prior art uniformly encapsulates the execution logic of the automation nodes in the workflow system into the container image. Specifically, the execution logic of each automation node is packaged into the container image. When the workflow is executed to the node, the image is scheduled and executed through the container orchestration framework to realize the automation task of the node and perform data processing. However, the data processing method provided in the related art has the following three problems: First, the lack of logic reuse results in repeated coding even in the face of similar requirements, such as delay or fixed interface calls, resulting in low development efficiency; second, the flexibility is limited. When the automation process needs to be fine-tuned, such as adjusting or removing the action sequence, the image needs to be rebuilt. At the same time, when facing a variety of similar scenarios, multiple versions of the same logic increase the management complexity; finally, the startup of the container image involves time-consuming steps such as scheduling and downloading. Especially in the first execution or in a poor network environment, the originally lightweight task may be delayed due to the image download, thereby reducing the efficiency of automated execution.

[0024] The above method embodiments involved in the present disclosure can be executed in a mobile terminal, a computer terminal or a similar computing device. Taking running on a mobile terminal as an example, the mobile terminal can be a smart phone, a tablet computer, a handheld computer, a mobile Internet device, a PAD, a game console and other terminal devices. Figure 1 1 is a hardware structure block diagram of a mobile terminal of a data processing method according to an embodiment of the present application. Figure 1 As shown, the mobile terminal may include one or more ( Figure 1 Only one is shown in the figure) a processor 102 (the processor 102 may include but is not limited to a central processing unit (CPU), a graphics processing unit (GPU), a digital signal processing (DSP) chip, a microprocessor (MCU), a field-programmable logic device (FPGA), a neural network processor (NPU), a tensor processing unit (TPU), an artificial intelligence (AI) type processor, etc.) and a memory 104 for storing data. In one embodiment of the present application, it may also include: an input and output device 108 and a display device 110.

[0025] In some optional embodiments, the above-mentioned device can also provide a human-computer interaction interface with a touch-sensitive surface, which can sense finger contact and / or gestures to perform human-computer interaction with a graphical user interface (GUI). The human-computer interaction function may include the following interactions: creating web pages, drawing, word processing, making electronic documents, games, video conferencing, instant messaging, sending and receiving emails, call interface, playing digital videos, playing digital music and / or web browsing, etc. The executable instructions for executing the above-mentioned human-computer interaction functions are configured / stored in a computer program product executable by one or more processors or a readable storage medium.

[0026] Those skilled in the art will understand that Figure 1 The structure shown is only for illustration and does not limit the structure of the mobile terminal. Figure 1 More or fewer components as shown, or with Figure 1 Different configurations shown.

[0027] According to one embodiment of the present application, an embodiment of a data processing method is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0028] Figure 2 is a flow chart of a data processing method according to one embodiment of the present application, such as Figure 2 As shown, the method comprises the following steps:

[0029] Step S21, obtaining function requirement information and preset execution parameters of the target task node, wherein the function requirement information is used to determine the to-be-deployed function corresponding to the target task node, and the preset execution parameters are used to represent instance execution parameters of the to-be-deployed function;

[0030] Step S22, determining a target action unit based on the function requirement information, wherein the target action unit includes: a first action unit and a second action unit, the first action unit is used to represent a built-in action unit associated with the function to be deployed, and the second action unit is used to represent a mirror action unit associated with the function to be deployed;

[0031] Step S23, orchestrating the target action unit to create an action unit flow corresponding to the target task node, wherein the action unit flow is used to represent a process execution template corresponding to the function to be deployed;

[0032] Step S24, executing the action unit flow based on the preset execution parameters to obtain an instance execution result, wherein the instance execution result is used to perform functional verification on the action unit flow.

[0033] The target task node mentioned above refers to a specific node that needs to be automatically executed in the workflow system. The target task node carries specific business logic functions, such as notification sending, status update, etc. During the execution of the workflow, when the target task node is reached, the corresponding task will be automatically executed according to the pre-set automation logic without manual intervention, thereby improving the execution efficiency and automation level of the process.

[0034] The above-mentioned functional requirement information refers to the automation functions that need to be implemented at a specific node in the workflow system, including but not limited to the office automation (OA) system notification function and the email notification function. Specifically, when the workflow is executed to a specific node, the workflow system can automatically identify and execute the automation tasks associated with the node, such as automatically sending message notifications within the OA system and automatically sending email notifications to relevant recipients.

[0035] The above preset execution parameters refer to a set of parameters pre-defined when designing a workflow node, which are used to describe the general requirements and framework of the node's automated execution logic. The preset execution parameters include but are not limited to employee ID, task data, system configuration information, etc., as well as possible output formats.

[0036] The above instance execution parameters refer to the actual input parameters for each automation node when the workflow instance is running. The instance execution parameters are dynamically generated according to the current process status and business needs when the workflow is executed to a specific node, and are used to guide the action unit on the node on how to perform its automation task. The dynamic generation of instance execution parameters ensures that the node can perform precise automation operations according to the personalized needs of each instance.

[0037] The first action unit mentioned above is the built-in action unit, which is a series of automated execution units pre-implemented in the workflow system, and is used to quickly execute common and simple task commands, such as delayed waiting, sending OA notifications, etc. The execution of the built-in action unit is completely carried out in the memory space of the workflow system, and there is no need to start additional containers or call external services. Therefore, the response speed is extremely fast, which can effectively improve the execution efficiency of the workflow.

[0038] The second action unit, the image action unit, is an automated execution unit that is packaged through container image technology and implemented based on the container orchestration system. Image action units are usually used to perform more complex, resource-intensive or time-consuming tasks, such as big data processing, machine learning model prediction, time-consuming system calls, etc. Since the above tasks may require a special operating environment or a large amount of computing resources, the use of container images can ensure that the tasks are executed in the correct environment and can be flexibly scheduled to a system with sufficient resources.

[0039] The above-mentioned orchestration process refers to the process of organizing and arranging a series of action units in a workflow system to create a model that can automatically execute a specific task process. The orchestration process includes but is not limited to a linear model or a directed acyclic graph (DAG) model. The linear model is simple and intuitive, and the action units are executed in sequence. It is suitable for node automation with simple logic and no parallel processing. The DAG model is more complex and allows parallel and branch execution. It is suitable for the automated execution of workflow nodes with complex logic and multiple execution paths.

[0040] The above-mentioned action unit flow refers to an ordered set of action units used to specifically describe and execute the automation function of a workflow node in the workflow system. The action units in the action unit flow are connected to each other through input and output parameters. The output result of the previous action unit is used as the input parameter of the next action unit, allowing the workflow system to execute a series of tasks in a predetermined order, thereby realizing the automation of the node and ensuring the consistency of the execution process and the accuracy of data transmission.

[0041] The above process execution template refers to a templated structure used to describe and guide the execution process of a specific workflow instance in a workflow system. A workflow system can be regarded as a process execution template, which specifies in detail a series of steps and task nodes required to complete a specific business process, as well as the execution order and dependencies between these nodes.

[0042] Figure 3 is a schematic diagram of a workflow system according to one embodiment of the present application, such as Figure 3 The workflow system shown includes 6 nodes, among which the action unit flow of node 3 includes, first, making a request operation based on the built-in action unit, then waiting for 10 seconds, and then synchronizing the data to the system based on the mirror action unit, and finally re-making a request operation based on the built-in action unit; the action unit flow of node 6 includes, first, sending an email based on the mirror action unit, and then waiting for 10 seconds based on the built-in action unit.

[0043] Figure 4 is a schematic diagram of a data processing method according to one embodiment of the present application, such as Figure 4 As shown, the "Notify Associated Persons" node action unit flow is displayed.

[0044] For example, taking the leave workflow as an example, first of all, it is necessary to fill in the leave information, and then enter the team leader approval node, and the target task node is "notify associated personnel". The functional requirement information of the "notify associated personnel" node is that after receiving the leave application, the notification is automatically sent to the associated colleagues, human resources and department heads, while ensuring the accuracy and timeliness of the notification. The preset execution parameters include the specific information of the leave application, such as the applicant, leave type, leave duration, etc., and the contact information of the associated personnel who receive the notification. Based on the functional requirement information, it is determined that the target action unit includes a built-in action unit for sending OA notifications to associated colleagues and human resources, and a mirror action unit for sending email notifications of detailed leave information to the department head. Subsequently, based on the built-in action unit and the mirror action unit, the orchestration processing is performed, and the action unit flow corresponding to the "notify associated personnel" node is created based on the linear model. When an employee's leave application is submitted to the "notify associated personnel" node, the action unit flow is automatically started, first sending OA notifications to associated colleagues and human resources through the built-in built-in action unit, and then sending emails to the department head based on the mirror action unit.

[0045] For example, when employee A submits a leave application, the automated processing flow of the "Notify Associated Personnel" node is triggered. The task of this node is to send notifications to employee A's associated colleague A, associated human resources colleague B, and supervisor colleague C to ensure that they are aware of employee A's leave application in a timely manner and can make corresponding approvals or processes. In this process, first obtain the leave application information submitted by employee A, including details such as leave type and leave duration, as well as the associated personnel information receiving the notification. Subsequently, according to the functional requirements of the "Notify Associated Personnel" node, that is, automatically send OA notifications to associated colleagues and human resources, and send detailed email notifications to department heads, determine the target action unit to send OA notifications to colleagues A and B based on the built-in action unit, and send email notifications containing detailed leave information to department head colleague C based on the mirror action unit. After determining the target action unit, the above-mentioned built-in action unit and mirror action unit are arranged and processed according to the linear model to create the action unit flow of the "Notify Associated Personnel" node to ensure that the execution order of the action unit conforms to the notification and approval process. When employee A's leave application reaches the "Notify Associated Personnel" node, the action unit flow is automatically started. First, an OA notification is sent to colleagues A and B through the built-in action unit. Then, based on the mirror action unit, an email notification with detailed leave information is sent to the department head, colleague C.

[0046] Based on the above steps S21 to S24, by obtaining the functional requirement information and preset execution parameters of the target task node, and determining the target action unit based on the functional requirement information, the target action unit is orchestrated and processed, and an action unit flow corresponding to the target task node is created. Finally, the action unit flow is executed based on the preset execution parameters to obtain the instance execution result, thereby achieving the purpose of efficiently, quickly and on-demand adjustment of the automation execution logic in different scenarios, thereby achieving the technical effect of improving the reusability and flexibility of the automation nodes, and thus solving the technical problems of poor reusability and low flexibility of the data processing methods provided in the relevant technologies.

[0047] The data processing method in the embodiment of the present application is further introduced below.

[0048] Optionally, in step S22, determining the target action unit based on the functional requirement information includes:

[0049] Step S221, parsing the function requirement information to obtain a function parsing result, wherein the function parsing result is used to determine at least one sub-function included in the function to be deployed;

[0050] Step S222, determining the target action unit based on the function analysis result.

[0051] Exemplarily, taking the functional requirement information of the "Notify associated personnel" node as an example, analysis is performed and the functional analysis result is to send OA notifications and email notifications. The target action units corresponding to sending OA notifications and email notifications are the first action unit and the second action unit, namely the built-in action unit and the mirror action unit.

[0052] Based on the above optional embodiments, by parsing the functional requirement information to obtain the functional analysis result, and determining the target action unit based on the functional analysis result, different action units can be dynamically selected and combined according to different business scenario requirements, and the execution logic of the automation node can be quickly adjusted to adapt to different workflow orchestration requirements.

[0053] Optionally, in step S222, determining the target action unit based on the function analysis result includes:

[0054] Step S2221, querying the current workflow system based on the function analysis result to obtain a query result, wherein the current workflow system includes multiple candidate action units, and the execution frequency of the candidate action units is higher than a preset threshold;

[0055] Step S2222: in response to the presence of candidate action units matching the sub-function in the query results, determine built-in action units based on the candidate action units.

[0056] Exemplarily, taking the "Notify Associated Personnel" node as an example, first perform functional analysis on the "Notify Associated Personnel" node, and obtain the result of its functional analysis as OA notification. Subsequently, query the current workflow system, search for candidate action units with an execution frequency higher than the preset threshold, and identify whether there are existing units that can meet the functional requirements of the node. The query results show that there is a candidate action unit called "Enterprise OA Notification" in the system, and its execution frequency is 350 times / week, which is much higher than the preset threshold of 200 times / week. It can be judged that the candidate action unit of "Enterprise OA Notification" matches the OA notification at this time, and the candidate action unit of "Enterprise OA Notification" is determined as a built-in action unit.

[0057] Based on the above optional embodiment, the current workflow system is queried based on the function analysis result to obtain the query result, and in response to the existence of candidate action units matching the sub-function in the query result, the built-in action unit is determined based on the candidate action unit, thereby avoiding redundant development work and improving the efficiency of automation execution and the reusability of automation nodes.

[0058] Optionally, in step S2222, determining the target action unit based on the function parsing result includes: in response to the absence of a candidate action unit matching the sub-function in the query result, acquiring an image action unit corresponding to the sub-function from a preset image repository.

[0059] For example, taking the "Notify Associated Personnel" node as an example, the "Notify Associated Personnel" node is first functionally parsed, and its functional parsing result is obtained as email notification. Subsequently, the current workflow system is queried to search for candidate action units with an execution frequency higher than a preset threshold, and to identify whether there are existing units that can meet the functional requirements of the node. The query results show that there are no candidate action units matching the email notification in the system, and it is necessary to obtain the mirror action unit corresponding to the sub-function from the preset mirror repository.

[0060] Based on the above optional embodiment, when there is no candidate action unit matching the sub-function in the query result, obtaining the mirror action unit corresponding to the sub-function from the preset mirror repository can reduce development costs and time consumption, while improving the flexibility of using automation nodes.

[0061] Optionally, the data processing method in the embodiment of the present disclosure also includes: using a preset programming language to write an image action unit corresponding to the sub-function; packaging the image action unit to obtain a packaging result, wherein the packaging result is used to represent the container image corresponding to the image action unit; and uploading the packaging result to a preset image repository.

[0062] The above-mentioned preset programming languages ​​include but are not limited to Python, Java, Go, Shell and other programming languages.

[0063] Specifically, according to the specific requirements and scenarios of the sub-function, a suitable programming language is selected to write the corresponding image action unit of the sub-function, and the written image action unit is packaged to generate a container image corresponding to the image action unit, and uploaded to the preset image repository.

[0064] For example, the "Notify Associated Personnel" node in the leave workflow needs to implement automated OA notification and email notification, and the existing workflow system only provides built-in action units for OA notification, so a separate mirror action unit for email notification needs to be developed. First, use the Python programming language to write the corresponding mirror action unit for email notification; second, use Docker or other container technologies to package the written program and generate a container image; finally, upload the packaged result to the preset image repository, such as Docker Hub, private repository, etc., for the workflow system to call and execute when needed.

[0065] Based on the above optional embodiments, the mirror action units corresponding to the sub-functions are written in a preset programming language, and the mirror action units are packaged and processed, and finally the packaged results are uploaded to the preset mirror warehouse. This can simplify the deployment and management of automation nodes, while improving the portability of the code and the isolation of the environment, thereby improving the flexibility of the execution of automation nodes.

[0066] Optionally, the data processing method in the embodiment of the present disclosure further includes: performing registration processing on the mirror action unit to obtain a registration result, wherein the registration result is used to indicate that the mirror action unit is in an available state; and binding the mirror action unit to the action unit stream based on the registration result.

[0067] For example, to enable the use of the mirror action unit for sending emails in the workflow system, the written mirror action unit needs to be registered in the workflow system, indicating that the mirror action unit is available and can be bound to the action unit flow of the node for use.

[0068] For example, in the workflow system, there is a mirror action unit written in Python for email notification. In order to enable this mirror action unit to be recognized and used in the workflow system, first, in the mirror registration module of the workflow management platform, a mirror action unit registration request for the email notification function is submitted. The above request contains the basic information of the mirror action unit, such as name, version, function description, input parameter type and output result format. After verifying the integrity, security and interface compatibility of the mirror action unit with the workflow system, the workflow system generates a mirror action unit named "MailNotifier", and the mirror action unit is already in an available state. It is added to the action unit flow so that it can be called by the workflow node.

[0069] Based on the above optional embodiment, the mirror action unit is registered to obtain a registration result, and the mirror action unit is bound to the action unit flow based on the registration result. The mirror action unit can be flexibly added, replaced or moved in the workflow, thereby making the design and adjustment of the workflow system simpler and able to quickly adapt to changes in business needs.

[0070] Optionally, in step S23, the target action unit is orchestrated to create an action unit flow corresponding to the target task node, including:

[0071] Step S231, obtaining a preset arrangement sequence, wherein the preset arrangement sequence is used to determine the execution sequence of the built-in action unit and the mirror action unit;

[0072] Step S232: Arrange the target action unit based on a preset arrangement order to obtain an action unit stream.

[0073] For example, taking the leave approval workflow as an example, the preset scheduling order is: first, the action unit built into the workflow locally is to send OA notifications to related colleagues and related human resources; secondly, an email notification is sent to the department head, so that the target action unit is scheduled and processed based on the preset scheduling order, and an action unit flow that first performs OA notification and then email notification is obtained.

[0074] Based on the above optional embodiments, a preset orchestration order is obtained, and the target action unit is orchestrated based on the preset orchestration order to obtain an action unit flow, thereby ensuring that the workflow system executes the action unit according to the established strategy, avoiding uncertainty and confusion in the execution process, and at the same time, the execution order of the action unit can be easily adjusted to quickly respond to changes in business logic without modifying the underlying code, thereby reducing the complexity and cost of workflow system reconstruction.

[0075] Optionally, in step S24, the action unit flow is executed based on the preset execution parameters, and the example execution result obtained includes:

[0076] Step S241, filling the action unit flow with preset execution parameters to obtain a parameter filling result, wherein the parameter filling result is used to determine the execution object associated with the target action unit;

[0077] Step S242, executing the action unit flow based on the parameter filling result to obtain the instance execution result.

[0078] For example, assume that in the "Notify Associated Personnel" node of the leave workflow, the preset execution parameters include associated colleague A, associated human resources colleague B, and associated department head colleague C, so that the action unit flow is filled and processed based on the preset execution parameters to implement the function of sending an OA notification to colleague A based on the built-in action unit, then sending an OA notification to human resources colleague B, and finally sending an email to department head colleague C based on the mirror action unit.

[0079] Based on the above optional embodiments, the action unit flow is filled with preset execution parameters to obtain parameter filling results, and the action unit flow is executed based on the parameter filling results to obtain instance execution results, so that the workflow system can adapt to various business scenarios without redesigning the action unit flow for each scenario, thereby reducing the complexity of workflow design and maintenance.

[0080] Optionally, in step S242, executing the action unit flow based on the parameter filling result includes: in response to a current action unit in the action unit flow being a built-in action unit, executing a built-in execution function corresponding to the built-in action unit in the local environment based on the parameter filling result.

[0081] The above-mentioned built-in execution functions refer to functions or methods that are pre-defined and implemented within the workflow system and are used to perform specific automated tasks. Common, frequently used business logic or data processing operations are usually optimized and directly embedded into the workflow system as built-in execution functions. When the workflow executes to a built-in action unit containing a built-in execution function, the system will immediately call these functions without the need for additional container image scheduling or external service calls, thereby achieving fast response and efficient execution.

[0082] Exemplarily, in the action unit flow of the "Course Release Review Feedback" node, two built-in action units are included: "Send Review Result Notification" and "Update Course Status". When the course review event triggers the "Course Release Review Feedback" node, the workflow system starts to execute the built-in execution function corresponding to the built-in action unit. In order to make full use of the lightweight concurrency characteristics of coroutines, the workflow system schedules and executes the above built-in action units within a single thread. The built-in execution function uses Python's asyncio library to implement the "Send Review Result Notification" startup, allowing it to switch to other tasks or continue processing the next built-in action unit while waiting for the notification sending service to respond without blocking the entire thread.

[0083] Based on the above optional embodiments, when the current action unit in the action unit stream is a built-in action unit, the built-in execution function corresponding to the built-in action unit is executed in the local environment based on the parameter filling result, which not only reduces the waiting time, but also avoids the resource overhead brought by the use of additional threads, so that the system can maintain high concurrent processing capabilities under limited resources.

[0084] Optionally, in step S242, executing the action unit flow based on the parameter filling result includes: in response to a current action unit in the action unit flow being a mirrored action unit, scheduling execution of the mirrored action unit based on the parameter filling result and the container orchestration framework.

[0085] For example, when an employee submits a leave application and enters the "Notify Associated Personnel" node, the workflow system fills in the results based on the parameters, that is, the execution parameters of the current workflow instance, such as "Associated Colleagues", "Associated Human Resources", and "Associated Department Head". Among them, the "Associated Department Head" parameter is specified as Colleague C, which triggers the execution of the mirror action unit "Cc Email to Department Head". After the workflow system recognizes that the current action unit is a mirror action unit, it will schedule and execute this mirror action unit based on the container orchestration framework, such as Kubernetes.

[0086] Based on the above optional embodiments, when the current action unit in the action unit flow is a mirror action unit, the mirror action unit is scheduled for execution based on the parameter filling result and the container orchestration framework. When a mirror action unit needs to be updated or maintained, only the corresponding container image needs to be replaced or updated without affecting the execution of other nodes in the workflow, thereby reducing maintenance costs and improving the maintainability of the system.

[0087] Figure 5 is a schematic diagram of a data processing method according to one embodiment of the present application, such as Figure 5 As shown, the actual execution status of the "Notify Associated Personnel" node is displayed. The execution parameters corresponding to "Notify Associated Personnel" include: Associated Colleague A, Associated Human Resources Colleague B, and Associated Department Head Colleague C. In the process of performing the "Notify Associated Personnel" node, the OA notification based on the built-in action unit is first executed in the workflow local environment, and the OA notification is sent to the associated colleague A, and then the OA notification is sent to the associated human resources colleague B. Finally, in the container mirror environment, an email is sent to the department head colleague C based on the mirror action unit, thereby completing the execution of the entire node action unit flow. High-frequency functions are realized by executing built-in action units in the workflow local environment, and new functions are realized by executing mirror action units in the container mirror environment, thereby solving the technical problems of poor reusability and low flexibility of the data processing methods provided in the relevant technologies.

[0088] Through the description of the above implementation methods, those skilled in the art can clearly understand that the method according to the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes a number of instructions for a terminal device (which can be a mobile phone, computer, server, or network device, etc.) to execute the methods of each embodiment of the present application.

[0089] In the present embodiment, a data processing device is also provided, which is used to implement the above-mentioned embodiments and preferred implementation modes, and the descriptions that have been made will not be repeated. As used below, the term "module" can implement a combination of software and / or hardware of a predetermined function. Although the devices described in the following embodiments are preferably implemented in software, the implementation of hardware, or a combination of software and hardware, is also possible and conceived.

[0090] Figure 6 is a structural block diagram of a data processing device according to one embodiment of the present application, such as Figure 6 As shown, the device comprises:

[0091] The acquisition module 601 is used to acquire the function requirement information and preset execution parameters of the target task node, wherein the function requirement information is used to determine the to-be-deployed function corresponding to the target task node, and the preset execution parameters are used to represent the instance execution parameters of the to-be-deployed function;

[0092] A determination module 602 is used to determine a target action unit based on the function requirement information, wherein the target action unit includes: a first action unit and a second action unit, the first action unit is used to represent a built-in action unit associated with the function to be deployed, and the second action unit is used to represent a mirror action unit associated with the function to be deployed;

[0093] A creation module 603 is used to perform orchestration processing on the target action unit and create an action unit flow corresponding to the target task node, wherein the action unit flow is used to represent a process execution template corresponding to the function to be deployed;

[0094] The execution module 604 is used to execute the action unit flow based on preset execution parameters to obtain an instance execution result, wherein the instance execution result is used to perform functional verification on the action unit flow.

[0095] Optionally, the determination module 602 is further used to: parse the function requirement information to obtain a function analysis result, wherein the function analysis result is used to determine at least one sub-function included in the function to be deployed; and determine the target action unit based on the function analysis result.

[0096] Optionally, the determination module 602 is also used to: perform query processing on the current workflow system based on the function analysis result to obtain a query result, wherein the current workflow system includes multiple candidate action units, and the execution frequency of the candidate action units is higher than a preset threshold; in response to the presence of a candidate action unit matching the sub-function in the query result, determine the built-in action unit based on the candidate action unit.

[0097] Optionally, the determination module 602 is further configured to: in response to the absence of a candidate action unit matching the sub-function in the query result, acquire an image action unit corresponding to the sub-function from a preset image repository.

[0098] Optionally, the data processing device also includes: a writing module 605, which is used to write the image action unit corresponding to the sub-function using a preset programming language; a packaging module 606, which is used to package the image action unit to obtain a packaging result, wherein the packaging result is used to represent the container image corresponding to the image action unit; an uploading module 607, which is used to upload the packaging result to a preset image repository.

[0099] Optionally, the data processing device further includes: a registration module 606, used to register the mirror action unit to obtain a registration result, wherein the registration result is used to indicate that the mirror action unit is in an available state; and a binding module 609, used to bind the mirror action unit to the action unit stream based on the registration result.

[0100] Optionally, the creation module 603 is further used to: obtain a preset arrangement order, wherein the preset arrangement order is used to determine the execution order of the built-in action unit and the mirror action unit; and perform arrangement processing on the target action unit based on the preset arrangement order to obtain an action unit stream.

[0101] Optionally, the execution module 604 is also used to: fill the action unit flow with preset execution parameters to obtain a parameter filling result, wherein the parameter filling result is used to determine the execution object associated with the target action unit; execute the action unit flow based on the parameter filling result to obtain an instance execution result.

[0102] Optionally, the execution module 604 is further configured to: in response to the current action unit in the action unit stream being a built-in action unit, execute a built-in execution function corresponding to the built-in action unit in the local environment based on the parameter filling result.

[0103] Optionally, the execution module 604 is further configured to: in response to the current action unit in the action unit stream being a mirror action unit, schedule execution of the mirror action unit based on the parameter filling result and the container orchestration framework.

[0104] It should be noted that the above modules can be implemented by software or hardware. For the latter, it can be implemented in the following ways, but not limited to: the above modules are all located in the same processor; or the above modules are located in different processors in any combination.

[0105] An embodiment of the present application further provides a computer-readable storage medium, in which a computer program is stored, wherein the computer program is configured to execute the steps of any of the above method embodiments when running.

[0106] Optionally, in this embodiment, the above-mentioned computer-readable storage medium may include but is not limited to: a USB flash drive, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk or an optical disk, and other media that can store computer programs.

[0107] Optionally, in this embodiment, the computer-readable storage medium may be located in any one of the computer terminals in a computer terminal group in a computer network, or in any one of the mobile terminals in a mobile terminal group.

[0108] Optionally, in this embodiment, the computer-readable storage medium may be configured to store a computer program for performing the following steps:

[0109] S1, obtaining function requirement information and preset execution parameters of a target task node, wherein the function requirement information is used to determine the function to be deployed corresponding to the target task node, and the preset execution parameters are used to represent instance execution parameters of the function to be deployed;

[0110] S2, determining a target action unit based on the function requirement information, wherein the target action unit includes: a first action unit and a second action unit, the first action unit is used to represent a built-in action unit associated with the function to be deployed, and the second action unit is used to represent a mirror action unit associated with the function to be deployed;

[0111] S3, orchestrate the target action unit and create an action unit flow corresponding to the target task node, wherein the action unit flow is used to represent the process execution template corresponding to the function to be deployed;

[0112] S4, executing the action unit flow based on the preset execution parameters to obtain an instance execution result, wherein the instance execution result is used to perform functional verification on the action unit flow.

[0113] Optionally, the above-mentioned computer-readable storage medium is also configured to store program code for executing the following steps: parsing the functional requirement information to obtain a functional analysis result, wherein the functional analysis result is used to determine at least one sub-function included in the function to be deployed; and determining the target action unit based on the functional analysis result.

[0114] Optionally, the computer-readable storage medium is also configured to store program code for executing the following steps: querying the current workflow system based on the function analysis results to obtain query results, wherein the current workflow system includes multiple candidate action units, and the execution frequency of the candidate action units is higher than a preset threshold; in response to the presence of a candidate action unit matching the sub-function in the query results, determining a built-in action unit based on the candidate action unit.

[0115] Optionally, the computer-readable storage medium is further configured to store program code for executing the following steps: in response to the absence of a candidate action unit matching the sub-function in the query result, obtaining an image action unit corresponding to the sub-function from a preset image repository.

[0116] Optionally, the computer-readable storage medium is further configured to store program codes for executing the following steps: writing an image action unit corresponding to a sub-function using a preset programming language; packaging the image action unit to obtain a packaging result, wherein the packaging result is used to represent the container image corresponding to the image action unit; and uploading the packaging result to a preset image repository.

[0117] Optionally, the computer-readable storage medium is further configured to store program codes for executing the following steps: registering the mirror action unit to obtain a registration result, wherein the registration result is used to indicate that the mirror action unit is in an available state; and binding the mirror action unit to the action unit stream based on the registration result.

[0118] Optionally, the above-mentioned computer-readable storage medium is also configured to store program code for executing the following steps: obtaining a preset arrangement order, wherein the preset arrangement order is used to determine the execution order of the built-in action unit and the mirror action unit; and arranging the target action unit based on the preset arrangement order to obtain an action unit stream.

[0119] Optionally, the above-mentioned computer-readable storage medium is also configured to store program code for executing the following steps: filling the action unit flow with preset execution parameters to obtain a parameter filling result, wherein the parameter filling result is used to determine the execution object associated with the target action unit; executing the action unit flow based on the parameter filling result to obtain an instance execution result.

[0120] Optionally, the computer-readable storage medium is further configured to store program code for executing the following steps: in response to the current action unit in the action unit stream being a built-in action unit, executing a built-in execution function corresponding to the built-in action unit in a local environment based on a parameter filling result.

[0121] Optionally, the computer-readable storage medium is further configured to store program code for executing the following steps: in response to a current action unit in the action unit stream being a mirrored action unit, scheduling execution of the mirrored action unit based on a parameter filling result and a container orchestration framework.

[0122] In the computer-readable storage medium of this embodiment, by obtaining the functional requirement information and preset execution parameters of the target task node, and determining the target action unit based on the functional requirement information, the target action unit is orchestrated and processed, and an action unit flow corresponding to the target task node is created. The action unit flow is executed based on the preset execution parameters to obtain an instance execution result, thereby achieving the purpose of efficiently, quickly and on-demand adjustment of the automation execution logic in different scenarios, thereby achieving the technical effect of improving the reusability and flexibility of the automation nodes, and further solving the technical problems of poor reusability and low flexibility of the data processing methods provided in the relevant technologies.

[0123] Through the description of the above implementation methods, it is easy for those skilled in the art to understand that the example implementation methods described here can be implemented by software or by combining software with necessary hardware. Therefore, the technical solution according to the implementation methods of the present application can be embodied in the form of a software product, which can be stored in a computer-readable storage medium (which can be a CD-ROM, a USB flash drive, a mobile hard disk, etc.) or on a network, and includes several instructions to enable a computing device (which can be a personal computer, a server, a terminal device, or a network device, etc.) to execute the method according to the implementation methods of the present application.

[0124] In an exemplary embodiment of the present application, a program product capable of implementing the above method of the present embodiment is stored on a computer-readable storage medium. In some possible implementations, various aspects of the embodiments of the present application can also be implemented in the form of a program product, which includes a program code. When the program product is run on a terminal device, the program code is used to enable the terminal device to execute the steps of various exemplary implementations of the present application described in the above "Exemplary Method" section of the present embodiment.

[0125] According to the program product for implementing the above method in the embodiment of the present application, it can adopt a portable compact disk read-only memory (CD-ROM) and include program code, and can be run on a terminal device, such as a personal computer. However, the program product of the embodiment of the present application is not limited thereto. In the embodiment of the present application, the computer-readable storage medium can be any tangible medium containing or storing a program, which can be used by or in combination with an instruction execution system, an apparatus or a device.

[0126] The program product may be in any combination of one or more computer-readable media. 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 thereof. More specific examples (non-exhaustive) of computer-readable storage media include: an electrical connection with one or more wires, a portable 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 thereof.

[0127] It should be noted that the program code contained in the computer-readable storage medium can be transmitted using any appropriate medium, including but not limited to wireless, wired, optical cable, RF, etc., or any suitable combination of the above.

[0128] An embodiment of the present application further provides an electronic device, including a memory and a processor, wherein a computer program is stored in the memory, and the processor is configured to run the computer program to execute the steps in any one of the above method embodiments.

[0129] Optionally, the electronic device may further include a transmission device and an input / output device, wherein the transmission device is connected to the processor, and the input / output device is connected to the processor.

[0130] Optionally, in this embodiment, the processor may be configured to perform the following steps through a computer program:

[0131] S1, obtaining function requirement information and preset execution parameters of a target task node, wherein the function requirement information is used to determine the function to be deployed corresponding to the target task node, and the preset execution parameters are used to represent instance execution parameters of the function to be deployed;

[0132] S2, determining a target action unit based on the function requirement information, wherein the target action unit includes: a first action unit and a second action unit, the first action unit is used to represent a built-in action unit associated with the function to be deployed, and the second action unit is used to represent a mirror action unit associated with the function to be deployed;

[0133] S3, orchestrate the target action unit and create an action unit flow corresponding to the target task node, wherein the action unit flow is used to represent the process execution template corresponding to the function to be deployed;

[0134] S4, executing the action unit flow based on the preset execution parameters to obtain an instance execution result, wherein the instance execution result is used to perform functional verification on the action unit flow.

[0135] Optionally, the processor may also be configured to perform the following steps through a computer program: parsing the function requirement information to obtain a function analysis result, wherein the function analysis result is used to determine at least one sub-function included in the function to be deployed; and determining the target action unit based on the function analysis result.

[0136] Optionally, the processor may also be configured to perform the following steps through a computer program: query the current workflow system based on the function analysis results to obtain query results, wherein the current workflow system includes multiple candidate action units, and the execution frequency of the candidate action units is higher than a preset threshold; in response to the presence of a candidate action unit matching the sub-function in the query results, determine a built-in action unit based on the candidate action unit.

[0137] Optionally, the processor may be configured to execute the following steps through a computer program: in response to the absence of a candidate action unit matching the sub-function in the query result, obtaining a mirror action unit corresponding to the sub-function from a preset mirror repository.

[0138] Optionally, the above-mentioned processor can also be configured to perform the following steps through a computer program: write the image action unit corresponding to the sub-function using a preset program language; package the image action unit to obtain a packaging result, wherein the packaging result is used to represent the container image corresponding to the image action unit; and upload the packaging result to a preset image repository.

[0139] Optionally, the processor may also be configured to perform the following steps through a computer program: registering the mirror action unit to obtain a registration result, wherein the registration result is used to indicate that the mirror action unit is in an available state; and binding the mirror action unit to the action unit stream based on the registration result.

[0140] Optionally, the processor may also be configured to perform the following steps through a computer program: obtaining a preset choreography order, wherein the preset choreography order is used to determine the execution order of built-in action units and mirrored action units; and choreography processing the target action unit based on the preset choreography order to obtain an action unit stream.

[0141] Optionally, the above-mentioned processor can also be configured to perform the following steps through a computer program: fill the action unit flow with preset execution parameters to obtain a parameter filling result, wherein the parameter filling result is used to determine the execution object associated with the target action unit; execute the action unit flow based on the parameter filling result to obtain an instance execution result.

[0142] Optionally, the processor may also be configured to perform the following steps through a computer program: in response to a current action unit in the action unit stream being a built-in action unit, executing a built-in execution function corresponding to the built-in action unit in a local environment based on a parameter filling result.

[0143] Optionally, the processor may also be configured to execute the following steps through a computer program: in response to a current action unit in the action unit stream being a mirror action unit, scheduling execution of the mirror action unit based on a parameter filling result and a container orchestration framework.

[0144] In the electronic device of this embodiment, by obtaining the functional requirement information and preset execution parameters of the target task node, and determining the target action unit based on the functional requirement information, the target action unit is then orchestrated and processed to create an action unit flow corresponding to the target task node, and finally the action unit flow is executed based on the preset execution parameters to obtain an instance execution result, thereby achieving the purpose of efficiently, quickly and on-demand adjustment of the automation execution logic in different scenarios, thereby achieving the technical effect of improving the reusability and flexibility of the automation nodes, and thus solving the technical problems of poor reusability and low flexibility of the data processing methods provided in the relevant technologies.

[0145] Figure 7 is a schematic diagram of an electronic device according to an embodiment of the present application. Figure 7 As shown, the electronic device 700 is merely an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0146] like Figure 7 As shown, the electronic device 700 is in the form of a general computing device. The components of the electronic device 700 may include but are not limited to: at least one processor 710, at least one memory 720, a bus 730 connecting different system components (including the memory 720 and the processor 710), and a display 740.

[0147] The memory 720 stores program codes, which can be executed by the processor 710, so that the processor 710 executes the steps described in the method section of the embodiment of the present application according to various exemplary implementations of the present application.

[0148] The memory 720 may include a readable medium in the form of a volatile storage unit, such as a random access memory unit (RAM) 7201 and / or a cache memory unit 7202, and may further include a read-only memory unit (ROM) 7203, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory.

[0149] In some examples, the memory 720 may also include a program / utility 7204 having a set (at least one) of program modules 7205, such program modules 7205 including but not limited to: an operating system, one or more application programs, other program modules, and program data, each of which or some combination thereof may include the implementation of a network environment. The memory 720 may further include a memory remotely disposed relative to the processor 710, and these remote memories may be connected to the electronic device 700 via a network. Examples of the above-mentioned network include but are not limited to the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0150] Bus 730 may represent one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, a local bus of processor 710, or any of a variety of bus architectures.

[0151] The display 740 may be, for example, a touch screen liquid crystal display (LCD) that enables a user to interact with a user interface of the electronic device 700 .

[0152] Optionally, the electronic device 700 may also communicate with one or more external devices 800 (e.g., keyboards, pointing devices, Bluetooth devices, etc.), one or more devices that enable a user to interact with the electronic device 700, and / or any device that enables the electronic device 700 to communicate with one or more other computing devices (e.g., routers, modems, etc.). Such communication may be performed through an input / output (I / O) interface 750. Furthermore, the electronic device 700 may also communicate with one or more networks (e.g., a local area network (LAN), a wide area network (WAN), and / or a public network, such as the Internet) through a network adapter 760. Figure 7 As shown, the network adapter 760 communicates with other modules of the electronic device 700 via the bus 730. It should be understood that although Figure 7Not shown, other hardware and / or software modules may be used in conjunction with electronic device 700, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.

[0153] The electronic device 700 may further include: a keyboard, a cursor control device (such as a mouse), an input / output interface (I / O interface), a network interface, a power supply and / or a camera.

[0154] It can be understood by those skilled in the art that Figure 7 The structure shown is for illustration only and does not limit the structure of the above electronic device. Figure 7 More or fewer components as shown, or with Figure 1 The memory 720 may be used to store computer programs and corresponding data, such as computer programs and corresponding data corresponding to the data processing method in the embodiment of the present application. The processor 710 executes various functional applications and data processing by running the computer programs stored in the memory 720, that is, implements the above-mentioned data processing method.

[0155] The embodiment of the present application further provides a computer program product. Optionally, in this embodiment, the computer program product may include a computer program, and the computer program implements the method provided in the embodiment when executed by a processor.

[0156] Optionally, the computer program included in the above-mentioned computer program product is executed by a processor to perform the following steps:

[0157] S1, obtaining function requirement information and preset execution parameters of a target task node, wherein the function requirement information is used to determine the function to be deployed corresponding to the target task node, and the preset execution parameters are used to represent instance execution parameters of the function to be deployed;

[0158] S2, determining a target action unit based on the function requirement information, wherein the target action unit includes: a first action unit and a second action unit, the first action unit is used to represent a built-in action unit associated with the function to be deployed, and the second action unit is used to represent a mirror action unit associated with the function to be deployed;

[0159] S3, orchestrate the target action unit and create an action unit flow corresponding to the target task node, wherein the action unit flow is used to represent the process execution template corresponding to the function to be deployed;

[0160] S4, executing the action unit flow based on the preset execution parameters to obtain an instance execution result, wherein the instance execution result is used to perform functional verification on the action unit flow.

[0161] The embodiments of the present application also provide a computer program product. Optionally, the computer program product may include a non-volatile computer-readable storage medium, which may be used to store a computer program, and when the computer program is executed by a processor, the method provided in the embodiments is implemented.

[0162] Optionally, the computer program stored in the non-volatile computer-readable storage medium is used by the processor to execute the following steps:

[0163] S1, obtaining function requirement information and preset execution parameters of a target task node, wherein the function requirement information is used to determine the function to be deployed corresponding to the target task node, and the preset execution parameters are used to represent instance execution parameters of the function to be deployed;

[0164] S2, determining a target action unit based on the function requirement information, wherein the target action unit includes: a first action unit and a second action unit, the first action unit is used to represent a built-in action unit associated with the function to be deployed, and the second action unit is used to represent a mirror action unit associated with the function to be deployed;

[0165] S3, orchestrate the target action unit and create an action unit flow corresponding to the target task node, wherein the action unit flow is used to represent the process execution template corresponding to the function to be deployed;

[0166] S4, executing the action unit flow based on the preset execution parameters to obtain an instance execution result, wherein the instance execution result is used to perform functional verification on the action unit flow.

[0167] The embodiment of the present application further provides a computer program. Optionally, in this embodiment, when the computer program is executed by a processor, the method provided in the above embodiment is implemented.

[0168] Optionally, the computer program is executed by a processor to perform the following steps:

[0169] S1, obtaining function requirement information and preset execution parameters of a target task node, wherein the function requirement information is used to determine the function to be deployed corresponding to the target task node, and the preset execution parameters are used to represent instance execution parameters of the function to be deployed;

[0170] S2, determining a target action unit based on the function requirement information, wherein the target action unit includes: a first action unit and a second action unit, the first action unit is used to represent a built-in action unit associated with the function to be deployed, and the second action unit is used to represent a mirror action unit associated with the function to be deployed;

[0171] S3, orchestrate the target action unit and create an action unit flow corresponding to the target task node, wherein the action unit flow is used to represent the process execution template corresponding to the function to be deployed;

[0172] S4, executing the action unit flow based on the preset execution parameters to obtain an instance execution result, wherein the instance execution result is used to perform functional verification on the action unit flow.

[0173] The serial numbers of the above-mentioned embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.

[0174] In the above embodiments of the present application, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, please refer to the relevant description of other embodiments.

[0175] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the device embodiments described above are only schematic. For example, the division of units can be a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of units or modules, which can be electrical or other forms.

[0176] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed over multiple units. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

[0177] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0178] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art or all or part of the technical solution, can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, server or network device, etc.) to perform all or part of the steps of each embodiment method of the present application. The aforementioned storage medium includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, disk or optical disk, etc. Various media that can store program codes.

[0179] The above are only preferred implementations of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present application. These improvements and modifications should also be regarded as the scope of protection of the present application.

Claims

1. A data processing method, characterized in that: include: Acquire function requirement information and preset execution parameters of the target task node, wherein the function requirement information is used to determine the function to be deployed corresponding to the target task node, and the preset execution parameters are used to represent instance execution parameters of the function to be deployed; Determine a target action unit based on the function requirement information, wherein the target action unit includes: a first action unit and a second action unit, the first action unit is used to represent a built-in action unit associated with the function to be deployed, and the second action unit is used to represent a mirror action unit associated with the function to be deployed; Performing orchestration processing on the target action unit to create an action unit flow corresponding to the target task node, wherein the action unit flow is used to represent a process execution template corresponding to the function to be deployed; The action unit flow is executed based on the preset execution parameters to obtain an instance execution result, wherein the instance execution result is used to perform functional verification on the action unit flow.

2. The data processing method according to claim 1, characterized in that: Determining the target action unit based on the functional requirement information includes: Parsing the function requirement information to obtain a function analysis result, wherein the function analysis result is used to determine at least one sub-function included in the function to be deployed; The target action unit is determined based on the function analysis result.

3. The data processing method according to claim 2, characterized in that: Determining the target action unit based on the function analysis result includes: Performing query processing on the current workflow system based on the function analysis result to obtain a query result, wherein the current workflow system includes a plurality of candidate action units, and the execution frequency of the candidate action units is higher than a preset threshold; In response to the candidate action unit matching the sub-function existing in the query result, the built-in action unit is determined based on the candidate action unit.

4. The data processing method according to claim 3, characterized in that: Determining the target action unit based on the function analysis result includes: In response to the candidate action unit not existing in the query result and matching the sub-function, the mirror action unit corresponding to the sub-function is acquired from a preset mirror repository.

5. The data processing method according to claim 4, characterized in that: The method further comprises: Using a preset programming language to write the mirror action unit corresponding to the sub-function; Packaging the image action unit to obtain a packaging result, wherein the packaging result is used to represent the container image corresponding to the image action unit; The packaging result is uploaded to the preset image repository.

6. The data processing method according to claim 4, characterized in that: The method further comprises: Performing registration processing on the mirror action unit to obtain a registration result, wherein the registration result is used to indicate that the mirror action unit is in an available state; The mirrored action unit is bound to the action unit stream based on the registration result.

7. The data processing method according to claim 1, characterized in that: Performing orchestration processing on the target action unit to create the action unit flow corresponding to the target task node includes: Obtaining a preset arrangement sequence, wherein the preset arrangement sequence is used to determine an execution sequence of a built-in action unit and the mirror action unit; The target action unit is arranged based on the preset arrangement order to obtain the action unit stream.

8. The data processing method according to claim 7, characterized in that: Executing the action unit flow based on the preset execution parameters to obtain the example execution result includes: Filling the action unit flow with the preset execution parameters to obtain a parameter filling result, wherein the parameter filling result is used to determine an execution object associated with the target action unit; The action unit flow is executed based on the parameter filling result to obtain the instance execution result.

9. The data processing method according to claim 8, characterized in that: Executing the action unit flow based on the parameter filling result includes: In response to the current action unit in the action unit stream being the built-in action unit, a built-in execution function corresponding to the built-in action unit is executed in a local environment based on the parameter filling result.

10. The data processing method according to claim 8, characterized in that: Executing the action unit flow based on the parameter filling result includes: In response to the current action unit in the action unit stream being the mirrored action unit, the mirrored action unit is scheduled for execution based on the parameter filling result and a container orchestration framework.

11. A data processing device, characterized in that: include: An acquisition module, used to acquire function requirement information and preset execution parameters of a target task node, wherein the function requirement information is used to determine the function to be deployed corresponding to the target task node, and the preset execution parameters are used to represent instance execution parameters of the function to be deployed; A determination module, configured to determine a target action unit based on the function requirement information, wherein the target action unit includes: a first action unit and a second action unit, the first action unit being used to represent a built-in action unit associated with the function to be deployed, and the second action unit being used to represent a mirror action unit associated with the function to be deployed; A creation module, used to perform orchestration processing on the target action unit, and create an action unit flow corresponding to the target task node, wherein the action unit flow is used to represent a process execution template corresponding to the function to be deployed; An execution module is used to execute the action unit flow based on the preset execution parameters to obtain an instance execution result, wherein the instance execution result is used to perform functional verification on the action unit flow.

12. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, wherein the computer program is configured to execute the data processing method according to any one of claims 1 to 10 when executed by a processor.

13. An electronic device comprising a memory and a processor, characterized in that: A computer program is stored in the memory, and the processor is configured to run the computer program to execute the data processing method according to any one of claims 1 to 10.

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