We use Nintex to create and manage all the workflows associated with the data controlled by our clients. Now, with the web version, the costs have increased because, on-premises, you could create all the workflows you needed without having to track the number of active workflows and actions. However, now you have to manage all active workflows very seriously.
Pros
Manage Workflows.
Create Workflows.
Actions associated.
Cons
New actions in the box.
Drag & Drop of some actions.
Configurations
Likelihood to Recommend
When you need to manage different actions associated with some data (for example, flows to generate other actions or to generate other flows), Nintex Workflows is a great tool for making this. Other actions that are more complex are not suited to Nintex because you need to operate significant pieces of code to achieve your objective.
VU
Verified User
Manager in Information Technology (Utilities company, 5001-10,000 employees)
We use Nintex a lot to create "smart" forms and workflows. The combination of all the Nintex options in Workflows and Forms is very powerful and it saves us a lot of time and money. Tasks can be sent to employees and people outside of our organisation, this really saves us a lot of time, because we don't have to e-mail and do everything manually. Our main scope is automate (batch) processes as much as possible.
Pros
An Easy way to create "smart" forms
It's quite easy to create very powerful workflows
Easy to learn and good customer support
Cons
Would love a better overview of crashed workflows and options to revive them easier.
An option to sort rules in a Nintex forms, complex forms with lots of rules can be hard to administrate because it lacks this option.
Likelihood to Recommend
Easy to learn and manage and haven't had really big problems with it. Would love to see some more updates and new features on the O365 platform. Recently their weir quite a few of problems because of Microsoft "cloud updates", they should manage that better to prevent problems for their users.
VU
Verified User
Professional in Information Technology (Utilities company, 5001-10,000 employees)
We use the Nintex Process Platform for several business units in our company. Sharing documentation with specific metadata with external partners such as contractors and asset owners is done with workflows. Another example is the processing of data from field engineers which is needed to process in our geographical information system. An engineer has done some adjustments to one or more assets. Then the data is sent to a back office to process the data in other backend applications.
Pros
Drag and drop of elements in the GUI
Good information is supplied trough the help function
Good platform where the community can provide questions and feedback
Cons
More detailed event logging when something has gone bad in a workflow
It looks like the focus is on the cloud platform instead of SharePoint
document creation is expensive
Likelihood to Recommend
Nintex is very good in automate manual actions in SharePoint Online with documents and/or list items. Especially in combination with the use of Nintex Forms. For example, start a workflow when a user has submitted a document with a specific option enabled which will inform other users and send the document to different stakeholders. Another example is the way that approval workflows work and can easily be adjusted to the needs of the customer. If you want to build a whole new application (with custom actions) then Nintex is not the tool you need.
Nintex Process Platform is being used across the organization as a document generation platform for sales contracts in conjunction with DocuSign. It addresses the need for a seamless system that allows us to automatically generate documents that can be sent to our customers upon completion of an order being placed.
Pros
Integration with Salesforce
Customizability
Robust function
Cons
Larger Community
Ease of Use
UX Aesthetics
Likelihood to Recommend
I believe that Nintex Process Platform is well suited to a use case where those who are implementing it are fairly tech and software savvy. The platform is fairly robust and can be customized to a significant degree, but it does take some time to familiarize oneself with it fully. I would say that where it is less appropriate is for users who are not power users and would struggle with customizing the system to adapt to their needs. Such users would likely struggle with the UX and become frustrated.
We use it as an approval solution to improve our workflows and business-related processes. The approval of mandatory HR processes are rebuilt without any paper usage in the Nintex workflow engine. The Nintex forms that we are using are already checking for the needed information. Also, the connection with SAP is improving these processes.
Pros
User handling
Solution providing
Cons
On premise behind cloud
Special points in user handling UI
Likelihood to Recommend
Well suited:
Process and approval digitalization, user handling, and workflow optimization like HR processes or rebuild automation for the approval matrix.
It's well implemented in the system architecture with Microsoft products.
Less suited:
Some parts that are useful are not implemented in the on-prem version of Nintex. What is in some parts is making life a little bit difficult because user finds the solution in the cloud version and wishes that it was also possible in the on-prem version.
Some technical scenarios are not possible. For example, ADFS or something similar, but that's not directly a problem from Nintex itself. This is a mix from Microsoft and the engine.
Nintext can be leveraged across the entire organization as a productivity enhancement tool to create workflows. The tool is given to the Lines of Business to self administer. The problem it resolved was how LOBs can create simple workflow programs by themselves.
Pros
It's simple to install and sustain on the SharePoint platform.
The workflows are simple to document and follow once created. Users can just follow the start trigger to the end.
It's priced well compared to enterprise tools.
Cons
End-users can create triggers that create endless triggers so it is powerful, but we would like the ability to limit the number of triggers if coded wrong.
Likelihood to Recommend
It can easily support business workflows and be managed by the LOBs with limited tech experience. At the same time, a tech-savvy person could create a robust complex workflow.
VU
Verified User
Employee in Information Technology (Utilities company, 5001-10,000 employees)
