I have no active experience with 2013 Workflows. From SharePoint 2007, my summary of Workflows is as follows:
- SharePoint OOTB Workflows are hard to really customize
- Visual Studio Workflows are complicated.
- SharePoint Designer Workflows work but it’s hard to get all the functionality you need without a lot of Custom Activities through Visual Studio–Also you need seriously technical folks with system permissions
- Couldn’t get K2 to seriously work in our environments
From just observation, it looks like Nintex understands users, workflows and SharePoint.
Comments
I have only worked with SharePoint Designer workflows and Nintex Workflows within SharePoint 2010, but I am very please with the Nintex. The ease of editing workflows along with an expanded action set is very nice! Just as an added comment my favorite Nintex action is the ability to add content to lists outside of the current site collection.
Could you offer some testimonials from developers, case studies and cost analysis?
thanks,
Stephan
Apart of Nintex, there are other workflow solutions that expand SharePoint capabilities. Not being impartial here, (I work for the company), I would like to recommend you Datapolis, which uses state machine workflows and is able to convert them into stand-alone business applications. You can learn more at www.datapolis.com.
How do you like it?
