The most valuable feature is the FTP file transfer.

The only other tool I could compare it to currently is Control-M. I have worked with other automation tools in the past but not as much as Rocket Zena. In terms of comparison with Control-M, its user interface is way better than Control-M. You can click Ctrl-G and bring a diagram view. You're able to view in a diagram format. The view that it provides is easy, and you can move to the left, up, or down. You can double-click on a certain process. It'll drill into that process and all of its underlying components. You can double-click on an arrow or a component, and it'll bring up a screen that'll have all the variables that are assigned to that particular piece, as well as the values at run time. So, the diagram feature of it, at least for me, is pretty valuable.

In the latest upgrade, Zena added a web-based client. The more I use it, the more I like it. It's an excellent interface. They do a good job of steadily improving the solution to make it more useful. 

The whiteboard is handy when setting up processes and scheduling tasks, especially large ones. It helps you visualize the processes you're building so you can see what you're doing a lot easier than if you were just using a text-based system. It's a critical feature when you're building or troubleshooting jobs. You can see what you're doing and take out or add steps as needed. 

I like the whole product, but specifically, I like the licensing. It's very easy to acquire a license for this product.

It's very easy to use. It's much easier to use than other products like ESP, for example. Technical support and the price are also very good.

Rocket Zena is easy to use.

I have used other tools with similar capabilities; it's the ease of use.

It appears to be nearly identical to the other products.

Its FTP feature is very good, as is scheduling any process or task with the Zena client. I have found it to be very helpful. If a task fails, it gives you a prompt. Most of the time, I use it to create RPA tasks and schedule them. Whenever a task fails or is completed, I get a notification.

It operates in layman's language. It's very easy and convenient for users who are very new to technology.

The graphical user interface is very usable and most of the features and functions are displayed on the screen. You just have to click and see the options and you get to know what they are used for. There is a very good help option for whatever you need to know about the tool. With it, you will get to know about the product thoroughly: how to configure it and how to use it from start to end.

The solution is very informative when using Zena Client and Zena workstation. There is very good communication between them. The results of tasks can be added as an attachment to an email. If I am not in front of my system, I can get a log and output where I can see if it was completed or, if there was an error, what the error is, and where it failed.

From a Linux configuration point of view, Rocket Zena is straightforward. It's fairly easy to set up the server and agents once you know how to do it.

We use Rocket Zena’s containerized deployment with Docker (automated with Kubernetes). It is great, but there is a learning curve. We have a single server on the OpenShift cluster, on which we have a Rocket Zena agent installed. We don't have rocket Zena inside the containers or on the nodes themselves, but on the centralized server. That server will run jobs to all the other Docker nodes from that one single point of view. It is better when using Rocket Zena because we don't really have to have Rocket Zena on so many servers, which can lead to small configuration problems and the need to maintain Rocket Zena in more places.

Containerized deployment with Docker saved us time. If you want to troubleshoot an issue, you can redeploy the same container. If you find infrastructure as a code and you have everything re-deployable as a container, when there is an issue or you need to roll back, you can easily redeploy the container. You don't have to reinstall it.

We use Rocket Zena to manage complex operational workflows, end-to-end, across multiple technology stacks. We have a standard, single place where we can have automated workflows. This standardization across different platforms makes it easy to both write new workflows and troubleshoot what is and is not working. Considering that it can be a big mess and very hard to understand what should be done, this simplification of processes is important to our organization.

Rocket Zena's cross-platform job scheduling helped save programming time by automating repetitive tasks. It also helped improve accuracy when running jobs.

Since everything is done by Rocket Zena, and we do not have to manually schedule some jobs on the operating system level, it freed up our engineers to focus on more value-added work. We have seen a 10% increase in time savings.

Rocket Zena helped us consolidate our processes, solutions, and tools. It is important to us and that's why we use it across all our platforms.

I have found the scheduling feature the most valuable. I can map dependencies by using ASG-Zena. It gives a nice, quick visualization as to where things are.