A WORKFLOW SMORGASBORD in Word

Maker Data Matrix 2d barcode in Word A WORKFLOW SMORGASBORD

In s 4, 5, and 6, we work with the two development tools for building workflows in Office 2007 the SharePoint Designer and Visual Studio. Each tool is good and serves a specific audience and purpose. To help you get a handle on where and when to use each tool, take a look at Table 9-1. This information is reproduced from the WSS v3 SDK and is available online at http://msdn2.microsoft.com/en-us/library/ms461944.aspx. It is reproduced here with the express permission of Bill Gates (well, no, not really, but I know a guy named Bill and he said it would be OK does that count ).

Table 9-1. Differences Between SharePoint Designer and Visual Studio for Workflow Development. Taken from the WSS v3 SDK, See Previously Cited URL.

Can write workflows for Microsoft Windows SharePoint Services (version 3). Code-behind file enables developer to write custom Microsoft Visual C# or Microsoft Visual Basic .NET code to express business logic. Generates workflow markup file. Workflow is authored as a template, which can be associated with multiple sites and lists. Workflow markup file, or markup and codebehind files, compiled into workflow assembly. Workflow template must be associated with each list on which it is to be available. Workflow template can be associated with a site content type. Can use any forms technology. For example, Microsoft ASP.NET 2.0 forms for Microsoft Windows SharePoint Services (version 3) workflows. Can include workflow modifications. Can author custom activities for inclusion in workflows. Package workflow assembly and workflow definition as a SharePoint Feature, and deploy to the site. Can use initiation form to gather information from the user when they start the workflow.

Can write workflows for Microsoft Windows SharePoint Services (version 3). No code behind; workflow rules file declaratively encapsulates business logic instead. Generates workflow markup file. Workflow is authored against and databound to specific list at design time. Workflow markup, workflow rules, and supporting file are stored, uncompiled, in a specific document library on the site. Association happens when the workflow is authored against the specific list; no later association is necessary or possible. Cannot author workflows against content types. Automatically generates Microsoft ASP.NET 2.0 forms, which you can then customize. Workflow modifications are not available. Must use activities provided. Automatically handles deployment to specific list. Can use initiation form to gather information from the user when they start the workflow.

Table 9-1. Differences Between SharePoint Designer and Visual Studio for Workflow Development. Taken from the WSS v3 SDK, See Previously Cited URL.

Can use custom forms for users to interact with tasks in Microsoft Windows SharePoint Services (version 3). Visual Studio debugging available. Can author both sequential and state workflows.

Can use custom forms for users to interact with SharePoint tasks. No step-by-step debugging available. Can author only sequential workflows.

* Taken from the WSS v3 SDK, available online at http://msdn2.microsoft.com/en-us/library/ ms461944.aspx

The experience of working with the Office 2007 client applications and the Office 2007 server applications specifically Workflow in our case is phenomenal. The level of integration and interaction is exceptional. But let s face it not everyone will upgrade all of their client applications to the 2007 versions immediately. This is understandable. Upgrading thousands of users desktops is not an operation to be taken lightly especially when the change is as significant as the change from Office 2003 to Office 2007. Microsoft and their partners are making a valiant effort to streamline this and help however they can, but it is nonetheless a daunting task. So, does this mean that we can t take advantage of the server-side benefits and improvements in the Office 2007 System until the client side is updated Absolutely not. As we explored earlier in the book, users of previous Office versions can still play in the SharePoint 2007/Workflow playground. They just don t get all the bells and whistles. To help alleviate some of their feelings of being second-class citizens, we ll burn a few cycles here exploring how the experience for Office 2003 users can be made a bit better.

Note I m only going to be focusing on the Office 2003 client here. You could probably take some of this

material and make it work in Office XP and maybe even Office 2000, but I m not going to be looking at either of those here.

Before we get started solving the problem, let s make sure we all understand exactly what it is we re trying to accomplish. From my perspective, the elements lacking in Office 2003 related to workflow are the following: Notification of pending workflow tasks for the current document The ability to interact with workflow tasks from the client The ability to initiate a workflow from the client applications