Windows Desktop plugin steps are used for Windows Desktop applications automation.
Prerequisites:
Desktop: Apply Licence
Apply Desktop Plugins License to Process Studio
Apply Desktop Plugins License to Agents
Setup:
Process Studio DesktopSpy is used to get many of the configuration parameters of Desktop plugin steps. To be able to use DesktopSpy we need to configure Process Studio Options Desktop SPY Port and Desktop Runtime Port. This is shown in the snapshots below.
The step is used to perform click action on a Windows Desktop application element.
No.
Field Name
Description
1
Step Name
Name of the step. This name has to be unique in a single workflow.
2
Prefix
Prefix is populated when working with popup windows and multiple domains. Prefix is meant to get an identifier for an instance of an application.
This field must be provided if it is returned by Desktop Spy. If Prefix is not returned by Desktop Spy it should be left blank.
If prefix is blank it assigns a default prefix.
3
Accessor/Alternative
Accessor is a Windows Desktop application element identifier for a selected prefix above. This field is populated with Accessor or alternative Accessor.
In case the Prefix field is blank it uses the default prefix.
4
Click Type
Click Type has three options:
- Single Click
- Double Click and
- Right Click
5
Mode
Select ‘WINDOWS’ or ‘JAVA_APPLET’ from the drop down list.
Generally WINDOWS mode is used for .Net Windows-based applications while JAVA_APPLET is used for applet based applications(e.g. Oracle E-business suite application)
The step is used to close the current Windows Desktop application element.
No.
Field Name
Description
1
Step Name
Name of the step. This name has to be unique in a single workflow.
2
Prefix
Prefix is populated when working with popup windows and multiple domains. Prefix is meant to get an identifier for an instance of a windows application.
This field must be provided if it is returned by Desktop Spy. If Prefix is not returned by Desktop Spy it should be left blank.
If prefix is blank it assigns a default prefix.
3
Mode
Select ‘WINDOWS’ or ‘JAVA_APPLET’ from the drop down list.
Generally WINDOWS mode is used for .Net Windows-based applications while JAVA_APPLET is used for applet based applications(e.g. Oracle E-business suite application)
The step is used to highlight an element on a Windows Desktop Application. This step is also useful during Process Studio Workflow development and debugging.
No.
Field Name
Description
1
Step Name
Name of the step. This name has to be unique in a single workflow.
2
Prefix
Prefix is populated when working with popup windows and multiple domains. Prefix is meant to get an identifier for an instance of an application.
This field must be provided if it is returned by Desktop Spy. If Prefix is not returned by Desktop Spy it should be left blank.
If prefix is blank it assigns a default prefix.
3
Accessor/Alternative
Accessor is a Windows Desktop application element identifier for a selected prefix above. This field is populated with Accessor or alternative Accessor.
In case the Prefix field is blank it uses the default prefix.
4
Mode
Select ‘WINDOWS’ or ‘JAVA_APPLET’ from the drop down list.
Generally WINDOWS mode is used for .Net Windows-based applications while JAVA_APPLET is used for applet based applications(e.g. Oracle E-business suite application)
The step is used to perform Mouse Actions on Windows Desktop application elements.
No.
Field Name
Description
1
Step Name
Name of the step. This name has to be unique in a single workflow.
2
Prefix
Prefix is populated when working with popup windows and multiple domains. Prefix is meant to get an identifier for an instance of an application.
This field must be provided if it is returned by Desktop Spy. If Prefix is not returned by Desktop Spy it should be left blank.
If prefix is blank it assigns a default prefix.
3
Accessor/Alternative
Accessor is a Windows Desktop application element identifier for a selected prefix above. This field is populated with Accessor or alternative Accessor.
In case the Prefix field is blank it uses the default prefix.
4
MouseAction Type
Choose a value from the drop down list from the following values.
- Drag & Drop
- Mouse Hover
5
Destination prefix
If Drag & Drop is chosen above Destination prefix becomes active. Provide a value for the destination elements prefix.
6
Destination Accessor/Alternative
If Drag & Drop is chosen above Destination Accessor/Alternative also becomes active. Provide a value for the destination elements Accessor/Alternative.
7
Mode
Select ‘WINDOWS’ or ‘JAVA_APPLET’ from the drop down list.
Generally WINDOWS mode is used for .Net Windows-based applications while JAVA_APPLET is used for applet based applications(e.g. Oracle E-business suite application)
The step is used to open a Windows Application.
No.
Field Name
Description
1
Step Name
Name of the step. This name has to be unique in a single workflow.
2
Prefix
In this plugin Prefix is usually the title for the application window.
If we need to specify a wait time for an application window (with a specified prefix) to open then provide values in prefix as well as Windows load timeout field below. Both are mandatory.
Note: If the application window with the specified prefix is already open or not found in the provided time then the step as well as workflow fails.
3
Path of Application
Provide the full path of the Windows Desktop Application executable.
4
Windows load timeout
This is maximum time provided after opening the application to load application window elements.
4
Mode
Select ‘WINDOWS’ or ‘JAVA_APPLET’ from the drop down list.
Generally WINDOWS mode is used for .Net Windows-based applications while JAVA_APPLET is used for applet based applications(e.g. Oracle E-business suite application)
The step is used to read value of any element on the Windows Application.
No.
Field Name
Description
1
Step Name
Name of the step. This name has to be unique in a single workflow.
2
Prefix
Prefix is populated when working with popup windows and multiple domains. Prefix is meant to get an identifier for an instance of an application.
This field must be provided if it is returned by Desktop Spy. If Prefix is not returned by Desktop Spy it should be left blank.
If prefix is blank it assigns a default prefix.
Read Parameter Tab:
No.
Field Name
Description
Input Fields:
1
Accessor/Alternative
Accessor is a Windows Desktop application element identifier for a selected prefix above. This field is populated with Accessor or alternative Accessor.
In case the Prefix field is blank it uses the default prefix.
2
Read Type
Read Type can be Text or Value depending on the element type. (For e.g. for Button Label Read Type is text and for field Read Type is value).
3
Output
Provide a name of a field to store the value read.
4
Mode
Select ‘WINDOWS’ or ‘JAVA_APPLET’ from the drop down list.
Generally WINDOWS mode is used for .Net Windows-based applications while JAVA_APPLET is used for applet based applications(e.g. Oracle E-business suite application).
This step is a start node to be able to use any succeeding Desktop plugin steps in a workflow.
No.
Field Name
Description
1
Step Name
Name of the step. This name has to be unique in a single workflow.
2
Start node
Enable the checkbox if this step is the first step in the workflow.
3
Applet Support
Enable checkbox for Applet support in the workflow.
4
Open Application
If this checkbox is enabled the three fields below are also enabled else the three fields below are disabled.
If this checkbox is disabled this step is used to simply starts Desktop plugin driver.
However, If this checkbox is enabled it starts Desktop plugin driver. Additionally, the step can be used to open any Windows Application.
5
Prefix
Prefix is populated when working with popup windows and multiple domains. Prefix is meant to get an identifier for an instance of an application window. Prefix is usually the title for the application window.
This field must be provided if it is returned by Desktop Spy. If Prefix is not returned by Desktop Spy it should be left blank.
If prefix is blank it assigns a default prefix.
If we need to specify a wait time for an application window (with a specified prefix) to open then provide values in prefix as well as Windows load timeout field below. Both are mandatory.
Note: If the application window with the specified prefix is already open or not found in the provided time then the step as well as workflow fail.
6
Path of Application
Provide the full path of the Windows Desktop Application executable
7
Windows load timeout(in millisecond)
This is maximum time provided after opening the application to load application window elements.
8
Mode
Select ‘WINDOWS’ or ‘JAVA_APPLET’ from the drop down list.
Generally WINDOWS mode is used for .Net Windows-based applications while JAVA_APPLET is used for applet based applications(e.g. Oracle E-business suite application)
The step is used to stop Desktop plugin engine.
No.
Field Name
Description
1
Step Name
Name of the step. This name has to be unique in a single workflow.
The step is used to check the status of Desktop utilities.
No.
Field Name
Description
1
Step Name
Name of the step. This name has to be unique in a single workflow.
2
Prefix
Prefix is populated when working with popup windows and multiple domains. Prefix is meant to get an identifier for an instance of an application.
This field must be provided if it is returned by Desktop Spy. If Prefix is not returned by Desktop Spy it should be left blank.
If prefix is blank it assigns a default prefix.
3
Accessor/Alternative
Accessor is a Windows Desktop application element identifier for a selected prefix above. This field is populated with Accessor or alternative Accessor.
In case the Prefix field is blank it uses the default prefix.
4
Utilities Type
Select a value from the drop down list.
- Exists
- Is Checked
- Is Enabled
- Is Visible
- Application Exists
5
Output
Provide a field name to store the value of output. This is a Boolean value.
6
Mode
Select ‘WINDOWS’ or ‘JAVA_APPLET’ from the drop down list.
Generally WINDOWS mode is used for .Net Windows-based applications while JAVA_APPLET is used for applet based applications(e.g. Oracle E-business suite application)
The Desktop WaitUntil step waits until a desktop application window is open or exists or element is present, visible, checked or enabled on the desktop application window in Desktop automation. The maximum wait time is until the timeout specified. The Desktop WaitUntil step can also wait for reverse of the above conditions.
No.
Field Name
Description
1
Step Name
Name of the step. This name has to be unique in a single workflow.
2
Prefix
Prefix is populated when working with popup windows and multiple domains. Prefix is meant to get an identifier for an instance of an application.
This field must be provided if it is returned by Desktop Spy. If Prefix is not returned by Desktop Spy it should be left blank.
If prefix is blank it assigns a default prefix.
3
Accessor/Alternative
Accessor is a Windows Desktop application element identifier for a selected prefix above. This field is populated with Accessor or alternative Accessor.
In case the Prefix field is blank it uses the default prefix.
4
Wait until condition
5
reverse of above condition
6
Timeout (in seconds)
Maximum time in seconds to wait for the expected wait until condition else to timeout and fail the step.
7
Mode
Select ‘WINDOWS’ or ‘JAVA_APPLET’ from the drop down list.
Generally WINDOWS mode is used for .Net Windows-based applications while JAVA_APPLET is used for applet based applications(e.g. Oracle E-business suite application)
The step is used to write text in a windows desktop application.
No.
Field Name
Description
1
Step Name
Name of the step. This name has to be unique in a single workflow.
2
Prefix
Prefix is populated when working with popup windows and multiple domains. Prefix is meant to get an identifier for an instance of an application.
This field must be provided if it is returned by Desktop Spy. If Prefix is not returned by Desktop Spy it should be left blank.
If prefix is blank it assigns a default prefix.
Write Parameter Tab:
No.
Field Name
Description
Fields:
1
Accessor/Alternative
Accessor is a Windows Desktop application element identifier for a selected prefix above. This field is populated with Accessor or alternative Accessor.
In case the Prefix field is blank it uses the default prefix.
2
Write Type
Write Type can be Set New Text or Append Text depending on the activity required.
3
Input Text
Provide the Text to be set as New Text or to Append.
4
Mode
Select ‘WINDOWS’ or ‘JAVA_APPLET’ from the drop down list.
Generally WINDOWS mode is used for .Net Windows-based applications while JAVA_APPLET is used for applet based applications(e.g. Oracle E-business suite application)