Abstract: Systems and methods for allocating computing environments for completing an RPA (robotic process automation) workload are provided. A request for completing an RPA workload is received. A number of computing environments to allocate for completing the RPA workload is calculated based on a selected one of a plurality of RPA autoscaling strategies. The calculated number of computing environments is allocated for allocating one or more RPA robots to complete the RPA workload. The computing environments may be virtual machines.

Abstract: A method and/or apparatus for creating and/or editing a machine pool with bring your own machine (BYOM) includes creating and/or editing a machine pool with a static list of machines. A user input machine list and an existing machine list are retrieved, and the user input machine list and existing machine list are compared to identify one or more changes between the user input machine list and existing machine list. Next, a new machine specification is created when the one or more changes between the user input machine list and existing machine list are identified. The one or more machines are then moved to the new machine specification.

Abstract: 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.

Abstract: A method and/or apparatus for creating and/or editing a machine pool with bring your own machine (BYOM) includes creating and/or editing a machine pool with a static list of machines. A user input machine list and an existing machine list are retrieved, and the user input machine list and existing machine list are compared to identify one or more changes between the user input machine list and existing machine list. Next, a new machine specification is created when the one or more changes between the user input machine list and existing machine list are identified. The one or more machines are then moved to the new machine specification.

Abstract: Systems and methods for allocating computing environments for completing an RPA (robotic process automation) workload are provided. A request for completing an RPA workload is received. A number of computing environments to allocate for completing the RPA workload is calculated based on a selected one of a plurality of RPA autoscaling strategies. The calculated number of computing environments is allocated for allocating one or more RPA robots to complete the RPA workload. The computing environments may be virtual machines.

Abstract: 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.

Abstract: In some embodiments, an automation optimizer is configured to determine whether a provisioning condition is satisfied, for instance according to a current length of a job queue, or according to a current workload of a selected RPA host platform executing a plurality of software robots. When to the provisioning condition is satisfied, some embodiments automatically provision additional VMs onto the respective RPA host platform, and automatically remove VMs when automation demand is low. Exemplary RPA hosts include cloud computing platforms and on-premises servers, among others.

Abstract: Systems and methods for implementing an RPA (robotic process automation) cloud suite comprising a plurality of RPA related services are provided. Each of the plurality of RPA related services of the RPA cloud suite is associated with one of a plurality of nodes of a hierarchical model. A routing address for each respective RPA related service of the plurality of RPA related services is defined according to a standardized format for the RPA cloud suite based on the node associated with the respective RPA related service.

Abstract: 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.

Abstract: Systems and methods for consumption based billing for RPA (robotic process automation) are provided. Usage of RPA related resources by a user is quantified based on RPA execution data associated with the user. A bill for the user is generated based on the quantified usage of RPA related resources. The generated bill is output.

Abstract: 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.

Abstract: 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.

Abstract: A primary file can be used to specify default build properties for software under development. A set of modified build properties may be stored in a supplemental file. The default build properties can be temporarily overridden with modified build properties for a given build, allowing freedom in the choice of build properties without proliferation of files used for the same purpose, which can be confusing. In addition, users can create new build commands for software under development, and associate the new commands with supplemental files. When the user invokes a new build command, the build process can override the default properties with the modified properties in the supplemental file, and then restore the defaults. Other advantages and features of the invention are described below.

Abstract: Hierarchical structures are visualized and navigated using an orbital model. Sibling nodes are orbitally displayed in a generally circular arrangement along an orbital path. Choosing one of the orbitally displayed nodes opens it, moving down in the hierarchy. Nodes which were not chosen are undisplayed, and child node(s) of the chosen node are orbitally displayed. Node movements may be animated. A history displays recently chosen nodes. Choosing a parent node of the orbiting nodes undisplays the child nodes, and the parent node and its siblings are orbitally displayed, thereby moving up in the hierarchy. A user may select nodes from different parts of the hierarchy by moving them into a selection tray. Selected nodes can then be subjected to a specified batch operation. Controls are available for sorting nodes and/or for altering node appearance in the display.

Abstract: Hierarchical structures are visualized and navigated using an orbital model. Sibling nodes are orbitally displayed in a generally circular arrangement along an orbital path. Choosing one of the orbitally displayed nodes opens it, moving down in the hierarchy. Nodes which were not chosen are undisplayed, and child node(s) of the chosen node are orbitally displayed. Node movements may be animated. A history displays recently chosen nodes. Choosing a parent node of the orbiting nodes undisplays the child nodes, and the parent node and its siblings are orbitally displayed, thereby moving up in the hierarchy. A user may select nodes from different parts of the hierarchy by moving them into a selection tray. Selected nodes can then be subjected to a specified batch operation. Controls are available for sorting nodes and/or for altering node appearance in the display.

Abstract: A primary file can be used to specify default build properties for software under development. A set of modified build properties may be stored in a supplemental file. The default build properties can be temporarily overridden with modified build properties for a given build, allowing freedom in the choice of build properties without proliferation of files used for the same purpose, which can be confusing. In addition, users can create new build commands for software under development, and associate the new commands with supplemental files. When the user invokes a new build command, the build process can override the default properties with the modified properties in the supplemental file, and then restore the defaults. Other advantages and features of the invention are described below.

Abstract: A primary file can be used to specify default build properties for software under development. A set of modified build properties may be stored in a supplemental file. The default build properties can be temporarily overridden with modified build properties for a given build, allowing freedom in the choice of build properties without proliferation of files used for the same purpose, which can be confusing. In addition, users can create new build commands for software under development, and associate the new commands with supplemental files. When the user invokes a new build command, the build process can override the default properties with the modified properties in the supplemental file, and then restore the defaults. Other advantages and features of the invention are described below.

Abstract: A software development environment exposes a GUI with visual markings for differentiating developer modifications to software files. The differentiation techniques can be provided as defaults with embodiments of the invention, or can be customizable to allow for useful grouping of modifications. The software development environment may also provide a selection tool for accepting, rejecting, or further modifying previous file modifications. A history of modifications may be maintained in the event that a developer needs to re-implement modifications that have been removed or distorted. A navigation tool facilitates analysis of modifications.

Abstract: Systems and methods are provided for navigating to multiple destination types from a single search interface element in an Integrated Development Environment (IDE) Graphical User Interface (GUI). Exemplary destination types are files, lines of code, symbols, bookmarks, and tool windows. An algorithm can be used to automatically determine a likely destination type from any characters entered into a search element. The automatically determined destination type can be prioritized in the search. The burden of specifying an appropriate type of search element is thus shifted away from the developer. An auto-complete feature can provide the developer with a selection of various destinations, which may include different destination types, when a partial identification is entered into the search element. Other advantages and features of the invention are described below.

Abstract: A primary file can be used to specify default build properties for software under development. A set of modified build properties may be stored in a supplemental file. The default build properties can be temporarily overridden with modified build properties for a given build, allowing freedom in the choice of build properties without proliferation of files used for the same purpose, which can be confusing. In addition, users can create new build commands for software under development, and associate the new commands with supplemental files. When the user invokes a new build command, the build process can override the default properties with the modified properties in the supplemental file, and then restore the defaults. Other advantages and features of the invention are described below.