Nintex Process Platform

It has become integral to several key business processes

We are currently investigating which collaboration platform best suits our needs. Chances are that we move to SharePoint Online and then we're going to also consider the microsoft power platform (power automate and power apps) to develop forms and workflows. Aspecially the pricing model for the cloud is currently a blocking factor to go for the Nintex solution in the Cloud.

Nintex runs in such manner that it needs "push" to keep and resolve failed workflows. We found regular failures in cases of concurrent use of the workflows by multiple persons might end up with obscure failures like "enumeration has been modified" etc.Further, the default approval forms are really a drag, take ages to load, so we had to replace them all together with javascript based solutions (which defeats the purpose of the nintex in the first place).

This works best for our kind of requirements and environment. The usability is very simple and results are powerful.

Although the tool is very good and easy to use, we have little content on the internet, we have little tutorial, the discussion forum is very little seen and used. It would be ideal to have more sources of information from people asking questions on forums and on youtube and other social media.

I use the Nintex Process Platform, encourage others to use it, and know that a non-insignificant level of functionality would be lost if the license was not renewed. There are more complicated and labor-intensive ways of simulating the work that N.P.P. does currently, but why would any company want the more complicated, labor-intensive option?

Unfortunately, we will not be using Nintex going forward because the experience in on-prem Nintex and SharePoint 2016 is not replicable in Office 365 / SharePoint online. Also, the licensing model is different and would not be cost-effective to scale in the new environment with a lower-functioning version of Nintex (Nintex online is not as robust and user-friendly as the on-prem version). Our parent company assesses capability, licensing models, cost, and security to weigh in on whether a tool can exist in our portfolio. While on-prem Nintex was a great solution for our business when connected to SharePoint 2016, the online version that connects to SharePoint online is feature-weak, in development, and does not march capability forward for us in a meaningful way. The parent operating company has opted to go with Microsoft Flow instead.

The primary influence is overall IT budget and overall direction by IT Management.

We use Nintex workflow everyday. If it's not designing a new workflow, it is definitely running some internal workflow already.

The biggest reason to renew is because of the sunk cost of all of the existing workflows that we have built. We would have to rebuild all of the workflows in SharePoint designer and/or have reduced functionality because of the things we are doing with Nintex that are not possible out of the box with Designer.

We are very pleased with the capabilities and reliability of Nintex Workflows and felt we have achieved a significant amount of ROI.

Nintex Forms is very easy to work with and makes developing easy to push out to end users.

Renewal is mainly on the fact that Nintex is so widely used and it would be impossible to migrate all of these existing workflows to another engine. Third-party lock-in within SharePoint is pretty strong, which makes it difficult to move to something else. Our Nintex database is well-over 100 GBs.

Nintex email support is very good, and I've been impressed. The Community however is non-existent and filled with unanswered questions.

Nintex has been used within the company for over 5 years. Many hours of training and collaborating have been invested into the product. User adoption is at a significant usage level to justify the current product renewal.

I don't work in the business apps department anymore but from everything I've seen after working with Nintex, I would highly recommend it.

We have a lot of dependencies on this product and will renew because of its ease of use and how pervasive its use is inside our environment.

I have since moved on to a new position that does not currently have Nintex. Part of my roadmap is to purchase Nintex for the new organization that I work for. I work in a different industry now, but there are many areas that Nintex can help to increase productivity.

Once users have started using Nintex Workflow, they've learned how easy it is to develop custom workflows. Once users are familiar and happy with a product, it typically best to stick with it.

Nintex is complete and easy to use, and the cost is fair for such a great tool.