Introduction To Windows Workflow In Windows Share Point


Published on

Published in: Technology
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Introduction To Windows Workflow In Windows Share Point

  1. 2. <ul><li>Overview of Workflows in Sharepoint </li></ul>
  2. 3. Office Workflow Vision <ul><li>Facilitate human processes by attaching business logic to items and documents in Windows SharePoint Services, while providing context and tracking progress </li></ul><ul><li>Empower information workers using Office Server with out-of-the-box solutions and self-service tools to support a broad range of routing and tracking scenarios without IT involvement </li></ul><ul><li>Empower organizations to build a broad range of sophisticated workflow solutions that take advantage of the full functionality of the Windows Workflow Foundation (WF) platform and integrate into the SharePoint and Office experiences </li></ul>
  3. 4. Office Workflow Ecosystem SharePoint Services WF Web Service History List Reporting & Admin Source List Task List <ul><li>Initiation and parameter setting </li></ul><ul><li>Ad-hoc Customization (Forward/Delegate) </li></ul><ul><li>Task Completion </li></ul>Authoring Apps Browser UI <ul><li>Administration </li></ul><ul><li>Reporting/Status </li></ul><ul><li>Initiation </li></ul><ul><li>Parameter setting </li></ul><ul><li>Ad-hoc Customization (Forward/Delegate) </li></ul><ul><li>Task Notification and Completion </li></ul>Outlook <ul><li>Task Notification </li></ul><ul><li>Task Completion </li></ul>SharePoint Designer <ul><li>Wizard-based authoring </li></ul><ul><li>Forms integration </li></ul><ul><li>Application deployment </li></ul>Access <ul><li>Initiation and parameter setting </li></ul><ul><li>Task Completion </li></ul><ul><li>Reporting </li></ul>
  4. 5. Workflow Authoring Scenarios Visual Studio and Workflow SDK Out-of-the-Box Solutions (with customization) SharePoint Designer Workflow Routing and Approval Review – Approval Signature collection East Asian workflow Structured Ad Hoc Office Server Features List Moderation Publishing Process Document Expiration Tracking Applications Issue tracking LOB Integration Custom Form Actions Email Notification Exception Handling Document Processes Spec Review Weekly Status Report Custom Tracking Apps Service Requests Asset Tracking Industry specific processes Purchase orders Product lifecycle mgmt <ul><li>Data External to SharePoint </li></ul><ul><li>Reusable Workflows in SharePoint </li></ul><ul><li>Management of SharePoint </li></ul><ul><li>Content specific workflow </li></ul><ul><li>Rules based notification </li></ul>
  5. 6. The workflow functionality in Windows SharePoint Services 3.0 is built on the Windows Workflow Foundation (WF), a Microsoft Windows platform component that provides a programming infrastructure and tools for development and execution of workflow-based applications. WF simplifies the process of asynchronous programming to create stateful, long-running, and persistent workflow applications. The WF run-time engine manages workflow execution and allows workflows to remain active for long periods of time and to survive restarting the computer. Run-time services offer functionality such as transactions and persistence to manage errors gracefully and correctly Workflow Architecture
  6. 7. <ul><li>Windows Workflow Foundation supports two fundamental workflow styles: </li></ul><ul><li>Sequential workflows   </li></ul><ul><li>  Represents a workflow as a procession of steps that execute in order until the last activity completes. However, sequential workflows are not purely sequential in their execution. Because they can receive external events and include parallel logic flows, the exact order of activity execution can vary. </li></ul>
  7. 8. <ul><li>State machine workflows    </li></ul><ul><li>  Represents a set of states, transitions, and actions. One state is denoted as the start state, and then, based on an event, a transition can be made to another state. The state machine can have a final state that determines the end of the workflow </li></ul>
  8. 9. Who Uses Workflow? <ul><li>Adhoc participation by Knowledge workers </li></ul><ul><ul><li>Participates in WSS, Office, and Outlook </li></ul></ul><ul><ul><li>Starts workflows, completes tasks </li></ul></ul><ul><ul><li>Focus – flexible and familiar </li></ul></ul><ul><li>Familiar to WSS Administrators </li></ul><ul><ul><li>Set workflow settings (available workflows, default settings) </li></ul></ul><ul><ul><li>Manage Site/Box (deployment, activation) </li></ul></ul><ul><ul><li>Focus – consistent and integrated </li></ul></ul><ul><li>Powerful tools for Developers </li></ul><ul><ul><li>Suited development tools </li></ul></ul><ul><ul><ul><li>VS for professional developers </li></ul></ul></ul><ul><ul><ul><li>SharePoint Designer for site authors </li></ul></ul></ul><ul><ul><li>SDK with activities and samples </li></ul></ul>
  9. 10. Workflow Authoring Tools SharePoint Designer (Web Designer) Activities Re-use OOB/deployed activities Forms Auto-generated Forms -ASPX Deployment Workflow authored live against server Runtime compilation Development Model Wizard-based workflow designer Visual Studio (Pro-Dev) Activities Re-use OOB/deployed activities Can author new activities Forms Designed Forms -InfoPath -ASPX Deployment Solutions package generated Box administrator installable Development Model Visual workflow designer
  10. 11. Office Workflow Host <ul><li>WSS host provides: </li></ul><ul><ul><li>Persistence </li></ul></ul><ul><ul><li>Event Delivery </li></ul></ul><ul><ul><li>Timer </li></ul></ul><ul><ul><li>History and Reporting </li></ul></ul><ul><ul><li>WSS Application Integration </li></ul></ul><ul><li>Workflow Foundation is hosted in WSS process on all front-end machines </li></ul><ul><li>Workflow instances are aggressively dehydrated to the back-end database </li></ul>
  11. 12. Detailed comparison of capabilities Visual Studio 2005 Designer for Windows Workflow Foundation SharePoint Designer 2007 Can write workflows for Windows SharePoint Services or SharePoint Server Can write workflows for Windows SharePoint Services or SharePoint Server Code-behind file enables developer to write custom Visual C# or Visual Basic .NET code to express business logic No code-behind file; workflow rules file declaratively encapsulates business logic Generates workflow markup file Generates workflow markup file Workflow is authored as a template, which can be associated with multiple sites and lists Workflow is authored against and data-bound to specific list at design time Workflow markup file, or markup and code-behind files, are compiled into workflow assembly Workflow markup, workflow rules, and supporting file are stored, uncompiled, in a specific document library on the site Workflow template must be associated with each list on which it is to be available Association happens when the workflow is authored against the specific list; no later association is necessary or possible Can use any forms technology. For example, ASP forms for Windows SharePoint Services workflows, or InfoPath forms for SharePoint Server workflows Automatically generates ASP.NET forms, which you can then customize Can include workflow modifications Workflow modifications are not available Can use custom symmetrical InfoPath forms, which enables Office client integration of custom workflow forms InfoPath forms integration not available Can author custom activities for inclusion in workflows Must use activities provided Package workflow assembly and workflow definition as a SharePoint feature, and deploy to the site Automatically handles deployment to specific list Can use Initiation form to gather information from the user when starting the workflow Can use Initiation form to gather information from the user when starting the workflow Can use custom forms for users to interact with SharePoint tasks Can use custom forms for users to interact with SharePoint tasks Visual Studio debugging available No step-by-step debugging available Can author both sequential and state workflows Can author only sequential workflows