Spying Angular web forums using AA mode

[gouthamedara]

I have an application that is built on Angular. As you know, we have dynamic web pages that will load based on the drop down options selected. But when I pass the values to the drop down using HTML edit Select, it is not recognizing the input. As we know, AA is another good way of spying and passing the values as Global Send Keys. This is ideally the best solution. But when I spy using AA, Blue Prism crashes. I am not sure why! Anyone else has similar issues? If so please tell me how you resolved it. Right now I am using surface automation to run the process. It is working perfectly fine but I feel it would be much easier if AA mode works.

[Denis__Dennehy]

Section 3.5 of the Browser Automation Guide mentions this exact issue. The problem is that the application is built to expect a specific event that is not being triggured by the value chageing. You need to do some experimentation to trigger whatever event the application is waiting for to recognise the text has changed. For some applications this is a tab or enter within the element. For some elements the only way for the application to recognise that text is changing is to use Global Send Keys (see the guide on how to use that option correctly). AA mode has a useful navigate option called Focus that sometimes work to ensure the element is on-screen before you use a global click and global sendkeys to it.

[gouthamedara]

I did look at the guides to find answers. That is how I understood some ad-hoc is needed. I played with Surface Automation and found a solution using TAB and global send keys to trigger the action. All is good now but I am just wondering if BP 6 has any updates regarding this issue.

[Denis__Dennehy]

The issue is an application with elements that are not easily accessible - the same problem would occur in every RPA tool and every accessibility screen reader/navigation tool for people with disabilities. Version 6 is due to have new UIA interfaces and a new browser interface (for iE/Edge/Chrome/Firefox) added over the coming months which will increase the scope of what can be done without the need for surface automation, but it is always likely that applications that have not been created and tested with accessibility in mind will always have elements requiring logic like you have had to implement.

[gouthamedara]

Thank you for the clarification. Will look forward to version 6 soon