Workflow generation method and device, equipment, storage medium and product

By receiving task attribute data and using work scenario classification model and template recommendation model, workflow templates are automatically generated, which solves the problems of low efficiency and incorrect permission allocation of users' manual configuration of workflows in the existing technology, and realizes automated workflow management and Permission control improves the intelligence and adaptability of workflows.

CN118982223APending Publication Date: 2024-11-19SHANGHAI PUDONG DEVELOPMENT BANK
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411098500.3
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-08-12
Publication Date
2024-11-19

AI Technical Summary

Technical Problem

Existing workflow management tools require users to manually configure process steps, task assignments, and permission controls, resulting in inefficient and prone to data breaches or access permission assignment errors.

Method used

By receiving task attribute data, extracting task features, and using pre-trained work scenario classification model and template recommendation model, appropriate workflow templates are automatically generated, including workflow status information, steps and permission control rules, thereby generating the work of the target task. flow.

Benefits of technology

It realizes closed-loop management from receiving task attribute data to automatically generating workflows, automatically allocating permissions and controlling the flow of work items, reducing manual intervention, improving the intelligence and adaptability of workflows, and reducing the user's decision-making burden.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118982223A_ABST
    Figure CN118982223A_ABST
Patent Text Reader

Abstract

The embodiment of the invention relates to the technical field of computers, and provides a workflow generation method and device, equipment, a storage medium and a product. Performing feature extraction on the target task attribute data to obtain task features; inputting the task features into a pre-trained working scene classification model to obtain a workflow scene corresponding to the target task; determining a first workflow template of the target task according to the workflow scene and the attribute data of the target task, wherein the first workflow template comprises workflow state information, workflow steps and authority control rules; and generating a workflow of the target task according to the first workflow template and the attribute data of the target task. Through the embodiment of the invention, the appropriate workflow can be automatically generated for the user, and the intelligence and adaptability of the workflow are improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The embodiments of this specification relate to the field of computer technology, and in particular to a workflow generation method, apparatus, device, storage medium, and product. Background Art

[0002] Workflow refers to the sequence of activity flows of work items, a complete process completed by multiple departments, multiple positions, and multiple links through coordination and sequential work. With the development and popularization of computer technology and network technology, various types of enterprise and personal information applications have emerged in an endless stream, and workflow has also emerged. Workflow is the source of work efficiency. A good workflow can enable the healthy development of various business management tasks of an enterprise, thereby ensuring the efficient operation of the enterprise. Existing workflow management tools usually require users to manually configure workflows. However, during the configuration process, users need to define process steps, task allocation, permission control, etc. in detail. The management and maintenance of workflow permissions usually requires in-depth technical knowledge, which may be complicated and cumbersome for non-technical personnel, resulting in data leakage or incorrect access permission allocation. Therefore, there is an urgent need for a workflow generation method that can automatically generate workflows for users to reduce the decision-making burden of users. Summary of the invention

[0003] In view of the above-mentioned problems in the prior art, the purpose of the embodiments of this specification is to provide a workflow generation method, device, equipment, storage medium and product to solve the problem in the prior art that users manually configure workflows, which is inefficient and prone to data leakage or access rights allocation errors.

[0004] In order to solve the above technical problems, the specific technical solutions of the embodiments of this specification are as follows:

[0005] On the one hand, an embodiment of this specification provides a workflow generation method, the method comprising:

[0006] Receive target task attribute data;

[0007] Extracting features from the target task attribute data to obtain task features;

[0008] Inputting the task features into a pre-trained work scenario classification model to obtain a workflow scenario corresponding to the target task;

[0009] Determine a first workflow template for the target task according to the workflow scenario and the target task attribute data, wherein the first workflow template includes workflow transfer status information, workflow steps and authority control rules;

[0010] A workflow for the target task is generated according to the first workflow template and the target task attribute data.

[0011] Furthermore, the task characteristics include task type, task complexity, task urgency, task priority, resource requirements, relevant personnel information, authority control information and status flow rules.

[0012] Furthermore, the work scenario classification model is a decision tree model; the step of inputting the task features into a pre-trained work scenario classification model to obtain a workflow scenario corresponding to the target task includes:

[0013] Calculate the characteristic value of each of the task characteristics to obtain a characteristic value set;

[0014] Inputting the feature value set into the root node of the decision tree model;

[0015] Allocate each task feature to a corresponding child node according to the splitting rule and feature value set of the root node;

[0016] Repeat the above steps until a leaf node is reached, and use the scenario category corresponding to the leaf node as the workflow scenario corresponding to the target task.

[0017] Further, determining the first workflow template of the target task according to the workflow scenario and the target task attribute data includes:

[0018] The workflow scenario and target task attribute data are input into a pre-trained template recommendation model to obtain a first workflow template.

[0019] Further, the step of generating a workflow of a target task according to the first workflow template and the target task attribute data includes:

[0020] Determine the task nodes, the flow conditions between the task nodes, the flow logic between the task nodes and the steps included in the task nodes according to the workflow flow status information and the workflow steps;

[0021] Determine the relevant personnel and corresponding permissions for each task node according to the permission control rules;

[0022] The task nodes, the flow conditions between the task nodes, the flow logic between the task nodes, the necessary steps included in the task nodes, the personnel related to each of the task nodes and the corresponding permissions are used as placeholders in the first workflow template;

[0023] The task attribute data is mapped to the placeholder in the first workflow template to generate the workflow of the target task.

[0024] Furthermore, the method further comprises:

[0025] responding to a user workflow template adjustment instruction;

[0026] Generate workflow template configuration information according to the workflow template adjustment instruction;

[0027] Adjust the first workflow template according to the workflow template configuration information to obtain a second workflow template;

[0028] A workflow for the target task is generated according to the second workflow template and the target task attribute data.

[0029] Furthermore, the method further comprises:

[0030] Recording status change information during the automatic transfer of the target task;

[0031] According to the preset state anomaly detection rules, determine whether there is an anomaly in the state change information;

[0032] If so, an alarm notification is triggered and sent to the corresponding user terminal.

[0033] On the other hand, an embodiment of the present specification provides a workflow generation device, the device comprising:

[0034] A receiving module, used for receiving target task attribute data;

[0035] A feature extraction module is used to extract features from the target task attribute data to obtain task features;

[0036] A scenario confirmation module is used to input the task features into a pre-trained work scenario classification model to obtain a workflow scenario corresponding to the target task;

[0037] A template determination module, used to determine a first workflow template of the target task according to the workflow scenario and target task attribute data, wherein the first workflow template includes workflow transfer status information, workflow steps and authority control rules;

[0038] The workflow generation module is used to generate a workflow of a target task according to the first workflow template and target task attribute data.

[0039] On the other hand, an embodiment of the present specification further provides a computer device, including a memory, a processor, and a computer program stored in the memory, wherein when the computer program is executed by the processor, the instructions of any one of the above methods are executed.

[0040] On the other hand, an embodiment of the present specification further provides a computer-readable storage medium having a computer program stored thereon, wherein when the computer program is executed by a processor of a computer device, the computer program executes instructions of any one of the above-described methods.

[0041] On the other hand, the embodiments of this specification further provide a computer program product, which, when executed by a processor of a computer device, executes instructions of any one of the above methods.

[0042] By adopting the above technical scheme, the workflow generation method provided in the embodiment of this specification can realize closed-loop management from receiving task attribute data to automatically generating workflows. Through task feature extraction, workflow scenario classification, workflow template determination and workflow generation, it can flexibly respond to different types of tasks and generate appropriate workflows for them, thereby automatically allocating permissions and controlling the flow of work items, reducing the need for manual intervention, improving the intelligence and adaptability of workflows, and reducing the decision-making burden of users.

[0043] The above description is only an overview of the technical solutions of some embodiments of this specification. In order to more clearly understand the technical means of some embodiments of this specification, they can be implemented in accordance with the contents of the specification. In order to make the above and other purposes, features and advantages of the embodiments of this specification more obvious and easy to understand, the following specifically cites the preferred embodiments and describes them in detail in conjunction with the attached drawings. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0045] Figure 1 A schematic diagram of an implementation environment of a workflow generation method in some embodiments of this specification is shown;

[0046] Figure 2 A schematic diagram showing a flow chart of a workflow generation method in some embodiments of this specification;

[0047] Figure 3 A schematic diagram of a process for determining a workflow scenario corresponding to the target task in some embodiments of this specification is shown;

[0048] Figure 4 A schematic diagram of a process of generating a workflow of a target task according to the first workflow template and target task attribute data in some embodiments of this specification is shown;

[0049] Figure 5 A flowchart of another embodiment of a workflow generation method in this specification is shown;

[0050] Figure 6 A flowchart of another embodiment of a workflow generation method in this specification is shown;

[0051] Figure 7 A schematic diagram of the module structure of a workflow generation device in some embodiments of this specification is shown;

[0052] Figure 8 A schematic diagram of the structure of a computer device in this specification is shown.

[0053] Description of the accompanying symbols:

[0054] 101. Terminal;

[0055] 102. Server side;

[0056] 701, receiving module;

[0057] 702. Feature extraction module;

[0058] 703, scene confirmation module;

[0059] 704. Template determination module;

[0060] 705. Workflow generation module;

[0061] 802. Computer equipment;

[0062] 804, processor;

[0063] 806. Memory;

[0064] 808, driving mechanism;

[0065] 810, input / output module;

[0066] 812. Input device;

[0067] 814. Output device;

[0068] 816. Presentation equipment;

[0069] 818. Graphical user interface;

[0070] 820, network interface;

[0071] 822, communication link;

[0072] 824. Communication bus. DETAILED DESCRIPTION

[0073] The following will be combined with the drawings in the embodiments of this specification to clearly and completely describe the technical solutions in the embodiments of this specification. Obviously, the described embodiments are only part of the embodiments of this specification, not all of the embodiments. Based on the embodiments in this specification, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this specification.

[0074] It should be noted that the terms "first", "second", etc. in this specification and claims 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 interchanged where appropriate, so that the embodiments of this specification described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, device, product or equipment that includes 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 equipment.

[0075] like Figure 1 The figure shows a schematic diagram of an implementation environment of a workflow generation method according to an embodiment of the present specification, which may include: a terminal 101 and a server 102, wherein the terminal 101 and the server 102 communicate with each other through a network, and the network may include a local area network (LAN), a wide area network (WAN), the Internet or a combination thereof, and is connected to a website, a user device (such as a computing device) and a back-end system.

[0076] The terminal 101 is used for the user to input target task attribute data and workflow template adjustment instructions, and sends the target task attribute data and workflow template adjustment instructions to the server 102. In an optional embodiment, the terminal 101 may include but is not limited to electronic devices such as self-service terminal devices, desktop computers, tablet computers, laptop computers, smart wearable devices, etc. Optionally, the operating system running on the electronic device may include but is not limited to Android system, IOS system, Linux, Windows, etc. Of course, the terminal 101 is not limited to the above-mentioned electronic devices with a certain entity, and it can also be software running in the above-mentioned electronic devices.

[0077] The server end 102 can be used to receive target task attribute data; and to extract features from the target task attribute data to obtain task features; and to input the task features into a pre-trained work scenario classification model to obtain a workflow scenario corresponding to the target task; and to determine a first workflow template for the target task based on the workflow scenario and the target task attribute data, wherein the first workflow template includes workflow transfer status information, workflow steps and authority control rules; and to generate a workflow for the target task based on the first workflow template and the target task attribute data. Optionally, the server end 102 can be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, content distribution networks (CDNs), and big data and artificial intelligence platforms.

[0078] It should be noted that Figure 1 This is only one implementation environment of the workflow generation method provided in the embodiment of the present application. In practical applications, other implementation environments may also be included.

[0079] Figure 2 This is a flowchart of a workflow generation method provided in an embodiment of this specification. This specification provides method operation steps as described in the embodiment or flowchart, but may include more or fewer operation steps based on conventional or non-creative labor. The order of steps listed in the embodiment is only one way of executing the steps among many orders, and does not represent the only order of execution. When the actual system or device product is executed, it can be executed in the order of the method shown in the embodiment or the accompanying drawings or in parallel. Specifically, Figure 2 As shown, the method includes:

[0080] S201: receiving target task attribute data;

[0081] S202: Extracting features from the target task attribute data to obtain task features;

[0082] S203: Inputting the task features into a pre-trained work scenario classification model to obtain a workflow scenario corresponding to the target task;

[0083] S204: Determine a first workflow template for the target task according to the workflow scenario and the target task attribute data, wherein the first workflow template includes workflow transfer status information, workflow steps, and authority control rules;

[0084] S205: Generate a workflow for a target task according to the first workflow template and target task attribute data.

[0085] By adopting the above technical scheme, the workflow generation method provided in the embodiment of this specification can realize closed-loop management from receiving task attribute data to automatically generating workflows. Through task feature extraction, workflow scenario classification, workflow template determination and workflow generation, it can flexibly respond to different types of tasks and generate appropriate workflows for them, thereby automatically allocating permissions and controlling the flow of work items, reducing the need for manual intervention, improving the intelligence and adaptability of workflows, and reducing the decision-making burden of users.

[0086] In step S201, for example, the target task is a software development task, and its target task attribute data may include basic data such as task type, departments involved, required resources, estimated completion time, person in charge information, task name, task description, priority, deadline, etc., and also include authority control information, such as person in charge, approver, participant and authority level, etc., in addition to the project management mode, necessary steps, such as quality scanning, security scanning and auditing, etc. In some embodiments, in addition to being user input, the target task attribute data can also be obtained from a task book, a form submitted by a user, a database record or a project management requirement. For example, the user does not directly input the target task attribute data, but uploads the task book or task requirement book to the terminal, and then the target task attribute data can be obtained by extracting keywords from the task book. After receiving the target task attribute data, it is necessary to perform format conversion, data cleaning, association aggregation and other processing on the target task attribute data to convert it into data that meets the requirements, thereby providing support for subsequent data analysis and decision-making.

[0087] In step S202, feature extraction of target task attribute data includes: firstly selecting the features most relevant to the target task by methods such as chi-square test or correlation analysis, and then extracting task features using BERT or a neural network model. In some embodiments of this specification, task features include task type, task complexity, task urgency, task priority, resource requirements, relevant personnel information, authority control information, deadlines, and state flow rules.

[0088] In step S203, in the embodiment of this specification, the work scene classification model is a decision tree model; Figure 3 , the step of inputting the task features into a pre-trained work scenario classification model to obtain a workflow scenario corresponding to the target task includes:

[0089] S301: Calculate the feature value of each of the task features to obtain a feature value set;

[0090] S302: Inputting the feature value set into the root node of the decision tree model;

[0091] S303: Allocate each task feature to a corresponding child node according to the splitting rule and feature value set of the root node;

[0092] S304: Repeat step S303 until a leaf node is reached, and use the scenario category corresponding to the leaf node as the workflow scenario corresponding to the target task.

[0093] Specifically, task features mainly include discrete features and continuous features. For discrete features, such as task type, task urgency, etc., since they have their own classification attributes, they can be directly One-Hot encoded according to their classification attributes. For continuous features, such as deadlines, they need to be converted into discrete features first, and then One-Hot encoded, and the One-Hot encoded value of each task feature is used as its feature value. In step S302, the feature value set is input into a pre-built decision tree model, where the construction of the decision tree is a recursive process, starting from the root node, and continuously dividing the feature value set into smaller subsets until a certain stop condition (such as reaching the maximum depth) is met. At each node, the decision tree algorithm automatically evaluates all available features and selects an optimal feature for segmentation. The selection of the best feature is usually based on a purity metric (such as information gain, Gini impurity or gain rate), which measures the degree of purity improvement of the subset after the feature is used to segment the data set. According to the different values ​​of the best feature, the feature value set is divided into two or more subsets, each subset corresponds to a child node, and the above process is repeated for each child node until the stop condition is met. The node splitting rule is based on the selected best feature. For each feature, the decision tree algorithm considers all possible values ​​(or value ranges) and evaluates the purity improvement under each splitting method. When the decision tree is built, the feature value set of the task feature can be input into the decision tree model. Starting from the root node, the task feature corresponding to the root node is selected from the feature value set and split according to the splitting rule of the root node. The task feature is assigned to the corresponding child node, and the above process is repeated for the child node until a leaf node is reached. The leaf node contains a classification result. Therefore, the workflow scenario corresponding to the target task can be confirmed by the task feature and the pre-trained decision tree model. For example, when a task has high urgency and high priority, the workflow scenario of the task can be determined as a fast, simplified and responsive scenario; when a task has a general urgency and high priority, and has relevant data such as quality and safety, the workflow scenario of the task can be determined as a high-quality key work scenario.

[0094] In step S204, in some embodiments of this specification, determining the first workflow template of the target task according to the workflow scenario and the target task attribute data includes:

[0095] The workflow scenario and target task attribute data are input into a pre-trained template recommendation model to obtain a first workflow template.

[0096] Specifically, in the neural network model, a mapping relationship is established between the task attribute data and the workflow scenario and the corresponding workflow template. The input layer receives the task attribute data and the workflow scenario, the hidden layer performs feature extraction and pattern recognition, and the output layer gives the best workflow template. Through a large number of historical workflow templates and scenario corresponding training, the neural network model has the ability to automatically recommend suitable workflow templates. In practical applications, the trained decision tree and neural network model can be integrated into the workflow management system. When the system receives a new task, it automatically inputs the task attributes, first confirms the workflow scenario through the decision tree model, and then obtains the workflow template according to the workflow scenario and the neural network model. The workflow template contains the workflow status information, workflow steps and the authority control rules that meet the specifications. According to the authority control rules defined in the workflow template, the relevant permissions and access rights are automatically allocated and managed. For example, if a work is in progress and requires the participation of multiple approval work, the system can recommend a process template containing multiple approval links to reasonably plan the workflow situation.

[0097] In some embodiments of this specification, refer to Figure 4 , the step of generating a workflow of a target task according to the first workflow template and the target task attribute data includes:

[0098] S401: Determine the task nodes, the flow conditions between the task nodes, the flow logic between the task nodes and the steps included in the task nodes according to the workflow flow status information and the workflow steps;

[0099] S402: Determine the personnel and corresponding permissions of each task node according to the permission control rule;

[0100] S403: The task nodes, the flow conditions between the task nodes, the flow logic between the task nodes, the necessary steps included in the task nodes, the personnel related to each of the task nodes and the corresponding permissions are used as placeholders in the first workflow template;

[0101] S404: Map the task attribute data to the placeholder in the first workflow template to generate the workflow of the target task.

[0102] Specifically, the workflow state information includes the workflow state, the flow logic between states, the key activities that need to be performed during the state flow process, and the flow conditions (such as time and events). For example, the workflow states include "to be developed", "under development", "SIT test", etc. The flow logic between states is that the task flows from "to be developed" to "under development" and then to "SIT test", where there are also necessary activities such as branch merging and branch scanning from "under development" to "SIT test". The workflow steps include the specific steps contained in each state. Each workflow state is regarded as a task node. The steps contained in each task node can be determined according to the workflow steps. At the same time, the relevant personnel and corresponding access rights or management rights of each task node are determined according to the authority control rules. Thus, the placeholders in the workflow template can be determined, and the target task attribute data can be mapped to the placeholders in the workflow template, so as to obtain the workflow of the target task. After the workflow is determined, the relevant users only need to pay attention to and complete their own work. After the current work is completed or the state flow conditions are met, the work will automatically flow to the next appropriate state. For example, if a task needs to go through multiple approval stages, the system can automatically transfer the task to the next approver's task list according to predefined rules. Thus, automatic workflow generation can automatically allocate permissions and control the flow of work items, reducing the need for manual intervention and improving task flow efficiency.

[0103] In some embodiments of this specification, refer to Figure 5 , the workflow generation method further includes:

[0104] S501: responding to a user workflow template adjustment instruction;

[0105] S502: Generate workflow template configuration information according to the workflow template adjustment instruction;

[0106] S503: adjusting the first workflow template according to the workflow template configuration information to obtain a second workflow template;

[0107] S504: Generate a workflow for the target task according to the second workflow template and the target task attribute data.

[0108] It can be understood that if the first workflow template does not meet user needs, the user can initiate a workflow template adjustment instruction to adjust the placeholder information in the workflow template to obtain a second workflow template that meets the user's personalized needs. In this way, the workflow template can be adaptively adjusted to meet ever-changing business needs.

[0109] In some embodiments of this specification, refer to Figure 6 , the workflow generation method further includes:

[0110] S601: Recording status change information during the automatic transfer of the target task;

[0111] S602: judging whether there is an abnormality in the state change information according to a preset state abnormality detection rule;

[0112] S603: If yes, trigger an alarm notification, and send the alarm notification to the corresponding user terminal.

[0113] It can be understood that whenever the status of a job changes, the status information before and after the change is recorded and stored in the form of logs, including timestamps, executors, and reasons for status changes, to provide traceability and audit functions for job status changes. These log records can be used to track the evolution of job status and understand the processing of jobs in different states. At the same time, in order to help users optimize workflows and improve work efficiency, a visual interface can also be provided to display log records of job status changes. Users and managers can view specific log records through the interface and analyze and evaluate the status changes based on the recorded change information. This helps users understand the evolution of work and find potential improvement points, thereby providing support for decisions such as workflow optimization. By setting status anomaly detection rules and conditions, anomalies in job status changes are detected and alarm notifications are triggered. When an abnormal situation occurs, a notification is triggered to remind the relevant users or managers so that they can be processed and adjusted in a timely manner, thereby helping users avoid potential problems and delays and ensure the smooth progress of the workflow. For example, when it is detected that a job has stayed in the ongoing state for too long, exceeding the preset time range, an alarm notification is sent to the relevant person in charge for timely follow-up and resolution.

[0114] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties. And the acquisition, storage, use, and processing of data in the technical solutions described in the embodiments of this application are in compliance with relevant regulations.

[0115] Based on the workflow generation method described above, the embodiment of this specification also provides a workflow generation device. The device may include a system (including a distributed system), software (application), module, component, server, client, etc. using the method described in the embodiment of this specification and a device combined with necessary implementation hardware. Based on the same innovative concept, the device in one or more embodiments provided in the embodiment of this specification is as described in the following embodiments. Since the implementation scheme and method of the device to solve the problem are similar, the implementation of the specific device in the embodiment of this specification can refer to the implementation of the aforementioned method, and the repetitions will not be repeated. As used below, the term "unit" or "module" can implement a combination of software and / or hardware of predetermined functions. Although the device described in the following embodiments is preferably implemented in software, the implementation of hardware, or a combination of software and hardware, is also possible and conceived.

[0116] Specifically, Figure 7 This is a schematic diagram of the module structure of an embodiment of a workflow generation device provided in the embodiment of this specification, referring to Figure 7 As shown, a workflow generation device provided in an embodiment of this specification includes:

[0117] Receiving module 701, used to receive target task attribute data;

[0118] A feature extraction module 702 is used to extract features from the target task attribute data to obtain task features;

[0119] A scenario confirmation module 703 is used to input the task features into a pre-trained work scenario classification model to obtain a workflow scenario corresponding to the target task;

[0120] A template determination module 704 is used to determine a first workflow template for the target task according to the workflow scenario and the target task attribute data, wherein the first workflow template includes workflow transfer status information, workflow steps and authority control rules;

[0121] The workflow generation module 705 is used to generate a workflow of a target task according to the first workflow template and target task attribute data.

[0122] The beneficial effects obtained by the device provided in the embodiments of this specification are consistent with the beneficial effects obtained by the above method and will not be repeated here.

[0123] Reference Figure 8As shown, based on the workflow generation method described above, a computer device 802 is also provided in an embodiment of the specification, wherein the method is run on the computer device 802. The computer device 802 may include one or more processors 804, such as one or more central processing units (CPUs), each of which may implement one or more hardware threads. The computer device 802 may also include any memory 806, which is used to store any kind of information such as code, settings, data, etc. Non-limitingly, for example, the memory 806 may include any one or more combinations of the following: any type of RAM, any type of ROM, flash memory device, hard disk, optical disk, etc. More generally, any memory may use any technology to store information. Further, any memory may provide volatile or non-volatile retention of information. Further, any memory may represent a fixed or removable component of the computer device 802. In one case, when the processor 804 executes an associated instruction stored in any memory or a combination of memories, the computer device 802 may perform any operation of the associated instruction. The computer device 802 also includes one or more drive mechanisms 808 for interacting with any storage, such as a hard disk drive mechanism, an optical disk drive mechanism, etc.

[0124] The computer device 802 may also include an input / output module 810 (I / O) for receiving various inputs (via input devices 812) and for providing various outputs (via output devices 814). A specific output mechanism may include a presentation device 816 and an associated graphical user interface (GUI) 818. In other embodiments, the input / output module 810 (I / O), the input device 812, and the output device 814 may not be included, and the computer device 802 may be used as a computer device in a network. The computer device 802 may also include one or more network interfaces 820 for exchanging data with other devices via one or more communication links 822. One or more communication buses 824 couple the components described above together.

[0125] The communication link 822 may be implemented in any manner, for example, through a local area network, a wide area network (e.g., the Internet), a point-to-point connection, etc., or any combination thereof. The communication link 822 may include any combination of hardwired links, wireless links, routers, gateway functions, name servers, etc. governed by any protocol or combination of protocols.

[0126] Corresponding to Figures 1 to 6 In addition to the method shown, an embodiment of the specification also provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the steps of the above method are executed.

[0127] The embodiment of the present specification also provides a computer-readable instruction, wherein when the processor executes the instruction, the program therein causes the processor to execute the following Figures 1 to 6 The method shown.

[0128] The embodiments of the present specification also provide a computer program product, including at least one instruction or at least one program, wherein the at least one instruction or the at least one program is loaded and executed by a processor to implement the following Figures 1 to 6 The method shown.

[0129] It should be understood that in the various embodiments of this specification, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this specification.

[0130] It should also be understood that in the embodiments of this specification, the term "and / or" is only a description of the association relationship of the associated objects, indicating that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this specification generally indicates that the associated objects before and after are in an "or" relationship.

[0131] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed in this specification can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in the above description according to function. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this specification.

[0132] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0133] In the several embodiments provided in this specification, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, or it can be an electrical, mechanical or other form of connection.

[0134] 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 on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the embodiments of this specification.

[0135] In addition, each functional unit in each embodiment of this specification 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 integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0136] 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 this specification is essentially 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, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of this specification. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk and other media that can store program codes.

[0137] Specific embodiments are used in this specification to illustrate the principles and implementation methods of this specification. The description of the above embodiments is only used to help understand the methods and core ideas of this specification. At the same time, for those skilled in the art, according to the ideas of this specification, there will be changes in the specific implementation methods and application scope. In summary, the content of this specification should not be understood as a limitation on this specification.

Claims

1. A workflow generation method, characterized in that: The method comprises: Receive target task attribute data; Extracting features from the target task attribute data to obtain task features; Inputting the task features into a pre-trained work scenario classification model to obtain a workflow scenario corresponding to the target task; Determine a first workflow template for the target task according to the workflow scenario and the target task attribute data, wherein the first workflow template includes workflow transfer status information, workflow steps and authority control rules; A workflow for the target task is generated according to the first workflow template and the target task attribute data.

2. The method according to claim 1, characterized in that The task characteristics include task type, task complexity, task urgency, task priority, resource requirements, relevant personnel information, authority control information and status flow rules.

3. The method according to claim 1, characterized in that: The work scene classification model is a decision tree model; the task feature is input into a pre-trained work scene classification model to obtain a workflow scene corresponding to the target task, including: Calculate the characteristic value of each of the task characteristics to obtain a characteristic value set; Inputting the feature value set into the root node of the decision tree model; Allocate each task feature to a corresponding child node according to the splitting rule and feature value set of the root node; Repeat the above steps until a leaf node is reached, and use the scenario category corresponding to the leaf node as the workflow scenario corresponding to the target task.

4. The method according to claim 1, characterized in that: The step of determining the first workflow template of the target task according to the workflow scenario and the target task attribute data includes: The workflow scenario and target task attribute data are input into a pre-trained template recommendation model to obtain a first workflow template.

5. The method according to claim 1, characterized in that The step of generating a workflow of a target task according to the first workflow template and the target task attribute data includes: Determine the task nodes, the flow conditions between the task nodes, the flow logic between the task nodes and the steps included in the task nodes according to the workflow flow status information and the workflow steps; Determine the relevant personnel and corresponding permissions for each task node according to the permission control rules; The task nodes, the flow conditions between the task nodes, the flow logic between the task nodes, the necessary steps included in the task nodes, the personnel related to each of the task nodes and the corresponding permissions are used as placeholders in the first workflow template; The task attribute data is mapped to the placeholder in the first workflow template to generate the workflow of the target task.

6. The method according to claim 1, characterized in that The method further comprises: responding to a user workflow template adjustment instruction; Generate workflow template configuration information according to the workflow template adjustment instruction; Adjust the first workflow template according to the workflow template configuration information to obtain a second workflow template; A workflow for the target task is generated according to the second workflow template and the target task attribute data.

7. The method according to claim 1, characterized in that The method further comprises: Recording status change information during the automatic transfer of the target task; According to the preset state anomaly detection rules, determine whether there is an anomaly in the state change information; If so, an alarm notification is triggered and sent to the corresponding user terminal.

8. A workflow generation device, characterized in that: The device comprises: A receiving module, used for receiving target task attribute data; A feature extraction module is used to extract features from the target task attribute data to obtain task features; A scenario confirmation module is used to input the task features into a pre-trained work scenario classification model to obtain a workflow scenario corresponding to the target task; A template determination module, used to determine a first workflow template of the target task according to the workflow scenario and target task attribute data, wherein the first workflow template includes workflow transfer status information, workflow steps and authority control rules; The workflow generation module is used to generate a workflow of a target task according to the first workflow template and target task attribute data.

9. A computer device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the method according to any one of claims 1 to 7 is implemented.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method according to any one of claims 1 to 7 is implemented.

11. A computer program product, characterized in that The method comprises at least one instruction or at least one program, wherein the at least one instruction or the at least one program is loaded and executed by a processor to implement the method according to any one of claims 1 to 7.