Hi Swaroop,
We've seen similar issues in our environment and I've found that usually it's the attach or launch action that aren't set correctly. Are you able to run your object in debug in the higher environments? If so, can you confirm that the bot can spy any element in the browser window, or is it just the outer window that's available? If just the outer window, check your attach/launch carefully. Try updating your window titles, adding a process name, and utilizing child index of 0 or 1 on attach stages. Add an attach page call and "attached?" decision at the top of every action page in the object to make sure you're attached before navigating. Confirm your launch is the true URL, not some refresh redirect and that there are no unnecessary parameters or settings. Another way to test is to put your launch in the object that's failing (assuming you have multiple objects for the application per best practices?) and see if the elements are available. If the "basic actions" object (launch, log in, etc.) works and subsequent objects do not, that's another indicator that the attach isn't working properly.
Also, my understanding is that the force renderer parameter is to enable UIA mode and won't have an impact on browser mode spying or elements (but I could very well be incorrect there). That said, if you can't get browser mode to work in the other environments and you're otherwise stuck completely, UIA might be a good option. Again, though, I've usually found that if you can't spy any elements within the window in anything other than UIA, the attach probably didn't work correctly.
I would further recommend adding a match index of 1 to each element if you don't already have it- sometimes when BP says it can't find something it's really because it finds too many of that something. I vaguely remember this being a point of confusion for me personally when we were on 6.4.
Hope this helps.
------------------------------
Diane Sanzone
------------------------------
