Nintex offers a platform that helps companies discover, automate, and optimize business processes.
$480
Minimum 1,000 users per user
ProcessMaker
Score 8.9 out of 10
N/A
ProcessMaker is a process automation platform that helps organizations optimize and scale their business operations. By combining workflow automation, AI-driven decision-making, and advanced analytics, ProcessMaker empowers businesses to streamline complex processes, improve efficiency, and enhance customer experiences.
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.
The task mining component is well suited for processes where there are a lot of steps performed in a variety of systems, particularly by a single individual on a team. It also requires a robust activity ID to be able to track an activity. It is not well suited when trying to track a process where the content is in an email.
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.
User interface. It is clean and easy to understand. You won't get overwhelmed the second you log in.
The workflow maker. With a drag and drop interface, you can easily visualize and implement what you want on the screen. Out of all the programs we tested, this one had the easiest process maker and designer.
Ease of understanding. My biggest recommendation would be that this program is easy to access for anyone. There are complications (see negatives) but this program can be implemented quickly and efficiently, and nearly anyone can learn to use it. You will not feel like you are in the dark with it.
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.
Complications when you get to the more advanced pieces. When trialing, I found that the more advanced a process got, the more complicated it got for me in coding. When you begin using the more advanced features, you will find that you need to have a basic knowledge of coding - otherwise you won't go any further. This was my sole issue. Unfortunately, it was one that would have brought the school to a grinding halt if they were to ever get more complicated than they were.
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.
I gave this overall rating for ProcessMaker due to its overall flexibility, design and ease of use for most. Examples of this from us include it being an excellent and trustworthy tool for automating processes, the abilities and capabilities for real-time process tracking and the web-based accessibility and implementation which allows for easy access and management of the tool.
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 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.
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.
Before making the decision to get ProcessMaker, we assessed different and best options in the market, which are also quite competitive. KiSSFLOW, Blueworks Live, and Bizagi, being the most relevant and ADONIS, to mention the ones we consider the most relevant and capable of meeting our needs. In the end, we went for ProcessMaker because of mainly three things as described before: 1. Real-time process status tracking. 2. Metrics and dashboards. 3. Ease of use for constructing diagrams.
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.
The capability is robust and quite industry agnostic. It would benefit significantly with some out of the box models - e.g. procure to pay on SAP and similar. They could also develop industry specific examples which could kickstart the implementation for organizations.
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.
I'm using Communication edition to introduce BPMN in my organization. I can build the first process in a short time, make my boss more confident with my job.
But, with ProcessMaker, we need more time to design code to handle the process, and without PHP/Javascript Programmer, it seems hard to work with more and more processes online.
However, IE Browser is not well supported, somewhat let the user confuse.
