Redwood RunMyJobs Reviews

The primary use case of this tool was to arrange and automate our workflow processes. It has been of great advantage to us to enhance operational efficiency and productivity within our organization. 

This tool has been a good companion to rely on when it comes to automation. It automates the routine tasks and also saves a lot of time and resources. By automating the tasks, the risk of errors has been reduced over time. The software helps us to design and manage very complex workflows with ease. It also ensures that tasks are completed on time without any errors.

Redwood RunMyJobs has improved the overall performance of my organization. 

By automating the job processes it has saved us a lot of time and resources. It has also gradually reduced the human errors. The tools have totally eliminated the manual intervention processes. 

The security features that Redwood offers are a standout feature of the tool. It ensures that the data that are under execution are safe and confidential. It does not allow any data leakages. 

Integration with various other systems and applications is smooth with Redwood. 

The reporting features provide insight into the workflow performance and help us to identify the errors and rectify them. 

Redwood RunMyJobs is highly reliable.

Redwood RunMyJobs has the ability to automate a wide range of tasks and workflows with an ease that is remarkable. This feature has helped us to save a lot of time, reduce human errors, and ensure consistency in the execution of processes. 

It has a great user interface which is really simple to understand and to operate. The design of the tool simplifies the workflow creation and management. 

Redwood RunMyJobs has a very robust security system. It ensures the data are safe during the execution processes.

Enhancing the user interface would make it more appealing and accessible to a wide range of users. 

Providing clear and more transparent costing structures would benefit a lot of new users. Some users find the cost to be higher so offering more flexible pricing options could be beneficial. 

Providing training materials and tutorials would be helpful to new users. 

Expanding the reporting features could be valuable as it is one of the best features that Redwood RunMyJobs provides. Mobile accessibility can be improved.

I have been using this tool for more than seven months now and it has been a game-changer for me.

It is a very stable and reliable tool.

Redwood RunMyJobs is highly scalable and is a great tool when it comes to automation.

I did use a different solution before switching to Redwood RunMyJobs. The previous tool was not compatible enough with the business requirements so I had to switch to Redwood. This tool had everything I was looking for in an automation tool.

The initial setup was easy and straightforward.

The primary use case associated with Redwood RunMyJobs is to automate the job scheduling processes. 

I have used it to handle critical tasks. It has been of great use to me in handling the job processes with ease. The platform has been very reliable and efficient in automating critical workflows. 

It can be used to automate the daily data backup of the organization. It gives a clear insight into the performance of the organization. It also triggers notification if any critical tasks fail to execute. Redwood RunMyJobs has saved a significant amount of time and effort by automating my job scheduling processes. I would highly recommend it to anyone who is looking for a reliable workload automation solution. 

Error handling and integration with any other systems are some of the remarkable features of the software. It is easy to set up if the user has some technical knowledge about it. It is easy-to-use software and it improves overall productivity.

Redwood has helped us to automate many of the manual tasks and has saved a significant amount of time. This has allowed us to focus on more important tasks and has improved overall productivity. 

The accuracy and quality of the work have improved by automating the business processes. Human errors and the time taken to complete the tasks have significantly reduced over time. 

The platform makes sure that more work gets done in less amount of time. The software has helped us to reduce costs, avoid penalties, and improve visibility by automating the business process. 

It gives real-time status updates of the tasks that are being executed and it also tracks the progress of the tasks. 

Error detection is an excellent factor of the software.

Error handling and the recovery feature ensure that my job processes are not stopped if any error occurs. This has improved the reliability of my work.

The automated job scheduling allows us to perform the job processes with ease. It has saved a lot of time and effort by automating the business process. 

There is no necessity to do the tasks manually. Redwood has significantly improved the efficiency and accuracy of the tasks by reducing human errors. 

Integration with various other systems has been truly easy with Redwood. It handles the tasks and adapts to the changing demands. 

The platform also keeps the record and status of the tasks that are being executed. It keeps a detailed record of who initiated the task, when the execution occurred and what was the outcome of the task. 

Overall I have found Redwood RunMyJobs to be a truly valuable tool.

It would be great if Redwood RunMyJobs could be made available for other platforms. 

The support team is responsive, however, it can be more active and reach out to the users who need assistance. 

More flexibility in the reporting options would enhance the product. 

Enhancing the user interface would make it more appealing to new users with limited technical knowledge. 

The documentation is detailed. That said, it can be made more user-friendly and easily accessible. 

It would be great if advanced features were added to Redwood RunMyJobs. 

The cost may be of concern to smaller organizations with limited budgets.

I have been using Redwood RunMyJobs for the past six months to automate job processes at our organization.

I previously used a different workload automation solution called Control-M. Redwood RunMyJobs is so much easier to use than the previous tool that I have used. 

The user-friendly interface makes the work easier. It is way more flexible than the tools that I have used. It can be used to automate a wide range of tasks ranging from simple to complex tasks. 

It is of great use when it comes to integrating the tasks.

Redwood is used to create intelligent process flows that support diverse IT processes for business, including managed file transfer, hybrid cloud automation, complex data management, and DevOps.

To meet business demands, the content file can be uploaded to produce new documents. It connects to the PI system - the BODS system in our case.

Redwood Workload Automation becomes the primary location for the workflow and data flow from several platforms.

Redwood servers can be connected to Oracle DB, Peoplesoft, and other databases in addition to SAP.

It helps in reducing the workload and is platform-independent.

Redwood Workload Automation has less coding and scripting, and it performs and delivers business more quickly.

Redwood helps us to schedule batch jobs on a daily, weekly, and yearly basis to keep the business running smoothly.

It is simple to install Redwood Automation agent servers on every server side and trigger the necessary jobs in keeping with business needs, and many problems have been fixed, such as the ability to gather data on the number of activities that are executed each day.

Redwood enables people to focus on innovation instead of the daily management of repeated processes.

It also transforms the digital enterprise with scalability and integration with all technologies in a modern enterprise.

It also allows us to add dependencies that otherwise wouldn't be there and tie jobs from different systems together.

It is capable of adhering to service-level agreements for complicated order flows.

This also enables the interdependent scheduling of groups of window scripts and shell scripts.

It is a completely automated tool with minimal need for operator involvement, and less supervision is required to operate it.

While using the software we were lacking helpful documentation on how to use the product in some situations. We request that they provide more helpful documents in the future.  

The ability to get accurate counts of historical processes is limited. 

Migration from legacy solutions to Redwood business process automation is manual.

Customer support should be enhanced so that we can automatically raise tickets and incidents in customer service.

Apart from this, Redwood is doing great and is the best automation tool in the market.

I've used the solution for six to 12 months.

It's used for all of our SAP applications. We have ERP, CRM, and data warehousing. It's used for our PeopleSoft, and it's used for some of the other corporate internal applications. Informatica Data Warehousing uses it.

I don't build jobs. I'm part of the team that did the version and the infrastructure part of it. Our teams go through the process definition and the chain definition for the most part, and I believe they do not use the visual process editor.

In terms of deployment, the core of it is SaaS, and you still have some internal servers. It's never 100% SaaS.

Going to a SaaS solution has eliminated some of the down times that we needed to install some of our patches. For our agent servers, we're able to create redundant servers so that we can take one down at a time and not involve any downtime. So far, the various upgrades that we received had extremely short outage durations of one or two minutes. The ability to stay up-to-date and current, both from a security standpoint and from an application enhancement standpoint or bug fixes, has been fabulous as compared to an on-prem solution, which would take a long project to upgrade. That's probably been the biggest benefit. Moving to a SaaS solution has a lot of advantages. When you're running factories and projects 24 hours a day and seven days a week, uptime is very important, and you try to minimize any downtime, even planned downtime.

It has dramatically reduced the time and effort that our organization spends on deployment, updates, and maintenance. With our other application, it would be a six-month project to do a major upgrade. So far, with the upgrades that have been done by Redwood, the downtime is only for a few minutes. There is a gigantic difference.

We're pretty heavy into SAP. They have a good SAP interface where we're able to create and utilize jobs even from SAP, which gives us some additional features. It's about the same on the other applications that are simply running command-type batch jobs, but the SAP interface gives us a lot of flexibility. Some of it's similar to what we already had, but it has a positive impact on us.

It's a very powerful tool. It has a lot of flexibility for how you can define jobs and build them. There are different ways in which you can construct jobs depending on your specific needs and requirements. It has a lot of features for different ways that you can build jobs, which is great for power users but a bit confusing for newcomers because there are a lot of different options. 

It lacks some of the common reporting features. I'm a bit surprised that there aren't some standard reports to be able to extract any data on usage. They've described to us that customers have different reporting needs, so they let them develop those, but reporting is a common need. It would be helpful to have it as part of the solution.

One of our business groups has used Redwood SAP BPA for at least 10 years before I started working with it, and then the rest of our teams moved over from AutoSys to Redwood over the last year and a half.

It has been pretty stable. Performance-wise, we've had to work on it a bit simply because of our volume. That's more with database performance. We haven't had any problems with any jobs because of any bandwidth performance.

So far, it's been good. It scales. As we did the conversion, we did probably eight different deployments or eight different sub-projects to bring various applications live. That part of it scaled very well, with the exception of some of the performance of the database tuning, which took some time, but part of it had to do with the high volume of jobs that we run.

It's deployed across a broad list of applications, across multiple data centers. Its users include business people, developers, and schedulers for jobs. There are hundreds of people who use it.

I have contacted them. I would rate them an eight out of ten at this point.

Positive

Over the last year and a half, we've migrated from AutoSys to Redwood. We switched because of their roadmap and their commitment to keeping the product fresh by patching on a regular basis and providing regular updates. Looking at other competitors, there was also the cost-benefit.

The future of AutoSys was unclear. It was a product that we had used for almost 25 years, but the roadmap was unclear on whether that was going to be a viable product going forward. It put us onto a SaaS product that is definitely more stable and gives us a roadmap into the future for enterprise-wide job scheduling.

Redwood is a little more complex than the AutoSys application we used before. It creates some challenges from the standpoint that there's a two-step process. You build a job and then you schedule the process to run. You build a process definition or a chain definition, whereas, in AutoSys, you do it basically in one step. That part has been a little bit more difficult, but it has given us a lot more flexibility, specifically in terms of the ability to write some very complex calendaring that we couldn't quite do before for the scheduling portion of it.

It was complex. We had a high number of jobs, and we had a percentage of jobs that were very complex in terms of how they were built. Also, we were moving from a system that had been in place for over 20 years. So, you don't always have experts around who understood why it was done that way, but the conversion pretty much brought everything over the way it was executed before.

We spent a year. Part of that was the volume of jobs that we have and the number of teams involved. We've got multiple job scheduling teams by application. We don't have one central team, which made it more difficult from a conversion standpoint. There were a lot of people to train.

As a job scheduling tool, Redwood has reduced the footprint for what's needed. There are still process servers that are required to be inside in order to communicate with SAP and keep the communication inside, which is good from a security standpoint, but the core application is in the cloud. So, we're not responsible for patching the database or patching the core components of the application. This means our upgrades have become very simple because it's a small agent that gets updated during any software release. So, the actual upgrade process is just a few minutes of downtime, which has been a huge benefit. Server-wise, we probably have the same number of internal servers because there are some gateway servers that are utilized, and we've duplicated them and made them redundant so that we can take down and patch them one at a time to minimize any downtime and failover capabilities. Our net is probably similar, but the planned downtime is significantly or exponentially less.

Being hosted on SaaS has reduced the patching requirements that are needed. Any of the connectivity and vulnerability requirements are pretty much handled by the application now, so we don't have to deal with that internally. When you move to a SaaS solution, you're at the wind of the internet, if you will, for final connectivity, but it's not quite as important in job scheduling because your jobs, once they fire off and run, continue to run on the application servers if there is any outage. So, it's not like other applications that are more chatty or require a persistent connection.

We used the Redwood migration team. Our experience with them was good. They are sharp people, and they know their product very well. Alex Borders was the most helpful. He was our lead for the conversion. He had a huge wealth of knowledge.

From our side, there were two of us who worked on it from a standpoint. I worked on it from the technical side, and the other person worked on it from the governance side in terms of whatever we had to change internally process-wise, but each application had its own teams involved in it. So, there were hundreds of people involved in it. Most of it was from the testing and training standpoint for the job support and job processing teams, basically our developers and schedulers.

We're not even a full year into running it yet, so it's a little hard to provide any input about the ROI.

It initially surprised me because we went from an application that was priced by connection to agents/the number of agents to an application that was priced based on the number of job executions. At that time, many of the products we looked at were also priced on job execution. That seems to be more common in the business or in the vendors that provide solutions out there, but that was probably our biggest difference.

An evaluation of other products was done, but we had already used the SAP version of Redwood. So, we were already familiar with its capability. The fact that we already had people who were familiar with supporting it weighed pretty heavily into it.

It's important to do a PoC, take some of your complicated processes, and ensure that your expectations are met.

For the people I work with, the time freed up from using this solution is about the same because we were already using an Enterprise job scheduler. It's probably the same workload. Similarly, the reduction in service interruptions and process failures is the same, but we've drastically cut down our planned downtime. 

I would rate it a nine out of ten.

Redwood RunMyJobs is primarily deployed for orchestrating and scheduling tasks. It caters to a diverse range of environments, spanning enterprise IT systems, data centers, and manufacturing facilities. The solution strives to streamline the administration of intricate workflows and assignments, guaranteeing their prompt and effective execution. 

Although the details of the solution's environment are unspecified, it's clear that it has broad applicability across diverse industries and sectors. From expansive IT infrastructures to manufacturing plants and financial institutions, any environment grappling with intricate job scheduling and automation stands to gain from Redwood RunMyJobs.

The solution automates seamlessly. Additionally, Redwood aids in streamlining the development and deployment processes, facilitating the efficient delivery of software products. 

With its ingenious features, Redwood enables the seamless integration of code changes, ensuring continuous testing and deployment. This not only saves time and effort but also guarantees a heightened level of quality in the final product. 

Moreover, Redwood's intuitive interface allows for effortless scheduling of pipelines, granting users unrivaled flexibility and control over their software development lifecycle. 

Equipped with comprehensive notification capabilities, Redwood ensures that stakeholders are promptly informed of any critical events or issues, enabling swift action and resolution.

Redwood, a marvel in the realm of business Process Automation, reigns supreme in the art of scheduling, monitoring, and birthing reports. 

It conjures simplicity from the depths of complexity, effortlessly shouldering burdensome workloads. Its integration features allow for connectivity, linking with other third-party applications, and orchestrating the elegant exchange of data. 

The solution has an astonishing array of mind-boggling functions, including good reporting features, monitoring and alert services, a captivating user interface, boundless machine learning capabilities, and an unparalleled customer support system.

The customer support, a formidable legion of troubleshooters, stands ready to lend their expert guidance.

The user interface has an intuitive design.

I have not noted any downsides.

I've used the solution for seven months straight.

Intensive testing aids in detecting and resolving potential issues prior to deployment. 

Expandability gauges how effectively a system can handle heightened workload or demand. It's frequently divided into three categories, infusing additional resources (such as memory, CPU, or storage) into a solitary machine. It's generally simpler to execute, yet it may face limitations imposed by the hardware itself.

My company dabbled with alternative software in the early stages, but this solution emerged as a solution that satisfied all of our intricate requirements. With its unparalleled capabilities and ingenious features, it increases efficiency and productivity. 

Ensuring privacy, security, and ethical considerations can convolute the setup process, particularly when handling sensitive data or deploying  systems in regulated industries

The actual return on investment hinges on the seamless integration of capabilities into workflows and processes, as well as adeptness in fulfilling user requirements.

We use Redwood RunMyJobs for job scheduling and all job-related things.

We were previously using SAP SM37, and we were not able to schedule the jobs. Redwood RunMyJobs has been very useful for job scheduling and checking and monitoring jobs.

Redwood RunMyJobs should add more good features.

I have been using Redwood RunMyJobs for two years.

I rate Redwood RunMyJobs an eight or nine out of ten for stability.

Many users are using Redwood RunMyJobs for job scheduling in our organization.

I rate Redwood RunMyJobs an eight out of ten for scalability.

The solution’s initial setup is easy.

Redwood RunMyJobs is deployed on-cloud in our organization.

Overall, I rate Redwood RunMyJobs an eight out of ten.