Engineer at a tech services company with 5,001-10,000 employees
Real User
2014-10-07T22:54:38Z
Oct 7, 2014
Before getting into the available workflow activities, I need to mention a couple of things:
1. SharePoint 2013 has a scalable workflow engine whereas with 2010 something like BizTalk would be needed.
2. SharePoint 2013 workflow only really supports HTTP web services because of the cloud architecture; creating a 2010 workflow in 2013 will give you access to all the workflow activities.
3. There are different grades of SharePoint workflow: you can use SharePoint Designer (a Windows client application which is more that adequate for most tasks) but I would recommend Nintex as the best experience. Nintex is still built on SharePoint workflow but has a web-based designer which has many different activities, and more available from the Nintex developer site. Then there is Visual Studio if you want to create your own activities or www.codeplex.com to download custom activities.
The main aspects of Nintex is that it can be used by the business people (I know of many companies where this is the case) and there are many connectors for using cloud services like Box, SalesForce and Bing. It is not the only product in this category, but I can't really give better advice without knowing what the target scenario is. If this is general purpose use then I would definitely consider Nintex,
I have experience with SharePoint Work Flow only and the answer is you gotta be kidding me.
SharePoint workflow can hardly integrate and I do not really know what do you want it for... if you do not mind, go for cloud services... expense claim you got concur, Salesforce does has Force.com with API for integration.
Find out in this report how the two Enterprise Content Management solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI.
Before getting into the available workflow activities, I need to mention a couple of things:
1. SharePoint 2013 has a scalable workflow engine whereas with 2010 something like BizTalk would be needed.
2. SharePoint 2013 workflow only really supports HTTP web services because of the cloud architecture; creating a 2010 workflow in 2013 will give you access to all the workflow activities.
3. There are different grades of SharePoint workflow: you can use SharePoint Designer (a Windows client application which is more that adequate for most tasks) but I would recommend Nintex as the best experience. Nintex is still built on SharePoint workflow but has a web-based designer which has many different activities, and more available from the Nintex developer site. Then there is Visual Studio if you want to create your own activities or www.codeplex.com to download custom activities.
The main aspects of Nintex is that it can be used by the business people (I know of many companies where this is the case) and there are many connectors for using cloud services like Box, SalesForce and Bing. It is not the only product in this category, but I can't really give better advice without knowing what the target scenario is. If this is general purpose use then I would definitely consider Nintex,
I have experience with SharePoint Work Flow only and the answer is you gotta be kidding me.
SharePoint workflow can hardly integrate and I do not really know what do you want it for... if you do not mind, go for cloud services... expense claim you got concur, Salesforce does has Force.com with API for integration.