I have added some click activities inside my project with Simulate Type =“Check”, It was working fine before but suddenly it stops working. It is only working after making Simulate Type=“Uncheck”.
Same project code is working on another system with same configuration and same ui path version.
Ui path version:- 2018.1.3
Community Edition
MS Windows 10 Pro 64-bit
Has anyone had this problem before or know how to work with it?
simulate click tries to click as soon as the page is loaded. If the page is taking time to load completely it fails in that scenario.
Can use delay to ensure it works correctly always.
I think I had a similar issue. The robot that was working 2018.1.1 failed in 2018.1.3. I had to change all IE clicks from SimulateClick to SendWindowMessage.
Starting with 2018.1.1, you can change the properties for multiple activities at one time, by selecting all desired activities (by holding Ctrl while clicking activities). The shared properties between the selected activities will be displayed in the properties channel. Then you can, for example, check SendWindowMessages, and the change will be applied to all selected activities.
Thanks for sharing this helpful feature of UiPath 2018.1.1 with us.
My project consists of multiple xaml files, is there have feature of ui path for setting any control property on project level, so that will be more useful for us.
Guys can we gather more details about this issue. We are not able to reproduce it in our environment.
share a workflow
share logs (low level tracing)
@vikrammahit “Same project code is working on another system with same configuration and same ui path version.” can you please enable low level tracing and share logs ?
Hi Andrei,
I am facing similar issue of “Simulate Click” Check not working anymore.
IE Version : 11.1358.10586.0
OS Version : Windows-10 Pro 64 bit
UiPath : 2018.1.3
Could you share some details about your project? Was it working before and stopped?
Could you collect the information mentioned in previous posts of this topic? It would help debug the issue.
Sharing your problematic workflow would be helpful as well.