Nintex Process Platform Reviews

Our primary use for this solution is for automating workflows in business applications.

The most valuable feature is the workflows. We have started working with the SmartObjects and the SmartForms, as well.

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.

I would rate the stability four and a half out of five. Overall it is good, but sometimes it fails.

This is a very easy solution to scale out.

We have approximately sixty thousand users for this solution. Perhaps one hundred of them support the applications and integration, but the majority of them are end-users.

Technical support for this solution is good. We have a contract with them and the support is good. They always help.

I have used Pega and I feel that it offers more than the K2 solution, in terms of the latest technology. For example, I like their implementation of the AI and the robotics inside of their system.

We are part of a technical team and we have the expertise, so the initial setup was not complex for us.

We had a consultant from K2 assist us with the setup.

This is a good solution and it is easy to implement. I think that it adds value to any organization, mainly in terms of business applications where you need workflows. It is easy to use, and workflow design can be done by business users. Overall, it is a good product to have in an organization.

I would rate this solution seven out of ten.

In our company, we have different deals, each with a small number of workflow processes. They were primarily using email for approvals that followed. So, we replaced this with Nintex wherever possible. Through Nintex forms, we were able to customize these as well.  

It has helped us a lot, especially during the initial phase of a project where most of the things are done on paper. From our perspective, you can save at least thirty percent in terms of time spent on manual processes, and documenting approvals and process flows.

We are currently facing a lot of issues with Nintex, and we are trying to move away from this solution. In fact, we have already reduced its usage.

The feature that I found most valuable is the ability to impersonate the users so that high-level access to certain resources can be provided. For example, impersonating the super admin allows you to perform actions that cannot be performed by regular users, and they can be badged with this kind of action set. 

Another thing that I like is the deeper loops, and also deeper schedules so that you can schedule a particular workflow to a particular type.

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.

Initially, the product was very stable, but as our usage grew, the issues also increased. This may be a problem with our environment, but in any case, we are now at a point where we are trying to move away from Nintex.

I would rate the scalability a six out of ten.

We have approximately fifty thousand users, right from the VP to the workshop people.

I would rate their technical support a four out of ten. We never get the right solutions. Most of the time we get generic answers that are not to the point.

Nintex was chosen as the first option.

The initial setup was straightforward. During the trial, I had installed it myself. The installation was not a problem at any time.

The deployment and maintenance team is approximately four people. We have three environments, and four people handle the deployments and batch updates.

We have seen ROI.

We did evaluate other options, with one of them being K2. We had seen a few reviews and consulted with Microsoft as well. Based on everyone's answers we chose Nintex.

This is a good solution for mid-scale deployment and mid-scale usage, but as the usage increases, the issues along with it also increase.

I would rate this solution a seven out of ten.

We use Nintex for processing workflows and forms for SharePoint 2010.  Moslty for approval workflows and tracking requests.

One of the processes that we developed was to allow requests for new login accounts. These require managerial as well as HR approval, then it sends workflows after the approval to a lot of different individuals as tasks for them to handle their part of the new user request.

Being able to simply create workflows to handle business processes. It allows us to route approvals to users without human intervention.

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.

To automate paper processes or digital processes which are typically focused around capturing information from emails, approvals, and business documents.

We have been able to automate many different business processes for several different departments. Our solutions using Nintex has been most successful in automating HR processes because it allows you to easily and rapidly build solutions that conform to the unique business processes for each entity. Every department/company business model and structure is unique. This tool set makes it easy to integrate current processes and increase adoption rates and usage for the tool, as well as the process changes to update it on the fly.

• Lazy Approval (email-based approval)
• External system connectivity actions
• Delegation
• Rapid solution development

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

To automate a manual process through Nintex Workflow in a SharePoint environment.

It provides data accuracy with fewer failures. It saves time as tasks are automated.

This tool is really helpful in reducing a lot of manual work. Its drag and drop components help to create a workflow faster than SharePoint Workflow Designer.

• Scheduling a site workflow is much easier and more convenient. 
• I like the feature of getting an email for a workflow error, then I do not have to go through every instance. 
• Conditional start of the workflow is the highlight of Nintex Workflow. 
• Only Nintex has the feature which allows attachments to an email.

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

Our maintenance costs are reduced.

For the past three years, I have been using Nintex with SharePoint 2010 as well as the 2013 environment.

Automating business processes, such as employee annual reviews, new employee onboarding, and advanced approval processes. 

Approvals are completed faster now that they can be done via mobile, using LazyApproval.

• Allows us to provide desktop/laptop and mobile solutions to our users.
• Using workflow for simple approvals and LazyApproval; the feature is easy to implement for mobile approval.

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.

We use it for SharePoint 2013.

There has been no noticeable improvement.

I find it useful to utilize LDAP query action to find out the status of a particular user.

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

We use it for SharePoint 2013 and 2010, and SharePoint Online (Office 365).

Able to automate business processes and help reduce a significant amount of development efforts.

• Workflow (escalation, reminder, LazyApproval, actions, etc.)
• Ease of use

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