What is our primary use case?
I am a solution provider and I implement RPA products and automate processes for my clients.
In my recent deployment of this product, it is primarily used for financial processes, such as reconciliation in Excel. There are different Excel sheets that I reconcile using automation.
How has it helped my organization?
This product helps us by automating functions in finance. Users are able to have attended bots but can save time by handing processes to the bots to run.
The bots are deployed on our on-premises server, and users are able to assign work to them to run while they continue their own work. The processes that the bots are running do not interfere with the day-to-day business. The server simply gives them time for the processes that they are performing.
When a process is running in the background, it is consistent. In situations where processes are running and controlling the user interface, once in a while they might miss what's being clicked.
What is most valuable?
The most valuable features are the Excel activities. It has a number of Excel activities that are quite reliable.
The Studio is used for development and the Control Tower is used for management.
What needs improvement?
This is a Java-based application that takes up a lot of space and when it runs, consumes a lot of memory. This affects the reliability because it gets to a point where it hangs.
There are some basic features missing in the Excel activities. For example, you cannot delete a row or a column, which are some of the things that I would like to be able to do.
An example of something that is difficult to do is get yesterday's date. There is a lot of scripting that has to be done. It's not direct because you can't simply use a date variable and then subtract one day. Instead, you have to do some coding to get it. That was a problem for our deployment because reconciliations are done for the previous day, and when you're naming files with yesterday's date or creating folders according to date, you have to do a lot of manipulation in the code.
For how long have I used the solution?
I worked with WorkFusion for approximately eight months between November 2020 and August 2021.
What do I think about the stability of the solution?
In terms of consistency, it's good. However, in terms of reliability, because it consumes a lot of memory, it gets to a point where it starts hanging. The fact that it needs a lot of memory is the only problem.
What do I think about the scalability of the solution?
I would not recommend this product for large automation projects because it gave us problems in terms of space and the speed at which it was executing. Once it starts running a large process with loops, it hangs. So, the process takes longer to complete.
When I deployed this solution, it was for a financial institution that had a six-person team. We automated three processes that have to do with reconciliation and they run them every week or two. The six people share roles and the bots assist them.
The reason that we deployed bots for them is that they are limited in number and needed assistance. At this point, the usage is not expected to grow.
How are customer service and support?
I asked some questions on the forum and I tried to contact the support in South Africa, but I couldn't get the assistance I required. These people were not coming through, so I just had to do my own research.
Ultimately, technical support never got back to me on any of the queries that I raised. As such, I cannot give them any plusses. In fact, I still have pending questions in the forum.
Which solution did I use previously and why did I switch?
How was the initial setup?
Setting up the server and the desktop versions are quite straightforward, both for the studio and for the control tower. As long as you have the required access, the setup process is straightforward. You just have to press the Next button on a series of screens.
We had a deployment on IIS and I built a web application on top of the bot. In total, the deployment took about a week because there were some functionalities that were not being picked up properly. Once those were completed, everything worked properly.
Post-setup, the deployment was a little bit difficult.
In terms of maintenance, one or two people are sufficient. You need a developer, and then somebody to support the infrastructure.
What about the implementation team?
I implemented this product alone. It was a bit difficult so I used the online forum and also tried to contact technical support in South Africa.
What's my experience with pricing, setup cost, and licensing?
My client is using RPA Express, which is available for them to use free of charge. Their parent company is in another country, so they're not paying for anything locally.
The Studio comes standard and is available at no charge but the Control Tower requires a license. The orchestration platform, where you manage your bots and users, is also available with a separate license.
As a developer, you cannot download the developer studio for free unless you are working for your clients.
Which other solutions did I evaluate?
My client had chosen and acquired WorkFusion in advance of hiring me. They were looking for a consultant to assist them with development and deployment.
What other advice do I have?
My advice for anybody who is implementing WorkFusion is to use it for small desktop processes, such as sending out a report via email, or small amounts of Excel reconciliation. However, once you have more than 1,000 or 2,000 data rows, it's going to be a bit hectic to consume that much data. That said, for small desktop applications, it's going to work.
When it comes to deploying to the server, it's going to be a bit complicated for enterprise solutions, especially because of the space. When they want to deploy it, they should have at least 16 GB of RAM and at least four CPU cores. Otherwise, anything below that will be too slow.
In summary, this is a good product for small desktop-level automation, but I do not recommend it for large-scale automation because it consumes too much memory and the processes run slowly or hang as a result. There is a lot of work to be done and considering the support does not get back to you, you might struggle with an issue for a long time. Also, there is very little content available online.
I would rate this solution a six out of ten.
Which deployment model are you using for this solution?
On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.