Sounds like some sort of custom trigger is not being triggered with the automated version.
You say it works when you "click" on it. What method are you using to make the selection in the dropdown? If that makes the selection, but the button does not enable, it sounds like the mouse click itself may be the trigger. Have you tried making the selection (assuming you already have it doing this) then applying a "click" to the dropdown object once your selection is in place?
There are obviously triggers on all these fields which cause the continue button to enable. If you have access to the dev team, they should be able to tell you exactly what these triggers are so you can match them ....
NisHera - The objects are definitely being recognized in TestComplete so I don't think that's an issue. I have also tried adding delays before and after the drop-down selection and it's still failing.
Colin_McCrae - When I say "click" I mean manually intervening and clicking on the drop-down and selecting the value while the test is waiting for the next page's objects to load. I tried what you said and added a manual click after and also tried adding one before and neither one worked, unfortunately. It was a great suggestion, regardless. I have attached a screenshot of part of the test for more context. The drop-downs in question are highlighted in yellow.
I have a bug open with a video attached but the dev team is saying that they can't reproduce it manually so they do not want to spend time fixing it. I would be happy to find a workaround as long as I could get past this without intervention.
Hi all. I did not figure out a solution to this issue but the issue resolved itself when the developers changed the way the Next button works. The drop-downs are still causing issues but they implemented an OnClick Next Button validation that picks up on the values. Thanks for your help!
