0
May 19, 2011<br />WF 101SharePoint 2010 and Workflow<br />Roy Higgs<br />Technical specialist<br />royh@k2.com<br />
<ul><li>K2 is a platform for automating process-driven applications
Founded in 1997 -  300+ employees
Global presence; headquartered in Redmond, Washington
2,500+ customers worldwide, including 15 percent of the Fortune 100
Customers in more than 54 countries, over 1 Million Users
Deep Microsoft Partnership as a Global Independent Software Vendor (ISV)</li></ul>WHO IS K2?<br />
Workflow Overview<br />Build a Workflow - Demo<br />Agenda<br />
Defining terms<br />Business Process - A set of one or more linkedprocedures or activities which collectively realize an o...
90%<br />4.04<br />88%<br />3.92<br />88%<br />3.60<br />80%<br />78%<br />3.24<br />76%<br />3.12<br />66%<br />3.04<br /...
PRESCRIPTIVE<br />Submitter<br />Document routing<br />Approvals<br />Simple forms<br />Review and Approvals<br />Rework<b...
Time Sheets
Expense Reports</li></ul>Notification<br />
PRESCRIPTIVE<br />Submitter<br />Solutions<br />Document routing<br />Approvals<br />Simple forms<br />Business applicatio...
Help Desk
Customer Onboarding</li></ul>Review and Approvals<br />Rework<br />Notification<br />
PRESCRIPTIVE<br />ASSISTIVE<br />Submitter<br />Document routing<br />Approvals<br />Simple forms<br />Business applicatio...
Workflow solution complexity<br />Highest Adoption<br />Capabilities & Complexity<br />SPD Workflows<br />OOB Workflows<br...
Solution Technology Selection<br /><ul><li>Resourcing
System Support
Development Support
BA Support
Upcoming SlideShare
Loading in...5
×

Microsoft SharePoint and Workflow - SharePoint Saturday Sacramento

1,331

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
1,331
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
56
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • Basic – O&amp;G
  • Definitions: Prescriptive – It suggest that the process is prescriptive in nature and will run from end to end along one of the designed process paths. This is good for some kinds of processes. For example an expense claim process is something that is generally prescriptive in nature. You claim for one or more things, and while the approval route may differ based on the amount, the process is always the same and we do not want people to think to much about this kind of process. The process is fixed or prescriptive in this kind of scenario and this works well where policy or fixed processes need to be implemented. Assistive – We use this word to describe the fact that Case led processes are different. They “assist” people to make the right decision by presenting them with a mix of information around the process they are involved in. It will be letters that the customer has sent, information from our systems on the customer, graphs and reports about other customers or trends and so on. The action that people will take in this kind of process is not “prescribed” but driven by the value of the information presented. These kind of processes are more “adhoc” in nature and it is impossible up front to know which route such a business process will actually follow to completion.
  • Definitions: Prescriptive – It suggest that the process is prescriptive in nature and will run from end to end along one of the designed process paths. This is good for some kinds of processes. For example an expense claim process is something that is generally prescriptive in nature. You claim for one or more things, and while the approval route may differ based on the amount, the process is always the same and we do not want people to think to much about this kind of process. The process is fixed or prescriptive in this kind of scenario and this works well where policy or fixed processes need to be implemented. Assistive – We use this word to describe the fact that Case led processes are different. They “assist” people to make the right decision by presenting them with a mix of information around the process they are involved in. It will be letters that the customer has sent, information from our systems on the customer, graphs and reports about other customers or trends and so on. The action that people will take in this kind of process is not “prescribed” but driven by the value of the information presented. These kind of processes are more “adhoc” in nature and it is impossible up front to know which route such a business process will actually follow to completion.
  • Definitions: Prescriptive – It suggest that the process is prescriptive in nature and will run from end to end along one of the designed process paths. This is good for some kinds of processes. For example an expense claim process is something that is generally prescriptive in nature. You claim for one or more things, and while the approval route may differ based on the amount, the process is always the same and we do not want people to think to much about this kind of process. The process is fixed or prescriptive in this kind of scenario and this works well where policy or fixed processes need to be implemented. Assistive – We use this word to describe the fact that Case led processes are different. They “assist” people to make the right decision by presenting them with a mix of information around the process they are involved in. It will be letters that the customer has sent, information from our systems on the customer, graphs and reports about other customers or trends and so on. The action that people will take in this kind of process is not “prescribed” but driven by the value of the information presented. These kind of processes are more “adhoc” in nature and it is impossible up front to know which route such a business process will actually follow to completion.
  • Transcript of "Microsoft SharePoint and Workflow - SharePoint Saturday Sacramento"

    1. 1. May 19, 2011<br />WF 101SharePoint 2010 and Workflow<br />Roy Higgs<br />Technical specialist<br />royh@k2.com<br />
    2. 2. <ul><li>K2 is a platform for automating process-driven applications
    3. 3. Founded in 1997 - 300+ employees
    4. 4. Global presence; headquartered in Redmond, Washington
    5. 5. 2,500+ customers worldwide, including 15 percent of the Fortune 100
    6. 6. Customers in more than 54 countries, over 1 Million Users
    7. 7. Deep Microsoft Partnership as a Global Independent Software Vendor (ISV)</li></ul>WHO IS K2?<br />
    8. 8. Workflow Overview<br />Build a Workflow - Demo<br />Agenda<br />
    9. 9. Defining terms<br />Business Process - A set of one or more linkedprocedures or activities which collectively realize an objective or policy goal in the context of an organizational structure defining functional roles and relationships. <br />Workflow- The automation of a business process, in whole or part, during which documents, information or tasks are passed from one participant to another for action, according to a set of procedural rules.<br />Business Process Management (BPM)– The practice of developing, running, performance measuring, and simulating Business Processes to effect the continued improvement of those processes. Business Process Management is concerned with the lifecycle of the Process Definition.<br />
    10. 10. 90%<br />4.04<br />88%<br />3.92<br />88%<br />3.60<br />80%<br />78%<br />3.24<br />76%<br />3.12<br />66%<br />3.04<br />62%<br />Why bpm / why workflow<br />Expected Benefits<br />Reasons Why<br />What are the main reasons your organization is using, or plans to use, workflow, business process management, document management or content management technology?<br />What do you see as the key benefits of workflow, document management and content management technology?<br />Productivity<br />improvements<br />Better customer<br />service<br />Improves knowledge<br />sharing<br />Greater accuracy<br />Cost savings<br />Improved<br />management control<br />Enhanced team working<br />Helps with legal<br />compliance issues<br />To improve service<br />To introduce greater efficiencies<br />or improved productivity<br />To reduce operational costs<br />To improve organizational agility<br />To improve the visibility of<br />Processes<br />To meet regulatory requirements<br />or legal compliance issues<br />2.0 2.5 3.0 3.5 4.0 4.5 5.0<br />0% 20% 40% 60% 80% 100%<br />On a scale of 1 to 5, where 1 = "not important" and 5 = "very important"<br />Percentage of respondents<br />Note: respondents could choose more than one option<br />Source: PMP Research<br />
    11. 11. PRESCRIPTIVE<br />Submitter<br />Document routing<br />Approvals<br />Simple forms<br />Review and Approvals<br />Rework<br />Solutions<br /><ul><li>Document Approval
    12. 12. Time Sheets
    13. 13. Expense Reports</li></ul>Notification<br />
    14. 14. PRESCRIPTIVE<br />Submitter<br />Solutions<br />Document routing<br />Approvals<br />Simple forms<br />Business application<br />Complex routing<br />Dynamic logic<br />External data sources<br />Integrated reporting<br /><ul><li>Policy & Compliance Review
    15. 15. Help Desk
    16. 16. Customer Onboarding</li></ul>Review and Approvals<br />Rework<br />Notification<br />
    17. 17. PRESCRIPTIVE<br />ASSISTIVE<br />Submitter<br />Document routing<br />Approvals<br />Simple forms<br />Business application<br />Complex routing<br />Dynamic logic<br />External data sources<br />Integrated reporting<br />Core processes<br />Non-linear process<br />Visibility by stage<br />Performance metrics<br />Adhoc<br />Audit<br />Checklists<br />Review and Approvals<br />Rework<br />Notification<br />
    18. 18. Workflow solution complexity<br />Highest Adoption<br />Capabilities & Complexity<br />SPD Workflows<br />OOB Workflows<br />WF Workflows<br />Documents<br />Lists<br />Sites<br />Records<br />List Forms (InfoPath)<br />BCS<br />InfoPath<br />ASP.NET<br />Web Services & WCF<br />General DAL<br />Reporting & BI<br />Search<br />Publishing<br />.NET Development<br />Effort<br />SharePoint Users<br />Power Users<br />Developers/Admins<br />Developers<br />
    19. 19. Solution Technology Selection<br /><ul><li>Resourcing
    20. 20. System Support
    21. 21. Development Support
    22. 22. BA Support
    23. 23. Internal / Contractor
    24. 24. Project Plan
    25. 25. Costing
    26. 26. General Constraints
    27. 27. Business Buy in
    28. 28. Source Accessibility
    29. 29. Unstructured (Documents)
    30. 30. SharePoint Usage
    31. 31. Number of Sources
    32. 32. Available API
    33. 33. New Sources
    34. 34. Source Owners
    35. 35. Archiving
    36. 36. Data Dependencies
    37. 37. Number of Fields
    38. 38. Number of records
    39. 39. SharePoint Usage</li></ul>Requirements<br /><ul><li>Rules
    40. 40. Users
    41. 41. Notifications
    42. 42. SLA / Escalations
    43. 43. Page Flow
    44. 44. Form Validation
    45. 45. External Lookups
    46. 46. Data Density
    47. 47. Logging Dashboards
    48. 48. Data Sources KPIs
    49. 49. Realtimevs Scheduled</li></ul>Effort<br />Process<br />Data Sources<br />Reporting<br />Forms<br />Requirements<br />
    50. 50. Microsoft SharePoint 2010 & Workflow<br />Sites<br />Workflow<br /><ul><li>InfoPath Form Services
    51. 51. Business Connectivity Services
    52. 52. External Lists
    53. 53. OOB Workflows
    54. 54. Visio Premium
    55. 55. SharePoint Designer
    56. 56. Visual Studio
    57. 57. API Enhancements
    58. 58. REST/ATOM/RSS</li></ul>Communities<br />Composites<br />Content<br />Insights<br />Search<br />
    59. 59. Reusable Workflows<br />Not bound to a single list or content type<br />Portable across environments e.g. from dev to production<br />Ultimately owned by a content type but can be associated with “All” content types<br />Should be the most common type of workflow created going forward<br />Site Workflows<br />Associated with site as owning container<br />Can run on any item with a site e.g. the site itself, one or more lists, one or more list items<br />Typically a specific solution to a niche problem where a reusable workflow can’t be used<br />List Workflows<br />What we had in SharePoint 2007<br />Attached to a single list<br />Not portable<br />Generally should not be used anymore<br />Types of workflows<br />
    60. 60. High-privilege workflows<br />
    61. 61. List Events<br />List is being Added/Deleted<br />List was Added/Deleted<br />Workflow Events<br />Workflow is Starting<br />Workflow was Started/Postponed/Completed<br />Web Events<br />Site is being Provisioned/was Provisioned<br />List Email<br />List received an email message<br />New SharePoint events<br />
    62. 62. New actions<br />
    63. 63. New conditions<br />
    64. 64. SharePoint 2010 is based on the .NET Framework version 3.5<br />Thus, all workflows in SharePoint 2010 are not Workflow Foundation 4.0 Workflows<br />Actions exposed to users is still Yes/No within non-developer designers<br />Workflow history still maintained within lists that have an inherent shelf-life<br />What’s not new<br />
    65. 65. New SharePoint Workflow stencil-set for Visio Premium<br />Visio 2010 as a workflow designer<br />
    66. 66. Caveats<br />10 Nested If’s<br />Uses new SPD Stencils and requires Visio 2010 Premium<br />No recursion (back to parent or re-work steps)<br />Only outcomes are ‘Yes’ or ‘No’<br />Visio 2010 as a workflow designer<br />
    67. 67. Visualization of workflow status via Visio Services<br />Visio services as workflow visualization<br />
    68. 68. From Visio, migrate into SharePoint Designer 2010 as a reusable workflow<br />Once deployed, it can be saved to a template<br />The template can then be imported into Visual Studio 2010 and modified<br />Visio 2010 process deployment<br />Deploy <br />Package<br />Save to File System<br />Create New ProjectImport WSP<br />File system<br />WSP<br />Visio<br />VWI<br />
    69. 69. QUESTIONS?<br />
    1. A particular slide catching your eye?

      Clipping is a handy way to collect important slides you want to go back to later.

    ×