Process automation method and device, computer equipment, readable storage medium and program product

Abstract

The invention relates to a process automation method and device, computer equipment, a computer readable storage medium and a computer program product. The method comprises the steps of obtaining parameter information in a task application form; determining a target to-be-processed task according to the parameter information; determining a corresponding template flow according to the target to-be-processed task; the template process comprises an execution sequence of sub-tasks of the target to-be-processed task and a parameter transmission rule of each sub-task; and executing each subtask according to the parameter information, the execution sequence of the subtasks and the parameter transmission rule of each subtask until the execution of the last subtask is completed. By adopting the method, the number of times of manually initiating the application can be reduced, the filling of the parameters of the corresponding sub-task during each application is reduced, and the automatic management of the process is realized, so that the process management efficiency is improved.

Description

Technical Field

[0001] The present application relates to the field of network operation and maintenance technology, and in particular to a process automation method, apparatus, computer equipment, computer-readable storage medium, and computer program product. Background Art

[0002] As enterprises continue to introduce and widely deploy new technologies such as distribution, microservices, cloud native, and open source, the deployment architecture of application systems and the resources and component requirements they require are becoming increasingly complex, resulting in a sharp increase in the complexity of operations and maintenance.

[0003] In traditional technology, an IT service management platform is built based on the ITIL v2 / v3 concept to achieve standardization and regularization of service management. Each business department can submit service requests through the platform. Traditional IT service management platforms provide separate services according to different technical lines. A task may be completed through multiple services. Only after the first service is completed can an application for subsequent service be manually initiated.

[0004] However, the current service process management method has the problem of low efficiency in the IT service management process. Summary of the invention

[0005] Based on this, it is necessary to provide a process automation method, device, computer equipment, computer-readable storage medium and computer program product that can improve management efficiency in response to the above technical problems.

[0006] In a first aspect, the present application provides a process automation method, the method comprising:

[0007] Get the parameter information in the task application form;

[0008] Determine the target task to be processed according to the parameter information;

[0009] Determine a corresponding template process according to the target task to be processed; the template process includes the execution order of subtasks of the target task to be processed and the parameter transfer rule of each subtask;

[0010] According to the parameter information, the execution order of the subtasks and the parameter transfer rule of each subtask, each of the subtasks is executed until the last subtask is completed.

[0011] In one of the embodiments, before determining the corresponding template process according to the target task to be processed, the method further includes:

[0012] For each task to be processed, obtain the subtasks corresponding to the task to be processed and the execution order of each subtask;

[0013] According to the execution order, the subtasks are sorted by at least one of series connection or parallel connection;

[0014] The parameter transfer rules of each of the subtasks that have been sorted are configured, and the template flow of each of the tasks to be processed is determined.

[0015] In one embodiment, the parameter information includes key parameters and associated parameters corresponding to the key parameters; before obtaining the parameter information in the task application form, it includes:

[0016] In response to the input instruction, obtaining key parameters of the task application in the initial task application form;

[0017] Based on the parameter mapping rule and the key parameter, generating an associated parameter corresponding to the key parameter;

[0018] Fill the associated parameters into the initial task application form to determine the task application form.

[0019] In one embodiment, executing each of the subtasks according to the parameter information, the execution order of the subtasks and the parameter transfer rule of each of the subtasks includes:

[0020] In the case where the current subtask is not the first subtask, based on the parameter transfer rule and the execution order of the subtasks, the input parameters of the current subtask are obtained; the input parameters at least include first-type input parameters, the first-type input parameters represent a previous parameter that references at least one of the parameter information and the parameters of the previous subtask; the previous subtask is any previous subtask of the current subtask;

[0021] The input parameters of the current subtask are processed according to the processing logic of the current subtask to execute the current subtask.

[0022] In one embodiment, the input parameter further includes a second type of input parameter; and obtaining the input parameter of the current subtask based on the parameter transfer rule and the execution order of the subtask includes:

[0023] According to the execution order of the subtasks, obtaining the predecessor subtask of the current subtask and the parameters of the predecessor subtask;

[0024] According to the parameter transfer rule of the current subtask, acquiring corresponding parameters from at least one of the parameter information and the parameters of the preceding subtask as the first type of input parameters;

[0025] The second type of input parameter is determined according to at least one of the first type of input parameter and an external parameter, wherein the external parameter represents a parameter corresponding to a task to be processed other than the target task to be processed.

[0026] In one embodiment, the method further comprises:

[0027] Obtaining the total processing period of the target pending tasks;

[0028] Determine the processing deadline of each of the subtasks according to the total processing deadline and the execution order of the subtasks; the sum of the processing deadlines of the subtasks is greater than or equal to the total processing deadline;

[0029] Compare the processing deadline of each of the subtasks with the corresponding preset processing deadline, and select the subtasks whose processing deadline is greater than the preset processing deadline;

[0030] Send reminder information to the subtasks that meet the preset conditions.

[0031] In a second aspect, the present application further provides a process automation device, the device comprising:

[0032] The acquisition module is used to obtain parameter information in the task application form;

[0033] A task determination module, used to determine a target task to be processed according to the parameter information;

[0034] A template process determination module, used to determine a corresponding template process according to the target task to be processed; the template process includes the execution order of the subtasks of the target task to be processed and the parameter transfer rules of each subtask;

[0035] The execution module is used to execute each of the subtasks according to the parameter information, the execution order of the subtasks and the parameter transfer rule of each subtask until the last subtask is completed.

[0036] In a third aspect, the present application further provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and the processor implements the steps of the above method when executing the computer program.

[0037] In a fourth aspect, the present application further provides a computer-readable storage medium having a computer program stored thereon, wherein the computer program implements the steps of the above method when executed by a processor.

[0038] In a fifth aspect, the present application also provides a computer program product, including a computer program, which implements the steps of the above method when executed by a processor.

[0039] The above-mentioned process automation method, device, computer equipment, computer-readable storage medium and computer program product pre-set the template process corresponding to each pending task, and the template process includes the execution order of each subtask and the parameter transfer rules of each subtask; determine the target pending task according to the parameter information in the task application form, and obtain the template process corresponding to the target pending task from the preset template process corresponding to each pending task according to the target pending task. The template process avoids the manual initiation of the subtask applied later after the previous subtask is completed, thereby improving the efficiency of inter-process management. According to the execution order of each subtask in the template process and the parameter transfer rules of each subtask, as well as the parameter information, the parameters of each subtask can be automatically determined; it avoids the need to fill in the parameters of the corresponding subtask when manually initiating the application, and also improves the reference and exchange of parameters between each subtask, breaking the information islands between each subtask. All subtasks are executed and completed according to the parameters of each subtask, further improving the efficiency of process management. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] In order to more clearly illustrate the technical solutions in the embodiments of the present application or related technologies, the drawings required for use in the embodiments of the present application or related technical descriptions will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.

[0041] Figure 1 An application environment diagram of a process automation method in an embodiment;

[0042] Figure 2 A schematic diagram of a process automation method in one embodiment;

[0043] Figure 3 A schematic diagram of a process flow of pre-configuring a template process for tasks to be processed in one embodiment;

[0044] Figure 4 A schematic diagram of a process for determining a task application form in one embodiment;

[0045] Figure 5 A schematic diagram of a flow chart of executing each subtask according to parameter information, the execution order of the subtasks and the parameter transfer rule of each subtask in an embodiment;

[0046] Figure 6 A schematic diagram of a process of obtaining input parameters of a current subtask based on parameter transfer rules and the execution order of subtasks in an embodiment;

[0047] Figure 7A schematic diagram of a process for urging the completion of subtasks in an embodiment;

[0048] Figure 8 A schematic diagram of a process automation method in another embodiment;

[0049] Fig. 9 is a structural block diagram of a process automation device in an embodiment;

[0050] Fig.10 FIG. 4 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0051] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0052] The process automation method provided in the embodiment of the present application can be applied to Figure 1 In the application environment shown. Among them, the terminal 102 communicates with the server 104 through the network. The data storage system can store the data that the server 104 needs to process. The data storage system can be integrated on the server 104, or it can be placed on the cloud or other network servers. The server obtains the parameter information in the task application form sent by the terminal device; according to the parameter information, the target task to be processed is determined; according to the target task to be processed, the corresponding template process is determined; the template process includes the execution order of the subtasks of the target task to be processed and the parameter transfer rules of each subtask; according to the parameter information, the execution order of the subtasks and the parameter transfer rules of each subtask, each subtask is executed until the last subtask is completed. Among them, the terminal 102 can be, but is not limited to, various personal computers, laptops, smart phones, tablet computers, Internet of Things devices and portable wearable devices. The Internet of Things devices can be smart speakers, smart TVs, smart air conditioners, smart car devices, projection devices, etc. Portable wearable devices can be smart watches, smart bracelets, head-mounted devices, etc. Head-mounted devices can be virtual reality (VR) devices, augmented reality (AR) devices, smart glasses, etc. The server 104 may be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides cloud computing services.

[0053] In an exemplary embodiment, Figure 2 As shown, a process automation method is provided, which is applied to Figure 1 The server in the example is used to illustrate, including the following steps S202 to S206. Among them:

[0054] Step S202, obtaining parameter information in the task application form.

[0055] Among them, the task application form is a document filled out by the user for task application, also called a work order, which contains basic information and parameters of the work order, such as tasks for machine delivery.

[0056] Optionally, the user fills in a task application form on the terminal device and sends the task application form to the server, and the server obtains the parameter information in the task application form. For example, the user fills in information in the task application form for the task delivered by the machine, and the filled-in information includes, for example, the number of machines, the area to be placed, the configuration of the machine, the ownership of the machine, etc. When filling in the form, the user selects the data of the management object (such as the machine) from the Configuration Management Database (CMDB) through customized controls; the server automatically fills the relevant attributes of the management object into the corresponding field according to the parameter mapping rules, simplifying the task application form filling process when the user applies.

[0057] Optionally, the server obtains the task application form filled out by the user and obtains the parameter information in the task application form. The parameter information includes three parts: basic attributes, management attributes, and configuration attributes. The basic attributes mainly include basic information such as the work order name, abbreviation, status, description, work order type, business type, and source; the management attributes mainly include the work order business owner Owner, applicant, SLA (working day), work order construction / maintenance project team, operation / communication time saving, etc.; the configuration attributes mainly include task scheduling configuration, parameter verification configuration, attachment configuration, etc.

[0058] Step S204: determining the target task to be processed according to the parameter information.

[0059] Optionally, the server determines the corresponding target task to be processed based on the parameter information, such as if the parameter information includes a task name field of machine delivery. For another example, if the parameter information includes a task name field of software delivery, the server determines the corresponding target task to be processed based on the parameter information. The parameter information may also include at least one other field information that can determine the target task to be processed, such as a configuration task type, a configuration task identifier, etc.

[0060] Step S206, determining a corresponding template process according to the target task to be processed; the template process includes the execution order of the subtasks of the target task to be processed and the parameter transfer rule of each subtask.

[0061] The template process is determined based on the research of various pending tasks conducted in the early stage. It is mainly guided by the value delivery concept of ITIL4, designs the scenario-based value realization of operation and maintenance services, builds a self-service operation and maintenance delivery chain, and realizes the cross-technology line collaborative automated service delivery capability. ITIL4, the Information Technology Infrastructure Library version 4, is a widely accepted IT service management (ITSM) framework in the world.

[0062] Before configuring the template process, the server obtains research requirements to clarify the owner of the task to be processed and the group or individual involved in the process; then it decomposes each step of the task to be processed into the smallest, specific, atomic subtasks, clarifies the responsibilities, goals, and values ​​of each subtask, and defines the subtasks; finally, according to the dependencies between subtasks, it arranges each independent subtask to form a serial and parallel workflow. The arrangement includes the arrangement order / process of each subtask and the transmission rules of the parameters of each subtask.

[0063] Each independent subtask is arranged to form a serial and parallel workflow, including: the server arranges the subtasks in at least one of serial and parallel by dragging and dropping. The same subtask can be referenced multiple times in the task flow to be processed, and the task can be renamed to distinguish different task processing contents. The server also pre-configures the parameter transfer rules for each subtask. The parameters of the current subtask come from the parameter information in the work order, the input parameters and output parameters of the previous subtask, etc. The parameter transfer rules of the subtask are configured to realize the standardized flow of parameters in the task flow to be processed.

[0064] Optionally, the server determines a corresponding template process from preset pending tasks according to the target pending task. Assume that the pending task is machine delivery, which includes n subtasks, where n is a natural number greater than or equal to 2. The subtasks of machine delivery are: machine delivery, machine room entry, network cable plugging, IP address allocation, operating system installation, vulnerability patching, software installation, archiving, etc.

[0065] For example, pending task 1 is machine delivery, including 8 subtasks; pending task 2 is software delivery, including n subtasks; and so on. According to the subtasks included in the pending task, a corresponding template process is configured for each pending task. The server determines the corresponding template process from the preset pending tasks according to the target pending task, and executes each subtask according to the template process.

[0066] Step S208, executing each subtask according to the parameter information, the execution order of the subtasks and the parameter transfer rule of each subtask, until the last subtask is completed.

[0067] Optionally, the template process corresponding to the target task to be processed is the execution order of the three subtasks and the transfer rules of each subtask. For example, the execution order of the subtasks is subtask 1, subtask 2, and subtask 3. According to the parameter transfer rule of subtask 1, the server uses part of the parameter information in the task application form as the input parameter of subtask 1, executes subtask 1 according to the input parameter of subtask 1, and generates the output parameter of subtask 1 after the execution of subtask 1. According to the parameter transfer rule of subtask 2, the server uses part of the parameter information in the task application form and the output parameter after the execution of subtask 1 as the input parameter of subtask 2, executes subtask 2 according to the input parameter of subtask 2, and generates the output parameter of subtask 2 after the execution of subtask 2. According to the parameter transfer rule of subtask 3, the server uses the output parameter of subtask 2 as the input parameter of subtask 3, and executes subtask 3 according to the input parameter of subtask 3.

[0068] It should be noted that the execution order of several subtasks corresponding to the pending task and the transfer rules of each subtask are set according to actual needs, and the number of subtasks is not limited. According to the execution order of subtasks, the input parameters or output parameters of the previous subtask can be used by the subsequent subtask. Each subtask will have corresponding input parameters, but it may not generate corresponding output parameters. For example, in the machine delivery task, the subtasks of machine delivery, machine room entry, and network cable plugging will not generate output parameters, but the allocation of IP addresses will generate output parameters, that is, the IP address is the output parameter. In the subsequent subtasks of installing software, the output parameter of the IP address will be used as the input parameter.

[0069] In the above-mentioned process automation method, by presetting the template process corresponding to each pending task, the template process includes the execution order of each subtask and the parameter transfer rules of each subtask; the target pending task is determined according to the parameter information in the task application form, and the template process corresponding to the target pending task is obtained from the preset template process corresponding to each pending task according to the target pending task. The template process avoids the manual initiation of the subtask applied later after the previous subtask is completed, thereby improving the efficiency of inter-process management. According to the execution order of each subtask in the template process and the parameter transfer rules of each subtask, as well as the parameter information, the parameters of each subtask can be automatically determined; it is avoided that the parameters of the corresponding subtask need to be filled in multiple times when manually initiating the application, and it also improves the reference and exchange of parameters between each subtask, breaks the information islands between each subtask, reduces the number of subtask applications and the number of application forms filled in; all subtasks are completed according to the parameters of each subtask, further improving the efficiency of process management.

[0070] In an exemplary embodiment, Figure 3 As shown, before determining the corresponding template process according to the target to-be-processed task, the template process of the to-be-processed task is pre-configured, and further includes steps S302 to S306. Among them:

[0071] Step S302: for each task to be processed, obtain the subtasks corresponding to the task to be processed and the execution order of each subtask.

[0072] Optionally, before determining the corresponding template process according to the target pending task, pre-configure the template process of the pending task, and for each pending task, clarify the owner of the pending task and the group or individual involved in the process; then decompose each step of the pending task into the smallest, specific, atomic subtasks, clarify the responsibilities, goals and values ​​of each subtask, define the subtasks, and obtain the subtasks corresponding to each pending task.

[0073] Step S304: sorting the subtasks according to the execution order by at least one of serial connection and parallel connection.

[0074] Optionally, the server arranges the subtasks in at least one of series and parallel by dragging and dropping according to the execution order of the subtasks and the dependency relationship of the subtasks. For example, if the pending task 1 includes 5 subtasks, the execution order of the subtasks is subtask 1, subtask 2, subtask 3, subtask 4, and subtask 5. For another example, if the pending task 2 includes 6 subtasks, the execution order of the subtasks is subtask 1, subtask 2, and subtask 3 in parallel, all of which are post-tasks of subtask 1, and subtask 4, subtask 5, and subtask 6 in parallel.

[0075] Step S306, configuring the parameter transfer rules for each subtask that has been sorted, and determining the template flow for each task to be processed.

[0076] Optionally, the server also configures the parameter transfer rules for each subtask that has been sorted in advance. For example, the input parameters of the first type of subtask are based on the parameter information in the work order; the input parameters of the second type of subtask are based on at least one of the input parameters and output parameters of the previous subtask; the input parameters of the third type of subtask are based on the parameter information and at least one of the input parameters and output parameters of the previous subtask. The parameter transfer rules of the configured subtasks are used to realize the standardized flow of parameters of the task flow to be processed.

[0077] In this embodiment, by configuring the execution order of each subtask and the parameter transfer rule of each subtask as a template process, it is possible to directly call the template process to realize the automation of the target task process to be processed.

[0078] In an exemplary embodiment, Figure 4 As shown, the parameter information includes key parameters and associated parameters corresponding to the key parameters; before obtaining the parameter information in the task application form, the task application form is determined, and steps S402 to S406 are also included. Among them:

[0079] Step S402, in response to the input instruction, obtaining key parameters in the initial task application form.

[0080] Among them, key parameters refer to the necessary information in the initial task application form that directly affects the nature of the task application or determines the nature of the task. Key parameters are usually required to be explicitly provided by the user.

[0081] Optionally, the server fills in the key parameters of the task application in the initial task application form in response to the user's input instruction. The key parameters include parameters other than basic parameter types such as text, value column, password, etc.

[0082] In traditional technology, users fill in application form parameters each time they apply for a service task, and they need to complete the previous subtask before they can manually apply for the next subtask. When applying for the next subtask, they need to fill in the application parameters again. In this embodiment, users only need to fill in the form when applying for a task for the first time, which greatly reduces the number of times users fill in application forms, thereby automating the process and improving efficiency.

[0083] Step S404: Generate associated parameters corresponding to the key parameters based on the parameter mapping rule and the key parameters.

[0084] Among them, the associated parameters are additional information derived from the key parameters through certain rules or logic. These parameters are not directly provided by the user, but are automatically generated by the system based on the key parameters and preset rules.

[0085] Optionally, the server selects data of key parameters from a configuration management database (CMDB) through a customized control; the server automatically obtains associated parameters of the key parameters according to a parameter mapping rule.

[0086] Step S406, filling in the associated parameters into the initial task application form to determine the task application form.

[0087] Optionally, the server fills the associated parameters into the fields corresponding to the initial task application form to determine the task application form. This simplifies the task application form filling process when the user applies. It also facilitates the subsequent server to obtain parameter information from the task application form.

[0088] In this embodiment, based on the development of customized controls, after the user selects key parameters when filling out the form on the page, the key parameters can be automatically filled into other fields of the form according to the parameter mapping rules, avoiding manual filling of parameters multiple times and realizing the automation of the process.

[0089] In an exemplary embodiment, Figure 5 As shown, each subtask is executed according to the parameter information, the execution order of the subtasks and the parameter transfer rule of each subtask, including steps S502 to S504. Among them:

[0090] Step S502, when the current subtask is not the first subtask, based on the parameter passing rules and the execution order of the subtasks, the input parameters of the current subtask are obtained; the input parameters include at least first type input parameters, and the first type input parameters represent the previous parameters of at least one of the referenced parameter information and the parameters of the predecessor subtask; the predecessor subtask is any previous subtask of the current subtask.

[0091] Optionally, when the current subtask is not the first subtask, the input parameters of the current subtask are obtained based on the parameter passing rules and the execution order of the subtasks; since the parameter passing rules for each subtask are different, the input parameters of the subtask are also different. The input parameters include at least a first type of input parameter, and the first type of input parameter represents a prior parameter of at least one of the referenced parameter information and the parameters of the preceding subtask; the preceding subtask is any prior subtask of the current subtask. If the current subtask is subtask 9, according to the parameter passing rules of subtask 9, the parameter information, the output parameters of subtask 1, the input parameters of subtask 5, and part of the input parameters of subtask 7 are obtained as the input parameters of the current subtask. That is, these prior parameters are not processed, and the prior parameters are directly reused.

[0092] Optionally, when the current subtask is the first subtask, that is, there is no preceding subtask, the server obtains input parameters of the current subtask based on the parameter transfer rule and the execution order of the subtasks; the input parameters include parameter information in the task application form.

[0093] Step S504: Process the input parameters of the current subtask according to the processing logic of the current subtask to execute the current subtask.

[0094] Optionally, the server processes the input parameters of the current subtask according to the processing logic of the current subtask to execute the current subtask. After each current subtask is processed, the target task to be processed is processed according to the subtask execution order and parameter transfer rules to achieve standardized transfer of each subtask parameter to complete the target task to be processed.

[0095] In this embodiment, standardized transmission of parameters for each subtask is achieved based on parameter transmission rules and the execution order of subtasks, replacing the offline communication and collaboration process across technical lines and eliminating the waiting and manual handling of parameters in the target pending task delivery process.

[0096] In an exemplary embodiment, Figure 6 As shown, the input parameters also include second type input parameters; based on the parameter transfer rule and the execution order of the subtasks, the input parameters of the current subtask are obtained, including steps S602 to S606. Among them:

[0097] Step S602: Obtain the predecessor subtask of the current subtask and the parameters of the predecessor subtask according to the execution order of the subtasks.

[0098] Optionally, the server obtains the previous subtask of the current subtask and the parameters of the previous subtask according to the execution order of the subtasks. If the current subtask is subtask 6, then any of subtasks 1-5 can be called a previous subtask. And obtain the parameters of the previous subtask.

[0099] Step S604: According to the parameter transfer rule of the current subtask, a corresponding parameter is obtained from at least one of the parameter information and the parameters of the preceding subtask as a first type of input parameter.

[0100] Optionally, in the case where the current subtask reuses parameters, the server obtains corresponding parameters from at least one of the parameter information and the parameters of the previous subtask as the first type of input parameters according to the parameter transfer rule of the current subtask. For example, there are 10 input parameters in the parameter information, and the target task to be processed includes 10 subtasks. It is assumed that subtask 1, subtask 3, subtask 5, subtask 7, and subtask 9 all use 5 of the 10 input parameters in the parameter information as input parameters of each subtask.

[0101] Furthermore, the server determines whether the input parameters of each subtask need special processing, and the special processing is used to enrich or logically process the subtask parameters. If subtask 1 does not need special processing, that is, the input parameters of subtask 1 are 5 of the 10 input parameters. The input parameters can be processed according to the processing logic of subtask 1 to execute and complete subtask 1.

[0102] Step S606: Determine a second type of input parameter according to at least one of the first type of input parameter and the external parameter.

[0103] The external parameters represent the parameters corresponding to the tasks to be processed other than the target tasks to be processed.

[0104] Optionally, if subtask 3, subtask 5, subtask 7, and subtask 9 all require special processing of input parameters, the parameter special preprocessing microservice protocol is called to enrich the first type of input parameters. If subtask 3 requires two parameters as second type input parameters in addition to the aforementioned five reused input parameters, the calculation of the second type input parameters at this time includes at least one of the following: the server determines the second type input parameters based on the first type input parameters. The server jointly determines the second type input parameters based on the first type input parameters and external parameters. The server jointly determines the second type input parameters based on external parameters. And so on, determine the second type input parameters corresponding to each of subtask 5, subtask 7, and subtask 9.

[0105] In this embodiment, the previous parameter can be referenced by at least one subtask, which improves the reuse rate, the efficiency of parameter calculation, and the efficiency of process automation. The second type of input parameter can also be calculated based on the previous parameter and the external parameter, so that each subtask can obtain its corresponding first type input parameter and second type input parameter to execute the subtask.

[0106] In an exemplary embodiment, Figure 7 As shown, the urging of subtasks includes steps S702 to S708. Among them:

[0107] Step S702, obtaining the total processing period of the target task to be processed.

[0108] Optionally, the server obtains the total processing period of the target pending tasks, for example, the total processing period of the target pending tasks is 9 days.

[0109] Step S704, determining the processing deadline of each subtask according to the total processing deadline and the execution order of the subtasks; the sum of the processing deadlines of the subtasks is greater than or equal to the total processing deadline.

[0110] Optionally, the server determines the processing deadline for each subtask based on the total processing deadline and the execution order of the subtasks. The server evaluates the processing deadline for each subtask, and then accumulates the time consumed by the serial subtasks by sorting out the serial-parallel relationship, and obtains the processing deadline for the parallel subtasks, thereby preliminarily deriving the processing deadline for the work order, which is also the working day SLA. For example, if the target task to be processed includes 3 subtasks, and if subtask 2 and subtask 3 are processed in parallel, the processing deadline for subtask 2 is 8 days, and subtask 3 only takes 7 days. When subtask 2 and subtask 3 are processed in parallel, the processing deadline is 8 days. The processing deadline for subtask 1 is 1 day. According to traditional process management, the processing deadline for the 3 subtasks of the target task to be processed may be 16 days.

[0111] Step S706: compare the processing deadline of each subtask with the corresponding preset processing deadline, and select subtasks whose processing deadline is greater than the preset processing deadline.

[0112] Optionally, in the execution process of the target pending task, the server compares the processing deadline of each subtask with the corresponding preset processing deadline, and screens out subtasks whose processing deadline is greater than the preset processing deadline. If the processing deadline is greater than the preset processing deadline, it means that the execution of the subtask is about to expire or has expired, and a reminder message is sent to the subtask that is about to expire or has expired. At the same time, the server can analyze the overall delivery cycle and the SLA compliance rate of each subtask, and identify the links with longer processing deadlines for improvement.

[0113] Step S708: Send reminder information to the subtasks that meet the preset conditions.

[0114] Optionally, the server sends reminder information to the subtask that is about to expire or has expired. If the task is still not processed after repeated reminders, the reminder information can be sent to management personnel, such as line leaders or leaders.

[0115] In this embodiment, the working day SLA of the subtask calculated by the task combination is used as a benchmark, and the system automatically calculates the time consumption of each subtask, automatically urges the overdue and about to be overdue subtasks, and analyzes the delivery status of each subtask at the same time, continuously improving the service delivery value stream.

[0116] In an exemplary embodiment, it includes a configuration phase and an application phase. Figure 8 As shown. In the configuration stage: the user enters instructions in the initial task application form, and the server fills in the key parameters of the task application in the initial task application form in response to the user's input instructions. Key parameters include parameters other than basic text, value columns, passwords and other parameter types. The server selects the data of key parameters from the Configuration Management Database (CMDB) through customized controls; the server automatically obtains the associated parameters of the key parameters according to the parameter mapping rules. The server fills the associated parameters into the corresponding fields of the initial task application form to determine the task application form. Simplifies the task application form filling process when the user applies. It is also convenient for the subsequent server to obtain parameter information from the task application form.

[0117] Through the standard application interface, configure the template process of each pending task, or execute the target pending task according to the template process of the target pending task. Before determining the corresponding template process according to the target pending task, pre-configure the template process of the pending task, and for each pending task, clarify the owner of the pending task and the group or individual involved in the process; then decompose each step of the pending task into the smallest, specific, atomic subtasks, clarify the responsibilities, goals and values ​​of each subtask, and define the subtasks to obtain the subtasks corresponding to each pending task. The server arranges the subtasks in at least one of series and parallel by dragging and dropping according to the execution order of the subtasks and the dependency relationship of the subtasks. For example, pending task 1 includes 5 subtasks, and the execution order of the subtasks is subtask 1, subtask 2, subtask 3, subtask 4 and subtask 5. For another example, pending task 2 includes 6 subtasks, and the execution order of the subtasks is subtask 1, subtask 2 and subtask 3 in parallel, all of which are post-tasks of subtask 1, and subtask 4, subtask 5 and subtask 6 in parallel. The server also configures the parameter transfer rules for each subtask that has been sorted in advance. For example, the input parameters of the first type of subtask are based on the parameter information in the work order; the input parameters of the second type of subtask are based on at least one of the input parameters and output parameters of the previous subtask; the input parameters of the third type of subtask are based on the parameter information and at least one of the input parameters and output parameters of the previous subtask. The parameter transfer rules of the configured subtasks are used to achieve the standardized flow of parameters in the task flow to be processed.

[0118] In the use phase: the user fills in the task application form on the terminal device and sends the task application form to the server, and the server obtains the parameter information in the task application form. For example, the user fills in information in the task application form for the machine delivery task, and the filled-in information includes, for example, the number of machines, the area to be placed, the configuration of the machine, the ownership of the machine, etc. When filling in the form, the user selects the data of the management object (such as the machine) from the configuration management database (CMDB) through the customized control; the server automatically fills the relevant attributes of the management object into the corresponding field according to the parameter mapping rule, simplifying the task application form filling process when the user applies. The server determines the corresponding target pending task based on the parameter information, such as the parameter information includes the task name field as machine delivery. For another example, the parameter information includes the task name field as software delivery; the server determines the corresponding target pending task based on the parameter information. The parameter information may also include at least one other field information that can determine the target pending task, such as the configuration task type, the configuration task identifier, etc. The server determines the corresponding template process from the preset pending tasks based on the target pending task. Assuming that the pending task is machine delivery, it includes n subtasks, and n is a natural number greater than or equal to 2. The subtasks of machine delivery are: machine out of the warehouse, into the machine room, plug in the network cable, assign IP address, install the operating system, patch vulnerabilities, install software, archive, etc. For example, pending task 1 is machine delivery, including 8 subtasks; pending task 2 is software delivery, including n subtasks; and so on. According to the subtasks included in the pending task, a corresponding template process is configured for each pending task. The server determines the corresponding template process from the preset pending tasks according to the target pending task, and executes each subtask according to the template process.

[0119] In the case where the current subtask is not the first subtask, the input parameters of the current subtask are obtained based on the parameter passing rules and the execution order of the subtasks; since the parameter passing rules for each subtask are different, the input parameters of the subtask are also different. The input parameters include at least a first type of input parameter, and the first type of input parameter represents a prior parameter of at least one of the referenced parameter information and the parameters of the preceding subtask; the preceding subtask is any prior subtask of the current subtask. If the current subtask is subtask 9, according to the parameter passing rules of subtask 9, the parameter information, the output parameters of subtask 1, the input parameters of subtask 5, and part of the input parameters of subtask 7 are obtained as the input parameters of the current subtask. That is, these prior parameters are not processed, and the prior parameters are directly reused.

[0120] When the current subtask is the first subtask, that is, there is no preceding subtask, the server obtains the input parameters of the current subtask based on the parameter transfer rule and the execution order of the subtasks; the input parameters include the parameter information in the task application form.

[0121] The server processes the input parameters of the current subtask according to the processing logic of the current subtask to execute the current subtask. After each current subtask is processed, the target task to be processed is implemented according to the subtask execution order and the parameter transfer rule to achieve the standardized transfer of each subtask parameter to complete the target task to be processed. The server obtains the previous subtask of the current subtask and the parameters of the previous subtask according to the execution order of the subtask. If the current subtask is subtask 6, then any one of subtasks 1-5 can be called a previous subtask. And obtain the parameters of the previous subtask. In the case of the current subtask reusing parameters, the server obtains the corresponding parameters from at least one of the parameter information and the parameters of the previous subtask according to the parameter transfer rule of the current subtask as the first type of input parameters. For example, there are 10 input parameters in the parameter information, and the target task to be processed includes 10 subtasks. It is assumed that subtask 1, subtask 3, subtask 5, subtask 7 and subtask 9 all use 5 of the 10 input parameters in the parameter information as the input parameters of each subtask.

[0122] Further, the server determines whether the input parameters of each subtask need special processing, and the special processing is used to enrich or logically process the subtask parameters. If subtask 1 does not require special processing, that is, the input parameters of subtask 1 are 5 of the 10 input parameters. The input parameters can be processed according to the processing logic of subtask 1 to execute and complete subtask 1. If subtasks 3, 5, 7, and 9 all need special processing of the input parameters, the parameter special preprocessing microservice protocol is called to enrich the first type of input parameters. If subtask 3 requires two parameters as second type input parameters in addition to the aforementioned 5 reused input parameters, the calculation of the second type input parameters at this time includes at least one of the following: the server determines the second type input parameters according to the first type input parameters. The server jointly determines the second type input parameters according to the first type input parameters and external parameters. The server jointly determines the second type input parameters according to the external parameters. And so on, determine the second type input parameters corresponding to each of subtasks 5, 7, and 9. Among them, the first type of input parameters represent the previous parameters of at least one of the referenced parameter information and the parameters of the predecessor subtask; the predecessor subtask is any previous subtask of the current subtask; the input parameters also include the second type of input parameters; among them, the external parameters represent the parameters corresponding to the tasks to be processed other than the target tasks to be processed.

[0123] The server processes the input parameters of the current subtask according to the processing logic of the current subtask to execute the current subtask. After each current subtask is processed, the target task to be processed is processed according to the subtask execution order and parameter transfer rules to achieve standardized transfer of each subtask parameter to complete the target task to be processed.

[0124] The process automation method also includes: the server obtains the total processing period of the target pending task. For example, the total processing period of the target pending task is 9 days. The server determines the processing period of each subtask according to the total processing period and the execution order of the subtasks. The server evaluates the processing period of each subtask, and then accumulates the time consumption of the serial subtasks by sorting out the serial-parallel relationship, and obtains the processing period of the parallel subtasks, thereby preliminarily obtaining the processing period of the work order, that is, the working day SLA. For example, the target pending task includes 3 subtasks, if subtask 2 and subtask 3 are parallel, the processing period of subtask 2 is 8 days, and subtask 3 only takes 7 days. When subtask 2 and subtask 3 are processed in parallel, the processing period is 8 days. The processing period of subtask 1 is 1 day. According to traditional process management, the processing period of the three subtasks of the target pending task may be 16 days. In the execution process of the target pending task, the server compares the processing period of each subtask with the corresponding preset processing period, and screens out the subtasks whose processing period is greater than the preset processing period. If the processing period is greater than the preset processing period, that is, the execution of the subtask is about to expire or has expired, a reminder message is sent to the subtask that is about to expire or has expired. At the same time, the server can analyze the overall delivery cycle and the SLA compliance rate of each subtask, and identify the links with longer processing periods for improvement. The server sends reminder messages to subtasks that are about to expire or have expired. If the subtask is still not processed after multiple reminders, reminder messages can be sent to management personnel, such as line leaders or leaders.

[0125] It should be understood that, although the various steps in the flowcharts involved in the above-mentioned embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps does not have a strict order restriction, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above-mentioned embodiments can include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.

[0126] Based on the same inventive concept, the embodiment of the present application also provides a process automation device for implementing the process automation method involved above. The implementation solution provided by the device to solve the problem is similar to the implementation solution recorded in the above method, so the specific limitations in one or more process automation device embodiments provided below can refer to the limitations of the process automation method above, and will not be repeated here.

[0127] In an exemplary embodiment, Fig. 9 As shown, a process automation device is provided, including: an acquisition module 901, a task determination module 902, a template process determination module 903 and an execution module 904, wherein:

[0128] The acquisition module 901 is used to acquire parameter information in the task application form.

[0129] The task determination module 902 is used to determine the target task to be processed according to the parameter information.

[0130] The template process determination module 903 is used to determine the corresponding template process according to the target task to be processed; the template process includes the execution order of the subtasks of the target task to be processed and the parameter transfer rules of each subtask.

[0131] The execution module 904 is used to execute each subtask according to the parameter information, the execution order of the subtasks and the parameter transfer rule of each subtask until the last subtask is completed.

[0132] In an exemplary embodiment, a process automation device is provided, further comprising:

[0133] The template process generation module is used to obtain the subtasks corresponding to each pending task and the execution order of each subtask; sort the subtasks according to the execution order through at least one of series or parallel connection; configure the parameter transfer rules for each subtask that has been sorted, and determine the template process for each pending task.

[0134] In an exemplary embodiment, the parameter information includes key parameters and associated parameters corresponding to the key parameters; the process automation device further includes:

[0135] The task application form generation module is used to obtain the key parameters of the task application in the initial task application form in response to the input instruction; generate the associated parameters corresponding to the key parameters based on the parameter mapping rules and the key parameters; fill the associated parameters into the initial task application form to determine the task application form.

[0136] In an exemplary embodiment, the execution module 904 includes:

[0137] A parameter acquisition unit is used to acquire input parameters of the current subtask based on parameter passing rules and the execution order of subtasks when the current subtask is not the first subtask; the input parameters include at least first-type input parameters, and the first-type input parameters represent reference parameter information and a prior parameter of at least one of the parameters of a preceding subtask; a preceding subtask is any prior subtask of the current subtask.

[0138] The execution unit is used to process the input parameters of the current subtask according to the processing logic of the current subtask to execute the current subtask.

[0139] In an exemplary embodiment, the input parameter further includes a second type of input parameter; and the parameter acquisition unit includes:

[0140] The first acquisition sub-unit is used to acquire the previous sub-task of the current sub-task and the parameters of the previous sub-task according to the execution order of the sub-tasks.

[0141] The second acquisition subunit is used to acquire corresponding parameters as first type input parameters from at least one of the parameter information and the parameters of the preceding subtask according to the parameter transfer rule of the current subtask.

[0142] The parameter determination subunit is used to determine the second type of input parameters according to at least one of the first type of input parameters and external parameters, wherein the external parameters represent parameters corresponding to the tasks to be processed other than the target task to be processed.

[0143] In an exemplary embodiment, a process automation device is provided, further comprising:

[0144] The reminder module is used to obtain the total processing period of the target pending tasks; determine the processing period of each subtask based on the total processing period and the execution order of the subtasks; the sum of the processing periods of each subtask is greater than or equal to the total processing period; compare the processing period of each subtask with the corresponding preset processing period, and filter out the subtasks whose processing period is greater than the preset processing period; send reminder information to the subtasks that meet the preset conditions.

[0145] Each module in the above process automation device can be implemented in whole or in part by software, hardware, or a combination thereof. Each module can be embedded in or independent of a processor in a computer device in the form of hardware, or can be stored in a memory in a computer device in the form of software, so that the processor can call and execute operations corresponding to each module.

[0146] In an exemplary embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as shown in FIG. Fig.10As shown. The computer device includes a processor, a memory, an input / output interface (Input / Output, referred to as I / O) and a communication interface. Among them, the processor, the memory and the input / output interface are connected through a system bus, and the communication interface is connected to the system bus through the input / output interface. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store template process data, parameter information and other data. The input / output interface of the computer device is used to exchange information between the processor and an external device. The communication interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a process automation method is implemented.

[0147] Those skilled in the art will understand that Fig.10 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0148] In one embodiment, a computer device is further provided, including a memory and a processor, wherein a computer program is stored in the memory, and the processor implements the steps in the above method embodiments when executing the computer program.

[0149] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps in the above-mentioned method embodiments are implemented.

[0150] In one embodiment, a computer program product is provided, including a computer program, which implements the steps in the above method embodiments when executed by a processor.

[0151] A person of ordinary skill in the art can understand that all or part of the processes in the above-mentioned embodiment method can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in the present application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, an artificial intelligence (AI) processor, etc., but are not limited to this.

[0152] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0153] The above-described embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be construed as limiting the scope of the present application. It should be noted that, for a person of ordinary skill in the art, several modifications and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.

Claims

1. A process automation method, characterized in that: The method comprises: Get the parameter information in the task application form; Determine the target task to be processed according to the parameter information; Determine a corresponding template process according to the target task to be processed; the template process includes the execution order of subtasks of the target task to be processed and the parameter transfer rule of each subtask; According to the parameter information, the execution order of the subtasks and the parameter transfer rule of each subtask, each of the subtasks is executed until the last subtask is completed.

2. The method according to claim 1, characterized in that: Before determining the corresponding template process according to the target task to be processed, the process further includes: For each task to be processed, obtain the subtasks corresponding to the task to be processed and the execution order of each subtask; According to the execution order, the subtasks are sorted by at least one of series connection or parallel connection; The parameter transfer rules of each of the subtasks that have been sorted are configured, and the template flow of each of the tasks to be processed is determined.

3. The method according to claim 1, characterized in that The parameter information includes key parameters and associated parameters corresponding to the key parameters; before obtaining the parameter information in the task application form, it includes: In response to the input instruction, obtaining key parameters of the task application in the initial task application form; Based on the parameter mapping rule and the key parameter, generating an associated parameter corresponding to the key parameter; Fill the associated parameters into the initial task application form to determine the task application form.

4. The method according to claim 1, characterized in that The executing each of the subtasks according to the parameter information, the execution order of the subtasks and the parameter transfer rule of each of the subtasks includes: In the case where the current subtask is not the first subtask, based on the parameter transfer rule and the execution order of the subtasks, the input parameters of the current subtask are obtained; the input parameters at least include first-type input parameters, the first-type input parameters represent a previous parameter that references at least one of the parameter information and the parameters of the previous subtask; the previous subtask is any previous subtask of the current subtask; The input parameters of the current subtask are processed according to the processing logic of the current subtask to execute the current subtask.

5. The method according to claim 4, characterized in that The input parameters also include a second type of input parameters; the acquiring the input parameters of the current subtask based on the parameter transfer rule and the execution order of the subtasks includes: According to the execution order of the subtasks, obtaining the predecessor subtask of the current subtask and the parameters of the predecessor subtask; According to the parameter transfer rule of the current subtask, acquiring corresponding parameters from at least one of the parameter information and the parameters of the preceding subtask as the first type of input parameters; The second type of input parameter is determined according to at least one of the first type of input parameter and an external parameter, wherein the external parameter represents a parameter corresponding to a task to be processed other than the target task to be processed.

6. The method according to claim 1, characterized in that The method further comprises: Obtaining the total processing period of the target pending tasks; Determine the processing deadline of each of the subtasks according to the total processing deadline and the execution order of the subtasks; the sum of the processing deadlines of the subtasks is greater than or equal to the total processing deadline; Compare the processing deadline of each of the subtasks with the corresponding preset processing deadline, and select the subtasks whose processing deadline is greater than the preset processing deadline; Send reminder information to the subtasks that meet the preset conditions.

7. A process automation device, characterized in that: The device comprises: The acquisition module is used to obtain parameter information in the task application form; A task determination module, used to determine a target task to be processed according to the parameter information; A template process determination module, used to determine a corresponding template process according to the target task to be processed; the template process includes the execution order of the subtasks of the target task to be processed and the parameter transfer rules of each subtask; The execution module is used to execute each of the subtasks according to the parameter information, the execution order of the subtasks and the parameter transfer rule of each subtask until the last subtask is completed.

8. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 6 are implemented.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

10. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

Images