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.
Manager at a energy/utilities company with 10,001+ employees
Real User
Top 20
2023-09-08T05:53:28Z
Sep 8, 2023
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 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.
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.
Senior Sharepoint Developer at Zak Solutions for Computer Systems
Real User
2022-09-08T20:37:38Z
Sep 8, 2022
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.
Director of IT Operation at Credit Guarantee Company
Real User
2022-04-29T15:19:04Z
Apr 29, 2022
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.
Digital Solution Engineer at a tech services company with 1-10 employees
Real User
2021-05-11T20:42:07Z
May 11, 2021
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.
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.
Senior Manager - Reporting and Analytics at a financial services firm with 201-500 employees
Real User
2020-10-11T08:58:19Z
Oct 11, 2020
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.
Technical Architect at a manufacturing company with 1,001-5,000 employees
Real User
2019-05-16T16:17:00Z
May 16, 2019
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.
Nintex Process Platform automates processes such as approvals, vendor requests, and leave management, optimizing workflows in sectors like government, banking, and HR.
Nintex Process Platform streamlines collaboration and integrates seamlessly with Microsoft tools. It supports account management, loan origination, claims reimbursement, and public e-services, while also assisting with onboarding, resource management, and compliance workflows. Users benefit from its ease of maintenance,...
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.
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 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.
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.
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 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.
The solution is a bit too expensive. It could be cheaper.
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.
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.
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.
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.