Embedded Robot Invocation via Port Discovery and Consent
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In robotic process automation (RPA), users are unable to invoke robots from applications other than the robot tray or conductor API, limiting flexibility and accessibility.
Innovation Solution
A method that allows invoking robots by launching an application to identify a port and token, generating a randomized code, and requesting user consent through a consent application, registering the code with a local listener module, and passing information to a global listener module for authentication and communication with the robot.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If users invoke robots through robot tray or conductor API, then robot invocation is reliable and controlled, but user accessibility and flexibility are limited
Solution Approach 1:
The robot link is embedded within multiple different applications (email client, document editor, etc.), enabling a single robot invocation mechanism to serve multiple application contexts. This allows users to invoke robots from any application where the link is embedded, not just from the robot tray or conductor API, thereby improving accessibility and versatility while maintaining a unified invocation approach.
Solution Approach 2:
The patent introduces an intermediary communication mechanism between applications and robots. The application containing the robot link communicates with the robot through a standardized interface, which then coordinates with the robot execution environment. This intermediary layer enables flexible invocation from any application while maintaining controlled and reliable robot execution, resolving the contradiction between accessibility and complexity.
2Ease of operation
If robot links are embedded within applications, then user accessibility improves, but security and authentication complexity increase
Solution Approach 1:
The system performs preliminary authentication and port discovery before robot invocation. When an application contains a robot link, the system pre-establishes communication channels and validates authentication credentials before the actual robot execution is triggered. This preliminary action ensures security is maintained while keeping the actual invocation process simple and easy for users.
Solution Approach 2:
The patent implements a feedback mechanism where the system continuously monitors and validates authentication status, port availability, and robot execution state. This feedback loop ensures that security checks are performed automatically in the background, maintaining ease of operation for users while ensuring comprehensive security validation through structured feedback mechanisms.
Data Source
AI summary
A process for invoking a robot from an application may include launching the application from a computing system to invoke a robot link embedded within the application. The process may also include initiating from the application a port discovery process to identify a port, port details, and a token. The process may further include generating by the application a randomized code and invoking a consent application requesting approval from a user of the computing system to invoke the robot from the application. The process may also include registering the randomized code with a local listener module and passing user information and the token to a global listener module. The process may further include receiving from the global listener module the token and port identification, allowing the application to authenticate itself with, and communicate with, the robot, thereby completing the robot invoking process.