Nintex Process Platform Reviews

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.

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.

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 use it for SharePoint 2013 and 2010, and SharePoint Online (Office 365).

Able to automate business processes and help reduce a significant amount of development efforts.

• Workflow (escalation, reminder, LazyApproval, actions, etc.)
• Ease of use

Currently, copying workflow actions from one workflow to another is not possible. Also, the Office 365 solution is not as mature as on-premise.

It is very easy to use events. K2 has useful tools.

It didn't calculate the designs I needed. If a customer doesn't know what to do with the BPM tool, then they won't know how to start using the tool. It is very flexible because you can design your own main forms, but if there were some templates according to your market, it would be more useful for a new customer. That would make K2 more user-friendly and easier to use.

Perhaps they may add some different holdings, and if you carry a file which uses either shape, you can handle the document. That's not our preferred method to manage software. Perhaps they could add a simple archiving function in the software. That would be very useful.

We've had some problems but they solve them in a very timely manner, so even if it has a problem, they fix it. Problems are rare, but sometimes it stops and you have to check it. We didn't have too many problems but sometimes it stopped and didn't go forward. 

It is very easy to add users.

We have implemented K2 for two companies, but there are four or five companies using K2. There is a common problem right now in Turkey, so it is not easy to manage software installation.

Their technical support team is very fast. They make a remote connection and help us out.

We actually don't need this solution in our own company. We have a demo platform that we implement because we are developing software, so we don't need this solution. We use alternative management stuff.

The initial setup is very easy, it doesn't take too much effort to install if you know what to do. Setup time depends on what you do. For example, you can get up and running and make the system worthwhile within one week or it could last two or three months. This is a complicated question.

It is very flexible but that also means that it has too many tools. It is hard to stop. You can do whatever you want but this takes practice to understand how to use this solution best.

If you need to integrate into anything, K2 is very useful. I advise you to be organized from the outset, before starting the project. This is very important.

I would rate this solution an eight out of ten. We have examined too many workflows. Some are better, but this one is good enough.

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.

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.