http://www.slideshare.net/pwicklund/sharepoint-2010-workflows
types of workflows:
1.List
2.Content Type (Reusable )
3. Sites
Out of box workflows:
1.Approval
2.Collect feedback
3.Collect signature
4. Three state
5. Disposition
6,Translation Mngt
Defining sharepoint custom sequential workflow thru code:
http://msdn.microsoft.com/en-us/library/gg265727.aspx
When to go for Visual Studio workflows in place of sharepoint designers:
When should I use Visual Studio for Workflow?
As I mentioned earlier SharePoint Designer (SPD) is a great platform for developing basic workflows, however it has several limitations and in some cases these can mean that you have to look at Visual Studio as the solution for your workflow design.
In my experience the limitations of SPD are as follows:
- Workflows are bound to a specific list/site
In SPD any workflow you create can only exist on the list (and in the site) that you created the workflow on. You cannot design a workflow and then move it to another site. - No code support
You cannot write custom code within the SPD workflow tools. You can write custom activities to include in SPD, but you would need to do that in Visual Studio anyway. - No WSS Solution Package (WSP) support
Your workflow will be deployed to the site via SPD and there is no support for packaging these as WSP files, which provide a more maintainable and upgradeable method of deploying customisations to SharePoint. - No support for State Machine workflows
You can only build Sequential workflows with SPD, there is no support for State Machine Workflows.
Advertisement
