Automation Windows Using Child Sessions for Concurrent RPA Work
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 both the user and the robot to interact with the same application instances and file system, with the parent and child sessions having access to a common file system, allowing for simultaneous operation 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
Solution Approach 1:
The system divides the computing system into separate sessions: a user session for human interaction and a robot session for automated tasks. Each session operates independently with its own window and process space, allowing the robot to control applications without blocking user access to other applications.
Solution Approach 2:
The patent introduces a session manager as an intermediary component that coordinates between the user session and robot session. The session manager handles session creation, monitoring, and resource allocation, enabling the robot to operate autonomously while the user maintains interaction capabilities through the same operating system.
2Reliability
If conventional virtual machines or emulators are used to isolate the robot, then the robot can run independently, but the complexity of the system increases significantly
Solution Approach 1:
Instead of using full virtual machines or emulators, the patent creates a simplified copy of the user session environment called a robot session. This robot session includes a robot window and robot process that mirror the essential components needed for automation, reducing complexity while maintaining independent operation capability.
Solution Approach 2:
The session manager provides universal functionality that serves both user and robot operations through a single operating system instance. Rather than requiring separate virtualized environments, the session manager handles multiple sessions (user and robot) within the same OS, reducing overall system complexity while maintaining reliability.
3Productivity
If the robot runs in the same session as the user, then resource sharing is simplified, but the user loses the ability to interact with applications during robot operation
Solution Approach 1:
The patent adds a temporal and spatial dimension to session management by creating parallel sessions (user session and robot session) that operate simultaneously. Each session has its own window and process space, allowing resources to be shared through the common file system while interactions are separated in time and space, enabling concurrent user and robot operations.
Data Source
AI summary
Automation windows for robotic process automation (RPA) for attended or unattended robots are disclosed. A child session is created and hosted as a window including the user interfaces (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.