Nintex Process Platform Reviews

We use K2 as a business process management tool in our company that is connected with our applications. Also, we are using an American-based workflow engine besides K2. We also use ELSA, an open-source platform.

Mainly, we use the tool for automation and workflow. So, we are using ASP.NET for development. Also, we are connected with K2 tool.

Our company needs K2 as an engine. We don't prefer to use the forms because the overall cost is high. Because of this, we have to go to workflowengine.io since it gives us the same results at very low prices. It's not restricted to processes or something like this.

AI is the most required functionality in tools nowadays in the market. The tool lacks to offer support for the Arabic language, and it needs consideration.

My company has been using K2 for two years.

It is not a stable solution.

It is not a scalable solution because of its high prices. We also need K2 engine for small businesses for 50k USD since small businesses are already using other tools for form building. We need something similar to a workflow engine. We use a Russian product offering good protection since it is a .NET-based workflow engine, and its server also can use any programming language. We turned to this tool owing to K2's high prices since, in the end, we ended up paying 300k USD. 100 to 5,000 users work on the solution.

The technical support is very good.

We had previously evaluated other workflow engines, a Russian product. We also used SharePoint Nintex. We switched to K2 since we use Visual Studio for the automation process and to develop our own portal using ASP.NET. So, we don't want more than the required license for forms and other components that we don't need or don't use.

The setup process was not too hard or difficult to understand. It was acceptable since there were no technical issues.

I have seen a return on investment using the solution. So, it is worth the money for its workflow engine and not the forms since I don't need them. Also, I developed the forms using a third-party application which was cheaper.

Prices for licenses of K2 are high. We bought a distributed license for 35k USD. Also, we pay an annual subscription of around 20k. Sometimes we try to lift K2 to higher prices. I need a license for SMBs and distributors, for which I pay around 50k USD. Also, I need a distributed license for our project.

I don't recommend others to start with K2 because of its high prices. There are other components that fit the needs of K2 that will not consider reducing their prices. I rate the overall product an eight out of ten.

It has a lot of features for creating and managing workflows, as well as for integrating with other applications. Nintex offers features, particularly to ensure a user-friendly experience.

At times, issues arise in certain scenarios. In such cases, the versioning can become quite difficult. There may be no other way but to restart the entire process or rectify it at that point.  

So, there is room for improvement in terms of the stability of this solution.

In future releases, Access-related features are important because a lot of data is stored in Excel in most organizations. So whenever we need to upload this data, we need to have workflow features that can validate each row and other data before inserting it into the software system. These features are not available in the standard version. We are not looking for a one-time import of data. Instead, we want to be able to process the data in real-time using DXL. This is one of the things we are looking for. 

The second is the ability to create Word reports. A report that is created in Microsoft Word.

This is a very common type of report, and it is used to present data in a clear and concise way. I would like to be able to create different types of word reports, such as listing reports and formatted reports. But Nintex does not provide any control over MS Word to control and format it. I would like to see MS-related connectivity with Nintex Workflow.

I have been using this solution for more than six years. However, we used the on-premise version, which had certain limitations in comparison with a cloud version. 

I am satisfied with the customer service and support.

Positive

We have worked with Nintex and SharePoint.

The solution is expensive compared to its competitors. 

We are actually in the process of evaluating low-code tools in this space. We are looking for a private cloud under the Azure cloud environment. 

The on-premise version of Nintex Workflow was good for the workload that we were using.

However, the trend has changed, and now all the features are available on the cloud, not on-premise. So we have to move to the cloud.

We are cost-sensitive, so we can't just move the tool to the cloud directly. We need to evaluate and understand our requirements first. And since we are in the pharma industry, we need to make sure that the software is compliant with Part 11 regulations. For Nintex and other products, we need to develop them with those features in mind. So, that's an additional layer of customization that is required for all these platforms. That's why we are looking for a ready-made product that is compliant with Part 11 and FDA regulations.

So it will be easier for us, and it will reduce the need for customization. So in that sense, we are basically evaluating the different options. It was never a key factor for us, but we are not happy with Nintex, so that's why we are not considering it. This is the product we have been using for the past 6-7 years, and it was one of the best ones because it integrated well with SharePoint. We hardly had to do any customizations in SharePoint because everything was created locally.

If I consider the standard version, I would rate it eight out of ten. However, the enterprise version has some additional features that I would like to use, but the cost in not so fair. So if I factor in the cost, I would rate it lower, maybe around seven out of ten.

Our searches are automated for the approval process, and we have automated our dual management process with K2.

We have 41 processes automated within K2.

It was only a process automation tool for workflows and approval, but now since being bought out by Nintex, we will have many other products available to use. For example, the RPA part of Nintex can plug into K2 and be used together.

The most valuable features of this solution are that it's no code, it's very flexible, and it's easy to design.

Currently, it's taking quite some time to deploy a package, it needs improvement. If they can simplify the deployment then it would be helpful. 

I would like to see a versioning tool included within K2 similar to Visual Studio to do your versioning of programs. It would be very useful and assist us a lot.

If they could also include an RPA as a tool, or integrate it with RPA products. It would be beneficial, as we wouldn't have to purchase anything else.

I have been using K2 for eight years.

We are using the latest version.

It's a stable solution. It is one of the features I like most.

It's a scalable product. We have approximately 4,000 AD users for this solution in our organization.

We have had no problems with the technical support at all.

Previously, we used Lotus Notes for workflows and approvals. 

The initial setup is very straightforward.

I have a development team of four people on safety.

There is an initial fee when purchasing and a fee for maintenance afterward.

It is not an expensive solution.

We have plans to continue using this solution and I would definitely recommend it.

I would rate K2 an eight out of ten.

We are currently using K2 Five classic. We have several use cases. The main use case is the vendor request. We process all requests that come in from existing or new vendors through K2. Our legal department uses it for checklists and other things. The approval process, onboarding, and all other related things are also done through K2. It is used for onboarding, termination, suspension, access, and many other things. All these things are automated.

It is for process automation, and it saves a lot of time and resources. Some of the things used to take weeks, and now they can be done in days and hours. Previously, we needed a spreadsheet, and now everything is done through a form. Everything is automatic, and eventually, the returns are pretty good.

The workflow engine of K2 is its main strength. Its workflow engine is probably one of the best, and that's the reason why Nintex bought K2. It can clearly handle any complex process or scenario.

K2 is almost low-code. It is a no-code or low-code solution. You don't have to read a whole lot of code. It is pretty much GUI based. Their support is also excellent.

The biggest advantage of K2 is SmartObjects, which allow you to separate the data from the application. It is a standalone application that allows you to build a data source from different places, which a lot of other applications also do. It is called SmartObjects technology, which is pretty powerful. If I have data from different applications, such as JD and ServiceNow, I can just create a SmartObject based on a data source and use it. I have some forms that have six, seven, or eight applications in a single form with data from different places.

K2 is a workflow solution, and there is no RPA solution with K2. This is where K2 lacks a little bit. It is just a heavy workflow solution. It doesn't have a supplemental product like RPA. If you want to use RPA, you have to use Blue Prism, UIPath, or something else. If you use Nintex, it has an RPA solution. 

It is a form-based application, and they are doing everything electronically. The initial investment in K2 is heavy because it is a BPM software. It does not have a low cost because they charge you the same for one workflow or 100 workflows.

I have been using this solution for seven years. I also used to work for K2.

It is used across the board. Almost everyone in the accounting department uses this solution. We also have a bunch of different legal departments, and they also use it. It is being used from the bottom to all the way up. When someone submits a request, it can go to the VP and all the way up. Because it is an approval process, it depends on how high it goes.

Their support is excellent.

The on-premises setup was fairly complex four years ago because we had to build the servers. You have to build test servers, staging and production environments, and all kinds of stuff. When you go for the cloud solution, you don't have to maintain any of those, which is why we are moving to the cloud solution. Our initial investment was quite a bit, and we're trying to move to the cloud solution.

The initial investment in K2 is heavy. Currently, the expenditure is $28,000 for a year. After we go to the cloud, it is going to be per seat and probably cheaper. Currently, there are unlimited users.

I would rate K2 an eight out of ten as a BPM solution. 

We use the solution for SharePoint on-prem and SharePoint online. The solution is deployed both on the cloud and on-prem.

The solution has helped us to automate our business processes, our approval systems, and automation for quickly developing on SharePoint on-prem and SharePoint online.

The Nintex Workflow's straight workflow and auto-response feature, along with its layer response functionality, make it easier for my end users to respond to emails. They can either opt for a date response or respond directly on our website without having to navigate to the initial screen. Overall, it is a straightforward and user-friendly process.

The cost of the solution is high and has room for improvement.

I wish to improve integration with additional Office 365 products. Nintex competes with Microsoft Power Automate, which is gaining market share due to its compatibility and ease of integration with both Microsoft and non-Microsoft operating systems.

I have been using the solution for 12 years.

The solution is stable.

The solution is scalable.

The technical support is good.

Positive

The initial setup is straightforward.

We have seen a return on investment with Nintex Workflow.

Nintex Workflow is more expensive than Microsoft's native products, but it is still considered moderately priced when compared to higher-end products such as K2.

I give the solution a nine out of ten.

We have around 2,000 current users and are expanding to 2,500 next year.

Although Nintex Workflow is a great product, we need to assess our capabilities before integrating it with a Microsoft application. It's worth noting that Microsoft's application is actually less expensive than Nintex Workflow. Nintex Workflow is at the top end of the price range.

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.

Nintex Process Platform’s most valuable feature is workflow. It is flexible and shares an update quickly. It is easy to maintain as well.

The product’s support for the mobile platform and its ability to handle artificial loads could be better. Its capabilities from the customer’s perspective need improvement. They should add repair and remediation features. 

We have been using Nintex Process Platform for more than five years.

It is a stable product.

It is a scalable product.

The initial process was easy for me to execute. However, it is complicated for those who don’t have any experience working on it. We deploy the product on the Windows servers. The deployment includes planning user access management.

The product’s price is competitive compared to other vendors.

Nintex Process Platform has a good workflow and efficient local support services. I recommend it to others and rate it a nine out of ten.

It is used to automate all business applications.

The solution is good.

There have been some glitches, and the workflow fails frequently. We had to upgrade to fix it. Even when there is a threshold limit with Sharepoint, it impacts the K2 level. The solution should be more developer-friendly because many steps are involved compared to Power Automate.

We have been using this solution for five years and are using version 5.2. It is deployed on-premises.

It is a stable solution.

It is a scalable solution. From an end-user perspective, we have close to 6000 employees. In addition, we have a third party who does maintenance.

We contacted the technical support team a couple of times last year. I rate the technical support a ten out of ten.

Positive

The setup is easy.

I rate this solution a nine out of ten. Regarding advice, from a business perspective, I would say assess the licensing cost before proceeding.