Table of Contents
Introduction
As an enterprise developer, it's no surprise that one business process often encountered is the approving of documents, such as legal contracts, budgets, etc. Business workflows are often followed, but in a way that is typically inefficient. For example, an employee might fill out an expense report and forward it to HR for approval. This typically involves filling out an Excel or Word document, e-mailing it to HR for processing, then waiting for either a check and/or a response or request for changes. SharePoint offers a simplified solution for routing documents through a workflow process. The problem is that there are few workflows available in SharePoint, some may not meet the requirements/needs of the business, and you can't modify existing, builtin SharePoint workflows.
There are two ways to add custom-built workflows to SharePoint Server 2007: SharePoint Designer 2007 and Visual Studio .Net 2005 with Extensions for Workflows (WF). SharePoint Designer 2007 offers limited workflow authoring, but VS.NET 2005 (and later) offers significantly extensible capabilities.
The following tutorial shows you how to develop a simple workflow that allows an approver to reject, approve, or set other statuses of a document.
Requirements: (All of the following must be installed and performed on the SharePoint Server 2007 server.)
(All of the following must be performed on the SharePoint Server 2007 server.)
Back to TOC
Creating the InfoPath Initiation Form
- Startup InfoPath 2007.
- Click on Design a Form Template, in the Design a Form area.
- Click on Blank, in the Form Template area.
- Click on OK.
- Click on Data Source, under Design Tasks.
- Right-click on the myFields folder, then click on Properties.
- Set the Name of the Data Source to "initiationFields" (without quotes).
- Click on OK.
- Right-click on the initiationFields folder, then click on Add.
- Enter "initApprover" (without quotes) in the Name field.
- Click on OK.
- Right-click on the initiationFields folder, then click on Add.
- Enter "initExpires" (without quotes) in the Name field.
- Set the Data type to Date and Time.
- Click on OK.
- Right-click on the initiationFields folder, then click on Add.
- Enter "initComments" (without quotes) in the Name field.
- Click on OK.
- Click on Design Tasks, then click on Controls.
- Uncheck the Automatically create data source check box.
- From the Controls toolbox, drag a Text Box control onto the design area.
- Click on initApprover, then click on OK.
- Rename the label to "Approver:" (without quotes).
- Drag and drop a Date Picker control onto the design area.
- Click on initExpires, then click on OK.
- Rename the label to "Expires:" (without quotes).
- Drag a Text Box control onto the design area.
- Click on initComments, then click on OK.
- Rename the label to "Comments:" (without quotes).
- Drag a button onto the design area.
- Right-click on the button, then click on Button Properties.
- Set the Label to "Send for Approval" (without quotes).
- Click on Rules.
- Click on Add.
- Click on Add Action.
- Select Submit using a data connection, from the Action drop-down list.
- Click on Add.
- Select Create a new connection to.
- Select Submit data.
- Click on Next.
- Select To the hosting environment...
- Click on Next.
- Name the data connection "Initiation" (without quotes).
- Click on Finish.
- Click on OK.
- Click on Add Action.
- Select Close the form, from the Action drop-down list.
- Uncheck the "... prompt to save ..." check box.
- Click on OK four times.
- Click on Tools, in the menu bar, then click on Form Options.
- Click on Security and Trust.
- Uncheck "Automatically determine security level...".
- Select Full Trust.
- Check the "Sign this form template" check box.
- Click on Create Certificate.
- Click on OK.
- Click on Compatibility.
- Check the "Design a form template that can be opened in a browser...".
- In the "Enter the URL of a server..." field, enter the HTTP path to the SharePoint 2007 server (e.g., http://dotnetfun).
- Click on OK.
Attaching an Item Metadata Schema File which allows us to set form fields from the VS.NET workflow.
- Open/start an instance of Windows' Notepad.
- Enter the following XML code:<![CDATA[<z:row xmlns:z="#RowsetSchema" ows_initApprover="" ows_initExpires="" ows_initComments="" />]]>
- Save the document as ItemMetadata.xml (ensuring that "Save as Type" is set to "All types").
- Close Windows' Notepad.
- Click on Data Source, under Design Tasks.
- Click on Data Source.
- Click on Manage Data Connections.
- Click on Add.
- Select "Create a new connection to:", then select Receive data.
- Click on Next.
- Select XML document, then click on Next.
- Click on Browse, then locate the ItemMetadata.xml file you just saved.
- Open the ItemMetadata.xml file.
- Click on Next.
- Select "Include the data as a resource...", then click on Next.
- Set the name to "ItemMetadata" (without quotes), and ensure the check box is checked.
- Click on Finish.
- Click on Close.
- In the design area, right-click on the initComments text box, then click on Properties.
- In the Default Value area, click on the button next to the Value field.
- Click on "Insert Field or Group".
- From the Data Source drop-down list, select ItemMetadata.
- Click on/select the initComments field.
- Click OK three times.
- In the design area, right-click on the initExpires Date Picker, then click on Properties.
- In the Default Value area, click on the button next to the Value field.
- Click on "Insert Field or Group".
- From the Data Source drop-down list, select ItemMetadata.
- Click on/select the initExpires field.
- Click OK three times.
Publishing the form.
- Click on File, from the menu bar, then click on Publish.
- Click on "To a network location...".
- Click on Next.
- Click on the Browse button, then press Alt-4.
- Call the folder "Published InfoPath Forms" (without quotes).
- Click on OK.
- Set the file name to "ApprovalInitiation.xsn" (without quotes).
- Click on OK.
- Set the "Form template name" to "ApprovalInitiation" (without quotes).
-
- Click on Next, ensuring the user access path/field is empty.
- Click on Publish.
- Click on Close.
Generating an initiationFields class file for use with the VS.NET workflow project.
- Click on File, from the menu bar, then click on "Save as Source Files".
- Navigate to where the form was published in the preceding steps, then click on OK, clicking on OK to ignore the warning.
- In Windows, click on the Start button, then navigate to Programs, Microsoft Visual Studio 2005, Visual Studio Tools, then click on "Visual Studio 2005 Command Prompt".
- Navigate to the location where the form was published. For example, try typing and entering this: cd "%HOMEPATH%\My Documents\Published InfoPath Forms"
- Type and enter the following command: xsd /c myschema.xsd /o:.
- Back in InfoPath, Save the InfoPath document, calling it "ApprovalInitiation.xsn" (without quotes), clicking on OK when prompted about Publishing the form.
- Close InfoPath.
Back to TOC
Creating the InfoPath Action Form
- Startup InfoPath 2007.
- Click on Design a Form Template, in the Design a Form area.
- Click on Blank, in the Form Template area.
- Click on OK.
- Click on Data Source, under Design Tasks.
- Right-click on the myFields folder, then click on Properties.
- Set the Name of the Data Source to "actionFields" (without quotes).
- Click on OK.
- Right-click on the actionFields folder, then click on Add.
- Set the Name to "actionStatus" (without quotes).
- Click on OK.
- Right-click on the actionStatus field in the actionFields data source, then click on Properties.
- In the Defaul Value area, click on the button next to Value.
- Click on "Insert Field or Group".
- Activate the Data Source drop-down list box, then select ItemMetadata.
- Click on actionStatus, then click on OK.
- Click on OK two times.
- Right-click on the actionFields folder, then click on Add.
- Set the Name to "actionComments" (without quotes).
- Click on OK.
- Click on Design Tasks, then click on Controls.
- Uncheck the Automatically create data source check box.
- Drag a Drop-down List Box onto the design area.
- Select actionStatus, then click on OK.
- Rename the label to "Approval Status:" (without quotes).
- Right-click on the drop-down list box, then click on Properties.
- In the "List box entries" section, ensure that "Enter list box entries manually" is selected.
- Select the first list entry, then click on Modify.
- Enter "Approve" (without quotes) in the Value and Display Name fields.
- Click on OK.
- Click on Add.
- Enter "Needs Revising" in the Value and Display Name fields.
- Click on OK.
- Click on Add.
- Enter "Reject" in the Value and Display Name fields.
- Click on OK.
- Click on OK.
- Drag and drop a Text Box control onto the design area.
- Select actionComments, then click on OK.
- Drag a button onto the design area.
- Right-click on the button, then click on Button Properties.
- Set the Label to "Submit" (without quotes).
- Click on Rules.
- Click on Add.
- Click on Add Action.
- Select Submit using a data connection, from the Action drop-down list.
- Click on Add.
- Select Create a new connection to.
- Select Submit data.
- Click on Next.
- Select "To the hosting environment...".
- Click on Next.
- Name the data connection "Action" (without quotes).
- Click on Finish.
- Click on OK.
- Click on Add Action.
- Select Close the form, from the Action drop-down list.
- Uncheck the "... prompt to save ..." check box.
- Click on OK four times.
- Click on Tools, in the menu bar, then click on Form Options.
- Click on Security and Trust.
- Uncheck "Automatically determine security level...".
- Select Full Trust.
- Check the "Sign this form template" check box.
- Click on Create Certificate.
- Click on OK.
- Click on Compatibility.
- Check the "Design a form template that can be opened in a browser...".
- In the "Enter the URL of a server..." field, enter the HTTP path to the SharePoint 2007 server (e.g., http://dotnetfun).
- Click on OK.
Attaching an Item Metadata Schema File which allows us to set form fields from the VS.NET workflow.
- Open/start an instance of Windows' Notepad.
- Enter the following XML code:<![CDATA[<z:row xmlns:z="#RowsetSchema" ows_actionStatus="" ows_actionComments="" />]]>
- Save the document as ItemMetadata.xml (ensuring that "Save as Type" is set to "All types").
- Close Windows' Notepad.
- Click on Data Source, under Design Tasks.
- Click on Data Source.
- Click on Manage Data Connections.
- Click on Add.
- Select "Create a new connection to:", then select Receive data.
- Click on Next.
- Select XML document, then click on Next.
- Click on Browse, then locate the ItemMetadata.xml file you just saved.
- Open the ItemMetadata.xml file.
- Click on Next.
- Select "Include the data as a resource...", then click on Next.
- Set the name to "ItemMetadata" (without quotes), and ensure the check box is checked.
- Click on Finish.
- Click on Close.
- In the design area, right-click on the actionComments text box, then click on Properties.
- In the Default Value area, click on the button next to the Value field.
- Click on "Insert Field or Group".
- From the Data Source drop-down list, select ItemMetadata.
- Click on/select the actionComments field.
- Click OK three times.
Publishing the form.
- Click on File, from the menu bar, then click on Publish.
- Click on "To a network location...".
- Click on Next.
- Click on the Browse button, then navigate to and open the "Published InfoPath Forms" folder.
- Click on OK.
- Set the file name to "ApprovalAction.xsn" (without quotes).
- Click on OK.
- Set the "Form template name" to "ApprovalAction" (without quotes).
- Click on Next, ensuring the user access path/field is empty.
- Click on Publish.
- Click on Close.
- Save the InfoPath document, calling it "ApprovalAction.xsn" (without quotes), clicking on OK when prompted about Publishing the form.
- Close InfoPath.
Back to TOC
Creating the Approval Workflow in VS.NET 2005
- Startup VS.NET 2005.
- Click on File-->new--Project.
- Select SharePoint, under Project Types.
- Select SharePoint Server Sequential Workflow Library, under Templates.
- Name the project and solution "SharePointApprovalWorkflow" (without quotes).
- Click on OK.
Adding the initiationFields class file to the project.
- In the Solution Explorer, right-click on the SharePointApprovalWorkflow project, then navigate to Add, then click on Existing Item...
- Navigate to the folder where the initiationFields class file was generated using the VS.NET xsd command. This might be "%HOMEPATH%\My Documents\Published InfoPath Forms"
- Select the myschema.cs class file, but DO NOT open it.
- Press F2 to rename the class file, calling it "initiationFields.cs" (without quotes), then press Enter to commit the rename.
- Click on Add, ensuring the class file was added in the Solution Explorer.
Creating the workflow.
- In the Solution Explorer, right-click on Workflow1.cs, then click on View Designer.
- In the designer, right-click on onWorkflowActivated1, then click on Generate Handlers.
- Directly above the onWorkflowActivated1_Invoked method, but NOT inside of the method itself, type the following:<![CDATA[ public String initApprover = default(String);
public DateTime? initExpires = default(DateTime?);
public String initComments = default(String);]]>
- In the designer, right-click on onWorkflowActivated1, then click on Properties.
- Inside of the onWorkflowActivated1_Invoked method, type the following code:<![CDATA[ XmlSerializer serializer = new XmlSerializer(typeof(initiationFields));
XmlTextReader reader = new XmlTextReader(new System.IO.StringReader(this.workflowProperties.InitiationData));
initiationFields initFields = (initiationFields)serializer.Deserialize(reader);
this.initApprover = initFields.initApprover;
this.initExpires = initFields.initExpires;
this.initComments = initFields.initComments;]]>
- In the Solution Explorer, right-click on Workflow1.cs, then click on View Designer.
- Right-click on onWorkflowActivated1, then click on Properties.
- In the Toolbox, drag and drop a CreateTask object onto the design area, directly beneath the onWorkflowActivated1 object, from the SharePoint - Workflow Task area.
- In the Properties pane, click on the CorrelationToken property's empty field, then type "taskToken" (without quotes).
- Click on the plus sign next to the CorrelationToken property, then select Workflow1 in the OwnerActivityName property.
- Click on the TaskID property, then click on the elipses button.
- Click on the "Bind to a new member" tab."
- Select Create Field, then type "taskID" (without quotes) in the "New member name" field.
- Click on OK.
- Click on the TaskProperties property, then click on the elipses button.
- Click on the "Bind to a new member" tab."
- Select Create Field, then type "taskProperties" (without quotes) in the "New member name" field.
- Click on OK.
- Press Ctrl-Shift-S to save all of your changes.
- In the designer, right-click on createTask1, then click on Generate Handlers.
- At the top of the class file, add the following using statement:<![CDATA[using Microsoft.SharePoint.Utilities;]]>
- Somewhere in the class file, add the following method:<![CDATA[ private SPPrincipalInfo ResolveUser(String UserName)
{
return SPUtility.ResolvePrincipal(
this.workflowProperties.Web,
UserName,
SPPrincipalType.All,
SPPrincipalSource.All,
null,
false);
}]]>
- In the createTask1_MethodInvoking method, type the following code:<![CDATA[ this.taskID = Guid.NewGuid();
this.taskProperties.AssignedTo = this.ResolveUser(this.initApprover).LoginName;
this.taskProperties.Description = "Approve " +
this.workflowProperties.Item.Name + " Task Assigned to " +
this.ResolveUser(this.initApprover).DisplayName;
this.taskProperties.DueDate =
(this.initExpires != null ? this.initExpires.Value :
DateTime.Now.AddDays(7));
this.taskProperties.Title = "Approve " +
this.workflowProperties.Item.Name;
this.taskProperties.ExtendedProperties["actionStatus"] = "Approve";
this.taskProperties.ExtendedProperties["actionComments"] =
DateTime.Now.ToString() + ": " +
this.workflowProperties.OriginatorUser.Name +
" wants you to approve this document. Comment(s): " +
this.initComments + "\r\n";
this.taskProperties.SendEmailNotification = true;]]>
- Click on the Workflow1.cs [Design] tab.
- From the Toolbox, drag and drop a While to directly beneath the createTask1 object.
- In the Properties pane, click on the Condition property, then activate the drop-down list.
- Select Code Condition.
- Click on the plus sign next to Condition, then type "whileActivity1_CheckIfTaskComplete" (without quotes) in the empty Condition property field.
- Press the Enter key, this will take you back to the code view.
- Right above the whileActivity1_CheckIfTaskComplete method, NOT inside of it, type the following code:<![CDATA[ private bool blnIsTaskComplete = false;]]>
- Inside of the whileActivity1_CheckIfTaskComplete method, type the following code:<![CDATA[ e.Result = !this.blnIsTaskComplete;]]>
- Click on the Workflow1.cs [Design] tab.
- In the Toolbox, drag and drop an OnTaskChanged object directly into the whileActivity1 area.
- In the Properties pane, click on the AfterProperties property, then elipses button.
- Click on the "Bind to a new member tab", then select the Create Field option.
- In the "New member name" field, type "taskChangedAfterProperties".
- Click on OK.
- In the Properties pane, click on the BeforeProperties property, then elipses button.
- Click on the "Bind to a new member tab", then select the Create Field option.
- In the "New member name" field, type "taskChangedBeforeProperties".
- Click on OK.
- Click on the CorrelationToken property, then activate the drop-down list.
- Select taskToken from the list (NOT workflowToken).
- In the Properties pane, click on the Executor property, then elipses button.
- Click on the "Bind to a new member tab", then select the Create Field option.
- In the "New member name" field, type "taskChangedExecutor".
- Click on OK.
- In the Properties pane, click on the TaskID property, then elipses button.
- In the "Bind to existing member" tab, locate and select the taskID property.
- Click on OK.
- Press Ctrl-Shift-S to save all of your changes.
- In the designer area, right-click on onTaskChanged1, then click on Generate Handlers.
- In the onTaskChanged1_Invoked method, type the following code:<![CDATA[ this.blnIsTaskComplete =
(this.taskChangedAfterProperties.ExtendedProperties["actionStatus"].ToString() == "Approve" ||
this.taskChangedAfterProperties.ExtendedProperties["actionStatus"].ToString() == "Reject");
// If the task has expired, set it to complete:
if (this.initExpires != null &&
DateTime.Now > this.initExpires)
this.blnIsTaskComplete = true;]]>
- Click on the Workflow1.cs [Design] tab.
- From the Toolbox, drag and drop a CompleteTask object directly beneath the whileActivity1 object.
- In the Properties pane, click on the CorrelationToken property, then activate the drop-down list.
- Select taskToken.
- In the Properties pane, click on the TaskId property, then click on the elipses button.
- In the "Bind to an existing member" tab, locate and select the TaskID property.
- Click on OK.
- In the Properties pane, click on the TaskOutcome property, then click on the elipses button.
- Click on the "Bind to a new member" tab, then click on Create Field.
- In the "New member name" field, type "taskOutcome".
- Click on OK.
- Right-click on completeTask1, then click on Generate Handlers.
- In the completeTask1_MethodInvoking method, type the following code:<![CDATA[ this.taskOutcome = this.taskChangedAfterProperties.ExtendedProperties["actionStatus"].ToString();
this.taskProperties.PercentComplete = 100;]]>
- Press Ctrl-Shift-S to save all of your changes.
- Build the project by pressing F6.
Sign the project with a strong-name key and add it to the GAC.
- In the Solution Explorer, right-click on SharePointApprovalWorkflow, then click on Properties.
- Click on the Signing tab/option.
- Ensure "Sign the Assembly" is checked.
- Under "Choose a strong name key file", click on the drop-down list, then click on/select New...
- Set the "Key file name" to "SharePointApprovalWorkflow.snk" (without quotes).
- Uncheck the option to password-protect the key.
- Click on OK.
- Press Ctrl-Shift-S to save all of your changes.
- Build the project by pressing F6.
- In Windows, open/startup the Microsoft .Net Framework 2.0 Configuration MMC tool, typically from the Administrative Tools folder in the Programs menu of Start button (aka mscorcfg.msc).
- Navigate to and select My Computer.
- Click on "Manage the Assembly Cache".
- Click on "View List of Aseemblies in the Assembly Cache".
- Right-click on the Assembly Cache node in the left pane, then click on Add...
- Navigate to the bin\Debug folder where the SharePointApprovalWorkflow project compiled the assembly, typically "%HOMEPATH%\My Documents\Visual Studio 2005\Projects\SharePointApprovalWorkflow\SharePointApprovalWorkflow\bin\Debug", then select and open the SharePointApprovalWorkflow.dll assembly.
- In the right pane, locate the SharePointApprovalWorkflow assembly, then write and store the Public Key Token, as you will need this value later (you can copy it by double-clicking on it, then selecting the text from the dialog box and copying it to the clipboard).
- Close the MMC.
Back to TOC
Deploying the VS.NET workflow and InfoPath forms to SharePoint Server 2007
- In the VS.NET 2005 workflow project, click on Tools from the menu bar, then click on Code Snippets Manager.
- Click on the Add button.
- In the Language drop-down list, select XML.
- Navigate to and Open the following folder: "%ProgramFiles%\Microsoft Visual Studio 8\Xml\1033\Snippets\SharePoint Server Workflow"
- Click on OK.
Creating the Feature.xml file.
- Right-click on the SharePointApprovalWorkflow project, navigate to Add, then click on New Item.
- Select XML File, then call the file name "Feature.xml" (without quotes).
- Click on Add.
- In the code editor, place the cursor directly beneath the first line, the XML declaration line.
- Press Ctrl-K-X.
- Double-click on "SharePoint Server Workflow".
- Double-click on Feature.xml Code.
- Remove the ElementFile element/node from the XML file.
- Generate a random GUID from a website such as this one: http://www.famkruithof.net/uuid/uuidgen.
- Copy and paste the generated GUID into the ID property, replacing the GUID value currently present.
- Change the Title from "Default Title" to "Custom Approval Workflow" (without quotes).
- Set the Description property to "Custom-designed approval workflow." (without quotes).
- Press Ctrl-Shift-S to save all of your changes.
- The Feature.xml file should look something like this:<![CDATA[<!--xml version="1.0" encoding="utf-8" ?-->
<Feature Id="7d943930-f3ad-11dc-95ff-0800200c9a66"
Title="Custom Approval Workflow"
Description="Custom-designed approval workflow."
Version="12.0.0.0"
Scope="Site"
ReceiverAssembly="Microsoft.Office.Workflow.Feature, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c"
ReceiverClass="Microsoft.Office.Workflow.Feature.WorkflowFeatureReceiver"
xmlns="http://schemas.microsoft.com/sharepoint/">
<ElementManifests>
<ElementManifest Location="workflow.xml" />
</ElementManifests>
<Properties>
<Property Key="GloballyAvailable" Value="true" />
<!-- Value for RegisterForms key indicates the path to the forms relative to feature file location -->
<!-- if you don't have forms, use *.xsn -->
<Property Key="RegisterForms" Value="*.xsn" />
</Properties>
</Feature>]]>
Creating the Workflow.xml file.
- Right-click on the SharePointApprovalWorkflow project, navigate to Add, then click on New Item.
- Select XML File, then call the file name "Feature.xml" (without quotes).
- Click on Add.
- In the code editor, place the cursor directly beneath the first line, the XML declaration line.
- Press Ctrl-K-X.
- Double-click on "SharePoint Server Workflow".
- Double-click on Workflow.xml Code.
- Set the Name property to "Custom Approval Workflow" (without quotes).
- Set the Description to "Custom-designed approval workflow." (without quotes).
- Generate a random GUID from a website such as this one: http://www.famkruithof.net/uuid/uuidgen.
- Copy and paste the generated GUID into the ID property, replacing the GUID value currently present.
- Set the CodeBehindClass property to "SharePointApprovalWorkflow.Workflow1" (without quotes).
- In the CodeBesideAssembly property, replace the publicKeyToken with the copied Public Key Token obtained via the GAC earlier.
- In the Association_FormURN element, replace the associationFormURN value with the URN of the ApprovalInitiation.xsn document. To get this a) Open up InfoPath and the ApprovalInitiation.xsn document, b) click on Open when you get the security notice, c) click on Tools, then Design this Form, d) click on File, then Properties, e) copy the contents of the ID field, f) then paste this value into the Association_FormURN element.
- In the Instantiation_FormURN element, replace the associationFormURN value with the URN used in the preceding step.
- In the Task0_FormURN element, replace the existing value with the URN of the ApprovalAction.xsn document. To get this a) Open up InfoPath and the ApprovalAction.xsn document, b) click on Open when you get the security notice, c) click on Tools, then Design this Form, d) click on File, then Properties, e) copy the contents of the ID field, f) then paste this value into the Task0_FormURN element.
- Comment/remark out both the Modification_GUID_FormURN and Modification_GUID_Name elements, as we will not be using them (once the initiation is complete, there's no going back in this example/workflow).
- Press Ctrl-Shift-S to save all of your changes.
- The Workflow.xml should look something like this:<![CDATA[<!--xml version="1.0" encoding="utf-8" ?-->
<Elements xmlns="http://schemas.microsoft.com/sharepoint/">
<Workflow
Name="Custom Approval Workflow"
Description="Custom-designed approval workflow."
Id="d5df1be0-f3ae-11dc-95ff-0800200c9a66"
CodeBesideClass="SharePointApprovalWorkflow.Workflow1"
CodeBesideAssembly="SharePointApprovalWorkflow, Version=1.0.0.0, Culture=neutral, PublicKeyToken=3e823471b9dbc370"
TaskListContentTypeId="0x01080100C9C9515DE4E24001905074F980F93160"
AssociationUrl="_layouts/CstWrkflIP.aspx"
InstantiationUrl="_layouts/IniWrkflIP.aspx"
ModificationUrl="_layouts/ModWrkflIP.aspx"
StatusUrl="_layouts/WrkStat.aspx">
<Categories/>
<!-- Tags to specify InfoPath forms for the workflow; delete tags for forms that you do not have -->
<MetaData>
<Association_FormURN>urn:schemas-microsoft-com:office:infopath:ApprovalInitiation:-myXSD-2008-03-16T04-37-49</Association_FormURN>
<Instantiation_FormURN>urn:schemas-microsoft-com:office:infopath:ApprovalInitiation:-myXSD-2008-03-16T04-37-49</Instantiation_FormURN>
<Task0_FormURN>urn:schemas-microsoft-com:office:infopath:ApprovalAction:-myXSD-2008-03-16T05-02-49</Task0_FormURN>
<!--
<Modification_GUID_FormURN>modificationURN</Modification_GUID_FormURN>
<Modification_GUID_Name>Name of Modification</Modification_GUID_Name>
-->
<AssociateOnActivation>false</AssociateOnActivation>
</MetaData>
</Workflow>
</Elements>]]>
Installing the workflow in SharePoint Server 2007.
- In Windows' Explorer, navigate to the following folder: "%ProgramFiles%\\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\FEATURES"
- Create a new folder here called "CustomApprovalWorkflow" (without quotes).
- Copy and paste the following files into the CustomApprovalWorkflow folder: ApprovalAction.xsn, ApprovalInitiation.xsn, Feature.xml, and Workflow.xml
- Open up a Windows' Command Prompt.
- Type the following command: cd "%ProgramFiles%\Common Files\Microsoft Shared\web server extensions\12\BIN"
- Type the following command: stsadm -o installFeature -name CustomApprovalWorkflow -force
- Press Enter.
- You should've gotten the following message: Operation completed successfully.
- Type the following command: stsadm -o activateFeature -name CustomApprovalWorkflow -url http://URLToSharePointServer
- Ensure the URLToSharePointServer is replaced with the site URL of the SharePoint Server 2007 to where this workflow will be employed/used.
- Restart IIS by typing and entering "iisreset" (without quotes) from a Windows' Command Prompt.
Back to TOC
Using the Deployed Custom Workflow in SharePoint Server 2007
Associating a workflow with a document library.
- Locate a document library to which you'd like to associate this workflow.
- Click on the Settings menu on the Toolbar of the list/library.
- Click the Document Library Settings.
- Click on Workflow settings.
- Select on "Custom Approval Workflow".
- Call the workflow "Custom Approval Workflow" (without quotes).
- Select "New task list" from the Task List drop-down menu.
- Click on Next.
- You're now at the association form, which is the same as the initiation form (the ApprovalInitiation.xsn form). What's entered here will determine what's set by default for all new workflows initiated for this library, so ensure you leave each field blank, except for the Comments area.
- In Comments, enter "Please approve this document." (without quotes).
- Click on "Send for Approva". This will not actually send the form for approval, just save the form's values for future workflows.
Initiating a document workflow.
- Upload a test document to this library. We'll refer to this document as the "test document".
- In the library, locate the test document, and activate its drop-down menu.
- Click on Workflows from the drop-down menu.
- Click on "Custom Approval Workflow".
- In the Approver field, type in your full name, or the name of a person who has been added to SharePoint Server 2007 and is allowed to interact with workflows.
- In the Expires field, enter the date after today.
- In Comments, enter "Please approve this document." (without quotes).
- Click on "Send for Approval". The workflow status of this document should set to In Progress. If it's set to Error, please revisit the preceding steps to determine what you might've missed, and visit the section referring to fixing problems (below)
- Locate the test document in the library, then click on the In Progress link. This will allow you to view the status of this document's workflow.
- At this point, the document needs approval, so no task has been started, as it's set not to start automatically. So, under Tasks, click on the test document's link to start a task.
- This page/form is what the approver(s) should see in order to approve, reject, or revise a document. To approve this document, leave the Approval Status to Approve.
- In Comments, enter "Approved." (without quotes).
- Click on the Submit button. The workflow is now complete, as either Reject or Approve are the status values necessary to complete the workflow.
Back to TOC
If Problems Arise, and Making Changes
If changes need to be made to the VS.NET project.
Making changes to the workflow VS.NET 2005 project(s) involves re-adding the assembly to the GAC and restarting IIS.
- Make the changes in VS.NET, then recompile the project/solution.
- Open up the Microsoft .Net Framework 2.0 Configuration MMC.
- Under My Computer, click on "Manage the assemly cache".
- Click on "View List of Assemblies in the Assembly Cache".
- Locate the SharePointApprovalWorkflow assembly.
- Right-click on SharePointApprovalWorkflow, then click on Delete.
- Click on Yes.
- Right-click on Assembly Cache, then click on Add...
- Locate and open the SharePointApprovalWorkflow.dll assembly.
- Restart IIS by running "iisreset" (without quotes) from a command prompt.
If changes need to be made to the InfoPath form(s).
Making changes to the InfoPath form(s) involves changing the form(s)'s content(s), publishing and saving them, then uninstalling the reinstalling the workflow in SharePoint Server 2007. You do not need to restart IIS if you're just making changes to the InfoPath form(s).
- Open up the InfoPath form from the location where it was saved, not published. Note: the locations where InfoPath forms are saved and where they are published are two different locations altogether--NEVER modify a published InfoPath form. Instead, ALWAYS modify the original, saved form(s).
- Click on Open if you get a security notice warning.
- Click on Tools from the menu bar, then click on "Design this form". This will open the form in another instance of InfoPath. You can close the other, read-only instance.
- Make any changes then save the form.
- Click on File, from the menu bar, then click on Publish.
- Click on "To a network location...".
- Click on Next.
- Click on the Browse button, then locate and open/select the folder to which the form was published, if it's not already in the field.
- Click on OK.
- Click on Next.
- Click on Next, ensuring the user access path/field is empty.
- Click on Publish.
- Click on Close.
- Open up a Windows' Command Prompt.
- Type the following command: cd "%ProgramFiles%\Common Files\Microsoft Shared\web server extensions\12\BIN"
- Type the following command: stsadm -o uninstallFeature -name CustomApprovalWorkflow -force
- Press Enter.
- You should've gotten the following message: Operation completed successfully.
- Type the following command: stsadm -o installFeature -name CustomApprovalWorkflow -force
- Press Enter.
- You should've gotten the following message: Operation completed successfully.
Back to TOC
What's Missing from this Workflow?
This sample workflow is extremely basic and is missing several elements that you will probably want to develop in a real-world, enterprise environment. The following are just some:
- E-mails: One thing that you might want to implement is the sending of e-mail messages upon changes made to the workflow. For example, upon a new workflow initiation, you'll probably want to notify the approver(s)/assignee(s) that an approval is awaiting him or her, and provide links to the appropriate content in the HTML-encoded message. I personally use the SPUtility.SendEmail() method for this.li>
- Workflow History Logging: Another thing you'll probably want to implement is the tracking of what's being done and the status of the workflow at particular action points in the flow. For example, when an approver/assignee rejects or approves a document, you'll want to log the comments and status to the workflow's history. I personally use the Workflow's CreateHistoryEvent() method for this.
Back to TOC
Additional Information & Resources
