A visualization-based RPA multi-scenario orchestration method, system, device, and media

Abstract

This invention provides a visualization-based multi-scenario RPA orchestration method, system, device, and medium in the field of RPA orchestration technology. The method includes the following steps: Step S10, visually orchestrating each sub-component in an RPA designer to obtain several components; Step S20, visually orchestrating each component to obtain the corresponding RPA, and setting the DSL for each RPA; Step S30, verifying each RPA; Step S40, converting the DSL into execution instructions and sending them to a browser to automatically execute the corresponding RPA. The advantages of this invention are: greatly improving the readability and efficiency of RPA orchestration.

Description

Technical Field

[0001] This invention relates to the field of RPA orchestration technology, and in particular to a visualization-based RPA multi-scenario orchestration method, system, device and medium. Background Technology

[0002] RPA stands for Robotic Process Automation, and an RPA designer is an IDE tool based on low-code, visual technology that allows users to arrange automated workflows by dragging and dropping with a mouse. A single RPA process is the simplest application scenario. However, due to the diverse automation needs of users, the following situations also exist in practical applications: 1. An RPA may consist of dozens to hundreds of steps; 2. One RPA needs to be executed immediately after another; 3. A complete automation requirement involves different business systems, for example: first downloading operational reports from a cross-border e-commerce platform's seller platform, and then importing the operational reports into the user's ERP system; 4. A complete automation requirement involves business systems on different platforms, for example: the user's ERP system is a desktop application, not a web application.

[0003] For PRA orchestration, the smallest granular function or instruction is usually abstracted into a component. An RPA consists of several components, and different application scenarios have different representation methods. For example, an RPA is displayed by a view, and multiple RPAs are displayed by a project (a collection of multiple views). Due to the complexity of real-world application scenarios, the following problems arise:

[0004] The views are fragmented, with different RPAs described independently, making it impossible to view the entire RPA from a holistic perspective. This requires frequent switching between multiple independent views (files), and when dealing with complex RPAs, the number of components is very large, resulting in poor readability and low orchestration efficiency.

[0005] Therefore, how to provide a visualization-based multi-scenario RPA orchestration method, system, device, and medium to improve the readability and efficiency of RPA orchestration has become an urgent technical problem to be solved. Summary of the Invention

[0006] The technical problem to be solved by the present invention is to provide a visualization-based multi-scenario orchestration method, system, device and medium for RPA, so as to improve the readability and efficiency of RPA orchestration.

[0007] In a first aspect, the present invention provides a visualization-based multi-scenario orchestration method for RPA, comprising the following steps:

[0008] Step S10: Visually arrange each sub-component in the RPA designer to obtain several components;

[0009] Step S20: Visually arrange each of the components to obtain the corresponding RPA, and set the DSL of each RPA;

[0010] Step S30: Verify each of the RPAs;

[0011] Step S40: Convert the DSL into execution instructions and send them to the browser to automatically execute the corresponding RPA.

[0012] Further, step S10 specifically includes:

[0013] The frequency of use of the pairing combinations between each sub-component is counted. On the RPA designer, the sub-components with a usage frequency greater than a preset frequency threshold are visualized and arranged, and then encapsulated into several components.

[0014] The element includes at least one sub-element.

[0015] Further, step S20 specifically includes:

[0016] For different business systems and platforms, the RPA components are visually orchestrated in the RPA designer to obtain the corresponding RPA, and the DSL of each RPA is set.

[0017] Step S30 specifically involves:

[0018] In the RPA designer, each component of each RPA is expanded into a sub-component, or each sub-component is collapsed into a component, thereby enabling a global check of each RPA.

[0019] Further, step S40 specifically includes:

[0020] The DSL is converted into execution instructions that match the server or client, and then the execution instructions are sent to the browser of the server or client to automatically execute the corresponding RPA.

[0021] Secondly, the present invention provides a visualization-based RPA multi-scenario orchestration system, comprising the following modules:

[0022] The sub-component encapsulation module is used to visually arrange each sub-component in the RPA designer to obtain several components;

[0023] The RPA orchestration module is used to visually orchestrate each of the aforementioned components to obtain the corresponding RPA, and to set the DSL for each of the aforementioned RPAs;

[0024] The RPA verification module is used to verify each of the RPAs.

[0025] The RPA execution module is used to convert the DSL into execution instructions and send them to the browser to automatically execute the corresponding RPA.

[0026] Furthermore, the sub-component packaging module specifically comprises:

[0027] The frequency of use of the pairing combinations between each sub-component is counted. On the RPA designer, the sub-components with a usage frequency greater than a preset frequency threshold are visualized and arranged, and then encapsulated into several components.

[0028] The element includes at least one sub-element.

[0029] Furthermore, the RPA orchestration module specifically comprises:

[0030] For different business systems and platforms, the RPA components are visually orchestrated in the RPA designer to obtain the corresponding RPA, and the DSL of each RPA is set.

[0031] The RPA verification module is specifically as follows:

[0032] In the RPA designer, each component of each RPA is expanded into a sub-component, or each sub-component is collapsed into a component, thereby enabling a global check of each RPA.

[0033] Furthermore, the RPA execution module specifically comprises:

[0034] The DSL is converted into execution instructions that match the server or client, and then the execution instructions are sent to the browser of the server or client to automatically execute the corresponding RPA.

[0035] Thirdly, the present invention provides a visualization-based RPA multi-scenario orchestration device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the method described in the first aspect.

[0036] Fourthly, the present invention provides a visualization-based RPA multi-scenario orchestration medium on which a computer program is stored, which, when executed by a processor, implements the method described in the first aspect.

[0037] One or more technical solutions provided in the embodiments of the present invention have at least the following technical effects or advantages:

[0038] By directly encapsulating commonly used sub-components into components, the encapsulated components can be reused and arranged directly during RPA orchestration. This greatly reduces the number of components displayed on the RPA designer, enhances RPA readability, and significantly reduces the difficulty of RPA orchestration. By collapsing and expanding sub-components, RPA can be checked globally without switching between multiple independent files. Ultimately, this greatly improves the readability and efficiency of RPA orchestration and facilitates RPA maintenance.

[0039] The above description is merely an overview of the technical solution of the present invention. In order to better understand the technical means of the present invention and to implement it in accordance with the contents of the specification, and in order to make the above and other objects, features and advantages of the present invention more apparent and understandable, specific embodiments of the present invention are described below. Attached Figure Description

[0040] The present invention will be further described below with reference to the accompanying drawings and embodiments.

[0041] Figure 1 This is a flowchart of a visualization-based multi-scenario orchestration method for RPA according to the present invention.

[0042] Figure 2 This is a schematic diagram of the structure of a visualization-based RPA multi-scenario orchestration system according to the present invention.

[0043] Figure 3 This is a schematic diagram of the structure of a visualization-based RPA multi-scenario orchestration device according to the present invention.

[0044] Figure 4 This is a schematic diagram of the structure of a visualization-based RPA multi-scenario orchestration medium according to the present invention. Detailed Implementation

[0045] This application provides a visualization-based multi-scenario RPA orchestration method, system, device, and medium to improve the readability and efficiency of RPA orchestration.

[0046] The technical solution in this application embodiment has the following general idea: commonly used sub-components are directly encapsulated into components, and the encapsulated components are reused and arranged directly during RPA orchestration to reduce the number of components displayed and improve the readability and efficiency of RPA orchestration.

[0047] Example 1

[0048] This embodiment provides a visualization-based RPA multi-scenario orchestration method, such as... Figure 1 As shown, it includes the following steps:

[0049] Step S10: Visually arrange each sub-component in the RPA designer to obtain several components;

[0050] Step S20: Visually arrange each of the components to obtain the corresponding RPA, and set the DSL of each RPA;

[0051] Step S30: Verify each of the RPAs;

[0052] Step S40: Convert the DSL into execution instructions and send them to the browser to automatically execute the corresponding RPA.

[0053] Step S10 specifically involves:

[0054] The frequency of use of the pairing combinations between each sub-component is counted. On the RPA designer, the sub-components with a usage frequency greater than a preset frequency threshold are visualized and arranged, and then encapsulated into several components.

[0055] The element includes at least one sub-element, meaning that the granularity of the element can be large or small, and can be set as needed.

[0056] For example, component 1 → component 2 → component 3 → component 4 form an RPA. Component 1 is composed of sub-component 1, component 2 is composed of sub-component 2, component 3 is composed of sub-component 1 and sub-component 5, and component 4 is composed of sub-component 2, sub-component 3 and sub-component 6. If the combination of component 3 → component 4 is used frequently, component 3 and component 4 can be combined into component 5 for reuse. By reusing the sub-components, the programming efficiency and reusability can be greatly improved.

[0057] That is, the elements and sub-elements described in this application can be self-contained and infinitely nested. For example, A and B form the AB element, AB and C form the ABC element, and ABC and D are arranged into RPA, which is nested at 3 levels.

[0058] Step S20 specifically involves:

[0059] For different business systems and platforms, the RPA components are visually orchestrated in the RPA designer to obtain the corresponding RPA, and the DSL of each RPA is set.

[0060] For example, the RPA executed in business system A includes: component a1 → component a2 → component a3 → component a4; the RPA executed in business system B includes: component b1 → component b2 → component b3 → component b4.

[0061] Step S30 specifically involves:

[0062] In the RPA designer, each component of each RPA can be expanded into sub-components, or each sub-component can be collapsed into a component, thereby enabling global verification of each RPA. Collapsing the sub-components can increase the readability of the RPA.

[0063] Step S40 specifically involves:

[0064] The DSL is converted into execution instructions that match the server or client, and then the execution instructions are sent to the browser of the server or client to automatically execute the corresponding RPA. Since the DSL description of RPA is platform-independent, it can be converted into execution instructions that the server or client can recognize, and the execution of the two RPAs can be scheduled respectively.

[0065] Example 2

[0066] This embodiment provides a visualization-based RPA multi-scenario orchestration system, such as... Figure 2 As shown, it includes the following modules:

[0067] The sub-component encapsulation module is used to visually arrange each sub-component in the RPA designer to obtain several components;

[0068] The RPA orchestration module is used to visually orchestrate each of the aforementioned components to obtain the corresponding RPA, and to set the DSL for each of the aforementioned RPAs;

[0069] The RPA verification module is used to verify each of the RPAs.

[0070] The RPA execution module is used to convert the DSL into execution instructions and send them to the browser to automatically execute the corresponding RPA.

[0071] The sub-component packaging module is specifically:

[0072] The frequency of use of the pairing combinations between each sub-component is counted. On the RPA designer, the sub-components with a usage frequency greater than a preset frequency threshold are visualized and arranged, and then encapsulated into several components.

[0073] The element includes at least one sub-element, meaning that the granularity of the element can be large or small, and can be set as needed.

[0074] For example, component 1 → component 2 → component 3 → component 4 form an RPA. Component 1 is composed of sub-component 1, component 2 is composed of sub-component 2, component 3 is composed of sub-component 1 and sub-component 5, and component 4 is composed of sub-component 2, sub-component 3 and sub-component 6. If the combination of component 3 → component 4 is used frequently, component 3 and component 4 can be combined into component 5 for reuse. By reusing the sub-components, the programming efficiency and reusability can be greatly improved.

[0075] That is, the elements and sub-elements described in this application can be self-contained and infinitely nested. For example, A and B form the AB element, AB and C form the ABC element, and ABC and D are arranged into RPA, which is nested at 3 levels.

[0076] The RPA orchestration module is specifically as follows:

[0077] For different business systems and platforms, the RPA components are visually orchestrated in the RPA designer to obtain the corresponding RPA, and the DSL of each RPA is set.

[0078] For example, the RPA executed in business system A includes: component a1 → component a2 → component a3 → component a4; the RPA executed in business system B includes: component b1 → component b2 → component b3 → component b4.

[0079] The RPA verification module is specifically as follows:

[0080] In the RPA designer, each component of each RPA can be expanded into sub-components, or each sub-component can be collapsed into a component, thereby enabling global verification of each RPA. Collapsing the sub-components can increase the readability of the RPA.

[0081] The RPA execution module is specifically:

[0082] The DSL is converted into execution instructions that match the server or client, and then the execution instructions are sent to the browser of the server or client to automatically execute the corresponding RPA. Since the DSL description of RPA is platform-independent, it can be converted into execution instructions that the server or client can recognize, and the execution of the two RPAs can be scheduled respectively.

[0083] Based on the same inventive concept, this application provides an electronic device embodiment corresponding to Embodiment 1, as detailed in Embodiment 3.

[0084] Example 3

[0085] This embodiment provides a visualization-based RPA multi-scenario orchestration device, such as... Figure 3 As shown, it includes a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it can implement any of the embodiments in Example 1.

[0086] Since the electronic device described in this embodiment is the device used to implement the method in Embodiment 1 of this application, those skilled in the art can understand the specific implementation method and various variations of the electronic device in this embodiment based on the method described in Embodiment 1 of this application. Therefore, how the electronic device implements the method in the embodiment of this application will not be described in detail here. Any device used by those skilled in the art to implement the method in the embodiment of this application falls within the scope of protection of this application.

[0087] Based on the same inventive concept, this application provides a storage medium corresponding to Embodiment 1, as detailed in Embodiment 4.

[0088] Example 4

[0089] This embodiment provides a visualization-based RPA multi-scenario orchestration medium, such as... Figure 4 As shown, a computer program is stored thereon, which, when executed by a processor, can implement any of the embodiments in Example 1.

[0090] The technical solutions provided in this application embodiment have at least the following technical effects or advantages:

[0091] By directly encapsulating commonly used sub-components into components, the encapsulated components can be reused and arranged directly during RPA orchestration. This greatly reduces the number of components displayed on the RPA designer, enhances RPA readability, and significantly reduces the difficulty of RPA orchestration. By collapsing and expanding sub-components, RPA can be checked globally without switching between multiple independent files. Ultimately, this greatly improves the readability and efficiency of RPA orchestration and facilitates RPA maintenance.

[0092] Those skilled in the art will understand that embodiments of the present invention can be provided as methods, systems, or computer program products. Therefore, the present invention can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention can 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, etc.) containing computer-usable program code.

[0093] This 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 block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can 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, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0094] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0095] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0096] While specific embodiments of the present invention have been described above, those skilled in the art should understand that the specific embodiments described are merely illustrative and not intended to limit the scope of the present invention. Equivalent modifications and variations made by those skilled in the art in accordance with the spirit of the present invention should be covered within the scope of protection of the claims of the present invention.

Claims

1. A visualization-based multi-scenario orchestration method for RPA, characterized in that: Includes the following steps: Step S10: Calculate the usage frequency of the pairing combinations between each sub-component, and visually arrange each sub-component with a usage frequency greater than a preset frequency threshold on the RPA designer to encapsulate several components; each component includes at least one sub-component. Step S20: For different business systems and platforms, perform visual orchestration of each component in the RPA designer to obtain the corresponding RPA, and set the DSL of each RPA; Step S30: Expand each component of each RPA into sub-components or collapse each sub-component into a component in the RPA designer, and then check each RPA from a global perspective. Step S40: Convert the DSL into an execution instruction that matches the server or client, and then send the execution instruction to the browser of the server or client to automatically execute the corresponding RPA.

2. A visualization-based RPA multi-scenario orchestration system, characterized in that: Includes the following modules: The sub-component encapsulation module is used to count the usage frequency of paired combinations among sub-components, and to visually arrange sub-components with usage frequencies greater than a preset frequency threshold on the RPA designer, encapsulating them into several components; each component includes at least one sub-component. The RPA orchestration module is used to visually orchestrate each component on the RPA designer to obtain the corresponding RPA for different business systems and platforms, and to set the DSL of each RPA. The RPA verification module is used to expand each component of each RPA into sub-components or collapse each sub-component into a component in the RPA designer, thereby verifying each RPA from a global perspective. The RPA execution module is used to convert the DSL into execution instructions that match the server or client, and then send the execution instructions to the browser of the server or client to automatically execute the corresponding RPA.

3. A visualization-based RPA multi-scenario orchestration device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the program, it implements the method as described in claim 1.

4. A visualization-based RPA multi-scenario orchestration medium, on which computer programs are stored, characterized in that... When the program is executed by the processor, it implements the method as described in claim 1.

Images