Getting Appian RPA Recording Error Like 'Unsupported element: Text, Interactions wont be recorded' with Windows(WPF) application

I am getting below error when try to navigate through various Windows(WPF) app controls. Can any once please help to resolve this issue?

Getting stuck in recording due to this error and tried many things but nothing seems working.

And this error is coming on various control like text, Toolbar etc.

  Discussion posts and replies are publicly visible

Parents
  • 0
    Certified Associate Developer

    Hi,

    Ensure that your Appian RPA is up to date, as the latest versions often have enhanced support for WPF applications.

    It's crucial to confirm that the WPF application has been designed with UI accessibility features in mind; this can significantly influence the RPA tool's interaction capabilities.

    In the Appian RPA tool, check and modify the settings if necessary to ensure they align with the requirements for WPF application compatibility.

    When dealing with UI elements that the recorder does not support, consider alternative methods of interaction such as navigating through controls using keyboard shortcuts and tab orders, employing image recognition to identify UI elements, or utilizing coordinate-based clicks for static layouts.

    In instances where the recorder falls short of capturing certain elements, writing custom scripts may be required to enable the necessary interactions.

Reply
  • 0
    Certified Associate Developer

    Hi,

    Ensure that your Appian RPA is up to date, as the latest versions often have enhanced support for WPF applications.

    It's crucial to confirm that the WPF application has been designed with UI accessibility features in mind; this can significantly influence the RPA tool's interaction capabilities.

    In the Appian RPA tool, check and modify the settings if necessary to ensure they align with the requirements for WPF application compatibility.

    When dealing with UI elements that the recorder does not support, consider alternative methods of interaction such as navigating through controls using keyboard shortcuts and tab orders, employing image recognition to identify UI elements, or utilizing coordinate-based clicks for static layouts.

    In instances where the recorder falls short of capturing certain elements, writing custom scripts may be required to enable the necessary interactions.

Children