Apache Camel is an open source integration platform.
N/A
Nintex
Score 8.0 out of 10
N/A
Nintex offers a platform that helps companies discover, automate, and optimize business processes.
$480
Minimum 1,000 users per user
SAP Signavio Process Transformation Suite
Score 8.1 out of 10
N/A
The SAP Signavio portfolio offers an integrated platform that helps usersto realign the organization and bring changes, with a suite of products that support business processes. The SAP Signavio portfolio offers a range of business transformation solutions to serve the emerging practice of customer excellence (CEX). SAP Signavio solutions bring together a full 360-degree view of outside-in and inside-out thinking, translating experiences into operational reality by putting the customer at the…
Message brokering across different systems, with transactionality and the ability to have fine tuned control over what happens using Java (or other languages), instead of a heavy, proprietary languages. One situation that it doesn't fit very well (as far as I have experienced) is when your workflow requires significant data mapping. While possible when using Java tooling, some other visual data mapping tools in other integration frameworks are easier to work with.
We use Nintex to automate fundraising outreach at scale. It helps us send personalized emails to a large contact list, and we’d also like to automate follow-ups when there’s no reply. If you need highly customized solutions or clean, fully controllable code, I wouldn’t recommend Nintex. It has many features, but it’s not the same as building your own system from scratch. That said, it can save a lot of time for standard automation workflows.
Pros: 1. It reduces technical debt and accelerates a smooth transition, while harmonizing across data migration regions which replaces the legacy customization that are not for S4/HANA. 2. It cuts operational cost by 30% - 40% and improves SLA adherence, while process intelligence identifies duplicate or redundant approval steps when we know SAP ecosystems ties all modules together for better data insights. Cons: 1. Complicated and costly for small businesses. 2. Mature process required for better data feeding and data insights. 3. If non-SAP system data feed might cause misleading and incomplete data insights
Camel has an easy learning curve. It is fairly well documented and there are about 5-6 books on Camel.
There is a large user group and blogs devoted to all things Camel and the developers of Camel provide quick answers and have also been very quick to patch Camel, when bugs are reported.
Camel integrates well with well known frameworks like Spring, and other middleware products like Apache Karaf and Servicemix.
There are over 150 components for the Camel framework that help integrate with diverse software platforms.
Integrations with other services using various secure authentication methods, along with the seamless integration with SharePoint, are the icing on the cake. This makes it superior to other BPM tools available in the market.
Flexibility in application development - The diverse configurable properties offer multiple ways to utilise the controls and events, affording the flexibility to expand your scope and enabling the creation and use of processes in a myriad of ways.
The streamlined and efficient deployment process significantly accelerates release management, allowing for faster and smoother implementation of updates and new features.
The user interface of the pages offers a more refined and appealing look and feel compared to most other BPM tools.
Location agnostic (or home office agnostic) collaboration in virtual workshops
Internally within the team or with clients, I can prepare, gather materials, and lead during a workshop or meeting with SAP Signavio Process Transformation Suite and feel incredibly positioned as the facilitator. Whether in real time or in an asynchronous manner.
The combination of highly adaptable and visual work with collaborative tools like forms, comments, timers, and point voting transforms it into a tool I use frequently.
If you are creating a process with parallel subprocesses, there's no way to see, in a single view in Nintex, all the steps for the subprocesses. You have to view each sub-process in its own view, so it's hard to see what's going on at a high level.
There isn't an easy way to filter the processes by another user (not yourself) in Nintex. There is a report that shows processes and objects by user, but that's not as convenient. This is something that I've seen in other tools (OpenPages by IBM) so I am surprised that it is missing.
Nintex doesn't really have a way to capture iterative processes (which we have a lot of). It's designed for linear processes.
For businesses looking to improve their current business processes, I think SAP Signavio Process Transformation Suite is incredibly well-suited.
In my opinion, SAP Signavio Process Transformation Suite excels in sectors with strict regulatory requirements.
I think SAP Signavio Process Transformation Suite is the best option when teams from several departments must work together on process design or improvement initiatives because of its real-time collaboration capabilities.
We are currently investigating which collaboration platform best suits our needs. Chances are that we move to SharePoint Online and then we're going to also consider the microsoft power platform (power automate and power apps) to develop forms and workflows. Aspecially the pricing model for the cloud is currently a blocking factor to go for the Nintex solution in the Cloud.
Based on the on-prem experience with this tool, I believe that they have a lot of potential to help the online version catch up to where the on-prem left off. Nintex developed their online version and it is not as fully formed or capable compared to the on-prem version, and the licensing model scales back what we would have liked to be an expansion or at least continuous improvement of existing flows. It is also not near as user friendly specifically to non-developers and has an uncanny similarity to Microsoft Flow in the online instance. Consistent with my reviews of the tool - I believe they have some good approaches to design thinking that, if translated well from on-prem to online, could make this a clear winner again.
The Nintex Process Platform has never crashed or had any availability issues during my usage. However there was an issue that was of my own making that caused a slowdown of the system. I had set up a process to run once a day and check for employees on a list that had certain parameters selected, and for some reason that I had to troubleshoot, the process instead ran constantly, which filled the cache quickly. I ended up having to dismantle that process so the system didn't crash.
Unlike any other process automation product out there. Not only is it a low-code, easy to use tool for building processes in environments like SharePoint or Salesforce, they have really started to expand their tool-set by offering tools to manage other things like process mapping, RPA, mobile,etc.
The support team works as fast as they can and they are usually fast to solver the issues. Sometimes they need more time to solve one of them because our workflows and so on are more complex than usual clients.
I find it tedious, and of bad quality. The product does not have the maturity of an enterprise tool and yet when teething or other issues that should not be there appear the response is underwhelming. Customer success managers are meant to help customers follow up on these cases because the feedback is routinely dismissed
I used the Nintex training software, it was easy to watch and follow along. It didn't go too fast and was descriptive enough to understand what the steps needed were in order to produce efficient workflows and user friendly forms.
1.Start with Simple Workflows: Begin with basic workflows to gain user confidence before tackling complex processes. 2.Involve Stakeholders Early: Engage business users and IT early to align workflows with real business needs. 3.Comprehensive Training: Invest in user training to ensure smooth adoption and reduce resistance. 4.Leverage Prebuilt Templates: Use Nintex’s templates to speed up implementation and maintain consistency. 5.Iterate and Optimize: Continuously improve workflows based on user feedback and performance metrics.
Training is taking way longer than expected. We have had more than 50 hours of training and still do not feel proficient enough to do anything meaningful with Process Intelligence. The Process Insights are pretty intuitive but does take a willingness to dig in and explore, but in general good right out of the box.
If you are looking for a Java-based open source low cost equivalent to webMethods or Azure Logic Apps, Apache Camel is an excellent choice as it is mature and widely deployed, and included in many vendored Java application servers too such as Redhat JBoss EAP. Apache Camel is lacking on the GUI tooling side compared to commercial products such as webMethods or Azure Logic Apps.
Microsoft environment does not have the scalability of Nintex; it is perfect for small and medium-sized companies, especially in environments where Microsoft environment is almost entirely used. Although Microsoft offers options to connect to other applications, its platform lacks the development and robustness that Nintex provides. Nintex not only covers Microsoft environments but also Google and other important platforms.
We were able to end the use of archive versions thanks to SAP Signavio Process Transformation Suite, and everyone has access to the most recent archive. Mac and Windows users can collaborate on a single document. A design tool that spans the concept phase, design phase, and delivery to engineering
The scalability is really bottlenecked by the imagination of the user. I was able to make processes for my own personal usage, making my daily tasks easier. I was also able to make processes that affected hundreds of employees, making large standardization and efficiency gains. So either way, the system is used the same way, and I was the limiting factor.
Very fast time to market in that so many components are available to use immediately.
Error handling mechanisms and patterns of practice are robust and easy to use which in turn has made our application more robust from the start, so fewer bugs.
However, testing and debugging routes is more challenging than working is standard Java so that takes more time (less time than writing the components from scratch).
Most people don't know Camel coming in and many junior developers find it overwhelming and are not enthusiastic to learn it. So finding people that want to develop/maintain it is a challenge.
People have woken up to the amount of overlap after mapping their processes.
People can be resistant to process changes. You need to have the support from above or support from the 'business' that you are process changing to be able to see the positive impacts.
Numbers talk. if you can get a general salary figure from your HR dept to show savings for 'employee bands', then when you present reports, they will be all the richer in data.
With the help of Signavio, we are now much more operationally efficient, which saves money and makes better use of our resources.
The software's emphasis on collaboration has encouraged innovation within our teams, resulting in original solutions and better project outputs.
Compliance is crucial for our sector. We have lowered the danger of regulatory problems by maintaining stringent compliance standards with the aid of Signavio.
