I'm quite impressed with the event driven capabilities of ActiveBatch Workload Automation. We are able to automate processes depending on events such as files dropped or updated in a database so that we can take action instantly, without manual intervention. The extensive library of integrated job steps is another major plus. As an example, the integration with Salesforce, PowerShell, or SQL operations is a plug-and-play, which saves tremendous amounts of development time. Review collected by and hosted on G2.com.

The biggest complaint that I have with ActiveBatch is the logging verbosity of very large workflows. Although detailed, it may take time to go through long logs to identify a small problem. Also, sometimes the re-engineering of existing scripts or complicated legacy jobs in order to take full advantage of its advanced capabilities takes more re-engineering than expected. Review collected by and hosted on G2.com.

The best part of ActiveBatch that I like is the way it can perform repetitive tasks without my interference. The frequency of use is high as I rely on it to carry out my daily activities. The features count facilitates the variety of jobs on platforms. I have linked it to our ERP and database systems, and this has simplified the processes. It enables me to remain productive since I do not have to be vigilant of tasks always. Review collected by and hosted on G2.com.

The problem is that certain settings may be initially confusing. Despite having a powerful amount of features, it is time sensitive to comprehend them. This impacts on my work when I have to create new workflows within a short time. There are times when additional steps are needed to be integrated with some systems. Review collected by and hosted on G2.com.

The greatest benefit that can be seen to me is that it places background processes in a structured and orderly manner. I use it to handle activities between the internet and the databases and this makes operations uniform. I can use its features to determine dependencies and prevent job conflicts. This has enhanced my work planning as well as decreased the necessity to engage tasks manually throughout the day. Review collected by and hosted on G2.com.

A negative effect I have observed is that ActiveBatch Workload may be initially overwhelming due to the volume of features it possesses. It is a process to realize the ultimate working of all. Certainly, establishing new working processes demands additional effort in others, which annoys my progress. Review collected by and hosted on G2.com.

ActiveBatch is very effective when it comes to managing complex cross platform workflows. We apply it to automate our whole nightly ETL operation, to transfer data between systems consistently. The built-in Job Step Library is amazing; it offers pre-built integrations with different applications and technologies, such as the ability to connect simply to our cloud storage or database systems. Review collected by and hosted on G2.com.

Though quite powerful, the interface of ActiveBatch may be slightly outdated and less user-friendly as compared to newer solutions, which will need some adaptation. Initial learning curve, particularly in advanced scripting and complex workflow design is quite steep. Review collected by and hosted on G2.com.

The best aspect of ActiveBatch is that it allows our important IT processes to run with a high level of reliability without the close monitoring. E.g. database backups, file transfers, report generations occur automatically in the correct order. I especially like the in built notifications which inform the team about the completion of a task or the need to attend to something. Review collected by and hosted on G2.com.

The only disadvantage I have encountered using it is that set up of long chains of jobs with more than one dependency can be time consuming. The definition of each step should be thoroughly established to make sure tasks are activated in the right order, and this can be slow at times when introducing new processes. Review collected by and hosted on G2.com.

The most significant benefit to me is the ability to be in control of the routine operational jobs. I depend on it in managing data flows within our online store as it helps me send out such tasks as order files generation and periodic database maintenance scripts. The number of times I use it is very high because they are processes that are performed daily. The site has some robust features that ensure that I can specify job requirements and time constraints. Review collected by and hosted on G2.com.

The only disadvantage that I have observed in the use of ActiveBatch Workload Automation is that sometimes it may be inconvenient to maintain older workflows. Our company created numerous job sequences in the first implementation and when it comes to reviewing them after several months, it is important to carefully check them as there are several steps intertwined. Review collected by and hosted on G2.com.

The outstanding aspect is that it enhances accountability of IT team. Each of the planned procedures has a definite owner and a recorded history, which lessens the confusion between shifts changes. The features allow the role based access and approval actions prior to the execution of key jobs. It has moulded our internal discipline because we use it so often. It is also linked to ServiceNow to update the tickets, making the operational communication well organized and trackable. Review collected by and hosted on G2.com.

One of the challenges was the effort required during implementation. It required time to harmonize the various departments in terms of naming conventions and job ownership. It has a powerful range of features, although it occasionally introduces additional configuration procedures. With the frequent use we get the slightest setup errors to show up. This added more pressure to our IT staff until the clear definition of standards during peak accounting cycles. Review collected by and hosted on G2.com.

One of the things that I find interesting about ActiveBatch is the ability to hold processes to be predictable and accountable. Each of the scheduled jobs indicates ownership, estimation due date, and the status of completion thus easy to do follow ups. Since the team utilizes it on a daily basis when running scripts, generating reports, and performing maintenance, it has enhanced reliability, lowered the possibility of missing actions, and has enabled us to organize projects without having to monitor all the time whether the jobs are being performed correctly. Review collected by and hosted on G2.com.

In my experience, ActiveBatch may be enhanced in graphically presenting overlapping workflows. Under the condition that several sequences are interdependent or are performed simultaneously, it may be hard to see the entire picture. Since the platform is extensively used in day to day operations, this occasionally increases the coordination efforts to make sure that everything is operating properly. Review collected by and hosted on G2.com.

The outstanding feature is the ability to coordinate and order several processes among systems. I apply it in all my daily activities and automate them to make sure that there is no daily monitoring of dependencies and that deadlines are met. I especially appreciate the fact that it minimizes possibilities of errors and makes operations predictable, which makes me calm in the midst of heavy project times. Review collected by and hosted on G2.com.

The thing that I do not like is the fact that a workflow with nonstandard tasks might take extra steps to be configured. This will reduce the speed at which jobs are implemented in case of a series of projects to be automated. This imposes little planning and additional checks in my role to make sure that all processes will run without any problems, which costs me a little more time. Review collected by and hosted on G2.com.

The greatest benefit to me is the ability to specify the tasks by when and how to execute them. As an employee in the online retail infrastructure, I have been using it daily to allocate priorities as well as determine the conditions of execution of the financial and inventory jobs. The variety of features associated with events based triggers ensures that its workflows remain predictable. Due to high frequency of use we rely on such structured rules in order to evade conflicts in operations and unnecessary overtime. Review collected by and hosted on G2.com.

Among the negative effects I have had is that an advanced workflow logic might be challenging to document in a clear manner to non-technical stakeholders. Although the feature count is solid, it is observed that in some cases, the process of explicating job requirements to finance or operations departments may need additional meetings. Since we have been using it a lot, any confusion regarding the task ownership can generate internal friction and slow down the process of decision making. Review collected by and hosted on G2.com.