RPA Engine Version Selection for Stable Bot Execution
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing RPA scenarios face compatibility issues when executed in environments with different versions of the RPA engine, leading to operational instability and migration-related risks, which conventional methods fail to fully resolve.
Innovation Solution
An RPA bot execution optimization method that automatically determines an optimal RPA engine version for executing RPA scenarios, regardless of the environment's RPA engine version, by identifying a representative scenario version and selecting the appropriate engine based on priority-based criteria, including version matching, recommended versions, and engine profiles.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If RPA scenarios are executed in environments with different RPA engine versions, then RPA bot execution flexibility is improved, but compatibility issues and operational instability occur
Solution Approach 1:
The system performs preliminary actions by automatically detecting the RPA engine version before execution and proactively selecting or installing the appropriate engine version. The RPA agent checks the current engine version, compares it with the required version from the scenario metadata, and pre-installs or switches to the compatible engine version before the scenario executes, preventing compatibility issues from arising.
Solution Approach 2:
The RPA agent acts as an intermediary between the scenario and the RPA engine. It mediates version compatibility by detecting the scenario's required version, managing the engine version selection process, and ensuring the correct engine is activated. This intermediary layer handles the complexity of version matching and installation, allowing scenarios to execute reliably across different engine versions without direct conflicts.
2Reliability
If RPA engine version is strictly matched with scenario creation environment, then execution reliability is improved, but system complexity and deployment difficulty increase
Solution Approach 1:
The system implements self-service by having the RPA agent automatically detect the scenario's required engine version from its metadata, autonomously select the appropriate engine version, and install or switch to it without manual intervention. The agent manages the entire version compatibility process independently, eliminating the need for users to manually configure or manage engine versions while ensuring reliable execution.
3Adaptability or versatility
If RPA scenarios are migrated to newer engine versions, then compatibility with latest engine is improved, but migration risks and operational disruption increase
Solution Approach 1:
The system performs preliminary version detection and selection before execution occurs. The RPA agent checks the scenario metadata to identify the required engine version and proactively installs or switches to that version in advance. This prevents the need for risky post-execution migrations and ensures the correct engine is already in place, maintaining operational stability while achieving compatibility.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A robotic process automation (RPA) bot execution optimization method is provided. The method includes installing an RPA agent and a default RPA engine on the computing system in a process of installing an RPA solution; acquiring, by the installed RPA agent, an execution request for an RPA bot; determining, by the installed RPA agent, a representative version of an RPA scenario for the RPA bot; preparing, by the installed RPA agent, an optimal RPA engine version for executing the RPA scenario representative version; and controlling, by the installed RPA agent, the prepared optimal RPA engine version to execute the RPA scenario.