CN112817594B - Method for adding data in linkage mode among multiple applications - Google Patents
Method for adding data in linkage mode among multiple applications Download PDFInfo
- Publication number
- CN112817594B CN112817594B CN202110141372.6A CN202110141372A CN112817594B CN 112817594 B CN112817594 B CN 112817594B CN 202110141372 A CN202110141372 A CN 202110141372A CN 112817594 B CN112817594 B CN 112817594B
- Authority
- CN
- China
- Prior art keywords
- qrobot
- node
- flow
- data
- task
- 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.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/38—Creation or generation of source code for implementing user interfaces
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
- G06F9/4451—User profiles; Roaming
Abstract
The invention provides a method for adding data in a linkage manner among multiple applications, which comprises an adding setting step and an adding operation triggering step in a flow, wherein the adding setting step comprises the following steps: s1: creating an audionodeServer in the flow template; s2: editing a front-end interface of the audionoderver on a visual interface; s3: the front-end interface calls an audionodeServer to acquire the flow information of an application; s4: adding a Qrobot adding node at the target position of the front-end interface, and performing custom configuration; s5: and after the Qrobot adds the node, issuing, wherein in the issuing process, the audioNodeServer checks whether the Qrobot adds the node into a loop, and if so, the Qrobot adds the node into the loop, and the node is not allowed to be issued. The beneficial effects of the invention are as follows: the repeated labor is avoided, the working efficiency is improved, and the automation of the working service process is realized.
Description
Technical Field
The invention relates to the technical field of computer information processing, in particular to a method for adding data among multiple applications in a linkage manner.
Background
In a traditional office mode, for example, data needing to be newly added in a work flow generally needs to be manually added into a corresponding database, flows need to be respectively and correspondingly established for different work scenes, the data needs to be maintained on time, and timeliness is difficult to guarantee. For example, a new job co-worker will enter the database of the "pass resume" and start the employee job process if the new job co-worker passes after the interview process is finished.
Therefore, in order to simplify a large amount of repeated redundant operations in an actual working scene, repeated flow contents can be automatically added by linkage addition of data among multiple applications, the workload of data filling is reduced to the maximum extent, and the working efficiency is greatly improved.
Disclosure of Invention
In order to solve the technical problem, the invention discloses a method for adding data in linkage among multiple applications, and the technical scheme of the invention is implemented as follows:
a method for adding data in linkage among multiple applications comprises a Qrobot adding setting step and a Qrobot adding operation triggering step in a flow, wherein the Qrobot adding setting step is used for adding nodes and performing custom configuration, the Qrobot adding operation triggering step in the flow is used for executing custom configuration content, and the Qrobot adding setting step comprises the following steps:
s1: creating an audionodeServer in the flow template;
s2: editing a front-end interface FlowPainter of the audioNodeServer on a visual interface;
s3: the front-end interface FlowPainter calls the audioNodeServer to acquire the flow information of one application;
s4: adding a Qrobot adding node at the target position of the front-end interface FlowPainter, and performing custom configuration;
s5: after the Qrobot adds the node, issuing operation is carried out, in the process of issuing, the audioNodeServer checks whether the Qrobot adds the node into a loop, and if the node is in the loop, the node is not allowed to be issued;
the step of triggering Qrobot addition in the process comprises a process engine and Qrobot rear-end execution, wherein the process engine comprises a process engine FlowEngine, the process engine FlowEngine is initialized, and the initialized process engine FlowEngine encapsulates Qrobot tasks generated by Qrobot addition nodes in the process into messages and sends the messages to a message queue;
the Qrobot backend execution includes:
e1: executing an application process QrobotDaemon to receive a Qrobot task through a message queue;
e2: executing an application flow QrobotDaemon to check the validity of the Qrobot task;
e3: if the Qrobot task passes the legality, executing Qrobot task operation of adding nodes into the Qrobot;
the flow engine FlowEngine is responsible for executing the set flow, and the execution application flow QrobotDaemon executes the task of the Qrobot adding node created in the flow;
the method provided by the audionoderver comprises the following steps: acquiring an application flow method m1, a flow node adding method m2, a flow node setting updating method m3, a flow node deleting method m4 and a flow method m5 after release and edition;
the front-end interface FlowPainter completes the operation of adding nodes to the Qrobot by a flow node adding method m 2;
in S4, the method for custom configuration includes: a, configuring a target application of the Qrobot adding node data, wherein the flow engine FlowEngine can add the data into the target application when executing the task operation of the Qrobot adding node;
b: configuring a field mapping rule when the Qrobot adds node data, wherein the flow engine FlowEngine can fill a field value of data triggering the Qrobot adding node into a field of a target application according to the field mapping rule when the Qrobot adding node operation is executed;
c: after the configuration is finished, the front-end interface FlowPainter calls an update flow node setting method m3 in the audioNodeServer to update the configuration of the flow node;
and the front-end interface FlowPainter issues the flow by calling the flow method m5 after issuing and editing in the audioNodeServer.
Preferably, in E2, if the application flow of the generated Qrobot add node has been deleted, the Qrobot task is abandoned.
Preferably, in the E2, if the target application operated by the Qrobot add node has been deleted, the Qrobot task is abandoned.
Preferably, in E2, the field mapping rule of the Qrobot add-on node task is null or illegal, and the Qrobot task is discarded.
Preferably, the performing the Qrobot add node operation includes: and assembling the submitted data according to the field mapping rule, and submitting the data to the target application.
By implementing the technical scheme of the invention, the technical problems that newly added data in the working process generally needs to be manually added into a corresponding database, the processes need to be respectively and correspondingly established for different working scenes, the data needs to be maintained on time and the timeliness is difficult to ensure in the prior art can be solved; by implementing the technical scheme of the invention, repeated process contents can be automatically added through a method for adding data in linkage among multiple applications, so that the repeated labor can be avoided, the working efficiency is improved, the automation of the workflow process of the work service is realized, one-time form filling and multi-stage triggering are realized, the change and the setting are more friendly through a visual interface, the operation is convenient, the flexibility of the system is higher, the expandability is strong, and the technical effect of adapting to various work scenes is achieved.
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 one embodiment of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
In which like parts are designated by like reference numerals. It should be noted that the terms "front," "back," "left," "right," "upper" and "lower" used in the following description refer to directions in the drawings, and the terms "bottom" and "top," "inner" and "outer" refer to directions toward and away from, respectively, the geometric center of a particular component.
FIG. 1 is a schematic flow chart of a Qrobot add setup procedure;
FIG. 2 is a schematic flow diagram of a process engine;
FIG. 3 is a diagram illustrating a process flow of Qrobot backend execution.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, 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 invention.
Examples
In a preferred embodiment, as shown in fig. 1, fig. 2 and fig. 3, a method for adding data by linkage among multiple applications includes a Qrobot addition setting step and a Qrobot addition operation triggering step in a flow, where the Qrobot addition setting step includes:
s1: creating an audionodeServer in the flow template;
s2: editing a front-end interface FlowPainter of the audio NodeServer on a visual interface;
s3: the front-end interface FlowPainter calls the audioNodeServer to acquire the flow information of one application;
s4: adding a Qrobot adding node at the target position of the front-end interface FlowPoint, and performing custom configuration;
s5: after the Qrobot adds the node, issuing operation is carried out, in the issuing process, the audioNodeServer checks whether the Qrobot adds the node into a loop, and if so, the Qrobot adds the node into the loop, the node is not allowed to be issued;
the step of triggering Qrobot addition in the process comprises a process engine module and a Qrobot rear-end execution module, wherein the process engine module comprises a process engine FlowEngine, the process engine module comprises the step of initializing the process engine FlowEngine, the initialized process engine FlowEngine encapsulates tasks generated by Qrobot addition nodes in the process into messages and sends the messages to a message queue, and the Qrobot rear-end execution module comprises the following steps:
e1: executing an application flow QrobotDaemon, and receiving a Qrobot adding node through a message queue;
e2: executing an application flow QrobotDaemon to check the validity of the Qrobot adding node;
e3: and if the legality of the Qrobot adding node passes, executing the task operation of the Qrobot adding node.
In a specific embodiment, the method for adding data in a linkage manner among multiple applications can automatically add repeated process contents, reduce the workload of filling data to the greatest extent and greatly improve the working efficiency. Including Qrobot add settings and triggering Qrobot add operations in the flow. In the Qrobot addition setup:
s1, creating an instance audioNodeServer according to the template, wherein the method provided by the instance audioNodeServer comprises the following steps: acquiring an application flow m1, adding a flow node m2, updating a setting m3 of the flow node, deleting a flow node m4 and issuing an edited flow m 5;
s2: initializing a visual flow editing page FlowPainter, and displaying the flow, calling an audioNodeServer editing flow, and storing and issuing the edited flow to a user in a visual form by a front-end interface FlowPainter;
s3: the front-end interface FlowPainter calls the audioNodeServer to acquire the flow information of one application, and displays the flow of the application to a user in a visual form.
S4: and the user triggers the operation of adding the Qrobot adding node at the target position on the front-end interface FlowPainter, and the front-end interface FlowPainter calls an adding flow node method m2 of the audioNodeServer to finish the adding operation of the Qrobot adding node.
S5: after the addition of the Qrobot node is completed, the user can configure the Qrobot node on the front-end interface FlowEngine, and the configured contents include: a. configuring a target application of the Qrobot adding node, wherein the flow engine can add the data of the Qrobot adding node into the target application when executing Qrobot operation; b. configuring a field mapping rule when the Qrobot adds the node, wherein the flow engine can trigger the field mapping rule of the Qrobot adding node according to the field mapping when executing Qrobot operation, and the flow engine can fill the field value of the data triggering the Qrobot adding into the field of the target application according to the field mapping rule when executing the Qrobot operation; c. after the configuration is finished, the front-end interface flowpointer calls an update flow node setting method m3 in the audionoderver to update the configuration of the flow node.
S6: after the user completes the Qrobot node addition, triggering the operation of flow release on the front-end interface FlowPainter: the front-end interface FlowPainter calls a post-release editing flow method m5 in the audioNodeServer to release the flow; in the process of issuing the flow, the audionoderver checks whether the Qrobot adding operation is in a loop, and if so, the audionoderver does not allow the flow to be issued. A loop formation means, for example, that a is added to B, and then B is added to a again, and if a loop is formed, the flow does not have the meaning of execution, and therefore if a loop is formed, the flow is not issued.
After the process is released, the operation of triggering a Qrobot adding node in the next part of the process is carried out, the Qrobot adding triggering step in the process comprises a process engine module and a Qrobot rear-end execution module, the process engine module comprises a process engine FlowEngine, the process engine module comprises initializing the process engine FlowEngine, the initialized process engine FlowEngine executes the process which is set by a user and released, when the Qrobot adding node in the process is executed, a Qrobot task is generated and encapsulated into a message to be sent to a message queue, as shown in FIG. 2; as shown in fig. 3, the flow engine FlowEngine is initialized to execute a flow set by a user, and execute a Qrobot task created in the application flow QrobotDaemon. The method comprises the following steps:
e1: executing an application flow QrobotDaemon as a consumer of a message queue, and receiving a Qrobot task in the message queue;
e2: the execution of the application flow QrobotDaemon checks the validity of the Qrobot task in the message queue: if the application flow of the Qrobot adding node for generating the Qrobot task is deleted, the Qrobot task is abandoned; if the target application of the Qrobot adding node is deleted, abandoning the Qrobot task, wherein the target application is a large frame and comprises contents such as a form, a process engine and the like, the target application comprises an application process, and the deletion of the target application is to delete the application process; if the field mapping rule of the Qrobot adding node is empty or illegal, abandoning the Qrobot task, wherein the field mapping rule is that the Qrobot updating data wants to determine a specific field in a specific updating form, an analysis rule needs to be set in advance in the Qrobot adding configuration step, and after the data is analyzed according to the analysis rule, the data is displayed in the field which corresponds to the binding in the form, wherein the binding also needs to be set in the analysis rule;
e3: after the application flow QrobotDaemon is executed to check that the validity of the Qrobot task passes, the Qrobot adding operation is started to be executed: assembling submitted data according to a field mapping rule, submitting the data to a target application, wherein the target application is a large framework and comprises contents such as a form and a process engine, the target application comprises an application process, the field mapping rule is that a specific field in a specific updated form is required to be determined by Qrobot updated data, an analysis rule needs to be set in advance in a Qrobot adding configuration step, and after the data is analyzed according to the analysis rule, the data is displayed in a field which is bound to the form correspondingly, and the binding also needs to be set in the analysis rule. The data submitted according to the field mapping rule is legal and effective and can be executed effectively.
For example, during company recruitment, after an interview process is finished, an employee who newly enters a job according to the prior art passes an interview and then enters a database of a "passing resume" and needs to be manually added to the database. After the addition and the setting of the nodes are completed, after the user completes interview recording, only the relevant data after the interview passes are uploaded to the process, after the addition of the process is completed, all data after the interview passes can be automatically transmitted to the process of passing the resume, manual input is not needed, the workload of filling data is reduced to the maximum extent, and the work efficiency is greatly improved.
The method provided by the example audionoderver comprises the following steps: the method comprises the steps of obtaining an application flow m1, adding a flow node m2, updating a setting m3 of the flow node, deleting the flow node m4 and publishing an edited flow m5, and is convenient for a user to operate when the user adds data by using the Qrobot and comprises the steps of selecting the application flow, adding the flow node, updating the flow node, deleting the flow node and publishing the edited flow.
In a preferred embodiment, the FlowEngine is responsible for executing a flow set by a user, and executing a Qrobot task created in the application flow QrobotDaemon execution flow.
In a preferred embodiment, the method provided by the audionodeserver includes: the method comprises the steps of obtaining an application flow method m1, a flow node adding method m2, a flow node updating method m3, a flow node deleting method m4 and a flow method after release and edition m5, wherein the methods are used for facilitating the operation of a user when the user adds data by using Qrobot and comprise application flow selection, flow node addition, flow node updating, flow node deletion, flow after release and edition and the like.
In a preferred embodiment, the front-end interface FlowPainter completes the Qrobot add node operation by the add flow node method m 2.
In this embodiment, in the Qrobot addition setting step, the user triggers an operation of adding a Qrobot addition node at a target position on the front-end interface flowpointer, and the front-end interface flowpointer calls the add flow node method m2 of the audionoderver to complete the addition operation of the Qrobot addition node.
In a preferred embodiment, in S4, the method of custom configuration includes:
configuring a target application of the Qrobot adding node data, wherein the data is added into the target application by the FlowEngine when the task operation of the Qrobot adding node is executed;
b: configuring a field mapping rule when the Qrobot adds node data, wherein the field value of the data triggering the Qrobot adding node is filled into a field of a target application according to the field mapping rule when the initialization process engine FlowEngine executes the operation of the Qrobot adding node;
c: after the configuration is finished, the front-end interface flowpointer calls the updated process node setting method m3 in the audionoderver to update the configuration of the process node.
In a preferred embodiment, the frontend interface flowpointer issues a flow by calling the post-issuance edited flow method m5 in the audionoderver.
In this embodiment, after completing the configuration of the Qrobot node addition, the user triggers the operation of flow issuance on the front-end interface flowpointer: the front-end interface FlowPainter calls a post-release editing flow method m5 in the audioNodeServer to release the flow; in the process of issuing the flow, the audionoderver checks whether the Qrobot adding operation is in a loop, and if so, the audionoderver does not allow the flow to be issued. A loop formation means, for example, that a is added to B, and then B is added to a again, and if a loop is formed, the flow does not have the meaning of execution, and therefore if a loop is formed, the flow is not issued.
In a preferred embodiment, in E2, if the application flow of the generated Qrobot add node has been deleted, the task of the Qrobot add node is abandoned.
In this embodiment, the application flow is the basis for configuring and executing the whole Qrobot add node, and when the application flow does not exist, the role of the Qrobot add node does not have the basis and meaning for execution.
In a preferred embodiment, in E2, if the target application operated by the Qrobot add node has been deleted, the task of the Qrobot add node is abandoned.
In this embodiment, the target application is a large framework and includes contents such as a form and a flow engine, the target application includes an application flow, the application flow is deleted while the target application is deleted, and when the application flow does not exist, the role of adding a node by the Qrobot has no basis and meaning for execution.
In a preferred embodiment, in E2, the field mapping rule of the Qrobot add node task is null or illegal, and the task of the Qrobot add node is abandoned.
In this embodiment, the field mapping rule is that the Qrobot update data is to determine a specific field in a specific update form, an analysis rule needs to be set in advance in the step of adding and configuring the Qrobot, and after the data is analyzed according to the analysis rule, the field corresponding to the binding in the form is displayed, where the binding also needs to be set in the analysis rule.
In a preferred embodiment, performing the Qrobot add node operation includes: and assembling the submitted data according to the field mapping rule, and submitting the data to the target application.
In this embodiment, the target application is a large framework, and includes contents such as a form and a process engine, the target application includes an application process, and the field mapping rule is that, because the Qrobot update data wants to determine a specific field in a specific update form, an analysis rule needs to be set in advance in the step of adding and configuring the Qrobot, and after the data is analyzed according to the analysis rule, the data is displayed in a field corresponding to a binding in the form, where the binding also needs to be set in the analysis rule. The data submitted according to the field mapping rule is legal and effective and can be executed effectively.
It should be understood that the above-described embodiments are merely exemplary of the present invention, and are not intended to limit the present invention, and that any modification, equivalent replacement, or improvement made without departing from the spirit and principle of the present invention shall fall within the protection scope of the present invention.
Claims (5)
1. A method for adding data in linkage among multiple applications is characterized in that: the method comprises a Qrobot adding setting step and a Qrobot adding operation triggering step in the process, wherein the Qrobot adding setting step is used for adding nodes and performing custom configuration, the Qrobot adding operation triggering step in the process is used for executing custom configuration content, and the Qrobot adding setting step comprises the following steps:
s1: creating an audionodeServer in the flow template;
s2: editing a front-end interface FlowPainter of the audioNodeServer on a visual interface;
s3: the front-end interface FlowPainter calls the audioNodeServer to acquire the flow information of one application;
s4: adding a Qrobot adding node at the target position of the front-end interface FlowPainter, and performing custom configuration;
s5: after the Qrobot adds the node, issuing operation is carried out, in the issuing process, the audioNodeServer checks whether the Qrobot adds the node into a loop, and if so, the Qrobot adds the node into the loop, the node is not allowed to be issued;
the step of triggering Qrobot addition in the process comprises the execution of a process engine and a Qrobot rear end, wherein the process engine comprises a process engine FlowEngine, the process engine FlowEngine initializes, and the initialized process engine FlowEngine encapsulates a Qrobot task generated by a Qrobot addition node in the process into a message and sends the message to a message queue;
the Qrobot backend execution includes:
e1: executing an application process QrobotDaemon to receive a Qrobot task through a message queue;
e2: executing an application flow QrobotDaemon to check the validity of the Qrobot task;
e3: if the Qrobot task passes the legality, executing Qrobot task operation of adding nodes into the Qrobot;
the flow engine FlowEngine is responsible for executing the set flow, and the execution application flow QrobotDaemon executes the task of the Qrobot adding node created in the flow;
the method provided by the audionoderver comprises the following steps: acquiring an application flow method m1, a flow node adding method m2, a flow node setting updating method m3, a flow node deleting method m4 and a flow method m5 after release and edition;
the front-end interface FlowPainter completes the operation of adding nodes to the Qrobot by a flow node adding method m 2;
in S4, the method of custom configuration includes: a, configuring a target application of the Qrobot adding node data, wherein the flow engine FlowEngine can add the data into the target application when executing the task operation of the Qrobot adding node;
b: configuring a field mapping rule when the Qrobot adds node data, wherein the flow engine FlowEngine fills a field value of data triggering the Qrobot adding node into a field of a target application according to the field mapping rule when executing the Qrobot adding node operation;
c: after the configuration is finished, the front-end interface FlowPainter calls an update flow node setting method m3 in the audioNodeServer to update the configuration of the flow node;
and the front-end interface FlowPainter issues the flow by calling the flow method m5 after the issue and the edition in the audioNodeServer.
2. The method for linkage addition of data among multiple applications according to claim 1, wherein: and in the E2, if the generated application flow of the Qrobot adding node is deleted, the Qrobot task is abandoned.
3. The method for linkage data addition among multiple applications according to claim 1, wherein: in the E2, if the target application operated by the Qrobot add node has been deleted, the Qrobot task is abandoned.
4. The method for linkage data addition among multiple applications according to claim 1, wherein: in the E2, the field mapping rule of the Qrobot add-on node task is null or illegal, and the Qrobot task is discarded.
5. The method for linkage data addition among multiple applications according to claim 1, wherein: executing the Qrobot add node operation comprises: and assembling the submitted data according to the field mapping rule, and submitting the data to the target application.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110141372.6A CN112817594B (en) | 2021-02-02 | 2021-02-02 | Method for adding data in linkage mode among multiple applications |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110141372.6A CN112817594B (en) | 2021-02-02 | 2021-02-02 | Method for adding data in linkage mode among multiple applications |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112817594A CN112817594A (en) | 2021-05-18 |
| CN112817594B true CN112817594B (en) | 2022-06-21 |
Family
ID=75860438
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110141372.6A Active CN112817594B (en) | 2021-02-02 | 2021-02-02 | Method for adding data in linkage mode among multiple applications |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112817594B (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109740920A (en) * | 2018-12-29 | 2019-05-10 | 江苏电力信息技术有限公司 | It is called by management and monitoring RPA robot realizes the method that operation flow automates |
| CN111126781A (en) * | 2019-11-29 | 2020-05-08 | 苏宁云计算有限公司 | RPA service flow establishing method and system |
| CN111798216A (en) * | 2020-07-14 | 2020-10-20 | 上海智子信息科技股份有限公司 | Robot process automation multi-tool integration method and system |
| CN112035630A (en) * | 2020-03-27 | 2020-12-04 | 北京来也网络科技有限公司 | Dialogue interaction method, device, equipment and storage medium combining RPA and AI |
-
2021
- 2021-02-02 CN CN202110141372.6A patent/CN112817594B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109740920A (en) * | 2018-12-29 | 2019-05-10 | 江苏电力信息技术有限公司 | It is called by management and monitoring RPA robot realizes the method that operation flow automates |
| CN111126781A (en) * | 2019-11-29 | 2020-05-08 | 苏宁云计算有限公司 | RPA service flow establishing method and system |
| CN112035630A (en) * | 2020-03-27 | 2020-12-04 | 北京来也网络科技有限公司 | Dialogue interaction method, device, equipment and storage medium combining RPA and AI |
| CN111798216A (en) * | 2020-07-14 | 2020-10-20 | 上海智子信息科技股份有限公司 | Robot process automation multi-tool integration method and system |
Non-Patent Citations (3)
| Title |
|---|
| Construction and Practice of Intelligent;Zhenyu Zhang等;《人工智能与机器人研究》;20200219;第1-10页 * |
| Power Platform之Power Automate新增RPA功能;shuzhen.yu;《https://www.cnblogs.com/shuzhenyu/p/12072648.html》;20191220;第1-18页 * |
| 快速上手可视化编排;阿里云;《https://help.aliyun.com/document_detail/176393.html》;20210106;第1-27页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112817594A (en) | 2021-05-18 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US5826086A (en) | Device and method for aiding designing process of software development | |
| EP2458562A1 (en) | computer aided assembly sequence generation | |
| CN110147225A (en) | A kind of code generating method, device and computer equipment, storage medium | |
| CN106774170B (en) | A kind of generation system of three-dimensional mechanical processing technique | |
| CN101777004A (en) | Method and system for realizing BPEL sub-process multiplexing based on template in service-oriented environment | |
| JP2010113425A (en) | Manufacturing information management method and manufacturing information management system | |
| JP3361594B2 (en) | Method and apparatus for setting / changing graph creation | |
| CN113253971B (en) | Voice interaction method and device, voice interaction system, vehicle and medium | |
| US20050261791A1 (en) | Interfaces from external systems to time dependent process parameters in integrated process and product engineering | |
| CN113032633B (en) | Method for customizing table by using reference data item | |
| CN112817594B (en) | Method for adding data in linkage mode among multiple applications | |
| JPS59214964A (en) | Conversational scheduling system | |
| JP2607467B2 (en) | Table conversion type software configuration method | |
| CN115422621A (en) | Method, system, device and storage medium for modifying colors of digital-analog parts in batch | |
| JP2004265278A (en) | Automatic program generation device | |
| US20130132425A1 (en) | Query definition apparatus and method for multi-tenant | |
| US20200302661A1 (en) | Information processing apparatus, computer-readable recording medium, and drawing creation support method | |
| CN112506395A (en) | Vehicle design processing method and device and computer equipment | |
| CN112486474A (en) | Method for manufacturing visual workflow configuration platform based on mxgraph and activiviti technology | |
| CN107506201A (en) | A kind of python skeleton generating methods and system | |
| JPH10222355A (en) | Gui application developing device | |
| KR20050084119A (en) | Software for die-stamping modelling | |
| JPH11219444A (en) | Scenario editing device | |
| Mishra | Mini Project | |
| CN116028182A (en) | Logic flow big data processing method and processing system |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |