Nintex Process Platform Reviews

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

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 it for internal process automation.

The solution helped us automate several processes we used to do manually.

It supports SharePoint in the platform, and it's easy to customize to the maximum extent.

The integration could be improved, and we are looking for a solution on Office 365, not on-premise SharePoint. In addition, we cannot use the same solution on cloud, and we have to purchase it all over again to get it on cloud.

We have been using this solution for three years. We have a perpetual version, so we stopped renewing it last year. It is deployed on-premises on Sharepoint.

The initial setup is straightforward.

I rate this solution a seven out of ten because of its limitations.

One use of the solution is for the leave request process end to end. Someone submits a request, there is verification, and then depending on the answer of the monitor of the human resources, a document is generated for a digital signature where the item is stored in SharePoint. 

The SharePoint feature is a really good connection, there are many features that are good. 

The interface could be better and more language support is needed in the development environment or in the solutions platform in general. Here in Algeria, we have clients wanting the solution to be in French instead of English.

In the future, I think it would be a benefit for the company to have a larger social media presence. This way more people would know about the solution and its benefits.

I have been using this solution for approximately one year.

The solution is stable. For what I use it for, I have not had any problems or encountered any errors.

We have two people using the solution in my company. We are building demos to show potential clients.

The technical support is very good.

I used previously K2, then after Nintex bought K2, we are now using them both. 

The main difference is K2 is used for complex and deep processes. While this solution is used for simple to moderately complicated processes.

In the initial setup, I found there to be too much compromise in the cloud version. The cloud version is deployed in any environment with no problem. We did not install an optimized version for now, but I think it is not going to be complicated because it is on serval different SharePoints.

We did the implementation ourselves and it took one week to do. The maintenance of the solution is done by Nintex on their end.

The price of this solution is affordable but the problem in Algeria is our community is a bit slower. The new clients might feel the solution is a bit expensive.

I have evaluated Kudzu and SAP CRMs previously. They both have CRM connections which are good.

I would recommend this solution to others.

I rate Nintex Workflow a nine out of ten.

I primarily use the solution as a development platform.

The solution in general is very easy to use. It's very user-friendly, and it has satisfied the requirements I have. 

It's a really good platform. 

The integration capabilities have been very useful. It's very powerful and very advanced.

The stability of the product is quite good.

The Workflow Designer needs improvement. For example, when you design a workflow on K2, it shows the entire area between one action and another action. However, you should be able to see the structure for this action. It's not automatically structured.

It sould be automatically structured from the shared action to the following action. In K2, you should be able to organize it by yourself. Workflows should be very easy to organize exactly as you need them. It shouldn't be inflexible. The mapping processes need to be better.

You can't really change the look and feel. You should be able to customize the solution a bit more.

The document generation, the dynamic document generation, could be a great addition as a feature.

I've only been using the solution for six months. It hasn't been that long just yet, however, I am enjoying the product.

The stability is very good. There are no bugs or glitches. It doesn't crash or freeze. It's reliable.

The product doesn't seem to have many limitations. It can likely scale well. 

There's no need for technical support as we order services done for us. As far as it's from K2 goes, there's a web solution on the platform and there are partners for the company. Up until this point, however, I haven't found the need to reach out. I haven't had problems that required assistance.

I worked with Nintex for a few years. Recently, after I ran a comparison between K2 and Nintex, I've been working for six months on the K2 platform. I've found it very useful, and very easy in comparison. However, I still use both. Nintex acquired K2 recently.

Compared to Nintex, Nintex is easier to set up. Unlike in K2, in Nintex, you can just build on top of SharePoint. If you want SharePoint, the environment is set up and can install directly in Nintex. In K2, you are configuring two environments. 

I am unsure of the exact pricing. Nintex acquired K2 in 2020 and there may be a shift in the cost structure. I can't speak directly to that, however.

We are a K2 customer and a Nintex partner, although, since the 2020 acquisition, they are the same company now.

I would recommend the solution, especially for companies that are working to go paperless.

I suggest that if they want to integrate between systems from a strategy department into another department, to really look at the integration layers that they have, as it's very advanced.

In general, I would rate this solution at a nine out of ten. We've been largely happy with the product.

We have implemented an end-to-end workflow solution for a private bank for their loan origination system. We have also implemented a claims reimbursement system, and item-level permissions for SharePoint lists using Nintex workflows.

For end-to-end approval workflows, Nintex workflows are deployed on the SharePoint front-end servers. The claims reimbursement workflows are end-to-end workflows for approvals of claims within the organization. Those for financial services include loan origination, legal and compliance, and core banking system workflows.

Resource management and employee onboarding workflows have also been created to automate the employee onboarding process.

From what was a 20 to 30-day approval cycle, it has now come down to between two and three days for approving loans and claims.

SharePoint does not support item-level/row-level permissions, and we were able to implement the solution using Nintex workflows.

The product and its features have improved the productivity and efficiency of the process flow within the application and systems, providing end-to-end connectivity to all systems.

Tracking of all approvals minutely, audit logs for issues, and helping to find out any non-compliance in the process flows.

State machine and sequential Workflows are excellent features for creating complex state machine and sequential workflows that integrate with major Microsoft products like CRM Dynamics, SAP, and Peoplesoft.

We can create workflows for document management, publishing workflows, and create other custom workflow solutions spanning multiple roles and levels of approvals.

It has integration with BI and Analytics tools, and RPA toolsets as well. 

Custom integration using REST APIs for Line of Business applications is helpful.

It provides good audit and reporting for workflow tasks to detect and resolve issues.

We had issues with long-running workflows for approval processes. While the workflows are waiting for the action to be taken by the approvers, sometimes the approval takes time and workflows do not respond to the actions after a certain number of days.

We would like to design parallel workflows and long-running workflows, along with new features for connecting to cloud-based systems.

When the workflow tasks increase in number, there are issues with performance that need to be addressed.

We have been using the Nintex workflow solution for close to eight years.

The Nintex solution is stable for small to medium workflows and even, to an extent, large workflows.

The Nintex solution can scale from a single server to multiple server deployments to manage workloads.

Good customer support in terms of help desk, and support for fixing product issues.

The initial setup was straightforward, with appropriate demos, documentation, and user manuals.

Implementing the workflows as a development vendor for a major financial services organization, real estate firms, and insurance companies.

Looking at the capabilities and usage for all process flows to be automated within multiple systems and applications throughout the enterprise, the ROI will be met and break-even reached within a year.

We are using Nintex Workflow for internal reviews between banking groups, and automating the workflow.

Integrating with work services is required, and it's an area that needs improvement.

Stability needs improvement.

From a monitoring point of view, and alerting should be improved.

We have been using Nintex Workflow for almost four years.

Unfortunately, Nintex Workflow is not that stable. We are looking at shifting to another tool.

We have over 200 users in our organization.

We have technical support available to us, but we have not utilized often, our resources are capable of addressing all of our technical issues.

Previously, we did not use another solution, it was our first test workflow system.

With the initial setup, most of the cases are straightforward.

The deployment and implementation are done ourselves.

Comparatively, it's expensive.

We are planning to decommission this product for use and we are still exploring other products.

I would recommend some other tools rather than this.

I would rate Nintex Workflow a seven out of ten.

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.