Product Boundary
This page helps you to understand the product limits and provide the framework for definition and requirement of the product.
Application Automation
The table below elaborates the applications and technologies that are supported by AE RPA. This section includes following topics:
Web Apps
Following is the list of supported web applications.
Web Apps using Mozilla Firefox
Below is the table defining boundaries for the applications using Mozilla Firefox.
OS Supported |
Versions supported |
Supported technologies inside the application |
Controls Supported |
|
92 Onwards |
|
|
Limitation: Flash, Silverlight, ActiveX Applets |
|||
Note:
|
Web App using Google Chrome
Below is the table defining boundaries for the applications using Google Chrome.
OS Supported |
Versions supported |
Supported technologies inside the application |
Controls Supported |
|
93 Onwards |
|
|
Limitation: Flash, Silverlight, ActiveX, Applets |
|||
Note:
|
Web Apps using Microsoft Edge - Chromium
Below is the table defining boundaries for the applications using Microsoft Edge.
OS Supported |
Versions supported |
Supported technologies inside the application |
Controls Supported |
|
93 Onwards |
HTML Nested Frames Iframe |
|
Limitation: Flash, Silverlight, ActiveX, Applets |
|||
Note: The content highlighting option using the Multimodal Interface is not supported for some of the applications using Microsoft Edge browser. This happens because the controls of such applications are guarded by the style-src Content Security Policy (CSP). |
Web Apps using Microsoft Edge - IE Compatibility
Below is the table defining boundaries for the applications using Microsoft Edge.
OS Supported |
Versions supported |
Supported technologies inside the application |
Controls Supported |
|
93 Onwards |
HTML Nested Frames Iframe |
|
Limitation: Flash, Silverlight, ActiveX, Applets |
|||
Note:
|
Web Application Automation - Data Grids Element Looping
Below is the table defining boundaries for the application automation – Data Grids element looping.
OS Supported |
Versions supported |
Supported technologies inside the application |
Controls Supported |
|
|
|
|
Limitation:
|
|||
Note: It might not be possible to capture the correct selector/ capture selector at all by scraping and user might have to provide it manually. |
Web Apps using Internet Explorer with Webdriver/ Selenium
Below is the table defining boundaries for the applications using IE.
OS Supported |
Versions supported |
Supported technologies inside the application |
Controls Supported |
|
IE 11 |
|
|
Limitation: Flash, Silverlight, ActiveX, Applets |
|||
Note: Scraping may not work on certain sites (For example, having frames or very heavy content). Workaround is to configure the steps using Chrome and then change to IE Selenium based application. |
Mainframe Apps
Following is the list of supported Mainframe applications.
Mainframe using Attachmate Extra Emulator
Below is the table defining boundaries for the applications using Attachmate extra emulator.
OS Supported |
Versions supported |
Supported technologies inside the application |
Controls Supported |
|
Screen based automation without needing focus |
|
Mainframe using Passport HIO Emulator
Below is the table defining boundaries for the applications using Passport HIO Emulator.
OS Supported |
Versions supported |
Supported technologies inside the application |
Controls Supported |
|
Screen based automation without needing focus |
|
Mainframe using Micro Focus Reflection Emulator for IBM and Open System
Below is the table defining boundaries for the applications using Micro Focus Reflection.
OS Supported |
Versions supported |
Supported technologies inside the application |
Controls Supported |
|
16.0.209.0 |
Screen based automation without needing focus |
|
EHLLAPI Plugin for Mainframe Emulators
Below is the table defining boundaries for EHLLAPI based Mainframe Application automation.
OS Supported |
Versions supported |
Supported technologies inside the application |
Controls Supported |
|
|
Mainframe emulators compliant with EHLLAPI interface |
|
Limitation:
|
Java Apps
Following is the list of supported Java Applications.
Java Applications - Java AWT
Below is the table defining boundaries for Java AWT.
OS Supported |
Versions supported |
Supported technologies inside the application |
Controls Supported |
|
1.8 and above |
|
|
Limitation:
|
|||
Notes:
|
Java Application Java – Swing
Below is the table defining boundaries for Java Swing.
OS Supported |
Versions supported |
Supported technologies inside the application |
Controls Supported |
|
1.8 and above |
|
|
Limitation:
|
|||
Notes:
|
Java Application Java – FX
Below is the table defining boundaries for Java FX.
OS Supported |
Versions supported |
Supported technologies inside the application |
Controls Supported |
|
1.8 and above |
|
|
Limitation:
|
|||
Notes:
|
Execute JavaScript Activity
Below is the table defining boundaries for executing JavaScript activity.
OS Supported |
Versions supported |
Supported technologies inside the application |
Controls Supported |
|
|
|
|
Limitation: JavaScript functions cannot be defined in the JavaScript activity. |
|||
Note: TheJavScript code is specific to a browser version. The script written for one version for the web browser may or may not work on another version or another browser. |
Web API
Following is the list of supported Web API.
Web API
Below is the table defining boundaries for Web API.
OS Supported |
Versions supported |
Supported technologies inside the application |
Controls Supported |
|
|
REST |
|
Limitation: Complex types not supported. |
|||
Note: For https, certificate should be pre-installed before using it. |
Web API – BAPI
Below is the table defining boundaries for Web API – BAPI.
OS Supported |
Versions supported |
Supported technologies inside the application |
Controls Supported |
|
|
SAP BAPI |
|
Limitation: BAPIs exposed via SAP-PI or SAP-Netweaver Gateway or any other middleware. (This is supported via generic Web API in case the APIs support standard REST protocol) |
|||
Note: For https, certificate should be pre-installed before using it. |
Text Extractor Activity
Following are the details for text extractor activity.
Text Extractor Activity
Below is the table defining boundaries for text extractor activity.
OS Supported |
Versions supported |
Supported technologies inside the application |
Controls Supported |
|
|
|
|
Limitations:
|
|||
Note: This Activity should be used in conjunction with Focus Window activity to bring a required screen in focus. |
Process Recorder
Following are the details for process recorder.
Web Recording (Chrome/Firefox/Internet Explorer)
Below is the table defining boundaries for process recorder.
OS Supported |
Versions supported |
Supported technologies inside the application |
Controls Supported |
|
|
|
Web Recording |
Limitation:
|
Windows Desktop Application Recording
Below is the table defining boundaries for process recorder.
OS Supported |
Versions supported |
Supported technologies inside the application |
Controls Supported |
|
Windows Desktop application |
|
Windows Recording |
Limitation:
|
Excel Application Recording
Below is the table defining boundaries for process recorder.
OS Supported |
Versions supported |
Supported technologies inside the application |
Controls Supported |
|
Excel Apps 2019 and Office 365 |
|
Windows Recording |
Limitation:
|
Microsoft Excel Plugin
Below is the table defining boundaries for Microsoft excel plugin.
OS Supported |
Versions supported |
Supported technologies inside the application |
Controls Supported |
|
|
|
Excel cells |
Limitation: Pivot Table, Macros with input parameters |
|||
Note: Looping over data in an excel and updating the data in the loop is supported using the corresponding activities in the Toolbox of Automation Studio. |
Microbot
Below is the table defining boundaries for Microbot.
OS Supported |
Versions supported |
Supported technologies inside the application |
Controls Supported |
|
|
|
Only primitive data types are supported as input and output parameters |
Limitation: Complex data types not supported as input and output parameters |
SAP thick client Application
Below is the table defining boundaries for SAP thick client application.
OS Supported |
Versions supported |
Supported technologies inside the application |
Controls Supported |
|
|
SAP Recording based automation of SAP thick client application without the need for focus. |
|
Limitation: Tree controls with dynamic nodes in it. |
|||
Note: For SAP recorder, we record all the controls which is possible by SAP GUI scripting and playback it. For some of the controls where user is setting value to controls, we are parameterizing the value. If new control is encountered which is not parameterized, user can parameterize manually by editing script and replacing the value to be parameterized with wscript. arguments(n) where n is index of next argument. Argument indexes 0,1,2 are reserved. |
Outlook
Below is the table defining boundaries for outlook.
OS Supported |
Versions supported |
Supported technologies inside the application |
Controls Supported |
|
Outlook 2019 and Outlook 365 |
E-Mail Items |
E-Mail Items basic operation like Search mail, Send mail, Reply mail, Forward mail, read mail, Create mail, delete mail and download attachment. |
Limitation:
|
File Operations
Below is the table defining boundaries for file operations.
OS Supported |
Versions supported |
Supported technologies inside the application |
Controls Supported |
|
|
|
Basic File operation and Scan file |
Limitation: For Scan file the Scan engine without command line scanning is not supported. |
Print Screen Activity
Below is the table defining boundaries for print screen activity.
OS Supported |
Versions supported |
Supported technologies inside the application |
Controls Supported |
|
|
|
Take a print screen of current focus window |
Limitation : Print screen is not possible in case if screen is locked |
|||
Note: This Activity should be used in conjunction with Window Focus activity to bring a required screen in focus. |
KeyEvents Activity
Below is the table defining boundaries for key events activity.
OS Supported |
Versions supported |
Supported technologies inside the application |
Controls Supported |
|
|
|
|
Limitation: UAC (user access control) popup, OS specific events (ex: windows key, windows+L, Control+Alt+Delete), sendkey won’t work if system is locked. |
|||
Note: KeyEvents activity sends key combination to the focused window only. |
SendKey Interaction
Below is the table defining boundaries for Send Key Interaction.
OS Supported |
Versions supported |
Supported technologies inside the application |
Controls Supported |
|
|
|
Send keyboards events to web element |
Limitation: IE9 to IE11 & above doesn’t support sendkeys |
|||
Note: KeyEvents activity sends key combination to the web element |
Focus Window Activity
Below is the table defining boundaries for focus window activity.
OS Supported |
Versions supported |
Supported technologies inside the application |
Controls Supported |
|
All windows application |
|
Focus activity brings the matching title into foreground. |
Limitation: App title which are not tracked in the task manager does not work. |
|||
Note: If the matched title is outside the docked application in case of Engage, then that matching window title is brought into foreground and focus. |
Dock Window Activity
Below is the table defining boundaries for dock window activity.
OS Supported |
Versions supported |
Supported technologies inside the application |
Controls Supported |
|
All windows application |
|
Dock activity docks the matching title if it is undocked, in Engage. |
Limitation: Dock activity has no relevance in Automation studio. So, it bypasses the execution if it is run in ACE. App title which are not tracked in the task manager does not work. |
Siebel High Interactivity
Below is the table defining boundaries for Siebel High Interactivity
OS Supported |
Versions supported |
Supported technologies inside the application |
Controls Supported |
|
|
|
|
Limitation: ActiveX controls outside the supported controls list |
|||
Notes:
|
Oracle Forms
Below is the table defining boundaries for Oracle Forms.
OS Supported |
Versions supported |
Supported technologies inside the application |
Controls Supported |
|
|
|
|
Limitations:
|
|||
Notes:
|
Application Host Activity
Below is the table defining boundaries for Application Host activity.
OS Supported |
Versions supported |
Supported technologies inside the application |
Controls Supported |
|
|
|
|
Limitations:
|
|||
Note: Application host activity can only be added inside an Application activity |
Image Control Activity
Below is the table defining boundaries for Image Control activity.
OS Supported |
Versions supported |
Supported technologies inside the application |
Controls Supported |
|
|
|
Image based lookup with support for offset |
Limitation:
|
|||
Note:
|
Execute Database Activity
Below is the table defining boundaries to execute Database activity.
OS Supported |
Versions supported |
Supported technologies inside the application |
Controls Supported |
|
|
SQL Server and Oracle |
Insert and select query on data |
Limitation: Any alteration to the Database and table. |
|||
Note: SQL 2016 is certified. |
SharePoint Operations
Below is the table defining boundaries for SharePoint operations.
OS Supported |
Versions supported |
Supported technologies inside the application |
Controls Supported |
|
SharePoint 20 Windows 10 |
SharePoint functionalities |
|
Limitation: Currently SharePoint 2010 is only supported and for current logged in user who has direct access to SharePoint , not SSO based. |
Windows Applications using Studio Configuration
Below is the table defining boundaries for Windows applications using Studio Configuration.
OS Supported |
Versions supported |
Supported technologies inside the application |
Controls Supported |
|
|
Applications supporting Microsoft UI Accessibility framework |
Controls having programmatic access using Microsoft UI Automation framework |
Limitations:
|
|||
Note: Some controls require Focus to perform action. |
PDF Activity
Below is the table defining boundaries for PDF activity.
OS Supported |
Versions supported |
Supported technologies inside the application |
Controls Supported |
|
NA |
|
Text and Tables |
Limitations:
|
Excel Recorder
Below is the table defining boundaries for Excel Recorder.
OS Supported |
Versions supported |
Supported technologies inside the application |
Controls Supported |
|
|
As supported by Excel Macros |
As supported by Excel Macros |
Limitation: It creates a new studio process and it is expected that the user copies the new process into existing automation process (copy the steps and arguments) |
Citrix Application Type
Below is the table defining boundaries for Citrix Application.
OS Supported |
Versions supported |
Supported technologies inside the application | Controls Supported |
|
|
Technologies supported by Studio | |
Limitation:
|
|||
Note: The feature can be customized for other versions of Citrix. For more information, see Product Customization. |
Ae-w2a-bridge JS Library
AssistEdge Web to Automation bridge JS library allows consumers to use this library in their web applications and make automation calls to AssistEdge (Web Engage and EPA) running on their local systems. Below is the table defining boundaries for this feature.
OS Supported |
Versions supported |
Supported technologies inside the application | Controls Supported |
NA | Controls supported by Web Engage and EPA | ||
Limitation:
|
Office 365 Support
Microsoft Graph REST API v1.0 is supported for O365 features mentioned in User-Guide. OAuth Flow Types “Authorization code flow” is supported for O365 activities Graph API authentication.
NOTE: |
In the Input Configuration screen, while entering workflow arguments then, the case must not match with the predefined process argument. |
Decision Rule Process
To import rules in a Decision Rule process, you need to upload the Rule Template Excel file. Following are the boundaries for creating the Excel file:
- You can add maximum 10 number of columns to define the input parameters (When-And) and another 10 number of columns to define the output parameters (Then-And). For both input and output parameters, you can add multiple ‘And’ columns, however, there must be only one respective ‘When’ and ‘Then’ column for the input and output parameters.
- You can define maximum of 3000 rules, that is, maximum number of rows can be 3000 and maximum file size of the Excel file can be 2 MB.
Execute ML Model Activity
The Execute ML model studio activity has the following prerequisites:
- Python 3.6 and above, ASP.NET Core Runtime 6.0, and .NET Runtime v6.0 should be present on the system where ML model activity is being executed.
- All the required libraries and packages required to execute the ML model should be installed on the system.
- The ML logic must be defined inside a method and the method can be inside or outside a class.
- The method parameter data type, both input and output must be of string datatype and only string datatype is supported.
- For remote hosting type, the Micro AI Bridge service must be running on a Linux machine.
- For remote hosting type, if you prefer https you have to create your own proxy server which routes to the MicroAI Bridge service url. For information on MicroAI Bridge refer the MicroAI Bridge Service section in Automation Studio.
Decision Rule Process
To import rules in a Decision Rule process, you need to upload the Rule Template Excel file. Following are the boundaries for creating the Excel file:
- You can add maximum 10 number of columns to define the input parameters (When-And) and another 10 number of columns to define the output parameters (Then-And). For both input and output parameters, you can add multiple ‘And’ columns, however, there must be only one respective ‘When’ and ‘Then’ column for the input and output parameters.
- You can define maximum of 3000 rules, that is, maximum number of rows can be 3000 and maximum file size of the Excel file can be 2 MB.