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
(Visited 14 times, 1 visits today)
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?
(Visited 1 times, 1 visits today)
