CN117519779A - Flow scheduling method and device for heterogeneous RPA products - Google Patents
Flow scheduling method and device for heterogeneous RPA products Download PDFInfo
- Publication number
- CN117519779A CN117519779A CN202311568662.4A CN202311568662A CN117519779A CN 117519779 A CN117519779 A CN 117519779A CN 202311568662 A CN202311568662 A CN 202311568662A CN 117519779 A CN117519779 A CN 117519779A
- Authority
- CN
- China
- Prior art keywords
- rpa
- manufacturer
- interface
- information
- parameter
- 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
- 238000000034 method Methods 0.000 title claims abstract description 47
- 238000013507 mapping Methods 0.000 claims description 28
- 238000004590 computer program Methods 0.000 claims description 27
- 238000001914 filtration Methods 0.000 claims description 10
- 238000012545 processing Methods 0.000 claims description 10
- 230000008569 process Effects 0.000 claims description 9
- 238000003860 storage Methods 0.000 claims description 9
- 230000000007 visual effect Effects 0.000 claims description 7
- 230000001419 dependent effect Effects 0.000 claims description 3
- 238000012795 verification Methods 0.000 claims description 3
- 238000012800 visualization Methods 0.000 claims description 2
- 230000006978 adaptation Effects 0.000 abstract description 3
- 238000010586 diagram Methods 0.000 description 12
- 238000011161 development Methods 0.000 description 7
- 230000006870 function Effects 0.000 description 5
- 230000008901 benefit Effects 0.000 description 4
- 238000005516 engineering process Methods 0.000 description 4
- 238000004801 process automation Methods 0.000 description 4
- 238000004519 manufacturing process Methods 0.000 description 3
- 238000013461 design Methods 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 230000004044 response Effects 0.000 description 2
- 238000013473 artificial intelligence Methods 0.000 description 1
- 230000000295 complement effect Effects 0.000 description 1
- 230000008676 import Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 239000000725 suspension Substances 0.000 description 1
Classifications
-
- 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/448—Execution paradigms, e.g. implementations of programming paradigms
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Stored Programmes (AREA)
Abstract
The invention discloses a flow scheduling method and a flow scheduling device for heterogeneous RPA products, which can be used in the technical field of robot flow automation, and the method comprises the following steps: after receiving a flow scheduling request of an RPA product of a calling party, acquiring RPA interface information; according to the RPA interface information, PRA manufacturer interface information corresponding to the RPA product is obtained; determining an RPA manufacturer parameter entering field according to the parameter entering field of a calling party and PRA manufacturer interface information, and assembling manufacturer interface calling data; pushing the manufacturer interface call data to corresponding RPA manufacturer service through a corresponding PRA manufacturer interface; receiving an RPA product calling result fed back by an RPA manufacturer service; and determining a parameter output field of the calling party according to the RPA product calling result, and feeding back the parameter output field to the calling party. The invention can shield the difference between different RPA products, realize the fast adaptation of the cross RPA products and the unified scheduling of the application flow, improve the efficiency and save the manpower.
Description
Technical Field
The invention relates to the technical field of robot process automation, in particular to a process scheduling method and device for heterogeneous RPA products.
Background
This section is intended to provide a background or context to the embodiments of the invention that are recited in the claims. The description herein is not admitted to be prior art by inclusion in this section.
In recent years, a robot process automation technology (Robotic Process Automation, english is called RPA for short) is vigorous, and is the most mature and widely applied man-machine interaction automation technology in the artificial intelligence field at present. At present, RPA manufacturers compete strongly, and each RPA product has advantages and disadvantages, and is used as an application party of the RPA technology, and the RPA products are selected to cooperate with a plurality of RPA manufacturers, so that the binding of a single RPA manufacturer is avoided, and the complementary advantages of the RPA products are realized. In the actual business operation process, different RPA products often need respective RPA controllers to schedule respective RPA application flows to be executed on devices of respective RPA robots, and for such a scenario, the RPA products do not have RPA flow scheduling capability across the RPA products.
The RPA market basically purchases an RPA product, when the demand is increased or a single RPA product cannot support richer RPA scenes, if the RPA product is newly introduced, the unified scheduling of the application flow of the cross RPA product is realized, the advantage complementation of different RPA products is realized, and the RPA product is a service pain point to be solved urgently.
When each family adopts a mode of a plurality of RPA products to construct the RPA application, the design, development and operation of the RPA application are realized in one RPA product, the RPA applications among different RPA products can not be mutually called, and the unified scheduling requirement for the RPA application flow needing to cross the RPA products is not met.
At present, aiming at a scene of crossing RPA products, the scheme basically adopted is that the application flow of one RPA product can be scheduled and executed by using an own RPA controller, and a plurality of RPA products need a plurality of RPA controllers, so the following problems exist:
(1) Flow calls across RPA products cannot be supported;
(2) The RPA controllers are needed to be connected when the RPA products are purchased, so that the development cost is high, time and labor are wasted, and the cost is high;
(3) The method can not be quickly adapted to new RPA manufacturers, and needs to re-develop codes and re-deploy;
disclosure of Invention
The embodiment of the invention provides a flow scheduling method of heterogeneous RPA products, which can shield the difference between different RPA products, realize the fast adaptation of the cross RPA products and the unified scheduling of the application flow, improve the efficiency and save the manpower, and comprises the following steps:
after receiving a flow scheduling request of an RPA product of a calling party, acquiring RPA interface information corresponding to the RPA product;
according to the RPA interface information, PRA manufacturer interface information corresponding to the RPA product is obtained;
determining an RPA manufacturer parameter entering field according to the parameter entering field of the calling party and PRA manufacturer interface information;
according to the RPA manufacturer parameter entering field, the RPA interface information and the PRA manufacturer interface information, manufacturer interface calling data are assembled, wherein the manufacturer interface calling data comprise the RPA manufacturer parameter entering field, the manufacturer interface number and the interface access information;
pushing the manufacturer interface call data to a corresponding RPA manufacturer service through a PRA manufacturer interface corresponding to the manufacturer interface number, wherein the RPA manufacturer service calls up an RPA product according to a machine specified in the interface access information;
receiving an RPA product calling result fed back by an RPA manufacturer service;
and determining a parameter output field of the calling party according to the RPA product calling result, and feeding back the parameter output field to the calling party.
The embodiment of the invention also provides a flow scheduling device of heterogeneous RPA products, which can shield the difference between different RPA products, realize the uniform scheduling of the rapid adaptation and application flow of the cross RPA products, improve the efficiency and save the manpower, and comprises:
the RPA interface information acquisition module is used for acquiring RPA interface information corresponding to the RPA product after receiving a flow scheduling request of the RPA product of the calling party;
the PRA manufacturer interface information obtaining module is used for obtaining PRA manufacturer interface information corresponding to the RPA product according to the RPA interface information;
the RPA manufacturer parameter entering field determining module is used for determining the RPA manufacturer parameter entering field according to the parameter entering field of the calling party and the PRA manufacturer interface information;
the manufacturer interface call data assembly module is used for assembling manufacturer interface call data according to the RPA manufacturer parameter entering field, the RPA interface information and the PRA manufacturer interface information, wherein the manufacturer interface call data comprises the RPA manufacturer parameter entering field, the manufacturer interface number and the interface access information;
the service calling module pushes the manufacturer interface calling data to the corresponding RPA manufacturer service through the PRA manufacturer interface corresponding to the manufacturer interface number, wherein the RPA manufacturer service calls up an RPA product according to a machine appointed in the interface access information;
the calling result feedback module is used for receiving the RPA product calling result fed back by the RPA manufacturer service;
and the parameter-out field feedback module is used for determining parameter-out fields of the calling party according to the RPA product calling result and feeding back the parameter-out fields to the calling party.
The embodiment of the invention also provides a computer device which comprises a memory, a processor and a computer program stored on the memory and capable of running on the processor, wherein the processor realizes the flow scheduling method of the heterogeneous RPA product when executing the computer program.
The embodiment of the invention also provides a computer readable storage medium, wherein the computer readable storage medium stores a computer program, and the computer program realizes the flow scheduling method of the heterogeneous RPA product when being executed by a processor.
The embodiment of the invention also provides a computer program product, which comprises a computer program, and the computer program realizes the flow scheduling method of the heterogeneous RPA product when being executed by a processor.
In the embodiment of the invention, after receiving a flow scheduling request of an RPA product of a calling party, RPA interface information corresponding to the RPA product is obtained; according to the RPA interface information, PRA manufacturer interface information corresponding to the RPA product is obtained; determining an RPA manufacturer parameter entering field according to the parameter entering field of the calling party and PRA manufacturer interface information; according to the RPA manufacturer parameter entering field, the RPA interface information and the PRA manufacturer interface information, manufacturer interface calling data are assembled, wherein the manufacturer interface calling data comprise the RPA manufacturer parameter entering field, the manufacturer interface number and the interface access information; pushing the manufacturer interface call data to a corresponding RPA manufacturer service through a PRA manufacturer interface corresponding to the manufacturer interface number, wherein the RPA manufacturer service calls up an RPA product according to a machine specified in the interface access information; receiving an RPA product calling result fed back by an RPA manufacturer service; and determining a parameter output field of the calling party according to the RPA product calling result, and feeding back the parameter output field to the calling party. Compared with the technical scheme that when a plurality of RPA products are subjected to flow scheduling, a plurality of RPA controllers of different manufacturers are required to be accessed, namely, a plurality of manufacturers are required to be adapted, the embodiment of the invention adopts one RPA product adapter, after receiving a flow call request, RPA interface information and PRA manufacturer interface information can be sequentially acquired to determine the parameter entering field of the RPA manufacturer, namely, the RPA manufacturer service corresponding to the selected RPA product is selected, then manufacturer interface call data are assembled, and because the RPA interface information designates a machine, the RPA manufacturer service can start the RPA product according to the designated machine to complete the call, return the call result, and then determine the parameter exiting field of the caller and feed back to the caller to complete the whole call flow, thereby realizing the flow call of the cross-RPA product, having high efficiency, being capable of rapidly adapting to new RPA products without developing and redeploying and saving manpower.
Drawings
In order to more clearly illustrate the embodiments of the invention or the technical solutions in the prior art, the drawings that are required in the embodiments or the description of the prior art will be briefly described, it being obvious that the drawings in the following description are only some embodiments of the invention, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art. In the drawings:
fig. 1 is a flowchart of a method for scheduling a flow of heterogeneous RPA products according to an embodiment of the present invention;
FIG. 2 is a schematic diagram of a flow schedule for heterogeneous RPA products in an embodiment of the invention;
FIG. 3 is a schematic diagram of writing configuration information according to an embodiment of the present invention;
fig. 4 is a schematic diagram of a flow scheduling apparatus for heterogeneous RPA products according to an embodiment of the present invention;
fig. 5 is another schematic diagram of a flow scheduling apparatus for heterogeneous RPA products according to an embodiment of the present invention.
Detailed Description
For the purpose of making the objects, technical solutions and advantages of the embodiments of the present invention more apparent, the embodiments of the present invention will be described in further detail with reference to the accompanying drawings. The exemplary embodiments of the present invention and their descriptions herein are for the purpose of explaining the present invention, but are not to be construed as limiting the invention.
First, terms involved in the embodiments of the present invention are explained.
RPA (robot flow automation, robotic Process Automation): the method takes man-machine interaction automation technology as a leading part, simulates the operation of human on a computer, and realizes the automation of the workflow.
RPA application flow: the robot is a rule program for executing the target job task, and a developer writes codes according to the service rules and distributes the codes to the corresponding RPA for execution.
Fig. 1 is a flowchart of a flow scheduling method of a heterogeneous RPA product according to an embodiment of the present invention, including:
step 101, after receiving a flow scheduling request of an RPA product of a calling party, acquiring RPA interface information corresponding to the RPA product;
step 102, obtaining PRA manufacturer interface information corresponding to an RPA product according to the RPA interface information;
step 103, determining the parameter entering field of the RPA manufacturer according to the parameter entering field of the calling party and the PRA manufacturer interface information;
step 104, according to the RPA manufacturer parameter field, the RPA interface information and the PRA manufacturer interface information, manufacturer interface calling data are assembled, wherein the manufacturer interface calling data comprise the RPA manufacturer parameter field, the manufacturer interface number and the interface access information;
step 105, pushing the vendor interface call data to a corresponding RPA vendor service through a PRA vendor interface corresponding to the vendor interface number, wherein the RPA vendor service calls up an RPA product according to a machine specified in the interface access information;
step 106, receiving an RPA product calling result fed back by the RPA manufacturer service;
step 107, determining parameter output fields of the calling party according to the RPA product calling result, and feeding back the parameter output fields to the calling party.
Compared with the technical scheme that when a plurality of RPA products are subjected to flow scheduling, a plurality of RPA controllers of different manufacturers are required to be accessed, namely, a plurality of manufacturers are required to be adapted, the embodiment of the invention adopts one RPA product adapter, after receiving a flow call request, RPA interface information and PRA manufacturer interface information can be sequentially acquired to determine the parameter entering field of the RPA manufacturer, namely, the RPA manufacturer service corresponding to the selected RPA product is determined, and because the RPA interface information designates a machine, the RPA manufacturer service can start the RPA product according to the designated machine to complete the call, return the call result, and then determine the parameter exiting field of the calling party and feed back to the calling party to complete the whole call flow, so that the flow call of the cross-RPA product is realized, the efficiency is high, the novel RPA product can be quickly adapted, development and redeployment are not needed, and the labor is saved. Each step is described in detail below.
Referring to fig. 2, which is a schematic diagram of flow scheduling of heterogeneous RPA products in an embodiment of the present invention, the design concept is that interfaces with the same function make unified standards on a caller, for example, the caller starts the RPA robot, and the caller starts the RPA robot according to the standard interface, and the interfaces are routed to different RPA products through an adapter to start the RPA robot to execute the flow.
In step 101, after receiving a flow scheduling request of an RPA product of a calling party, obtaining RPA interface information corresponding to the RPA product;
step 101 corresponds to RPA interface management in fig. 2, and in an embodiment, the flow scheduling request includes a standard interface name of an RPA product;
the step 101 specifically includes:
obtaining RPA interface information according to the standard interface name of the RPA product in the flow scheduling request; the RPA interface information comprises a standard interface name, a standard interface number and standard interface access information, wherein the standard interface access information comprises a specified machine IP;
for example, the standard interface names are start RPA robot, stop RPA robot, query robot state, process import, process execution, process suspension, and query process progress, and the standard interface names and standard interface numbers in the RPA interface are uniformly approved by all callers. The RPA interface information may be in tabular form with standard interface numbers as primary keys.
In step 102, according to the RPA interface information, PRA vendor interface information corresponding to an RPA product is obtained;
step 102 corresponds to vendor interface management in fig. 2, and step 102 specifically includes:
and obtaining PRA manufacturer interface information according to the standard interface number in the RPA interface information, wherein the PRA manufacturer interface information comprises a manufacturer number, a standard interface number, a manufacturer interface name and manufacturer interface access information, and the manufacturer interface access information comprises one or any combination of a manufacturer interface url, a manufacturer access protocol (jdbc/restful and the like) and dependent data.
In addition, if more vendor information is desired, it may be implemented by RPA vendor management, which includes vendor number, vendor name, etc. The PRA vendor interface information may be in tabular form.
In step 103, determining an RPA manufacturer parameter entry field according to the parameter entry field of the calling party and PRA manufacturer interface information;
step 103 corresponds to the mapping of the interface parameter fields in fig. 2, and step 103 specifically includes:
inquiring the mapping relation of the vendor interface entering field according to the entering field of the calling party, the standard interface number and the vendor interface number in the PRA vendor interface information, and determining the RPA vendor entering field, wherein the mapping relation of the vendor interface entering field describes the mapping relation of the entering field and the vendor entering field by taking the standard interface number and the vendor interface number as a main key.
The vendor interface entry field mapping relationship may be a list, the entry field including an entry field name and an entry field type, and the vendor entry field including a vendor entry field name and a vendor entry field type.
In step 104, according to the RPA manufacturer parameter entry field, RPA interface information and PRA manufacturer interface information, manufacturer interface call data is assembled, wherein the manufacturer interface call data comprises the RPA manufacturer parameter entry field, a manufacturer interface number and interface access information;
the interface access information comprises standard interface access information and manufacturer interface access information;
in step 105, pushing the vendor interface call data to a corresponding RPA vendor service through a PRA vendor interface corresponding to the vendor interface number, where the RPA vendor service calls up an RPA product according to a machine specified in the interface access information;
specifically, the specified machine refers to the specified machine IP, and the agnet client of the corresponding machine invokes the RPA application package to perform the RPA task. And when the execution is finished, calling back the interface of the adapter service of the RPA platform.
In step 106, receiving an RPA product calling result fed back by the RPA manufacturer service; specifically, the RPA vendor service invokes the PRA vendor interface provided by the RPA product adapter to feed back the invocation result.
In step 107, according to the RPA product calling result, the parameter-out field of the calling party is determined and fed back to the calling party.
Step 107 corresponds to the mapping of the interface parameter-out field, and step 107 specifically includes:
according to the PRA manufacturer interface number of the received RPA product calling result, PRA manufacturer interface information is obtained;
inquiring the mapping relation of the parameter-outputting fields of the manufacturer interface according to the PRA manufacturer interface information and the standard interface number in the flow call request, and determining the parameter-outputting fields of the caller, wherein the mapping relation of the parameter-outputting fields of the manufacturer interface describes the mapping relation of the parameter-outputting fields of the manufacturer with the standard interface number and the manufacturer interface number as main keys.
The vendor interface parameter field mapping relationship may be in a tabular form. The out-of-parameters field includes out-of-parameters field name and out-of-parameters field type, and the vendor out-of-parameters field includes vendor out-of-parameters field name and vendor out-of-parameters field type.
In one embodiment, after determining the parameter out field of the caller according to the RPA product call result, the method further comprises:
filtering out the parameter-out fields required by the user according to the filtering rules of the calling party on the parameter-out fields;
and feeding back parameter output fields required by the user to the calling party.
Here, the filtering of the response fields in fig. 2 corresponds, because some of the parameter-out fields may not be needed by the user, and thus, predefined filtering rules may be added to implement the filtering.
Referring to fig. 3, in an embodiment, the method further comprises:
receiving configuration information of a new RPA product input by a user through a visual page of a configuration service;
and verifying the configuration information, and writing the configuration information which passes verification into a DB server, wherein the configuration information comprises RPA interface information, PRA manufacturer interface information, a manufacturer interface parameter-entering field mapping relation and a manufacturer interface parameter-exiting field mapping relation.
After the configuration information is written to the DB server, the RPA product adapter reads the configuration information from the DB server. In the running state process, the configuration information is supported to be dynamically configured, the configuration information is effective in real time, redeployment is not needed, the development period is greatly shortened, the RPA scheduling efficiency is improved, and the labor cost is saved.
In an embodiment, the configuration information further includes authentication management information, where the authentication management information includes a vendor number, an authentication mode, an authentication user, an authentication password, and a symmetric key;
after receiving the authentication management information, the configuration service encrypts and stores the authentication management information;
before calling the RPA manufacturer service corresponding to the RPA product according to the RPA manufacturer parameter entering field, the RPA interface information and the PRA manufacturer interface information, the method further comprises the following steps:
acquiring authentication management information according to manufacturer numbers in PRA manufacturer interface information;
according to the RPA manufacturer parameter entering field, the RPA interface information and the PRA manufacturer interface information, calling the RPA manufacturer service corresponding to the RPA product, comprising:
if the authentication mode in the authentication management information is a token mode, acquiring the authentication token from the cache, and calling the RPA manufacturer service corresponding to the RPA product according to the authentication token, the RPA manufacturer access field, the RPA interface information and the PRA manufacturer interface information; after verifying the validity of the authentication token, the RPA manufacturer service calls up an RPA product according to a machine designated by the RPA interface information; the cache periodically acquires an authentication token from the RPA manufacturer service according to the authentication user and the authentication password;
if the authentication mode in the authentication management information is a symmetric key mode, calling the RPA manufacturer service corresponding to the RPA product according to the symmetric key, the RPA manufacturer parameter entering field, the RPA interface information and the PRA manufacturer interface information; and after the RPA manufacturer service decrypts the symmetric key correctly, calling up the RPA product according to the machine specified by the RPA interface information.
It should be noted that the authentication token may be present in the database in addition to the cache.
In one embodiment, receiving configuration information of a new RPA product input by a user through a visualization page of a configuration service includes:
when a user edits a preset field of configuration information on a visual page of a configuration service, responding to a click instruction of the user, and generating a processing template of the preset field;
input data of a user on the processing template is received.
In specific implementation, the prediction field may include a vendor number and a vendor interface number, which may be determined according to actual situations, and a processing template of the preset field may also be set.
The processing templates may take many forms, such as json strings and xml messages.
The following is a json string with business meaning, and the structure is as follows:
[
{"Value":"xxxxxx","Type":1,"Name":"{xxxxxx-xxxxxx-xxxxxx}"},
{"Value":"xxxxxx","Type":2,"Name":"AAAAAA"},
{"Value":"xxxxxx","Type":3,"Name":"{xxxxxx-xxxxxx-xxxxxx}"}
]
the following is a string of xml messages, the structure is as follows:
in the method provided by the embodiment of the invention, after receiving a flow scheduling request of an RPA product of a calling party, RPA interface information corresponding to the RPA product is obtained; according to the RPA interface information, PRA manufacturer interface information corresponding to the RPA product is obtained; determining an RPA manufacturer parameter entering field according to the parameter entering field of the calling party and PRA manufacturer interface information; calling RPA manufacturer service corresponding to the RPA product according to the RPA manufacturer parameter entering field, the RPA interface information and the PRA manufacturer interface information; the RPA manufacturer service calls up an RPA product according to a machine specified by the RPA interface information; receiving an RPA product calling result fed back by an RPA manufacturer service; and determining a parameter output field of the calling party according to the RPA product calling result, and feeding back the parameter output field to the calling party. Compared with the technical scheme that when a plurality of RPA products are subjected to flow scheduling, a plurality of RPA controllers of different manufacturers are required to be accessed, namely, a plurality of manufacturers are required to be adapted, the embodiment of the invention adopts one RPA product adapter, after receiving a flow call request, RPA interface information and PRA manufacturer interface information can be acquired in sequence to determine the parameter entering field of the RPA manufacturer, namely, the RPA manufacturer service corresponding to the selected RPA product is selected, and as the RPA interface information designates a machine, the RPA manufacturer service can start the RPA product according to the designated machine to complete the call, return the call result, and then determine the parameter exiting field of the calling party and feed back to the calling party to complete the whole call flow, so that the flow call of the cross-RPA product is realized, the efficiency is high, the novel RPA product can be adapted quickly, development and redeployment are not needed, manpower is saved, secondary code development is not needed, and the method is efficient and convenient. In addition, the scheme of the invention can also support a visual and configurable mode to realize the access of new RPA products and support agile production.
The embodiment of the invention also provides a flow scheduling device of the heterogeneous RPA product, which is described in the following embodiment. Because the principle of the device for solving the problem is similar to that of the flow scheduling method of the heterogeneous RPA product, the implementation of the device can be referred to the implementation of the flow scheduling method of the heterogeneous RPA product, and the repetition is omitted.
Fig. 4 is a schematic diagram of a flow scheduling apparatus for heterogeneous RPA products according to an embodiment of the present invention, including:
the RPA interface information obtaining module 401 is configured to obtain RPA interface information corresponding to an RPA product after receiving a flow scheduling request of the RPA product of the caller;
a PRA vendor interface information obtaining module 402, configured to obtain PRA vendor interface information corresponding to an RPA product according to the RPA interface information;
the RPA manufacturer parameter entry field determining module 403 is configured to determine an RPA manufacturer parameter entry field according to the parameter entry field of the caller and PRA manufacturer interface information;
the vendor interface call data assembling module 404 is configured to assemble vendor interface call data according to the RPA vendor parameter entry field, the RPA interface information, and the PRA vendor interface information, where the vendor interface call data includes the RPA vendor parameter entry field, the vendor interface number, and the interface access information;
the service calling module 405 pushes the vendor interface calling data to a corresponding RPA vendor service through a PRA vendor interface corresponding to the vendor interface number, where the RPA vendor service calls up an RPA product according to a machine specified in the interface access information;
a calling result feedback module 406, configured to receive an RPA product calling result fed back by the RPA vendor service;
the parameter-out field feedback module 407 is configured to determine a parameter-out field of the caller according to the RPA product calling result, and feed back the parameter-out field to the caller.
In an embodiment, the flow scheduling request includes a standard interface name of an RPA product;
the RPA interface information acquisition module is specifically configured to:
obtaining RPA interface information according to the standard interface name of the RPA product in the flow scheduling request; the RPA interface information comprises a standard interface name, a standard interface number and standard interface access information, wherein the standard interface access information comprises a specified machine IP;
the PRA manufacturer interface information obtaining module is specifically used for:
and obtaining PRA manufacturer interface information according to the standard interface number in the RPA interface information, wherein the PRA manufacturer interface information comprises a manufacturer number, a standard interface number, a manufacturer interface name and manufacturer interface access information, and the manufacturer interface access information comprises one or any combination of a manufacturer interface url, a manufacturer access protocol (jdbc/restful and the like) and dependent data.
In one embodiment, the RPA vendor reference field determination module is specifically configured to:
inquiring the mapping relation of the vendor interface entering field according to the entering field of the calling party, the standard interface number and the vendor interface number in the PRA vendor interface information, and determining the RPA vendor entering field, wherein the mapping relation of the vendor interface entering field describes the mapping relation of the entering field and the vendor entering field by taking the standard interface number and the vendor interface number as a main key.
In one embodiment, the interface access information includes standard interface access information and vendor interface access information; the RPA vendor service invokes the RPA product according to the machine IP specified by the standard interface access information.
In one embodiment, the parameter-out field feedback module is specifically configured to:
according to the PRA manufacturer interface number of the received RPA product calling result, PRA manufacturer interface information is obtained;
inquiring the mapping relation of the parameter-outputting fields of the manufacturer interface according to the PRA manufacturer interface information and the standard interface number in the flow call request, and determining the parameter-outputting fields of the caller, wherein the mapping relation of the parameter-outputting fields of the manufacturer interface describes the mapping relation of the parameter-outputting fields of the manufacturer with the standard interface number and the manufacturer interface number as main keys.
Referring to fig. 5, the apparatus further includes a response field filtering module 501 configured to:
after determining the parameter-out field of the calling party according to the RPA product calling result, filtering out the parameter-out field required by the user according to the filtering rule of the parameter-out field of the calling party;
and feeding back parameter output fields required by the user to the calling party.
In an embodiment, the apparatus further comprises a configuration module 502 for:
receiving configuration information of a new RPA product input by a user through a visual page of a configuration service;
and verifying the configuration information, and writing the configuration information which passes verification into a DB server, wherein the configuration information comprises RPA interface information, PRA manufacturer interface information, a manufacturer interface parameter-entering field mapping relation and a manufacturer interface parameter-exiting field mapping relation.
In the device provided by the embodiment of the invention, after receiving the flow scheduling request of the RPA product of the calling party, RPA interface information corresponding to the RPA product is obtained; according to the RPA interface information, PRA manufacturer interface information corresponding to the RPA product is obtained; determining an RPA manufacturer parameter entering field according to the parameter entering field of the calling party and PRA manufacturer interface information; calling RPA manufacturer service corresponding to the RPA product according to the RPA manufacturer parameter entering field, the RPA interface information and the PRA manufacturer interface information; the RPA manufacturer service calls up an RPA product according to a machine specified by the RPA interface information; receiving an RPA product calling result fed back by an RPA manufacturer service; and determining a parameter output field of the calling party according to the RPA product calling result, and feeding back the parameter output field to the calling party. Compared with the technical scheme that when a plurality of RPA products are subjected to flow scheduling, a plurality of RPA controllers of different manufacturers are required to be accessed, namely, a plurality of manufacturers are required to be adapted, the embodiment of the invention adopts one RPA product adapter, after receiving a flow call request, RPA interface information and PRA manufacturer interface information can be sequentially acquired to determine the parameter entering field of the RPA manufacturer, namely, the RPA manufacturer service corresponding to the selected RPA product is determined, and because the RPA interface information designates a machine, the RPA manufacturer service can start the RPA product according to the designated machine to complete the call, return the call result, and then determine the parameter exiting field of the calling party and feed back to the calling party to complete the whole call flow, so that the flow call of the cross-RPA product is realized, the efficiency is high, the novel RPA product can be quickly adapted, development and redeployment are not needed, and the labor is saved. In addition, the scheme of the invention can also support a visual and configurable mode to realize the access of new RPA products and support agile production.
The embodiment of the invention also provides a computer device which comprises a memory, a processor and a computer program stored on the memory and capable of running on the processor, wherein the processor realizes the flow scheduling method of the heterogeneous RPA product when executing the computer program.
The embodiment of the invention also provides a computer readable storage medium, wherein the computer readable storage medium stores a computer program, and the computer program realizes the flow scheduling method of the heterogeneous RPA product when being executed by a processor.
The embodiment of the invention also provides a computer program product, which comprises a computer program, and the computer program realizes the flow scheduling method of the heterogeneous RPA product when being executed by a processor.
It will be appreciated by those skilled in the art that embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
The foregoing description of the embodiments has been provided for the purpose of illustrating the general principles of the invention, and is not meant to limit the scope of the invention, but to limit the invention to the particular embodiments, and any modifications, equivalents, improvements, etc. that fall within the spirit and principles of the invention are intended to be included within the scope of the invention.
Claims (13)
1. The flow scheduling method of the heterogeneous RPA product is characterized by being applied to an RPA product adapter and comprising the following steps:
after receiving a flow scheduling request of an RPA product of a calling party, acquiring RPA interface information corresponding to the RPA product;
according to the RPA interface information, PRA manufacturer interface information corresponding to the RPA product is obtained;
determining an RPA manufacturer parameter entering field according to the parameter entering field of the calling party and PRA manufacturer interface information;
according to the RPA manufacturer parameter entering field, the RPA interface information and the PRA manufacturer interface information, manufacturer interface calling data are assembled, wherein the manufacturer interface calling data comprise the RPA manufacturer parameter entering field, the manufacturer interface number and the interface access information;
pushing the manufacturer interface call data to a corresponding RPA manufacturer service through a PRA manufacturer interface corresponding to the manufacturer interface number, wherein the RPA manufacturer service calls up an RPA product according to a machine specified in the interface access information;
receiving an RPA product calling result fed back by an RPA manufacturer service;
and determining a parameter output field of the calling party according to the RPA product calling result, and feeding back the parameter output field to the calling party.
2. The method of claim 1, wherein the flow scheduling request includes a standard interface name of an RPA product;
after receiving a flow scheduling request of an RPA product of a calling party, acquiring RPA interface information corresponding to the RPA product, including:
obtaining RPA interface information according to the standard interface name of the RPA product in the flow scheduling request; the RPA interface information comprises a standard interface name, a standard interface number and standard interface access information, wherein the standard interface access information comprises a specified machine IP;
according to the RPA interface information, PRA manufacturer interface information corresponding to the RPA product is obtained, which comprises the following steps:
and obtaining PRA manufacturer interface information according to the standard interface number in the RPA interface information, wherein the PRA manufacturer interface information comprises a manufacturer number, a standard interface number, a manufacturer interface name and manufacturer interface access information, and the manufacturer interface access information comprises one or any combination of a manufacturer interface url, a manufacturer access protocol and dependent data.
3. The method of claim 2, wherein determining the RPA vendor entry field based on the caller entry field and the PRA vendor interface information comprises:
inquiring the mapping relation of the vendor interface entering field according to the entering field of the calling party, the standard interface number and the vendor interface number in the PRA vendor interface information, and determining the RPA vendor entering field, wherein the mapping relation of the vendor interface entering field describes the mapping relation of the entering field and the vendor entering field by taking the standard interface number and the vendor interface number as a main key.
4. The method of claim 3, wherein the interface access information includes standard interface access information and vendor interface access information; the RPA vendor service invokes the RPA product according to the machine IP specified by the standard interface access information.
5. The method of claim 1, wherein determining the parameter out field of the caller based on the RPA product call result comprises:
according to the PRA manufacturer interface number of the received RPA product calling result, PRA manufacturer interface information is obtained;
inquiring the mapping relation of the parameter-outputting fields of the manufacturer interface according to the PRA manufacturer interface information and the standard interface number in the flow call request, and determining the parameter-outputting fields of the caller, wherein the mapping relation of the parameter-outputting fields of the manufacturer interface describes the mapping relation of the parameter-outputting fields of the manufacturer with the standard interface number and the manufacturer interface number as main keys.
6. The method of claim 1, further comprising, after determining the parameter out field of the caller based on the RPA product call result:
filtering out the parameter-out fields required by the user according to the filtering rules of the calling party on the parameter-out fields;
and feeding back parameter output fields required by the user to the calling party.
7. The method as recited in claim 1, further comprising:
receiving configuration information of a new RPA product input by a user through a visual page of a configuration service;
and verifying the configuration information, and writing the configuration information which passes verification into a DB server, wherein the configuration information comprises RPA interface information, PRA manufacturer interface information, a manufacturer interface parameter-entering field mapping relation and a manufacturer interface parameter-exiting field mapping relation.
8. The method of claim 7, wherein the configuration information further comprises authentication management information including vendor number, authentication mode, authenticated user, authentication password, and symmetric key;
after receiving the authentication management information, the configuration service encrypts and stores the authentication management information;
before calling the RPA manufacturer service corresponding to the RPA product according to the RPA manufacturer parameter entering field, the RPA interface information and the PRA manufacturer interface information, the method further comprises the following steps:
acquiring authentication management information according to manufacturer numbers in PRA manufacturer interface information;
according to the RPA manufacturer parameter entering field, the RPA interface information and the PRA manufacturer interface information, calling the RPA manufacturer service corresponding to the RPA product, comprising:
if the authentication mode in the authentication management information is a token mode, acquiring the authentication token from the cache, and calling the RPA manufacturer service corresponding to the RPA product according to the authentication token, the RPA manufacturer access field, the RPA interface information and the PRA manufacturer interface information; after verifying the validity of the authentication token, the RPA manufacturer service calls up an RPA product according to a machine designated by the RPA interface information; the cache periodically acquires an authentication token from the RPA manufacturer service according to the authentication user and the authentication password;
if the authentication mode in the authentication management information is a symmetric key mode, calling the RPA manufacturer service corresponding to the RPA product according to the symmetric key, the RPA manufacturer parameter entering field, the RPA interface information and the PRA manufacturer interface information; and after the RPA manufacturer service decrypts the symmetric key correctly, calling up the RPA product according to the machine specified by the RPA interface information.
9. The method of claim 7, wherein receiving configuration information of a new RPA product entered by a user through a visualization page of a configuration service comprises:
when a user edits a preset field of configuration information on a visual page of a configuration service, responding to a click instruction of the user, and generating a processing template of the preset field;
input data of a user on the processing template is received.
10. A process scheduling apparatus for heterogeneous RPA products, comprising:
the RPA interface information acquisition module is used for acquiring RPA interface information corresponding to the RPA product after receiving a flow scheduling request of the RPA product of the calling party;
the PRA manufacturer interface information obtaining module is used for obtaining PRA manufacturer interface information corresponding to the RPA product according to the RPA interface information;
the RPA manufacturer parameter entering field determining module is used for determining the RPA manufacturer parameter entering field according to the parameter entering field of the calling party and the PRA manufacturer interface information;
the manufacturer interface call data assembly module is used for assembling manufacturer interface call data according to the RPA manufacturer parameter entering field, the RPA interface information and the PRA manufacturer interface information, wherein the manufacturer interface call data comprises the RPA manufacturer parameter entering field, the manufacturer interface number and the interface access information;
the service calling module pushes the manufacturer interface calling data to the corresponding RPA manufacturer service through the PRA manufacturer interface corresponding to the manufacturer interface number, wherein the RPA manufacturer service calls up an RPA product according to a machine appointed in the interface access information;
the calling result feedback module is used for receiving the RPA product calling result fed back by the RPA manufacturer service;
and the parameter-out field feedback module is used for determining parameter-out fields of the calling party according to the RPA product calling result and feeding back the parameter-out fields to the calling party.
11. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the method of any of claims 1 to 9 when executing the computer program.
12. A computer readable storage medium, characterized in that the computer readable storage medium stores a computer program which, when executed by a processor, implements the method of any of claims 1 to 9.
13. A computer program product, characterized in that the computer program product comprises a computer program which, when executed by a processor, implements the method of any of claims 1 to 9.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311568662.4A CN117519779A (en) | 2023-11-22 | 2023-11-22 | Flow scheduling method and device for heterogeneous RPA products |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311568662.4A CN117519779A (en) | 2023-11-22 | 2023-11-22 | Flow scheduling method and device for heterogeneous RPA products |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117519779A true CN117519779A (en) | 2024-02-06 |
Family
ID=89747362
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311568662.4A Pending CN117519779A (en) | 2023-11-22 | 2023-11-22 | Flow scheduling method and device for heterogeneous RPA products |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117519779A (en) |
-
2023
- 2023-11-22 CN CN202311568662.4A patent/CN117519779A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109460223B (en) | API gateway management system and method thereof | |
| CN112650766A (en) | Database data operation method, system and server | |
| CN110321283B (en) | Interface test case generation method and device, computer device and storage medium | |
| CN110781180B (en) | Data screening method and data screening device | |
| CN113505520A (en) | Method, device and system for supporting heterogeneous federated learning | |
| CN110659018A (en) | Flow engine implementation method and device | |
| WO2021139778A1 (en) | System scheduling workflow generation method, system, apparatus, and computer readable storage medium | |
| CN104133676A (en) | Function execution method and function execution device based on scripts | |
| CN111784318A (en) | Data processing method and device, electronic equipment and storage medium | |
| CN111158800B (en) | Method and device for constructing task DAG based on mapping relation | |
| CN116661978B (en) | Distributed flow processing method and device and distributed business flow engine | |
| CN113609101A (en) | Real-time data task issuing method and device, electronic equipment and storage medium | |
| CN110471896B (en) | Data processing method, system and server | |
| CN117519779A (en) | Flow scheduling method and device for heterogeneous RPA products | |
| CN110941658A (en) | Data export method, device, server and storage medium | |
| CN112418796B (en) | Sub-process task node activation method and device, electronic equipment and storage medium | |
| CN115080663A (en) | Distributed database synchronization method, system, device and medium | |
| CN114610803A (en) | Data processing method and device, electronic equipment and storage medium | |
| CN113867714A (en) | Automatic code generation method adaptive to multiple languages | |
| CN113239297A (en) | Message pushing method, system and storage medium | |
| CN114785847B (en) | Network control software development configuration method, terminal and storage medium | |
| TWI729620B (en) | Module-oriented flow programming method | |
| TWI774469B (en) | Management system for program compilation and method for operating the system | |
| CN110990475B (en) | Batch task inserting method and device, computer equipment and storage medium | |
| CN111752951B (en) | Database table processing method and device |
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 |