Our organization uses Nintex Workflows for document management, task assignment, coordination, accountability, continuity and to ensure the end product is delivered to the customer.
It is being used by the program I work for with a government customer.
- Unlike SharePoint Designer WorkFlows, I enjoy the ease of use with Nintex WorkFlow drag & drop actions and how easy it is to configure them with SharePoint artifacts.
- Errors are not as difficulty to address after trial and error. I have encountered errors in SharePoint Designer WorkFlows. Based on my experience, Nintex WorkFlows are lot easier to work with and troubleshoot.
- The multitude of actions, that can be configured to create various Nintex WorkFlows, are endless. These actions can be mixed and matched to meet your customer requirements.
- Use of use with CSS and customizations.
- Though Nintex WorkFlows are great for administrators, they are not designed for developers who have to utilize workarounds in order to accomplish simple actions.
- For SharePoint migrations from 2010 to 2013, it appears that Nintex may not issue migration licenses as quickly as your customer may expect.
- Nintex is not a cheap product to purchase. Customers must assess their needs, requirements and budget before investing in Nintex licenses.
- The graphical interface for producing the workflows make the process very easy to understand and to implement.
- There is a lot of built in functionality that just doesn't exist in the standard SP workflows like Loops and FOR/NEXT, and accessing other sites within a workflow.
- The support is very good and the suite of tools from workflows to form building and mobile phone support allows great development of large applications.
- Trouble shooting remains a difficult task. It would be helpful if there were a manual dedicated solely to building trouble shooting actions and processes for Nintex.
- This may be my lack of investigation but to learn how to build forms or build mobile solutions it would also be good to have access to in-depth training videos.
- I also think there should be a better way to search a design workflow to find references to fields or variables. This would allow a quicker way to find areas of a workflow that deals with these fields or vars.
Nintex Workflow for SharePoint is being used extensively by various projects at SPAWAR and US Navy.
Most workflows involve some form of business process automation involving various activities such as tasking, event tracking, document management, issues, etc....
- Provides many more actions, constructs and functions than SharePoint Designer or most other 3rd party tools
- The ability to export and import workflows saves time and effort
- Nintex Workflow is extensible and allows user defined actions and nearly limitless potential using standard components
- We are not particular crazy about some of the action property dialogues. Some seem to be awkward when adding/editing email body for example
- Wish there was a way to open 2 workflows and then copy/paste actions between them
No need for developers to create workflows
Portable and extensible architecture
Projects where funding is at a premium (Designer is free)
One example that I've used many times is to have a list workflow synchronize with a dependent list. Several examples of timed Nintex Site Workflows involve end or the month reporting or weekly overdue notices. With the notices, I am able to don individual users as well a provide a summary report to the administrator. Another example of a timed workflow process is when I generate new report records for all team members for the next week; also, in the same workflow I lock down permissions on the existing records to read-only.
Nintex has great looping and querying of lists within a site. I can easily get an array of all the ids in a list such as team members, then use that array in a forEach loop to create records in another list specific for those individuals.
- Does a tremendous job of loop through arrays and querying lists for specific conditions.
- Some tasks are easy from the get-go like notifying a user on changes or new items. These tasks can be set up in minutes.
- Time processes are easy to instantiate with the workflow timer.
- This is an article I wrote on upgrading Nintex to World Class: https://community.nintex.com/community/dev-talk/blog/2017/01/05/upgrading-nintex-workflows-to-world-class.
- They need a better function library for String and Date Manipulation
- A For Loop with Counter controls instead of just a For Each iterating over collection.
- An Action Control to separate individuals for Person Controls containing group.
Nintex is optimal for Document Approval or any type of notification based on list events: Add, Change.
Nintex is good for Coordinating Master and Detail Lists.
Nintex is great for Customized Input Forms to Lists.
Nintex is great a mass record creation based on data from diverse list.
- Easy to develop and demonstrate applications
- Easy and interactive creation of workflows
- Develop very strong workflows that do not require development tools and skills
- Improved tools for laying out complex forms. Alignments etc.
- Support of bi-lingual forms
- Better support and manipulation of large forms
- Very easy for the end user to implement
- A person with low coding skills can effectively create a complex workflow
- The logging is very easy to check and implement
- The support system can be improved.
- Lots of organisation use lync/skype but the nintex support is not available over skype
- In case of production issues, there is no option to raise the severity.
- Great HTML emails
- Azure actions on O365 are helpful
- SQL action in workflow is very good.
- Nintex form doesn’t have SQL action for O365.
- Azure actions don’t allow you to get AD group members using NINTEX workflow.
- You can’t import a list workflow as site workflow.
- Extracting calendar occurance is very hard behind the workflow action.
- The interface and GUI are top notch and well designed. They make it easy to visualize the workflow.
- The verbiage and help section of Nintex Workflow make creating what you need very easy to read and understand.
- The community and forums are terrific and very responsive. You often get answers from people who work at Nintex.
- Integration with other systems is poor at best.
- The limitation of the processes they have in place. An example is a function that will execute a SQL statement will only return a max of 500 records last I used it.
- Issues with the designer and sometimes their servers seem to be laggy. It is hosted so you are relying on Nintex for some performance overhead.
- Integration with querying SharePoint data, providing robust data validation features, creating entry-points for using custom code
- Extends the basic SharePoint platform
- Provides features not natively available in SharePoint
- The browser design interface can be frustrating.
- Its performance is slow.
- The design, architecture, and syntax takes time to learn.
- Portfolio of actions, wide number of Nintex and SharePoint interactions.
- Forms as a compute platform, incredible amount of form capability.
- Repeatable standard forms and workflows.
- External data connection. Would allow Azure SQL to become a part of the Information Architecture.
- Central workflow management. Would allow greater enterprise adoption.
- Very easy to learn.
- Easy to make changes.
- Integrates with SharePoint
- A proper user guide would be helpful.
- Looking for "How do I" in Nintex takes you to too many different sites. I just want to go to one place.
We are passing through certain complex issues, but Nintex helpdesk is able to resolve it.
- Forms, useful builders friendly explanations.
- Workflow , nice design and complexity.
- Compability over Sharepoint migration.
- Expand compatibility.
- Connect to external sources and translate to forms Nintex.
- Migration proccess.
Workflows used to notification adjustment etc.
- Nintex Forms is easy, intuitive, and great to look at.
- Simple workflow creation is easy, but complex workflows usually trip our users.
- Nintex provides great support.
- User help materials are lacking. They've started Xchange etc., but I don't like the idea of monetizing help.
- Vendor response (distinct from support response) is slow.
- Very intuitive
- Strong user support and knowledge base
- Constantly updated and adding new features and extensions
- Improve the preview functionality, not all features work in preview
- Improve knowledge base around JS and CSS integration
- Add connectors to other systems into SP2016 not just Cloud solution
- It is easy to learn. The video demos are really helpful. You can follow through the script to learn how to use the tools. It would help any new user substantially to do the videos first thing. I geared my certificates to my needs.
- They are great at addressing concerns and problems. The team at Nintex is a phone call or email away. Never afraid to jump on Skype and work out a problem. We would pull out my workflow and test it out. Catching the error or working through a building block.
- They walk you through each step of the way. The team wants to make sure you understand the timeline, where you should be, and how to go forward. They have a pretty clear timeline and a team specifically geared for that timeline. They make sure to have weekly or bi-monthly check-ins. It is tailored to your needs.
- The demos are time-consuming. There was a bit of an expectation to get the demos done right away where we were ready to hop in.
- Nintex is easy to learn, but harder to master. There were some periods where I felt I really had to dig in there and read between the lines when it came to figuring the workflows out.
- Parts of the platform are new, which means there are a lot of updates. Updates are good, but hard when you are only now getting the hang of how everything works.
- The WYSIWYG workflow designer makes workflow generation straightforward.
- The ability to call external APIs makes integration with other systems outside of SharePoint easy.
- Using SharePoint as a platform allows us to quickly distribute the workflows throughout the organization.
- The workflow designer seems to have some rendering issues in non-IE browsers.
- Low learning curve.
- Big focus on developer/user experience.
- Multiple out-of-the-box connectors for third-party solutions like Office 365, Box and other apps mostly from the Microsoft ecosystem.
- They really know how to build a user community.
- Nintex is heavily dependent on Sharepoint and carries over many technical dependencies of this platform, making it difficult to scale.
- Nintex makes bold statements about being a leader in the business process world yet they don't recognize many standards, e.g., BPMN.
- We ran into a number of technical issues when supporting this platform.
- Visio-like design experience is very easy to use.
- Configuration for tasks allows custom messages to assignee explaining what to do.
- Easy to enable and disable actions used during testing. For example, I send myself emails listing variables so I can see values. After testing I can disable those actions before doing the final publish.
- Export and import workflows. Great for prod moves or to re-use workflows on another site.
- Especially like query list in site workflows.
- If a workflow error [occurs] we can’t see if it was a current or prior version.
- Some departments would like to have the capability to import Excel data into a list.
- Easy to learn the application.
- For complicated workflows it is much easier to add notes and understand what it is doing with the graphical interface vs. SharePoint Designer.
- The Forms application is very flexible and can handle almost any type of customization.
- Nintex documentation is almost non existent. It was difficult to find and not very helpful once found. The forums are helpful but that shouldn't be the first stop for how to use the product.
- Support for installation was also lacking. We installed it fairly easily following the instructions provided from Nintex, but started having problems with complex workflows timing out right away. The solution was explained by a Nintex Partner that came into our office and helped re-configure Nintex and our databases that Nintex used.
- Cross platform BPA integration.
- Intuitive user interface.
- Able to handle the most simple to the most complex BPA initiatives.
- Multiple approach options in Nintex Workflow and Nintex Workflow Cloud.
- Forms and Workflow May have to be updated as new features become available.
- Without training, end users may find Nintex Workflow difficult to use.
Now most of the teams in the organization are creating and maintaining their own workflows with little or no support at all from the IT team.
- Out-of-the-box SharePoint workflows were very tedious to build and manage, whereas Nintex is an easy to use, integrated solution that speeds development of workflows while increasing transparency and accountability.
- Integration with various platforms - One very stimulating feature about Nintex is the way it integrates with the other platforms that we use every day. To be specific, it allows you to connect to web service, CRM, Excel services, BCS, LDAP, active directory, XML and BizTalk. Moreover, the best thing about these integrations is that they require no code, thus allowing any of the users to incorporate them easily into workflows.
- Debugging and troubleshooting - It reduces the effort in debugging and troubleshooting through explicit log messages, and the ability to easily disable specific workflow actions / branches.
- Features like state machine multi-level approval, Lazy Approval (reply to approvals via email), Workflow visualizations, scheduled workflows, constants, delegation and so on, are available out of the box, without the need to write a single line of code, which makes it very appealing.
- Manual start of site workflows - Currently Nintex Online does not allow a way to toggle manual start for site workflows.
- Support for operators in *Wait for field change in current item* action.
- Wait for item update action in Nintex on-prem enables developer to use different operator based on need. Please enable operators in Nintex online action or wait for field change in current item action.
- Permissions to Nintex Apps (Forms and/or Workflows).
- Currently anyone with full control to a list or library can access the Nintex forms and workflows. We want our business users to have full access to lists and libraries, but do not want them modifying workflows as they are business critical. We need only the development team to have access to Nintex in O365. In SharePoint 2013 on-premises, I would go to Site Settings -> Nintex -> Allowed Workflow Designers -> Remove permissions except for the development team. We need this same access control in O365.
- The Nintex Platform is user friendly and easy to use.
- It has a deep set of built-in actions that allow users to create both simple and complex workflows .
- For those seeking to automate SharePoint, the Nintex Platform is deeply integrated into and leverages the native SharePoint architecture.
- While generally a good interface, there are some action configuration interfaces that some new users find are difficult to understand.
- The online version of Nintex Workflow continues to evolve, but does not yet have feature/action parity with its older on-premises counterpart.
- The user interface rendering can be slow at times. While it has improved over the years, I'd like to see individual action configuration dialogs be quicker than they are today.
- Sending emails to people when documentation has changed and needs to be reviewed again.
- An award process was moved to SharePoint using both Nintex Forms and Workflows. This enabled the admin to standardize the email, move the voting process into SharePoint and automate the emails to nominators and winners. It also facilitated the gathering and storage of all the information in one place and the sharing of information among a large group as the process moved from one stage to the next.
- I'd like to see the ability for central administrators to set up some standards across farms or site collection admins for deleting workflow history. Our environment is so huge that our central admins have turned off numerous Nintex actions due to the size of the environment.
- Changing fields based on other fields.
- Sending emails when change is made.
- Using information in other/linked lists
Nintex Platform Scorecard Summary
Feature Scorecard Summary
About Nintex Platform
Nintex Platform is a solution for Business Process Management and Digital Process Automation. Public and private sector organizations around the world leverage the Nintex Platform every day to quickly and easily manage, automate and optimize their business processes. Nintex Platform includes capabilities for process mapping, workflow automation, document generation, forms, mobile apps, process intelligence and more, all with an easy to use drag and drop designer.
Nintex seeks to drive improvement across the organization through broader participation in process improvement by knowledge workers most familiar with business process requirements, inefficiencies, or potential bottlenecks. With Nintex anyone in an organization is empowered to manage, automate and optimize their most critical business processes—all with clicks, not code.
Nintex Platform Competitors
Nintex Platform Customer Size Distribution
|Small Businesses (1-50 employees)||15%|
|Mid-Size Companies (51-500 employees)||36%|
|Enterprises (> 500 employees)||Enterprises (> 500 employees)||49%|
Nintex Platform Support Options
|Free Version||Paid Version|
|Video Tutorials / Webinar|
Nintex Platform Technical Details
|Deployment Types:||On-premise, SaaS|
|Mobile Application:||Apple iOS, Android, Mobile Web|