IT:AD:SharePoint:Concepts:Workflows
Watch this: * http://msdn.microsoft.com/en-us/vstudio/Video/ff623018
## Web Based SharePoint Workflow Designer ##
http://www.nintex.com/en-US/Products/Pages/NintexWorkflow2010.aspx
I think the term “SharePoint Workflow” is inherently misleading, because there are 3 kinds of SharePoint Workflow. There are “Sequential”, “State-Machine” and “Declarative No-Code” workflows, each with its own set of strengths and weaknesses. The “SharePoint Designer” workflows you are describing in your post are “Declarative No-Code” workflows, which admittedly are much more limited in scope than the other two.
H
owever, even the declarative no-code workflows can be extended with custom activities so that you end up with very powerful capabilities that are accessible directly from SharePoint Designer. In the same way that a well-designed library of server controls can greatly improve the productivity of web developers, a well-designed activity library can enable power users to automate fairly complex business processes. Src: http://bit.ly/yjwSP1
## SP 2007 ##
- Does not provide a web based WF designer.
- Use SharePoint Designer 2010
Terminology
- Events: an event is what starts or initiates a workflow.
- Eg: New Item created or Item changed
- Eg: Activated by Uers
- Conditions: determine if and when a workflow performs an activity.
- Eg: on Item Create or Saved, “if field equals value”.
- Actions: most basic unit of a workflow.
- Set them up in serial or parrallel.
## Resources ##