Nintex offers a platform that helps companies discover, automate, and optimize business processes.
$480
Minimum 1,000 users per user
Visual Studio
Score 8.8 out of 10
N/A
Visual Studio (now in the 2022 edition) is a 64-bit IDE that makes it easier to work with bigger projects and complex workloads, boasting a fluid and responsive experience for users. The IDE features IntelliCode, its automatic code completion tools that understand code context and that can complete up to a whole line at once to drive accurate and confident coding.
Nintex is easier than Visual Studio and richer than SharePoint Designer, chosen for accessibility, scalability, and faster business process automation.
What previously stood K2 apart from Nintex was purely the ability to have workflows executed outside of SharePoint. Nintex are due to release a product that resides in Azure that provides this feature as well. K2 should really look into redesigning the development GUIs they are …
Easier to use. Less complicated in setting up the system although K2 may be more powerful in terms of features and also not dependent on sharepoint engine. Nintex serves our purposes.
Well, the workflow design is much easier with Nintex Platform. Also the functions are much more versatile. But, if you are a programmer, forget what you know, you have to learn to think in SharePoint-ish and Nintex-ish.
There are not many SharePoint based workflow engines. We looked at K2 but the forms functionality provided by Nintex is what gives it the advantage. K2 is more flexible at the cost of more technical implementation. Nintex gives us an easy to use platform that anyone can pick up …
Microsoft Sharepoint Workflow 2010 is free and offers a lot of functionalities. Nintex has a better UI and is really simple to use. Nintex workflow set up is so simple that I can imagine that even non-IT employees could create one and help them and their teams to reduce manual …
The biggest feature difference we found was the ability to copy and paste a workflow step is missing from SharePoint Designer and available in Nintex. Additionally, Nintex has a wider variety of workflow tasks to choose from and an easier to easier to use designer. Nintex …
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.
When working with base C# code for desktop and web projects, then Microsoft Visual Studio is ideal as it provides the libraries and interfaces needed to quickly create, test and deploy solutions. It is when slightly more complex scenarios are required that issues can arise. The built-in integration for things like PowerBI Paginated Reports and dashboards is far from ideal.
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.
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.
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.
VS is the best and is required for building Microsoft applications. The quality and usefulness of the product far out-weight the licensing costs associated with it.
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 love the overall usability of Microsoft Visual Studio. I’ve been using this IDE for more than 20 years, and I’ve seen it evolve by leaps and bounds. Today, with AI and code-suggestion/completion features, developers no longer need to remember countless libraries, methods, or language syntax, or invest a huge amount of programming effort to complete a project. It truly offers everything a developer needs to program, debug, test, and deploy in a single IDE.
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.
There are many resources available supporting Visual Studio IDE. Microsoft whitepapers, forum posts, and online Visual Studio documentation. There are countless demonstration videos available, as well. If users are having issues, they can call Microsoft Support, but depending on the company's agreement with Microsoft, the number of included support calls will vary from organization to organization. I've found that Microsoft support calls can be hit or miss depending on who you get, but they can usually get you with the right support person for your issue.
IT is very complicated to understand all the functions that the environment has if you are not familiar with this type of development environments. It is important to select a good in-person training to achieve to understand all the possibilities and the capacity of the application. In this case, you will be able to develop a lot type of different applications.
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.
If you are not accustomed to develop in this type of development environments it would be complicated to follow all the parts of the course because if the course does not include a great tour with all the concepts to develop you will not have the option to understand all the functions.
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.
I personally feel Visual Studio IDE has [a] better interface and [is more] user friendly than other IDEs. It has better code maintainability and intellisense. Its inbuilt team foundation server help coders to check on their code then and go. Better nugget package management, quality testing and gives features to extract TRX file as result of testing which includes all the summary of each test case.
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.
Using the integration between Visual Studio and our source control service, the cost of re-work and losing code is drastically reduced.
Paid versions of Visual Studio enable developers to be so much more productive than hacked-together open source solutions that it's hard to imagine developing in Windows without it.
When combined with support subscriptions and the vast array of free online help options available, Visual Studio saves our developers time by keeping them coding and testing, not wasting their time trying to guess their way out of problems or spend endless hours online hoping to find answers.
