Automation Windows for Parallel RPA and User Interaction
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional emulators, simulators, virtual machines, and hybrid virtual machines do not effectively address the issues arising with attended automation robots operating on the same computing system as the user, leading to the user being unable to interact with other applications on the machine that require user interaction.
Innovation Solution
The implementation of automation windows that allow for the creation of a child session window and child session within a parent session, enabling the robot to operate independently while the user interacts with the same computing system, with both sessions having access to a common file system, allowing seamless interaction and monitoring.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Extent of automation
If the robot controls applications through the user interface in the same manner as the user, then the robot can perform automated tasks, but the user becomes unable to interact with other applications on the machine that require user interaction
Solution Approach 1:
The system segments the user interface into multiple independent session windows, allowing the robot to operate in one session while the user interacts with another session simultaneously. This segmentation resolves the conflict by dividing the UI control space so that automated and manual operations do not interfere with each other.
Solution Approach 2:
The patent introduces session windows as an intermediary layer between the robot and the underlying applications. Instead of the robot directly controlling applications through the UI, it controls them through a dedicated session window, which acts as a mediator that isolates robot operations from user operations.
2Reliability
If conventional emulators or virtual machines are used to isolate the robot, then the robot can run independently, but the complexity of the system increases and resource sharing becomes limited
Solution Approach 1:
Instead of using full virtual machines or emulators, the system creates simplified session window copies that provide the necessary isolation for robot operations. These session windows replicate the essential UI environment without the overhead of complete OS virtualization, reducing system complexity while maintaining operational independence.
Solution Approach 2:
The session window mechanism serves multiple functions simultaneously: it provides UI isolation for the robot, maintains access to the common file system, enables parallel user interaction, and simplifies resource sharing. This multi-functionality reduces the need for separate specialized systems.
3Productivity
If the robot runs on the same computing system as the user, then resource sharing is efficient, but the user experience deteriorates as the robot takes over the interface
Solution Approach 1:
The system segments the user interface into multiple independent session windows, allowing the robot to operate in one session while the user interacts with another session simultaneously. This segmentation resolves the conflict by dividing the UI control space so that automated and manual operations do not interfere with each other.
Solution Approach 2:
The patent introduces a new dimension of session management to the traditional single UI space. By adding the session window dimension, the system allows multiple independent operation contexts to coexist on the same computing system, transforming the flat UI space into a multi-layered session architecture.
Data Source
AI summary
Automation windows for RPA for attended or unattended robots are disclosed. A child session is created and hosted as a window including the UIs of applications of a window associated with a parent session. Running multiple sessions allows a robot to operate in this child session while the user interacts with the parent session. The user may thus be able to interact with applications that the robot is not using or the user and the robot may be able to interact with the same application if that application is capable of this functionality. The user and the robot are both interacting with the same application instances and file system. Changes made via the robot and the user in an application will be made as if a single user made them, rather than having the user and the robot each work with separate versions of the applications and file systems.