IA-Connect Java

The first element handle to compare.

The second element handle to compare.

Add the following expression here: workflow()

The Java element handle which is a parent of the element you are searching for. This could be a window you located earlier using 'Wait for Java desktop element'.

The optional Java name of the element to search for. This can be discovered via Inspection.

The optional Java element description of the element to search for. This can be discovered via Inspection.

The optional Java element role of the element to search for. This can be discovered via Inspection.

If set to true then the whole tree below the parent window handle will be searched. This is more thorough but can take longer. If set to false, only elements directly below the parent window handle in the tree will be searched.

The maximum relative depth to search from the parent element for child elements. Direct child elements will have a depth value of 0.

If multiple elements match the search, which element (starting at 1) should be matched. Can be used in conjunction with 'Sort by column' to choose the sort order for matching.

An optional advanced filter to further restrict the search using conditional operators and any element field. Example 1: [Width] < 200. Example 2: [Name] like 'Document*' AND [Role] like 'Label*'. See the documentation for more examples.

If multiple elements match the search, this allows you to specify which element property to sort by. This will be used in conjunction with 'Match index' to pick the required element. For example: If 'Sort by column name' is [TopEdge] and 'Match index' is 1 then the matching element nearest the top of the screen will be matched.

If multiple elements match the search, should 'Match index' match from the top of the sorted list (true) or from the bottom of the sorted list (false).

Should the element search be case sensitive? When set to True, only elements matching the exact string/text searches will be returned. By default, this is set to false.

Should only visible elements be searched? By default, this is set to true.

Should only showing elements be searched? Showing elements are typically items displayed in an alternative tab or collapsed menu. By default, this is set to true.

A comma separated list of roles to not traverse (step into) when searching. The search will still check if the element matches the search criteria however it will not search any child elements. This parameter can be used to optimise element searching. This is only used if the 'Search child elements' input parameter is set to 'True'.

The maximum number of elements to search when looking for the target element, restricting the search to only check the first N number of elements found in the Java tree. By default, this is set to 2000. This parameter can be used to optimise element searching. This is only used if the 'Search child elements' input parameter is set to 'True'.

The maximum number of child elements to search in each element when looking for the target element, restricting the search to only check the first N number of child elements found for each element in the Java tree. By default, this is set to 200. This parameter can be used to optimise element searching. This is only used if the 'Search child elements' input parameter is set to 'True'.

Should the element be checked (true) or unchecked (false)?

If set to true (the default) then IA-Connect Agent will attempt to automatically detect the 'click' action name in non-English locales. If there are more than two possible actions for the element then the 'Override action name' will be used. If set to false then IA-Connect Agent will not attempt to detect the 'click' action name in non-English locales and the action may fail unless an 'Override action name' value is provided.

The name of the 'Click' action in non-English locales, e.g. 'cliquer' or 'hacer clic'. This can be determined from the output of the action 'Get actions for Java element' and is typically case sensitive.

Add the following expression here: workflow()

Either specify the folder containing the Windows Access Bridge DLL (a component of the Java runtime) in the session where the Agent is running or enter the full filename of a Windows Access Bridge DLL to force that particular DLL to be used. If you do not provide a path, then the standard Windows search path will be used.

The location of the IA-JavaAccessBridge.dll COM DLL (a built-in component of the IA-Connect Agent) if you need to host it externally to the EXE (perhaps due to a security allow list). This can either be the full path, or the path relative to the location of the IA-Connect Agent. For example, if both the Agent and the IA-JavaAccessBridge.dll COM DLL are in the same folder then just passing the file name of the DLL is sufficient.

Is the Windows Access Bridge DLL being used 64bit?

If the Windows Access Bridge DLL you are trying to load is 64bit, should this be run via an out-of-process COM DLLSurrogate instead of calling directly (in memory) from IA-Connect. By default, this is set to 'True'. You could try unchecking this if the IA-JavaAccessBridge DLL is being blocked.

Should the Java Access Bridge be enabled? By default, this is set to 'True'.

The path to the .accessibility.properties file which controls whether the Java Access Bridge is enabled. If you do not provide a path, then this defaults to %USERPROFILE%.accessibility.properties.

The maximum number of seconds to wait for IA-Connect to connect to the Java Access Bridge. By default, this is 20 seconds.

Add the following expression here: workflow()

The Java element handle which is a parent of the element you are searching for. This could be a window you located earlier using 'Wait for Java desktop element'.

The screen X coordinate in pixels to locate the element at.

The screen Y coordinate in pixels to locate the element at.

Add the following expression here: workflow()

Should the Java Access Bridge be disabled? By default, this is set to 'True'.

The path to the .accessibility.properties file which controls whether the Java Access Bridge is enabled. If you do not provide a path, then this defaults to %USERPROFILE%.accessibility.properties.

Add the following expression here: workflow()

The optional UIA element name to search for (starting from the parent window handle). This can be discovered via Inspection.

The optional UIA element class name to search for (starting from the parent window handle). This can be discovered via Inspection.

The optional UIA element localized control type to search for (starting from the parent window handle). This can be discovered via Inspection.

The process ID of the running process. This can be retrieved as an output from the "Run Process" action.

If set to true then the whole tree below the parent window handle will be searched. This is more thorough but can take longer. If set to false, only elements directly below the parent window handle in the tree will be searched.

If multiple elements match the search, which element (starting at 1) should be matched. Can be used in conjunction with 'Sort by column' to choose the sort order for matching.

An optional advanced filter to further restrict the search using conditional operators and any element field. Example 1: [Width] < 200. Example 2: [Name] like 'Document*' AND [Role] like 'Label*'. See the documentation for more examples.

If multiple elements match the search, this allows you to specify which element property to sort by. This will be used in conjunction with 'Match index' to pick the required element. For example: If 'Sort by column name' is [TopEdge] and 'Match index' is 1 then the matching element nearest the top of the screen will be matched.

If multiple elements match the search, should 'Match index' match from the top of the sorted list (true) or from the bottom of the sorted list (false).

If set to true and a 'Search process Id' is specified, child processes of that process Id are included in the search. This is common for Java since a launcher EXE often then runs a child 'Java(w).exe' process. If set to false then only a process matching the exact 'Search process Id' will be returned.

Add the following expression here: workflow()

The Java element handle which is a parent of the element you are searching for. This could be a window you located earlier using 'Wait for Java desktop element'.

The optional Java name of the element to search for. This can be discovered via Inspection.

The optional Java element description of the element to search for. This can be discovered via Inspection.

The optional Java element role of the element to search for. This can be discovered via Inspection.

If set to true then the whole tree below the parent window handle will be searched. This is more thorough but can take longer. If set to false, only elements directly below the parent window handle in the tree will be searched.

The maximum relative depth to search from the parent element for child elements. Direct child elements will have a depth value of 0.

If multiple elements match the search, which element (starting at 1) should be matched. Can be used in conjunction with 'Sort by column' to choose the sort order for matching.

An optional advanced filter to further restrict the search using conditional operators and any element field. Example 1: [Width] < 200. Example 2: [Name] like 'Document*' AND [Role] like 'Label*'. See the documentation for more examples.

If multiple elements match the search, this allows you to specify which element property to sort by. This will be used in conjunction with 'Match index' to pick the required element. For example: If 'Sort by column name' is [TopEdge] and 'Match index' is 1 then the matching element nearest the top of the screen will be matched.

If multiple elements match the search, should 'Match index' match from the top of the sorted list (true) or from the bottom of the sorted list (false).

Should the element search be case sensitive? When set to True, only elements matching the exact string/text searches will be returned. By default, this is set to false.

Should only visible elements be searched? By default, this is set to true.

Should only showing elements be searched? Showing elements are typically items displayed in an alternative tab or collapsed menu. By default, this is set to true.

A comma separated list of roles to not traverse (step into) when searching. The search will still check if the element matches the search criteria however it will not search any child elements. This parameter can be used to optimise element searching. This is only used if the 'Search child elements' input parameter is set to 'True'.

The maximum number of elements to search when looking for the target element, restricting the search to only check the first N number of elements found in the Java tree. By default, this is set to 2000. This parameter can be used to optimise element searching. This is only used if the 'Search child elements' input parameter is set to 'True'.

The maximum number of child elements to search in each element when looking for the target element, restricting the search to only check the first N number of child elements found for each element in the Java tree. By default, this is set to 200. This parameter can be used to optimise element searching. This is only used if the 'Search child elements' input parameter is set to 'True'.

Add the following expression here: workflow()

The Java element handle which is a parent of the element you are searching for. This could be a window you located earlier using 'Wait for Java desktop element'.

The optional Java name of the element to search for. This can be discovered via Inspection.

The optional Java element description of the element to search for. This can be discovered via Inspection.

The optional Java element role of the element to search for. This can be discovered via Inspection.

If set to true then the whole tree below the parent window handle will be searched. This is more thorough but can take longer. If set to false, only elements directly below the parent window handle in the tree will be searched.

The maximum relative depth to search from the parent element for child elements. Direct child elements will have a depth value of 0.

If multiple elements match the search, which element (starting at 1) should be matched. Can be used in conjunction with 'Sort by column' to choose the sort order for matching.

An optional advanced filter to further restrict the search using conditional operators and any element field. Example 1: [Width] < 200. Example 2: [Name] like 'Document*' AND [Role] like 'Label*'. See the documentation for more examples.

If multiple elements match the search, this allows you to specify which element property to sort by. This will be used in conjunction with 'Match index' to pick the required element. For example: If 'Sort by column name' is [TopEdge] and 'Match index' is 1 then the matching element nearest the top of the screen will be matched.

If multiple elements match the search, should 'Match index' match from the top of the sorted list (true) or from the bottom of the sorted list (false).

Should the element search be case sensitive? When set to True, only elements matching the exact string/text searches will be returned. By default, this is set to false.

Should only visible elements be searched? By default, this is set to true.

Should only showing elements be searched? Showing elements are typically items displayed in an alternative tab or collapsed menu. By default, this is set to true.

A comma separated list of roles to not traverse (step into) when searching. The search will still check if the element matches the search criteria however it will not search any child elements. This parameter can be used to optimise element searching. This is only used if the 'Search child elements' input parameter is set to 'True'.

The maximum number of elements to search when looking for the target element, restricting the search to only check the first N number of elements found in the Java tree. By default, this is set to 2000. This parameter can be used to optimise element searching. This is only used if the 'Search child elements' input parameter is set to 'True'.

The maximum number of child elements to search in each element when looking for the target element, restricting the search to only check the first N number of child elements found for each element in the Java tree. By default, this is set to 200. This parameter can be used to optimise element searching. This is only used if the 'Search child elements' input parameter is set to 'True'.

The colour of the rectangle to be drawn (e.g. red, green, blue, yellow, purple or orange) or a string hex code e.g. #FF0000.

The thickness (in pixels) of the highlight rectangle border.

Add the following expression here: workflow()

The Java element handle which is a parent of the element you are searching for. This could be a window you located earlier using 'Wait for Java desktop element'.

The optional Java name of the element to search for. This can be discovered via Inspection.

The optional Java element description of the element to search for. This can be discovered via Inspection.

The optional Java element role of the element to search for. This can be discovered via Inspection.

If set to true then the whole tree below the parent window handle will be searched. This is more thorough but can take longer. If set to false, only elements directly below the parent window handle in the tree will be searched.

The maximum relative depth to search from the parent element for child elements. Direct child elements will have a depth value of 0.

If multiple elements match the search, which element (starting at 1) should be matched. Can be used in conjunction with 'Sort by column' to choose the sort order for matching.

An optional advanced filter to further restrict the search using conditional operators and any element field. Example 1: [Width] < 200. Example 2: [Name] like 'Document*' AND [Role] like 'Label*'. See the documentation for more examples.

If multiple elements match the search, this allows you to specify which element property to sort by. This will be used in conjunction with 'Match index' to pick the required element. For example: If 'Sort by column name' is [TopEdge] and 'Match index' is 1 then the matching element nearest the top of the screen will be matched.

If multiple elements match the search, should 'Match index' match from the top of the sorted list (true) or from the bottom of the sorted list (false).

Should the element search be case sensitive? When set to True, only elements matching the exact string/text searches will be returned. By default, this is set to false.

Should only visible elements be searched? By default, this is set to true.

Should only showing elements be searched? Showing elements are typically items displayed in an alternative tab or collapsed menu. By default, this is set to true.

A comma separated list of roles to not traverse (step into) when searching. The search will still check if the element matches the search criteria however it will not search any child elements. This parameter can be used to optimise element searching. This is only used if the 'Search child elements' input parameter is set to 'True'.

The maximum number of elements to search when looking for the target element, restricting the search to only check the first N number of elements found in the Java tree. By default, this is set to 2000. This parameter can be used to optimise element searching. This is only used if the 'Search child elements' input parameter is set to 'True'.

The maximum number of child elements to search in each element when looking for the target element, restricting the search to only check the first N number of child elements found for each element in the Java tree. By default, this is set to 200. This parameter can be used to optimise element searching. This is only used if the 'Search child elements' input parameter is set to 'True'.

If set to 'True' (the default) then the element will be expanded. If set to 'False' then the element will be collapsed.

If set to 'True' then the IA-Connect Agent will validate the element state afterwards to check that the 'Expanded' state matches the expected state and raises an exception if this does not match. For example, if expanding an element then the 'IsExpanded' property should be true. If set to 'False' then the element state is not validated.

The number of seconds to wait for the state change after expanding or collapsing. By default, this is set to 0.05 (20 milliseconds).

Add the following expression here: workflow()

The Java element handle which is a parent of the element you are searching for. This could be a window you located earlier using 'Wait for Java desktop element'.

The optional Java name of the element to search for. This can be discovered via Inspection.

The optional Java element description of the element to search for. This can be discovered via Inspection.

The optional Java element role of the element to search for. This can be discovered via Inspection.

If set to true then the whole tree below the parent window handle will be searched. This is more thorough but can take longer. If set to false, only elements directly below the parent window handle in the tree will be searched.

The maximum relative depth to search from the parent element for child elements. Direct child elements will have a depth value of 0.

If multiple elements match the search, which element (starting at 1) should be matched. Can be used in conjunction with 'Sort by column' to choose the sort order for matching.

An optional advanced filter to further restrict the search using conditional operators and any element field. Example 1: [Width] < 200. Example 2: [Name] like 'Document*' AND [Role] like 'Label*'. See the documentation for more examples.

If multiple elements match the search, this allows you to specify which element property to sort by. This will be used in conjunction with 'Match index' to pick the required element. For example: If 'Sort by column name' is [TopEdge] and 'Match index' is 1 then the matching element nearest the top of the screen will be matched.

If multiple elements match the search, should 'Match index' match from the top of the sorted list (true) or from the bottom of the sorted list (false).

Should the element search be case sensitive? When set to True, only elements matching the exact string/text searches will be returned. By default, this is set to false.

Should only visible elements be searched? By default, this is set to true.

Should only showing elements be searched? Showing elements are typically items displayed in an alternative tab or collapsed menu. By default, this is set to true.

A comma separated list of roles to not traverse (step into) when searching. The search will still check if the element matches the search criteria however it will not search any child elements. This parameter can be used to optimise element searching. This is only used if the 'Search child elements' input parameter is set to 'True'.

The maximum number of elements to search when looking for the target element, restricting the search to only check the first N number of elements found in the Java tree. By default, this is set to 2000. This parameter can be used to optimise element searching. This is only used if the 'Search child elements' input parameter is set to 'True'.

The maximum number of child elements to search in each element when looking for the target element, restricting the search to only check the first N number of child elements found for each element in the Java tree. By default, this is set to 200. This parameter can be used to optimise element searching. This is only used if the 'Search child elements' input parameter is set to 'True'.

Add the following expression here: workflow()

The Java element handle which is a parent of the element you are searching for. This could be a window you located earlier using 'Wait for Java desktop element'.

The optional Java name of the element to search for. This can be discovered via Inspection.

The optional Java element description of the element to search for. This can be discovered via Inspection.

The optional Java element role of the element to search for. This can be discovered via Inspection.

If set to true then the whole tree below the parent window handle will be searched. This is more thorough but can take longer. If set to false, only elements directly below the parent window handle in the tree will be searched.

The maximum relative depth to search from the parent element for child elements. Direct child elements will have a depth value of 0.

If multiple elements match the search, which element (starting at 1) should be matched. Can be used in conjunction with 'Sort by column' to choose the sort order for matching.

An optional advanced filter to further restrict the search using conditional operators and any element field. Example 1: [Width] < 200. Example 2: [Name] like 'Document*' AND [Role] like 'Label*'. See the documentation for more examples.

If multiple elements match the search, this allows you to specify which element property to sort by. This will be used in conjunction with 'Match index' to pick the required element. For example: If 'Sort by column name' is [TopEdge] and 'Match index' is 1 then the matching element nearest the top of the screen will be matched.

If multiple elements match the search, should 'Match index' match from the top of the sorted list (true) or from the bottom of the sorted list (false).

Should the element search be case sensitive? When set to True, only elements matching the exact string/text searches will be returned. By default, this is set to false.

Should only visible elements be searched? By default, this is set to true.

Should only showing elements be searched? Showing elements are typically items displayed in an alternative tab or collapsed menu. By default, this is set to true.

A comma separated list of roles to not traverse (step into) when searching. The search will still check if the element matches the search criteria however it will not search any child elements. This parameter can be used to optimise element searching. This is only used if the 'Search child elements' input parameter is set to 'True'.

The maximum number of elements to search when looking for the target element, restricting the search to only check the first N number of elements found in the Java tree. By default, this is set to 2000. This parameter can be used to optimise element searching. This is only used if the 'Search child elements' input parameter is set to 'True'.

The maximum number of child elements to search in each element when looking for the target element, restricting the search to only check the first N number of child elements found for each element in the Java tree. By default, this is set to 200. This parameter can be used to optimise element searching. This is only used if the 'Search child elements' input parameter is set to 'True'.

Add the following expression here: workflow()

The element handle of the element which you want to return the child element properties for. This could be located using 'Get Java element properties' or some other search which returns an element handle.

The element index of the first item to return, starting from 1. If you wish to return the elements in the reverse order (from the bottom of the tree), you can alternatively specify a negative index starting from -1. For example, an index of -10 would return the tenth item from the bottom.

The maximum number of elements to return. This parameter can be used to return large sets of elements in smaller chunks, for example large tables. Instead of attempting to return the entire table which may cause a timeout for extremely large tables, you could instead return 500 rows at a time.

The maximum length of the description field. This can sometimes contain a large amount of text so setting a maximum value can increase search speed. By default, there is no maximum string length so full descriptions will be returned.

If set to true then all child elements below the parent handle will be searched. This is more thorough but can take longer. If set to false, only direct child elements of the parent handle will be searched.

The optional Java element role of the child elements to search for. This can be discovered via Inspection.

The maximum relative depth to search from the parent element for child elements. Direct child elements will have a depth value of 0.

Add the following expression here: workflow()

The element handle of the element which you want to return the child element properties for. This could be located using 'Get Java element properties' or some other search which returns an element handle.

The maximum length of the description field. This can sometimes contain a large amount of text so setting a maximum value can increase search speed. By default, there is no maximum string length so full descriptions will be returned.

Add the following expression here: workflow()

The optional UIA element localized control type to search for (starting from the parent window handle). This can be discovered via Inspection.

The process ID of the running process. This can be retrieved as an output from the "Run Process" action.

The element index of the first item to return, starting from 1. If you wish to return the elements in the reverse order (from the bottom of the tree), you can alternatively specify a negative index starting from -1. For example, an index of -10 would return the tenth item from the bottom.

The maximum number of elements to return. This parameter can be used to return large sets of elements in smaller chunks, for example large tables. Instead of attempting to return the entire table which may cause a timeout for extremely large tables, you could instead return 500 rows at a time.

If set to true then the whole tree below the parent window handle will be searched. This is more thorough but can take longer. If set to false, only elements directly below the parent window handle in the tree will be searched.

The maximum length of the description field. This can sometimes contain a large amount of text so setting a maximum value can increase search speed. By default, there is no maximum string length so full descriptions will be returned.

If set to true and a 'Search process Id' is specified, child processes of that process Id are included in the search. This is common for Java since a launcher EXE often then runs a child 'Java(w).exe' process. If set to false then only a process matching the exact 'Search process Id' will be returned.

Add the following expression here: workflow()

The Java element handle which is a parent of the element you are searching for. This could be a window you located earlier using 'Wait for Java desktop element'.

The optional Java name of the element to search for. This can be discovered via Inspection.

The optional Java element description of the element to search for. This can be discovered via Inspection.

The optional Java element role of the element to search for. This can be discovered via Inspection.

If set to true then the whole tree below the parent window handle will be searched. This is more thorough but can take longer. If set to false, only elements directly below the parent window handle in the tree will be searched.

The maximum relative depth to search from the parent element for child elements. Direct child elements will have a depth value of 0.

If multiple elements match the search, which element (starting at 1) should be matched. Can be used in conjunction with 'Sort by column' to choose the sort order for matching.

An optional advanced filter to further restrict the search using conditional operators and any element field. Example 1: [Width] < 200. Example 2: [Name] like 'Document*' AND [Role] like 'Label*'. See the documentation for more examples.

If multiple elements match the search, this allows you to specify which element property to sort by. This will be used in conjunction with 'Match index' to pick the required element. For example: If 'Sort by column name' is [TopEdge] and 'Match index' is 1 then the matching element nearest the top of the screen will be matched.

If multiple elements match the search, should 'Match index' match from the top of the sorted list (true) or from the bottom of the sorted list (false).

Should the element search be case sensitive? When set to True, only elements matching the exact string/text searches will be returned. By default, this is set to false.

Should only visible elements be searched? By default, this is set to true.

Should only showing elements be searched? Showing elements are typically items displayed in an alternative tab or collapsed menu. By default, this is set to true.

A comma separated list of roles to not traverse (step into) when searching. The search will still check if the element matches the search criteria however it will not search any child elements. This parameter can be used to optimise element searching. This is only used if the 'Search child elements' input parameter is set to 'True'.

The maximum number of elements to search when looking for the target element, restricting the search to only check the first N number of elements found in the Java tree. By default, this is set to 2000. This parameter can be used to optimise element searching. This is only used if the 'Search child elements' input parameter is set to 'True'.

The maximum number of child elements to search in each element when looking for the target element, restricting the search to only check the first N number of child elements found for each element in the Java tree. By default, this is set to 200. This parameter can be used to optimise element searching. This is only used if the 'Search child elements' input parameter is set to 'True'.

The maximum length of the description field. This can sometimes contain a large amount of text so setting a maximum value can increase search speed. By default, there is no maximum string length so full descriptions will be returned.

Add the following expression here: workflow()

The Java element handle which is a parent of the element you are searching for. This could be a window you located earlier using 'Wait for Java desktop element'.

The optional Java name of the element to search for. This can be discovered via Inspection.

The optional Java element description of the element to search for. This can be discovered via Inspection.

The optional Java element role of the element to search for. This can be discovered via Inspection.

If set to true then the whole tree below the parent window handle will be searched. This is more thorough but can take longer. If set to false, only elements directly below the parent window handle in the tree will be searched.

The maximum relative depth to search from the parent element for child elements. Direct child elements will have a depth value of 0.

If multiple elements match the search, which element (starting at 1) should be matched. Can be used in conjunction with 'Sort by column' to choose the sort order for matching.

An optional advanced filter to further restrict the search using conditional operators and any element field. Example 1: [Width] < 200. Example 2: [Name] like 'Document*' AND [Role] like 'Label*'. See the documentation for more examples.

If multiple elements match the search, this allows you to specify which element property to sort by. This will be used in conjunction with 'Match index' to pick the required element. For example: If 'Sort by column name' is [TopEdge] and 'Match index' is 1 then the matching element nearest the top of the screen will be matched.

If multiple elements match the search, should 'Match index' match from the top of the sorted list (true) or from the bottom of the sorted list (false).

Should the element search be case sensitive? When set to True, only elements matching the exact string/text searches will be returned. By default, this is set to false.

Should only visible elements be searched? By default, this is set to true.

Should only showing elements be searched? Showing elements are typically items displayed in an alternative tab or collapsed menu. By default, this is set to true.

A comma separated list of roles to not traverse (step into) when searching. The search will still check if the element matches the search criteria however it will not search any child elements. This parameter can be used to optimise element searching. This is only used if the 'Search child elements' input parameter is set to 'True'.

The maximum number of elements to search when looking for the target element, restricting the search to only check the first N number of elements found in the Java tree. By default, this is set to 2000. This parameter can be used to optimise element searching. This is only used if the 'Search child elements' input parameter is set to 'True'.

The maximum number of child elements to search in each element when looking for the target element, restricting the search to only check the first N number of child elements found for each element in the Java tree. By default, this is set to 200. This parameter can be used to optimise element searching. This is only used if the 'Search child elements' input parameter is set to 'True'.

The maximum length of the description field. This can sometimes contain a large amount of text so setting a maximum value can increase search speed. By default, there is no maximum string length so full descriptions will be returned.

Add the following expression here: workflow()

The Java element handle which is a parent of the element you are searching for. This could be a window you located earlier using 'Wait for Java desktop element'.

The optional Java name of the element to search for. This can be discovered via Inspection.

The optional Java element description of the element to search for. This can be discovered via Inspection.

The optional Java element role of the element to search for. This can be discovered via Inspection.

If set to true then the whole tree below the parent window handle will be searched. This is more thorough but can take longer. If set to false, only elements directly below the parent window handle in the tree will be searched.

The maximum relative depth to search from the parent element for child elements. Direct child elements will have a depth value of 0.

If multiple elements match the search, which element (starting at 1) should be matched. Can be used in conjunction with 'Sort by column' to choose the sort order for matching.

An optional advanced filter to further restrict the search using conditional operators and any element field. Example 1: [Width] < 200. Example 2: [Name] like 'Document*' AND [Role] like 'Label*'. See the documentation for more examples.

If multiple elements match the search, this allows you to specify which element property to sort by. This will be used in conjunction with 'Match index' to pick the required element. For example: If 'Sort by column name' is [TopEdge] and 'Match index' is 1 then the matching element nearest the top of the screen will be matched.

If multiple elements match the search, should 'Match index' match from the top of the sorted list (true) or from the bottom of the sorted list (false).

Should the element search be case sensitive? When set to True, only elements matching the exact string/text searches will be returned. By default, this is set to false.

Should only visible elements be searched? By default, this is set to true.

Should only showing elements be searched? Showing elements are typically items displayed in an alternative tab or collapsed menu. By default, this is set to true.

A comma separated list of roles to not traverse (step into) when searching. The search will still check if the element matches the search criteria however it will not search any child elements. This parameter can be used to optimise element searching. This is only used if the 'Search child elements' input parameter is set to 'True'.

The maximum number of elements to search when looking for the target element, restricting the search to only check the first N number of elements found in the Java tree. By default, this is set to 2000. This parameter can be used to optimise element searching. This is only used if the 'Search child elements' input parameter is set to 'True'.

The maximum number of child elements to search in each element when looking for the target element, restricting the search to only check the first N number of child elements found for each element in the Java tree. By default, this is set to 200. This parameter can be used to optimise element searching. This is only used if the 'Search child elements' input parameter is set to 'True'.

Add the following expression here: workflow()

The Java element handle which is a parent of the element you are searching for. This could be a window you located earlier using 'Wait for Java desktop element'.

The optional Java name of the element to search for. This can be discovered via Inspection.

The optional Java element description of the element to search for. This can be discovered via Inspection.

The optional Java element role of the element to search for. This can be discovered via Inspection.

If set to true then the whole tree below the parent window handle will be searched. This is more thorough but can take longer. If set to false, only elements directly below the parent window handle in the tree will be searched.

The maximum relative depth to search from the parent element for child elements. Direct child elements will have a depth value of 0.

If multiple elements match the search, which element (starting at 1) should be matched. Can be used in conjunction with 'Sort by column' to choose the sort order for matching.

An optional advanced filter to further restrict the search using conditional operators and any element field. Example 1: [Width] < 200. Example 2: [Name] like 'Document*' AND [Role] like 'Label*'. See the documentation for more examples.

If multiple elements match the search, this allows you to specify which element property to sort by. This will be used in conjunction with 'Match index' to pick the required element. For example: If 'Sort by column name' is [TopEdge] and 'Match index' is 1 then the matching element nearest the top of the screen will be matched.

If multiple elements match the search, should 'Match index' match from the top of the sorted list (true) or from the bottom of the sorted list (false).

Should the element search be case sensitive? When set to True, only elements matching the exact string/text searches will be returned. By default, this is set to false.

Should only visible elements be searched? By default, this is set to true.

Should only showing elements be searched? Showing elements are typically items displayed in an alternative tab or collapsed menu. By default, this is set to true.

A comma separated list of roles to not traverse (step into) when searching. The search will still check if the element matches the search criteria however it will not search any child elements. This parameter can be used to optimise element searching. This is only used if the 'Search child elements' input parameter is set to 'True'.

The maximum number of elements to search when looking for the target element, restricting the search to only check the first N number of elements found in the Java tree. By default, this is set to 2000. This parameter can be used to optimise element searching. This is only used if the 'Search child elements' input parameter is set to 'True'.

The maximum number of child elements to search in each element when looking for the target element, restricting the search to only check the first N number of child elements found for each element in the Java tree. By default, this is set to 200. This parameter can be used to optimise element searching. This is only used if the 'Search child elements' input parameter is set to 'True'.

Add the following expression here: workflow()

The element handle of the element which you want to return the parent element properties for. This could be located using 'Get Java element properties' or some other search which returns an element handle.

The maximum length of the description field. This can sometimes contain a large amount of text so setting a maximum value can increase search speed. By default, there is no maximum string length so full descriptions will be returned.

Add the following expression here: workflow()

The parent UIA window handle to act as the starting point for the search. This can be discovered via Inspection using UIA actions such as 'Wait for desktop element' or 'Wait for element'.

The optional UIA element name to search for (starting from the parent window handle). This can be discovered via Inspection.

The optional UIA element class name to search for (starting from the parent window handle). This can be discovered via Inspection.

The optional UIA element automation ID to search for (starting from the parent window handle). This can be discovered via Inspection.

The optional UIA element localized control type to search for (starting from the parent window handle). This can be discovered via Inspection.

If set to true then the whole tree below the parent window handle will be searched. This is more thorough but can take longer. If set to false, only elements directly below the parent window handle in the tree will be searched.

If multiple elements match the search, which element (starting at 1) should be matched. Can be used in conjunction with 'Sort by column' to choose the sort order for matching.

An optional advanced filter to further restrict the search using conditional operators and any element field. Example 1: [Width] < 200. Example 2: [Name] like 'Document*' AND [Role] like 'Label*'. See the documentation for more examples.

If multiple elements match the search, this allows you to specify which element property to sort by. This will be used in conjunction with 'Match index' to pick the required element. For example: If 'Sort by column name' is [TopEdge] and 'Match index' is 1 then the matching element nearest the top of the screen will be matched.

If multiple elements match the search, should 'Match index' match from the top of the sorted list (true) or from the bottom of the sorted list (false).

The maximum length of the description field. This can sometimes contain a large amount of text so setting a maximum value can increase search speed. By default, there is no maximum string length so full descriptions will be returned.

Add the following expression here: workflow()

The Java element handle which is a parent of the element you are searching for. This could be a window you located earlier using 'Wait for Java desktop element'.

If set to true then the whole tree below the parent window handle will be searched. This is more thorough but can take longer. If set to false, only elements directly below the parent window handle in the tree will be searched.

The maximum relative depth to search from the parent element for child elements. Direct child elements will have a depth value of 0.

Should only visible elements be searched? By default, this is set to true.

Should only showing elements be searched? Showing elements are typically items displayed in an alternative tab or collapsed menu. By default, this is set to true.

A comma separated list of roles to not traverse (step into) when searching. The search will still check if the element matches the search criteria however it will not search any child elements. This parameter can be used to optimise element searching. This is only used if the 'Search child elements' input parameter is set to 'True'.

The maximum number of elements to search when looking for the target element, restricting the search to only check the first N number of elements found in the Java tree. By default, this is set to 2000. This parameter can be used to optimise element searching. This is only used if the 'Search child elements' input parameter is set to 'True'.

The maximum number of child elements to search in each element when looking for the target element, restricting the search to only check the first N number of child elements found for each element in the Java tree. By default, this is set to 200. This parameter can be used to optimise element searching. This is only used if the 'Search child elements' input parameter is set to 'True'.

Should the child element roles in the CSV output be indented? This may help to better visualise the parent and child relationships in the Java element tree. By default, this is set to 'True'.

Should the element descriptions be included in the CSV output? By default, this is set to 'True'.

Should the element dimensions (height, width and bounding edges) be included in the CSV output? By default, this is set to 'True'.

Add the following expression here: workflow()

The Java element handle which is a parent of the element you are searching for. This could be a window you located earlier using 'Wait for Java desktop element'.

The optional Java name of the element to search for. This can be discovered via Inspection.

The optional Java element description of the element to search for. This can be discovered via Inspection.

The optional Java element role of the element to search for. This can be discovered via Inspection.

If set to true then the whole tree below the parent window handle will be searched. This is more thorough but can take longer. If set to false, only elements directly below the parent window handle in the tree will be searched.

The maximum relative depth to search from the parent element for child elements. Direct child elements will have a depth value of 0.

If multiple elements match the search, which element (starting at 1) should be matched. Can be used in conjunction with 'Sort by column' to choose the sort order for matching.

An optional advanced filter to further restrict the search using conditional operators and any element field. Example 1: [Width] < 200. Example 2: [Name] like 'Document*' AND [Role] like 'Label*'. See the documentation for more examples.

If multiple elements match the search, this allows you to specify which element property to sort by. This will be used in conjunction with 'Match index' to pick the required element. For example: If 'Sort by column name' is [TopEdge] and 'Match index' is 1 then the matching element nearest the top of the screen will be matched.

If multiple elements match the search, should 'Match index' match from the top of the sorted list (true) or from the bottom of the sorted list (false).

Should the element search be case sensitive? When set to True, only elements matching the exact string/text searches will be returned. By default, this is set to false.

Should only visible elements be searched? By default, this is set to true.

Should only showing elements be searched? Showing elements are typically items displayed in an alternative tab or collapsed menu. By default, this is set to true.

A comma separated list of roles to not traverse (step into) when searching. The search will still check if the element matches the search criteria however it will not search any child elements. This parameter can be used to optimise element searching. This is only used if the 'Search child elements' input parameter is set to 'True'.

The maximum number of elements to search when looking for the target element, restricting the search to only check the first N number of elements found in the Java tree. By default, this is set to 2000. This parameter can be used to optimise element searching. This is only used if the 'Search child elements' input parameter is set to 'True'.

The maximum number of child elements to search in each element when looking for the target element, restricting the search to only check the first N number of child elements found for each element in the Java tree. By default, this is set to 200. This parameter can be used to optimise element searching. This is only used if the 'Search child elements' input parameter is set to 'True'.

Should the child element roles in the CSV output be indented? This may help to better visualise the parent and child relationships in the Java element tree. By default, this is set to 'True'.

Should the element descriptions be included in the CSV output? By default, this is set to 'True'.

Should the element dimensions (height, width and bounding edges) be included in the CSV output? By default, this is set to 'True'.

Add the following expression here: workflow()

The Java element handle which is a parent of the element you are searching for. This could be a window you located earlier using 'Wait for Java desktop element'.

The optional Java name of the element to search for. This can be discovered via Inspection.

The optional Java element description of the element to search for. This can be discovered via Inspection.

The optional Java element role of the element to search for. This can be discovered via Inspection.

If set to true then the whole tree below the parent window handle will be searched. This is more thorough but can take longer. If set to false, only elements directly below the parent window handle in the tree will be searched.

The maximum relative depth to search from the parent element for child elements. Direct child elements will have a depth value of 0.

If multiple elements match the search, which element (starting at 1) should be matched. Can be used in conjunction with 'Sort by column' to choose the sort order for matching.

An optional advanced filter to further restrict the search using conditional operators and any element field. Example 1: [Width] < 200. Example 2: [Name] like 'Document*' AND [Role] like 'Label*'. See the documentation for more examples.

If multiple elements match the search, this allows you to specify which element property to sort by. This will be used in conjunction with 'Match index' to pick the required element. For example: If 'Sort by column name' is [TopEdge] and 'Match index' is 1 then the matching element nearest the top of the screen will be matched.

If multiple elements match the search, should 'Match index' match from the top of the sorted list (true) or from the bottom of the sorted list (false).

Should the element search be case sensitive? When set to True, only elements matching the exact string/text searches will be returned. By default, this is set to false.

Should only visible elements be searched? By default, this is set to true.

Should only showing elements be searched? Showing elements are typically items displayed in an alternative tab or collapsed menu. By default, this is set to true.

A comma separated list of roles to not traverse (step into) when searching. The search will still check if the element matches the search criteria however it will not search any child elements. This parameter can be used to optimise element searching. This is only used if the 'Search child elements' input parameter is set to 'True'.

The maximum number of elements to search when looking for the target element, restricting the search to only check the first N number of elements found in the Java tree. By default, this is set to 2000. This parameter can be used to optimise element searching. This is only used if the 'Search child elements' input parameter is set to 'True'.

The maximum number of child elements to search in each element when looking for the target element, restricting the search to only check the first N number of child elements found for each element in the Java tree. By default, this is set to 200. This parameter can be used to optimise element searching. This is only used if the 'Search child elements' input parameter is set to 'True'.

If set to 'True' then the IA-Connect Agent will attempt to obtain a list of all options in the selection by selecting each one in turn (in JAB). If set to 'False' (the default) then the 'Get list of options by reading labels' parameter should be set to 'True' otherwise the list of options will not be read.

If set to 'True' then the IA-Connect Agent will attempt to obtain a list of all options in the selection by reading the child labels (in the JAB tree). For drop-down lists you will almost certainly need to set the 'Expand first' parameter to 'True' because the child elements aren't exposed until the list drops down. Also set the 'Collapse after' parameter to 'True' to close the list afterwards. The 'Get list of options by selecting' parameter should also be set to 'False' or this option will be ignored (as you can't get the list via both methods). If set to 'False' (the default) then the 'Get list of options by selecting' parameter should be set to 'True' otherwise the list of options will not be read.

If set to 'true' then the action will attempt to expand the list before searching for the list item elements. This is useful for dynamic lists as the other list item elements may not be created until the list is expanded. If set to false (the default) then the list will not be expanded.

If set to true then the list will be collapsed after executing the search. If set to false (the default) then the list will not be collapsed.

The number of seconds to wait between the expand and collapse actions, if these are set to 'True'. By default, this is 0.05 (20 milliseconds).

The maximum number of list items to return, by default this is 100.

Add the following expression here: workflow()

The Java element handle which is a parent of the element you are searching for. This could be a window you located earlier using 'Wait for Java desktop element'.

The optional Java name of the element to search for. This can be discovered via Inspection.

The optional Java element description of the element to search for. This can be discovered via Inspection.

The optional Java element role of the element to search for. This can be discovered via Inspection.

If set to true then the whole tree below the parent window handle will be searched. This is more thorough but can take longer. If set to false, only elements directly below the parent window handle in the tree will be searched.

The maximum relative depth to search from the parent element for child elements. Direct child elements will have a depth value of 0.

If multiple elements match the search, which element (starting at 1) should be matched. Can be used in conjunction with 'Sort by column' to choose the sort order for matching.

An optional advanced filter to further restrict the search using conditional operators and any element field. Example 1: [Width] < 200. Example 2: [Name] like 'Document*' AND [Role] like 'Label*'. See the documentation for more examples.

If multiple elements match the search, this allows you to specify which element property to sort by. This will be used in conjunction with 'Match index' to pick the required element. For example: If 'Sort by column name' is [TopEdge] and 'Match index' is 1 then the matching element nearest the top of the screen will be matched.

If multiple elements match the search, should 'Match index' match from the top of the sorted list (true) or from the bottom of the sorted list (false).

Should the element search be case sensitive? When set to True, only elements matching the exact string/text searches will be returned. By default, this is set to false.

Should only visible elements be searched? By default, this is set to true.

Should only showing elements be searched? Showing elements are typically items displayed in an alternative tab or collapsed menu. By default, this is set to true.

A comma separated list of roles to not traverse (step into) when searching. The search will still check if the element matches the search criteria however it will not search any child elements. This parameter can be used to optimise element searching. This is only used if the 'Search child elements' input parameter is set to 'True'.

The maximum number of elements to search when looking for the target element, restricting the search to only check the first N number of elements found in the Java tree. By default, this is set to 2000. This parameter can be used to optimise element searching. This is only used if the 'Search child elements' input parameter is set to 'True'.

The maximum number of child elements to search in each element when looking for the target element, restricting the search to only check the first N number of child elements found for each element in the Java tree. By default, this is set to 200. This parameter can be used to optimise element searching. This is only used if the 'Search child elements' input parameter is set to 'True'.

The index (starting at 1) of the list item state to query.

Add the following expression here: workflow()

The Java element handle which is a parent of the element you are searching for. This could be a window you located earlier using 'Wait for Java desktop element'.

The optional Java name of the element to search for. This can be discovered via Inspection.

The optional Java element description of the element to search for. This can be discovered via Inspection.

The optional Java element role of the element to search for. This can be discovered via Inspection.

If set to true then the whole tree below the parent window handle will be searched. This is more thorough but can take longer. If set to false, only elements directly below the parent window handle in the tree will be searched.

The maximum relative depth to search from the parent element for child elements. Direct child elements will have a depth value of 0.

If multiple elements match the search, which element (starting at 1) should be matched. Can be used in conjunction with 'Sort by column' to choose the sort order for matching.

An optional advanced filter to further restrict the search using conditional operators and any element field. Example 1: [Width] < 200. Example 2: [Name] like 'Document*' AND [Role] like 'Label*'. See the documentation for more examples.

If multiple elements match the search, this allows you to specify which element property to sort by. This will be used in conjunction with 'Match index' to pick the required element. For example: If 'Sort by column name' is [TopEdge] and 'Match index' is 1 then the matching element nearest the top of the screen will be matched.

If multiple elements match the search, should 'Match index' match from the top of the sorted list (true) or from the bottom of the sorted list (false).

Should the element search be case sensitive? When set to True, only elements matching the exact string/text searches will be returned. By default, this is set to false.

Should only visible elements be searched? By default, this is set to true.

Should only showing elements be searched? Showing elements are typically items displayed in an alternative tab or collapsed menu. By default, this is set to true.

A comma separated list of roles to not traverse (step into) when searching. The search will still check if the element matches the search criteria however it will not search any child elements. This parameter can be used to optimise element searching. This is only used if the 'Search child elements' input parameter is set to 'True'.

The maximum number of elements to search when looking for the target element, restricting the search to only check the first N number of elements found in the Java tree. By default, this is set to 2000. This parameter can be used to optimise element searching. This is only used if the 'Search child elements' input parameter is set to 'True'.

The maximum number of child elements to search in each element when looking for the target element, restricting the search to only check the first N number of child elements found for each element in the Java tree. By default, this is set to 200. This parameter can be used to optimise element searching. This is only used if the 'Search child elements' input parameter is set to 'True'.

The name of the list item to select or deselect.

If set to 'True' then the item name search will be case sensitive (e.g. it must match exactly to the list item). If set to 'False' (the default) then the item name search will not be case sensitive.

Add the following expression here: workflow()

The Java element handle for the parent table element you are searching. This could be a table you located earlier using 'Get Java element properties'.

The screen X coordinate in pixels to locate the table cell at.

The screen Y coordinate in pixels to locate the table cell at.

Should an element handle be returned for the cell?

Add the following expression here: workflow()

The Java element handle which is a parent of the element you are searching for. This could be a window you located earlier using 'Wait for Java desktop element'.

The optional Java name of the element to search for. This can be discovered via Inspection.

The optional Java element description of the element to search for. This can be discovered via Inspection.

The optional Java element role of the element to search for. This can be discovered via Inspection.

If set to true then the whole tree below the parent window handle will be searched. This is more thorough but can take longer. If set to false, only elements directly below the parent window handle in the tree will be searched.

The maximum relative depth to search from the parent element for child elements. Direct child elements will have a depth value of 0.

If multiple elements match the search, which element (starting at 1) should be matched. Can be used in conjunction with 'Sort by column' to choose the sort order for matching.

An optional advanced filter to further restrict the search using conditional operators and any element field. Example 1: [Width] < 200. Example 2: [Name] like 'Document*' AND [Role] like 'Label*'. See the documentation for more examples.

If multiple elements match the search, this allows you to specify which element property to sort by. This will be used in conjunction with 'Match index' to pick the required element. For example: If 'Sort by column name' is [TopEdge] and 'Match index' is 1 then the matching element nearest the top of the screen will be matched.

If multiple elements match the search, should 'Match index' match from the top of the sorted list (true) or from the bottom of the sorted list (false).

Should the element search be case sensitive? When set to True, only elements matching the exact string/text searches will be returned. By default, this is set to false.

Should only visible elements be searched? By default, this is set to true.

Should only showing elements be searched? Showing elements are typically items displayed in an alternative tab or collapsed menu. By default, this is set to true.

A comma separated list of roles to not traverse (step into) when searching. The search will still check if the element matches the search criteria however it will not search any child elements. This parameter can be used to optimise element searching. This is only used if the 'Search child elements' input parameter is set to 'True'.

The maximum number of elements to search when looking for the target element, restricting the search to only check the first N number of elements found in the Java tree. By default, this is set to 2000. This parameter can be used to optimise element searching. This is only used if the 'Search child elements' input parameter is set to 'True'.

The maximum number of child elements to search in each element when looking for the target element, restricting the search to only check the first N number of child elements found for each element in the Java tree. By default, this is set to 200. This parameter can be used to optimise element searching. This is only used if the 'Search child elements' input parameter is set to 'True'.

The row index of the cell in the table, starting at 1.

The column index of the cell in the table, starting at 1.

If set to true then an element handle will be returned for the cell.

The viewport element typically contains the table and represents the visible area of the table. If set to 'True' (the default) then IA-Connect Agent will attempt to detect the table visible bounds and the index of the cells at each corner by calculating the size of the viewport. This allows you to determine which components of the table are currently visible on screen. If set to 'False' then the viewport coordinates will not be populated.

If set to 'True' (the default) then the parent elements of the viewport will also be processed to help refine the visible size of the viewport. This is useful if it is embedded in another viewport. If set to 'False' then viewport parent elements will not be processed.

The maximum number of parent elements to process when enumerating the viewport. By default, this is set to 50.

The roles of the viewport parent element to consider when enumerating to calculate the viewport size. This is used to exclude parent elements that are smaller in size than the viewport which can skew the size calculation, for example page tabs. By default, these are: Panel, Viewport, Layered pane, Root pane.

A left inner margin for the enumerated viewport. This value can be used to exclude any cells which might be only showing by a single pixel or two and are almost entirely offscreen. By default, this is set to 2 and should only be increased if you are trying to influence the data returned by the IA-Connect Agent.

A top inner margin for the enumerated viewport. This value can be used to exclude any cells which might be only showing by a single pixel or two and are almost entirely offscreen. By default, this is set to 2 and should only be increased if you are trying to influence the data returned by the IA-Connect Agent.

A right inner margin for the enumerated viewport. This value can be used to exclude any cells which might be only showing by a single pixel or two and are almost entirely offscreen. By default, this is set to 2 and should only be increased if you are trying to influence the data returned by the IA-Connect Agent.

A bottom inner margin for the enumerated viewport. This value can be used to exclude any cells which might be only showing by a single pixel or two and are almost entirely offscreen. By default, this is set to 2 and should only be increased if you are trying to influence the data returned by the IA-Connect Agent.

Add the following expression here: workflow()

The Java element handle which is a parent of the element you are searching for. This could be a window you located earlier using 'Wait for Java desktop element'.

The optional Java name of the element to search for. This can be discovered via Inspection.

The optional Java element description of the element to search for. This can be discovered via Inspection.

The optional Java element role of the element to search for. This can be discovered via Inspection.

If set to true then the whole tree below the parent window handle will be searched. This is more thorough but can take longer. If set to false, only elements directly below the parent window handle in the tree will be searched.

The maximum relative depth to search from the parent element for child elements. Direct child elements will have a depth value of 0.

If multiple elements match the search, which element (starting at 1) should be matched. Can be used in conjunction with 'Sort by column' to choose the sort order for matching.

An optional advanced filter to further restrict the search using conditional operators and any element field. Example 1: [Width] < 200. Example 2: [Name] like 'Document*' AND [Role] like 'Label*'. See the documentation for more examples.

If multiple elements match the search, this allows you to specify which element property to sort by. This will be used in conjunction with 'Match index' to pick the required element. For example: If 'Sort by column name' is [TopEdge] and 'Match index' is 1 then the matching element nearest the top of the screen will be matched.

If multiple elements match the search, should 'Match index' match from the top of the sorted list (true) or from the bottom of the sorted list (false).

Should the element search be case sensitive? When set to True, only elements matching the exact string/text searches will be returned. By default, this is set to false.

Should only visible elements be searched? By default, this is set to true.

Should only showing elements be searched? Showing elements are typically items displayed in an alternative tab or collapsed menu. By default, this is set to true.

A comma separated list of roles to not traverse (step into) when searching. The search will still check if the element matches the search criteria however it will not search any child elements. This parameter can be used to optimise element searching. This is only used if the 'Search child elements' input parameter is set to 'True'.

The maximum number of elements to search when looking for the target element, restricting the search to only check the first N number of elements found in the Java tree. By default, this is set to 2000. This parameter can be used to optimise element searching. This is only used if the 'Search child elements' input parameter is set to 'True'.

The maximum number of child elements to search in each element when looking for the target element, restricting the search to only check the first N number of child elements found for each element in the Java tree. By default, this is set to 200. This parameter can be used to optimise element searching. This is only used if the 'Search child elements' input parameter is set to 'True'.

The index of the first row to return. By default, this is set to 1.

The maximum number of rows to return. By default, all rows are returned.

The index of the first column to return. By default, this is set to 1.

The maximum number of columns to return. By default, all columns are returned.

If set to 'True' then the IA-Connect Agent will attempt to return the output collection columns to match the column names in the Java table. If set to 'False' (the default) then the column headers will be called 'Column_N' in the collection (since collections cannot have blank names).

If set to 'True' (the default) then the IA-Connect Agent will return the row index in the output collection as an additional column. By default, the row index column will be called 'Row_index' however this can be changed by passing a column name in the 'Name of column to store row index' parameter. This is useful if you plan to filter the output collection and keep track of which row the filtered result relates to. If set to 'False' then no row index column will be returned.

If 'Return row index in output collection' is set to 'True' then you can override the default column name of '_Row_Index' by providing a value here.

Add the following expression here: workflow()

The Java element handle which is a parent of the element you are searching for. This could be a window you located earlier using 'Wait for Java desktop element'.

The optional Java name of the element to search for. This can be discovered via Inspection.

The optional Java element description of the element to search for. This can be discovered via Inspection.

The optional Java element role of the element to search for. This can be discovered via Inspection.

If set to true then the whole tree below the parent window handle will be searched. This is more thorough but can take longer. If set to false, only elements directly below the parent window handle in the tree will be searched.

The maximum relative depth to search from the parent element for child elements. Direct child elements will have a depth value of 0.

If multiple elements match the search, which element (starting at 1) should be matched. Can be used in conjunction with 'Sort by column' to choose the sort order for matching.

An optional advanced filter to further restrict the search using conditional operators and any element field. Example 1: [Width] < 200. Example 2: [Name] like 'Document*' AND [Role] like 'Label*'. See the documentation for more examples.

If multiple elements match the search, this allows you to specify which element property to sort by. This will be used in conjunction with 'Match index' to pick the required element. For example: If 'Sort by column name' is [TopEdge] and 'Match index' is 1 then the matching element nearest the top of the screen will be matched.

If multiple elements match the search, should 'Match index' match from the top of the sorted list (true) or from the bottom of the sorted list (false).

Should the element search be case sensitive? When set to True, only elements matching the exact string/text searches will be returned. By default, this is set to false.

Should only visible elements be searched? By default, this is set to true.

Should only showing elements be searched? Showing elements are typically items displayed in an alternative tab or collapsed menu. By default, this is set to true.

A comma separated list of roles to not traverse (step into) when searching. The search will still check if the element matches the search criteria however it will not search any child elements. This parameter can be used to optimise element searching. This is only used if the 'Search child elements' input parameter is set to 'True'.

The maximum number of elements to search when looking for the target element, restricting the search to only check the first N number of elements found in the Java tree. By default, this is set to 2000. This parameter can be used to optimise element searching. This is only used if the 'Search child elements' input parameter is set to 'True'.

The maximum number of child elements to search in each element when looking for the target element, restricting the search to only check the first N number of child elements found for each element in the Java tree. By default, this is set to 200. This parameter can be used to optimise element searching. This is only used if the 'Search child elements' input parameter is set to 'True'.

The viewport element typically contains the table and represents the visible area of the table. If set to 'True' (the default) then IA-Connect Agent will attempt to detect the table visible bounds and the index of the cells at each corner by calculating the size of the viewport. This allows you to determine which components of the table are currently visible on screen. If set to 'False' then the viewport coordinates will not be populated.

If set to 'True' (the default) then the parent elements of the viewport will also be processed to help refine the visible size of the viewport. This is useful if it is embedded in another viewport. If set to 'False' then viewport parent elements will not be processed.

The maximum number of parent elements to process when enumerating the viewport. By default, this is set to 50.

The roles of the viewport parent element to consider when enumerating to calculate the viewport size. This is used to exclude parent elements that are smaller in size than the viewport which can skew the size calculation, for example page tabs. By default, these are: Panel, Viewport, Layered pane, Root pane.

A left inner margin for the enumerated viewport. This value can be used to exclude any cells which might be only showing by a single pixel or two and are almost entirely offscreen. By default, this is set to 2 and should only be increased if you are trying to influence the data returned by the IA-Connect Agent.

A top inner margin for the enumerated viewport. This value can be used to exclude any cells which might be only showing by a single pixel or two and are almost entirely offscreen. By default, this is set to 2 and should only be increased if you are trying to influence the data returned by the IA-Connect Agent.

A right inner margin for the enumerated viewport. This value can be used to exclude any cells which might be only showing by a single pixel or two and are almost entirely offscreen. By default, this is set to 2 and should only be increased if you are trying to influence the data returned by the IA-Connect Agent.

A bottom inner margin for the enumerated viewport. This value can be used to exclude any cells which might be only showing by a single pixel or two and are almost entirely offscreen. By default, this is set to 2 and should only be increased if you are trying to influence the data returned by the IA-Connect Agent.

Add the following expression here: workflow()

The element handle of the element which you want to return all of the parent elements properties for. This could be located using 'Get Java element properties' or some other search which returns an element handle.

The maximum length of the description field. This can sometimes contain a large amount of text so setting a maximum value can increase search speed. By default, there is no maximum string length so full descriptions will be returned.

The maximum number of parent elements to process. By default, this is set to 50.

Add the following expression here: workflow()

The element handle of the element which you want to return the visible bounds for. This could be located using 'Get Java element properties' or some other search which returns an element handle.

The maximum number of parent elements to process when calculating the visible size of the specified element. By default, this is set to 50.

The roles of the parent elements to consider when calculating the element size. This is used to exclude parent elements that are smaller in size than the element which can skew the size calculation, for example page tabs. By default, these are: Panel, Viewport, Layered pane, Root pane.

Should IA-Connect draw a rectangle around the element so that it is visible on screen? By default, this is set to false.

Add the following expression here: workflow()

Add the following expression here: workflow()

The Java Virtual Machine ID. This is unique across all Java virtual machines.

Add the following expression here: workflow()

The Java element handle which is a parent of the element you are searching for. This could be a window you located earlier using 'Wait for Java desktop element'.

The optional Java name of the element to search for. This can be discovered via Inspection.

The optional Java element description of the element to search for. This can be discovered via Inspection.

The optional Java element role of the element to search for. This can be discovered via Inspection.

If set to true then the whole tree below the parent window handle will be searched. This is more thorough but can take longer. If set to false, only elements directly below the parent window handle in the tree will be searched.

The maximum relative depth to search from the parent element for child elements. Direct child elements will have a depth value of 0.

If multiple elements match the search, which element (starting at 1) should be matched. Can be used in conjunction with 'Sort by column' to choose the sort order for matching.

An optional advanced filter to further restrict the search using conditional operators and any element field. Example 1: [Width] < 200. Example 2: [Name] like 'Document*' AND [Role] like 'Label*'. See the documentation for more examples.

If multiple elements match the search, this allows you to specify which element property to sort by. This will be used in conjunction with 'Match index' to pick the required element. For example: If 'Sort by column name' is [TopEdge] and 'Match index' is 1 then the matching element nearest the top of the screen will be matched.

If multiple elements match the search, should 'Match index' match from the top of the sorted list (true) or from the bottom of the sorted list (false).

Should the element search be case sensitive? When set to True, only elements matching the exact string/text searches will be returned. By default, this is set to false.

Should only visible elements be searched? By default, this is set to true.

Should only showing elements be searched? Showing elements are typically items displayed in an alternative tab or collapsed menu. By default, this is set to true.

A comma separated list of roles to not traverse (step into) when searching. The search will still check if the element matches the search criteria however it will not search any child elements. This parameter can be used to optimise element searching. This is only used if the 'Search child elements' input parameter is set to 'True'.

The maximum number of elements to search when looking for the target element, restricting the search to only check the first N number of elements found in the Java tree. By default, this is set to 2000. This parameter can be used to optimise element searching. This is only used if the 'Search child elements' input parameter is set to 'True'.

The maximum number of child elements to search in each element when looking for the target element, restricting the search to only check the first N number of child elements found for each element in the Java tree. By default, this is set to 200. This parameter can be used to optimise element searching. This is only used if the 'Search child elements' input parameter is set to 'True'.

The number of X pixels to offset the click action by. This parameter supports both positive (right) and negative (left) offset values.

The number of Y pixels to offset the click action by. This parameter supports both positive (down) and negative (up) offset values.

The relative position of the element to offset from (Center / Centre / Middle, Left, Right, Top, Bottom, Top Left, Top Right, Bottom Left, Bottom Right).

The delay in milliseconds (thousandths of a second) between the first and second click. The default is 10 milliseconds.

Add the following expression here: workflow()

The Java element handle which is a parent of the element you are searching for. This could be a window you located earlier using 'Wait for Java desktop element'.

The optional Java name of the element to search for. This can be discovered via Inspection.

The optional Java element description of the element to search for. This can be discovered via Inspection.

The optional Java element role of the element to search for. This can be discovered via Inspection.

If set to true then the whole tree below the parent window handle will be searched. This is more thorough but can take longer. If set to false, only elements directly below the parent window handle in the tree will be searched.

The maximum relative depth to search from the parent element for child elements. Direct child elements will have a depth value of 0.

If multiple elements match the search, which element (starting at 1) should be matched. Can be used in conjunction with 'Sort by column' to choose the sort order for matching.

An optional advanced filter to further restrict the search using conditional operators and any element field. Example 1: [Width] < 200. Example 2: [Name] like 'Document*' AND [Role] like 'Label*'. See the documentation for more examples.

If multiple elements match the search, this allows you to specify which element property to sort by. This will be used in conjunction with 'Match index' to pick the required element. For example: If 'Sort by column name' is [TopEdge] and 'Match index' is 1 then the matching element nearest the top of the screen will be matched.

If multiple elements match the search, should 'Match index' match from the top of the sorted list (true) or from the bottom of the sorted list (false).

Should the element search be case sensitive? When set to True, only elements matching the exact string/text searches will be returned. By default, this is set to false.

Should only visible elements be searched? By default, this is set to true.

Should only showing elements be searched? Showing elements are typically items displayed in an alternative tab or collapsed menu. By default, this is set to true.

A comma separated list of roles to not traverse (step into) when searching. The search will still check if the element matches the search criteria however it will not search any child elements. This parameter can be used to optimise element searching. This is only used if the 'Search child elements' input parameter is set to 'True'.

The maximum number of elements to search when looking for the target element, restricting the search to only check the first N number of elements found in the Java tree. By default, this is set to 2000. This parameter can be used to optimise element searching. This is only used if the 'Search child elements' input parameter is set to 'True'.

The maximum number of child elements to search in each element when looking for the target element, restricting the search to only check the first N number of child elements found for each element in the Java tree. By default, this is set to 200. This parameter can be used to optimise element searching. This is only used if the 'Search child elements' input parameter is set to 'True'.

Should IA-Connect attempt to focus the element before global clicking?

Should a global mouse click be performed at the element coordinates (to focus the element) before entering text?

Should any existing value be replaced by double clicking the mouse (to highlight it) and then deleting?

Should any existing value be replaced by pressing Ctrl-A (to highlight all) and then deleting? Some elements may not support highlighting with Ctrl-A in which case the alternative option of 'Replace existing value using double mouse click delete' should be tried.

The password value to global input.

If set to true then send key events (a lower level API which sends simulated keystrokes to the operating system) will be used. If set to false then send keys (a higher level API which sends keystrokes to the focused element) will be used instead.

The number of milliseconds between each key press.

The number of milliseconds between each click if the parameter 'Replace existing value using double mouse click delete' is set to true.

Should symbols in the 'Password to input' not be interpreted as special keys (e.g. + for Shift, ^ for Ctrl)? This should be set to true if you are attempting to input the actual symbols.

Add the following expression here: workflow()

The Java element handle which is a parent of the element you are searching for. This could be a window you located earlier using 'Wait for Java desktop element'.

The optional Java name of the element to search for. This can be discovered via Inspection.

The optional Java element description of the element to search for. This can be discovered via Inspection.

The optional Java element role of the element to search for. This can be discovered via Inspection.

If set to true then the whole tree below the parent window handle will be searched. This is more thorough but can take longer. If set to false, only elements directly below the parent window handle in the tree will be searched.

The maximum relative depth to search from the parent element for child elements. Direct child elements will have a depth value of 0.

If multiple elements match the search, which element (starting at 1) should be matched. Can be used in conjunction with 'Sort by column' to choose the sort order for matching.

An optional advanced filter to further restrict the search using conditional operators and any element field. Example 1: [Width] < 200. Example 2: [Name] like 'Document*' AND [Role] like 'Label*'. See the documentation for more examples.

If multiple elements match the search, this allows you to specify which element property to sort by. This will be used in conjunction with 'Match index' to pick the required element. For example: If 'Sort by column name' is [TopEdge] and 'Match index' is 1 then the matching element nearest the top of the screen will be matched.

If multiple elements match the search, should 'Match index' match from the top of the sorted list (true) or from the bottom of the sorted list (false).

Should the element search be case sensitive? When set to True, only elements matching the exact string/text searches will be returned. By default, this is set to false.

Should only visible elements be searched? By default, this is set to true.

Should only showing elements be searched? Showing elements are typically items displayed in an alternative tab or collapsed menu. By default, this is set to true.

A comma separated list of roles to not traverse (step into) when searching. The search will still check if the element matches the search criteria however it will not search any child elements. This parameter can be used to optimise element searching. This is only used if the 'Search child elements' input parameter is set to 'True'.

The maximum number of elements to search when looking for the target element, restricting the search to only check the first N number of elements found in the Java tree. By default, this is set to 2000. This parameter can be used to optimise element searching. This is only used if the 'Search child elements' input parameter is set to 'True'.

The maximum number of child elements to search in each element when looking for the target element, restricting the search to only check the first N number of child elements found for each element in the Java tree. By default, this is set to 200. This parameter can be used to optimise element searching. This is only used if the 'Search child elements' input parameter is set to 'True'.

Should IA-Connect attempt to focus the element before global clicking?

Should a global mouse click be performed at the element coordinates (to focus the element) before entering text?

Should any existing value be replaced by double clicking the mouse (to highlight it) and then deleting?

Should any existing value be replaced by pressing Ctrl-A (to highlight all) and then deleting? Some elements may not support highlighting with Ctrl-A in which case the alternative option of 'Replace existing value using double mouse click delete' should be tried.

The text value to global input using the keyboard.

If set to true then send key events (a lower level API which sends simulated keystrokes to the operating system) will be used. If set to false then send keys (a higher level API which sends keystrokes to the focused element) will be used instead.

The number of milliseconds between each key press.

The number of milliseconds between each click if the parameter 'Replace existing value using double mouse click delete' is set to true.

Should symbols in the 'Text to input' not be interpreted as special keys (e.g. + for Shift, ^ for Ctrl)? This should be set to true if you are attempting to input the actual symbols.

Add the following expression here: workflow()

The Java element handle which is a parent of the element you are searching for. This could be a window you located earlier using 'Wait for Java desktop element'.

The optional Java name of the element to search for. This can be discovered via Inspection.

The optional Java element description of the element to search for. This can be discovered via Inspection.

The optional Java element role of the element to search for. This can be discovered via Inspection.

If set to true then the whole tree below the parent window handle will be searched. This is more thorough but can take longer. If set to false, only elements directly below the parent window handle in the tree will be searched.

The maximum relative depth to search from the parent element for child elements. Direct child elements will have a depth value of 0.

If multiple elements match the search, which element (starting at 1) should be matched. Can be used in conjunction with 'Sort by column' to choose the sort order for matching.

An optional advanced filter to further restrict the search using conditional operators and any element field. Example 1: [Width] < 200. Example 2: [Name] like 'Document*' AND [Role] like 'Label*'. See the documentation for more examples.

If multiple elements match the search, this allows you to specify which element property to sort by. This will be used in conjunction with 'Match index' to pick the required element. For example: If 'Sort by column name' is [TopEdge] and 'Match index' is 1 then the matching element nearest the top of the screen will be matched.

If multiple elements match the search, should 'Match index' match from the top of the sorted list (true) or from the bottom of the sorted list (false).

Should the element search be case sensitive? When set to True, only elements matching the exact string/text searches will be returned. By default, this is set to false.

Should only visible elements be searched? By default, this is set to true.

Should only showing elements be searched? Showing elements are typically items displayed in an alternative tab or collapsed menu. By default, this is set to true.

A comma separated list of roles to not traverse (step into) when searching. The search will still check if the element matches the search criteria however it will not search any child elements. This parameter can be used to optimise element searching. This is only used if the 'Search child elements' input parameter is set to 'True'.

The maximum number of elements to search when looking for the target element, restricting the search to only check the first N number of elements found in the Java tree. By default, this is set to 2000. This parameter can be used to optimise element searching. This is only used if the 'Search child elements' input parameter is set to 'True'.

The maximum number of child elements to search in each element when looking for the target element, restricting the search to only check the first N number of child elements found for each element in the Java tree. By default, this is set to 200. This parameter can be used to optimise element searching. This is only used if the 'Search child elements' input parameter is set to 'True'.

The number of X pixels to offset the click action by. This parameter supports both positive (right) and negative (left) offset values.

The number of Y pixels to offset the click action by. This parameter supports both positive (down) and negative (up) offset values.

The relative position of the element to offset from (Center / Centre / Middle, Left, Right, Top, Bottom, Top Left, Top Right, Bottom Left, Bottom Right).

The number of times to click the element, by default this is 1.

The number of seconds to wait between clicks, by default this is 0.

Add the following expression here: workflow()

The Java element handle which is a parent of the element you are searching for. This could be a window you located earlier using 'Wait for Java desktop element'.

The optional Java name of the element to search for. This can be discovered via Inspection.

The optional Java element description of the element to search for. This can be discovered via Inspection.

The optional Java element role of the element to search for. This can be discovered via Inspection.

If set to true then the whole tree below the parent window handle will be searched. This is more thorough but can take longer. If set to false, only elements directly below the parent window handle in the tree will be searched.

The maximum relative depth to search from the parent element for child elements. Direct child elements will have a depth value of 0.

If multiple elements match the search, which element (starting at 1) should be matched. Can be used in conjunction with 'Sort by column' to choose the sort order for matching.

An optional advanced filter to further restrict the search using conditional operators and any element field. Example 1: [Width] < 200. Example 2: [Name] like 'Document*' AND [Role] like 'Label*'. See the documentation for more examples.

If multiple elements match the search, this allows you to specify which element property to sort by. This will be used in conjunction with 'Match index' to pick the required element. For example: If 'Sort by column name' is [TopEdge] and 'Match index' is 1 then the matching element nearest the top of the screen will be matched.

If multiple elements match the search, should 'Match index' match from the top of the sorted list (true) or from the bottom of the sorted list (false).

Should the element search be case sensitive? When set to True, only elements matching the exact string/text searches will be returned. By default, this is set to false.

Should only visible elements be searched? By default, this is set to true.

Should only showing elements be searched? Showing elements are typically items displayed in an alternative tab or collapsed menu. By default, this is set to true.

A comma separated list of roles to not traverse (step into) when searching. The search will still check if the element matches the search criteria however it will not search any child elements. This parameter can be used to optimise element searching. This is only used if the 'Search child elements' input parameter is set to 'True'.

The maximum number of elements to search when looking for the target element, restricting the search to only check the first N number of elements found in the Java tree. By default, this is set to 2000. This parameter can be used to optimise element searching. This is only used if the 'Search child elements' input parameter is set to 'True'.

The maximum number of child elements to search in each element when looking for the target element, restricting the search to only check the first N number of child elements found for each element in the Java tree. By default, this is set to 200. This parameter can be used to optimise element searching. This is only used if the 'Search child elements' input parameter is set to 'True'.

The number of X pixels to offset the click action by. This parameter supports both positive (right) and negative (left) offset values.

The number of Y pixels to offset the click action by. This parameter supports both positive (down) and negative (up) offset values.

The relative position of the element to offset from (Center / Centre / Middle, Left, Right, Top, Bottom, Top Left, Top Right, Bottom Left, Bottom Right).

Add the following expression here: workflow()

The Java element handle which is a parent of the element you are searching for. This could be a window you located earlier using 'Wait for Java desktop element'.

The optional Java name of the element to search for. This can be discovered via Inspection.

The optional Java element description of the element to search for. This can be discovered via Inspection.

The optional Java element role of the element to search for. This can be discovered via Inspection.

If set to true then the whole tree below the parent window handle will be searched. This is more thorough but can take longer. If set to false, only elements directly below the parent window handle in the tree will be searched.

The maximum relative depth to search from the parent element for child elements. Direct child elements will have a depth value of 0.

If multiple elements match the search, which element (starting at 1) should be matched. Can be used in conjunction with 'Sort by column' to choose the sort order for matching.

An optional advanced filter to further restrict the search using conditional operators and any element field. Example 1: [Width] < 200. Example 2: [Name] like 'Document*' AND [Role] like 'Label*'. See the documentation for more examples.

If multiple elements match the search, this allows you to specify which element property to sort by. This will be used in conjunction with 'Match index' to pick the required element. For example: If 'Sort by column name' is [TopEdge] and 'Match index' is 1 then the matching element nearest the top of the screen will be matched.

If multiple elements match the search, should 'Match index' match from the top of the sorted list (true) or from the bottom of the sorted list (false).

Should the element search be case sensitive? When set to True, only elements matching the exact string/text searches will be returned. By default, this is set to false.

Should only visible elements be searched? By default, this is set to true.

Should only showing elements be searched? Showing elements are typically items displayed in an alternative tab or collapsed menu. By default, this is set to true.

A comma separated list of roles to not traverse (step into) when searching. The search will still check if the element matches the search criteria however it will not search any child elements. This parameter can be used to optimise element searching. This is only used if the 'Search child elements' input parameter is set to 'True'.

The maximum number of elements to search when looking for the target element, restricting the search to only check the first N number of elements found in the Java tree. By default, this is set to 2000. This parameter can be used to optimise element searching. This is only used if the 'Search child elements' input parameter is set to 'True'.

The maximum number of child elements to search in each element when looking for the target element, restricting the search to only check the first N number of child elements found for each element in the Java tree. By default, this is set to 200. This parameter can be used to optimise element searching. This is only used if the 'Search child elements' input parameter is set to 'True'.

The row index of the cell in the table, starting at 1.

The column index of the cell in the table, starting at 1.

The viewport element typically contains the table and represents the visible area of the table. If set to 'True' (the default) then IA-Connect Agent will attempt to detect the table visible bounds and the index of the cells at each corner by calculating the size of the viewport. This allows you to determine which components of the table are currently visible on screen. If set to 'False' then the viewport coordinates will not be populated.

If set to 'True' (the default) then the parent elements of the viewport will also be processed to help refine the visible size of the viewport. This is useful if it is embedded in another viewport. If set to 'False' then viewport parent elements will not be processed.

The maximum number of parent elements to process when enumerating the viewport. By default, this is set to 50.

The roles of the viewport parent element to consider when enumerating to calculate the viewport size. This is used to exclude parent elements that are smaller in size than the viewport which can skew the size calculation, for example page tabs. By default, these are: Panel, Viewport, Layered pane, Root pane.

A left inner margin for the enumerated viewport. This value can be used to exclude any cells which might be only showing by a single pixel or two and are almost entirely offscreen. By default, this is set to 2 and should only be increased if you are trying to influence the data returned by the IA-Connect Agent.

A top inner margin for the enumerated viewport. This value can be used to exclude any cells which might be only showing by a single pixel or two and are almost entirely offscreen. By default, this is set to 2 and should only be increased if you are trying to influence the data returned by the IA-Connect Agent.

A right inner margin for the enumerated viewport. This value can be used to exclude any cells which might be only showing by a single pixel or two and are almost entirely offscreen. By default, this is set to 2 and should only be increased if you are trying to influence the data returned by the IA-Connect Agent.

A bottom inner margin for the enumerated viewport. This value can be used to exclude any cells which might be only showing by a single pixel or two and are almost entirely offscreen. By default, this is set to 2 and should only be increased if you are trying to influence the data returned by the IA-Connect Agent.

The mouse button to use when clicking on the table cell. Left = 0, Right = 1, Middle = 2, Double left = 3.

The number of X pixels to offset the click action by. This parameter supports both positive (right) and negative (left) offset values.

The number of Y pixels to offset the click action by. This parameter supports both positive (down) and negative (up) offset values.

The relative position of the element to offset from (Center / Centre / Middle, Left, Right, Top, Bottom, Top Left, Top Right, Bottom Left, Bottom Right).

The number of seconds to wait between clicks, by default this is 0.05 (20 milliseconds).

Add the following expression here: workflow()

The Java element handle which is a parent of the element you are searching for. This could be a window you located earlier using 'Wait for Java desktop element'.

The optional Java name of the element to search for. This can be discovered via Inspection.

The optional Java element description of the element to search for. This can be discovered via Inspection.

The optional Java element role of the element to search for. This can be discovered via Inspection.

If set to true then the whole tree below the parent window handle will be searched. This is more thorough but can take longer. If set to false, only elements directly below the parent window handle in the tree will be searched.

The maximum relative depth to search from the parent element for child elements. Direct child elements will have a depth value of 0.

If multiple elements match the search, which element (starting at 1) should be matched. Can be used in conjunction with 'Sort by column' to choose the sort order for matching.

An optional advanced filter to further restrict the search using conditional operators and any element field. Example 1: [Width] < 200. Example 2: [Name] like 'Document*' AND [Role] like 'Label*'. See the documentation for more examples.

If multiple elements match the search, this allows you to specify which element property to sort by. This will be used in conjunction with 'Match index' to pick the required element. For example: If 'Sort by column name' is [TopEdge] and 'Match index' is 1 then the matching element nearest the top of the screen will be matched.

If multiple elements match the search, should 'Match index' match from the top of the sorted list (true) or from the bottom of the sorted list (false).

Should the element search be case sensitive? When set to True, only elements matching the exact string/text searches will be returned. By default, this is set to false.

Should only visible elements be searched? By default, this is set to true.