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.

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.

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.

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.

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.

As a Solutions Architect my role is to help my clients implement tools and technology that can build and automate their businesses. While my clients and their environments very widely, Nintex delivers a product that can be used regardless of the industry, division, etc.

In most cases we help clients implement Nintex Workflow to automate business processes that can be tedious when done manually, such as information approvals, notifications, and integrations with other system/data.

The biggest improvement to the organizations that I work with is that it allows the users to reduce, if not eliminate completely, the amount of human interaction, for both complex as well as simple business processes. This allows the users more time to focus on aspects of their work that can have more impact on the longer term strategies of the business.

The Vizio-style designer that runs in the browser is, to me, by far the most valuable feature of the solution. It means that the customer doesn’t have to install any client tools to create powerful workflows.

Another feature that is very close in importance is that it leverages the out-of-the-box SharePoint back-end. This means that you don’t need to install or deploy additional infrastructure to support Nintex Workflow, unlike some of its competitors.

While Nintex Workflow has pretty robust troubleshooting abilities, I think that improving the default logging and notifications would be helpful. Many times we work with clients that have started a workflow, but find that it doesn’t work as they expect, and need assistance in troubleshooting and correcting any errors. That, and offering a licensing model that allows for multiple small workflows, would be a huge improvement to an already great platform.

I have used Nintex Workflow 2010 and Nintex Worflow 2013. I have not worked with a client that has the most recent version deployed.

Overall, I would rank Nintex Workflow at eight out of 10. It is a strong product and is definitely best in its class. It offers strong usability with the in-browser, Vizio-style designer, and can also deliver on some powerful workflow actions. There are times, when dealing with complex workflows, where understanding the application and its nuances is required.

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.

Our primary use for this solution is for automating workflows in business applications.

The most valuable feature is the workflows. We have started working with the SmartObjects and the SmartForms, as well.

The SmartForms need to be simplified so that the non-expert, business users can make use of them without coding. That will help a lot. 

I would also like to see the BPM features from Pega implemented, that have to do with the implementation of AI and the robotics.

The AI should be able to learn inside the platform so that it adds intelligence to the tool itself. That way, it can handle the things that are being taken care of by external entities. It will first learn how to handle new events, and then handle them by itself in the future.

I would rate the stability four and a half out of five. Overall it is good, but sometimes it fails.

This is a very easy solution to scale out.

We have approximately sixty thousand users for this solution. Perhaps one hundred of them support the applications and integration, but the majority of them are end-users.

Technical support for this solution is good. We have a contract with them and the support is good. They always help.

I have used Pega and I feel that it offers more than the K2 solution, in terms of the latest technology. For example, I like their implementation of the AI and the robotics inside of their system.

We are part of a technical team and we have the expertise, so the initial setup was not complex for us.

We had a consultant from K2 assist us with the setup.

This is a good solution and it is easy to implement. I think that it adds value to any organization, mainly in terms of business applications where you need workflows. It is easy to use, and workflow design can be done by business users. Overall, it is a good product to have in an organization.

I would rate this solution seven out of ten.