Bug 6660

Automated Testing Tool Issue 11 June, 2021

miguel sosa
24 May, 2021
Product: PowerBuilder Category: Third Party Software
Version: 2019 R2 Build: 2328
Classification: Issue Publishing: Public
Priority: P3
Status: Verifying Reason:
Communication Status: Waiting for Customer
Kai Zhao @Appeon 11 June, 2021
#11
Hi Miguel,

I would like to check with you if the response provided has been helpful enough
to resolve your case. If so, can we proceed to close the ticket?
Otherwise, do let us know if we can provide you with any further assistance and
keep in mind that you are always welcome to open another ticket in case you
need it.

Regards,
ZhaoKai
Kai Zhao @Appeon 02 June, 2021
#10
Hi Miguel,

Thanks for your response! We will wait for your updates. 

Regards,
ZhaoKai
miguel sosa 02 June, 2021
#9
Thank you for the update Kai. We will download PB 2019 R3 and send a test compile to customers to see how the testing goes.
Kai Zhao @Appeon 02 June, 2021
#8
Hi Miguel,

PB 2019 R3 has fixed the issue in bug 4131, and the PB 2019 R3 application works well with UiPath on our end. Please upgrade to PB 2019 R3 build 2703 to see if your application works well. You can get the installer from our Downloads portal at https://account.appeon.com/download/2019 (login required).

Regards,
ZhaoKai
Govinda Lopez @Appeon 01 June, 2021
#7
Hi Miguel,

I will transfer your ticket to our engineering team for further analysis. We will keep you updated on the results here.


Regards,
miguel sosa 01 June, 2021
#6
I actually just noticed there are quite a bit of bugs reported with 2019 and RPA selection including bug 4179 and it can't be coincidence that they all occurred when updating to PB 2019. Now we have a number of customers that use RPA tools complaining it's not working so we do need a solution or changes to be made to PB 2019 next release or some workaround to at least be able to inform our customers it's currently in the works of being fixed.
miguel sosa 01 June, 2021
#5
Hello Govinda,

I just noticed that Bug 4131has the same issue I'm reporting. Was there any changes done to powerbuilder code to correct this possibly in 2019 R3. It seems the issues occurred also when upgrading to PB 2019.

Thanks,
Miguel
Govinda Lopez @Appeon 25 May, 2021
#4
Hi Miguel,

The legacy technology called MSAA is still present and supported. You can still use that and you don't need to modify anything for it to be available. However, solutions like UIPath make use of the new Microsoft UI Automation technology by default. So, if it finds that it is present on your app, it will look for that by default. You might want to check with UIPath if there is a setting to enforce the use of MSAA instead for your PB apps.

Please do let us know if this was useful.


Regards,
miguel sosa 25 May, 2021
#3
Hey Govinda,

Thanks for the feedback. I do see we don't have populated accessibleName nor description in most objects however when I looked at the code back in 2017 R3 it's not populated either yet the Testing software picks up the values correctly. Like I said we just did a source migration from PB2017 R3 to PB2019 R2 without any object modification within the source and that's when it stopped working. There is no way we can go thru all our objects and start assigning Accessibility values. Is there any other possible configuration at the PB/Worspace or project level that can be done?

Thanks,
Miguel
Govinda Lopez @Appeon 24 May, 2021
#2
Hi Miguel Sosa,

To enable support for PowerBuilder controls/objects through Microsoft UI Automation, you will need to set the AccessibleName and AccessibleDescription properties in the controls' Property tab page. Note that AccessibleRole property is unsupported by Microsoft UI Automation.

For example: The following statements set the AccessibleName and AccessibleDescription properties for a command button in a Window:

cb_1.accessiblename = "Delete"
cb_1.accessibledescription = "Deletes selected text"

The following statement sets the AccessibleName property of a button in a DataWindow object:

dw_1.Object.b_1.accessiblename = "Update"

Deployment:

When you deploy an accessible application, you must deploy the pbacc.dll and PBAccessibility.dll files.

Please let us know if the problem persists after applying these changes and corresponding tests.


Regards,
Govinda Lopez @Appeon 24 May, 2021
#1
Hi Miguel Sosa,

To enable support for PowerBuilder controls/objects through Microsoft UI Automation, you will need to set the AccessibleName and AccessibleDescription properties in the controls' Property tab page. Note that AccessibleRole property is unsupported by Microsoft UI Automation.

For example: The following statements set the AccessibleName and AccessibleDescription properties for a command button in a Window:

cb_1.accessiblename = "Delete"
cb_1.accessibledescription = "Deletes selected text"

The following statement sets the AccessibleName property of a button in a DataWindow object:

dw_1.Object.b_1.accessiblename = "Update"

Deployment:

When you deploy an accessible application, you must deploy the pbacc.dll and PBAccessibility.dll files.

Please let us know if the problem persists after applying these changes and corresponding tests.


Regards,
miguel sosa 24 May, 2021
*Phenomenon:
We have a customer using UIPATH (2020.4.1. version) RPA automated testing tool in our application which compiles using Powerbuilder 2019 R2 and when they click on the fields in the application it no longer gets the field value/name so they can’t write their testing scripts since the field value is not recognized.

The same application was being used in our previous release that was compiled in Powerbuilder 207 R3 and it worked correctly. We haven’t done any changes to our explorer nor datawindow values from the previous version to our current.

*Reproduce Steps: Click on any field and the automated testing app doesnt recognize field name.


Remarks:
OS:
Windows Server 2016
Platform:
64-bit
Database Type:
Oracle
Database Version:
Oracle 19c 19.0.0.0.0