Nintex Process Platform Reviews

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 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.

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.

1. SmartObject makes the center of data management, where developer and/or someone can call to it with only one place. SmartObject will return data from other system (such as MS-SQL, Oracle, SharePoint, SAP, etc.) to solve requirements.

2. K2 connect for SAP, easy to make interface between SAP with K2 connect for SAP service designer. Developer can design interface without coding and transform it into SmartObjects.

3. Workflow, to support more complex business processes, logic and data flow without coding.

4. SmartForm, fast and easy to develop web form to connect to SmartObject and workflow. Where you can create web application and ready to release to users within an hour.

• Supports conditional approval by business logic very easily
• Multiple approvals
• Notice of approval by email

Performance. Some customers ask why K2 is slow? Upgrade to current version will get the better performance.

More than 7 years.

Easy to makes deployment package.

Found less in the current version.

No.

Eight out of 10.

Eight out of 10.

K2 is my first and only one solution that I recommend.

Setup is easy in standalone. Distributed setup is complex and requires more network knowledge.

I’m working in the development field and do not know much about this.

No, my team was trying to map requirements to the K2 solution.

K2 makes your work simple.

The solution has the capability to handle robust execution.

The solution's flexibility can be improved. K2 needs to be fully code-free, and they should try Endeavor to make it code-free. It will help to hide the complexities of smart objects.

Improvements can be made because we are implementing one solution and need a solution that integrates into itself. It's very tedious to manage, so they should ensure that everything is integrated and taken care of.

We have been using K2 for three years.

The solution is scalable. Approximately 100 people use it in our organization.

The customer service and support team are good. The premium support is good, and their response is fast.

K2 is reasonably priced and you pay for licenses. It costs less than half a million, and you own your licenses yearly. Additionally, you pay 400,000 for support and maintenance, but similar tools charge per user. So you are paying roughly $80 per month for one user, which can be quite costly if you have a large organization.

We are currently evaluating Camunda and Integrify.

I rate the solution a six out of ten. K2 is not mature and still needs a lot of stabilization. My advice to new users considering the product will be to use it without customizing it. After installation, use the vanilla workflows, and you will get fast performance. However, if you customize it, you will run into challenges.

To automate a manual process through Nintex Workflow in a SharePoint environment.

It provides data accuracy with fewer failures. It saves time as tasks are automated.

This tool is really helpful in reducing a lot of manual work. Its drag and drop components help to create a workflow faster than SharePoint Workflow Designer.

• Scheduling a site workflow is much easier and more convenient. 
• I like the feature of getting an email for a workflow error, then I do not have to go through every instance. 
• Conditional start of the workflow is the highlight of Nintex Workflow. 
• Only Nintex has the feature which allows attachments to an email.

Converting a document from PDF to MS Word, or vice versa, needs to be improved.

Our maintenance costs are reduced.

For the past three years, I have been using Nintex with SharePoint 2010 as well as the 2013 environment.

We primarily use the solution for government and public e-services. We always deal with K2 in these areas. We use the solution to mostly deal with workflows.

The design and the vision the solution allows for is great. 

It's gotten better with time. version 4.6, for example, wasn't the best but 5.4 and 5.6 continue to be a bit fancier and offer up a bit more. The improvements are great.

The enhancements, overall, are great. It's so easy to use compared to the competition. Its enhanced usability makes it the best of the lot.

We are able to use K2 to manage as our environment and have everything deployed to the servers.

The performance of the product is excellent.

The solution offers very good integration capabilities. We've never had issues integrating it without solutions.

Even though the performance is better than the competition, it needs to be enhanced and improved upon. They could always refine this a bit more.

The licensing needs to be improved. Right now, we find it's getting more expensive to use the product.

The K2 platform could be enhanced.

We have approximately six years of experience working with this solution. It's probably been a bit more than that, actually.

You can definitely scale the solution. K2 has a feature that allows it to go with other solutions quite well. It's the best option for companies that need a solution that can scale due to the fact that it can integrate with many systems.

We've dealt with customer service in the past and they were satisfactory. They are very good and very easy to work with. We haven't had any trouble in that regard.

Largely, the initial setup is straightforward. It's not too complex.

The deployment of the product takes two or three days. In terms of the workflow, it can be implemented in about one week. Overall, you can go live within two or three weeks.

The licensing is quite extensive. I cannot speak to whether it is cheaper or more expensive, however, the licensing model needs to be reimagined and revised. Overall, I've found that they've become more expensive over time.

We have a partnership with K2.

All in all, I'd recommend the product to other organizations.

I'd rate the solution eight out of ten. If the pricing was better, I'd probably rate it higher, however, their licensing model has changed and things are more expensive than they used to be.

Our use case of the solution is to help the sales people in the field, enable them to have all the information from the backend and to more easily put together a proposal for management regarding new tenants of shopping centers. There is a process that flows to the works department, the legal department, the asset manager, and the project manager. They are able to make suggestions, comment, discuss numbers, and make some declarations. It provides good feedback to the management who then need to make a decision. We provide this service for both internal and external clients. We're a customer of K2blackpearl and I'm the company chief information officer. 

The value of this solution is that it's easy to maintain, and to further develop. It's quite low code, so there is not the need of really specialized people and customization is quite simple. 

I think there can be improvements in the product but that may be linked to the decisions that we have taken to put it on-premise, because now we're making big changes and the scope of the project has changed so that we now want external partners to have access to the system. Because we're on-premise, it's more complicated to provide access to their own network. Next time I would go for the cloud. 

I've been using this solution for about three years now. 

Stability is good, no issue there.

Scalability is good. We implemented it in Belgium and then in France and we're now expanding the scope further.  

We haven't needed to contact technical support as we work directly with the integrator. 

I believe the initial deployment took about three months. We used an integrator to help with that and it was successful. They provided some training for us so we'd be able to figure out how to do things ourselves. It was great. 

I would suggest to anyone wanting to deploy this solution to find a good integrator that understands the business first, not only from the technical side. Don't hesitate to take the journey. I would also suggest starting with a small solution and then expand it. Like everything, do a minimum viable product and then extend it a bit more slowly and grow into it.  

I would rate this solution an eight out of 10.