CN113298331A - Work order processing method, device and system and electronic equipment - Google Patents
Work order processing method, device and system and electronic equipment Download PDFInfo
- Publication number
- CN113298331A CN113298331A CN202010109026.5A CN202010109026A CN113298331A CN 113298331 A CN113298331 A CN 113298331A CN 202010109026 A CN202010109026 A CN 202010109026A CN 113298331 A CN113298331 A CN 113298331A
- Authority
- CN
- China
- Prior art keywords
- work order
- workflow
- task
- meta
- scheduling system
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000003672 processing method Methods 0.000 title claims abstract description 16
- 238000000034 method Methods 0.000 claims abstract description 42
- 238000004891 communication Methods 0.000 claims abstract description 29
- 230000006978 adaptation Effects 0.000 claims description 40
- 238000004590 computer program Methods 0.000 claims description 12
- 230000008569 process Effects 0.000 abstract description 17
- 238000007726 management method Methods 0.000 description 45
- 230000003044 adaptive effect Effects 0.000 description 5
- 238000010586 diagram Methods 0.000 description 5
- 230000006870 function Effects 0.000 description 5
- 230000009471 action Effects 0.000 description 4
- 238000006243 chemical reaction Methods 0.000 description 3
- 238000003491 array Methods 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
- 230000002123 temporal effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/063—Operations research, analysis or management
- G06Q10/0631—Resource planning, allocation, distributing or scheduling for enterprises or organisations
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/103—Workflow collaboration or project management
Abstract
The embodiment of the application provides a work order processing method, a work order processing device, a work order processing system and electronic equipment. The method is applied to a work order management end; the work order management end establishes communication with a target scheduling system in advance, and the target scheduling system is a task scheduling system serving as a work order receiving party; the method comprises the following steps: acquiring workflow description information of a workflow to be processed as target description information from a predefined information base containing the workflow description information, wherein each workflow description information is used for describing each meta-task indicated by the workflow and the dependency relationship of each meta-task; generating a workflow work order in a target data form by using the target description information, wherein the workflow work order is used as a work order to be issued; and sending the work order to be issued to a target scheduling system, enabling the target scheduling system to receive the work order to be issued, and sequentially executing each meta-task indicated by the work order to be issued to obtain an execution result. Through the scheme, the complexity of the task scheduling process can be reduced.
Description
Technical Field
The present application relates to the field of task scheduling technologies, and in particular, to a work order processing method, apparatus, system, and electronic device.
Background
In the task scheduling process, a scheduling node in the task scheduling system dispatches each meta-task indicated by the workflow work order to the task processing equipment according to the workflow work order, and further, the task processing equipment realizes the processing of the meta-task. The workflow work order records a plurality of meta-tasks and the dependency relationship among the meta-tasks. The task processing device may be a device in the task scheduling system, or may be a device for executing a task associated with the task scheduling system.
In the related art, the workflow work order processed by the task scheduling system is extracted from the database associated with the task scheduling system, and the workflow work order in the associated database is defined according to the data format recognized by the task scheduling system.
The inventor finds that the related art has at least the following problems in the process of implementing the application:
because the workflow work order is predefined according to the data form that the task scheduling system can recognize, if the task scheduling system switches, the workflow must be defined again by setting the workflow for the same workflow, so as to adapt to a new task scheduling system, which undoubtedly makes the task scheduling process more cumbersome.
Disclosure of Invention
An object of the embodiments of the present application is to provide a work order processing method, device, system and electronic device, so as to solve the problem of high complexity in a task scheduling process in the related art. The specific technical scheme is as follows:
in a first aspect, an embodiment of the present application provides a work order processing method, which is applied to a work order management end; the work order management end establishes communication with a target scheduling system in advance, and the target scheduling system is a task scheduling system serving as a work order receiving party; the method comprises the following steps:
acquiring workflow description information of a workflow to be processed as target description information from a predefined information base containing the workflow description information, wherein each workflow description information is used for describing each meta-task indicated by the workflow and the dependency relationship of each meta-task;
generating a workflow work order in a target data form by using the target description information, wherein the workflow work order is used as a work order to be issued; the target data form is a data form of a work order which can be identified by the target scheduling system;
and sending the work order to be issued to the target scheduling system, enabling the target scheduling system to receive the work order to be issued, and sequentially executing each meta-task indicated by the work order to be issued to obtain an execution result.
Optionally, the method further comprises:
and generating workflow description information of any workflow so as to store the workflow description information to the information base.
Optionally, the generating workflow description information of any workflow includes:
displaying an information editing interface for a user to edit; the information editing interface displays identification information of a plurality of meta tasks in a preset database;
acquiring task combination information which is set in the information editing interface by the user and aims at a workflow, wherein the task combination information comprises identification information selected by the user and a dependency relationship set for the selected identification information;
and taking the meta-task indicated by the identification information in the task combination information as a meta-task required to be described by the to-be-generated workflow description information, and taking the dependency relationship in the task combination information as a dependency relationship required to be described by the to-be-generated workflow description information to generate the to-be-generated workflow description information.
Optionally, the display information editing interface includes:
determining a first type meta-task which the user has available authority from a plurality of first type meta-tasks in a predetermined database; the first type of meta-task belongs to a local mode;
and displaying the information editing interface which takes the determined first type of meta-tasks and second type of meta-tasks as display elements, wherein the second type of meta-tasks are meta-tasks belonging to a global mode in the preset database.
Optionally, the generating a workflow work order in a target data form by using the target description information as a work order to be issued includes:
determining an adaptation module matched with the target scheduling system; each task scheduling system corresponds to one adaptation module;
and transmitting the target description information to an adaptation module matched with the target scheduling system, so that the adaptation module matched with the target scheduling system generates a workflow work order in a target data form by using the target description information.
Optionally, before the sending the work order to be issued to the target scheduling system, the method further includes:
marking a work order type for the work order to be issued, wherein the work order type is a global type or a non-global type;
correspondingly, after the target scheduling system sequentially executes each meta-task indicated by the work order to be issued and obtains an execution result, if the work order type of the work order to be issued is a global type, the execution result of each meta-task of the work order to be issued is stored in a specified shared area, and if the work order type of the work order to be issued is a non-global type, the execution result of each meta-task indicated by the work order to be issued is stored in a specified special area.
In a second aspect, an embodiment of the present application provides a work order processing system, including: the work order management terminal and the target scheduling system; the target scheduling system is a task scheduling party serving as a work order receiving party, and the work order management end establishes communication with the target scheduling system in advance;
the work order management end is used for acquiring the workflow description information of the workflow to be processed from a predefined information base containing the workflow description information as target description information, wherein each workflow description information is used for describing each meta-task indicated by the workflow and the dependency relationship of each meta-task; generating a workflow work order in a target data form by using the target description information, wherein the workflow work order is used as a work order to be issued; the target data form is a data form of a work order which can be identified by the target scheduling system; sending the work order to be issued to the target scheduling system;
and the target scheduling system is used for receiving the work order to be issued sent by the work order management end and sequentially executing each meta-task indicated by the work order to be issued to obtain an execution result.
In a third aspect, an embodiment of the present application provides a work order processing apparatus, which is applied to a work order management end; the work order management end establishes communication with a target scheduling system in advance, and the target scheduling system is a task scheduling system serving as a work order receiving party; the device comprises:
the system comprises an acquisition module, a processing module and a processing module, wherein the acquisition module is used for acquiring workflow description information of a workflow to be processed from a predefined information base containing the workflow description information as target description information, and each workflow description information is used for describing each meta-task indicated by the workflow and the dependency relationship of each meta-task;
the generating module is used for generating a workflow work order in a target data form by using the target description information, and the workflow work order is used as a work order to be issued; the target data form is a data form of a work order which can be identified by the target scheduling system;
and the sending module is used for sending the work order to be issued to the target scheduling system, so that the target scheduling system receives the work order to be issued and sequentially executes each element task indicated by the work order to be issued to obtain an execution result.
Optionally, the apparatus further comprises:
and the description information generation module is used for generating the workflow description information of any workflow so as to store the workflow description information to the information base.
Optionally, the description information generating module is specifically configured to:
displaying an information editing interface for a user to edit; the information editing interface displays identification information of a plurality of meta tasks in a preset database;
acquiring task combination information which is set in the information editing interface by the user and aims at a workflow, wherein the task combination information comprises identification information selected by the user and a dependency relationship set for the selected identification information;
and taking the meta-task indicated by the identification information in the task combination information as a meta-task required to be described by the to-be-generated workflow description information, and taking the dependency relationship in the task combination information as a dependency relationship required to be described by the to-be-generated workflow description information to generate the to-be-generated workflow description information.
Optionally, the description information generating module displays an information editing interface, including:
determining a first type meta-task which the user has available authority from a plurality of first type meta-tasks in a predetermined database; the first type of meta-task belongs to a local mode;
and displaying the information editing interface which takes the determined first type of meta-tasks and second type of meta-tasks as display elements, wherein the second type of meta-tasks are meta-tasks belonging to a global mode in the preset database.
Optionally, the generating module is specifically configured to:
determining an adaptation module matched with the target scheduling system; each task scheduling system corresponds to one adaptation module;
and transmitting the target description information to an adaptation module matched with the target scheduling system, so that the adaptation module matched with the target scheduling system generates a workflow work order in a target data form by using the target description information, and the workflow work order serves as a work order to be issued.
Optionally, the apparatus further comprises:
the marking module is used for marking the type of the work order to be issued before the sending module sends the work order to be issued to the target scheduling system, wherein the type of the work order is a global type or a non-global type;
correspondingly, after the target scheduling system sequentially executes each meta-task indicated by the work order to be issued and obtains an execution result, if the work order type of the work order to be issued is a global type, the execution result of each meta-task of the work order to be issued is stored in a specified shared area, and if the work order type of the work order to be issued is a non-global type, the execution result of each meta-task indicated by the work order to be issued is stored in a specified special area.
In a fourth aspect, an embodiment of the present application provides an electronic device, including a processor, a communication interface, a memory, and a communication bus, where the processor and the communication interface complete communication between the memory and the processor through the communication bus;
a memory for storing a computer program;
and the processor is used for realizing the steps of the work order processing method provided by the first aspect when executing the program stored in the memory.
In a fifth aspect, an embodiment of the present application provides a computer-readable storage medium, where a computer program is stored in the computer-readable storage medium, and when the computer program is executed by a processor, the steps of the work order processing method provided in the first aspect are implemented.
In the scheme provided by the embodiment of the application, the work order management end is additionally arranged, and the work order management end issues the workflow work order to the task scheduling system, so that the definition limitation caused by directly defining the work order in the scheduling system is avoided; moreover, the workflow description information is preset instead of the workflow work order, and the data universality is ensured. Therefore, when the dispatching system is switched, the work order management end only needs to generate the workflow work order in the data form matched with the dispatching system switched to currently by using the workflow description information, and repeated setting of the same workflow is avoided. Therefore, through the scheme, the complexity of the task scheduling process can be reduced.
Of course, not all advantages described above need to be achieved at the same time in the practice of any one product or method of the present application.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
Fig. 1 is a flowchart of a work order processing method according to an embodiment of the present disclosure;
FIG. 2 is a flowchart of a manner of generating workflow description information provided by an embodiment of the present application;
FIG. 3 is a diagram illustrating a matching relationship between each adaptation module and a corresponding scheduling system in a work order management end;
fig. 4 is a schematic structural diagram of a work order processing apparatus according to an embodiment of the present disclosure;
fig. 5 is a schematic structural diagram of a work order processing system according to an embodiment of the present disclosure;
fig. 6 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
In the related art, in the task scheduling process, a scheduling node in a task scheduling system dispatches each meta-task indicated by a workflow work order to task processing equipment according to the predefined workflow work order, and further, the task processing equipment realizes the processing of the meta-task. The workflow work order records a plurality of meta-tasks and the dependency relationship among the meta-tasks. The task processing device may be a device in the task scheduling system, or may be a device for executing a task associated with the task scheduling system. For example: for an Apache AirFlow scheduling system, the data form of a workflow work order is a DAG (directed acyclic graph), that is, each meta-task forming a workflow and the dependency relationship of each meta-task are described by the directed acyclic graph; correspondingly, the scheduling node dispatches tasks to all working nodes in the scheduling system according to a pre-defined DAG (directed acyclic graph), and then each working node realizes the processing of the meta-tasks. Another example is: for an Apache Oozie scheduling system, the data form of a workflow work order is a workflow.xml file, wherein in the workflow.xml file, start and stop element tasks and execution logic of a workflow are described through actions such as start, end, kill, for and join, namely, the dependency relationship of each element task and each element task forming the workflow is described; correspondingly, dispatching nodes dispatch tasks to the YARN nodes of the Hadoop big data cluster associated with the dispatching system according to predefined workflow.
The inventor finds that the related art has at least the following problems in the process of implementing the application:
because the workflow work order is predefined according to the data form that the task scheduling system can recognize, if the task scheduling system switches, the workflow work order must be defined by setting the workflow again for the same workflow, so as to adapt to a new scheduling system, which undoubtedly makes the task scheduling process more cumbersome. Still taking the above-mentioned Apache AirFlow scheduling system and Apache Oozie scheduling system as an example, if switching from the Apache AirFlow scheduling system to the Apache Oozie scheduling system, a DAG (directed acyclic graph) cannot be applied to the Apache Oozie, and a workflow represented by the DAG (directed acyclic graph) must be reset in the Apache Oozie to define a workflow.
In order to solve the problems in the related art, embodiments of the present application provide a work order processing method, system, device and electronic device.
First, a work order processing method provided in the embodiment of the present application is described below.
The execution main body of the work order processing method provided by the embodiment of the application can be a work order management end. In a specific Application, the work order management end may be an APP (Application) or a web client for implementing workflow work order processing, which is reasonable. It is understood that the workflow work order is a work document recorded with the workflow, and the workflow includes a plurality of meta-tasks and a plurality of dependencies of the meta-tasks.
And the work order management end establishes communication with a target scheduling system in advance so that the work order management end can send the workflow work order to the target scheduling system, and the target scheduling system is a task scheduling system serving as a work order receiving party. It can be understood that when the scheduling system is switched, the task scheduling system as the work order receiver is changed, and at this time, the task scheduling system connected to the work order management end is also changed.
In addition, in order to solve the technical problem of the related art, in addition to the addition of the work order management end, an information base including workflow description information is defined in advance, and each workflow description information is used for describing each meta task indicated by a workflow and the dependency relationship of each meta task. It can be understood that the workflow description information is only information for describing the workflow and does not belong to any work order data form, so that the data universality can be ensured.
In a particular application, the workflow description information may include, but is not limited to: the identification of each meta-task, and the dependency of each meta-task. The event dependency relationship may also be referred to as a relationship between a parent task and a child task, and the child task is executed after the parent task is executed. In addition, the dependency may include a temporal dependency, i.e., a starting meta-task in a workflow is executed at a certain point in time, in addition to an event dependency. Wherein, the meta-task is the smallest task unit, and the task data of the meta-task may include: task item information, the task item information is used for indicating what things to do, and correspondingly, the task data of the meta task can indicate what things to do; of course, the task data of the meta-task may include, in addition to the task item information: identification information of the tool program required to process the meta-task, at which point the task data of the meta-task may indicate which things to do with which tools. Wherein, the tool program can be: the data content of the specific meta task is not limited by the programming tools corresponding to the programming languages of Phthon, java, shell and the like.
Moreover, each piece of workflow description information can be named through the flow identification of the described workflow, so that when any flow identification is obtained, the flow identification can be used as a query basis to search the workflow description information of the workflow with the flow identification from the information base. In addition, the storage format of the workflow description information is not limited herein, for example: the workflow description information is stored in the form of a text document, or in the form of a list, or the like.
As shown in fig. 1, a work order processing method provided in the embodiment of the present application may include the following steps:
s101, acquiring workflow description information of a workflow to be processed from a predefined information base containing the workflow description information as target description information;
in a specific application, the work order management end may execute S101 when detecting that a predetermined sending condition is satisfied. The predetermined sending condition may include, but is not limited to: reaching a predetermined point in time, or receiving a predetermined send instruction, etc.
Also, the number of workflows to be processed may be one or more. In addition, the pending workflow may be specified manually, for example: and outputting an interface containing the identification of each workflow to a manager, and further, selecting the identification by the manager through the interface and submitting the identification to the work order management end, so that the work order management end can know the workflow to be processed. Of course, the determination method of the pending workflow may further include: it is also reasonable that the work order management end determines the workflow which needs to be sent at the current time based on the preset corresponding relation between the workflow and the sending time range, so as to obtain the workflow to be processed.
It is understood that, before S101, the work order management end may generate the workflow description information of any workflow, so as to store the workflow description information in the information base. Thus, one or more workflow description information may be present in the information repository. For clarity of the scheme and clarity of layout, a specific implementation manner of generating the workflow description information of any workflow is introduced in the following. S102, generating a workflow work order in a target data form by using the target description information, wherein the workflow work order is used as a work order to be issued; the target data form is a data form of a work order which can be identified by the target scheduling system;
after the workflow description information of the workflow to be processed is acquired, in order to enable a target scheduling system as a work order receiver to identify the work order, the work order management end may generate the workflow work order, which has a target data form and is related to the workflow described by the target description information, as the work order to be issued by using the target description information, that is, the acquired workflow description information.
For example, if the task scheduling system as the work order receiver is an Apache air flow scheduling system, and the target data form is a DAG (directed acyclic graph) form, the target description information may be used to generate a workflow work order pertaining to the workflow described by the target description information in the form of a DAG (directed acyclic graph).
For example, if the task scheduling system as the work order receiver is Apache Oozie scheduling system, and the target data is in the form of a workflow.
It should be noted that there are various specific implementation manners for generating the workflow work order in the form of the target data by using the target description information. Optionally, in an implementation manner, generating a workflow work order in the form of target data by using the target description information, where the work order serving as a to-be-issued work order may include:
determining an adaptation module matched with the target scheduling system; each task scheduling system corresponds to one adaptation module;
and transmitting the target description information to an adaptation module matched with the target scheduling system, so that the adaptation module matched with the target scheduling system generates a workflow work order in a target data form by using the target description information, and the workflow work order is used as a work order to be issued.
In this implementation, the adaptation module matching the target scheduling system may be determined from adaptation modules set for a plurality of task scheduling systems in advance. It can be understood that a plurality of adaptation modules with adaptation functions are preset, and each adaptation module is used for converting any workflow description information into: and the workflow work order is matched with the task scheduling system corresponding to the adaptation module in a data form. In addition, it should be noted that any adaptation module is a program module having an information conversion function, where the information conversion function of the program module is: specifically, the information conversion function of the program module is: and converting the workflow description information into a workflow work order in a data form matched with the task scheduling system corresponding to the adaptation module.
The adaptation modules set for the plurality of task scheduling systems may be arranged inside the work order management end or outside the work order management end, which is reasonable.
For convenience of understanding, fig. 3 exemplarily shows a matching relationship diagram between each adaptation module in the work order management end and the corresponding scheduling system. As shown in fig. 3, the work order management end includes three adaptation modules, which are respectively: the adaptive module corresponding to the Apache AirFlow scheduling system, the adaptive module corresponding to the Apache Oozie scheduling system and the adaptive modules corresponding to other scheduling systems, so that when the target scheduling system is the Apache AirFlow scheduling system, the adaptive module corresponding to the Apache AirFlow scheduling system can be used, the target scheduling system is the Apache Oozie scheduling system, the adaptive module corresponding to the Apache Oozie scheduling system can be used, and when the target scheduling system is the other scheduling systems, the adapters corresponding to the other scheduling systems can be used. The other scheduling system may be any scheduling system other than the Apache AirFlow scheduling system and the Apache Oozie scheduling system, which is not limited herein.
The above-mentioned specific implementation manner of generating the workflow work order in the form of target data about the workflow described by the target description information by using the target description information is merely an example, and should not be construed as a limitation to the embodiments of the present application.
S103, sending the work order to be issued to the target scheduling system, enabling the target scheduling system to receive the work order to be issued, and sequentially executing each element task indicated by the work order to be issued to obtain an execution result.
After the work order to be issued is obtained, the work order to be issued can be sent to the target scheduling system, and correspondingly, the target scheduling system can receive the work order to be issued and sequentially execute each element task indicated by the work order to be issued to obtain an execution result.
The target scheduling system sequentially executes each meta-task indicated by the to-be-issued work order, and the execution result obtained may specifically be: and dispatching each meta-task indicated by the work order to be issued to the task processing equipment by the dispatching node in the target dispatching system according to the work order to be issued, and further, realizing the processing of the meta-task by the task processing equipment to obtain an execution result. The task processing device may be a device in the task scheduling system, or may be a device associated with the task scheduling system for executing a task.
For example, for an Apache AirFlow scheduling system, after receiving the to-be-issued work order, the scheduling node may dispatch a task to each work node in the Apache AirFlow scheduling system, and then each work node implements processing on a meta-task to obtain an execution result. Another example is: for the Apache Oozie scheduling system, after receiving the work order to be issued, the scheduling node may dispatch a task to a Hadoop big data cluster YARN node associated with the Apache Oozie scheduling system, and then the YARN node may process the meta-task to obtain an execution result.
In the scheme provided by the embodiment of the application, the work order management end is additionally arranged, and the work order management end issues the workflow work order to the task scheduling system, so that the definition limitation caused by directly defining the work order in the scheduling system is avoided; moreover, the workflow description information is preset instead of the workflow work order, and the data universality is ensured. Therefore, when the dispatching system is switched, the work order management end only needs to generate the workflow work order in the data form matched with the dispatching system switched to currently by using the workflow description information, and repeated setting of the same workflow is avoided. Therefore, through the scheme, the complexity of the task scheduling process can be reduced.
It should be noted that there are many ways to generate any workflow description information. The manner in which any workflow description information is generated is illustratively described below.
As shown in fig. 2, generating the workflow description information of any workflow may include:
s201, displaying an information editing interface for a user to edit; the information editing interface displays identification information of a plurality of meta tasks in a preset database;
s202, acquiring task combination information which is set in the information editing interface by the user and aims at a workflow, wherein the task combination information comprises identification information selected by the user and a dependency relationship set for the selected identification information;
the user sets the task combination information aiming at the workflow in the information editing interface in various ways.
Optionally, in an implementation manner, after the information editing interface is displayed, a user may select, in a click manner, identification information of each meta-task required by a workflow, and add identification information of a meta-task belonging to a parent task to the selected identification information, so as to give a dependency relationship of the meta-task.
Optionally, in another implementation manner, after the information editing interface is displayed, a user may drag identification information of each meta task required by a workflow to a specified editing region of the information editing interface in a dragging manner, and establish a dependency relationship for each identification information in the specified editing region by setting arrows between the identification information, where a tail end of the arrow is connected to the meta task belonging to the parent task, and a head end of the arrow is connected to the meta task belonging to the child task.
It will be appreciated that for a set of parent tasks and child tasks, the child tasks are dependent on the execution of the parent task for execution.
And S203, taking the meta-task indicated by the identification information in the task combination information as the meta-task required to be described by the workflow description information to be generated, and taking the dependency relationship in the task combination information as the dependency relationship required to be described by the workflow description information to be generated to generate the workflow description information to be generated.
After the execution is finished in S202, when the workflow description information is generated, the related information in the task combination information, specifically, the meta-task indicated by the identification information in the task combination information may be used as the meta-task that needs to be described by the workflow description information to be generated, and the dependency relationship in the task combination information may be used as the dependency relationship that needs to be described by the workflow description information to be generated. Thus, workflow description information of the workflow indicated by the task combination information is generated.
In addition, since the predetermined database may be used by a plurality of users, and the respective meta-tasks in the predetermined database may not be available for each user, the respective meta-tasks in the predetermined database may be divided into the first type meta-task and the second type meta-task. The first type of meta-task is a meta-task belonging to a local mode, that is, the first type of meta-task is only available for some users and not available for other users; the second type of meta-task is a meta-task belonging to the global mode, that is, the second type of meta-task is disclosed to all users. For this case, displaying the information editing interface may include:
determining a first type meta-task which the user has available authority from a plurality of first type meta-tasks in a predetermined database; the first type of meta-task belongs to a local mode;
and displaying the information editing interface which takes the determined first type of meta-tasks and second type of meta-tasks as display elements, wherein the second type of meta-tasks are meta-tasks belonging to a global mode in the preset database.
In addition, optionally, before the sending the to-be-issued work order to the task scheduling system, the method may further include:
marking a work order type for the work order to be issued, wherein the work order type is a global type or a non-global type;
correspondingly, the target scheduling system executes each element task indicated by the work order to be issued in sequence, after an execution result is obtained, if the work order type of the work order to be issued is a global type, the execution result of each element task of the work order to be issued is stored in a specified shared area, and if the work order type of the work order to be issued is a non-global type, the execution result of each element task indicated by the work order to be issued is stored in a specified special area.
By setting a global type or a non-global type for the work order to be issued, the accessible range of the execution result of each element task of the work order to be issued can be specified.
Moreover, when the type of the work order is marked for the work order to be issued, the work order can be manually given according to the actual situation; of course, it is not limited thereto.
Corresponding to the method embodiment, the embodiment of the application also provides a work order processing device, and the work order processing device is applied to a work order management end; the work order management end establishes communication with a target scheduling system in advance, and the target scheduling system is a task scheduling system serving as a work order receiving end. As shown in fig. 4, the work order processing apparatus may include:
an obtaining module 410, configured to obtain workflow description information of a to-be-processed workflow from a predefined information base including workflow description information, as target description information, where each workflow description information is information used to describe each meta-task indicated by a workflow and a dependency relationship of each meta-task;
a generating module 420, configured to generate a workflow work order in the form of target data as a work order to be issued by using the target description information; the target data form is a data form of a work order which can be identified by the target scheduling system;
a sending module 430, configured to send the work order to be issued to the target scheduling system.
In the scheme provided by the embodiment of the application, the work order management end is additionally arranged, and the work order management end issues the workflow work order to the task scheduling system, so that the definition limitation caused by directly defining the work order in the scheduling system is avoided; moreover, the workflow description information is preset instead of the workflow work order, and the data universality is ensured. Therefore, when the dispatching system is switched, the work order management end only needs to generate the workflow work order in the data form matched with the dispatching system switched to currently by using the workflow description information, and repeated setting of the same workflow is avoided. Therefore, through the scheme, the complexity of the task scheduling process can be reduced.
Optionally, the apparatus may further include:
and the description information generation module is used for generating the workflow description information of any workflow so as to store the workflow description information to the information base.
Optionally, the description information generating module is specifically configured to:
displaying an information editing interface for a user to edit; the information editing interface displays identification information of a plurality of meta tasks in a preset database;
acquiring task combination information which is set in the information editing interface by the user and aims at a workflow, wherein the task combination information comprises identification information selected by the user and a dependency relationship set for the selected identification information;
and taking the meta-task indicated by the identification information in the task combination information as a meta-task required to be described by the to-be-generated workflow description information, and taking the dependency relationship in the task combination information as a dependency relationship required to be described by the to-be-generated workflow description information to generate the to-be-generated workflow description information.
Optionally, the description information generating module displays an information editing interface, and may include:
determining a first type meta-task which the user has available authority from a plurality of first type meta-tasks in a predetermined database; the first type of meta-task belongs to a local mode;
and displaying the information editing interface which takes the determined first type of meta-tasks and second type of meta-tasks as display elements, wherein the second type of meta-tasks are meta-tasks belonging to a global mode in the preset database.
Optionally, the generating module 420 is specifically configured to:
determining an adaptation module matched with the target scheduling system; each task scheduling system corresponds to one adaptation module;
and transmitting the target description information to an adaptation module matched with the target scheduling system, so that the adaptation module matched with the target scheduling system generates a workflow work order in a target data form by using the target description information, and the workflow work order serves as a work order to be issued.
Optionally, the apparatus may further include:
the marking module is used for marking the type of the work order to be issued before the sending module sends the work order to be issued to the target scheduling system, wherein the type of the work order is a global type or a non-global type;
correspondingly, after the target scheduling system sequentially executes each meta-task indicated by the work order to be issued and obtains an execution result, if the work order type of the work order to be issued is a global type, the execution result of each meta-task of the work order to be issued is stored in a specified shared area, and if the work order type of the work order to be issued is a non-global type, the execution result of each meta-task indicated by the work order to be issued is stored in a specified special area.
In addition, the embodiment of the application also provides a work order processing system. As shown in fig. 5, the work order processing system may include: a work order management terminal 510 and a target scheduling system 520; the target scheduling system is a task scheduling party serving as a work order receiving party, and the work order management end establishes communication with the target scheduling system in advance;
the work order management terminal 510 is configured to obtain workflow description information of a to-be-processed workflow from a predefined information base including the workflow description information, as target description information, where each workflow description information is information used for describing each meta-task indicated by a workflow and a dependency relationship of each meta-task; generating a workflow work order in a target data form by using the target description information, wherein the workflow work order is used as a work order to be issued; the target data form is a data form of a work order which can be identified by the target scheduling system; sending the work order to be issued to the target scheduling system 520;
the target scheduling system 520 is configured to receive the to-be-issued work order sent by the work order management end, and sequentially execute each meta-task indicated by the to-be-issued work order to obtain an execution result.
Optionally, the work order management end 510 is further configured to generate workflow description information of any workflow, so as to store the workflow description information in the information base.
Optionally, the work order management end 510 generates workflow description information of any workflow, which specifically includes:
displaying an information editing interface for a user to edit; the information editing interface displays identification information of a plurality of meta tasks in a preset database;
acquiring task combination information which is set in the information editing interface by the user and aims at a workflow, wherein the task combination information comprises identification information selected by the user and a dependency relationship set for the selected identification information;
and taking the meta-task indicated by the identification information in the task combination information as a meta-task required to be described by the to-be-generated workflow description information, and taking the dependency relationship in the task combination information as a dependency relationship required to be described by the to-be-generated workflow description information to generate the to-be-generated workflow description information.
Optionally, the work order management terminal 510 displays an information editing interface, which may include:
determining a first type meta-task which the user has available authority from a plurality of first type meta-tasks in a predetermined database; the first type of meta-task belongs to a local mode;
and displaying the information editing interface which takes the determined first type of meta-tasks and second type of meta-tasks as display elements, wherein the second type of meta-tasks are meta-tasks belonging to a global mode in the preset database.
Optionally, the work order management end 510 generates a workflow work order in a target data form by using the target description information, and the work order as the work order to be issued may include:
determining an adaptation module matched with the target scheduling system; each task scheduling system corresponds to one adaptation module;
and transmitting the target description information to an adaptation module matched with the target scheduling system, so that the adaptation module matched with the target scheduling system generates a workflow work order in a target data form by using the target description information, and the workflow work order serves as a work order to be issued.
Optionally, the work order management terminal 510 is further configured to mark a work order type for the work order to be issued before sending the work order to be issued to the target scheduling system, where the work order type is a global type or a non-global type;
correspondingly, the target scheduling system 520 is further configured to sequentially execute each meta-task indicated by the to-be-issued work order, obtain an execution result, store the execution result of each meta-task of the to-be-issued work order in an appointed shared area if the work order type of the to-be-issued work order is a global type, and store the execution result of each meta-task indicated by the to-be-issued work order in an appointed dedicated area if the work order type of the to-be-issued work order is a non-global type.
In addition, an electronic device is provided in the embodiments of the present application, as shown in fig. 6, and includes a processor 601, a communication interface 602, a memory 603, and a communication bus 604, where the processor 601, the communication interface 602, and the memory 603 complete communication with each other through the communication bus 604,
a memory 603 for storing a computer program;
the processor 601 is configured to implement the steps of any of the work order processing methods in the above embodiments when executing the program stored in the memory 603.
The communication bus mentioned in the electronic device may be a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, or the like. The communication bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown, but this does not mean that there is only one bus or one type of bus.
The communication interface is used for communication between the electronic equipment and other equipment.
The Memory may include a Random Access Memory (RAM) or a Non-Volatile Memory (NVM), such as at least one disk Memory. Optionally, the memory may also be at least one memory device located remotely from the processor.
The Processor may be a general-purpose Processor, including a Central Processing Unit (CPU), a Network Processor (NP), and the like; but also Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) or other Programmable logic devices, discrete Gate or transistor logic devices, discrete hardware components.
In another embodiment provided by the present application, a computer-readable storage medium is further provided, in which a computer program is stored, and the computer program, when executed by a processor, implements the steps of any of the above-mentioned work order processing methods.
In yet another embodiment provided by the present application, there is also provided a computer program product containing instructions which, when run on a computer, cause the computer to perform the steps of any of the above-described method of work order processing.
In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, cause the processes or functions described in accordance with the embodiments of the application to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website site, computer, server, or data center to another website site, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that incorporates one or more of the available media. The usable medium may be a magnetic medium (e.g., floppy Disk, hard Disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., Solid State Disk (SSD)), among others.
It is noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
All the embodiments in the present specification are described in a related manner, and the same and similar parts among the embodiments may be referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the system embodiment, since it is substantially similar to the method embodiment, the description is simple, and for the relevant points, reference may be made to the partial description of the method embodiment.
The above description is only for the preferred embodiment of the present application, and is not intended to limit the scope of the present application. Any modification, equivalent replacement, improvement and the like made within the spirit and principle of the present application are included in the protection scope of the present application.
Claims (15)
1. A work order processing method is characterized in that the method is applied to a work order management end; the work order management end establishes communication with a target scheduling system in advance, and the target scheduling system is a task scheduling system serving as a work order receiving party; the method comprises the following steps:
acquiring workflow description information of a workflow to be processed as target description information from a predefined information base containing the workflow description information, wherein each workflow description information is used for describing each meta-task indicated by the workflow and the dependency relationship of each meta-task;
generating a workflow work order in a target data form by using the target description information, wherein the workflow work order is used as a work order to be issued; the target data form is a data form of a work order which can be identified by the target scheduling system;
and sending the work order to be issued to the target scheduling system, enabling the target scheduling system to receive the work order to be issued, and sequentially executing each meta-task indicated by the work order to be issued to obtain an execution result.
2. The method of claim 1, further comprising:
and generating workflow description information of any workflow so as to store the workflow description information to the information base.
3. The method of claim 2, wherein generating workflow description information for any workflow comprises:
displaying an information editing interface for a user to edit; the information editing interface displays identification information of a plurality of meta tasks in a preset database;
acquiring task combination information which is set in the information editing interface by the user and aims at a workflow, wherein the task combination information comprises identification information selected by the user and a dependency relationship set for the selected identification information;
and taking the meta-task indicated by the identification information in the task combination information as a meta-task required to be described by the to-be-generated workflow description information, and taking the dependency relationship in the task combination information as a dependency relationship required to be described by the to-be-generated workflow description information to generate the to-be-generated workflow description information.
4. The method of claim 3, wherein the displaying an information editing interface comprises:
determining a first type meta-task which the user has available authority from a plurality of first type meta-tasks in a predetermined database; the first type of meta-task belongs to a local mode;
and displaying the information editing interface which takes the determined first type of meta-tasks and second type of meta-tasks as display elements, wherein the second type of meta-tasks are meta-tasks belonging to a global mode in the preset database.
5. The method according to claim 1, wherein the generating a workflow work order in the form of target data as a work order to be issued by using the target description information comprises:
determining an adaptation module matched with the target scheduling system; each task scheduling system corresponds to one adaptation module;
and transmitting the target description information to an adaptation module matched with the target scheduling system, so that the adaptation module matched with the target scheduling system generates a workflow work order in a target data form by using the target description information, and the workflow work order serves as a work order to be issued.
6. The method according to any one of claims 1-5, wherein before sending the work order to be issued to the target scheduling system, the method further comprises:
marking a work order type for the work order to be issued, wherein the work order type is a global type or a non-global type;
correspondingly, after the target scheduling system sequentially executes each meta-task indicated by the work order to be issued and obtains an execution result, if the work order type of the work order to be issued is a global type, the execution result of each meta-task of the work order to be issued is stored in a specified shared area, and if the work order type of the work order to be issued is a non-global type, the execution result of each meta-task indicated by the work order to be issued is stored in a specified special area.
7. A work order processing system, comprising: the work order management terminal and the target scheduling system; the target scheduling system is a task scheduling party serving as a work order receiving party, and the work order management end establishes communication with the target scheduling system in advance;
the work order management end is used for acquiring the workflow description information of the workflow to be processed from a predefined information base containing the workflow description information as target description information, wherein each workflow description information is used for describing each meta-task indicated by the workflow and the dependency relationship of each meta-task; generating a workflow work order in a target data form by using the target description information, wherein the workflow work order is used as a work order to be issued; the target data form is a data form of a work order which can be identified by the target scheduling system; sending the work order to be issued to the target scheduling system;
and the target scheduling system is used for receiving the work order to be issued sent by the work order management end and sequentially executing each meta-task indicated by the work order to be issued to obtain an execution result.
8. A work order processing device is characterized in that the work order processing device is applied to a work order management end; the work order management end establishes communication with a target scheduling system in advance, and the target scheduling system is a task scheduling system serving as a work order receiving party; the device comprises:
the system comprises an acquisition module, a processing module and a processing module, wherein the acquisition module is used for acquiring workflow description information of a workflow to be processed from a predefined information base containing the workflow description information as target description information, and each workflow description information is used for describing each meta-task indicated by the workflow and the dependency relationship of each meta-task;
the generating module is used for generating a workflow work order in a target data form by using the target description information, and the workflow work order is used as a work order to be issued; the target data form is a data form of a work order which can be identified by the target scheduling system;
and the sending module is used for sending the work order to be issued to the target scheduling system, so that the target scheduling system receives the work order to be issued and sequentially executes each element task indicated by the work order to be issued to obtain an execution result.
9. The apparatus of claim 8, further comprising:
and the description information generation module is used for generating the workflow description information of any workflow so as to store the workflow description information to the information base.
10. The apparatus of claim 9, wherein the description information generation module is specifically configured to:
displaying an information editing interface for a user to edit; the information editing interface displays identification information of a plurality of meta tasks in a preset database;
acquiring task combination information which is set in the information editing interface by the user and aims at a workflow, wherein the task combination information comprises identification information selected by the user and a dependency relationship set for the selected identification information;
and taking the meta-task indicated by the identification information in the task combination information as a meta-task required to be described by the to-be-generated workflow description information, and taking the dependency relationship in the task combination information as a dependency relationship required to be described by the to-be-generated workflow description information to generate the to-be-generated workflow description information.
11. The apparatus of claim 10, wherein the description information generation module displays an information editing interface, comprising:
determining a first type meta-task which the user has available authority from a plurality of first type meta-tasks in a predetermined database; the first type of meta-task belongs to a local mode;
and displaying the information editing interface which takes the determined first type of meta-tasks and second type of meta-tasks as display elements, wherein the second type of meta-tasks are meta-tasks belonging to a global mode in the preset database.
12. The apparatus of claim 8, wherein the generation module is specifically configured to:
determining an adaptation module matched with the target scheduling system; each task scheduling system corresponds to one adaptation module;
and transmitting the target description information to an adaptation module matched with the target scheduling system, so that the adaptation module matched with the target scheduling system generates a workflow work order in a target data form by using the target description information, and the workflow work order serves as a work order to be issued.
13. The apparatus of any one of claims 8-12, further comprising:
the marking module is used for marking the type of the work order to be issued before the sending module sends the work order to be issued to the target scheduling system, wherein the type of the work order is a global type or a non-global type;
correspondingly, after the target scheduling system sequentially executes each meta-task indicated by the work order to be issued and obtains an execution result, if the work order type of the work order to be issued is a global type, the execution result of each meta-task of the work order to be issued is stored in a specified shared area, and if the work order type of the work order to be issued is a non-global type, the execution result of each meta-task indicated by the work order to be issued is stored in a specified special area.
14. An electronic device is characterized by comprising a processor, a communication interface, a memory and a communication bus, wherein the processor and the communication interface are used for realizing mutual communication by the memory through the communication bus;
a memory for storing a computer program;
a processor for implementing the method steps of any of claims 1-6 when executing a program stored in the memory.
15. A computer-readable storage medium, characterized in that a computer program is stored in the computer-readable storage medium, which computer program, when being executed by a processor, carries out the method steps of any one of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010109026.5A CN113298331A (en) | 2020-02-21 | 2020-02-21 | Work order processing method, device and system and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010109026.5A CN113298331A (en) | 2020-02-21 | 2020-02-21 | Work order processing method, device and system and electronic equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113298331A true CN113298331A (en) | 2021-08-24 |
Family
ID=77317603
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010109026.5A Pending CN113298331A (en) | 2020-02-21 | 2020-02-21 | Work order processing method, device and system and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113298331A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114500312A (en) * | 2021-12-29 | 2022-05-13 | 中国电信股份有限公司 | Communication line checking method, device, electronic equipment and system |
| WO2023142451A1 (en) * | 2022-01-29 | 2023-08-03 | 北京百度网讯科技有限公司 | Workflow generation methods and apparatuses, and electronic device |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20040003353A1 (en) * | 2002-05-14 | 2004-01-01 | Joey Rivera | Workflow integration system for automatic real time data management |
| CN101478431A (en) * | 2009-02-10 | 2009-07-08 | 浪潮通信信息系统有限公司 | Task scheduling system for management by visible process |
| CN102004659A (en) * | 2009-08-31 | 2011-04-06 | 埃森哲环球服务有限公司 | Integration environment generator |
| CN102915476A (en) * | 2012-05-11 | 2013-02-06 | 摩卡软件(天津)有限公司 | Visual business process design method |
| US20170075332A1 (en) * | 2015-09-15 | 2017-03-16 | Applied Materials, Inc. | Scheduling in manufacturing environments |
| CN107392566A (en) * | 2017-06-29 | 2017-11-24 | 无锡智道安盈科技有限公司 | A kind of visible process marketing activity design method |
| CN107644286A (en) * | 2017-08-15 | 2018-01-30 | 上海艾融软件股份有限公司 | Workflow processing method and device |
| CN110032371A (en) * | 2019-04-17 | 2019-07-19 | 杭州玳数科技有限公司 | A kind of method and device storing offline task workflow using XML |
| CN110674083A (en) * | 2019-10-10 | 2020-01-10 | 深圳前海微众银行股份有限公司 | Workflow migration method, device, equipment and computer readable storage medium |
-
2020
- 2020-02-21 CN CN202010109026.5A patent/CN113298331A/en active Pending
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20040003353A1 (en) * | 2002-05-14 | 2004-01-01 | Joey Rivera | Workflow integration system for automatic real time data management |
| CN101478431A (en) * | 2009-02-10 | 2009-07-08 | 浪潮通信信息系统有限公司 | Task scheduling system for management by visible process |
| CN102004659A (en) * | 2009-08-31 | 2011-04-06 | 埃森哲环球服务有限公司 | Integration environment generator |
| CN102915476A (en) * | 2012-05-11 | 2013-02-06 | 摩卡软件(天津)有限公司 | Visual business process design method |
| US20170075332A1 (en) * | 2015-09-15 | 2017-03-16 | Applied Materials, Inc. | Scheduling in manufacturing environments |
| CN107392566A (en) * | 2017-06-29 | 2017-11-24 | 无锡智道安盈科技有限公司 | A kind of visible process marketing activity design method |
| CN107644286A (en) * | 2017-08-15 | 2018-01-30 | 上海艾融软件股份有限公司 | Workflow processing method and device |
| CN110032371A (en) * | 2019-04-17 | 2019-07-19 | 杭州玳数科技有限公司 | A kind of method and device storing offline task workflow using XML |
| CN110674083A (en) * | 2019-10-10 | 2020-01-10 | 深圳前海微众银行股份有限公司 | Workflow migration method, device, equipment and computer readable storage medium |
Non-Patent Citations (1)
| Title |
|---|
| 王洪彬;王纯;: "异构调度环境下ETL工作流监控系统的设计与实现", 电信工程技术与标准化, no. 12, pages 66 - 70 * |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114500312A (en) * | 2021-12-29 | 2022-05-13 | 中国电信股份有限公司 | Communication line checking method, device, electronic equipment and system |
| WO2023142451A1 (en) * | 2022-01-29 | 2023-08-03 | 北京百度网讯科技有限公司 | Workflow generation methods and apparatuses, and electronic device |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108153670B (en) | Interface testing method and device and electronic equipment | |
| CN108304201B (en) | Object updating method, device and equipment | |
| CN109062563B (en) | Method and device for generating page | |
| CN114115852A (en) | Visual service arranging method, device, equipment and medium | |
| EP3586290B1 (en) | Systems and methods for tracking assets across a distributed network environment | |
| CN109117141B (en) | Method, device, electronic equipment and computer readable storage medium for simplifying programming | |
| CN113364853B (en) | Business service system, business request method and gateway equipment | |
| CN113298331A (en) | Work order processing method, device and system and electronic equipment | |
| CN114594927A (en) | Low code development method, device, system, server and storage medium | |
| CN111651196A (en) | Document publishing method, device and server | |
| CN108876309B (en) | Starting method and device of flow form, storage medium and electronic equipment | |
| CN114358742A (en) | Workflow execution method, device, equipment and storage medium | |
| CN107633080B (en) | User task processing method and device | |
| CN111324345A (en) | Data processing mode generation method, data processing method and device and electronic equipment | |
| CN109302336B (en) | Mail generation method and device, computer equipment and storage medium | |
| CN111125205A (en) | Signboard data display method, terminal and storage medium | |
| CN115793911A (en) | Data processing method and device, electronic equipment and storage medium | |
| US8260782B2 (en) | Data element categorization in a service-oriented architecture | |
| CN115022266A (en) | Group member adding method, device, equipment and medium | |
| CN109254855B (en) | Registration method and device of parameter transmission protocol and electronic equipment | |
| CN113360232A (en) | Task processing method and device, electronic equipment and storage medium | |
| CN112699251A (en) | Data aggregation method and device, electronic equipment and storage medium | |
| CN112579325A (en) | Business object processing method and device, electronic equipment and storage medium | |
| CN112416980A (en) | Data service processing method, device and equipment | |
| CN113923250A (en) | Method, device and system for assisting network service arrangement |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |