Camunda Platform vs Redwood Business Process Automation - Workload Edition

• Embedding a first-class process capability in your application.
• Providing a standards-based modeling capability, backed by a standards-native engine.
• Great support for developers and a developer community.
• Great set of comprehensive APIs across a number of different design points
• All of the code is available in GitHub as a great open source project with Apache licenses.
• Comprehensive documentation of code and APIs and usage.
• Innovative spin-offs like Zeebe.
• Support for micro-services orchestration.
• Support for both embedded and stand alone usage scenarios.
• The company is innovative and focused on this space.

Read full review

• SAP Batch Scheduling - This is THE BEST tool for triggering SAP jobs, bar none.
• User management- Other scheduling tools make it much more difficult to manage user access. Redwood user access management is a breeze and take less than half the time it take in other products.
• Scheduling Flexibility- The ease with which you can make custom time windows with Redwood is one of my favorite pluses. You can build as simple or as complex of a time window as you need to with Redwood.
• Support- The support that you get from Redwood is in my opinion the best in the world. I have dealt with all the big name players in IT and they all pale in comparison to Redwood. You will never feel like you are in it alone with the best support in the world right at your fingertips.

Read full review

• GUI lacks shortcuts
• GUI is not intuitive and hard to use. More involved technical capabilities are hidden in the menus which make navigation and setup difficult.
• Documentation is not fully fleshed out and examples are bare. The target audience is technically adept software developers, with expected experience and knowledge of javascript and java.
• Community exists but is relatively small and highly technical. Support is not easily accessible unless the costly paid version is opted for.
• Programming languages used are confusing as it merges java and javascript in certain scripts.
• Debugging is difficult as there is no error/typo checking or console in the designer when using scripts. It does not have the capabilities of more fully featured IDEs, but is a simple text entry for scripts.

Read full review

• The documentation is lacking severely, many times even leading to a suggestion of paying for professional services to figure out processes. Also not updating documentation when a new release makes the old documentation obsolete.
• AS400/iSeries has been a constant battle since inception, once an update fixes one thing, another seems to break within the AS400/iSeries space, and sometimes the fixes don't actually fix the issue. Over time now this has gotten much beter.
• Allowing an issue to go back and forth within a ticket countless times (sometimes over 40 responses) without just getting everyone together on a meeting. Update - this has gotten much better with time.
• Communication needs a lot of improvement. I have had to reach out to support just to get release notes when a new release is made available.
• The ability to get accurate counts of historical process runs is limited currently to 35 days and since you are billed for each process run in all environments, not just Production, this limits accountability in historical billing inquiries.

Read full review

• Freeware makes testing and utilizing Camunda a cost-effective solution
• High level of difficulty in implementation may require a lot more time and effort than normally expected. (2-3x more effort than other paid and fully featured solutions)

Read full review

• We reduced our MRP cycle from around 12 hours down to approximately 3
• We were able to let end-users trigger specific month-end jobs without also having the ability to submit anything else.
• we are able to schedule jobs in much more flexible ways than SAP offers
• We've had no negative impact by using Redwood

Read full review