We are currently experiencing issues when attempting to interact with a web based portal application created in Oracle. We are accessing this portal through Internet Explorer 11.0.46 on Windows 7 Operating system using Blue Prism version 4.2.37.
When spying the elements initially we used the HTML spying mode. The first issue noticed with this approach was that every time the target system was launched the element ID's would change, this was the only unique element and therefore we were required to use wild cards to identify the element. However even when the elements are matched, we are still seeing issues using the control functionality (i.e. When attempting to 'Select Item' in a combo box it will never return a result, weather searching via text or position - we have verified that the control is working manually).
To get around these issues we were required to use Active Accessibility spying mode. However we are now noticing that the element matching rules fail after every new release to the platform (weather the release is to pages we are using or not). We can obviously correct the spying rules but as releases on the platform are likely to be regular this would not be a viable plan for ourselves to proceed with in the long term.
To further compound the issue we are not experiencing consistent failures as the process will work on some CPU's but not others.
Is there anything you can recommend so that we are able to spy through HTML mode and use Blue Prisms in built functions correctly. Alternatively is there any literature on how Blue Prism uses Active Accessibility mode to match items.
