Nintex offers a platform that helps companies discover, automate, and optimize business processes.
$480
Minimum 1,000 users per user
OpenText Process Automation
Score 6.0 out of 10
N/A
OpenText Process Automation is an enterprise-scale Business Process Management (BPM) and Digital Process Automation (DPA) platform designed to orchestrate complex, data-heavy workflows. The solution specializes in Content-Centric Automation, natively integrating with enterprise content management systems to automate processes that require deep document understanding and regulatory compliance.
N/A
SAP BPM
Score 7.0 out of 10
N/A
SAP NetWeaver Business Process Management is a business process management offering and application infrastructure. It supports joint modeling of processes, central process execution via a Java-based engine, provision of interfaces for users, and integration of business rules into processes.
I was not part of selecting Nintex, but I think Nintex does a better job of generating linear flowcharts vs. Microsoft Visio because it automates the majority of the process of creating process maps. (Microsoft Visio is better for creating flowcharts that are not linear. …
Nintex is easier than Visual Studio and richer than SharePoint Designer, chosen for accessibility, scalability, and faster business process automation.
Nintex is great! It works well with these applications. We can build profiles to give the bot the ability to use the applications like an employee. This gives us the ability to automate tasks inside our applications. As stated earlier, some of the applications are web-based. …
Nintex licensing is very suitable for our needs and solutions built are embedded and is adding a lot of value with the added benefit of being easy to maintain. The time to production for building some complex solutions versus other low code platforms is significantly less …
We selected Nintex because Process Manager is a purpose designed platform for knowledge management. However, what we discovered is that there are significant limitations, which has lead us to now explore developing a knowledge management platoform in sharepoint. this is a much …
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 …
Nintex Process Platform is a great tool for automatic tasks and creating forms in SharePoint Online. For automating using other applications, including third party, Power Automate has more usage.
Xmind was great for mind mapping, but when I tried to use it as a process mapper, I found it was rather lacking. It has its uses, but process mapping (at least for us in our stage and phase of mapping) was not up to the task, unfortunately. We didn't have any other software we …
We use Outsystems for other processes in our operation but we see that this platform is not able to indentify processes when drawed. Besides that OutSystems requires some basic development knowledge to use it. This makes it not really useable for business units.
AppWorks platform is very user friendly which will help us to develop the components quickly and deploy it easily. Flows can be developed quickly compared to others platform where business users can view the flow easily.
I found the initial setup of NetWeaver is much simpler than other products especially in an SAP environment where we have SAP ERP/HRM/CRM as it can be well integrated with other SAP products. The only drawback is the need/dependency on SAP Portal. It is better suited in an …
While Winshuttle is comparable, they are really two different tools in that Winshuttle is a hang-on tool while BPM is a catalyst tool. With WS, workflows start in SAP, flow to Winshuttle, and back in SAP (at least with my limited experience). In BPM, everything is housed in the …
Features
Nintex
OpenText Process Automation
SAP NetWeaver BPM
Reporting & Analytics
Comparison of Reporting & Analytics features of Product A and Product B
Nintex
6.7
Ratings
14% below category average
OpenText Process Automation
8.0
Ratings
4% above category average
SAP NetWeaver BPM
10.0
Ratings
26% above category average
Dashboards
6.70 Ratings
8.00 Ratings
10.00 Ratings
Standard reports
6.90 Ratings
00 Ratings
10.00 Ratings
Custom reports
6.50 Ratings
8.00 Ratings
10.00 Ratings
Process Engine
Comparison of Process Engine features of Product A and Product B
Nintex
7.1
Ratings
16% below category average
OpenText Process Automation
8.8
Ratings
5% above category average
SAP NetWeaver BPM
10.0
Ratings
18% above category average
Process designer
7.70 Ratings
9.00 Ratings
10.00 Ratings
Process simulation
5.00 Ratings
9.00 Ratings
10.00 Ratings
Business rules engine
7.50 Ratings
9.00 Ratings
10.00 Ratings
SOA support
7.00 Ratings
9.00 Ratings
10.00 Ratings
Process player
7.40 Ratings
9.00 Ratings
10.00 Ratings
Support for modeling languages
6.00 Ratings
9.00 Ratings
10.00 Ratings
Form builder
7.90 Ratings
8.00 Ratings
10.00 Ratings
Model execution
7.90 Ratings
8.00 Ratings
10.00 Ratings
Collaboration
Comparison of Collaboration features of Product A and Product B
Nintex
9.0
Ratings
8% above category average
OpenText Process Automation
8.0
Ratings
4% below category average
SAP NetWeaver BPM
10.0
Ratings
18% above category average
Social collaboration tools
9.00 Ratings
8.00 Ratings
10.00 Ratings
Content Management Capabilties
Comparison of Content Management Capabilties features of Product A and Product B
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.
Especially for telecom sector, AppWorks handling huge data and transform it easily and very quickly to send it to target systems with in seconds. At a time communicate more than one systems.
If your organization is heavily invested in SAP as an enterprise wide solution already, BPM is really your only option. Solid, seamless integration, smooth workflow, and data trails for business analysis are impeccable. If you aren't already heavily invested, key questions to ask would be - Am I using too big a hammer? The results are impressive, no doubt, but the integration of BPM is demanding. A less-demanding, more intutive tool like Winshuttle or even AR Projekt that hooks in to SAP might be a simpler option
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.
New Responsive Form does not allow to create a custom button anywhere we want. It will be useful to allow to add the button control anywhere within the form that can trigger the click event rule.
It will be useful to allow CSS in New Responsive Form.
Found HTML Table tag does not work properly in New Responsive Form.
More functionalities related to HTML, CSS and JavaScript in New Responsive Form will be very helpful.
Renewal is mainly on the fact that Nintex is so widely used and it would be impossible to migrate all of these existing workflows to another engine. Third-party lock-in within SharePoint is pretty strong, which makes it difficult to move to something else. Our Nintex database is well-over 100 GBs. Nintex email support is very good, and I've been impressed. The Community however is non-existent and filled with unanswered questions.
Nintex Workflow does exactly what it is advertised to do: make workflow development fast and easy. It doesn't provide very much new functionality, but it isn't really supposed to. When I am working with a client on a SharePoint project, I am always happy if I hear that they use Nintex Workflow, as it makes workflows much easier.
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.
We have our own tech support for systems, I would say they probably could use more training on it, I don't really think it's anything regarding the SAP system, but more the knowledge they have on the system itself. It seems to take longer for them to fix any issues we may come across.
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.
I was not part of selecting Nintex, but I think Nintex does a better job of generating linear flowcharts vs. Microsoft Visio because it automates the majority of the process of creating process maps. (Microsoft Visio is better for creating flowcharts that are not linear. because it is less automated and more flexible.)
AppWorks platform is very user friendly which will help us to develop the components quickly and deploy it easily. Flows can be developed quickly compared to others platform where business users can view the flow easily.
I found the initial setup of NetWeaver is much simpler than other products especially in an SAP environment where we have SAP ERP/HRM/CRM as it can be well integrated with other SAP products. The only drawback is the need/dependency on SAP Portal. It is better suited in an environment where SAP ERP is running.
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.
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.