System administrator at a wholesaler/distributor with 1,001-5,000 employees
Real User
Dec 25, 2022
In the web interface, it stacks the tasks across the top, and they accumulate until you close or clean those out. That seems a little cumbersome. You must right-click and close all tabs constantly to keep the console clean and manage your views. Some of the documentation in the knowledge base can be hard to navigate. You have to search through lots of products to find the correct version of your product. Sometimes when you have that, you still get documentation or knowledge-based information for something unrelated to what you're using.
Sr. IT Product Manager at a healthcare company with 10,001+ employees
Real User
Nov 3, 2022
There is a limit of 6,000 components in a particular process. The processes that we've developed have a lot of components, but there's a limit, which is fine, but it would be great if it just didn't have that limitation. I understand the system limitation and so forth, but it would be great to not have this limitation. Another one that is probably a little bit bigger for me is that when there is an issue or there's an error, it writes on a different screen. I have to find the actual process name and go to a different screen to view the alert that got generated. On that screen, everyone's processes, not just the processes of the folks in my department, are thrown. It takes me a while to find the actual error so that I could go in there and look at the alert. It could be because of the way it was set up, but at least for me, it isn't too intuitive. For processes, ASG-Zena has four bubbles. It's green if a process is running and nothing has failed. It's yellow if something inside a process has failed, but the rest of the process is running. It's red if a process has failed, and it's blue if a process is complete. If there's something yellow, you can dig into a process and eventually find the error. For alerts, there's another screen, and this alert screen has everyone's alerts. Generally, I only have a view of the components that are owned by my department, but when I go to the alerts screen, the alerts from everyone in the company are there. Because I am not on the admin side, I don't know if this is something that wasn't set up properly on the admin side or if it is something that could have been improved in the tool. They can improve the UI loading time, at least in dev. It takes a long time. It could be because it has got so many components. It literally takes two or three minutes before it loads and you start using it. They can make some updates to get it up and running faster.
The main area for improvement with this product is around its usability. It is currently quite a complex tool to use, and doesn't offer a single point of system information.
Enterprise Business Intelligence Administration and Management at a government with 11-50 employees
Real User
Oct 4, 2020
The scheduling mapping is a little disjointed. There is no wizard-type approach. There are a lot of different things that you have to do in completely different areas. They could probably add the functionality for creating all components of a mapping or an OPA schedule. The component creation could be done collectively rather than through individual components.
Rocket Zena offers scheduling and dependency mapping, intuitive interface, and containerized deployment. It simplifies workflow automation, enhancing efficiency across platforms.Rocket Zena's strengths lie in its scheduling capabilities, graphical interface, and efficient deployment. It supports users in task management with cross-platform scheduling, streamlining repetitive tasks through automation. The web-based client facilitates process visualization and workflow management, while the...
In the web interface, it stacks the tasks across the top, and they accumulate until you close or clean those out. That seems a little cumbersome. You must right-click and close all tabs constantly to keep the console clean and manage your views. Some of the documentation in the knowledge base can be hard to navigate. You have to search through lots of products to find the correct version of your product. Sometimes when you have that, you still get documentation or knowledge-based information for something unrelated to what you're using.
There is a limit of 6,000 components in a particular process. The processes that we've developed have a lot of components, but there's a limit, which is fine, but it would be great if it just didn't have that limitation. I understand the system limitation and so forth, but it would be great to not have this limitation. Another one that is probably a little bit bigger for me is that when there is an issue or there's an error, it writes on a different screen. I have to find the actual process name and go to a different screen to view the alert that got generated. On that screen, everyone's processes, not just the processes of the folks in my department, are thrown. It takes me a while to find the actual error so that I could go in there and look at the alert. It could be because of the way it was set up, but at least for me, it isn't too intuitive. For processes, ASG-Zena has four bubbles. It's green if a process is running and nothing has failed. It's yellow if something inside a process has failed, but the rest of the process is running. It's red if a process has failed, and it's blue if a process is complete. If there's something yellow, you can dig into a process and eventually find the error. For alerts, there's another screen, and this alert screen has everyone's alerts. Generally, I only have a view of the components that are owned by my department, but when I go to the alerts screen, the alerts from everyone in the company are there. Because I am not on the admin side, I don't know if this is something that wasn't set up properly on the admin side or if it is something that could have been improved in the tool. They can improve the UI loading time, at least in dev. It takes a long time. It could be because it has got so many components. It literally takes two or three minutes before it loads and you start using it. They can make some updates to get it up and running faster.
The main area for improvement with this product is around its usability. It is currently quite a complex tool to use, and doesn't offer a single point of system information.
The scheduling mapping is a little disjointed. There is no wizard-type approach. There are a lot of different things that you have to do in completely different areas. They could probably add the functionality for creating all components of a mapping or an OPA schedule. The component creation could be done collectively rather than through individual components.