Nintex Process Platform Reviews

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. 

The main use case is accounts payable. We also implement it for human resources processes like onboarding and insurance plan changes.

The capacity to integrate with external platforms. It's great to be able to call web services or other external services.

There is room for improvement in the user experience in the forms. When we need to develop the forms, we don't have much customization, and I think we need more flexibility there.

It's technically difficult, but it would be great to be able to develop our own code and integrate it into the platform. We could then run our own code for specific actions and requests or even develop a page or form. So, if I can ask Nintex for something, it would be a way to integrate our own code for specific actions. 

When it comes to integration, it could have more options for custom requests.

We use Nintex Workflow Cloud. I have worked with the Nintex Process Platform for two to three years. 

I would rate the stability an eight out of ten. 

Scalability is a limitation of the product. It's not so easy to scale. I would give it a five out of ten. 

I'm an integrator for Nintex. So, the number of users depends on the customer. But we have thousands of users across all our customers.

So, it's suitable for enterprise-level companies. It's more suited for enterprise level, not for small or medium-sized businesses (SMBs). It's too expensive for the SMB market.

The quality needs improvement.

Neutral

I used Microsoft Power Platform.

Power Platform is better. It has more options and flexibility, even though it requires more technical skills to implement. 

Nintex is easier to implement and more user-friendly, but Power Platform can do a lot more.

The initial setup is simple. We have both hybrid and on-premises. We have all kinds of implementations.

Integration: For a technical person, it's quite simple. It could have more options for custom requests, but in general, it works fine.

The deployment process takes a couple of days.

Saving time is the biggest benefit. It gives the customers the flexibility to solve simple automation problems quickly. 

It saves time for both the employees and the company's administration.

I would rate the pricing for Nintex Process Platform as four out of ten; one is high, and ten is low.

It is pretty expensive.

I would recommend it for specific use cases. If it's something simple, I would recommend Nintex. 

For a large number of users, I recommend LeanIX. 

If it needs to be complex, I wouldn't recommend Nintex. I would recommend Power Platform instead.

Overall, I would rate it a six 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.

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.

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

The solution has the capability to handle robust execution.

The solution's flexibility can be improved. K2 needs to be fully code-free, and they should try Endeavor to make it code-free. It will help to hide the complexities of smart objects.

Improvements can be made because we are implementing one solution and need a solution that integrates into itself. It's very tedious to manage, so they should ensure that everything is integrated and taken care of.

We have been using K2 for three years.

The solution is scalable. Approximately 100 people use it in our organization.

The customer service and support team are good. The premium support is good, and their response is fast.

K2 is reasonably priced and you pay for licenses. It costs less than half a million, and you own your licenses yearly. Additionally, you pay 400,000 for support and maintenance, but similar tools charge per user. So you are paying roughly $80 per month for one user, which can be quite costly if you have a large organization.

We are currently evaluating Camunda and Integrify.

I rate the solution a six out of ten. K2 is not mature and still needs a lot of stabilization. My advice to new users considering the product will be to use it without customizing it. After installation, use the vanilla workflows, and you will get fast performance. However, if you customize it, you will run into challenges.

K2's best feature is that it can solve complex tasks, issues, and projects with little coding.

K2's support for DevOp team corporations is weak.

I've been using K2 for two and a half years.

K2 is very stable - there have been almost no problems in the time I've been using it.

The initial setup is straightforward because it can be deployed on a DB server, application server, and web server.

For the initial hundred users, the cost is $21,000 per year, which I find too high. There are soft thresholds for this initial license, like the number of forms and environments. 

I would give K2 a rating of seven out of ten.

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.