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