In this blog, learn when it’s time to extend your workflow functionality in SharePoint, but not replace it – by using Nintex Workflow.
One thing a lot of clients ask me: “When should I start looking at a third party product for my SharePoint Workflows?”
This can be a tricky question sometimes, as the answer always comes back to:
“It depends on what you want to do and what your requirements are.”
But I figured I would at least try to compare SharePoint Native Workflows with what would be the most logical product to extend workflow functionality in SharePoint, but not replace it: Nintex Workflow.
A quick primer: Nintex Workflow is a SharePoint add-in that replaces the user interface for SharePoint Workflows, as well as adds new functionality that are not currently found when creating workflows with SharePoint designer. The product still utilizes the same workflow engine as SharePoint native workflows use (Workflow Manager), and it still beholden to any limitations with that product.
That being said, the decision on whether to purchase Nintex really depends on some key questions based on your requirements.
Who will Create and Maintain the Workflows?
Advanced workflow creation in SharePoint and Nintex is not as simple as either company would like to tell you. Your audience should understand variables, loops, parallel block processing, and when to create certain columns in SharePoint that need to store certain information. You don’t necessarily need to be a developer to create and maintain workflows, but there are certain design patterns that should be considered when implementing them. If you have a fairly non-technical user base for your workflows:
The UI for Nintex is drag and drop, and much more graphical than a SharePoint designer. For users who prefer being able to see how the flow of their workflow looks, and see decision trees. Nintex provides a much easier user experience that SharePoint Designer, which depending on your audience, may be necessary. SPD is much more text-based (even though it can be modeled in Visio, which itself isn’t that intuitive).
What are you Trying to Accomplish with your Workflows?
The answer to this question can be relatively broad and often times: “We’re not sure what we’re going to be doing in the future.” That’s okay! Maybe the best strategy is to start with SPD and then move to Nintex when the requirements call for it. Workflows created in both will still function on the platform. It’s certainly not as pristine, but it makes more sense if your needs to move to Nintex never come to fruition.
When Would I Need to Move to a Product like Nintex?
My rule for when Nintex becomes a good idea: when you have a need to have workflows that need to communicate outside of data stored in SharePoint. Not even just SharePoint, but when you have needs that might cross web applications or even site collections. Nintex can handle cross authentication much easier than SharePoint Designer, as well as offer actions that SPD does not offer.
Here are a couple of example actions that Nintex provides:
- Adobe Sign integration
- DocuSign integration
- Document Generation
- Execute SQL (Enter a connection string and query, and get the results)
- Office 365 Add user to a Group
- Wait for Field Change in Current Item
- Web Request (more advanced than the basic call HTTP Web Service. You can easily perform PUT, POST, DELETE, and form the entire body of the message with authentication included)
- Ability to build and trim strings, substrings, and regular expressions
- Yammer integration
- Ability to provision instances in AWS, Azure, and Rackspace
- Ability to provision users in Office 365 and Yammer
- Ability to manipulate JSON dictionary collections (Sort, Join, Remove, Remove Duplicates)
Start with Simple Workflows
My recommendation when looking at workflow is: Start simple unless your requirements are already not simple. Visualize your processes first. Then choose a product that fits. If your business processes are not conducive to automating, then it might be time to consider Business Process Management help. A product is only as good as the processes you’re trying to automate.
If you’re interested in learning more about SharePoint 2016, Office 365, Nintex, or BPM Consulting services, please feel free to reach out to me at email@example.com