Nintex - It Works!!https://www.trustradius.com/business-process-management-bpmNintex PlatformUnspecified8.21661012015-09-18T17:51:56.485Z
September 18, 2015
Nintex - It Works!!
Score 9 out of 101
Nintex Workflow for Sharepoint
Overall Satisfaction with Nintex Workflow
We use Nintex Workflow across the organization as a tool to automate many of our business processes that were either manual, were once automated by systems that are now decommissioned at the company, and/or new process altogether. Not only do we use Nintex Workflow for automation of processes, it also helps to solve simple to moderate problems that would otherwise require some level of coding thereby simplifying our SharePoint environment.
- Document Approvals: Nintex Workflow makes it easy to gain approval for documentation that has been submitted via a document library in SharePoint. It has the ability to handle simple approval processes but can also powerhouse through more complex approval processes as well.
- Notifications: I think this one is worth mentioning although it is simple. Nintex Workflow has the ability to provide a more custom feel for notification than out of the box (OOTB) SharePoint notifications. It has the ability to include information from multiple lists in a site collection and it has the ability to create complex HTML to have a more custom email.
- Data Processing: I use Nintex Workflow at times for simple data processing: For example, I recently used Nintex Workflow with a SharePoint calendar to create a reservation system. Nintex Workflow plays a key role in the calculation of available time slots and other features in the reservation system.
- Images in notification are not impossible to accomplish, but because Nintex Workflow (and/or SharePoint) truncates the url for relativity purposes makes it difficult to just add the location of the image to the source editor.
- Nintex Workflows in my experience do not behave consistently with SharePoint document libraries that require more metadata around a document to entered. The workflow in some instances start once the metadata information have been entered (which is what I expect) and at other times start once the document has been uploaded and prior to entering the metadata.
- Nintex Workflow conditional start is not always consistent. There have been some instance where I have had a workflow set to start on a condition and when the condition was met the workflow failed to start.
- Error messages from Nintex Workflow failures are at times vague which makes it difficult to troubleshoot quickly especially in more complex workflows.
- Most certainly it has positive impact in the area of automation of group processes.
- It also has allowed my group in particular to increase our ability for customer service to the business.
- Nintex Workflow, if used incorrectly can significantly effect the SharePoint environments speed.
The only other product that I have used is the SharePoint out of the box workflows and Nintex Workflow is leaps and bounds over that.
I have found Nintex Workflow to be a powerful tool that helps with many of our solutions. Nintex Workflow is well suited for simple to medium complexity solutions or as an addition for complex solutions. It works well for intergroup processes like request processes, documentation approval, etc. It also helps with some simple data processing as well. It doesn't do complex calculation well and tends to fail when the process has a severe level of complexity.