Senior Operations Administrator at Illinois Mutual Life Insurance Company
Real User
2020-04-02T07:00:00Z
Apr 2, 2020
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.
Data Warehouse Operations Analyst at a leisure / travel company with 1,001-5,000 employees
Real User
2020-03-31T06:37:00Z
Mar 31, 2020
One of the valuable features is the ability to trigger workflows, one after another, based on success, without having to worry about overlapping workflows. The ability to integrate our BI, analytics, and our data quality jobs is also valuable
Senior IT Architect at a pharma/biotech company with 5,001-10,000 employees
Real User
2020-03-31T06:37:00Z
Mar 31, 2020
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.
Client Service Manager/Programmer at a tech vendor with 51-200 employees
Real User
2020-03-29T08:26:00Z
Mar 29, 2020
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.
Supervisor IT Operations at a insurance company with 501-1,000 employees
Real User
2020-03-29T08:26:00Z
Mar 29, 2020
The nice thing about ActiveBatch is once we have created a specific job that can be easily be replicated to another job, then minimal changes will have to be made. This makes things nice. Reduction of coding is substantial in a lot of cases. The replication of one job to another is just doing a few minor tweaks and rolling it into production. This decreases our development costs substantially.
ActiveBatch by Redwood automates and manages batch processes, data integration tasks, and workflow scheduling. It's used for file transfers, data processing, server monitoring, and report generation, supporting both on-prem and cloud environments.
Organizations implement ActiveBatch by Redwood to automate complex job scheduling and data workflows, integrating seamlessly with FTP, SQL, PowerShell, and other systems. With features like real-time monitoring, error handling, and centralized...
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.
One of the valuable features is the ability to trigger workflows, one after another, based on success, without having to worry about overlapping workflows. The ability to integrate our BI, analytics, and our data quality jobs is also valuable
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 nice thing about ActiveBatch is once we have created a specific job that can be easily be replicated to another job, then minimal changes will have to be made. This makes things nice. Reduction of coding is substantial in a lot of cases. The replication of one job to another is just doing a few minor tweaks and rolling it into production. This decreases our development costs substantially.