We performed a comparison between Fortra's JAMS and VisualCron based on real PeerSpot user reviews.
Find out in this report how the two Workload Automation solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."The scheduling and execution of jobs are the most valuable features. The scheduling is important because if there is a task we want to execute at 4:00 AM, there's no way we will have someone who can manually run the job. In addition, we execute 100 to 200 jobs per day, and manual intervention is not an option."
"The overall product is fantastic. I love it. It has been a fantastic, solid product. If I have one tiny bit of a problem with it, the support team gets in touch with me right away. I don't know if I've had another service that has been as fantastic as the JAMS support team."
"Being able to create a series of chained jobs, which are basically linked jobs is valuable."
"The feature or capability to import a job is most valuable. We can import an existing job from different platforms, and all the configurations get migrated as well without modifying the code, job schedule, etc."
"It makes everything that we want to do so much easier. We have had a number of instances in the past where we have had developers who have been working on a project, and even though we have had JAMS for all these years, they will create some SQL Server Agent job, or something like that, to run a task. When it is in code review and development is complete, the question always comes around, "Can JAMS do this?" The answer has always been, "Yes." Pretty much anything we have ever developed could be run by JAMS."
"The most valuable feature for us is that it's DR-ready. With respect to disaster recovery, it has the built-in capability for failover to our DR site. If all of the required ports are open, it can be done seamlessly."
"The most valuable feature is the easily accessible data in the database because we run a lot of SQL scripting against the database."
"I like how you can add new execution methods on the fly. It isn't overly complex to add Python script support to an execution method in the JAMS system. The scheduling is excellent. You can schedule a maintenance window and take that resource unit out of everything. It halts all of the jobs."
"It helped us reduce manual steps."
"The ability to clone jobs to shorten the time it takes to implement a process has been invaluable, but its flexibility also gives us the ability to create a job that can handle a multifaceted process with a complex workflow."
"The most valuable feature of VisualCron is its ability to schedule interactive jobs so that you can have interdependencies within the job and interdependencies of a job on another job, and so on."
"It has improved our organization with more automation within the business departments and less administration and development in the IT department. Usually, as the IT department, we are the bottleneck for many requirements within the business. With this tool, the business departments are able to perform many task themselves."
"What I like about VisualCron is that like its name, it's a very visual tool. In my previous company, there were a lot of scripts for all kinds of services, and through VisualCron, you get to group all flows and get a nice visual overview. VisualCron also has an alerting feature, so you receive alerts from it. VisualCron makes everything clearer and easier to maintain. Every other solution that I was looking for almost always needed a programmer, but with VisualCron, you can do what you need to do without programming skills, so this is another valuable feature of the tool."
"What I found most beneficial from VisualCron is that you can directly connect it with different databases, user accounts, and credentials. You can run queries from one machine to another using the credentials, unlike PowerShell, that's run by the machine itself. With VisualCron, you can directly ask other machines and run requests through user credentials. Suppose you have an AWS or Azure environment. In that case, you can maintain the connection between on-premises and cloud-based machines, which is the type of setup in the organization I'm working for. You can directly call some of the services via VisualCron on your local on-premises machine, and I found that an excellent feature of the tool."
"'ve only had a few cases where I've had to request support in the past 12 years of use, but the support response time and resolution were was extremely quick."
"We don't have to do any coding. We just plug and play and it works."
"The tabs in the JAMS file transfer could be clearer. It would help us demonstrate to our client that JAMS not only automates jobs but also does fast transfers, and it's an alternative that supports and filters different kinds of platforms. Filtering file transfers will be highly beneficial to them."
"Sometimes the UI is not the most responsive I've ever used. But because it does its job, I don't complain."
"When looking at a folder in JAMS with many jobs, it would be good to have better information in the list display of what's inside those jobs. We get some information, but other important details are missing."
"As an admin, I would like to have a web-based GUI instead of a client application that we have to install on our PCs."
"With no programming experience, I find JAMS code-driven automation challenging due to the required PowerShell scripting."
"The documentation is not super... It's not as quick and slick as I'd like it to be."
"The client is horrible. Every time JAMS puts out a survey on what they can improve, I always say, "The client: When you are setting up jobs, it is quite horrible." The response has been, "Well, we are just using the Windows foundation," and I am like, "Why isn't it only your product?" We can get around it now that we know its quirks, but it is not the most user-friendly of tools out there. The UI is completely unintuitive. We had to go and open up a support ticket with JAMS just to get something back. It is not user-friendly at all."
"JAMS lacks source control features. Our previous solution had job control language, but JAMS doesn't. When migrating between versions, JAMS doesn't migrate all the data, like job change history, etc. Also, the scheduler doesn't have a way to make jobs invisible, so you can temporarily turn a job off if you decide not to run it today."
"VisualCron is software, and you will experience performance degradation when you scale up. VisualCron takes too much memory or CPU power. We have to increase the hardware resources of a specific server or system."
"There are some conditions in the mail trigger, but you can only use them as an "AND" condition, not as an "OR" condition. This is an improvement that could be useful. For example, some people put "invoice" in the subject and others put "invoice" in the body. If I want to make a trigger for everybody whose sending invoices, I have to make two jobs for this now."
"The error timeout and info could be better. When making web request calls, it will time out sometimes and we won't get any useful info out of the error response."
"VisualCron seems to operate like an efficient machine when it comes to improvements and enhancements and new features. I always appreciate the quick response I get when bringing up an issue or coming up with suggestions. I've mentioned before that it would be great to see a move away from SQLCE and XML configuration files."
"An area for improvement in VisualCron is its cluttered interface. It isn't always easy to find all functionalities, so what VisualCron needs is a user interface expert who can improve the interface. There's a learning curve in terms of finding what you need from the interface of VisualCron. The technical support for VisualCron also needs improvement in terms of response time. Currently, there's no live support or hotline you can call to get quick answers, so this is what I'd like to see in the next version of VisualCron. A less cluttered and more streamlined interface, where you don't need to hunt for some of the features, is also what I'd like to see in the next VisualCron update."
"VisualCron's command console is a little bit difficult to understand and needs to improve."
"The only problem I face when I use the tool is that it doesn't contain much documentation or it doesn't have many video tutorials on its features."
"I want to improve the UI in VisualCron, as it's not as user-friendly, particularly when setting up the task scheduler. If you're familiar with the tool, then no problem, but if not, you'll have a problem typing text because sometimes, the cursor points to other places, so there's an issue with text box alignment in VisualCron. That was painful for me when I was just a VisualCron novice, but when you become used to it, there won't be a problem."
Fortra's JAMS is ranked 5th in Workload Automation with 27 reviews while VisualCron is ranked 14th in Workload Automation with 10 reviews. Fortra's JAMS is rated 9.0, while VisualCron is rated 9.0. The top reviewer of Fortra's JAMS writes "We can scale up our organization's scheduling and automation without having to add staff to the department". On the other hand, the top reviewer of VisualCron writes "It's user-friendly, and I didn't need long to understand the process". Fortra's JAMS is most compared with Control-M, Tidal by Redwood, AutoSys Workload Automation and Redwood RunMyJobs, whereas VisualCron is most compared with Microsoft Power Automate, Control-M, AutoSys Workload Automation and ActiveBatch by Redwood. See our Fortra's JAMS vs. VisualCron report.
See our list of best Workload Automation vendors.
We monitor all Workload 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.
