Microsoft SharePoint and Workflow - SharePoint Saturday Sacramento
Upcoming SlideShare
Loading in...5
×
 

Microsoft SharePoint and Workflow - SharePoint Saturday Sacramento

on

  • 1,489 views

 

Statistics

Views

Total Views
1,489
Views on SlideShare
1,485
Embed Views
4

Actions

Likes
0
Downloads
51
Comments
0

1 Embed 4

http://www.linkedin.com 4

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • Basic – O&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.

Microsoft SharePoint and Workflow - SharePoint Saturday Sacramento Microsoft SharePoint and Workflow - SharePoint Saturday Sacramento Presentation Transcript

  • May 19, 2011
    WF 101SharePoint 2010 and Workflow
    Roy Higgs
    Technical specialist
    royh@k2.com
    • 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)
    WHO IS K2?
  • Workflow Overview
    Build a Workflow - Demo
    Agenda
  • Defining terms
    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.
    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.
  • 90%
    4.04
    88%
    3.92
    88%
    3.60
    80%
    78%
    3.24
    76%
    3.12
    66%
    3.04
    62%
    Why bpm / why workflow
    Expected Benefits
    Reasons Why
    What 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?
    Productivity
    improvements
    Better customer
    service
    Improves knowledge
    sharing
    Greater accuracy
    Cost savings
    Improved
    management control
    Enhanced team working
    Helps with legal
    compliance issues
    To improve service
    To introduce greater efficiencies
    or improved productivity
    To reduce operational costs
    To improve organizational agility
    To improve the visibility of
    Processes
    To meet regulatory requirements
    or legal compliance issues
    2.0 2.5 3.0 3.5 4.0 4.5 5.0
    0% 20% 40% 60% 80% 100%
    On a scale of 1 to 5, where 1 = "not important" and 5 = "very important"
    Percentage of respondents
    Note: respondents could choose more than one option
    Source: PMP Research
  • PRESCRIPTIVE
    Submitter
    Document routing
    Approvals
    Simple forms
    Review and Approvals
    Rework
    Solutions
    • Document Approval
    • Time Sheets
    • Expense Reports
    Notification
  • PRESCRIPTIVE
    Submitter
    Solutions
    Document routing
    Approvals
    Simple forms
    Business application
    Complex routing
    Dynamic logic
    External data sources
    Integrated reporting
    • Policy & Compliance Review
    • Help Desk
    • Customer Onboarding
    Review and Approvals
    Rework
    Notification
  • PRESCRIPTIVE
    ASSISTIVE
    Submitter
    Document routing
    Approvals
    Simple forms
    Business application
    Complex routing
    Dynamic logic
    External data sources
    Integrated reporting
    Core processes
    Non-linear process
    Visibility by stage
    Performance metrics
    Adhoc
    Audit
    Checklists
    Review and Approvals
    Rework
    Notification
  • Workflow solution complexity
    Highest Adoption
    Capabilities & Complexity
    SPD Workflows
    OOB Workflows
    WF Workflows
    Documents
    Lists
    Sites
    Records
    List Forms (InfoPath)
    BCS
    InfoPath
    ASP.NET
    Web Services & WCF
    General DAL
    Reporting & BI
    Search
    Publishing
    .NET Development
    Effort
    SharePoint Users
    Power Users
    Developers/Admins
    Developers
  • Solution Technology Selection
    • Resourcing
    • System Support
    • Development Support
    • BA Support
    • Internal / Contractor
    • Project Plan
    • Costing
    • General Constraints
    • Business Buy in
    • Source Accessibility
    • Unstructured (Documents)
    • SharePoint Usage
    • Number of Sources
    • Available API
    • New Sources
    • Source Owners
    • Archiving
    • Data Dependencies
    • Number of Fields
    • Number of records
    • SharePoint Usage
    Requirements
    • Rules
    • Users
    • Notifications
    • SLA / Escalations
    • Page Flow
    • Form Validation
    • External Lookups
    • Data Density
    • Logging Dashboards
    • Data Sources KPIs
    • Realtimevs Scheduled
    Effort
    Process
    Data Sources
    Reporting
    Forms
    Requirements
  • Microsoft SharePoint 2010 & Workflow
    Sites
    Workflow
    • InfoPath Form Services
    • Business Connectivity Services
    • External Lists
    • OOB Workflows
    • Visio Premium
    • SharePoint Designer
    • Visual Studio
    • API Enhancements
    • REST/ATOM/RSS
    Communities
    Composites
    Content
    Insights
    Search
  • Reusable Workflows
    Not bound to a single list or content type
    Portable across environments e.g. from dev to production
    Ultimately owned by a content type but can be associated with “All” content types
    Should be the most common type of workflow created going forward
    Site Workflows
    Associated with site as owning container
    Can run on any item with a site e.g. the site itself, one or more lists, one or more list items
    Typically a specific solution to a niche problem where a reusable workflow can’t be used
    List Workflows
    What we had in SharePoint 2007
    Attached to a single list
    Not portable
    Generally should not be used anymore
    Types of workflows
  • High-privilege workflows
  • List Events
    List is being Added/Deleted
    List was Added/Deleted
    Workflow Events
    Workflow is Starting
    Workflow was Started/Postponed/Completed
    Web Events
    Site is being Provisioned/was Provisioned
    List Email
    List received an email message
    New SharePoint events
  • New actions
  • New conditions
  • SharePoint 2010 is based on the .NET Framework version 3.5
    Thus, all workflows in SharePoint 2010 are not Workflow Foundation 4.0 Workflows
    Actions exposed to users is still Yes/No within non-developer designers
    Workflow history still maintained within lists that have an inherent shelf-life
    What’s not new
  • New SharePoint Workflow stencil-set for Visio Premium
    Visio 2010 as a workflow designer
  • Caveats
    10 Nested If’s
    Uses new SPD Stencils and requires Visio 2010 Premium
    No recursion (back to parent or re-work steps)
    Only outcomes are ‘Yes’ or ‘No’
    Visio 2010 as a workflow designer
  • Visualization of workflow status via Visio Services
    Visio services as workflow visualization
  • From Visio, migrate into SharePoint Designer 2010 as a reusable workflow
    Once deployed, it can be saved to a template
    The template can then be imported into Visual Studio 2010 and modified
    Visio 2010 process deployment
    Deploy
    Package
    Save to File System
    Create New ProjectImport WSP
    File system
    WSP
    Visio
    VWI
  • QUESTIONS?