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 Internet Explorer

Below is the table defining boundaries for the applications using Internet Explorer.

 

OS Supported

Versions supported

Supported technologies inside the application

Controls Supported

  • Windows 10

  • Windows Server 2012 R2

  • Windows Server 2016

  • Windows Server 2019

IE (10-11)

  • HTML

  • Nested frames

  • Iframe

  • Text

  • Password

  • Submit

  • Button

  • Checkbox

  • Radio

  • Anchor[Links]

  • Select

  • Frame [Level N]

  • AJAX controls

Limitation: Flash, Silverlight, ActiveX, Applets, SmartGWT based apps

 

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

  • Windows 10

  • Windows Server 2012 R2

  • Windows Server 2016

  • Windows Server 2019

59 Onwards

  • HTML

  • Nested Frames

  • Iframe

  • Text

  • Password

  • Submit

  • Button

  • Checkbox

  • Radio

  • Anchor[Links]

  • Select

  • Frame [Level N]

  • AJAX controls

Limitation: Flash, Silverlight, ActiveX Applets

Note:

  • Lower versions of Firefox might work with appropriate Selenium but have not been tested with.
  • Basic authentication dialog handling is not directly supported for Chrome and Firefox which is shown when the browser  is  launched  and  navigated  to  login  URL. For  more  details on  steps to  automate  basic  authentication dialog  for Chrome  and  Firefox. See Handling  Basic  Authentication  for  Chrome  and  Firefox topic.

   

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

  • Windows 10

  • Windows Server 2012 R2

  • Windows Server 2016

  • Windows Server 2019

61 to 68

  • HTML

  • Nested Frames

  • Iframe

  • Text

  • Password

  • Submit

  • Button

  • Checkbox

  • Radio

  • Anchor[Links]

  • Select

  • Frame [Level N]

  • AJAX controls

Limitation: Flash, Silverlight, ActiveX, Applets

Note:

  • Lower versions of Chrome might work with appropriate Selenium but have not been tested with.
  • Basic authentication dialog handling is not directly supported for Chrome and Firefox which is shown when the browser  is  launched  and  navigated  to  login  URL. For  more  details on  steps to  automate  basic  authentication dialog  for Chrome  and  Firefox. See Handling  Basic  Authentication  for  Chrome  and  Firefox topic.

 

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

  • Windows 10

  • Windows Server 2012 R2

  • Windows Server 2016

  • Windows Server 2019

84 and 85

HTML

Nested Frames

Iframe

  • Text

  • Password

  • Submit

  • Button

  • Checkbox

  • Radio

  • Anchor[Links]

  • Select

  • Frame [Level N]

  • AJAX controls

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

  • Windows 10

  • Windows Server 2012 R2

  • Windows Server 2016

  • Windows Server 2019
     

84 and 85

HTML

Nested Frames

Iframe

  • Textbox
  • Button
  • Drop Down List
  • Radio Button
  • Checkbox
  • Table (loop)
  • Listbox
  • Date/Time Picker
  • Hyperlink
  • Textarea
  • Tab Selection

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).
    • For older version of Edge, please refer to User Manual.
  • Only the applications that are launched in Internet Explorer document mode 11 are fully supported.

 

 

 

 

 

 

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

  • Windows 10

  • Windows Server 2012 R2

  • Windows Server 2016

  • Windows Server 2019

  • IE (10, 11)

  • Chrome 61 to 68

  • Firefox 59.0 Onwards

 

  • Only elements with a common parent and having similar xpath structure can be looped where each element varies at only one place by its index in its xpath.

  • For ex: table -> tr[index] - > td - > button, ul - >li (index), etc.

Limitation:

  • Data grid has break in rows while displaying data elements. Since the Loop variable is assumed to always increase by '1'. Such inconsistency in the looping element css3 selectors, the loop exits when the first inconsistent selector is encountered.
  • If element ids are generated dynamically in the web page.

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

  • Windows 10

  • Windows Server 2012 R2

  • Windows Server 2016

  • Windows Server 2019

IE 11

  • HTML

  • Nested Frames

  • Iframe

  • Text

  • Password

  • Submit

  • Button

  • Checkbox

  • Radio

  • Anchor[Links]

  • Select

  • Frame [Level N]

  • AJAX controls

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

  • Windows 7

  • Windows8.1

  • Windows10

 

Screen based automation without needing focus

  • Get text from screen

  • Set text to the screen

  • Fire keyboard commands like F1, F12, Enter, ESC

  • All commands possible in the emulator are supported

   

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

  • Windows 10

  • Windows Server 2012 R2

  • Windows Server 2016

  • Windows Server 2019

 

Screen based automation without needing focus

  • Get text from screen

  • Set text to the screen

  • Fire keyboard commands like -F1, F12, Enter, ESC. All commands possible in the emulator are supported

 

 

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

  • Windows 10

  • Windows Server 2012 R2

  • Windows Server 2016

  • Windows Server 2019

16.0.209.0

Screen based automation without needing focus

  • Get text from screen

  • Set text to the screen

  • Fire keyboard commands like -F1, F12, Enter, ESC. All commands possible in the emulator are supported

 

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

  • Windows 10

  • Windows Server 2012 R2

  • Windows Server 2016

  • Windows Server 2019

 

Mainframe emulators compliant with EHLLAPI interface

  • Get text from screen

  • Set text to the screen

  • Fire keyboard commands like F1, F12, Enter, ESC

  • All commands possible EHLLAPI in the emulator are supported.

Limitation:

  • Supported with only 32 bit emulators which are compliant with EHLLAPI interface.
  • Supported screen size is 24*80

 

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

  • Windows 10

  • Windows Server 2012 R2

  • Windows Server 2016

  • Windows Server 2019

1.5 and above

 

  • Button

  • TextField

  • TextArea

  • CheckBox

  • RadioButton

  • List

  • Label

  • Menu

  • Table

  • Tree

  • Choicebox

  • Colourchooser

  • Slider

  • Applets also supported

Limitation:

  • Controls inside table like check boxes, radio buttons cannot be selected. However, table row can be selected.
  • API automation is not supported by applets which are not even accessible manually when docked inside Engage tab.

Notes:

  • JRE 5.0 or higher is installed on the agent’s machine
  • It uses ports on the local loopback interface
  • Feasible to set environment variables

   

Java Application Java – Swing

Below is the table defining boundaries for Java Swing.

 

OS Supported

Versions

supported

Supported technologies inside the application

Controls Supported

  • Windows 10

  • Windows Server 2012 R2

  • Windows Server 2016

  • Windows Server 2019

1.5 and above

 

  • JTextArea

  • JTextField

  • Jbutton

  • Jlabel

  • Jtable

  • Jtree

  • JTabbedPane

  • JComboBox

  • JCheckBox

  • JRadioButton

  • JMenuBar

  • Colourchooser

  • Slider

  • Applets also supported

Limitation:

  • Controls inside Jtable like checkboxes, radiobuttons cannot be selected. However, Jtable row can be selected.
  • API automation is not supported by applets which are not even accessible manually when docked inside Engage tab.

Notes:

  • JRE 5.0 or higher is installed on the agent’s machine
  • It uses ports on the local loopback interface
  • Feasible to set environment variables

   

 

Java Application Java – FX

Below is the table defining boundaries for Java FX.

 

OS Supported

Versions

supported

Supported technologies inside the application

Controls Supported

  • Windows 10

  • Windows Server 2012 R2

  • Windows Server 2016

  • Windows Server 2019

1.5 and above

 

  • Button

  • TextField

  • TextArea

  • CheckBox

  • RadioButton

  • List

  • Label

  • Menu

  • Table

  • Tree

  • Menubar

Limitation:

  • Controls inside table like check boxes, radio buttons cannot be selected. However, table row can be selected.
  • API automation is not supported by applets which are not even accessible manually when docked inside Engage tab.

Notes:

  • JRE 5.0 or higher is installed on the agent’s machine
  • It uses ports on the local loopback interface
  • Feasible to set environment variables

   

Execute JavaScript Activity

Below is the table defining boundaries for executing JavaScript activity.

 

OS Supported

Versions

supported

Supported technologies inside the application

Controls Supported

  • Windows 10

  • Windows Server 2012 R2

  • Windows Server 2016

  • Windows Server 2019

  • IE (10, 11)

  • Chrome 61 to 68

  • Firefox 59.0 Onwards

 

  • This activity always returns a single string value.

  • The window number on which the JavaScript activity is to be executed should be navigated to using the Shift Click interaction of the studio.

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

  • Windows 10

  • Windows Server 2012 R2

  • Windows Server 2016

  • Windows Server 2019

 

REST

  • Put, Get, Delete and Post method supported.

  • Only services with Basic Authentication or No Authentication are supported.

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

  • Windows 10

  • Windows Server 2012 R2

  • Windows Server 2016

  • Windows Server 2019

  • SAP ECC 6.0

  • Enhancement Package
    4 or above

SAP BAPI

  • SAP’s internal http/s server is supported

  • Basic Authorization (Username token) is supported

  • All Standard BAPIs are supported

  • All custom BAPIs are also supported by importing custom BAPIs using BAPIUtility

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

  • Windows 10

  • Windows Server 2012 R2

  • Windows Server 2016

  • Windows Server 2019

 

  • OneNote 2013/ 16

  • Tesseract 3.0.2.0

  • Google Vision API

  • Microsoft Vision API v2.0

  • Abbyy Cloud OCR

  • Image based lookup with support for offset.

  • Co-ordinate based extraction

Limitations:

  • Responsive UI with layout change
  • Resolution change with offset
  • Change in themes/ color scheme

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

  • Windows 10

  • Windows Server 2012 R2

  • Windows Server 2016

  • Windows Server 2019

  • IE

  • Chrome

  • Firefox

 

Web Recording

Limitation:

  • Chrome/Firefox
    While recording, if ENTER key is pressed on page (i.e.: Typed in Search Box and pressed Enter Key).
    If user opens a new tab before playback, then by clicking playback button, the application URL launches but focus on search field shifts to address bar and Enter gets executed in address bar rather than search input field (Automation fails).
    Hence, automation of Enter works fine when process is exported to Automation Studio because when ROBO runs, it always launches the application in browser.
    Also, ensure that the chrome instance is not running in background from system tray during recording and playback before launching the process recorder.
  • Dynamic control capture
    If a class is dynamically getting added or changed in existing HTML tag on mouse hover, then there is a possibility that playback fails on locating that control based on that dynamic class. This is because process recorder doesn’t move mouse during playback.
    Also, if both CSS path and XPath gets changed dynamically for an application when loaded, then control is not captured.
  • Recording for modal dialog window in IE
    Process recorder doesn’t capture control when show modal dialog window appears, For example, Calendar. This method only works in IE whereas Chrome & Firefox don’t support it as it is deprecated.
  • Mouse hover events will get captured after holding a mouse on target element (Menu with submenu option) for at least 2 seconds.
    If user doesn't hold mouse on such control which opens the sub menu, then playback will fail due to element not found as web recorder didn't captured the mouse hover.
    Refer Troubleshooting topic for alternate option.
  • Process recorder will not be able to capture interactions performed on dynamic iframes or iframes with cross domain URLs.
  • Process recorder is unable to record steps for JIRA application with file upload button due to technology constraints and will be available in next release.
  • A process is recorded using WinSCP application. Application is in launched state and process is run via process recorder.
    The Automation ID of the controls in the Login pop up window are dynamically generated and changing. Playback is not possible for such application.

 

   

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 10

  • Windows Server 2012 R2

  • Windows Server 2016

  • Windows Server 2019

Windows Desktop application

 

Windows Recording

Limitation:

  • Test run fails to automate an event for Windows application which opens a dialogue/dropdown/popup on click.
    Some Windows applications, for example: Outlook, Excel, PowerBI, Word etc. require focus to activate the window and hence user ends up clicking the control twice, this registers as two mouse clicks which fails the test run.
    Refer Troubleshooting Guide for alternate option.
  • In Windows application like MS Paint when user performs an action such as Save As which opens a popup, the recorder button gets hidden behind the paint window.
    Refer Troubleshooting Guide for alternate option.
  • Test run fails in Automation Studio for some windows applications due to change in container class name property. For example, Power BI or MS paint.
    Refer Troubleshooting Guide for alternate option
  • Control interactions/events which are not listed in Automation Studio will not be mapped from process recorder.
  • If you open a new incoming chat window of Skype/Lync while the recording is on, then Skype might crash.
  • Combination of keyboard & mouse interaction (For example, KeyPress<Ctrl> + Mouse Click) will not be recorded via process recorder.
  • Interaction will not be captured on selecting control by hovering mouse over control and selecting the content. (For example: Adding table in MSWord by selecting cells using mouse hover).
  • Sensitive information like SSN, UID, password etc. will not be captured and playback for these controls are not supported in process recorder.
    If field is not identified as password field i.e. the container classname/container name/name doesn’t have password as an identifier field, then its typed value will not be masked or encrypted.
  • Interaction on dynamic controls for Playback/Test run is not supported.
    Refer Troubleshooting Guide for alternate option.
  • Test run fails when user drags mouse to select some text/word/sentence.
    Since drag interaction is not supported in Automation Studio, it will not be mapped as previously explained. For work around refer Troubleshooting Guide for alternate option.
  • When we are recording process via process recorder then sometimes first step gets captured as Automation Recorder.
    Refer Troubleshooting Guide for alternate option.
  • When we are recording process via process recorder then in case of mouse hover scenario, user needs to perform click instead of just hovering mouse over the control for proper recording of steps.
  • Process recorder playback not supported for notepad++ file icons image in topmost tool bar due to technology constrains and will be available in next release.
  • During recording, if there are any windows applications running in background whose wpf windows property is being set to topmost, then at times, interaction on recorded application will not be captured due to interference in retrieving the automation element property.

   

Excel Application Recording

Below is the table defining boundaries for process recorder.

 

OS Supported

Versions supported

Supported technologies inside the application

Controls Supported

  • Windows 10

  • Windows Server 2012 R2

  • Windows Server 2016

  • Windows Server 2019

Excel Apps

 

Windows Recording

Limitation:

  • Excel - Interaction will not be captured on a cell when user types or enters value and stops process recording immediately without any further mouse/keyboard interaction.
    Refer Troubleshooting Guide for alternate option.
  • Excel – If process is recorded for opening a password protected excel file where user enters the password, it will not be mapped to Automation Studio due to invalid application title.

   

Microsoft Excel Plugin

Below is the table defining boundaries for Microsoft excel plugin.

 

OS Supported

Versions

supported

Supported technologies inside the application

Controls Supported

  • Windows 10

  • Windows Server 2012 R2

  • Windows Server 2016

  • Windows Server 2019

  • Microsoft Excel 2013

  • Microsoft Excel 2016

  • Get value from a cell

  • Set value to a cell

  • Copy value from a cell

  • Paste into a cell

  • Search (row lookup and column lookup)

  • Insert column

  • Insert row

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

  • Windows 10

  • Windows Server 2012 R2

  • Windows Server 2016

  • Windows Server 2019

 

 

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

  • Windows 10

  • Windows Server 2012 R2

  • Windows Server 2016

  • Windows Server 2019

  • ECC 6

  • EHP 4

SAP Recording based automation of SAP thick client application without the need for focus.

  • Controls supported for extraction:

  •   GuiTextField - gives text value

  •   GuiCTextField - gives text value

  •   GuiTextEdit - gives text value [multiline]

  •   GuiLabel - gives text value

  •   GuiComboBox - gives selected value

  •   GuiRadioButton - gives True/False depending on whether checkbox is Checked/Unchecked

  •   GuiCheckBox - gives True/False depending on whether checkbox is Checked/Unchecked

  •   GuiStatusBar - gives text value

  •   GuiTitleBar - gives text value

  •   GuiGridView - extracting value from its cells

  •   GuiTableControl - extracting value from its cells of standard control types mentioned above

  •   GuiTee - getting node text value. [if the control is checkbox, its selected state i.e. True/False is returned]

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

  • Windows 10

  • Windows Server 2012 R2

  • Windows Server 2016

  • Windows Server 2019

Outlook 2013, 2016

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:

  • Mail Search attachment filter not enabled for embedded images not supported.
  • Search will not work when outlook is opened in admin or safe mode.

   

File Operations

Below is the table defining boundaries for file operations.

 

OS Supported

Versions supported

Supported technologies inside the application

Controls Supported

  • Windows 10

  • Windows Server 2012 R2

  • Windows Server 2016

  • Windows Server 2019

  • Word 2013, 2016.

  • Excel 2013, 2016 and other text based files.

 

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

  • Windows 10

  • Windows Server 2012 R2

  • Windows Server 2016

  • Windows Server 2019

 

 

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

  • Windows 10

  • Windows Server 2012 R2

  • Windows Server 2016

  • Windows Server 2019

 

 

  • Send keyboards events to the focused window

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

  • Windows 10

  • Windows Server 2012 R2

  • Windows Server 2016

  • Windows Server 2019

  • IE (10, 11)

  • Chrome 61 to 68

  • Firefox 59.0 Onwards

 

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

  • Windows 10

  • Windows Server 2012 R2

  • Windows Server 2016

  • Windows Server 2019

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

  • Windows 10

  • Windows Server 2012 R2

  • Windows Server 2016

  • Windows Server 2019

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

  • Windows 10

  • Windows Server 2012 R2

  • Windows Server 2016

  • Windows Server 2019

  • Base release version: Siebel CRM 8.1.x / 8.2.x

  • Application Version: 15.8.0.0 SIA

 

  •    Navigation to any Tab and subtab.

  • Set and get text value in Grid control, Textbox, Combobox, Checkbox, Radio Button, DateTime control.

  • Performing Query, Go, New, Copy, Delete, Cancel operations on Applet.

  • Tree Expansion (Plus Button click) inside a Grid.

  • Hyperlink clicks inside a Grid.

  • Opening Tasks in Siebel.

  • Performing next and pervious operations in Task.

  • Table data from Grid.

  •    Radio buttons in Task View using windows Host.

Limitation: ActiveX controls outside the supported controls list

Notes:

  • All web controls need to be automated using web automation.
  • Windows Host activity supported only for radio buttons in the task view.

 

Oracle Forms

Below is the table defining boundaries for Oracle Forms.

 

OS Supported

Versions supported

Supported technologies inside the application

Controls Supported

  • Windows 10

  • Windows Server 2012 R2

  • Windows Server 2016

  • Windows Server 2019

  • Oracle EBS R12

  • Oracle 11i (which uses JRE 1.5+)

 

  • LWTextArea

  • LWTextField

  • Button

  • LWLabel Grid

  • LWMenu

  • LWChoiceBox

  • LWCheckBox

  • LWTab

  • RadioButton

  • ScrollBar

  • Navigator

  • StatusBar

  • Also, Dynamic Controls

Limitations:

  • Embedded controls are not supported
  • Embedded controls are not supported
  • Controls inside Grid like checkboxes, radio buttons cannot be selected.
  • However, you can click on particular row
  • API automation is not supported by applets which are not even accessible manually when docked inside Engage tab

Notes:

  • JRE 5.0 or higher is installed on the agent’s machine
  • It uses ports on the local loopback interface
  • For Oracle EBS 11i server, the JRE version should be 5.0+
  • Use Host activity inside the Oracle EBS web application to automate Oracle EBS forms

 

Application Host Activity

Below is the table defining boundaries for Application Host activity.

 

OS Supported

Versions supported

Supported technologies inside the application

Controls Supported

  • Windows 10

  • Windows Server 2012 R2

  • Windows Server 2016

  • Windows Server 2019

 

 

  • Controls supported in Java

  • Controls supported in Oracle EBS

  • Controls supported in Windows(only for Siebel)

Limitations:

  • Code Editor inside application host activity cannot access application host plugin but can access parent Application plugin.
  • Application Host - Windows option is not supported for application other than Siebel.
  • While configuring the UI element/ a field of a window popup box using Application Host Activity, even though controls are highlighted, the advance configuration screen remains blank and shows no control. To get control listing in advance configuration screen, provide name of the parent window in the Window Title of the configuration of the Application Host activity, instead of the name of the window popup box.

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

  • Windows 10

  • Windows Server 2012 R2

  • Windows Server 2016

  • Windows Server 2019

 

 

Image based lookup with support for offset

Limitation:

  • Responsive UI with layout change.
  • Resolution change with offset
  • Change in themes/ color scheme.
  • Down and Up key presses don’t work within webpage or on drop down boxes using image control in Citrix.

Note:

  • This Activity should be used in conjunction with Window Focus activity to bring a required screen in focus.
  • Automation is performed using mouse and keyboard simulation.

 

Execute Database Activity

Below is the table defining boundaries to execute Database activity.

 

OS Supported

Versions

supported

Supported technologies inside the application

Controls Supported

  • Windows 10

  • Windows Server 2012 R2

  • Windows Server 2016

  • Windows Server 2019

 

SQL Server and Oracle

Insert and select query on data

Limitation: Any alteration to the Database and table.

Note: SQL 2012  and SQL 2016/ Oracle 11g and 12 C are certified.

 

SharePoint Operations

Below is the table defining boundaries for SharePoint operations.

 

  OS Supported

Versions

supported

Supported technologies inside the application

Controls Supported

  • Windows 10

  • Windows Server 2012 R2

  • Windows Server 2016

  • Windows Server 2019

SharePoint 2010

SharePoint functionalities

  • SharePoint Move

  • SharePoint Delete

  • SharePoint Copy

  • SharePoint update

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

  • Windows 10

  • Windows Server 2012 R2

  • Windows Server 2016

  • Windows Server 2019

 

Applications supporting Microsoft UI Accessibility framework

Controls having programmatic access using Microsoft UI Automation framework

Limitations:

  • Custom controls, composite controls
  • Controls which requires Admin/ Elevated access to perform action
  • Applications not supporting Microsoft UI Accessibility Framework

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

  • Windows 10

  • Windows Server 2012 R2

  • Windows Server 2016

  • Windows Server 2019

NA

  • Text based pdfs

  • Password protected pdfs

  • Scanned pdfs

Text and Tables

Limitations:

  • Restricted pdfs, scanned pdf with handwritten data.
  • Pdfs with rotated data.
  • Selection templates to give expected result only if intended data is contained in rectangles.
  • For scanned pdfs extracted data accuracy depends on quality of PDF and it is not always 100% accurate and may require correction before any kind consumption.

 

Excel Recorder

Below is the table defining boundaries for Excel Recorder.

 

OS Supported

Versions supported

Supported technologies inside the application

Controls Supported

  • Windows 10

  • Windows Server 2012 R2

  • Windows Server 2016

  • Windows Server 2019

  • Microsoft Excel 2013

  • Microsoft Excel 2016

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
  • Windows 10

  • Windows Server 2012 R2

  • Windows Server 2016

  • Windows Server 2019

  • Citrix Receiver (Product Version 14.3.0.5014)

  • Citrix 7.15 LTSR

Technologies supported by Studio  

Limitation:

  • User should use the Citrix automation block in an intelligent way so as to avoid unnecessary data transfer b/w Citrix environment and client side Studio.
  • Time taken to setup Environment for a Citrix Citrix Application type process is directly proportional to the time taken to create a citrix session/ launch a published XenApp.
  • User should use File operation activities with utmost care.
  • Automation which requires focus must be launched by AssistEdge Citrix automation runtime.
  • Only Extracted fields of Activities will be available to use on client side from Citrix -server side.
Note: The feature can be customized for other versions of Citrix.  For more information, see Customization Guide.

 

 

 

 

 

 

 

 

 

 

 

 

 

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:

  • Browser Support : Chrome, Microsoft Edge
  • Maximum request payload size: 20 KB

 

 

 

 

 

 

 

 

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.

Auto Automation - Web Application

This section elaborates the limitations of web applications, such as, Chrome, Firefox, IE.

 

OS Supported

Versions supported

Application Type

  • Windows 10

  • Windows Server 2012 R2

  • Windows Server 2016

  • Windows Server 2019

  • Chrome 93

  • Firefox 92

Web recording using WebApps

Limitation:

 

Issue: Execution fails for processes which involves mouse hover on menu to view a submenu.


Error:  Perform ClickWeb Element not found Find By: 


Description: Discover Sensor cannot capture a recording when mouse hover action is performed on the menu to select and perform click control in submenu. This is due to the pace of recording and to avoid capturing unwanted mouse hover all over the web pages. When such recordings are exported in Studio, the execution fails. 


Workaround: 

  • Workaround for Chrome and Firefox web browsers: Hover the mouse on the control and wait for 2 seconds to capture the mouse hover . 
  • Workaround for Internet Explorer web browser: Press Ctrl and hover the mouse on the control; and wait for 2 seconds to capture the mouse hover. Ensure to press and hold Ctrl while performing mouse hover  control.

Note: Application host activity can only be added inside an Application activity.

 

Issue: Dynamic control capture such as dynamic change in position of web elements.


Error: Web Element not found Find By


Description: At times, execution fails for dynamic screen recordings in studio. When dynamic screens recordings are imported in studio, there is a possibility that at the time of execution, the controls of the screen such as, ID, CSS path, class might change. If the controls of the screen are changed, execution fails for the imported process in studio.


Note: Execution of dynamic control processes are not feasible if control keeps on changing at frequent intervals.


Issue: Execution fails for hidden elements in web application

 

Error: Element Not Visible


Description: If web elements are available in hidden mode, the execution for imported process fails in studio. For example: input of type radio/checkbox is in hidden mode, such as style as :display none


Workaround: This error occurs as AssistEdge Discover and Automation Studio analyzes CSS and xpath differently.
Perform the following modifications to resolve Element not visible error:

 

  1. Change interaction from Select checkbox to click.
  2. Uncheck Id by selecting FindBy property.
  3. Edit the css3xpath and remove input keyword from the end which points to its parent. For example: div:nth-child(2) > label:nth-child(3) > div:nth-child(1) > div:nth-child(3) > input.
  4. Save the changes.

 

Note: Additionally, you can capture this interaction in Automation Studio through Multimodal Interface and replace it with the failed interaction.
 

 

Auto-Automation - Excel Application

This section elaborates the limitations of excel applications.

 

OS Supported

Versions supported

Application Type

  • Windows 10

  • Windows Server 2012 R2

  • Windows Server 2016

  • Windows Server 2019

Last tested with Microsoft Excel 365

Excel recorder with excel macros scripts

Limitation:

 

Issue: Execution fails for paste operation in studio when copied from excel1 and switched to any other application and pasted in excel2. This error is generated due to the break in macro script where copied event of macro1 is not part of macro2.


Error:  Scriptstoreexception: Paste method of worksheet class failed


Description: In this scenario, two excel macro scripts gets generated and macro2 does not contain information about copy event that is performed in macro1. Hence, execution fails as operation ActiveSheet.Paste in studio.


Workaround: Manually change the Excel activity macro script to resolve the Scriptstoreexception error. 


Search for following lines in the macro script where paste interaction is required.


Range(Parameters.Item("inputField$")).Select
ActiveSheet.Paste


Add the following lines before the searched lines. 


Windows(Parameters.Item("activateinputField$")).Activate
Range(Parameters.Item("inputField")).Select
Selection.Copy


Note: Ensure you add these lines where paste interaction fails.


Sample once added:


Windows(Parameters.Item("activateinputField$")).Activate
Range(Parameters.Item("inputField")).Select
Selection.Copy
Range(Parameters.Item("inputField$")).Select
ActiveSheet.Paste

 

Quick Tips

  • Windows(Parameters.Item("activateinputField$")).Activate 
    This is a workbook name in which copy interaction is performed.
  • Range(Parameters.Item("inputField")).Select
    This is a cell number in which copy interaction is performed.
  • Selection.Copy 
    This is a copy interaction of macro.

 

Auto Automation - Windows Application

This section elaborates the limitations of windows applications.

 

OS Supported

Versions supported

Controls Supported

  • Windows 10

  • Windows Server 2012 R2

  • Windows Server 2016

  • Windows Server 2019

Windows Apps that supports UIA (Windows UI Automation Framework)

Windows Desktop Applications using WindowsApp

Limitation:

 

Issue: Execution fails for applications which requires click to activate a window. For example: MS Office Applications


Error: Control not found


Description: While recording a process, sometimes windows applications consider the first click to activate a window. In such cases, double click is performed to capture an interaction. The cases where second click involves a dialogue/ drop-down/ popup, the execution fails in studio because at the time of execution, first click is not considered as focus window interaction.
Workaround: After exporting the process in Studio, remove mouse clicks which are used to activate a window at the time of recording.

 

Issue: Execution fails after importing the process where automation Id and class name are missing for the control


Error: object reference not set to an instance or Control not found


Description: Automation Id and class name information are lost while exporting process from Insights Hub to Automation Studio. 


Workaround: You can configure the missing information in Automation Studio through Multimodal Interface. Once configured, select search by control order checkbox.

 

During execution for applications such as Notepad, copying a word from complete text is not feasible because text area is a single control and get text gets the complete text in that control.opy the steps and arguments)