SharePoint Intelligence Extending Share Point Designer 2010 Workflows With Custom Actions


Published on

Automating business processes with SharePoint is a powerful way to increase efficiency within any organization. With SharePoint Designer 2010, no-code (or declarative) workflows can be built to run either SharePoint 2010 On-Premise or in the cloud with Office 365. In this session, we’ll develop an expense report workflow from beginning to end to show how SharePoint Designer Workflows are being used in business today.

  • Be the first to comment

  • Be the first to like this

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

No notes for slide
  • Who i I am nothing but SharePoint Clients
  • SharePoint Intelligence Extending Share Point Designer 2010 Workflows With Custom Actions

    1. 1. Extending SharePoint Designer 2010 Workflows with Custom Actions<br /><br />Ivan Sanders<br />SharePoint MVP Developer, Evangelist<br /><br /><br />
    2. 2.
    3. 3. Workflow Actions Schema Overview <br />Schema Elements <br />I placed these in alphabetical order for easier reference, not in order of hierarchy. I will post the hierarchy the next time. <br />Action Element<br />Contains the information needed for the workflow engine to process a workflow activity, which is called an action in Windows SharePoint Services 3.0. A workflow Action element represents a workflow activity, such as sending e-mail notifications, updating Windows SharePoint Services 3.0 list items, creating and assigning tasks, as well as many other activities.<br />Condition Element <br />Represents a Condition statement, which is part of a rule sentence that can be displayed in a declarative, rules-based, code-free workflow editor, such as Microsoft Office SharePoint Designer 2007. <br />
    4. 4. Workflow Actions Schema Overview <br />Default Element <br />The Default element is a container for other elements and has no definable attributes.<br />Option Element <br />Used to populate DesignerType drop-down list box controls that are not data bound. Option elements contain text and value pairs that can be used to build a workflow sentence. They also contain information about their .NET data types.<br />Parameter Element <br />Used to describe the input and output parameters for a custom Actions or Conditions method call.<br />RuleDesignerElement <br />Complex type element. The RuleDesigner element contains information needed to render a workflow sentence in a declarative, code-free workflow editor such as Microsoft Office SharePoint Designer 2007.<br />WorkflowInfo Element <br />WorkflowInfo is the root element of the Actions schema. This element must be included in any .ACTIONS file that is installed on the server.<br />
    5. 5. Workflow in SPO?<br />New Workflow targets<br />Reusable Workflows can be applied to any list<br />Site Workflows can execute on site <br />New Workflow events<br />Emitted by SharePoint Online (i.e. WorkflowStarted)<br />Custom Events, Event Receivers<br />
    6. 6. Workflow Designer<br />Improved declarative workflow designer<br />
    7. 7. Task Process Designer<br />
    8. 8. Actions <br />Actions get work done in the workflow<br />Examples:<br />Create, copy, change, or delete list items/documents<br />Check items in or out<br />Send an e-mail<br />Create a task for person or group<br />Collect data via task for use in the workflow<br />Pause or stop the workflow<br />Log workflow information to a History list<br />Set workflow variables or perform calculations<br />
    9. 9. Conditions <br />Control flow of the workflow<br />Examples:<br />If any value equals value<br />If current item field equals value<br />Created by a specific person<br />Created in a specific date span<br />Title field contains keywords<br />
    10. 10. Steps <br />Allow you to organize your workflow<br />Steps performed in Serial or Parallel<br />
    11. 11. Impersonation <br />Workflows run with permissions of user<br />Use impersonation step to run as workflow author<br />
    12. 12. WorkflowSharePoint Designer 2010Implementing Workflows<br />demo <br />
    13. 13. Custom Workflow Actions<br />Define class/method in Visual Studio 2010<br />Sandbox Solutions API<br />Define new action via <WorkflowActions> schema<br />Maps designer to method call<br /><Action><br /><RuleDesigner><br /><Parameters><br />
    14. 14. Workflow Events<br />Implemented via Workflow Event Receiver<br />Override SPWorkflowEventReceiver<br />Scope<br />SPSite<br />SPWeb<br />SPList<br />SPContentType<br />Events<br />WorkflowStarting<br />WorkflowStarted<br />WorkflowCompleted<br />WorkflowLoading<br />WorkflowUnloading <br />WorkflowPostponed<br />
    15. 15. Creating and Deploying DocumentSet Actions & Customizable Conditions<br />demo <br />
    16. 16. SP2010 vs. SPO<br />Can’t export from SPD2010 to VS2010<br />Can’t build Visual Studio code workflows in a sandboxed solution<br />
    17. 17. Summary<br />Implement the workflow in SharePoint Designer 2010<br />Custom or copy & modify built in workflow<br />Actions, conditions and steps<br />Develop custom workflow actions and events in Visual Studio 2010<br />
    18. 18. Who can you trust??<br />The blogs I trust through all of the noise.<br />Maurice Prather<br />Andrew Connell<br />Spence Harbar<br />Jim Duncan<br />Heather Solomon<br />Todd Klindt<br />Todd Baginski<br />Todd Bleeker Tielens<br />Patrick Tisseghem<br />WictorWilen<br />Ted Patisson<br />Lars Fastrup<br />CarstenKeutmann<br />Keith Richie<br />Bill Baer<br />
    19. 19. Thank you<br /><br />Ivan Sanders<br />SharePoint MVP Developer, Evangelist<br /><br /><br />
    20. 20. What's on the Flash drive<br />Extras<br />
    21. 21. Extras<br />SharePoint 2007<br />SharePointSolutionInstaller<br />WSPBuilder<br />KerberosBuddy<br />SharePoint Sushi<br />SharePointManager2007 / 2010<br />SPViewPermissionSetting.wsp<br />2007 Office SDK1.5<br />SQL Scripts<br />SharePoint 2010<br />AutoSPInstaller<br />2010 Documentation<br />BusinessIntelligenceLabs<br />2010 Tips and tricks<br />SQL Scripts<br />npp.5.8.6<br />Search.StandardMasterPageAdapter.wsp<br />
    22. 22. Resources<br />Download SharePoint Designer 2010<br /><br />Introducing SharePoint Designer 2010<br /><br />SharePoint Designer 2010 Workflow <br /><br />Creating SharePoint Workflow Solutions<br /><br />Walkthrough: Create a Custom Site Workflow Activity<br /><br />
    23. 23. Performance<br />Addendum<br />
    24. 24. Database Performance<br />Database Volumes<br />Separate database volumes into unique LUN’s consisting of unique physical disk spindles.<br />Prioritize data among faster disks with ranking:<br />SQL TempDB data files<br />Database transaction log files<br />Search database<br />Content databases<br />In a heavily read-oriented portal site, prioritize data over logs.<br />Separate out Search database transaction log from content database transaction logs.<br />
    25. 25. Database Performance<br />SQL TempDB Data Files<br />Recommended practice is that the number of data files allocated for TempDB should be equal to number of core CPU’s in SQL Server.<br />TempDB data file sizes should be consistent across all data files.<br />TempDB data files should be spread across unique LUN’s and separated from Content DB, Search DB, etc…<br />TempDB Log file separated to unique LUN.<br />Optimal TempDB data file sizes can be calculated using the following formula: [MAX DB SIZE (KB)] X [.25] / [# CORES] = DATA FILE SIZE (KB)<br />Calculation result (starting size) should be roughly equal to 25% of the largest content or search DB.<br />Use RAID 10; separate LUN from other database objects (content, search, etc…).<br />“Autogrow” feature set to a fixed amount; if auto grow occurs, permanently increase TempDB size.<br />
    26. 26. Database Performance<br />Content Databases<br />100 content databases per Web application<br />100GB per content database<br />CAUTION: Major DB locking issues reported in collaborative DM scenarios above 100GB<br />Need to ensure that you understand the issues based on number of users, usage profiles, etc…<br />Service Level Agreement (SLA) requirements for backup and restore will also have an impact on this decision.<br />KnowledgeLake Lab testing demonstrated SharePoint performance was NOT impacted by utilizing larger DB sizes; tests included content DB sizes that were 100GB, 150GB, 200GB, 250GB, 300GB and 350GB.<br />
    27. 27. Database Performance<br />Content Databases - Continued<br />Pre-construct and pre-size<br />Script generation of empty database objects<br />“Autogrow” feature on<br />Use RAID 5 or RAID 10 logical units<br />RAID 10 is the best choice when cost is not a concern. <br />RAID 5 will be sufficient and will save on costs, since content databases tend to be more read intensive than write intensive.<br />Multi-core computer running SQL Server<br />Primary file group could consist of a data file for each CPU core present in SQL Server. <br />Move each data file to separate logical units consisting of unique physical disk spindles.<br />
    28. 28. Database Performance<br />Search Database<br />Pre-construct and pre-size<br />Script generation of empty database objects<br />“Autogrow” feature on<br />Use RAID 10 logical units<br />Should be a requirement for large-scale systems<br />Search database is extremely read/write intensive<br />Multi-core computer running SQL Server<br />Primary file group could consist of a data file for each CPU core present in SQL Server. <br />Move each data file to separate logical units consisting of unique physical disk spindles.<br />
    29. 29. Database Performance<br />Search Database<br />Search database is VERY read/write intensive!<br />Do not place any other database data files on any logical unit where search database files reside.<br />If possible, try to ensure that the RAID 10 logical units for the search database data files do not share their physical spindles with other databases.<br />Place the search database log files on an independent logical unit.<br />
    30. 30. Database Performance<br />Database Maintenance<br />Physical Volume File Fragmentation:<br />Defragment your physical volumes on a regular schedule for increased performance!<br />LUN’s need to be 20-50% larger than the data stored on them allow for effective defragmentation of the data files.<br />Performance Monitor Counters to watch:<br />Average Disk Queue Length<br />Single Digit values are optimal.<br />Occasional double-digit values aren’t a large concern.<br />Sustained triple-digit values require attention.<br />
    31. 31. Page Performance<br />Minimize HTTP Requests<br />80% of the end-user response time is spent on the front-end. Most of this time is tied up in downloading all the components in the page: images, stylesheets, scripts, Flash, etc. Reducing the number of components in turn reduces the number of HTTP requests required to render the page. This is the key to faster pages. <br />For static components: implement <br />"Never expire" policy by setting far future Expires header<br />Avoid Redirects<br />Redirects are accomplished using the 301 and 302 status codes. Here’s an example of the HTTP headers in a 301 response:<br />Optimize Images<br />After a designer is done with creating the images for your web page, there are still some things you can try before you uploading the images to your web server<br />Avoid Empty Image src<br />Image with empty string src attribute occurs more than one will expect.<br />