1 / 8

Converting SharePoint Workflows

Converting SharePoint Workflows. Presented by RJB Technical Consulting. Problem Overview.

elewa
Download Presentation

Converting SharePoint Workflows

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Converting SharePoint Workflows Presented by RJB Technical Consulting

  2. Problem Overview SharePoint Designer can make simple, easy workflows for any SharePoint site. These workflows, however, are restricted to the site they were created against, owing to site-specific GUIDs hard coded into each workflow.

  3. What is a GUID? • A Globally Unique Identifier, or “GUID”, is a special type of identifier used in SharePoint to provide a reference number which is unique in any context • GUIDs are generated using elements such as the MAC address of a computer to nearly guarantee a unique number being generated • There are more possible GUID combinations than there are observable stars in the sky (3.4 x 10^38 combinations vs 5 x 10^22 stars observable from Earth) • Because GUIDs are unique between SharePoint sites, this makes references difficult to create as universal

  4. Why does this matter? • References to specific lists will not be the same • References to columns will not be the same • References to sites will not be the same • SharePoint Designer workflow would have be rebuilt nearly from scratch on each site in the progression from Development to Production • This is both time consuming and dangerous • One mistake or variance and the workflow can fail

  5. How does Visual Studio help? • With a Visual Studio workflow, we have far more depth to work with than SharePoint Designer • Programmatically, we can get the GUID of the objects our workflow needs • Some methods accept other information in place of a GUID – which we can’t do in Designer • Visual Studio lets us “featurize” our workflow for deployment to SharePoint

  6. Key steps • Five key variables are required by almost every workflow: Initialization parameters, Context, ID, Item ID, and List • Removal of the Designer workflow initialization activity • Replacing the aforementioned activity with our own initialization method • Replace SharePoint Designer variables with strongly identified variables • Replace references in the code to GUIDs with variables or specific names of lists and columns • Replace any GUIDs in the aspx forms of the site

  7. Finishing up • Package core solution as a wsp (recommend WSP Builder) • Provision form files, images, and other elements • Create a batch script to install and deploy your feature with the workflow • Activate the feature on the target site • Add the workflow to a library or list

  8. Proceed to Demo Good luck!

More Related