We performed a comparison between ActiveBatch by Redwood and Bizagi based on real PeerSpot user reviews.
Find out in this report how the two Process Automation solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."It has helped with scheduling complex jobs with simple scripts."
"The most valuable feature is its stability. We've only had very minor issues and generally they have happened because someone has applied a patch on a Windows operating system and it has caused some grief. We've actually been able to resolve those issues quite quickly with ActiveBatch. In all the time that I've had use of ActiveBatch, it hasn't failed completely once. Uptime is almost 100 percent."
"The REST API adapters and native integrations for integrating and orchestrating the software stack are very flexible."
"It can connect to a number of third-party/legacy systems."
"Error Handling is one of the best standout features of ActiveBatch."
"The Jobs Library has been a tremendous asset. For the most, that's what we use. There are some outliers, but we pretty much integrate those Jobs Library steps throughout the process, whether it's REST calls, FTP processes, or file copies and moves... That has helped us to build end-to-end workflows."
"We leverage the solution's native integrations regularly. We have to get files from a remote server outside the organization, and even send things outside the organization. We use a lot of its file manipulation and SFTP functionality for contacting remote servers."
"Since we are no longer waiting for an operator to see that a job is finished, we have changed our daily cycle from running in eight hours down to about five. We had a third shift-operator retire and that position was never refilled."
"The product enables the users to automate the processes and provides a good user experience."
"It can be useful as a tool to improve your communications and the control of your processes. For example, when you have to explain a process to seven or eight stakeholders who think differently as well as have different experiences in different functional departments, it is not easy. Sometimes you are using a lot of technical terms, and other times, you are dealing with management terminology. The visual representation helps you create a better alignment and understanding for different roles and stakeholders of your workforce."
"The solution's simulation capabilities are the most valuable aspects."
"Bizagi is a very useful tool because it does not require you to program. The user logic is very easy to understand even for people who are not engineers or developers."
"In Bizagi, all of the features are valuable."
"The most valuable feature is the organizational modeling capability."
"Very user friendly and a professional solution."
"The most beneficial features of Bizagi for our business processes are its seamless connectivity between process elements and its ability to automate tasks and perform simulations."
"They have some crucial design flaws within the console that still need to be worked out because it is not working exactly how we hoped to see it, e.g., just some minor things where when you hit the save button, then all of a sudden all your job's library items collapse. Then, in order to continue on with your testing, you have to open those back up. I have taken that to them, and they are like, "Yep. We know about it. We know we have some enhancements that need to be taken care of. We have more developers now." They are working towards taking the minor things that annoy us, resolving them, and getting them fixed."
"Between version 10 and version 12 there was a change. In version 10, they had each object in its own folder. But on the back end, they saw it at the root level. So when we moved over to version 12, everything was in the same area mixed together. It was incredibly difficult and we actually had to create our own folders and move those objects—like schedules, jobs, user accounts—and manually put those into folders, whereas the previous version already had it."
"There are some issues with this version and finding the jobs that it ran. If you're looking at 1,000 different jobs, it shows based on the execution time, not necessarily the run time. So, if there was a constraint waiting, you may be looking for it in the wrong time frame. Plus, with thousands of jobs showing up and the way it pages output jobs, sometimes you end up with multiple pages on the screen, then you have to go through to find the specific job you're looking for. On the opposite side, you can limit the daily activity screen to show only jobs that failed or jobs currently running, which will shrink that back down. However, we have operators who are looking at the whole nightly cycle to make sure everything is there and make sure nothing got blocked or was waiting. Sometimes, they have a hard time finding every item within the list."
"The UI could potentially offer a more refined and user-friendly experience, fostering smoother interactions and facilitating easier navigation for users engaging with the application."
"The thing I've noticed the most is the Help function. It's very difficult, at times, to find examples of how to do something. The Help function will explain what the tool does, but we're not a Windows shop at the data warehouse. Our data warehouse jobs actually run on Linux servers. Finding things for Linux-based solutions is not as easy as it is for Windows-based solutions. I would like to see more examples, and more non-Windows examples as well, in the Help."
"They could provide an easier installation guide or technical support to the organizations during the installation process."
"We have faced a couple of issues where we were supposed to log a defect with ActiveBatch. That said, the Active batch Vendor Support is very responsive and reliable."
"It does have a little bit of a learning curve because it is fairly complex. You have to learn how it does things. I don't know if it's any worse than any other tool would be, just because of the nature of what it does... the learning curve is the hardest part."
"I would like to see the automation process included in the next release."
"It needs some better notation functionality."
"Enhancing data generation methods for easier printing and refining the file attachment and user interface to optimize usability."
"Agriculture, Industry."
"In business process mapping, you have pools and dark pools. I don't see that Bizagi differentiates between a regular pool and a dark pool."
"Difficult to export in formats other than PDF."
"Framework approach, which extends to reusability in tools, like Pega, for deployment management could be improved."
"They should improve the migration process between major versions, from version 9 to 10, we had to redo our implementation."
ActiveBatch by Redwood is ranked 6th in Process Automation with 35 reviews while Bizagi is ranked 7th in Process Automation with 78 reviews. ActiveBatch by Redwood is rated 9.2, while Bizagi is rated 8.4. The top reviewer of ActiveBatch by Redwood writes "Flexible, easy to use, and offers good automation". On the other hand, the top reviewer of Bizagi writes "A flexible, customizable solution that reduced time to market, but the UI and customer support could be better". ActiveBatch by Redwood is most compared with Control-M, AutoSys Workload Automation, Tidal by Redwood, Redwood RunMyJobs and VisualCron, whereas Bizagi is most compared with Camunda, Visio, Bonita, Microsoft Power Apps and ARIS BPA. See our ActiveBatch by Redwood vs. Bizagi report.
See our list of best Process Automation vendors.
We monitor all Process Automation reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.