If you want to automate, you have to use Nintex
April 02, 2019

If you want to automate, you have to use Nintex

Francisco Falomir | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
Review Source

Software Version

Nintex Workflow for Sharepoint

Overall Satisfaction with Nintex Platform

We are using Nintex Platform to automate processes across the whole organization. It includes Safety & Environment, Management of Changes, Improvements Control, Production Events Notification, JRS, Product Liability and so on. In the beginning, the scope was the plant site, but now we are developing workflows and forms for Quality Assurance, Internal Audits, and several administration workflows. In the future, we'll expand to the RRHH area.
  • We are using Nintex for Sharepoint, but using SQL connectors you can easily connect with other sources, like AD, relational databases, and ERP. That way, you are able to integrate data with a structured workflow, that is the weakness of database based software
  • Nintex workflow & forms are relatively easy to use. Now we are three people developing, and only one is a programmer. Our dream is to expand the developing function to the key users, at least for developing simple workflows
  • DOC generator is one of the most powerful tools. It allows you to make a final document from the workflow. The key to digitalization is to understand the processes are not documents but that it is important to have a final report.
  • Forms: Some functionality about validation, or buttons need to be implemented using JAVASCRIPT. It would be welcomed to include more functions in this area.
  • Forms: The parent-child relationship is another area to improve. Repeating sections don't have the required performance to make a strong relationship between two or more tables (Sharepoint lists).
  • Workflow: Using an on-premise environment, there is not a good system to manage workflows: versions, insights, purge, etc.
  • It is very difficult to estimate the ROI in our case because we are automating processes, not for saving time or money, but for ensuring the repetitive reporting of the activity.
  • In any case, comparing the Nintex cost and performance, I think Nintex is not an expensive solution.
  • Anyway, talking about the new industry 4.0, the digitalization of processes is the starting point if you don't want to lose the boat.

We are using Nintex with Sharepoint on-premise. We are not in charge of Nintex deployment or upgrade. In our case, an expert consultant is in charge of the Nintex platform maintenance. As far as I know, it is not a hard task. I would like to comment that Nintex Community is a wonderful platform to share experiences and to solve technical doubts.

As commented, we are three developers from Process Control System, it's not IT but OT (Operation Technologies). Only one of us is a programmer. The final users are from any area of the organization. When the users have begun to use Nintex workflows, they have realized the performance and a lot of feedback is coming from them.

We selected Nintex Platform because we have experience with other products, and we were satisfied with their performance. The integration with SharePoint was a very strong point to help us to decide because we wanted to use SP as a document library.

Well-suited to automation processes (it does not matter what type or complexity), you can have feedback on their productivity and performance. Great connectivity between several data sources to feed the processes and store the results. In our case, the SharePoint integration is amazing, managing not only processes based on a list but in the document's life cycle. Less appropriate for cases where your processes are based on several data tables with relations. It is better to use a relational database, then use workflow with connectors when you need some workflow performance, user tasks, mailing and so on.

Nintex Process Platform Feature Ratings