Uipath Inc.

Andrew Hall

Alison Tai

Tarek Madkour

Remus Rusanu

Ankit Saraf

Bo-Ying Fu

Jing Jin

Minyi Zhong

Jinglong Yang

According to one or more embodiments, a method is provided. The method is implemented by a trigger engine stored on a memory as processor executable instructions. The processor executable instructions being executed by a processor. The trigger engine operates as an intermediary for robotic process automations of a software platform. The method includes tracking operations within external systems and registering available events with respect to the operations into a database accessible by the robotic process automations. The method also includes enabling an active event of the external systems to be visible via a trigger of the trigger engine to the robotic process automations.

Cloud triggers for scheduling robots

Systems and methods for implementing robotic process automation (RPA) in the cloud are provided. An instruction for managing an RPA robot is received at an orchestrator in a cloud computing environment from a user in a local computing environment. In response to receiving the instruction, the instruction for managing the RPA robot is effectuated.

On-demand cloud robots for robotic process automation

Robot access control and governance for robotic process automation (RPA) is disclosed. A code analyzer of an RPA designer application, such as a workflow analyzer, may read access control and governance policy rules for an RPA designer application and analyze activities of an RPA workflow of the RPA designer application against the access control and governance policy rules. When one or more analyzed activities of the RPA workflow violate the access control and governance policy rules, the code analyzer prevents generation of an RPA robot or publication of the RPA workflow until the RPA workflow satisfies the access control and governance policy rules. When the analyzed activities of the RPA workflow comply with all required access control and governance policy rules, the RPA designer application may generate an RPA robot implementing the RPA workflow or publish the RPA workflow.

Robot access control and governance for robotic process automation

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.

Automation windows for robotic process automation

Inter-session automation for RPA is disclosed. A robot or another application or process running in the user session may interact with an application, but one or more attended RPA robots in one or more child sessions perform operations and fetch data that the user session robot will then use to interact with the application in the user session. Attended RPA robots in client sessions may share data through an IPC protocol, by storing data in a persistent data store, such as a spreadsheet, an object-oriented database, a plain text file, another data store or file, etc. The user session robot or another application or process running in the parent session can then read this information and respond accordingly.

Inter-session automation for robotic process automation (RPA) robots

Inter-session automation for robotic process automation (RPA) is disclosed. A robot or another application or process running in the user session may interact with an application, but one or more attended RPA robots in one or more child sessions perform operations and fetch data that the user session robot will then use to interact with the application in the user session. Attended RPA robots in client sessions may share data through an Inter-Process Communication (IPC) protocol, by storing data in a persistent data store, such as a spreadsheet, an object-oriented database, a plain text file, another data store or file, etc. The user session robot or another application or process running in the parent session can then read this information and respond accordingly.

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.

Automation windows for attended or unattended robots are disclosed. A child session is created and hosted as a window including the 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.

Growing community of inventors

Bellevue, WA, United States of America

Andrew Hall