Automic Automation Pros and Cons

The UI of automic is more attractive and effective to use for valuable productivity. The way of creating the flows are easy and will prove our talent. Review collected by and hosted on G2.com.

The up-gradation of automic is effecting the slowness of the platform which makes us irritate regarding performance. There are no proper ways of calling API which is not properly established within the automic which is one negative point found from the CA automic workload automation. Review collected by and hosted on G2.com.

Automic is an Information Technology Process Automation tool. Which is completely different than the RPA. It is advantageous as it does not depend on the UI for automation purpose. Instead it uses RFC calls for data extraction and processing. Review collected by and hosted on G2.com.

It can not be integrated just like that with any application and requires the web service calls to be available for the same. The Thick Client looked like a legacy application, but now we have Web interface for the same. Should be interesting to work with. Review collected by and hosted on G2.com.

Automic has always been known for their industry-leading and innovative capabilities in scheduling applications across enterprises. Automic continues this tradition.

It enables connectivity to any application, databases, operating system and capable to support the growing business. It is capable to integrate all business applications effectively. Compared to other scheduling tools available its immense feature such as forecasting, reporting, error detection and correction, audit and Load balancing make it more powerful and reliable. Review collected by and hosted on G2.com.

The latest version brought some key feature however still those are still not user friendly like adding and creating new dashboard, jobs views and report view are still not user friendly and easy readable. Review collected by and hosted on G2.com.

First, our configuration allows for the application to be in an active/passive state so that immediately when the active instance fails the passive instance takes over. We have over a thousand unique jobs configured to run. As with the CA7 product, the jobs can be configured to be scheduled based upon time/date parameters similar to cron or triggered based upon statuses of other jobs (or a mixture of the two). WCC is the UI to configure jobs; there is a lot of functionality to assist the creation and modification of jobs. Review collected by and hosted on G2.com.

On occasion, a job does not kill completely through the entire system(s). Assume access is available, it just takes killing the job on the remote system- this is rare and happens usually when the job is in a very bad state. Review collected by and hosted on G2.com.

- Easy view of all jobs at once in a workflow - with a option to zoom in and zoom out.

-Schduling jobs and workflows.

-- Setting up external dependencies

--Transport case to move jobs across environments Review collected by and hosted on G2.com.

-- External dependencies handling to export jobs sometime tricky.

--CA support time for P1 is 4 hours- however it varies with support level.

- Review collected by and hosted on G2.com.