Nintex Process Platform Reviews

It is very easy to create and deploy. It does not take your time like SharePoint Workflow. There is no need for the IT people to do it. SharePoint Workflow, needed a programmer to do it. So there are vendors looking forward to Nintex because it is easy to create by the end-user.

They have an expensive license for vendors. They have two types of licenses. It is the standard and enterprise. Some actions in the enterprise, are not available in the standard. We need all the features to be in the standard license. Around fifty features are not in the standard license. That is why it is a problem for us. I am looking forward to when they have the same features in the standard license as the enterprise license.

I have been working with Nintex Workflow for the past twelve years.

Nintex Workflow has great stability.

Nintex Workflow is definitely scalable.

Technical support is great to work with.

The initial setup was straightforward.

We did everything in-house and it is extremely user-friendly. 

The price is too high currently for the license structure. There are two types of licenses standard and enterprise.

Nintex Workflow is user-friendly and saves time I would rate Nintex Workflow a ten out of ten.

We use the solution for a lot of things. However, one of the main things we use it for is approval workflows.

I really like the visual representation. It actually looks like a flow chart, which is nicer than a SharePoint Designer workflow, which doesn't have that ability.

The solution is a bit too expensive. It could be cheaper.

I've been dealing with the solution for two or three years at this point.

The product is quite stable. I haven't had issues with bugs or glitches. It hasn't crashed or frozen on me. It's reliable, as far as I can tell.

It's my understanding that the solution is scalable. If a company needs to expand it, it should be able to do so.

We have about 1,500 users on the solution currently. Anyone who can access SharePoint can access this product, and that is pretty much the entire company.

I've dealt with technical support in the past. They could be better. They aren't as responsive or knowledgeable as they could be. I'm not completely satisfied with their level of service. That's just my own personal experience. They have tried to be helpful, and the issues I had with them were a long time ago.

The initial setup, as far as I understand it, was not complex. It was very straightforward. However, I personally didn't install it. It was installed when I came to the job.

The cost of the solution is quite high. If they could work to reduce it for their customer, that would be ideal for us.

We pay on a yearly basis. It's my understanding that we pay approximately $11,000/year.

We're just customers and end-users. We don't have a business relationship with the company.

I am using the latest version of the solution, whichever it is. I'm not sure of the exact name of the version.

I don't know how the product compares with other solutions other than the older versions of Workflow such as SharePoint Designer.  I know that with Online, SharePoint Online, there are other workflow management tools that you can use if you would like to.

In general, I would rate the solution at an eight out of ten. We're mostly happy with it.

Process automation, electronic forms, and digital transformation in all versions of SharePoint, on-prem and in Office 365. As a consultant and developer, I have used Nintex everywhere, including the SharePoint-agnostic Nintex Workflow Cloud.

In some instances, workflows I’ve built for customers have transformed the business, saving significant time and costs compared to manual, legacy processes. In several instances the savings have been enough to provide the ROI for SharePoint and Nintex licensing, and project costs, within a business quarter.

A well-placed digital transformation solution can reduce turnaround for key processes, enabling businesses to compete with and beat out competition by streamlining their processes and enabling their workforce to get more done in less time.

As a workflow automation solution, being able to route, approve and manage content is one of the few areas in SharePoint where there is a true ROI. Provides the ability to automate SharePoint processes (building sites, lists, updating content).

You can also automate document and content processes, onboarding and offboarding, and general IT and HR solutions.

With an extensive list of integrations with LOB data, your workflows can extend far beyond SharePoint, driving adoption of SharePoint and saving people, departments, and companies significant time in their daily processes. These are huge value drivers for SharePoint and Nintex.

• Built-in reporting on-prem is limited and clunky at best.
• Integration can be fairly technical, and often business rules inhibit product capabilities or force a developer to consider alternate methods for integration.
• Hawkeye is emerging as a reporting solution, but as a V1 product it’s not very useful yet.

Nintex is as stable as your SharePoint farm (on-prem), and in Office 365 workflows are robust. The application functions as expected and any issues with workflows or forms typically come down to design flaws rather than application issues. Nintex has been out and available since SharePoint 2007, so it’s a mature platform.

Scalability is tough. Workflows in SharePoint have the lowest priority of any task, and, in on-prem, workflows execute against the Web front-end servers. If your WFEs are under spec or at spec, workflow load will impact performance, and you may need to up resources or consider adding WFEs to enable large-scale deployments. 

In Office 365, the licensing model will be your limiting factor (subscription for the number of published workflows) so scalability is a non-issue.

Nintex technical support is not great. On a scale of one to 10 they are a three. They are slow to respond, and you often have to wait for or ask for escalation. It’s important to note that they only support "break/fix" – they will not assist with design or development questions. However, the online community and documentation in most cases more than makes up for support.

SharePoint Designer and Visual Studio are alternatives, as are K2 and a few newer players in the visual workflow and forms design arena. These tools tend to be far more technical to use, harder to support, and also have limitations not inherent to Nintex. While Nintex is an expensive solution, the value can be returned very quickly, with the quick development and go-live cycle, as compared to traditional or competitor tools. This is a key value for Nintex.

Setup is simple and straightforward. There are a few prerequisites for installation, but the Nintex documentation for on-premise installation is solid and, if followed, the installation will run very quickly. It does involve some downtime so planning is required (several IIS resets during installation). However, it’s one of the easier things to install in SharePoint.

In Office 365, installation is as simple as installing it from the store and adding the app to the site collection, so could not be much easier.

Nintex products are expensive, but valuable. Licensing in on-premise was historically based on a perpetual model, where you’d license per Web front-end. However, they are switching exclusively to a consumption (subscription) model, where you purchase the number of workflows you think you’ll use in your environment, and can scale up from there. 

I suggest talking to a Nintex partner for licensing advice and guidance for your specific needs.

We have tested and evaluated numerous competitors, the principal of which is K2. However, K2 is equally expensive when you get down to specifics, and requires a dedicated infrastructure, whereas Nintex resides on existing SharePoint Servers. K2 is also far more technical in nature. It does have some benefits over Nintex (principally high-volume workflows – think point-of-sale or hundreds or thousands of transactions per hour), so careful evaluation of your needs is important in selecting the right tool.

I have also developed workflows using SharePoint Designer and Visual Studio, but again they are far more complex and longer to develop, as compared to Nintex.

Get a trial, talk to a technical sales rep, and just go in and try to build something. It’s pretty amazing how easy it is to use, and trials are good for 30 days. Talk to a premier partner if you can.

Some time ago, I implemented a demo in Nintex for various use cases such as getting emails from the team, reading the email, writing the email, opening the email, and getting the attachment.

My team and I created a demo using Nintex, focusing on getting emails, reading, writing, and managing attachments. However, we did not explore Nintex Process Platform's full potential, and our hands-on usage was limited to demonstrations.

The user interface in Nintex needs improvement. It is not very intuitive and requires changes. Additionally, the deployment process should be easier.

My team and I have been familiar with Nintex Process Platform for about one year, mainly for learning.

I rate Nintex's stability as an eight out of ten.

I rate Nintex's scalability as an eight out of ten.

The technical support provided by Nintex is very helpful, which I rate as nine out of ten.

Positive

The Nintex Process Platform serves as an alternative solution, similar to UiPath. However, our company has Nintex, and thus I recommend Nintex to customers.

The installation process for Nintex required about two weeks.

The installation was supported by the distributor, and I am not certain about the exact number of people involved from my side.

Nintex Process Platform is expensive. Prices relate to both features and the professional services necessary due to our lack of an implementation team.

Overall, I would recommend Nintex Process Platform to others.

I'd rate the solution eight out of ten.

K2's best feature is that it can solve complex tasks, issues, and projects with little coding.

K2's support for DevOp team corporations is weak.

I've been using K2 for two and a half years.

K2 is very stable - there have been almost no problems in the time I've been using it.

The initial setup is straightforward because it can be deployed on a DB server, application server, and web server.

For the initial hundred users, the cost is $21,000 per year, which I find too high. There are soft thresholds for this initial license, like the number of forms and environments. 

I would give K2 a rating of seven out of ten.

We have predominantly been using the solution as the front end for automation solutions. I'm a program manager. We don't have a direct link to K2, but we work closely with them and carry out a lot of maintenance and other work through them. So it's quite a deep-rooted relationship.

The biggest selling point for us was that the solution had out of box connectivity with UiPath and we didn't have to write any custom code to be able to invoke UiPath bots and automation solutions. That worked well for us in the past but when you talk about other specific functionalities, like the applications or authentication on native operating systems for mobiles and those kinds of things, K2 is lacking big time. The solution doesn't really have a good set up and I think as more and more businesses want app rather than desktop systems or web systems, K2 is not necessarily the best solution going forward.

The solution is heavy and cumbersome and it has a very stringent way of doing things. It's not difficult but at the same time it's not flexible enough. If you don't do it properly, you can't render it on mobile properly and it just runs into a lot of issues. I think what we need is a more flexible platform that can actually give us that option, a second option or a main option, to move away from K2. We run into issues at times and it's mainly around the way we design applications and mainly around how we want to use applications. It restricts us in a very specific way to be able to fully utilize the capability. I think K2 is a bit far from being a perfect mobile development platform. We'd like to look at Microsoft as an option.

I've been using this solution for three years. 

Scalability is a kind of dependent thing. Essentially, it would require infrastructure and IT development to be able to do anything with the infra scalability or the platform scalability. We haven't tried it. We do know that when we want to sync up different environments, it's not that straightforward. I mean it's not complex, but it has a lot of activities. It's not a straight sync up between the two servers. You have to do a lot of tasks including download packages. It's a bit annoying because it takes up too much time from the ops team to be able to sync the two environments, especially when you're uploading packages that at times are not compatible. Again, it could be dependent on the way we've set it up on-prem. I don't necessarily know if that's a K2 issue or if it's an infra issue on our end, but assume it's likely both.

I haven't dealt with technical support because our ops team does that if they ever have to.

I'm a massive fan of K2 even though it's given me a bit of trouble in the past. Essentially, I think there are good features in there as well. It really comes down to your personal requirements, I believe. It's supposed to be a kind of designer-based application, work flow creation application or platform but I personally think that it takes a lot more technical ability to be able to design applications on K2. It requires more than somebody off the street, you need someone who can actually do a bit of design work and be able to spin up a really good application. It's not marketed properly, it's marketed as a designable application platform. But it's not necessarily, it requires a bit of programming knowledge.

The other thing I guess would be whether you want to pay for the licensing cost. There is a price for the K2 environment, does that suit you and your organization? That's something which you need to consider. Finally, K2 is also really hard to find, to be honest, and it comes at a premium so there's that maintenance cost as well or even development costs, which may be a lot higher than any other application that you may use. 

It's given us applications that are stable once you get it right. We haven't had many issues in terms of applications falling over or not responding, things like that. It can be a bit slow if it's database-intensive applications. Again, that could be a mixture of both infrastructure and also K2 application.

I would rate this solution a six out of 10. 

We use Nintex for processing workflows and forms for SharePoint 2010.  Moslty for approval workflows and tracking requests.

One of the processes that we developed was to allow requests for new login accounts. These require managerial as well as HR approval, then it sends workflows after the approval to a lot of different individuals as tasks for them to handle their part of the new user request.

Being able to simply create workflows to handle business processes. It allows us to route approvals to users without human intervention.

Nintex seems to be very server intensive. It is one of the reasons that we are moving to a different product on the SharePoint 2016 platform.

Our primary use for this solution is for automating workflows in business applications.

The most valuable feature is the workflows. We have started working with the SmartObjects and the SmartForms, as well.

The SmartForms need to be simplified so that the non-expert, business users can make use of them without coding. That will help a lot. 

I would also like to see the BPM features from Pega implemented, that have to do with the implementation of AI and the robotics.

The AI should be able to learn inside the platform so that it adds intelligence to the tool itself. That way, it can handle the things that are being taken care of by external entities. It will first learn how to handle new events, and then handle them by itself in the future.

I would rate the stability four and a half out of five. Overall it is good, but sometimes it fails.

This is a very easy solution to scale out.

We have approximately sixty thousand users for this solution. Perhaps one hundred of them support the applications and integration, but the majority of them are end-users.

Technical support for this solution is good. We have a contract with them and the support is good. They always help.

I have used Pega and I feel that it offers more than the K2 solution, in terms of the latest technology. For example, I like their implementation of the AI and the robotics inside of their system.

We are part of a technical team and we have the expertise, so the initial setup was not complex for us.

We had a consultant from K2 assist us with the setup.

This is a good solution and it is easy to implement. I think that it adds value to any organization, mainly in terms of business applications where you need workflows. It is easy to use, and workflow design can be done by business users. Overall, it is a good product to have in an organization.

I would rate this solution seven out of ten.