Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (3)

Resolved Powerbuilder2019R2 - Compatibility with RPA automation tools e.g. UIPath

  1. Issue
0
Votes
Undo
  1. rohit ranjan
    rohit ranjan
  2. PowerBuilder
  3. Thursday, 14 October 2021 07:09 AM UTC

Hi Team,

Following the migration of an application developed on PowerBuilder12.5 to PowerBuilder2019R2 Build 2328, a Client is reporting that their RPA automation tool – UIPath, no longer recognizes individual objects within table or grid like structures on the application GUI.

If Powerbuilder2019R2 supports RPA automation tools (in this case UIPath) as it did in Powerbuilder12.5, please advise of any changes.

If it is true please advise any setup or configuration changes that need to be made in Powerbuilder, the OS, or the RPA Tool to enable this functionality.

A support ticket was raised with UiPath and they confirmed that there is no compatibility issue between UiPath and Power Builder.

As some of the selectors are visible and others are not, then it is likely that the selectors inside these elements are set as private. This is normally set by the application developer but may in this case be cause by the builder. For UiPath or the Microsoft Accessibility tool to see the selector, it must be set as public. If this is set by the builder then it is something that could potentially be checked by Appeon.

OS - Windows Server 2016

Could you please suggest or help us on the above issue.

Thanks,

Rohit

Case statement not working when comparing longptr ...
Powerbuilder 2021 Deployed user32.dll Error
Responses (3)
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Thursday, 14 October 2021 13:01 PM UTC
  2. PowerBuilder
  3. # 1

Hi Rohit;

   That does not surprise me. There was even a few big changes "under the hood" from PB 12.5 to 12.6. When Appeon took over PB in July, 2016, SAP gave us the PN 12.6 code line. Appeon's 1st release (PB 2017) was based 100% on that codeine. However since 2017R2 ...though 2019Rx releases the technical architecture "under the hood" changed greatly. 

  The other aspect is that there are many "RPA automation tools" and each one can have various implementations under their hood. So it could just be a simple  imbalance between the two maybe even a tweak of a setting here/there.

Regards ... Chris

 

Comment
There are no comments made yet.
rohit ranjan
rohit ranjan Accepted Answer Pending Moderation
  1. Thursday, 14 October 2021 11:19 AM UTC
  2. PowerBuilder
  3. # 2

In Powerbuilder 2019 R3, new features listed include “UI Accessibility and automation support” where both Micsrosoft Active Accessibility (MSAA) and Microsoft Ui Automation are listed as supported.

In PB 2019 R2, is there any support for UI Accessibility and Automation via MSAA and MS UI Automation?

In PB 12.5, are both MSAA and MS UI Automation supported?

Comment
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Thursday, 14 October 2021 15:19 PM UTC
PB 2019 R2 and older did NOT support Microsoft UI Automation. They only supported MSAA. Do a quick test with PB 2019 R3 and I think you will see it works much better with UI Path.
  1. Helpful
There are no comments made yet.
Armeen Mazda @Appeon
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Thursday, 14 October 2021 07:48 AM UTC
  2. PowerBuilder
  3. # 3

Try PB 2019 R3... it supports Microsoft UI Automation.  https://docs.appeon.com/pb2019r3/whats_new/UI_accessibility_support.html

Comment
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Thursday, 14 October 2021 13:01 PM UTC
Great suggestion Armeen!
  1. Helpful
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.
We use cookies which are necessary for the proper functioning of our websites. We also use cookies to analyze our traffic, improve your experience and provide social media features. If you continue to use this site, you consent to our use of cookies.