You develop a custom Sequential Workflow for MOSS 2007 using Visual Studio 2008 and use InfoPath form templates as Initiation and Task forms. You deploy the workflow as a feature and are able to enable the workflow for a Document Library as well. However, when you trigger the workflow for an item/document in the document library, it generates the following exception,

“This form cannot be opened. It is not workflow enabled.”

You will also notice that for the InfoPath forms used by the workflow, if you go to the Central Administration page -> Application Management -> Managed form templates the status in the “workflow enabled” column for the form which you uploaded shows as “No”.

The element declaration in Feature.xml file is case-sensitive since it is based on XML formatting. Even if the information provided in the file is correct and the case-sensitivity (upper or lower casing of alphabets) of the XML text is not respected you are likely to see unidentifiable issues such as this.

Verify the following settings in the feature.xml file: 

<Property Key="GloballyAvailable" Value="true" />

<Property Key="RegisterForms" Value="*.xsn" />

In order for the infopath forms to register well to the SharePoint environment we need to ensure that we have added the above RegisterForms property to the feature.xml file of the workflow feature being deployed.

Apart from this, the property named “GloballyAvailable” needs to be added to the feature properties to ensure that the infopath forms are marked as “Workflow enabled” in the Central Admin site.

If you set the value of the property named "GloballyAvailable" to "TRUE" instead of "true", you will receive the above mentioned error. Formatting this value to the correct case and redeploying the workflow feature helps resolve the error above.

Expect the following behavior when you try making changes to these properties for a workflow feature:

1. Remove RegisterForms property from the feature.xml file and deplopy workflow feature: The workflow gets deployed but the infopath forms are not registered in the “Manage Form Templates” section in the Central Admin for SharePoint.
2. Uninstall the workflow feature and revert back the above changes.
3. Now, remove the GloballyAvailable property from the feature.xml file and deploy the workflow feature: The workflow gets deployed and the infopath forms are registered in the “Manage Form Templates” section in the Central Admin for SharePoint. However the status of these infopath forms for “Workflow enabled” column is set to No.
4. Uninstall the workflow feature and revert back the above changes. Deploy the workflow feature again and it is noticed that adding back the GloballyAvailable property to the feature.xml file sets the “Workflow enabled” column value to Yes.

Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use (http://go.microsoft.com/fwlink/?LinkId=151500) for other considerations.