IA-Connect UI

An array of UIA elements to check, in JSON format.

Add the following expression here: workflow()

The parent UIA window handle (a value of 1 or higher) to act as the starting point for the search. This can be discovered via Inspection using actions like '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 UIA 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 UIA tree will be searched.

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

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 [ClassName] 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 number of elements to search when looking for the target element in the UIA tree. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). By default, this is set to 0 (unlimited). This input is typically used to optimise element searching.

The maximum relative tree depth to search for child elements beneath the parent element. Direct child elements will have a depth value of 1. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). Set to 0 for an unlimited search depth. This input is typically used to optimise element searching.

The maximum number of child elements to search beneath each element when searching the UIA tree for the target element. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). By default, this is set to 0 (unlimited). This input is typically used to optimise element searching.

A comma separated list of UIA element localized control types to not traverse (step into) when searching the UIA tree for the target element. The search will still check if an individual element matches the search criteria, however it will not search any child elements of that element if its localized control type is on this exclusion list. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). This input is typically used to optimise element searching.

Add the following expression here: workflow()

The parent UIA window handle (a value of 1 or higher) to act as the starting point for the search. This can be discovered via Inspection using actions like '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 UIA 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 UIA tree will be searched.

If set to true then IA-Connect will attempt to expand the list before searching for the list item elements. This is useful for dynamic lists as the list item elements may not be created until the list is expanded.

If set to true then the list will be collapsed after executing the search.

The index in the list of the item to be clicked.

The number of seconds to wait between the expand and collapse actions if these are set to true.

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 [ClassName] 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 number of elements to search when looking for the target element in the UIA tree. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). By default, this is set to 0 (unlimited). This input is typically used to optimise element searching.

The maximum relative tree depth to search for child elements beneath the parent element. Direct child elements will have a depth value of 1. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). Set to 0 for an unlimited search depth. This input is typically used to optimise element searching.

The maximum number of child elements to search beneath each element when searching the UIA tree for the target element. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). By default, this is set to 0 (unlimited). This input is typically used to optimise element searching.

A comma separated list of UIA element localized control types to not traverse (step into) when searching the UIA tree for the target element. The search will still check if an individual element matches the search criteria, however it will not search any child elements of that element if its localized control type is on this exclusion list. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). This input is typically used to optimise element searching.

Add the following expression here: workflow()

The parent UIA window handle (a value of 1 or higher) to act as the starting point for the search. This can be discovered via Inspection using actions like '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 UIA 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 UIA tree will be searched.

If set to true then IA-Connect will attempt to expand the list before searching for the list item elements. This is useful for dynamic lists as the list item elements may not be created until the list is expanded.

If set to true then the list will be collapsed after executing the search.

The name of the element item to be clicked.

The number of seconds to wait between the expand and collapse actions if these are set to true.

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 [ClassName] 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 number of elements to search when looking for the target element in the UIA tree. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). By default, this is set to 0 (unlimited). This input is typically used to optimise element searching.

The maximum relative tree depth to search for child elements beneath the parent element. Direct child elements will have a depth value of 1. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). Set to 0 for an unlimited search depth. This input is typically used to optimise element searching.

The maximum number of child elements to search beneath each element when searching the UIA tree for the target element. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). By default, this is set to 0 (unlimited). This input is typically used to optimise element searching.

A comma separated list of UIA element localized control types to not traverse (step into) when searching the UIA tree for the target element. The search will still check if an individual element matches the search criteria, however it will not search any child elements of that element if its localized control type is on this exclusion list. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). This input is typically used to optimise element searching.

Add the following expression here: workflow()

The parent UIA window handle (a value of 1 or higher) to act as the starting point for the search. This can be discovered via Inspection using actions like '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 UIA 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 UIA 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 [ClassName] 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 number of elements to search when looking for the target element in the UIA tree. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). By default, this is set to 0 (unlimited). This input is typically used to optimise element searching.

The maximum relative tree depth to search for child elements beneath the parent element. Direct child elements will have a depth value of 1. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). Set to 0 for an unlimited search depth. This input is typically used to optimise element searching.

The maximum number of child elements to search beneath each element when searching the UIA tree for the target element. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). By default, this is set to 0 (unlimited). This input is typically used to optimise element searching.

A comma separated list of UIA element localized control types to not traverse (step into) when searching the UIA tree for the target element. The search will still check if an individual element matches the search criteria, however it will not search any child elements of that element if its localized control type is on this exclusion list. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). This input is typically used to optimise element searching.

Add the following expression here: workflow()

The parent UIA window handle (a value of 1 or higher) to act as the starting point for the search. This can be discovered via Inspection using actions like '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 UIA 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 UIA 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 [ClassName] 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 number of elements to search when looking for the target element in the UIA tree. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). By default, this is set to 0 (unlimited). This input is typically used to optimise element searching.

The maximum relative tree depth to search for child elements beneath the parent element. Direct child elements will have a depth value of 1. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). Set to 0 for an unlimited search depth. This input is typically used to optimise element searching.

The maximum number of child elements to search beneath each element when searching the UIA tree for the target element. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). By default, this is set to 0 (unlimited). This input is typically used to optimise element searching.

A comma separated list of UIA element localized control types to not traverse (step into) when searching the UIA tree for the target element. The search will still check if an individual element matches the search criteria, however it will not search any child elements of that element if its localized control type is on this exclusion list. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). This input is typically used to optimise element searching.

Add the following expression here: workflow()

The name of the process to search for, e.g. notepad.

Add the following expression here: workflow()

The element class name of the top level window to search for, e.g. 'Notepad'.

The title of the top level window to search for.

The optional process Id of the process which owns the window (for example, as provided by the output of the 'Run Process' action in the IA-Connect Environment / Session actions). Set to 0 to not search by process Id.

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 against available window properties. Example 1: [Width] < 200. Example 2: [Title] like '*Excel' AND [IsMinimised] = False AND [IsResizeable] = True. See the documentation for more examples.

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 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 specified (a value of 1 or higher) then the search will only consider elements owned by a process with this Process ID (PID). If IA-Connect launched the process then the PID is provided by the 'Run Process' action in the IA-Connect Environment / Session actions. If you don't know the PID then leave this field blank (or 0).

If set to true then the whole UIA 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 UIA tree will be searched.

If set to true, a handle to the located element will be returned. This handle can be used in further actions to act as a 'parent' handle.

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 [ClassName] 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 also included in the search. If set to false then only a process matching the exact 'Search process Id' will be returned.

The maximum number of elements to search when looking for the target element in the UIA tree. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). By default, this is set to 0 (unlimited). This input is typically used to optimise element searching.

The maximum relative tree depth to search for child elements beneath the parent element. Direct child elements will have a depth value of 1. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). Set to 0 for an unlimited search depth. This input is typically used to optimise element searching.

The maximum number of child elements to search beneath each element when searching the UIA tree for the target element. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). By default, this is set to 0 (unlimited). This input is typically used to optimise element searching.

A comma separated list of UIA element localized control types to not traverse (step into) when searching the UIA tree for the target element. The search will still check if an individual element matches the search criteria, however it will not search any child elements of that element if its localized control type is on this exclusion list. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). This input is typically used to optimise element searching.

Add the following expression here: workflow()

The parent UIA window handle (a value of 1 or higher) to act as the starting point for the search. This can be discovered via Inspection using actions like '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 specified (a value of 1 or higher) then the search will only consider elements owned by a process with this Process ID (PID). If IA-Connect launched the process then the PID is provided by the 'Run Process' action in the IA-Connect Environment / Session actions. If you don't know the PID then leave this field blank (or 0).

If set to true then the whole UIA 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 UIA tree will be searched.

If set to true, a handle to the located element will be returned. This handle can be used in further actions to act as a 'parent' handle.

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 [ClassName] 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 also included in the search. If set to false then only a process matching the exact 'Search process Id' will be searched.

The maximum number of elements to search when looking for the target element in the UIA tree. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). By default, this is set to 0 (unlimited). This input is typically used to optimise element searching.

The maximum relative tree depth to search for child elements beneath the parent element. Direct child elements will have a depth value of 1. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). Set to 0 for an unlimited search depth. This input is typically used to optimise element searching.

The maximum number of child elements to search beneath each element when searching the UIA tree for the target element. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). By default, this is set to 0 (unlimited). This input is typically used to optimise element searching.

A comma separated list of UIA element localized control types to not traverse (step into) when searching the UIA tree for the target element. The search will still check if an individual element matches the search criteria, however it will not search any child elements of that element if its localized control type is on this exclusion list. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). This input is typically used to optimise element searching.

Add the following expression here: workflow()

The parent UIA window handle (a value of 1 or higher) to act as the starting point for the search. This can be discovered via Inspection using actions like '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 UIA 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 UIA tree will be searched.

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.

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 [ClassName] 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 number of elements to search when looking for the target element in the UIA tree. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). By default, this is set to 0 (unlimited). This input is typically used to optimise element searching.

The maximum relative tree depth to search for child elements beneath the parent element. Direct child elements will have a depth value of 1. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). Set to 0 for an unlimited search depth. This input is typically used to optimise element searching.

The maximum number of child elements to search beneath each element when searching the UIA tree for the target element. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). By default, this is set to 0 (unlimited). This input is typically used to optimise element searching.

A comma separated list of UIA element localized control types to not traverse (step into) when searching the UIA tree for the target element. The search will still check if an individual element matches the search criteria, however it will not search any child elements of that element if its localized control type is on this exclusion list. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). This input is typically used to optimise element searching.

Add the following expression here: workflow()

The parent UIA window handle (a value of 1 or higher) to act as the starting point for the search. This can be discovered via Inspection using actions like '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 UIA 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 UIA 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 [ClassName] 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 number of elements to search when looking for the target element in the UIA tree. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). By default, this is set to 0 (unlimited). This input is typically used to optimise element searching.

The maximum relative tree depth to search for child elements beneath the parent element. Direct child elements will have a depth value of 1. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). Set to 0 for an unlimited search depth. This input is typically used to optimise element searching.

The maximum number of child elements to search beneath each element when searching the UIA tree for the target element. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). By default, this is set to 0 (unlimited). This input is typically used to optimise element searching.

A comma separated list of UIA element localized control types to not traverse (step into) when searching the UIA tree for the target element. The search will still check if an individual element matches the search criteria, however it will not search any child elements of that element if its localized control type is on this exclusion list. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). This input is typically used to optimise element searching.

Add the following expression here: workflow()

The parent UIA window handle (a value of 1 or higher) to act as the starting point for the search. This can be discovered via Inspection using actions like '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 UIA 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 UIA 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 [ClassName] 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 number of elements to search when looking for the target element in the UIA tree. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). By default, this is set to 0 (unlimited). This input is typically used to optimise element searching.

The maximum relative tree depth to search for child elements beneath the parent element. Direct child elements will have a depth value of 1. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). Set to 0 for an unlimited search depth. This input is typically used to optimise element searching.

The maximum number of child elements to search beneath each element when searching the UIA tree for the target element. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). By default, this is set to 0 (unlimited). This input is typically used to optimise element searching.

A comma separated list of UIA element localized control types to not traverse (step into) when searching the UIA tree for the target element. The search will still check if an individual element matches the search criteria, however it will not search any child elements of that element if its localized control type is on this exclusion list. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). This input is typically used to optimise element searching.

Add the following expression here: workflow()

The parent UIA window handle (a value of 1 or higher) to act as the starting point for the search. This can be discovered via Inspection using actions like 'Wait for desktop element' or 'Wait for element'.

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 UIA 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 UIA tree will be searched.

If set to true, a handle to the located element will be returned. This handle can be used in further actions to act as a 'parent' handle.

If set to true than the value of the located element will be returned.

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 UIA tree), you can alternatively specify a negative index starting from -1.

The maximum number of elements to return, or 0 to return all items.

Add the following expression here: workflow()

The parent UIA window handle (a value of 1 or higher) to act as the starting point for the search. This can be discovered via Inspection using actions like '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 UIA 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 UIA 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 [ClassName] 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 cell header subelement localized control type to search for. Leave blank if not searching for cell headers.

The cell header subelement control type (an non-localized integer) to search for. This is the same value across different languages. Leave at 0 if not searching for cell headers.

The cell subelement localized control type to search for.

The cell subelement control type (an non-localized integer) to search for. This is the same value across different languages.

If set to true then the UIA tree below the located element will be searched for cell and cell header subelements (i.e. the element values which will populate the cells in the output table). This is more thorough but can take longer. You may wish to set this to false if you are only interested in elements directly beneath the element.

The index of the first cell header subelement to return, starting from 1. If you wish to return the elements in the reverse order (from the bottom of the UIA tree), you can alternatively specify a negative index starting from -1.

The maximum number of cell header subelements to return, or 0 to return all subelements.

The index of the first cell subelement to return, starting from 1. If you wish to return the elements in the reverse order (from the bottom of the UIA tree), you can alternatively specify a negative index starting from -1.

The maximum number of cell subelements to return, or 0 to return all subelements.

The number of columns you would like in the output table. This value must be correct for the element being read, or you will receive unexpected results.

The priority for using the cell subelement value as the value to use in the output table. 1 is highest priority. 2 is second priority. 3 is third priority. 0 is do not use.

The priority for using the cell subelement text value as the value to use in the output table. 1 is highest priority. 2 is second priority. 3 is third priority. 0 is do not use.

The priority for using the cell subelement name (common for labels) as the value to use in the output table. 1 is highest priority. 2 is second priority. 3 is third priority. 0 is do not use.

The minimum width in pixels of a cell subelement to be included in the table.

The minimum height in pixels of a cell subelement to be included in the table.

Only include cell subelements which are fully contained within the bounding box. By default the bounding box is huge to include all elements.

Only include cell subelements which are fully contained within the bounding box. By default the bounding box is huge to include all elements.

Only include cell subelements which are fully contained within the bounding box. By default the bounding box is huge to include all elements.

Only include cell subelements which are fully contained within the bounding box. By default the bounding box is huge to include all elements.

If set to false (the default), the IA-Connect Agent will read the table immediately and return the contents to the Director. If reading large tables, this action may time out. If set to true, the IA-Connect Agent will read the table as an Agent thread and the IA-Connect Director (or Orchestrator, PowerShell module, Blue Prism) can monitor the status of this Agent thread, waiting for it to complete. This allows large tables to be read without timeouts. IA-Connect Agents 9.3 and earlier could only read tables immediately, not as an Agent thread.

If you previously ran this action as an Agent thread and set 'Seconds to wait for thread' to 0, provide the Agent thread Id to retrieve the results. This Agent thread Id will have been provided by the earlier call to this action. Set to 0 (the default) if you are reading a table (and hence not retrieving the results of a previous query run as an Agent thread).

If 'Read table as thread' is set to true, how many seconds to wait for the Agent thread to complete. If the Agent thread reading the table hasn't completed in this time, an exception will be raised. Set to 0 to bypass the wait: The Agent will continue to read the table, but also be available for the next action. You can then retrieve the results (the contents of the table) at a later time by using the action 'Wait for Agent thread to complete successfully' to wait for the Agent thread to complete and then re-run this 'Get multiple UIA elements as table' action with the input 'Retrieve output data for thread Id' set to the Agent thread Id.

The maximum number of elements to search when looking for the target element in the UIA tree. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). By default, this is set to 0 (unlimited). This input is typically used to optimise element searching.

The maximum relative tree depth to search for child elements beneath the parent element. Direct child elements will have a depth value of 1. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). Set to 0 for an unlimited search depth. This input is typically used to optimise element searching.

The maximum number of child elements to search beneath each element when searching the UIA tree for the target element. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). By default, this is set to 0 (unlimited). This input is typically used to optimise element searching.

A comma separated list of UIA element localized control types to not traverse (step into) when searching the UIA tree for the target element. The search will still check if an individual element matches the search criteria, however it will not search any child elements of that element if its localized control type is on this exclusion list. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). This input is typically used to optimise element searching.

Add the following expression here: workflow()

The UIA handle for the target element.

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

Add the following expression here: workflow()

The parent UIA window handle (a value of 1 or higher) to act as the starting point for the search. This can be discovered via Inspection using actions like '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 UIA 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 UIA tree will be searched.

If set to true then only onscreen columns will be returned.

If set to true then only onscreen rows will be returned.

If set to true, null values will be returned as '' (i.e. blank). If set to false, null values are typically returned as '(null)'.

By default, the header row in a DataGrid has the UIA element name 'Top Row'. If the header row has a different name, specify that name here.

If this input is set to then the row UIA name will be stored in a column in the output collection. The name of the column is defined by the input 'Name of column to store row UIA name'.

If the input 'Return row UIA name' is set to true then this input specifies the name of the column in the output collection to hold the row UIA name.

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 [ClassName] 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 element index of the first item (row) to return, starting from 1.

The maximum number of items (rows) to return, or 0 to return all items (rows).

Some datagrids have a few empty / null row elements in the UIA tree (usually at the top) and IA-Connect will automatically skip these row elements since they don't represent anything in the table which is visible in the UI. If this input is set to 0 (the default), the IA-Connect Agent will always scan row elements from the first row onwards, even if 'First item to return' is set to retrieve rows deeper within the table. This ensures consistency with row index numbers but impacts performance since all rows from the first row to the requested row(s) need to be scanned. If you are certain the only empty / null row elements in the table are within the first N (e.g. 10) rows, you can set this to N (e.g. 10) to potentially improve performance. Do not set to a value other than 0 unless you know what you are doing.

If set to false (the default), the IA-Connect Agent will read the table immediately and return the contents to the Director. If reading large tables, this action may time out. If set to true, the IA-Connect Agent will read the table as an Agent thread and the IA-Connect Director (or Orchestrator, PowerShell module, Blue Prism) can monitor the status of this Agent thread, waiting for it to complete. This allows large tables to be read without timeouts. IA-Connect Agents 9.3 and earlier could only read tables immediately, not as an Agent thread.

If you previously ran this action as an Agent thread and set 'Seconds to wait for thread' to 0, provide the Agent thread Id to retrieve the results. This Agent thread Id will have been provided by the earlier call to this action. Set to 0 (the default) if you are reading a datagrid (and hence not retrieving the results of a previous query run as an Agent thread).

If 'Read table as thread' is set to true, how many seconds to wait for the Agent thread to complete. If the Agent thread reading the table hasn't completed in this time, an exception will be raised. Set to 0 to bypass the wait: The Agent will continue to read the datagrid, but also be available for the next action. You can then retrieve the results (the contents of the datagrid) at a later time by using the action 'Wait for Agent thread to complete successfully' to wait for the Agent thread to complete and then re-run this 'Get UIA datagrid element contents' action with the input 'Retrieve output data for thread Id' set to the Agent thread Id.

The performance of reading some large datagrids (for example: with thousands of rows) has been observed to improve if you periodically scroll the datagrid into (or near) the location being scrolled. If set to 0 (the default), the datagrid will not be scrolled while reading the contents. If set to a value between 1 and 100, the datagrid will periodically be scrolled (every N percent of the total number of rows) while reading the contents. For example: If set to 20, the datagrid will be scrolled at 0, 20, 40, 60, 80 percent. Alternatively, use 'Scroll datagrid vertically every N rows' to scroll every N rows instead of every N percent.

The performance of reading some large datagrids (for example: with thousands of rows) has been observed to improve if you periodically scroll the datagrid into (or near) the location being scrolled. If set to 0 (the default), the datagrid will not be scrolled while reading the contents. If set to a value 1 or higher, the datagrid will be scrolled every N rows while reading the contents. For example: If set to 5, the datagrid will be scrolled every 5 rows. Alternatively, use 'Scroll datagrid vertically every N percent' to scroll every N percent of the rows instead of every N rows.

If scrolling the datagrid vertically while reading contents, this input defines how IA-Connect will locate the vertical scrollbar. If set to 0, IA-Connect will attempt to scroll the datagrid directly, either by using the 'scroll' pattern (if the datagrid supports it) or by searching for the vertical scrollbar contained within the datagrid. Alternatively, you can specify the IA-Connect UIA handle of the vertical scrollbar element (the scrollbar element itself, not the buttons within) which is a value of 1 or higher.

If scrolling the datagrid vertically while reading contents, this input specifies the minimum numbers of rows required in the table before IA-Connect will perform scrolling. If set to 0, IA-Connect will scroll regardless of the number of rows. If set to a positive number, IA-Connect will only perform scrolling when the datagrid has that number of rows or more.

If scrolling the datagrid vertically while reading contents: Set this input to true if a failure to scroll should be considered an exception, or set to false (the default) if a failure to scroll should be ignored. Common failures to scroll include failing to locate the scrollbars or the scrollbars don't have a UIA pattern suitable for scrolling ('scroll', 'rangevalue' or 'value').

By default, the vertical scrollbar 'row' in a datagrid has the UIA element name 'Vertical Scroll Bar'. If the vertical scrollbar has a different name, specify that name here. This will be used if you want IA-Connect to periodically scroll the datagrid while reading the contents, the input 'Scroll datagrid vertically element handle' field is set to 0 (specifying that IA-Connect should scroll the datagrid directly) but the datagrid doesn't implement the 'scroll' pattern.

The maximum number of elements to search when looking for the target element in the UIA tree. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). By default, this is set to 0 (unlimited). This input is typically used to optimise element searching.

The maximum relative tree depth to search for child elements beneath the parent element. Direct child elements will have a depth value of 1. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). Set to 0 for an unlimited search depth. This input is typically used to optimise element searching.

The maximum number of child elements to search beneath each element when searching the UIA tree for the target element. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). By default, this is set to 0 (unlimited). This input is typically used to optimise element searching.

A comma separated list of UIA element localized control types to not traverse (step into) when searching the UIA tree for the target element. The search will still check if an individual element matches the search criteria, however it will not search any child elements of that element if its localized control type is on this exclusion list. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). This input is typically used to optimise element searching.

Add the following expression here: workflow()

The parent UIA window handle (a value of 1 or higher) to act as the starting point for the search. This can be discovered via Inspection using actions like '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 UIA 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 UIA tree will be searched.

By default, the header row in a DataGrid has the UIA name 'Top Row'. If the header row has a different name, specify that name here.

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 [ClassName] 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 number of elements to search when looking for the target element in the UIA tree. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). By default, this is set to 0 (unlimited). This input is typically used to optimise element searching.

The maximum relative tree depth to search for child elements beneath the parent element. Direct child elements will have a depth value of 1. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). Set to 0 for an unlimited search depth. This input is typically used to optimise element searching.

The maximum number of child elements to search beneath each element when searching the UIA tree for the target element. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). By default, this is set to 0 (unlimited). This input is typically used to optimise element searching.

A comma separated list of UIA element localized control types to not traverse (step into) when searching the UIA tree for the target element. The search will still check if an individual element matches the search criteria, however it will not search any child elements of that element if its localized control type is on this exclusion list. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). This input is typically used to optimise element searching.

Add the following expression here: workflow()

Filter the results by the localized control type of the element.

If specified then the search will only consider elements owned by a process with this Process ID (PID). If IA-Connect launched the process then the PID is provided by the 'Run Process' action in the IA-Connect Environment / Session actions. If you don't know the PID then leave this field blank.

If set to true, a handle to the located element will be returned. This handle can be used in further actions to act as a 'parent' 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 UIA tree), you can alternatively specify a negative index starting from -1.

The maximum number of elements to return, or 0 to return all items.

If set to true and a 'Search process Id' is specified, child processes of that process Id are also included in the search. If set to false then only a process matching the exact 'Search process Id' will be returned.

Add the following expression here: workflow()

The screen X coordinate value (in pixels) where the UIA element should be searched for.

The screen Y coordinate value (in pixels) where the UIA element should be searched for.

Should IA-Connect raise an exception if a UIA element was not located at the specified location?

Add the following expression here: workflow()

The parent UIA window handle (a value of 1 or higher) to act as the starting point for the search. This can be discovered via Inspection using actions like '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 UIA 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 UIA 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 [ClassName] 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 number of elements to search when looking for the target element in the UIA tree. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). By default, this is set to 0 (unlimited). This input is typically used to optimise element searching.

The maximum relative tree depth to search for child elements beneath the parent element. Direct child elements will have a depth value of 1. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). Set to 0 for an unlimited search depth. This input is typically used to optimise element searching.

The maximum number of child elements to search beneath each element when searching the UIA tree for the target element. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). By default, this is set to 0 (unlimited). This input is typically used to optimise element searching.

A comma separated list of UIA element localized control types to not traverse (step into) when searching the UIA tree for the target element. The search will still check if an individual element matches the search criteria, however it will not search any child elements of that element if its localized control type is on this exclusion list. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). This input is typically used to optimise element searching.

Add the following expression here: workflow()

The parent UIA window handle (a value of 1 or higher) to act as the starting point for the search. This can be discovered via Inspection using actions like '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 UIA 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 UIA 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 [ClassName] 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 number of elements to search when looking for the target element in the UIA tree. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). By default, this is set to 0 (unlimited). This input is typically used to optimise element searching.

The maximum relative tree depth to search for child elements beneath the parent element. Direct child elements will have a depth value of 1. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). Set to 0 for an unlimited search depth. This input is typically used to optimise element searching.

The maximum number of child elements to search beneath each element when searching the UIA tree for the target element. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). By default, this is set to 0 (unlimited). This input is typically used to optimise element searching.

A comma separated list of UIA element localized control types to not traverse (step into) when searching the UIA tree for the target element. The search will still check if an individual element matches the search criteria, however it will not search any child elements of that element if its localized control type is on this exclusion list. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). This input is typically used to optimise element searching.

Add the following expression here: workflow()

The parent UIA window handle (a value of 1 or higher) to act as the starting point for the search. This can be discovered via Inspection using actions like '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 UIA 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 UIA tree will be searched.

If set to true, a handle to the located element will be returned. This handle can be used in further actions to act as a 'parent' handle.

If set to true than the value of the located element will be returned.

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 [ClassName] 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 number of elements to search when looking for the target element in the UIA tree. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). By default, this is set to 0 (unlimited). This input is typically used to optimise element searching.

The maximum relative tree depth to search for child elements beneath the parent element. Direct child elements will have a depth value of 1. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). Set to 0 for an unlimited search depth. This input is typically used to optimise element searching.

The maximum number of child elements to search beneath each element when searching the UIA tree for the target element. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). By default, this is set to 0 (unlimited). This input is typically used to optimise element searching.

A comma separated list of UIA element localized control types to not traverse (step into) when searching the UIA tree for the target element. The search will still check if an individual element matches the search criteria, however it will not search any child elements of that element if its localized control type is on this exclusion list. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). This input is typically used to optimise element searching.

For some elements, UIA is unaware of a clickable point within the element and will return an invalid coordinate (for example 0,0) instead of the center of the element. If this input is set to true, IA-Connect will check the validity of the coordinate provided by UIA and, if not within the element's boundary, will ignore the value provided by UIA and use the center of the element instead.

Add the following expression here: workflow()

The UIA handle for the target element.

Add the following expression here: workflow()

The parent UIA window handle (a value of 1 or higher) to act as the starting point for the search. This can be discovered via Inspection using actions like '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 UIA 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 UIA 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 [ClassName] 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).

Search colour in the format 0xAARRGGBB, #AARRGGBB, 0xRRGGBB or #RRGGBB where each colour channel is a byte in hex format (00 is fully off, FF is fully on). For example: #FF0000 for red, #00FF00 for blue, #000000 for black, #FFFFFF for white.

The maximum an element colour can deviate from the search colour before it isn't considered a match. 0 for no deviation. Deviation is measured in RGB values. For example: #FF0000 is 4 different from #FE0102. A deviation of 15 would be a good starting point.

An optional X offset for the left edge of the search area. This allows you to increase (with negative values) or decrease (with positive values) the search area.

An optional X offset for the right edge of the search area. This allows you to increase (with positive values) or decrease (with negative values) the search area.

An optional Y offset for the top edge of the search area. This allows you to increase (with negative values) or decrease (with positive values) the search area.

An optional Y offset for the bottom edge of the search area. This allows you to increase (with positive values) or decrease (with negative values) the search area.

Set to true to automatically hide the Agent (if visible) to ensure it doesn't obscure the element being analysed.

Set to true for the screen coordinates to be returned as physical coordinates. Set to false for the screen coordinates to be returned as virtual coordinates. If the underlying display scaling is 100%, both physical and virtual coordinates are the same. Element coordinates are always returned as virtual coordinates.

The maximum number of elements to search when looking for the target element in the UIA tree. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). By default, this is set to 0 (unlimited). This input is typically used to optimise element searching.

The maximum relative tree depth to search for child elements beneath the parent element. Direct child elements will have a depth value of 1. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). Set to 0 for an unlimited search depth. This input is typically used to optimise element searching.

The maximum number of child elements to search beneath each element when searching the UIA tree for the target element. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). By default, this is set to 0 (unlimited). This input is typically used to optimise element searching.

A comma separated list of UIA element localized control types to not traverse (step into) when searching the UIA tree for the target element. The search will still check if an individual element matches the search criteria, however it will not search any child elements of that element if its localized control type is on this exclusion list. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). This input is typically used to optimise element searching.

Add the following expression here: workflow()

Add the following expression here: workflow()

The parent UIA window handle (a value of 1 or higher) to act as the starting point for the search. This can be discovered via Inspection using actions like '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 UIA 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 UIA 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 [ClassName] 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 number of elements to search when looking for the target element in the UIA tree. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). By default, this is set to 0 (unlimited). This input is typically used to optimise element searching.

The maximum relative tree depth to search for child elements beneath the parent element. Direct child elements will have a depth value of 1. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). Set to 0 for an unlimited search depth. This input is typically used to optimise element searching.

The maximum number of child elements to search beneath each element when searching the UIA tree for the target element. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). By default, this is set to 0 (unlimited). This input is typically used to optimise element searching.

A comma separated list of UIA element localized control types to not traverse (step into) when searching the UIA tree for the target element. The search will still check if an individual element matches the search criteria, however it will not search any child elements of that element if its localized control type is on this exclusion list. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). This input is typically used to optimise element searching.

Add the following expression here: workflow()

The parent UIA window handle (a value of 1 or higher) to act as the starting point for the search. This can be discovered via Inspection using actions like '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 UIA 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 UIA 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 [ClassName] 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 number of elements to search when looking for the target element in the UIA tree. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). By default, this is set to 0 (unlimited). This input is typically used to optimise element searching.

The maximum relative tree depth to search for child elements beneath the parent element. Direct child elements will have a depth value of 1. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). Set to 0 for an unlimited search depth. This input is typically used to optimise element searching.

The maximum number of child elements to search beneath each element when searching the UIA tree for the target element. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). By default, this is set to 0 (unlimited). This input is typically used to optimise element searching.

A comma separated list of UIA element localized control types to not traverse (step into) when searching the UIA tree for the target element. The search will still check if an individual element matches the search criteria, however it will not search any child elements of that element if its localized control type is on this exclusion list. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). This input is typically used to optimise element searching.

Add the following expression here: workflow()

Add the following expression here: workflow()

Add the following expression here: workflow()

Add the following expression here: workflow()

The Id of the process to wait for (as provided by the 'Run Process' action in the IA-Connect Environment / Session actions).

Add the following expression here: workflow()

The name of the process to search for, e.g. notepad.

Add the following expression here: workflow()

The element class name of the top level window to search for, e.g. 'Notepad'.

The title of the top level window to search for.

The optional process Id of the process which owns the window (for example, as provided by the output of the 'Run Process' action in the IA-Connect Environment / Session actions). Set to 0 to not search by process Id.

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 against available window properties. Example 1: [Width] < 200. Example 2: [Title] like '*Excel' AND [IsMinimised] = False AND [IsResizeable] = True. See the documentation for more examples.

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

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

Add the following expression here: workflow()

The parent UIA window handle (a value of 1 or higher) to act as the starting point for the search. This can be discovered via Inspection using actions like '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 UIA 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 UIA tree will be searched.

If set to true then IA-Connect will attempt to expand the list before searching for the list item elements. This is useful for dynamic lists as the list item elements may not be created until the list is expanded.

If set to true then the list will be collapsed after executing the search.

If set to true then the output collection will contain an additional property indicating whether the list item is currently selected.

The number of seconds to wait between the expand and collapse actions if these are set to true.

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 [ClassName] 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 number of elements to search when looking for the target element in the UIA tree. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). By default, this is set to 0 (unlimited). This input is typically used to optimise element searching.

The maximum relative tree depth to search for child elements beneath the parent element. Direct child elements will have a depth value of 1. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). Set to 0 for an unlimited search depth. This input is typically used to optimise element searching.

The maximum number of child elements to search beneath each element when searching the UIA tree for the target element. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). By default, this is set to 0 (unlimited). This input is typically used to optimise element searching.

A comma separated list of UIA element localized control types to not traverse (step into) when searching the UIA tree for the target element. The search will still check if an individual element matches the search criteria, however it will not search any child elements of that element if its localized control type is on this exclusion list. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). This input is typically used to optimise element searching.

Add the following expression here: workflow()

The UIA handle for the target element.

Add the following expression here: workflow()

The optional class name of the top level window to search for, e.g. 'Chrome_WidgetWin_1'.

The optional title of the top level window to search for.

Set to true to only retrieve Win32 windows which the OS considers to be top-level. Set to false to retrieve all Win32 windows. Note that the Win32 definition of a window will include items you might not recognise as a window and many dialogs and message boxes are marked as top-level even though they are a child of a parent window.

Set to true to only retrieve Win32 windows which the OS considers to be visible. Set to false to retrieve both visible and non-visible Win32 windows. Note that offscreen or transparent windows might be marked as visible, but you cannot see them.

Set to true to only retrieve Win32 windows with a title bar. Set to false to retrieve Win32 windows regardless of whether they have a title bar or not. Note that some transparent windows have title bars but you cannot see them.

Set to true to only retrieve Win32 windows with a title (i.e. a title bar containing some text). Set to false to retrieve Win32 windows regardless of whether they have a title. Note that the title bar is the strip across the top of the window whereas the title is the text within it.

Set to true to only retrieve Win32 windows which do not have transparency. Set to false to retrieve Win32 windows regardless of whether they have transparency set or not.

The optional process Id of the process which owns the windows (for example, as provided by the output of the 'Run Process' action in the IA-Connect Environment / Session actions). Set to 0 to not search by process Id.

An optional advanced filter to further restrict the search using conditional operators and any element field. Example 1: [Width] < 200. Example 2: [Title] like '*Excel' AND [IsMinimised] = False AND [IsResizeable] = True. See the documentation for more examples.

If multiple windows match the search, this allows you to specify which window property to sort by. For example: If 'Sort by column name' is [TopEdge] then the list of windows will be returned ordered by top edge. If this field is left blank, windows will be returned in the order they are detected.

If multiple windows match the search and a sort column is specified, set to true (default) to sort ascending or set to false to sort descending.

If set to true, a UIA handle to each located Win32 window will be returned in the output collection (in the column 'UIAHandle'). This handle can be used in further actions to act as a 'parent' handle in IA-Connect UIA actions.

The index of the first window (row) to return, starting from 1.

The maximum number of windows to return, or 0 to return all items.

Add the following expression here: workflow()

The parent UIA window handle (a value of 1 or higher) to act as the starting point for the search. This can be discovered via Inspection using actions like '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 UIA 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 UIA tree will be searched.

The delay (in milliseconds) between each of the clicks.

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

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 [ClassName] 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 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 maximum number of elements to search when looking for the target element in the UIA tree. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). By default, this is set to 0 (unlimited). This input is typically used to optimise element searching.

The maximum relative tree depth to search for child elements beneath the parent element. Direct child elements will have a depth value of 1. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). Set to 0 for an unlimited search depth. This input is typically used to optimise element searching.

The maximum number of child elements to search beneath each element when searching the UIA tree for the target element. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). By default, this is set to 0 (unlimited). This input is typically used to optimise element searching.

A comma separated list of UIA element localized control types to not traverse (step into) when searching the UIA tree for the target element. The search will still check if an individual element matches the search criteria, however it will not search any child elements of that element if its localized control type is on this exclusion list. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). This input is typically used to optimise element searching.

For some elements, UIA is unaware of a clickable point within the element and will return an invalid coordinate (for example 0,0) instead of the center of the element. If this input is set to true, IA-Connect will check the validity of the coordinate provided by UIA and, if not within the element's boundary, will ignore the value provided by UIA and use the center of the element instead.

Add the following expression here: workflow()

The parent UIA window handle (a value of 1 or higher) to act as the starting point for the search. This can be discovered via Inspection using actions like '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 UIA 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 UIA 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 [ClassName] 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 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 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.

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.

Set to true if the password contains (or is entirely) an IA-Connect stored password identifier, in the format {IAConnectPassword:StoredPasswordIdentifier} or an IA-Connect Orchestrator generic credential, in the format {OrchestratorCredential:FriendlyName}. This stored password could have been generated by the 'Generate password' action, for example, or be held by the IA-Connect Orchestrator.

The maximum number of elements to search when looking for the target element in the UIA tree. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). By default, this is set to 0 (unlimited). This input is typically used to optimise element searching.

The maximum relative tree depth to search for child elements beneath the parent element. Direct child elements will have a depth value of 1. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). Set to 0 for an unlimited search depth. This input is typically used to optimise element searching.

The maximum number of child elements to search beneath each element when searching the UIA tree for the target element. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). By default, this is set to 0 (unlimited). This input is typically used to optimise element searching.

A comma separated list of UIA element localized control types to not traverse (step into) when searching the UIA tree for the target element. The search will still check if an individual element matches the search criteria, however it will not search any child elements of that element if its localized control type is on this exclusion list. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). This input is typically used to optimise element searching.

For some elements, UIA is unaware of a clickable point within the element and will return an invalid coordinate (for example 0,0) instead of the center of the element. If this input is set to true, IA-Connect will check the validity of the coordinate provided by UIA and, if not within the element's boundary, will ignore the value provided by UIA and use the center of the element instead.

Add the following expression here: workflow()

The parent UIA window handle (a value of 1 or higher) to act as the starting point for the search. This can be discovered via Inspection using actions like '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 UIA 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 UIA 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 [ClassName] 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 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.

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.

The maximum number of elements to search when looking for the target element in the UIA tree. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). By default, this is set to 0 (unlimited). This input is typically used to optimise element searching.

The maximum relative tree depth to search for child elements beneath the parent element. Direct child elements will have a depth value of 1. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). Set to 0 for an unlimited search depth. This input is typically used to optimise element searching.

The maximum number of child elements to search beneath each element when searching the UIA tree for the target element. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). By default, this is set to 0 (unlimited). This input is typically used to optimise element searching.

A comma separated list of UIA element localized control types to not traverse (step into) when searching the UIA tree for the target element. The search will still check if an individual element matches the search criteria, however it will not search any child elements of that element if its localized control type is on this exclusion list. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). This input is typically used to optimise element searching.

For some elements, UIA is unaware of a clickable point within the element and will return an invalid coordinate (for example 0,0) instead of the center of the element. If this input is set to true, IA-Connect will check the validity of the coordinate provided by UIA and, if not within the element's boundary, will ignore the value provided by UIA and use the center of the element instead.

Add the following expression here: workflow()

The parent UIA window handle (a value of 1 or higher) to act as the starting point for the search. This can be discovered via Inspection using actions like '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 UIA 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 UIA tree will be searched.

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

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 [ClassName] 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 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 maximum number of elements to search when looking for the target element in the UIA tree. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). By default, this is set to 0 (unlimited). This input is typically used to optimise element searching.

The maximum relative tree depth to search for child elements beneath the parent element. Direct child elements will have a depth value of 1. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). Set to 0 for an unlimited search depth. This input is typically used to optimise element searching.

The maximum number of child elements to search beneath each element when searching the UIA tree for the target element. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). By default, this is set to 0 (unlimited). This input is typically used to optimise element searching.

A comma separated list of UIA element localized control types to not traverse (step into) when searching the UIA tree for the target element. The search will still check if an individual element matches the search criteria, however it will not search any child elements of that element if its localized control type is on this exclusion list. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). This input is typically used to optimise element searching.

For some elements, UIA is unaware of a clickable point within the element and will return an invalid coordinate (for example 0,0) instead of the center of the element. If this input is set to true, IA-Connect will check the validity of the coordinate provided by UIA and, if not within the element's boundary, will ignore the value provided by UIA and use the center of the element instead.

Add the following expression here: workflow()

The parent UIA window handle (a value of 1 or higher) to act as the starting point for the search. This can be discovered via Inspection using actions like '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 UIA 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 UIA tree will be searched.

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

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 [ClassName] 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 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 maximum number of elements to search when looking for the target element in the UIA tree. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). By default, this is set to 0 (unlimited). This input is typically used to optimise element searching.

The maximum relative tree depth to search for child elements beneath the parent element. Direct child elements will have a depth value of 1. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). Set to 0 for an unlimited search depth. This input is typically used to optimise element searching.

The maximum number of child elements to search beneath each element when searching the UIA tree for the target element. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). By default, this is set to 0 (unlimited). This input is typically used to optimise element searching.

A comma separated list of UIA element localized control types to not traverse (step into) when searching the UIA tree for the target element. The search will still check if an individual element matches the search criteria, however it will not search any child elements of that element if its localized control type is on this exclusion list. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). This input is typically used to optimise element searching.

For some elements, UIA is unaware of a clickable point within the element and will return an invalid coordinate (for example 0,0) instead of the center of the element. If this input is set to true, IA-Connect will check the validity of the coordinate provided by UIA and, if not within the element's boundary, will ignore the value provided by UIA and use the center of the element instead.

Add the following expression here: workflow()

The parent UIA window handle (a value of 1 or higher) to act as the starting point for the search. This can be discovered via Inspection using actions like '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 UIA 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 UIA 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 [ClassName] 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).

Search colour in the format 0xAARRGGBB, #AARRGGBB, 0xRRGGBB or #RRGGBB where each colour channel is a byte in hex format (00 is fully off, FF is fully on). For example: #FF0000 for red, #00FF00 for blue, #000000 for black, #FFFFFF for white.

The maximum an element colour can deviate from the search colour before it isn't considered a match. 0 for no deviation. Deviation is measured in RGB values. For example: #FF0000 is 4 different from #FE0102. A deviation of 15 would be a good starting point.

An optional X offset for the left edge of the search area. This allows you to increase (with negative values) or decrease (with positive values) the search area.

An optional X offset for the right edge of the search area. This allows you to increase (with positive values) or decrease (with negative values) the search area.

An optional Y offset for the top edge of the search area. This allows you to increase (with negative values) or decrease (with positive values) the search area.

An optional Y offset for the bottom edge of the search area. This allows you to increase (with positive values) or decrease (with negative values) the search area.

The mouse button to press (Left, Right, Middle, Double left).

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 colour region to offset from (Center / Centre / Middle, Left, Right, Top, Bottom, Top Left, Top Right, Bottom Left, Bottom Right).

If performing a double click, the delay (in milliseconds) between each of the clicks.

Set to true to automatically hide the Agent (if visible) to ensure it doesn't obscure the element being analysed.

The maximum number of elements to search when looking for the target element in the UIA tree. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). By default, this is set to 0 (unlimited). This input is typically used to optimise element searching.

The maximum relative tree depth to search for child elements beneath the parent element. Direct child elements will have a depth value of 1. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). Set to 0 for an unlimited search depth. This input is typically used to optimise element searching.

The maximum number of child elements to search beneath each element when searching the UIA tree for the target element. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). By default, this is set to 0 (unlimited). This input is typically used to optimise element searching.

A comma separated list of UIA element localized control types to not traverse (step into) when searching the UIA tree for the target element. The search will still check if an individual element matches the search criteria, however it will not search any child elements of that element if its localized control type is on this exclusion list. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). This input is typically used to optimise element searching.

Add the following expression here: workflow()

The parent UIA window handle (a value of 1 or higher) to act as the starting point for the search. This can be discovered via Inspection using actions like '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 UIA 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 UIA tree will be searched.

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

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 [ClassName] 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 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 maximum number of elements to search when looking for the target element in the UIA tree. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). By default, this is set to 0 (unlimited). This input is typically used to optimise element searching.

The maximum relative tree depth to search for child elements beneath the parent element. Direct child elements will have a depth value of 1. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). Set to 0 for an unlimited search depth. This input is typically used to optimise element searching.

The maximum number of child elements to search beneath each element when searching the UIA tree for the target element. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). By default, this is set to 0 (unlimited). This input is typically used to optimise element searching.

A comma separated list of UIA element localized control types to not traverse (step into) when searching the UIA tree for the target element. The search will still check if an individual element matches the search criteria, however it will not search any child elements of that element if its localized control type is on this exclusion list. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). This input is typically used to optimise element searching.

For some elements, UIA is unaware of a clickable point within the element and will return an invalid coordinate (for example 0,0) instead of the center of the element. If this input is set to true, IA-Connect will check the validity of the coordinate provided by UIA and, if not within the element's boundary, will ignore the value provided by UIA and use the center of the element instead.

Add the following expression here: workflow()

The parent UIA window handle (a value of 1 or higher) to act as the starting point for the search. This can be discovered via Inspection using actions like '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 UIA 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 UIA tree will be searched.

The password value to input.

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 [ClassName] 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).

Set to true if the password contains (or is entirely) an IA-Connect stored password identifier, in the format {IAConnectPassword:StoredPasswordIdentifier} or an IA-Connect Orchestrator generic credential, in the format {OrchestratorCredential:FriendlyName}. This stored password could have been generated by the 'Generate password' action, for example, or be held by the IA-Connect Orchestrator.

The maximum number of elements to search when looking for the target element in the UIA tree. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). By default, this is set to 0 (unlimited). This input is typically used to optimise element searching.

The maximum relative tree depth to search for child elements beneath the parent element. Direct child elements will have a depth value of 1. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). Set to 0 for an unlimited search depth. This input is typically used to optimise element searching.

The maximum number of child elements to search beneath each element when searching the UIA tree for the target element. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). By default, this is set to 0 (unlimited). This input is typically used to optimise element searching.

A comma separated list of UIA element localized control types to not traverse (step into) when searching the UIA tree for the target element. The search will still check if an individual element matches the search criteria, however it will not search any child elements of that element if its localized control type is on this exclusion list. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). This input is typically used to optimise element searching.

If set to true (the default), the IA-Connect Agent will attempt to use a UIA value pattern to perform the text input action. If the UIA value pattern is unavailable in the chosen element, the IA-Connect Agent will fall back to other patterns (enabled or disabled via other inputs to this action). If set to false, the IA-Connect Agent will not attempt to use a value pattern and will immediately fall back to other chosen patterns.

If set to true, the IA-Connect Agent will attempt to use a UIA legacy pattern to perform the text input action if the value pattern is not available (either because it isn't present on the element or because its use was disabled).

Add the following expression here: workflow()

The parent UIA window handle (a value of 1 or higher) to act as the starting point for the search. This can be discovered via Inspection using actions like '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 UIA 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 UIA 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 [ClassName] 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 there is existing text in the element, should this be replaced?

The position (index) to begin inserting text. If there is existing text, the insert position can be used to insert at a specific position within the existing text.

The maximum number of elements to search when looking for the target element in the UIA tree. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). By default, this is set to 0 (unlimited). This input is typically used to optimise element searching.

The maximum relative tree depth to search for child elements beneath the parent element. Direct child elements will have a depth value of 1. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). Set to 0 for an unlimited search depth. This input is typically used to optimise element searching.

The maximum number of child elements to search beneath each element when searching the UIA tree for the target element. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). By default, this is set to 0 (unlimited). This input is typically used to optimise element searching.

A comma separated list of UIA element localized control types to not traverse (step into) when searching the UIA tree for the target element. The search will still check if an individual element matches the search criteria, however it will not search any child elements of that element if its localized control type is on this exclusion list. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). This input is typically used to optimise element searching.

If enabled, the IA-Connect Agent will check the new value of the element after inputting the requested text. If the new value doesn't match the expected value, an exception will be raised. If this input is false (the default), a warning will be entered into the log, but no exception will be raised.

If set to true (the default), the IA-Connect Agent will attempt to use a UIA value pattern to perform the text input action. If the UIA value pattern is unavailable in the chosen element, the IA-Connect Agent will fall back to other patterns (enabled or disabled via other inputs to this action). If set to false, the IA-Connect Agent will not attempt to use a value pattern and will immediately fall back to other chosen patterns.

If set to true, the IA-Connect Agent will attempt to use a UIA legacy pattern to perform the text input action if the value pattern is not available (either because it isn't present on the element or because its use was disabled).

Add the following expression here: workflow()

An array of UIA elements to enter text into, in JSON format.

Add the following expression here: workflow()

The parent UIA window handle (a value of 1 or higher) to act as the starting point for the search. This can be discovered via Inspection using actions like '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 UIA 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 UIA tree will be searched.

The text value to input.

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 [ClassName] 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 there is existing text in the element, should this be replaced?

The position (index) to begin inserting text. If there is existing text, the insert position can be used to insert at a specific position within the existing text.

The maximum number of elements to search when looking for the target element in the UIA tree. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). By default, this is set to 0 (unlimited). This input is typically used to optimise element searching.

The maximum relative tree depth to search for child elements beneath the parent element. Direct child elements will have a depth value of 1. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). Set to 0 for an unlimited search depth. This input is typically used to optimise element searching.

The maximum number of child elements to search beneath each element when searching the UIA tree for the target element. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). By default, this is set to 0 (unlimited). This input is typically used to optimise element searching.

A comma separated list of UIA element localized control types to not traverse (step into) when searching the UIA tree for the target element. The search will still check if an individual element matches the search criteria, however it will not search any child elements of that element if its localized control type is on this exclusion list. This input only works if the UIA element search mode is "Tree walk" (this can be enabled in the settings page in the Inspector). This input is typically used to optimise element searching.

If enabled, the IA-Connect Agent will check the new value of the element after inputting the requested text. If the new value doesn't match the expected value, an exception will be raised. If this input is false (the default), a warning will be entered into the log, but no exception will be raised.

If set to true (the default), the IA-Connect Agent will attempt to use a UIA value pattern to perform the text input action. If the UIA value pattern is unavailable in the chosen element, the IA-Connect Agent will fall back to other patterns (enabled or disabled via other inputs to this action). If set to false, the IA-Connect Agent will not attempt to use a value pattern and will immediately fall back to other chosen patterns.

If set to true, the IA-Connect Agent will attempt to use a UIA legacy pattern to perform the text input action if the value pattern is not available (either because it isn't present on the element or because its use was disabled).

Add the following expression here: workflow()

The parent UIA window handle (a value of 1 or higher) to act as the starting point for the search. This can be discovered via Inspection using actions like '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.