We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
"ActiveBatch can automate predictable, repeatable processes very well. There is no real trick to what ActiveBatch does. ActiveBatch does exactly what you would expect a scheduling piece of software to do. It does it in a timely manner and does it with very little outside interference and fanfare. It runs when it is supposed to, and I don't have to jump through a bunch of hoops to double check it."
"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."
"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."
"As far as centralization goes it's nice because we can see all these processes that are tied to this larger process. The commissions, FTP processing, the reporting, the file moves to the business users — all that is right there. It's very easy to read. It's easy to tie it together, visually, and see where each of these steps fits into the bigger picture."
"We use the main job-scheduling feature. It's the only thing we use in the tool. That's the reason we are using the tool: to reduce costs by replacing manual tasks with automated tasks and to perform regular, repetitive tasks in a more reliable way."
"What ActiveBatch allows you to do is develop a more efficient process. It gave me visibility into all my jobs so I could choose which jobs to run in parallel. This is much easier than when I have to try to do it through cron for Windows XP, where you really can't do things in parallel and know what is going on."
"One of the most valuable features is the job templates. If we need to create an FTP job, we just drag over the FTP template and fill out the requirements using the variables that ActiveBatch uses. And that makes it reusable. We can create a job once but use it for many different clients."
"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."
"The most valuable feature is the situational layer cake."
"The ability to define processes, build reports, and get insights or analytics on data is most valuable. It is a powerful platform."
"The solution is operating well overall."
"The most valuable feature is flexibility, as we can configure it to best suit our requirements."
"The stability has been good. We haven't had any issues."
"It is quite configurable, which is the most exciting feature. We can easily configure it as per our needs."
"The workflow designing and integration are the most valuable features. Also, the UI design was pretty easy."
"The solution offers excellent workflows."
"A nice thing to have would be the ability to comfortably pass variables from one job to another. That was one of the things that I found difficult."
"The reporting needs improvement. There is a real need for the ability to generate audit reports on the fly. It needs to be a lot easier than what I can do right now. This is a major item for me."
"One thing I've noticed is that navigation can be difficult unless you are familiar with the structure that we have in place. If someone else had to look at our ActiveBatch console and find a job, they might not know where to find it."
"I can't get the cleaning up of logs to work consistently. Right now, we are not setup correctly, and maybe it is something that I have not effectively communicated to them."
"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."
"There is this back and forth, where ActiveBatch says, "Your Oracle people should be dealing with this," and Oracle people say, "No, we don't know anything about ActiveBatch." Then, it all falls back on me as to what happens. Nobody is taking responsibility. This is the biggest failing for ActiveBatch."
"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."
"The interface is not that user-friendly and is a little tough to navigate."
"The previous versions had good training documents but the updated versions need to improve the documentation."
"They are currently spending some time on improving the product with respect to machine learning, especially related to robotic automation. They probably could be a little more adept on that area would help."
"Compared to other BPM products, the interface is somewhat complex, so the usability could be improved."
"The way the IDE works with the chatbox and the taxonomy imports could be a little smoother."
"The solution would benefit from more integration capabilities."
"It needs more integration with other platforms."
"It should have integration with non-relational databases. A lot of databases are non-relational, and as a company, we are planning to move to NoSQL or open-source databases. It would be good if we are able to install and use Pega on a NoSQL database. They can also try to tailor or organize the company a bit differently and go more towards the microservice concept. I would like Pega to develop machine learning and intelligent AI algorithms. They have a good foundation in terms of the model and the stuff that we are using for some customers, and it will be good to onboard as many machine learning algorithms as possible."
"It's called a local platform but on the other hand, it needs a lot of experience. It's not all that easy to click and plug and play. If you really want to use all the features out of this platform, you definitely need a lot of experience and a lot of training to get there."
"I don't think we've ever had a problem with the pricing or licensing. Even the maintenance fees are very much in line. They are not excessive. I think for the support that you get, you get a good value for your money. It's the best value on the market."
"ActiveBatch is currently redesigning themselves. In the past, they were a low cost solution for automation. They had a nice tool that was very inexpensive. With their five-year plan, they will be more enhancement-driven, so they're trying to improve their software, customer service, and the way that their customers get information from them. In doing that, they're raising the price of their base system. They changed from one pricing model to another, which has caused some friction between ActiveBatch and us. We're working through that right now with them. That's one of the reasons why we're why we were evaluating other software packages."
"The pricing was fair. There are additional costs for the plugins. We have the standard licensing fees for different pieces, then we have the plugins which were add-ons. However, we expected that."
"It allows for lower operational overhead."
"The price was fairly in line with other automation tools. I don't think it's exorbitantly expensive, relatively speaking."
"If you compare ActiveBatch licensing to Control-M, you're looking at $50,000 as opposed to millions."
"Currently, we are paying approximately $7,000 yearly, which includes support."
"It's a user-based license where, as you scale the numbers of users, the price increases."
"The solution could be less expensive according to my customers. However, I think the price of the solution is fair."
"The pricing is pretty good, compared to other similar products."
"The price is a bit expensive."
"We mostly have a yearly license."
"The price of this solution, including installation and configuration, is comparable to competing vendors."
"It is cost-effective for medium enterprises. It is cheaper than ServiceNow."
Orchestrate your entire tech stack with ActiveBatch Workload Automation and Enterprise Job Scheduling. Build and centralize end-to-end workflows under a single pane of glass. Seamlessly manage systems, applications, and services across your organization. Eliminate manual workflows with ActiveBatch so you can focus on higher value activities that drive your company forward.
Limitless Endpoints: Use native integrations and our low-code REST API adapter to connect to any server, any application, any service.
Proactive Support Model: 24/7- US-based support and predictive diagnostics.
Low Code Drag-and-Drop GUI: Easily build reliable, customizable, end-to-end processes.
Pega BPM helps you simplify and automate your operations so that you can reduce costs and improve business agility. Pega's unique Build For Change technology delivers repeatable solutions that can be efficiently reused and tailored to meet the requirements of diverse customers, product lines, channels, and geographies.
ActiveBatch Workload Automation is ranked 6th in Process Automation with 12 reviews while Pega BPM is ranked 3rd in Process Automation with 16 reviews. ActiveBatch Workload Automation is rated 9.2, while Pega BPM is rated 8.2. The top reviewer of ActiveBatch Workload Automation writes "Everything runs automatically from start to finish; we don't have to worry about somebody clicking the wrong button". On the other hand, the top reviewer of Pega BPM writes "Good case management and BPM workflow with easy cloud implementation". ActiveBatch Workload Automation is most compared with Control-M, AutoSys Workload Automation, Automic Workload Automation, Tidal Automation and VisualCron, whereas Pega BPM is most compared with Camunda Platform, ServiceNow, Appian, IBM BPM and Microsoft PowerApps. See our ActiveBatch Workload Automation vs. Pega BPM 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.