Documentation

Release Notes

Listed below are the release notes for the various Workflow Power Pack versions. If you have identified an issue that is not listed here then please check out the FAQ, Support Area or contact us directly.

Release notes are available for the following public releases:

 


Workflow Power Pack for SharePoint v1.2
 

Read the announcement to see what is new in this version.
 

#1004 - Code containing lookup variables cannot be validated in SP2010

Due to the manner SharePoint 2010 deals with lookup fields in custom activity validators, any custom code that contains lookup values (e.g [%Current Item:Transaction Date%]) will not be validated when a workflow is published. We believe this to be a bug in SharePoint 2010 as this works fine in SharePoint 2007.
If this is a big problem for you then you can pass in the lookup field as either parameter 1 or parameter 2 and refer to it using MyWorkflow.Parameter1.
Code that does not contain lookup fields is validated properly. Regardless of the scenario, the code does execute correctly.
 

#738 - Escaped assignments of type 'char' raise an error during syntax checking.

During the sytnax check of a SharePoint Designer workflow, the following returns an error: char c = '\\';. This is a known compiler issue, as a workaround create a string containing the escaped character and then take the first character from the string.
 

#731 - Code in Custom Code Conditions is not validated when the workflow is saved

When saving a workflow, any custom code added as part of a Workflow Action is automatically checked for syntax errors. However, SharePoint's architecture does not allow code added as part of a Condition to be validated at design time. Any syntax errors in Code Conditions will not appear until the Workflow is first executed.
 

#732 - Syntax errors related to missing Assembly references are not reported at design time

When saving a workflow, code stored as part of a Workflow Action is checked for syntax errors. Due to limitations in SharePoint's validation model the syntax is checked against a combined list of all Assembly References entered across all Web Applications. As a result, the syntax may be checked against assemblies not available on the Web Application the workflow is executed on.
 


Workflow Power Pack for SharePoint v1.1
 

Read the announcement to see what is new in this version.
 

#738 - Escaped assignments of type 'char' raise an error during syntax checking.

During the sytnax check of a SharePoint Designer workflow, the following returns an error: char c = '\\';. This is a known compiler issue, as a workaround create a string containing the escaped character and then take the first character from the string.
 

#731 - Code in Custom Code Conditions is not validated when the workflow is saved

When saving a workflow, any custom code added as part of a Workflow Action is automatically checked for syntax errors. However, SharePoint's architecture does not allow code added as part of a Condition to be validated at design time. Any syntax errors in Code Conditions will not appear until the Workflow is first executed.
 

#732 - Syntax errors related to missing Assembly references are not reported at design time

When saving a workflow, code stored as part of a Workflow Action is checked for syntax errors. Due to limitations in SharePoint's validation model the syntax is checked against a combined list of all Assembly References entered across all Web Applications. As a result, the syntax may be checked against assemblies not available on the Web Application the workflow is executed on.
 


Workflow Power Pack for SharePoint v1.0
 

Read the announcement to see what is new in this version.
 

#731 - Code in Custom Code Conditions is not validated when the workflow is saved

When saving a workflow, any custom code added as part of a Workflow Action is automatically checked for syntax errors. However, SharePoint's architecture does not allow code added as part of a Condition to be validated at design time. Any syntax errors in Code Conditions will not appear until the Workflow is first executed.
 

#732 - Syntax errors related to missing Assembly references are not reported at design time

When saving a workflow, code stored as part of a Workflow Action is checked for syntax errors. Due to limitations in SharePoint's validation model the syntax is checked against a combined list of all Assembly References entered across all Web Applications. As a result, the syntax may be checked against assemblies not available on the Web Application the workflow is executed on.