Abstract: Automatic data transfer between a source and a target using semantic artificial intelligence (AI) for robotic process automation (RPA) is disclosed. A user may be provided with the option of selecting a source and a target and indicating through an intuitive user interface that he or she would like to copy data from the source to the destination, regardless of format. This may be done at design time or at run time. For instance, the source and/or target may be a web page, a graphical user interface (GUI) of an application, an image, a file explorer, a spreadsheet, a relational database, a flat file source, any other suitable format, or any combination thereof. The source and the target may have different formats. The source, target, or both may not necessarily be visible to the user.

Abstract: To performing real-time bidirectional communication between robotic process automation (RPA) robots and a web application, a robot initiates execution of a primary workflow when a request is received from a web application. The robot then listens for one or more triggers from the web application to start execution of a secondary workflow, and executes the secondary workflow when the one or more triggers are detected. The robot also returns a result of the execution of the secondary workflow to the web application.

Abstract: Semantic matching between a source screen or source data and a target screen using semantic artificial intelligence (AI) for robotic process automation (RPA) workflows is disclosed. The source data or source screen and the target screen are selected on a matching interface, semantic matching is performed between the source data/screen and the target screen using an artificial intelligence/machine learning (AI/ML) model, and matching graphical elements and unmatched graphical elements are highlighted, allowing the developer to see which graphical elements match and which do not. The matching interface may also provide a confidence score of the individual matches, provide an overall mapping score, and allow the developer to hide/unhide the matched/unmatched graphical elements. Activities of an RPA workflow may be automatically created based on the semantic mapping that can be executed to perform the automation.

Abstract: Intent-based automation that discovers automatable tasks and/or determines task variants in data is disclosed. Task capture data may be utilized to determine task variants in task mining data. Semantic understanding of user actions by artificial intelligence (AI)/machine learning (ML) model(s), for example, may be applied to determine the intent of the user rather than only focusing on what actions the user is performing on the computing system. Application logs and semantic understanding may be used to facilitate a more accurate determination of what the user actually intends to do. Task capture for individual user flows may be performed. Once these are captured, task capture algorithms and AI/ML models are used to determine which parts of the flows are similar and/or match and which parts are unique. The path through these flows can then be followed to build a process graph that includes decision points representing the unique flows.

Abstract: Semantic matching between a source screen or source data and a target screen using semantic artificial intelligence (AI) for robotic process automation (RPA) workflows is disclosed. The source data or source screen and the target screen are selected on a matching interface, semantic matching is performed between the source data/screen and the target screen using an artificial intelligence/machine learning (AI/ML) model, and matching graphical elements and unmatched graphical elements are highlighted, allowing the developer to see which graphical elements match and which do not. The matching interface may also provide a confidence score of the individual matches, provide an overall mapping score, and allow the developer to hide/unhide the matched/unmatched graphical elements. Activities of an RPA workflow may be automatically created based on the semantic mapping that can be executed to perform the automation.

Abstract: Automatic data transfer between a source and a target using semantic artificial intelligence (AI) for robotic process automation (RPA) is disclosed. A user may be provided with the option of selecting a source and a target and indicating through an intuitive user interface that he or she would like to copy data from the source to the destination, regardless of format. This may be done at design time or at run time. For instance, the source and/or target may be a web page, a graphical user interface (GUI) of an application, an image, a file explorer, a spreadsheet, a relational database, a flat file source, any other suitable format, or any combination thereof. The source and the target may have different formats. The source, target, or both may not necessarily be visible to the user.

Abstract: Automatic data transfer between a source and a target using semantic artificial intelligence (AI) for robotic process automation (RPA) is disclosed. A user may be provided with the option of selecting a source and a target and indicating through an intuitive user interface that he or she would like to copy data from the source to the destination, regardless of format. This may be done at design time or at run time. For instance, the source and/or target may be a web page, a graphical user interface (GUI) of an application, an image, a file explorer, a spreadsheet, a relational database, a flat file source, any other suitable format, or any combination thereof. The source and the target may have different formats. The source, target, or both may not necessarily be visible to the user.

Abstract: A software robot is designed to carry out an activity (e.g., a mouse click, a text input, etc.) on a target element (e.g., a button, an input field, etc.) of a user interface. The robot's code specification is configured to include an on-screen image of the target element and a text displayed by the target element. The robot is configured to automatically identify the target element at runtime according to an element ID specified in the source-code of the user interface, and when such identification fails, to identify the target element according to the text and image stored in the robot's code.

Abstract: In some embodiments, a robotic process automation (RPA) design interface comprises a dedicated menu item which, when invoked, includes a file download activity into an existing robotic workflow. A configuration interface further enables the developer to set activity parameters such as a download trigger event and a destination folder for the downloaded file. In some embodiments, executing the download activity comprises the RPA robot suspending subsequent activities of the current robotic workflow until the respective download is complete, and automatically determining a set of runtime attribute values (e.g., filename, size, etc.) of the downloaded file.

Abstract: A software robot is designed to carry out an activity (e.g., a mouse click, a text input, etc.) on a target element (e.g., a button, an input field, etc.) of a user interface. The robot's code specification is configured to include an on-screen image of the target element and a text displayed by the target element. The robot is configured to automatically identify the target element at runtime according to an element ID specified in the source-code of the user interface, and when such identification fails, to identify the target element according to the text and image stored in the robot's code.

Abstract: A software robot is designed to carry out an activity (e.g., a mouse click, a text input, etc.) on a target element (e.g., a button, an input field, etc.) of a user interface. The robot's code specification is configured to include an on-screen image of the target element and a text displayed by the target element. The robot is configured to automatically identify the target element at runtime according to an element ID specified in the source code of the user interface, and when such identification fails, to identify the target element according to the text and image stored in the robot's code.

Abstract: In some embodiments, a robotic process automation (RPA) design interface comprises a dedicated menu item which, when invoked, includes a file download activity into an existing robotic workflow. A configuration interface further enables the developer to set activity parameters such as a download trigger event and a destination folder for the downloaded file. In some embodiments, executing the download activity comprises the RPA robot suspending subsequent activities of the current robotic workflow until the respective download is complete, and automatically determining a set of runtime attribute values (e.g., filename, size, etc.) of the downloaded file.

Abstract: Some embodiments of robotic process automation (RPA) design software facilitate the programming of RPA robots by supplying the developer with a universal helper spreadsheet pre-filled with formulae for carrying out a plurality of data conversions and/or manipulations, such as changing the format of dates and numbers and various calendar calculations. When automation activities call for such data manipulation, the helper spreadsheet enables even non-technical developers to program RPA robots using their spreadsheet expertise and intuitive design tools, instead of coding per se.

Abstract: A software robot is designed to carry out an activity (e.g., a mouse click, a text input, etc.) on a target element (e.g., a button, an input field, etc.) of a user interface. The robot's code specification is configured to include an on-screen image of the target element and a text displayed by the target element. The robot is configured to automatically identify the target element at runtime according to an element ID specified in the source-code of the user interface, and when such identification fails, to identify the target element according to the text and image stored in the robot's code.

Abstract: Some embodiments describe improvements to an interface for designing robotic process automation (RPA) software. In response to receiving user input that selects a target UI element for an RPA activity (e.g., mouse click, text input), some embodiments automatically identify a label element co-displayed with the respective target element. An activity configuration interface displays an activity name and/or description using the label element as a descriptor and/or substitute for the target element, making the interface more intuitive and accessible to developers without a programming background.

Abstract: Some embodiments describe improvements to an interface for designing robotic process automation (RPA) software. In response to receiving user input that selects a target UI element for an RPA activity (e.g., mouse click, text input), some embodiments automatically identify a label element co-displayed with the respective target element. An activity configuration interface displays an activity name and/or description using the label element as a descriptor and/or substitute for the target element, making the interface more intuitive and accessible to developers without a programming background.

Abstract: A software robot is designed to carry out an activity (e.g., a mouse click, a text input, etc.) on a target element (e.g., a button, an input field, etc.) of a user interface. The robot's code specification is configured to include an on-screen image of the target element and a text displayed by the target element. The robot is configured to automatically identify the target element at runtime according to an element ID specified in the source-code of the user interface, and when such identification fails, to identify the target element according to the text and image stored in the robot's code.

Abstract: A software robot is designed to carry out an activity (e.g., a mouse click, a text input, etc.) on a target element (e.g., a button, an input field, etc.) of a user interface. The robot's code specification is configured to include an on-screen image of the target element and a text displayed by the target element. The robot is configured to automatically identify the target element at runtime according to an element ID specified in the source code of the user interface, and when such identification fails, to identify the target element according to the text and image stored in the robot's code.

Abstract: A software robot is designed to carry out an activity (e.g., a mouse click, a text input, etc.) on a target element (e.g., a button, an input field, etc.) of a user interface. The robot's code specification is configured to include an on-screen image of the target element and a text displayed by the target element. The robot is configured to automatically identify the target element at runtime according to an element ID specified in the source code of the user interface, and when such identification fails, to identify the target element according to the text and image stored in the robot's code.

Abstract: A software robot is designed to carry out an activity (e.g., a mouse click, a text input, etc.) on a target element (e.g., a button, an input field, etc.) of a user interface. The robot's code specification is configured to include an on-screen image of the target element and a text displayed by the target element. The robot is configured to automatically identify the target element at runtime according to an element ID specified in the source code of the user interface, and when such identification fails, to identify the target element according to the text and image stored in the robot's code.