Nintex Process Platform Reviews

Nintex creates forms and digital workflows to automate processes. There is a decision-making engine built using business rules. We specifically use this solution for remittance processes for a bank.

Before using Nintex, we had a manual process which started with sending an email. This process is now 50% automated. We upload a form to start the workflow and the process follows certain business rules. For example, if an amount of money is more than or less than a specific amount, the automation sends it to a specific department. 

This solution is very easy to use and customize, using almost zero coding. It's built on SharePoint which many companies in our country have experience with. This made it easy to adapt the application in our environment.

We would like to have access to an on-premises solution. In our country, we have a relationship with Central Bank of Egypt, which do noes not allow cloud solutions to be used. They should offer an on-premises solution with a flexible price license.

The knowledge base for this solution could be improved and expanded upon. Currently, it takes time to find the specific answers we are looking for. 

I have used this solution for one year. 

This is a stable solution with good performance. However, stability and performance is dependant on capacity planning before the implementation. 

This is a scalable solution, however, some features are not available on the on-premises solution. An external vendor's assistance is needed to overcome this. 

The customer support team could offer faster assistance. It would help if they had a local team in Egypt to assist.

Neutral

The initial setup was straightforward but the customization of the system was time consuming. We started with a POC, worked in a test environment to complete customization and integrate with our full system and then pushed this to production. This whole process took two years. 

We have been able to free up time for our team members to focus on other projects. 

This solution is affordable and is cheaper than most alternatives on the market. We have a standard cloud license that costs about 20k per year.

We evaluated Bizagi, Appian and Pega.

I would rate this solution a seven out of ten. 

There are a few workflows, including one of the recent workflows we failed to deliver for a client, Jazz, a telecom operating in Pakistan. They sought to automate their HR processes through a finance solution. As an example, we developed an insurance claim workflow for them. With approximately 10,000 employees within their territory in Pakistan, they aimed to streamline the insurance claim process.

For example, if someone lost their laptop. The normal process takes so much time, the manual effort, and the paperwork to get different information from peers. Our solution centralized the process, allowing the finance team to monitor the status of claims and their dependencies on external entities, such as vendors. We integrated a specific step within the workflow to track the progress of claims with the vendor. The workflow facilitated seamless communication with the vendor, providing updates on the status and estimated time. This data, combined with inputs from different department heads and finance, enabled a comprehensive evaluation of each request, leading to informed approvals or rejections based on predefined parameters. The workflow consisted of seven to eight steps, each incorporating approvals and developer oversight. This is a high-level overview of our engagement with Jazz for their workflow automation.

The drag-and-drop feature is quite interesting; it helps us a lot. We can manage different dates within a single workflow and identify the number of tasks we can dynamically dedicate to other users. Even if we assign a task to a single person at any point, we can change the delegation in the future or the responding entity at any time. Moreover, Nintex integrates with Microsoft ecosystems such as Office 365, MS SQL, and Azure. This makes it a strong candidate for anyone interested in Nintex.

We would appreciate introducing a dynamic hierarchy from a generic source or a custom HnM solution. We can assign tasks to individual users but must integrate with Active Directory, create a security group, or work within Active Directory. It is possible to integrate it so that we aren't dependent on Active Directory or any other HnM solution. We can create a list within Nintex's workflow and obtain the updated data from there. Alternatively, we could leverage integration with a customized HnM solution.

It also facilitates the end developers to determine if UI is much easier or more intuitive in terms of visualization perspective. For example, when building the solution, we had approximately seven to eight steps, and each step added multiple conditional criteria. Whenever we opened the editor with Nintex's editor, it took us about two to five minutes to load the whole development, and if we scrolled within the workflow, it also took time to load the data flow. If this loading and syncing could be improved, and the UI could support a lazy loading feature, that would be appreciated.

I have been using Nintex Workflow for two years.

I rate the solution’s stability an eight out of ten.

The scalability is dependent on SharePoint, which relies on Active Directory. If you have an Active Directory, it depends on the Windows operating system, specifically the Windows server. While it might be challenging to scale horizontally, we can undoubtedly scale it vertically by adding more RAM, CPU, and other resources. The scalability issue has become more apparent recently, especially considering the on-premises solution. However, the number of processes within Nintex plays a significant role. If only ten processes are in place, scalability shouldn't pose a considerable challenge. Understanding the level of processes running within Nintex is crucial for addressing these issues effectively.

We cater the solution to enterprise-level business.

I rate the solution's scalability a seven out of ten.

The technical support is good if you need to build something. The community is very active and helpful.

Neutral

The learning curve is different if you start working within Nintex. It takes some time to understand everything. But connecting other PCs to work with your processes is easier once you get through it.

The deployment doesn't take much time because we deploy it, make changes, and save it. We keep it for the later development cycle instead of redeploying it. We deploy the release once we finish the development, which takes a few minutes.

I rate Nintex's initial setup around seven to eight out of ten.

The solution is expensive and costs around 1000 dollars. I rate the solution’s pricing an eight out of ten, where one is cheap, and ten is costly.

If a community edition is available during the initial phase, we could use it to demonstrate the capabilities and set it up on the client's premises. Additionally, if we were to consider the cloud side, the accessibility of the cloud platform is currently limited. If such an option were available, it would be greatly appreciated.

Overall, I rate the solution an eight out of ten.

So we have a process flow for which we wanted to use Nintex Workflow. So in SharePoint currently, we have set up that Nintex Workflow. So users used to submit and raise requests in the solution, and that is used to trigger the automatic workflows on the fact that a ticket is raised. Then, the approvals are taken. So all those things we had coded in Nintex Workflow. So, the solution was for some kind of an approval process within our company because there are multiple stakeholders, so it goes to multiple stakeholders for approval, and they approve it. All that happens when working with Nintex Workflow.

Within Nintex Workflow, I think the automatic triggering of the multiple workflows and the setting up of the auto trigger of those workflows are some of the valuable features of the solution. So that is nice.

I think we could have more interfaces with other applications. So I think it was lacking a little bit in its multiple in-house processes and other processes. So there is a little bit of a gap in collaboration.

I have experience with Nintex Workflow. I have been using the solution for a year. I am a customer of the solution.

I rate the solution's stability a seven out of ten. Sometimes it breaks, and then we need to manually restart Nintex Workflow, so it had that kind of intermittent disturbances.

I rate the solution's scalability an eight out of ten. There weren't any scalability issues, really. I think that we found it to be a little bit of a scalable device, but we were not able to achieve it. So there were limitations. So, maybe on the SharePoint side, there would be a limitation that we can raise only these many requests, and the space is about to get full. So that kind of scalability issue, I can remember.

In my organization, around 1,000 users were using the solution.

I never contacted Nintex Workflow's support team.

I think the initial setup is fine.

To those planning to use it, I think it's a good tool to start with.

I rate the overall solution an eight 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. 

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.

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.

Primarily, the solution is used to manage business processes in an organization. It helps with fast app developments and approvals. 

K2 has a very wide collection of smart object technology. It's phenomenal. The concept of the smart objects is core to K2. 

The setup is easy.

The solution is stable.

It can scale well.

Support is helpful. 

I'm not up to date on recent upgrades. I've heard that in the latest technology, the solution is much faster, and the UI has improved. It used to be notoriously slow. 

I'm not sure if they have reusability yet. That's one thing I've always wanted - the reusability of the components. 

We'd like to have integration with SharePoint. 

I've used the solution for more than five years. 

The solution is stable. There are no bugs or glitches. It's reliable. It doesn't crash or freeze. 

It's scalable. It's able to expand easily. 

There aren't too many users using it in the company. We had maybe 1,000 users at one point. I'm not sure if this is still the case. 

We've used technical support. I've contacted them many times. They provide good solutions. We're happy with the support.

While I have used other solutions in the past, I'm not really an expert in others. 

They have a well-managed three-tier implementation. It's very straightforward.

There's an integrated tool used during the deployment, and the process only takes five to ten minutes. The deployment tool makes it very fast and easy. 

You just need a team of five, maximum, for deployment and maintenance. You might not necessarily need a dedicated person to handle the deployment. 

The deployment is basically done in-house. 

The solution used to be server-based. Now that it is on the cloud, the licensing is user-based. 

In terms of the market, K2 is not overly expensive. It's mid-range. 

While K2 is cloud-based now, many older customers use an on-premises version. 

This solution was acquired by Nintex.

I'd advise potential users if they have a legacy K2 system, to upgrade to the latest version of K2. They provide support and handle the migration of legacy K2 to the latest version. You get more features and advancements. 

I'd rate the solution eight out of ten.