What is most valuable?
The solution has drag and drop features, and a development console that's in simple English, so even a non-tech can understand what the code means.
It has controls in boxes, just like Automation Anywhere, which helps alert the developer to take care of the smaller-level details which reduce errors. It's a very good feature.
The solution is comparatively quick to deploy for making smaller automation processes.
What needs improvement?
The solution's recommendation feature needs improvement. So many times it fails, which tells us that although the hardware configuration and software configuration and the environment stay the same, we should expect the automation tool to recognize images correctly, but it does not. There have been issues in which it has failed, and it remains a concern. At times, it crashes, for some unknown reason. We avoid automating any complex automation processes.
We find the solution to be not that user-friendly, and might be using the older version, which really did not have a lot of features, so my review is mostly based on the older version.
WinAutomation could work on a simpler process of providing a development of something that proactively tells us what is wrong in the code, because what is happening right now is that we make the scripting code in some other place and some other control, and we identify errors over there. We simply copy it to this control, which is not even providing any color-coding, or any other assistance to the developers. Copying it from elsewhere is necessary to pick up any errors with ease.
For how long have I used the solution?
I've been using the solution since 2015.
What do I think about the stability of the solution?
We were really fortunate to use the version which has extended the EXEs, so once we make a development in the studio and we compile it, and make an EXE out of it, that EXE can be used on any number of systems. When it comes to identifying images and creating logic based on those images, or moving the mouse to an image, the image recognition randomly fails for unknown reasons, although we've had a lot of assistance around it, and the developers have put a lot of effort to make a way around it, but when the image recognitions fail, it just stays on the system.
What do I think about the scalability of the solution?
It definitely is a scalable solution. The components that we use enable us to deploy as many EXEs on the system as we would like.
We have about four people working on the solution. In terms of execution, so the development team develops robots and creates and compiles EXEs, and the execution team actually executes manually. It is an assisted automation, it's not fully automated, so the trigger has to be done manually.
How are customer service and technical support?
In terms of technical support, response times were not that great, and the technical documentation provided was very limited. There is no forum where one could read other experiences or share advice.
There was a community when WinAutomation formed, but eventually, when the older versions ended support it went away.
We're pretty much left on our own to find solutions to problems at this point. They should at least provide documentation.
How was the initial setup?
The initial setup is very straightforward.
It was easy to wait for the deployment of the mission tasks. It's a quick implementation. When it comes to complex processes, there's a lot of handoffs required, and that's when it becomes a little bit difficult to manage. I'm sure with the new version they have improved this feature.
How long deployment takes depends on the complexity of the processes and the amount of testing planned. It takes a couple of days for a smaller process, and possibly up to two weeks for complex ones.
What other advice do I have?
We've used versions 4.0, 5.1, and 6.0 as well. We use the on-premises deployment model.
In terms of advice I'd give to others, I'd say, first of all, they should make sure they are implementing the most recent version, not the old version that I have used.
However, I'd suggest having a limited scope and to plan to work meticulously because if there is a bigger project, instead of making something wherein you're not able to reuse the components which you have already done for one project, and reuse it for the other project, a lot of time is wasted in copy-pasting code.
I'd rate the solution six out of ten.