Application Host
This activity helps to automate
UI elements of a Windows/JAVA based host application or a pop-up
window of the host application that may not get captured or identified
using other methods like the Multimodal
Interface.
Automation Studio supports
automation of the Java-based Oracle Forms in a codeless
manner with the help of out of box adapters. For an Oracle
EBS based application, only Application
Host activity is available that must be used to configure
the related automation process workflow.
NOTE:
|
· This
activity must be used inside an Application
activity or the system displays an error. This lets
you establish a connection between Automation Studio and
the configured application whose UI elements you want
to automate.
· Before
you start capturing automation steps using this
activity, make sure that the intended application is open
that must be launched using Automation Studio. Perform
Setup
Environment to launch the application. |
This activity lets you attach a plug in of the selected application
type to the configured and launched host application to identify
the UI elements.
Prerequisite: Configuring Application
You must configure the intended host application in Automation
Studio before you start configuring the steps of automation process
workflow. This establishes the connection between the required
application and Automation Studio to perform the automation.
Below are the minimum required properties for configuring the
intended host application. If you want to define remaining properties,
refer WindowsApps
for windows applications, WebApps
for Oracle EBS application or any other web application and JavaApps
for Windows and Java applications respectively.
Requirement |
Description |
Java
Application |
· Install Java
(JDK, v ) on the system where the automation process
workflow is designed and on the system where the automation
would run.
· Configure
Java application:
1. In the Admin
menu, add an application of Application
Type - JavaApps.
2. Browse and select the required
.jar file.
3. In
the Application Properties
panel:
· Enter
the URL of the JNLP file/applet in the JarFilePath/URL
field.
· Enter
the time out duration of the application launch in the
Launch
Time Out (in secs) field,
if the JavaAppType
is JNLP
Applications or
Applet.
4. In
the Environment Type
list, select the type of environment of the added Java
application.

5. Click
the (Save
Properties) icon to save the application.
The Java application is
configured. |
Oracle
EBS Application/Other Web Application |
Configure Oracle EBS
application/ Other Web application:
1. In
the Admin menu,
add an application of Application
Type- WebApps.
The mandatory fields are highlighted with red box.

2. In
the Application Properties
panel:
· In
the Login URL
field, enter the URL of the Oracle Form you want to access.
URL of a specific Oracle Form can be retrieved form the
properties of that form. To retrieve the Oracle form URL:
a. Navigate
to the required Oracle Form.

b. Right
click Form and
then click Properties.
The Properties
dialog box appears. Note the complete Address(URL)
of the Form that
must be entered as the Login
URL in the Application
Properties pane of the Admin
menu. You may need to scroll down to retrieve the complete
Address(URL) field.

· In
the Search URL
field, enter the same URL of the Oracle form you want
to access.
· In
the Display Name,
enter a desired name of the web application.
· In
the Misc Java
section, select the Has
Java Components check box.
· In
the Misc Java
section, select the type of environment in the Environment
Type list.

3. Click
the (Save
Properties) icon to save the application.
The Oracle EBS application
is configured.
NOTE:
|
To
start capturing the automation steps, you must
login to the required Oracle EBS application.
You
can automate the process of signing to an Oracle
EBS application using the Mutimodal Interface. See the Web
Mode section to know how to configure the
steps. Alternatively,
create a Sign-In
Process for
the intended Oracle EBS application and use the
SignIn Process
activity
to automate sign in steps. This helps to reuse
the sign in steps across other process workflow
as well. See Sign
In Process and Using
SignIn Process sections to know how to automate
signing in to an application. |
|
Windows application |
Configure Windows application:
1. In
the Admin menu,
add an application of Application
Type- WindowsApps.
The Add Application
dialog box opens.

2. In
the Application Name
field, enter a desired name of the EXE application you
want to add. The name must not contain any special character
or space.
3. Click
ADD and browse
for the windows application you want to configure. Click
Open.

The windows application
is configured.
|
Using Application Host Activity
1. In
an automation process workflow, click Process
Components in the Canvas
Tools pane to expand the tool and view the associated
activities.
2. Drag
the Application activity and drop on to the Flowchart
designer
on the Canvas.
The validation error symbol disappears when required inputs are
provided.

3. In
the Application Type list,
select the type of configured host application you want to automate.
For example, select WebApps
for Siebel or Oracle EBS applications, WindowsApps
for applications like Notepad or CMD and JavaApps
for Java applications. You must have at least one application
added for it to appears in the list.
4. In
the Select An Application
list, select the configured host application. Alternatively, you
can add the required host application at this point of time. To
add the application, click any of the links below:
· Java
Applications - Lets you configure the Java applications.
· Oracle
EBS Applications - Lets you configure the Oracle EBS and other
web applications like Siebel.
· Windows
Applications - Lets you configure the Windows applications.
5. Once
the application is configured and the login steps are captured
(if required), in the Menu
bar, click Test Run drop
down, and then click Setup Environment
to setup and launch the configured application. It helps to launch
the application using automation Studio. Before you start
capturing automation steps using this activity, make sure that
the intended application is open using the Automation Studio.
6. Double
click the Application activity, drag the Application Host and drop inside
the Application activity. The validation error
symbol disappears when required inputs are provided.

7. From
the drop down list, select the type you host application you want
to automate. Available options are - Java,
Oracle EBS and Windows.
A typical web application can be automated in the Windows
category.

8. Click
the (Settings) icon of the
Application Host activity
to attach the plug in based on the type of selected host application.
A dialog box appears where you can define configurations related
to the attached plug in.

9. In
the Attach Behavior list
of the Basics category,
select the identification criteria to identify the required host
application window to which the plug in must be attached. Available
options are:
· Equals - Selects the window
based on the exact match with the window name.
· Contains - Selects the window
based on the text present in the window name.
· StartsWith - Selects the window
based on the starting text of the window name.
· EndsWith - Selects the window
based on the text with which the window name ends.
10. In
the Window Title field,
enter the window name of the host application to which the plugin
must be attached. This field is available only if the Attach
Behavior selected is Equals,
Contains, StartsWith
or EndsWith. For example,
if the name of the Oracle Form is Oracle
Applications – AUTOSC, select the Attach Behavior as StartsWith and the enter the
Window Title as Oracle.
11. In
the Application Mode list,
select Dynamic or Static depending upon the type
of UI element to be extracted while performing the automation.
This field is available only if the host application type
is Oracle EBS.
12. Select
the Dispose on Complete
check box in the Misc
category if you want to close the application window once the
automation is completed.
13. In
the Wait Until Exists
category you can configure the time for the plug in to wait until
the UI element is found. You can use this to avoid any delay in
the page loading time. :
a. In
the Poll Frequency (ms)
field, enter the frequency of checking the availability of the
UI element. The time must be entered in milliseconds.
b. In
the Timeout (ms) field,
enter the wait time for the plug in until the UI element
is found or identified that it does not exists. The time must
be entered in milliseconds.
14. Close
the dialog box to save the plug in configurations.
15. Double
click to open the Application
Host activity block.
16. Click
ADD to add the Application
Control activity. Alternatively, you can drag the Application Control activity
from the Canvas Tools
pane, and drop inside the Application
Host activity.

17. Click
the (Field Configuration) icon. Manually
bring the application window in focus. Click any of the links
below for step by step guide to automate the UI elements of each
of the host application type:
· Java - Lets you automate UI elements of a Java
application
· Oracle EBS - Lets you automate UI elements
of a Java based Oracle EBS application
· Windows - Lets you automate Windows and Web
applications
Java
a. Hover
over the field that you want to capture. The field gets highlighted
with the blue box.

b. Click
the highlighted area. A dialog box appears where you can configure
the details related to the captured UI element. The search
path of the component and the window name are auto filled.
The fields that are mandatory are highlighted with the red box.

c. In
the Action list, select the action that you want
to perform on the captured area. Other fields change depending
on the selection from the list. Enter details of all the mandatory
fields and other relevant fields as per your requirement.
Refer Windows
Application Field Descriptions table to know more about the
available fields and their respective properties.
d. Close
the dialog box. The Save
Confirmation message box appears.
e. Click
YES to save the
entered details. Click NO
to exit the message box without saving the entered details and
to re-configure the required details.

f. You
need to add the Application Control
activity for every UI element you want to capture. Repeat steps
16 and 17 to capture all the UI elements involved in the automation
process workflow. You can edit the configuration by clicking the
(Settings) icon of the
Application Control activity.
The Java application host is configured.
Oracle EBS
a. Hover
over the application window to start capturing the automation
steps that you want to perform in the Oracle EBS application.
The area that you can capture gets highlighted with a blue box.

b. Click
the intended area from where you want to extract the Id of the
UI element. A dialog box appears where you can configure the details
related to the captured UI element. The Id of the component and
the window name are auto filled. The fields that are mandatory
are highlighted with red box.

c. In
the Action list, select the action that you want
to perform on the captured area. Other fields change depending
on the selection from the list. Enter details of all the mandatory
fields and other relevant fields as per your requirement.
Refer Oracle
EBS Field Descriptions table to know more about the available
fields and their respective properties.
d. Close
the dialog box. The Save
Confirmation message box appears.
e. Click
YES to save the
entered details. Click NO
to exit the message box without saving the entered details.

f. You
need to add the Application Control
activity for every UI element you want to capture. Repeat steps
16 and 18 to capture all the UI elements involved in the automation
process workflow. You can edit the configuration by clicking the
(Settings) icon of the
Application Control activity.
The Oracle EBS application is automated.
NOTE:
|
You must Close
Environment and then Reset Environment every time you
want to Test
Run a process workflow, else, error is received or
the test run fails. |
Oracle
EBS Application Field Descriptions
Property Name |
Usage |
Base
Properties |
Component id |
The Id of the selected UI element that gets auto
filled on selection of the UI element. You can replace
the static part of the component Id with an argument to
make a dynamic part of the component Id. To
create dynamic component Id:
1. Click the (Configure)
icon. The Dynamic ComponentId
Creator dialog box opens.

|
Window name |
The name of the window of the
selected UI element. |
Control Behavior |
Action |
It is the action or the interaction that can be
performed on the Oracle EBS application depending on the
type of UI element as per the requirement. Available options
are:
· Activate Window - Allows
to activate a form which is currently not in focus and
perform required action.
· Click - Allows to left
click the selected UI element.
· Click Toolbar Item By Index
- Clicks the corresponding toolbar item selected as per
its index in the Oracle EBS form.
· Click Toolbar Item By Value
- Clicks the corresponding toolbar item selected as per
its value in the Oracle EBS form.
· Close Window - Closes
the selected Oracle EBS Form.
· Decrement scroll bar
- Decrements the scroll bar as per the entered index.
· Get Text- Retrieves
text from the selected UI element.
· Get Statusbar Text -
Retrieves the text of the selected status bar.
· Get Radiobutton Text
- Retrieves the text of the selected radio button.
· Get Choicebox Text -
Retrieves the text or index of the selected choice box.
· Get selected Choicebox index
- Retrieves the index of the selected choice box.
· Get checkbox status-
Retrieves the status of the selected check-box.
· Get checkbox text -
Retrieves the text of the selected check-box.
· Get CellData - Extracts
data of the selected cell.
· Get Visible Row count
- Retrieves the count of visible rows in the grid.
· Get visible column count
- Retrieves the count of visible column s in the grid.
· Get Row count - Retrieves
the total number of rows available in the grid.
· Get Column count - Retrieves
the total number of columns available in the grid.
· Get Scroll bar value
- Retrieves the current position of the scroll bar of
the table.
· Get selected Tab Text
- Retrieves the text of the selected tab.
· Increment scroll bar
- Increments the scroll bar as per the entered index.
· Is Focused - Retrieves
the current state of the form. If the selected Form is
in focus, True
is returned else False
is returned.
· Is Exists - Retrieves
the current state of the form. If the selected Form exists,
True is returned
else False is
returned.
· Is visible - Retrieves
the current state of the form. If the selected Form is
visible, True
is returned else False
is returned.
· Is enabled - Retrieves
the current state of the form. If the selected Form is
enabled, True
is returned else False
is returned.
· Minimize Window - Minimizes
the selected Oracle EBS Form.
· Maximize Window - Maximizes
the selected Oracle EBS Form.
· Set Text - Sets user
provided text input to the selected UI element of the
Oracle EBS Form.
· Select Navigator Item by Index
- Selects the specified Function
available in the Navigator
window of an Oracle EBS Form as per the specified index.
· Select Tab By Value
- Selects the required tab as per the entered tab name.
It helps in switching of tabs.
· Select grid row - Selects
and clicks the corresponding row of the grid.
· Select Listview Item By Index
- Selects an item from a list-view (drop-down list) as
per the specified index.
· Select Choicebox By Value
- Selects a value from the corresponding choice box.
· Select RadioButton By Text-
Sets the corresponding radio button in the radio button
group.
· Set Checkbox Status
- Selects the required check-box.
· Set Focus - Brings the
Oracle EBS Form in focus before performing any action
on it.
· Set Scroll bar value
- Sets the scroll bar at the desired position. |
Interaction |
The corresponding interaction
set against the selected action. |
Appears
for Action that
require input index for execution. |
Index |
The index of the UI element where you want to perform
the selected Action
on the Oracle EBS Form such as 3, 5 and so on. |
Appears
for Action that
require input value for execution. |
Value |
The value of the UI element where you want to perform
the selected Action
on the Oracle EBS Form such as the tab name, tool bar
item name and so on. |
Appears
only if Action
selected is Select grid
row. |
Row Number |
The row number that must be selected. |
Appears
only if Action
selected is Select Listview
item by index. |
Item Index |
The index of the item that must be selected from
the list-view (drop down list). |
Appears
only if Action
selected is Set Text,
Select Choicebox By Value,
and Select RadioButton
By Text |
Text |
The user input to be specified. You must define
a parameter in the Parameter
bar to use this option.
Select the Is Default
Value check-box, and enter the input value, if
you want to set a default value. |
Appears
only if Action
selected is Set CheckBox
Status. |
IsSelected |
Signifies the status of the check box. You must
define a parameter in the Parameter
bar to use this option.
Select the Is Default
Value check-box, and enter the status manually,
if you want to set a default value. |
Field Properties |
Display Name |
User specified display name of the windows element
selected. |
Appears
for Action that
return a value such as actions related to Get
and Is interactions. |
Is C-View |
Is applicable only for AssistEdge Engage.
If selected, the field
configuration captured in Automation Studio is visible
in the Engage C-View
tab. |
Variable Name |
User defined name of the variable that stores the
captured or returned value. You can define the variable
name here itself or predefine it in the Parameter
bar. |
Variable Type |
Type of the variable defined. Available options
are:
· Text
· Numeric
· Decimal
· Boolean
· Data
Table |
Windows
a. Press
the Ctrl key and hover over the windows/web application
to start capturing the automation steps that you want to perform
in the Windows application. The area that you can capture gets
highlighted with a red box.
b. While
pressing the Ctrl button
click the intended area. A dialog box appears where you can configure
the details related to the captured UI element. The fields that
are mandatory are highlighted with red box.

c. In
the Action list, select the action that you want
to perform on the captured area. Other fields change depending
on the selection from the list. Enter details of all the mandatory
fields and other relevant fields as per your requirement.
Refer Windows
Application Field Descriptions table to know more about the
available fields and their respective properties.
d. Close
the dialog box. The Save
Confirmation message box appears. Click YES
to save the entered details. Click NO
to exit the message box without saving the entered details.

e. You
need to add the Application Control
activity for every UI element you want to capture. Repeat steps
16 and 17 to capture all the UI elements involved in the automation
process workflow. You can edit the configuration by clicking the
(Settings) icon of the
Application Control activity.
The Windows application host is configured.
Windows
Application Field Descriptions
Property Name |
Usage |
Control Behavior |
Action |
The applicable action or interaction that can be
performed on the selected UI element. The available options
change as per the type of host application being automated:
· Click-
Allows to left click the selected UI element.
· Expand/Collapse-
Allows to expand or collapse the selected UI element.
· Legacy Interaction- Allows
to configure UI element of the Windows application which
supports a legacy pattern.
· Get Text- Retrieves
text from the selected UI element.
· Set Text- Sets user
provided text input to the selected UI element and stores
it into a parameter. You must define the parameter in
the Parameter bar before you start
capturing the UI element.
· Mouse Click- Allows
mouse simulation. It requires the application to be in
focus. You can choose to perform Left
Click, Right Click
or Double Click
available from the drop down list.
· Keyboard Input-Captures
UI element input from the keyboard in the selected UI
element. This interaction allows performing different
keyboard input combinations with the help of Single
Key, Double Keys,
Triple Keys and
TextEntry options.
· Set Focus- brings the
UI element in focus before performing any action on it.
· If Control Exists- Checks
availability of the UI element on the windows application.
It is used while working with dynamic controls.
· Get Radio Button Status-
Retrieves status of the selected radio button status.
It returns true or false.
· Toggle Checkbox Action-
Toggles the current state of a checkbox.
· Get Checkbox Status-
Returns the current selection status of a checkbox.
· Perform ComboBox Select Value-
Selects the specified value from the drop-down list.
· Get ComboBox Value-
Retrieves value of the selected combo box.
· Perform ComboBox Set Text-
Sets a user-specified value on the selected ComboBox.
All ComboBox controls do not support this interaction.
· Scroll Horizontal- Performs
horizontal scroll based on the input provided on the percentage
scale from 0 to 100.
· Scroll Vertical- Performs
vertical scroll based on the input provided on the percentage
scale from 0 to 100.
· Select Tree Node- Selects
a node of a tree control using this interaction. Specify
the input in a specific format. For example. for selecting
node 1.1, enter
the input value as Number/1/1.1.

· Expand Tree Node- Expands
a node of the tree UI element.
· Select- Selects a particular
UI element.
· Get DataGrid Value by Index-
Retrieves data grid value by its index. Specify the cell
index from which the input is needed.
· Focus Data Grid Cell by Index-
Brings a data grid cell in focus based on the input cell
index.
· Set DataGrid Value by Index-
Sets the value to a DataGrid cell based on its index.
· Get Data from Table-
Retrieves complete data of a table control to a DataTable.
If required, the data from the DataTable can then be saved
in an excel/CSV file. Following are the steps involved
to retrieve the data.
f. Create
an argument of type System.Data.DataTable,
before extracting the UI element.
g. Click
WINDOWS MODE to
extract the Data Grid Table control.
h. Select
Get Data from the Table.
i. Set
the Variable Name
as the argument created in the first step.
j. Save
the configuration.
k. Use
Export Data Table activity
to write data to excel.
· Set Focus- This interaction
is used to bring any control to focus before performing
an action on it. |
Interaction |
The corresponding interaction class name auto populated
against the selected action. |
Interaction |
The interaction or the action type corresponding
to the selected interaction. |
Appears
if Action selected
is Legacy Interaction. |
Action
Type |
The interaction or the action
type corresponding to the legacy interaction. |
Key |
Appears if Action
selected is Keyboard
Input. The single key set as input from the keyboard. |
Key |
Appears if Action
selected is Keyboard
Input and Interaction
selected is DoubleKeys.
The second key which is set as input from the keyboard
along with the first key. |
Key |
Appears if Action
selected is Keyboard
Input and Interaction
selected is TripleKeys.
The third key which is set as input from the keyboard
along with the first and the second key. |
Text |
Appears if Action
selected is Keyboard
Input and Interaction
selected is TextEntry.
Allows user input as a text. |
Mouse Action |
Appears if Action
selected is Mouse Click.
Allows user input using the mouse. Available options are:
· LeftClick- Performs
a left click at the specified offset point.
· DoubleClick- Performs
a double click at the specified offset point.
· RightClick- Performs
a right click at the specified offset point. |
Field Properties |
Display Name |
User specified display name of the windows element
selected. |
AutomationId |
Unique identifier for the automation element in
the automation tree. See Handling
Dynamic Controls section to know more about the usage
of this field. |
Class Name |
Class name of the UI element as defined by the UI
element developer. See Handling
Dynamic Controls section to know more about the usage
of this field. |
Container Class Name |
Container class name of the UI element as defined
by the developer. See Handling
Dynamic Controls section to know more about the usage
of this field. |
Container Control Type |
Control type of the container of the UI element
as defined by the UI element developer. |
Container Name |
Container name of the UI element as defined by the
developer. See Handling
Dynamic Controls section to know more about the usage
of this field. |
Control Index |
Index of the current UI element within the entire
set of elements with the same values of automation Id,
class name and UI element name as that of the current
element. |
Control Name |
Control name of the UI element as defined by
the UI element developer. See Handling
Dynamic Controls section to know more about the usage
of this field. |
Control Type |
Control type of the UI element as defined by the
developer. |
Appears
if Action selected is Mouse
Click. |
Offset From Control |
It is the distance between the UI element and the
anchor. |
Is applicable
only for AssistEdge Engage. Appears if Action
selected is If Control
Exist. |
Is C-View |
If selected, the field configuration captured in
Automation Studio is visible in the C-View
tab of Engage application. |
Search By Control Order No. |
Signifies if the UI element needs to be searched
based on the UI element order number. Control order number
is the index of the current element within the entire
set of elements with the same value of UI element Id as
that of the current element. |
Appears
if Action selected
is Get Text. |
Variable Name |
User defined name of the variable that stores the
captured value. |
Variable Type |
Type of the variable defined. Available options
are:
· Text
· Numeric
· Decimal
· Boolean
· Data
Table |
Misc
Properties |
Max wait for input idle |
The maximum time interval in milliseconds for which
the windows plugin waits on launch before it starts executing
the configured interactions. |
Retry Count |
Number of times, the plugin retries to find a UI
element, if not found. |
Retry Interval (ms) |
The time interval in milliseconds for which the
plugin waits before it attempts for a retry. |
Handling
Dynamic Controls
Automation Studio provides different identification criteria
and Parametrization of the value of the dynamic field properties
of the UI elements. You can reconfigure some of the auto captured
field properties of such UI elements to create a more effective
way of identifying the indented UI element. For such controls,
remove the dynamic part of the string and use an appropriate option
for UI element identification. For example, if a Class
Name field is recognized as AssistEdge_Studio_20180205083009,
the later part of the string, which is a timestamp,is dynamic
and can be removed. Retain only the static part and reconfigure
the field properties using the suitable option.
Following are the different field properties that can be reconfigured
against their respective values:
· AutomationId
· Class
Name
· Container
Class Name
· Container
Name
· Control
Name

Use the (drop
down arrow) icon to reconfigure the identification criteria. Available
options are:
· Equals- Identifies the UI element
based on the exact match with the value of the selected field
property.
· Contains- Identifies the UI
element based on the string present in the value of the selected
field property.
· StartsWith- Identifies the UI
element based on the starting string of the value of the selected
field property.
· EndsWith- Identifies the UI
element based on the ending string of the value of the selected
field property.
· Regex- Identifies the UI element
with the string matching
the value of the selected field property as per the identification
pattern defined through the provided regular expression such as
a.b, *txt and others.
· Variable- Identifies the UI
element as per the parametrization of the value of the selected
field property value. Parametrization allows to run the identification
process over and over again using different values. With parameterization,
windows controls with looping and assignment activities, are used.
Application Host Properties
The properties of the Application
Host activity are listed in the following table and can
be edited in the Property grid on the right pane.
Property Name |
Usage |
Control Execution |
Ignore Error |
When this option is set to Yes,
the application ignores any error while executing the
activity.
If set to NA,
it bypasses the exception (if any) to let the automation
flow continue; however, it marks the automation status
as failure, in case of an exception.
By default, this option is set to No. |
Delay |
Wait After |
Specify the time delay that must occur after the
activity is executed. The value must be in milliseconds. |
Wait Before |
Specify the time delay that must occur before
the activity is executed. The value must be in milliseconds. |
Misc |
AppType |
The plugin that gets attached to the host application
depending on the type of host application. |
Breakpoint |
Select this option to mark this activity as the pause
point while debugging the process. At this point, the
process freezes during execution allowing you to examine if
the process is functioning as expected.
In large or complex processes, breakpoints help in
identifying the error, if any. |
Commented |
Select this option to mark this activity as inactive
in the entire process. When an activity is commented,
it is ignored during the process execution. |
DisplayName |
The display name of the activity in the flowchart
designer. By default, the name is set as the name of the
selected application. You can change the name as required. |
|