Microsoft SharePoint and Workflow - SharePoint Saturday Sacramento
- 1. May 19, 2011WF 101SharePoint 2010 and WorkflowRoy HiggsTechnical specialistroyh@k2.com
- 2. K2 is a platform for automating process-driven applications
- 3. Founded in 1997 - 300+ employees
- 4. Global presence; headquartered in Redmond, Washington
- 5. 2,500+ customers worldwide, including 15 percent of the Fortune 100
- 6. Customers in more than 54 countries, over 1 Million Users
- 7. Deep Microsoft Partnership as a Global Independent Software Vendor (ISV)WHO IS K2?
- 8. Workflow OverviewBuild a Workflow - DemoAgenda
- 9. Defining termsBusiness 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. 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.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.
- 10. 90%4.0488%3.9288%3.6080%78%3.2476%3.1266%3.0462%Why bpm / why workflowExpected BenefitsReasons WhyWhat are the main reasons your organization is using, or plans to use, workflow, business process management, document management or content management technology?What do you see as the key benefits of workflow, document management and content management technology?ProductivityimprovementsBetter customerserviceImproves knowledgesharingGreater accuracyCost savingsImprovedmanagement controlEnhanced team workingHelps with legalcompliance issuesTo improve serviceTo introduce greater efficienciesor improved productivityTo reduce operational costsTo improve organizational agilityTo improve the visibility ofProcessesTo meet regulatory requirementsor legal compliance issues2.0 2.5 3.0 3.5 4.0 4.5 5.00% 20% 40% 60% 80% 100%On a scale of 1 to 5, where 1 = "not important" and 5 = "very important"Percentage of respondentsNote: respondents could choose more than one optionSource: PMP Research
- 11. PRESCRIPTIVESubmitterDocument routingApprovalsSimple formsReview and ApprovalsReworkSolutionsDocument Approval
- 12. Time Sheets
- 14. PRESCRIPTIVESubmitterSolutionsDocument routingApprovalsSimple formsBusiness applicationComplex routingDynamic logicExternal data sourcesIntegrated reportingPolicy & Compliance Review
- 15. Help Desk
- 16. Customer OnboardingReview and ApprovalsReworkNotification
- 17. PRESCRIPTIVEASSISTIVESubmitterDocument routingApprovalsSimple formsBusiness applicationComplex routingDynamic logicExternal data sourcesIntegrated reportingCore processesNon-linear processVisibility by stagePerformance metricsAdhocAuditChecklistsReview and ApprovalsReworkNotification
- 18. Workflow solution complexityHighest AdoptionCapabilities & ComplexitySPD WorkflowsOOB WorkflowsWF WorkflowsDocumentsListsSitesRecordsList Forms (InfoPath)BCSInfoPathASP.NETWeb Services & WCFGeneral DALReporting & BISearchPublishing.NET DevelopmentEffortSharePoint UsersPower UsersDevelopers/AdminsDevelopers
- 20. System Support
- 22. BA Support
- 24. Project Plan
- 25. Costing
- 27. Business Buy in
- 30. SharePoint Usage
- 32. Available API
- 33. New Sources
- 34. Source Owners
- 35. Archiving
- 37. Number of Fields
- 40. Users
- 41. Notifications
- 43. Page Flow
- 44. Form Validation
- 45. External Lookups
- 46. Data Density
- 47. Logging Dashboards
- 48. Data Sources KPIs
- 50. Microsoft SharePoint 2010 & WorkflowSitesWorkflowInfoPath Form Services
- 52. External Lists
- 53. OOB Workflows
- 54. Visio Premium
- 56. Visual Studio
- 57. API Enhancements
- 59. Reusable WorkflowsNot bound to a single list or content typePortable across environments e.g. from dev to productionUltimately owned by a content type but can be associated with “All” content typesShould be the most common type of workflow created going forwardSite WorkflowsAssociated with site as owning containerCan run on any item with a site e.g. the site itself, one or more lists, one or more list itemsTypically a specific solution to a niche problem where a reusable workflow can’t be usedList WorkflowsWhat we had in SharePoint 2007Attached to a single listNot portableGenerally should not be used anymoreTypes of workflows
- 61. List EventsList is being Added/DeletedList was Added/DeletedWorkflow EventsWorkflow is StartingWorkflow was Started/Postponed/CompletedWeb EventsSite is being Provisioned/was ProvisionedList EmailList received an email messageNew SharePoint events
- 62. New actions
- 63. New conditions
- 64. SharePoint 2010 is based on the .NET Framework version 3.5Thus, all workflows in SharePoint 2010 are not Workflow Foundation 4.0 WorkflowsActions exposed to users is still Yes/No within non-developer designersWorkflow history still maintained within lists that have an inherent shelf-lifeWhat’s not new
- 65. New SharePoint Workflow stencil-set for Visio PremiumVisio 2010 as a workflow designer
- 66. Caveats10 Nested If’sUses new SPD Stencils and requires Visio 2010 PremiumNo recursion (back to parent or re-work steps)Only outcomes are ‘Yes’ or ‘No’Visio 2010 as a workflow designer
- 67. Visualization of workflow status via Visio ServicesVisio services as workflow visualization
- 68. From Visio, migrate into SharePoint Designer 2010 as a reusable workflowOnce deployed, it can be saved to a templateThe template can then be imported into Visual Studio 2010 and modifiedVisio 2010 process deploymentDeploy PackageSave to File SystemCreate New ProjectImport WSPFile systemWSPVisioVWI
- 69. QUESTIONS?
Editor's Notes
- #3: Basic – O&G
- #7: 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.
- #8: 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.
- #9: 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.