Nintex is still at the starting point of integrating with AI. It has integrated with a very small piece of artificial intelligence., like only integrated with the Google Cloud.

There is a benefit, like a no-code and low-code solution. But, again, if you are a developer, especially if you are a hardcore developer, you are using your code knowledge, its skills, and all. And, suddenly, you are moving into the low-code solution, and then you will feel, like, so many things you can't achieve with the low-code solution. 

And in that case, you are looking for some custom development. And it's a little bit difficult in the Nintex area. Because they are totally dependent on the low-code solution, and you are looking at where you can implement your custom things. 

However, you can do that thing, but that will be a difficult task. Also, the outcome, whatever you are trying to get from such kind of custom development, will be a little bit difficult.

Let's suppose, like, if you are working with a medium level of data or a small level of data that will be easier to handle with the Nintex. However, the bulk data on a high level of data would be difficult.

I have been working with Nintex for the past three years. I've been able to create some really good products in different domains, including banking and insurance. Everything seems achievable, but there are a few things I'm missing. 

First, debugging can be a bit difficult in Nintex. You can't debug forms and workflows easily. This is something that could be improved in future releases. It requires some R&D. 

Second, I would like to see more integration with AI. There is some custom integration available through the gateway, but it would be great to have more AI-related features built into the platform.  

There are a lot of apps in K2, but what I really found that needs improvement is the management section of K2, especially the management server and the admin page where you can manage processes, add users, set security fees, and add licenses.

The reason for this is because the part that is the section of administration, particularly the management called rows, has multiple rules, as many as you want. For instance, you may have around 200 rules, and when you view them, only the first ten are displayed, and you have to click next to see the next ten and so on until you get to the hundredth rule.

On that page, as of today, we only have what we call to fetch, where you can search for a particular rule you're looking for, or else you have to keep clicking until you get to the final page you want. So that's a bit challenging. 

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.

We want to upgrade our system. We need to develop more things and need the latest K2 tool to do that. The model we have is out of date. We need to move to K2 Five.

Our version is very old and we do not have support from K2 at this time. 

There are some glitches happening as we consider moving to K2 Five.

The solution needs more RPA and AI features. 

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. 

The solution does not integrate with many platforms.

Currently, a notable challenge lies in the alignment of user experiences across the eight or nine applications within the suite. Transitioning between applications can be somewhat cumbersome due to varying user interfaces. However, the provider is actively addressing this concern by consistently rolling out updates every four to five months, aimed at harmonizing and streamlining the interfaces. This ongoing effort is expected to enhance the user experience over time.

In terms of functionality and features, the platform stands out, offering flexibility with the option for both on-premises and cloud deployment. This flexibility extends to the RPA tool, providing clients with choices tailored to their preferences. 

An advantage lies in the shared security and data infrastructure across the toolset, facilitating smooth data transfer between applications. This contrasts with experiences with Oracle, where data transfer may involve complexities such as the need for intermediary file formats like TXL or SCZ.

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.

AI is the most required functionality in tools nowadays in the market. The tool lacks to offer support for the Arabic language, and it needs consideration.

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.

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.

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.

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.

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.

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. 

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.

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.

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. 

The solution is a bit too expensive. It could be cheaper.

• Built-in reporting on-prem is limited and clunky at best.
• Integration can be fairly technical, and often business rules inhibit product capabilities or force a developer to consider alternate methods for integration.
• Hawkeye is emerging as a reporting solution, but as a V1 product it’s not very useful yet.

K2's support for DevOp team corporations is weak.

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.

Nintex seems to be very server intensive. It is one of the reasons that we are moving to a different product on the SharePoint 2016 platform.

The timer jobs that we have would never run on time.

If you have a complex workflow, Nintex would just error out of it, without giving a "why" and "where". Error reporting is something that definitely needs improvement because most of the time it would just give a correlation ID or something. If there is a workflow issue then we don't know where it failed.

The Nintext Pause operation causes problems and so do the parallel use cases, so these also need improvement.

In the next version of the software, I would like to see a dashboard of all reports, the workflows that are running and their statuses. That would be helpful.

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.

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.

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 think there can be improvements in the product but that may be linked to the decisions that we have taken to put it on-premise, because now we're making big changes and the scope of the project has changed so that we now want external partners to have access to the system. Because we're on-premise, it's more complicated to provide access to their own network. Next time I would go for the cloud. 

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.

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

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.

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.

Performance. Some customers ask why K2 is slow? Upgrade to current version will get the better performance.

Converting a document from PDF to MS Word, or vice versa, needs to be improved.

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.

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.

The Management console needs to improve because sometimes it is too difficult to manage the workflow instances.

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.

The security features for this solution need to be improved.

The only complaint from our client is about the annual cost of licensing and support.

Bring all features available from the on-premise product into the cloud version and the workflow error reporting.

User interface could use some improvement. Perhaps integration with Visual Studio or SharePoint Designer would be useful.

NWC forms could be better.

The ability to build workflows that are not dependent on SharePoint is very desirable. The forms feature just isn’t as functional as the forms for SharePoint.