Resolved Issues:

• Resolved new issue from release 2.5.2 where Studio stopped responding after adding an End Workflow widget.
• Resolved issue where right-clicking sometimes resulted in an incorrect area being selected for cut/copy/paste/delete functions.

See the Known Issues and Limitations section for the latest known issues and limitations related to this release.

Update:

• Workflow Conductor has been successfully tested in Web garden environments. Using Workflow Conductor with Web gardens requires that the session state service is enabled. For more information, see the following article: http://store.bamboosolutions.com/KB/article.aspx?id=12859&cNode=0I3W2K

Resolved Issues:

• Removed the requirement to disable UAC Admin Approval Mode in Windows Server 2008 for Workflow Conductor installation and when using the Simple Publishing Method for workflow deployment (still required for older Solution Deployment Method).
• Resolved error when using Start Another Workflow in as part of some Request Approval processes.
• SharePoint lookup columns in sub-sites are now available as drop-down selections in widgets and standard Workflow Conductor lookups.
• Set field value widget now shows the values for a field when selecting a SharePoint lookup field in sub-site.
• Line breaks now show correctly in the Description field for the Request Approval widget.
• Resolved issue where Studio diagram could become grayed out when using a large number of nested Conditional Branch widgets.

See the Known Issues and Limitations section for the latest known issues and limitations related to this release.

Resolved Issues:

• Corrected behavior where the Request Approval widget followed the "Rejected" path when approved by a system account without an assigned email address.
• Resolved issue where tabs on the template gallery stopped responding when the "Manage Templates" tab or filters were used after upgrading from an earlier version of Workflow Conductor.

See the Known Issues and Limitations section for the latest known issues and limitations related to this release.

New Features:

• Customizable InfoPath forms for Request Approval, Request Feedback, and Collect Data from User task forms (requires InfoPath Forms Services).
• New workflow template gallery features:
  • View a personalized gallery of workflow templates you created.
  • Share workflow templates with other users.
  • Access workflow templates featured by administrators.
• Support for site workflows, which can be started without a specific list or library item.
• Advanced per-widget error handling options, including the ability to pause a workflow until an error can be corrected.
• New widgets:
  • Create Column – Create a new column in a list or library.
  • Move Item – Move an item from one list or library to another.
  • Subscribe User to Alert – Subscribe a user to alerts for a SharePoint list or item.
• New Conditional Branch widget conditions that branch the workflow based on results of the following conditional checks:
  • Is a role assigned to a user
  • Is a date/time within a date range
  • Is a user a member of a SharePoint group
  • Is a user a member of an Active Directory group
• Updated Request Feedback widget options that allow specifying the number of feedback responses required.

Resolved Issues:

• Resolved multiple issues related to Cut/Copy/Paste/Delete functions in Workflow Conductor Studio not selecting the correct area or item.
• If a workflow stops due to an error, it is no longer marked as “Canceled”, but is now correctly marked as “Errored”. It is also now shown under the correct category in the Workflow Reports Web Part.
• Group owner is now included when using Send Email addressed to a group.
• Added small delay between loops in Repeat for Each Item to prevent SharePoint’s workflow queue from getting overwhelmed after 10 or more items were processed.
• When selecting values for Date/Time columns that are configured as "Date Only”, the date picker no longer shows the time selector for date properties in the Update Item and Wait for Field Change widgets, or when setting a standard lookup field in any widget.
• Resolved issue where Add User to AD Group widgets did not run correctly if the “Group” property was defined using a variable.
• Fixed issue where some users upgrading from 2.0 or earlier would get stuck on the “Loading” screen when trying to apply updated settings in a previous workflow’s Create Item widget.
• Line breaks in approval comments stored in variables are now properly retained and appear correctly when inserted in emails.
• Fixed JavaScript error when using the Create Item widget on a survey list with special characters in the Subject field.
• Zoom In/Out options now work correctly for large imported templates.
• The Repeat While widget now works correctly when the "Loop Delay" property is set using a lookup.
• Fixed an issue that could cause an error in some instances if regional settings for date/time were different than the defined user’s machine when using “Run As” in Delay Until, Request Approval, Request Feedback, Collect Data from User, and Create Task.
• The Copy Item widget now works correctly with Bamboo's Custom Identifier Column when using the "Automatically Generate Unique ID" option on the target list.
• The Send Email widget now works correctly on file attachments over 8MB.  

See the Known Issues and Limitations section for the latest known issues and limitations related to this release.

• Widgets configured with lookups to SharePoint Date and Time columns will fail if the regional settings on the site where the workflow runs are different than the regional settings on the server. Affected widgets include Delay Until, Request Approval, Request Feedback, Collect Data From User, and Create Task.
• A JavaScript error is displayed when configuring a Create Item widget for a Survey list that includes a question with multiple lines of text.
• A JavaScript error is displayed when configuring Set Item Permissions and Update Item widgets with an External List lookup to a Survey list where the selected filter field is a question with multiple lines of text.

See the Known Issues and Limitations section for the latest known issues and limitations related to this release.

Resolved Issues:

• Fixes an issue with runtime widget error logging when creating a new database in Workflow Conductor 2.1.

See the Known Issues and Limitations section for the latest known issues and limitations related to this release.

New Features:

• Custom database names – The Workflow Conductor database now supports custom naming, allowing multiple instances of the database to reside on a single SQL Server.
• Updated Studio Toolbar – Workflow Conductor Studio features an improved ribbon-style menu for easy configuration and access to configured site navigation/breadcrumbs.
• Updated Studio Settings UI – The right pane interface includes new features and now supports smaller resolutions.
• Improved lookups – “Site Collection” properties in widgets can now be defined using lookups to stored values. “Current List” has been added as an option to the dropdown menu for lookups.
• Configurable Per-Widget Task Emails – Various task emails for “Request Approval”, “Request Feedback”, and “Collect Data from User” can now configured separately for each widget, including task-specific lookups (ex. “Task Description”). Default email content can be defined in Central Administration.
• Increased Widget Scope – The following widgets now support lookups to other Site Collections/Sites/Lists:
  • Set Field Value
  • Add Column
  • Repeat for Each Item
• Custom/Blank Site Creation – “Create Site” now supports Bamboo custom site templates and “blank” templates.
• Support for Bamboo Custom Columns – Workflow Conductor now supports the use of read/write activities for Bamboo’s Custom Columns.
• The “Save” and “Save As” functions have been combined to eliminate confusion and minimize lost changes.
• The Workflow Conductor Control Panel in Central Administration now features breadcrumb links for easier navigation.
• “User and Group Management” has been added to widget categories.

See the Known Issues and Limitations section for the latest known issues and limitations related to this release.

Resolved Issues:

• Workflows that contain lookups to "Current Site Collection" and "Current Site" may not resolve the site or site collection correctly when associated to a list in a different site or site collection.
• Other general bug fixes.

See the Known Issues and Limitations section for the latest known issues and limitations related to this release.

New Features:

• New Widget - Run PowerShell Script: Run Windows PowerShell scripts on the local server.
• New Widget - Update User Info: Update SharePoint user profile properties.
• New Widget - Update AD Account: Update Active Directory account information.
• New Widget - Add Column: Add an existing site column to a list or library.
• New Widget - Set Item Permissions: Set (or remove) item-level permissions.
• New Widget - Create AD Group: Create a new Active Directory group.
• New Widget - Remove AD Group: Remove a group from Active Directory.
• New Widget - Remove SharePoint Group: Remove a SharePoint site group.
• New Widget - Create Site: Create a new SharePoint site.
• New Widget - Delete Site: Delete a SharePoint site.
• New Widget - Set Site Permissions: Set the permissions for a SharePoint site.
• New workflow deployment methods:
  • Simple Publishing: Publish workflows without recycling the application pool. Workflows can be published locally to the list or as reusable workflows to the site or site collection that can be associated with any list or library in that site or site collection.
  • Solution Deployment: Deploy workflows as farm workflow solutions just as in previous versions of Workflow Conductor. Workflows can still be deployed immediately from Conductor Studio or at a scheduled time.
  • Manual workflow deployment: Workflows deployed using Solution Deployment that are scheduled can now be manually deployed at any time from the Workflow Conductor Control Panel. 
• With the new Simple Publishing deployment method, easily create new workflow versions by overwriting existing workflows of the same name. Workflows already in progress will be allowed to complete and new workflow instances will use the new workflow version.
• Enhanced lookup functionality:
  • Ability to define the site collection property using a lookup in the Create Item and Delete Item widgets.
  • Set the target group for the Add User to AD Group widget using a lookup.
  • Choose a display format for the results of user lookups.
• Improved Template Gallery user interface that allows filtering and sorting.
• Send Email widget now supports attachments.
• New options for notifying workflow initiators, designers, or any user, group or e-mail address about workflow errors.
• Includes sample manual installation scripts in the "misc" folder of the installation package.

Resolved Issues:

• If you start a workflow in Simulation Mode, the Repeat While widget Loop Delay property is not set to "0".
• When upgrading Workflow Conductor, the database configuration may fail if the previous version's Widget Category settings were modified from the default.
• Other general bug fixes.

See the Known Issues and Limitations section for the latest known issues and limitations related to this release.

New Features:

• Added support for users in Active directory sub-domains to user lookups, e-mail recipients, and Active Directory widgets.

Resolved Issues:

• If a Request Approval Widget is configured to require multiple approvers, the box to enter the number of approvers is missing in Workflow Conductor 1.6.
• Some users may see the following error when clicking the item link at the top of a Request Approval or Request Feedback task form: "The webpage cannot be found"
• When exporting data from the View Workflow Status page, the date and time format is incorrect.
• Some users may see the following error message when starting Studio for the first time: "An unexpected error has occurred."
• Other general bug fixes.

See the Known Issues and Limitations section for the latest known issues and limitations related to this release.

• New Widget - Collect Data From User: Collect data from a user mid-workflow with a SharePoint task.
• New Widget - Create SharePoint Group: Create a new SharePoint group for a site in a site collection.
• New Widget - Remove User from AD Group: Remove a user from an Active Directory group.
• New Widget - Remove User from SP Group: Remove a user from a SharePoint group.
• Two new pre-defined conditions for the Conditional Branch Widget:
  • Current item was created between these dates.
  • Current item was modified between these dates.
• External lookups now support lookups for Site, List, and Field names.
• Uses new Setup program.

• If a task due date is set to the current date using a workflow initiation form Date/Time field formatted as Date only, the task due date is not set.
• Conductor Studio calendar control does not format time display according to regional settings.
• Send Email does not work if the recipient property is a lookup to a SharePoint Person/Group column that allows multiple selections.
• Some widgets fail if widget properties are lookups to FBA users.
• Add User to AD Group fails if the Active Directory group name contains special characters.
• Update Item, Delete Item, Start Another Workflow, and Set Field Value Widgets will fail if the target is an External List Lookup to an item in another site collection using a date/time condition.
• Some Widgets fail if the workflow is run on a Document Set or a folder in a document library.
• Rich content editor in Conductor Studio shows error message when pasting text as HTML.
• In order to save the Access Accounts settings, you must first fill in the SQL Server name in General Settings. Details  
• Other general bug fixes.

See the Known Issues and Limitations section for the latest known issues and limitations related to this release.

• Initial release for Microsoft SharePoint Foundation 2010 and Microsoft SharePoint Server 2010.

Resolved Issues:
The following known issues in Workflow Conductor 1.5 for SharePoint 2007 were fixed in this release:

• Link to item on task forms incorrect for sub-sites.
• Error sometimes displayed when Studio diagram is refreshed after successful workflow deployment.
• Saved property values are not displayed when you edit the Run As > Other widget property.
• IIS reset required to view Active Directory settings after installing and configuring Workflow Conductor for the first time.
• Repeat For Each Item start and stop conditions do not match date values.
• If you use a Run Parallel widget with an Update Item in one branch and a Set Approval Status in the other, the item Approval Status will always be set to "Pending" no matter what is specified in the Set Approval Status widget.
• In Update Item, cannot change the "Site" property selection if the widget is configured to update another item in the Current Site.

See the Known Issues and Limitations section for the latest known issues and limitations related to this release.

Limitations:

• The Web Application feature Bamboo Workflow Conductor Web.config Modifications V2.5 may need to be deactivated and reactivated after Central Admin after upgrading from a previous version.

Known Issues:

• Users upgrading from previous versions may experience problems publishing new workflows. Manually deactivating then reactivating the Web Application feature labeled “Bamboo Workflow Conductor Web.config Modifications V2.5” and the Site Collection Feature “Bamboo Workflow Conductor Studio” should resolve these issues.
• When reassigning a task or requesting a change, users may have to click the “Submit” button twice before it responds if they checked the assignee name using "Enter" on the keyboard.
• When opening a Workflow Conductor task (such as an approval or feedback task) from within a Microsoft Office application, the task form fields are blank and the form cannot be completed. Opening the task from other locations still works correctly.
• Widgets can be dropped into invalid areas of the Request Approval widget, causing workflows to display an error message.
• In some cases, Workflow Conductor Web Part features may need to be manually deactivated and re-activated when upgrading if Web Parts are already being used on a page(s).
• Workflows fail when attempting to use Check In, Check Out, or Discard Check Out on items in the workflow Tasks list. 
• Update Item/Set Field Value widgets will not work on a Bamboo Custom Identifier Column if the “Automatically Generate Unique ID” option is enabled.
• Workflows that contain a Collect Data from User widget are canceled when run on a list in another site collection.
• If a Simple Publishing workflow uses a workflow initialization form field that contains a space in the form field name, any default value configured for the field will not be displayed in the workflow start page.
• If a workflow is in progress and a user clicks the "Workflow is committing..." message in the workflow status page, an error message is displayed.
• In the My Workflows and My Workflow Tasks Web Parts, version numbers will appear after the task name when a new version of a Simple Publishing workflow is published after the task is created.
• If a workflow that contains a lookup to a number or % column is deployed to a Document Library in a Meeting site, the workflow will be canceled if the column is empty.
• If a workflow initialization form Date and Time field is configured with a default value that includes a time, the time may not be displayed correctly in the workflow start page.
• If a Simple Publishing workflow with a Start Another Workflow widget is edited and published to a different scope, workflow initialization form values are not updated. For example, if the workflow was published to the list and then updated and published to the site, the Start Another Workflow widget retains its previous workflow initialization form values.
• After upgrading to Workflow Conductor 2.0 or later, a workflow deployed in Workflow Conductor 1.5 that contains a Create AD Account widget configured with a lookup from an initialization form Choice drop-down field will add a "]" to the end of the lookup when the workflow runs.
• Workflow is canceled if a Remove AD Group widget attempts to remove a group in an OU level lower than the one specified in the LDAP path.
• In the Template Gallery, cannot filter for Created By when the filter contains special characters.
• If a Simple Publishing workflow is associated to a list with an association name different than the workflow name, the workflow start page will display the workflow name instead of the association name.
• If you attempt to attach a Document Set in a Send Email widget, the workflow will be canceled.
• Some Widgets and task forms may not work correctly on German-language installations.
• The Repeat For Each Item widget "Start Item" condition does not work when using the "Is Null" operator with a Date/Time or Person/Group column.
• When upgrading Workflow Conductor, workflows that are "In Progress" and waiting for Delay For, Delay Until, Wait For Field Change, Request Approval, Or Request Feedback widgets do not complete after upgrading to Conductor 1.5 or higher.
• Saved property values are not displayed when you edit the Access SP via REST widget properties.
• If a Set Approval Status widget is configured to Run As "Initiator" or "Other", the item shows as Modified By "System Account".
• In some cases, the Approval Status of an item is not set properly for workflows deployed with the Start Option "Start this workflow to approve publishing a major version of an item."
• In the View Workflow Status page, "Starts With", "Ends With", "Equal To", and "Not Equal To" filters do not work on the Workflow Name and List columns.
• Set Field Value can incorrectly set a Person/Group (Person only) column to a SharePoint group name.

Limitations:

• When opening a workflow template created in Workflow Conductor version 1.6 or earlier in version 2.5 or later, some values for the Create Item widget may need to be re-entered before deploying the workflow again.
• Integrated task buttons in Microsoft Outlook are available for SharePoint Server 2010 only; SharePoint Foundation 2010 does not support this feature.
• A Bamboo KPI Custom Column field may show a blank value for a task list item if that item is updated using the Complete Task, Create Task, or Copy Item widgets.
• When editing a workflow template created in Workflow Conductor 1.6.1 after upgrading to 2.0, Create Item widget properties are not displayed correctly. Workaround: Re-enter the widget properties and save the template.
• After upgrading to Workflow Conductor 2.0, workflow solutions that were scheduled for deployment in the previous version but had not yet been deployed are not deployed at the scheduled time after the upgrade. This is because the workflow deployment method is changed to Simple Publishing in Conductor 2.0. The workflow can be manually deployed in the Workflow Solution Management page in the Workflow Conductor Control Panel.
• If a workflow with a Set Field Value widget is created on a Document Library and later associated to another list type, values set using the {Current Item:Name} lookup may not work correctly if the "Name" column in the new list was created manually and is not the default SharePoint "Name" column.
• An error page is displayed if a workflow is associated with a Bamboo workflow task content type.
• Some SharePoint site themes do not work well with Conductor Studio.
• The full account name must be used to lookup an FBA user in the Conductor Studio User Lookup form.
• Cannot assign a Request Approval or Request Feedback task to a user in another site collection who is not also in the current site collection.
• Create Item cannot create an item in a list name that includes an apostrophe (').
• Send Email does not work if the recipient property is a lookup to a SharePoint group or a Person/Group column allowing multiple selections that contains a group in another site collection.
• You must disable UAC Admin Approval Mode or turn off UAC to run Conductor on Windows Server 2008.

Known Issues:

• Widgets can be dropped into invalid areas of “Request Approval” widget, causing workflows to display an error message.
• In some cases, Workflow Conductor Web Part features may need to be manually deactivated and re-activated when upgrading if Web Parts are already being used on a page(s).
• Workflows fail when attempting to use “Check In”, “Check Out”, or “Discard Check Out” on the workflow task list.
• Copy Item/Update Item/Set Field Value widgets will not work on a Bamboo Custom Identifier Column if the “Automatically Generate Unique ID” option is enabled.
• The Zoom In/Out viewing options may not work correctly on some larger imported templates.
• The “Repeat While” widget may fail if the “Loop Delay” property value is set using a lookup.
• Workflows that contain a Collect Data From User widget are canceled when run on a list in another site collection.
• If a Simple Publishing workflow uses a workflow initialization form field that contains a space in the form field name, any default value configured for the field will not be displayed in the workflow start page.
• If a workflow is in progress and a user clicks the "Workflow is committing..." message in the workflow status page, an error message is displayed.
• In the My Workflows and My Workflow Tasks Web Parts, version numbers will appear after the task name when a new version of a Simple Publishing workflow is published after the task is created.
• If a workflow that contains a lookup to a number or % column is deployed to a Document Library in a Meeting site, the workflow will be canceled if the column is empty.
• If a workflow initialization form Date and Time field is configured with a default value that includes a time, the time may not be displayed correctly in the workflow start page.
• If a Simple Publishing workflow with a Start Another Workflow widget is edited and published to a different scope, workflow initialization form values are not updated. For example, if the workflow was published to the list and then updated and published to the site, the Start Another Workflow widget retains its previous workflow initialization form values.
• After upgrading to Workflow Conductor 2.0, a workflow deployed in Workflow Conductor 1.5 that contains a Create AD Account widget configured with a lookup from an initialization form Choice drop-down field will add a "]" to the end of the lookup when the workflow runs.
• Workflow is canceled if a Remove AD Group widget attempts to remove a group in an OU level lower than the one specified in the LDAP path.
• In the Template Gallery, cannot filter for Created By when the filter contains special characters.
• If a Simple Publishing workflow is associated to a list with an association name different than the workflow name, the workflow start page will display the workflow name instead of the association name.
• Workflow is canceled if a Send Email widget attempts to send an attachment 8MB or larger.
• If you attempt to attach a Document Set in a Send Email widget, the workflow will be canceled.
• Some Widgets and task forms may not work correctly on German-language installations.
• The Repeat For Each Item widget "Start Item" condition does not work when using the "Is Null" operator with a Date/Time or Person/Group column.
• When upgrading Workflow Conductor, workflows that are "In Progress" and waiting for Delay For, Delay Until, Wait For Field Change, Request Approval, Or Request Feedback widgets do not complete after upgrading to Conductor 1.5 or higher.
• Saved property values are not displayed when you edit the Access SP via REST widget properties.
• If a Set Approval Status widget is configured to Run As "Initiator" or "Other", the item shows as Modified By "System Account".
• In some cases, the Approval Status of an item is not set properly for workflows deployed with the Start Option "Start this workflow to approve publishing a major version of an item."
• In the View Workflow Status page, "Starts With", "Ends With", "Equal To", and "Not Equal To" filters do not work on the Workflow Name and List columns.
• Set Field Value can incorrectly set a Person/Group (Person only) column to a SharePoint group name.

Limitations:

• Integrated task buttons in Microsoft Outlook are not available for SharePoint Foundation (Server only).
• A Bamboo KPI Custom Column field may show a blank value for a task list item if that item is updated using the Complete Task, Create Task, or Copy Item widgets.
• When editing a workflow template created in Workflow Conductor 1.6.1 after upgrading to 2.0, Create Item widget properties are not displayed correctly. Workaround: Re-enter the widget properties and save the template.
• After upgrading to Workflow Conductor 2.0, workflow solutions that were scheduled for deployment in the previous version but had not yet been deployed are not deployed at the scheduled time after the upgrade. This is because the workflow deployment method is changed to Simple Publishing in Conductor 2.0. The workflow can be manually deployed in the Workflow Solution Management page in the Workflow Conductor Control Panel.
• If a workflow with a Set Field Value widget is created on a Document Library and later associated to another list type, values set using the {Current Item:Name} lookup may not work correctly if the "Name" column in the new list was created manually and is not the default SharePoint "Name" column.
• An error page is displayed if a workflow is associated with a Bamboo workflow task content type.
• Some SharePoint site themes do not work well with Conductor Studio.
• The full account name must be used to lookup an FBA user in the Conductor Studio User Lookup form.
• Cannot assign a Request Approval or Request Feedback task to a user in another site collection who is not also in the current site collection.
• Create Item cannot create an item in a list name that includes an apostrophe (').
• Send Email does not work if the recipient property is a lookup to a SharePoint group or a Person/Group column allowing multiple selections that contains a group in another site collection.
• You must disable UAC Admin Approval Mode or turn off UAC to run Conductor on Windows Server 2008.

• Workflows that contain a Collect Data From User widget are canceled when run on a list in another site collection.
• If a Simple Publishing workflow uses a workflow initialization form field that contains a space in the form field name, any default value configured for the field will not be displayed in the workflow start page.
• If a workflow is in progress and a user clicks the "Workflow is committing..." message in the workflow status page, an error message is displayed.
• In the My Workflows and My Workflow Tasks Web Parts, version numbers will appear after the task name when a new version of a Simple Publishing workflow is published after the task is created.
• If a workflow that contains a lookup to a number or % column is deployed to a Document Library in a Meeting site, the workflow will be canceled if the column is empty.
• If a workflow initialization form Date and Time field is configured with a default value that includes a time, the time may not be displayed correctly in the workflow start page.
• If a Simple Publishing workflow with a Start Another Workflow widget is edited and published to a different scope, workflow initialization form values are not updated. For example, if the workflow was published to the list and then updated and published to the site, the Start Another Workflow widget retains its previous workflow initialization form values.
• After upgrading to Workflow Conductor 2.0, a workflow deployed in Workflow Conductor 1.5 that contains a Create AD Account widget configured with a lookup from an initialization form Choice drop-down field will add a "]" to the end of the lookup when the workflow runs.
• Workflow is canceled if a Remove AD Group widget attempts to remove a group in an OU level lower than the one specified in the LDAP path.
• In the Template Gallery, cannot filter for Created By when the filter contains special characters.
• If a Simple Publishing workflow is associated to a list with an association name different than the workflow  name, the workflow start page will display the workflow name instead of the association name.
• Workflow is canceled if a Send Email widget attempts to send an attachment 8MB or larger.
• If you attempt to attach a Document Set in a Send Email widget, the workflow will be canceled.
• Some Widgets and task forms may not work correctly on German-language installations.
• The Repeat For Each Item widget "Start Item" condition does not work when using the "Is Null" operator with a Date/Time or Person/Group column.
• When upgrading Workflow Conductor, workflows that are "In Progress" and waiting for Delay For, Delay Until, Wait For Field Change, Request Approval, Or Request Feedback widgets do not complete after upgrading to Conductor 1.5 or higher.
• Saved property values are not displayed when you edit the Access SP via REST widget properties.
• If a Set Approval Status widget is configured to Run As "Initiator" or "Other", the item shows as Modified By "System Account".
• In some cases, the Approval Status of an item is not set properly for workflows deployed with the Start Option "Start this workflow to approve publishing a major version of an item."
• In the View Workflow Status page, "Starts With", "Ends With", "Equal To", and "Not Equal To" filters do not work on the Workflow Name and List columns.
• Set Field Value can incorrectly set a Person/Group (Person only) column to a SharePoint group name.

• When editing a workflow template created in Workflow Conductor 1.6.1 after upgrading to 2.0, Create Item widget properties are not displayed correctly. Workaround: Re-enter the widget properties and save the template.
• After upgrading to Workflow Conductor 2.0, workflow solutions that were scheduled for deployment in the previous version but had not yet been deployed are not deployed at the scheduled time after the upgrade. This is because the workflow deployment method is changed to Simple Publishing in Conductor 2.0. The workflow can be manually deployed in the Workflow Solution Management page in the Workflow Conductor Control Panel.
• If a workflow with a Set Field Value widget is created on a Document Library and later associated to another list type, values set using the {Current Item:Name} lookup may not work correctly if the "Name" column in the new list was created manually and is not the default SharePoint "Name" column.
• An error page is displayed if a workflow is associated with a Bamboo workflow task content type.
• Some SharePoint site themes do not work well with Conductor Studio.
• The full account name must be used to lookup an FBA user in the Conductor Studio User Lookup form.
• Cannot assign a Request Approval or Request Feedback task to a user in another site collection who is not also in the current site collection.
• Create Item cannot create an item in a list name that includes an apostrophe (').
• Send Email does not work if the recipient property is a lookup to a SharePoint group or a Person/Group column allowing multiple selections that contains a group in another site collection.
• You must disable UAC Admin Approval Mode or turn off UAC to run Conductor on Windows Server 2008.

• Some Widgets and task forms may not work correctly on German-language installations.
• When upgrading Workflow Conductor, the database configuration may fail if the previous version's Widget Category settings were modified from the default. Details 
• When upgrading Workflow Conductor, workflows that are "In Progress" and waiting for Delay For, Delay Until, Wait For Field Change, Request Approval, Or Request Feedback widgets do not complete after upgrading to Conductor 1.5.
• If you start a workflow in Simulation Mode, the Repeat While widget Loop Delay property is not set to "0".
• In some cases, the Approval Status of an item is not set properly for workflows deployed with the Start Option "Start this workflow to approve publishing a major version of an item."
• If a Set Approval Status widget is configured to Run As "Initiator" or "Other", the item shows as Modified By "System Account".
• The Repeat For Each Item widget "Start Item" condition does not work when using the "Is Null" operator with a Date/Time or Person/Group column.
• Set Field Value can incorrectly set a Person/Group (Person only) column to a SharePoint group name.
• Saved property values are not displayed when you edit the Access SP via REST widget properties.
• In the View Workflow Status page, "Starts With", "Ends With", "Equal To", and "Not Equal To" filters do not work on the Workflow Name and List columns.

• You must disable UAC Admin Approval Mode or turn off UAC to run Conductor on Windows Server 2008. Details 
• Some SharePoint site themes do not work well with Conductor Studio.
• Send Email does not work if the recipient property is a lookup to a SharePoint group or a Person/Group column allowing multiple selections that contains a group in another site collection.
• Create Item cannot create an item in a list name that includes an apostrophe (').
• Cannot assign a Request Approval or Request Feedback task to a user in another site collection who is not also in the current site collection.
• The full account name must be used to lookup an FBA user in the Conductor Studio User Lookup form.
• The Wait For Field Change widget does not support lookups for Yes/No and Choice columns.
• This product can be migrated from SharePoint 2007 to SharePoint 2010. However, there are limitations to the migration procedure. Read KB.12627: How to Migrate Bamboo Products from SharePoint 2007 to SharePoint 2010 for more information.

• When upgrading Workflow Conductor, the database configuration may fail if the previous version's Widget Category settings were modified from the default. Details 
• When upgrading Workflow Conductor, workflows that are "In Progress" and waiting for Delay For, Delay Until, Wait For Field Change, Request Approval, Or Request Feedback widgets do not complete after upgrading to Conductor 1.5.
• If you start a workflow in Simulation Mode, the Repeat While widget Loop Delay property is not set to "0".
• In some cases, the Approval Status of an item is not set properly for workflows deployed with the Start Option "Start this workflow to approve publishing a major version of an item."
• If a Set Approval Status widget is configured to Run As "Initiator" or "Other", the item shows as Modified By "System Account".
• The Repeat For Each Item widget "Start Item" condition does not work when using the "Is Null" operator with a Date/Time or Person/Group column.
• Set Field Value can incorrectly set a Person/Group (Person only) column to a SharePoint group name.
• Saved property values are not displayed when you edit the Access SP via REST widget properties.
• In the View Workflow Status page, "Starts With", "Ends With", "Equal To", and "Not Equal To" filters do not work on the Workflow Name and List columns.

• You must disable UAC Admin Approval Mode or turn off UAC to run Conductor on Windows Server 2008. Details 
• Some SharePoint site themes do not work well with Conductor Studio.
• Send Email does not work if the recipient property is a lookup to a SharePoint group or a Person/Group column allowing multiple selections that contains a group in another site collection.
• Create Item cannot create an item in a list name that includes an apostrophe (').
• Cannot assign a Request Approval or Request Feedback task to a user in another site collection who is not also in the current site collection.
• The full account name must be used to lookup an FBA user in the Conductor Studio User Lookup form.
• The Wait For Field Change widget does not support lookups for Yes/No and Choice columns.
• This product can be migrated from SharePoint 2007 to SharePoint 2010. However, there are limitations to the migration procedure. Read KB.12627: How to Migrate Bamboo Products from SharePoint 2007 to SharePoint 2010 for more information.

• When upgrading Workflow Conductor, the database configuration may fail if the previous version's Widget Category settings were modified from the default. Details
• When upgrading Workflow Conductor, workflows that are "In Progress" and waiting for Delay For, Delay Until, Wait For Field Change, Request Approval, Or Request Feedback widgets do not complete after upgrading to Conductor 1.5 or higher.
• If you start a workflow in Simulation Mode, the Repeat While widget Loop Delay property is not set to "0".
• In some cases, the Approval Status of an item is not set properly for workflows deployed with the Start Option "Start this workflow to approve publishing a major version of an item."
• If a Set Approval Status widget is configured to Run As "Initiator" or "Other", the item shows as Modified By "System Account".
• The Repeat For Each Item widget "Start Item" condition does not work when using the "Is Null" operator with a Date/Time or Person/Group column.
• Set Field Value can incorrectly set a Person/Group (Person only) column to a SharePoint group name.
• Saved property values are not displayed when you edit the Access SP via REST widget properties.
• In the View Workflow Status page, "Starts With" and "Ends With" filters do not work on the Workflow Name and List columns.

Limitations:

• You must disable UAC Admin Approval Mode or turn off UAC to run Conductor on Windows Server 2008. Details 
• Some SharePoint site themes do not work well with Conductor Studio.
• Send Email does not work if the recipient property is a lookup to a SharePoint group or a Person/Group column that allows multiple selections.
• Create Item cannot create an item in a list name that includes an apostrophe (').
• Create Item can only set one value for a Lookup column that allows multiple selections.
• Cannot assign a Request Approval or Request Feedback task to a user in another site collection who is not also in the current site collection.
• The Wait For Field Change widget does not support lookups for Yes/No and Choice columns.
• The full account name must be used to lookup an FBA user in the Conductor Studio User Lookup form.
• This product can be migrated from SharePoint 2007 to SharePoint 2010. However, there are limitations to the migration procedure. Read KB.12627: How to Migrate Bamboo Products from SharePoint 2007 to SharePoint 2010 for more information.

New Features:

• Custom database names – The Workflow Conductor database now supports custom naming, allowing multiple instances of the database to reside on a single SQL Server.
• Updated Studio Toolbar – Workflow Conductor Studio features an improved ribbon-style menu for easy configuration and access to configured site navigation/breadcrumbs.
• Updated Studio Settings UI – The right pane interface includes new features and now supports smaller resolutions.
• Improved lookups – “Site Collection” properties in widgets can now be defined using lookups to stored values. “Current List” has been added as an option to the dropdown menu for lookups.
• Configurable Per-Widget Task Emails – Various task emails for “Request Approval”, “Request Feedback”, and “Collect Data from User” can now configured separately for each widget, including task-specific lookups (ex. “Task Description”). Default email content can be defined in Central Administration.
• Increased Widget Scope – The following widgets now support lookups to other Site Collections/Sites/Lists:
  • Set Field Value
  • Add Column
  • Repeat for Each Item
• Custom/Blank Site Creation – “Create Site” now supports Bamboo custom site templates and “blank” templates.
• Support for Bamboo Custom Columns – Workflow Conductor now supports the use of read/write activities for Bamboo’s Custom Columns.
• The “Save” and “Save As” functions have been combined to eliminate confusion and minimize lost changes.
• The Workflow Conductor Control Panel in Central Administration now features breadcrumb links for easier navigation.
• “User and Group Management” has been added to widget categories.

See the Known Issues and Limitations section for the latest known issues and limitations related to this release.

Resolved Bugs:

• Workflows that contain lookups to "Current Site Collection" and "Current Site" may not resolve the site or site collection correctly when associated to a list in a different site or site collection.
• Other general bug fixes.

See the Known Issues and Limitations section for the latest known issues and limitations related to this release.

New Features:

• New Widget - Run PowerShell Script: Run Windows PowerShell scripts on the local server.
• New Widget - Update User Info: Update SharePoint user profile properties.
• New Widget - Update AD Account: Update Active Directory account information.
• New Widget - Add Column: Add an existing site column to a list or library.
• New Widget - Set Item Permissions: Set (or remove) item-level permissions.
• New Widget - Create AD Group: Create a new Active Directory group.
• New Widget - Remove AD Group: Remove a group from Active Directory.
• New Widget - Remove SharePoint Group: Remove a SharePoint site group.
• New Widget - Create Site: Create a new SharePoint site.
• New Widget - Delete Site: Delete a SharePoint site.
• New Widget - Set Site Permissions: Set the permissions for a SharePoint site.
• New workflow deployment methods:
  • Simple Publishing: Publish workflows without recycling the application pool. Workflows can be published locally to the list or as reusable workflows to the site or site collection that can be associated with any list or library in that site or site collection.
  • Solution Deployment: Deploy workflows as farm workflow solutions just as in previous versions of Workflow Conductor. Workflows can still be deployed immediately from Conductor Studio or at a scheduled time.
  • Manual workflow deployment: Workflows deployed using Solution Deployment that are scheduled can now be manually deployed at any time from the Workflow Conductor Control Panel. 
• With the new Simple Publishing deployment method, easily create new workflow versions by overwriting existing workflows of the same name. Workflows already in progress will be allowed to complete and new workflow instances will use the new workflow version.
• Enhanced lookup functionality:
  • Ability to define the site collection property using a lookup in the Create Item and Delete Item widgets.
  • Set the target group for the Add User to AD Group widget using a lookup.
  • Choose a display format for the results of user lookups.
• Improved Template Gallery user interface that allows filtering and sorting.
• Send Email widget now supports attachments.
• New options for notifying workflow initiators, designers, or any user, group or e-mail address about workflow errors.
• Includes sample manual installation scripts in the "misc" folder of the installation package.

Resolved Bugs:

• If you start a workflow in Simulation Mode, the Repeat While widget Loop Delay property is not set to "0".
• When upgrading Workflow Conductor, the database configuration may fail if the previous version's Widget Category settings were modified from the default.
• Other general bug fixes.

See the Known Issues and Limitations section for the latest known issues and limitations related to this release.

New Features:

• Added support for users in Active directory sub-domains to user lookups, e-mail recipients, and Active Directory widgets.

Resolved Bugs:

• If a Request Approval Widget is configured to require multiple approvers, the box to enter the number of approvers is missing in Workflow Conductor 1.6.
• Some users may see the following error when clicking the item link at the top of a Request Approval or Request Feedback task form: "The webpage cannot be found"
• When exporting data from the View Workflow Status page, the date and time format is incorrect.
• Some users may see the following error message when starting Studio for the first time: "An unexpected error has occurred."
• Other general bug fixes.

See the Known Issues and Limitations section for the latest known issues and limitations related to this release.

• New Widget - Collect Data From User: Collect data from a user mid-workflow with a SharePoint task.
• New Widget - Create SharePoint Group: Create a new SharePoint group for a site in a site collection.
• New Widget - Remove User from AD Group: Remove a user from an Active Directory group.
• New Widget - Remove User from SP Group: Remove a user from a SharePoint group.
• Two new pre-defined conditions for the Conditional Branch Widget:
  • Current item was created between these dates.
  • Current item was modified between these dates.
• External lookups now support lookups for Site, List, and Field names.
• Uses new Setup program.

• If a task due date is set to the current date using a workflow initiation form Date/Time field formatted as Date only, the task due date is not set.
• Conductor Studio calendar control does not format time display according to regional settings.
• Send Email does not work if the recipient property is a lookup to a SharePoint Person/Group column that allows multiple selections.
• Some widgets fail if widget properties are lookups to FBA users.
• Add User to AD Group fails if the Active Directory group name contains special characters.
• Update Item, Delete Item, Start Another Workflow, and Set Field Value Widgets will fail if the target is an External List Lookup to an item in another site collection using a date/time condition.
• Some Widgets fail if the workflow is run on a Document Set or a folder in a document library.
• Rich content editor in Conductor Studio shows error message when pasting text as HTML.
• In order to save the Access Accounts settings, you must first fill in the SQL Server name in General Settings. Details  
• Other general bug fixes.

See the Known Issues and Limitations section for the latest known issues and limitations related to this release.

• Initial release for Microsoft SharePoint Foundation 2010 and Microsoft SharePoint Server 2010.

Resolved Bugs:
The following known issues in Workflow Conductor 1.5 for SharePoint 2007 were fixed in this release:

• Link to item on task forms incorrect for sub-sites.
• Error sometimes displayed when Studio diagram is refreshed after successful workflow deployment.
• Saved property values are not displayed when you edit the Run As > Other widget property.
• IIS reset required to view Active Directory settings after installing and configuring Workflow Conductor for the first time.
• Repeat For Each Item start and stop conditions do not match date values.
• If you use a Run Parallel widget with an Update Item in one branch and a Set Approval Status in the other, the item Approval Status will always be set to "Pending" no matter what is specified in the Set Approval Status widget.
• In Update Item, cannot change the "Site" property selection if the widget is configured to update another item in the Current Site.

See the Known Issues and Limitations section for the latest known issues and limitations related to this release.

Known Issues

• Widgets can be dropped into invalid areas of “Request Approval” widget, causing workflows to display an error message.
• In some cases, Workflow Conductor Web Part features may need to be manually deactivated and re-activated when upgrading if Web Parts are already being used on a page(s).
• Workflows fail when attempting to use “Check In”, “Check Out”, or “Discard Check Out” on the workflow task list.
• Copy Item/Update Item/Set Field Value widgets will not work on a Bamboo Custom Identifier Column if the “Automatically Generate Unique ID” option is enabled.
• The Zoom In/Out viewing options may not work correctly on some larger imported templates.
• The “Repeat While” widget may fail if the “Loop Delay” property value is set using a lookup.
• Workflows that contain a Collect Data From User widget are canceled when run on a list in another site collection.
• If a Simple Publishing workflow uses a workflow initialization form field that contains a space in the form field name, any default value configured for the field will not be displayed in the workflow start page.
• If a workflow is in progress and a user clicks the "Workflow is committing..." message in the workflow status page, an error message is displayed.
• In the My Workflows and My Workflow Tasks Web Parts, version numbers will appear after the task name when a new version of a Simple Publishing workflow is published after the task is created.
• If a workflow that contains a lookup to a number or % column is deployed to a Document Library in a Meeting site, the workflow will be canceled if the column is empty.
• If a workflow initialization form Date and Time field is configured with a default value that includes a time, the time may not be displayed correctly in the workflow start page.
• If a Simple Publishing workflow with a Start Another Workflow widget is edited and published to a different scope, workflow initialization form values are not updated. For example, if the workflow was published to the list and then updated and published to the site, the Start Another Workflow widget retains its previous workflow initialization form values.
• After upgrading to Workflow Conductor 2.0, a workflow deployed in Workflow Conductor 1.5 that contains a Create AD Account widget configured with a lookup from an initialization form Choice drop-down field will add a "]" to the end of the lookup when the workflow runs.
• Workflow is canceled if a Remove AD Group widget attempts to remove a group in an OU level lower than the one specified in the LDAP path.
• In the Template Gallery, cannot filter for Created By when the filter contains special characters.
• If a Simple Publishing workflow is associated to a list with an association name different than the workflow name, the workflow start page will display the workflow name instead of the association name.
• Workflow is canceled if a Send Email widget attempts to send an attachment 8MB or larger.
• If you attempt to attach a Document Set in a Send Email widget, the workflow will be canceled.
• Some Widgets and task forms may not work correctly on German-language installations.
• The Repeat For Each Item widget "Start Item" condition does not work when using the "Is Null" operator with a Date/Time or Person/Group column.
• When upgrading Workflow Conductor, workflows that are "In Progress" and waiting for Delay For, Delay Until, Wait For Field Change, Request Approval, Or Request Feedback widgets do not complete after upgrading to Conductor 1.5 or higher.
• Saved property values are not displayed when you edit the Access SP via REST widget properties.
• If a Set Approval Status widget is configured to Run As "Initiator" or "Other", the item shows as Modified By "System Account".
• In some cases, the Approval Status of an item is not set properly for workflows deployed with the Start Option "Start this workflow to approve publishing a major version of an item."
• In the View Workflow Status page, "Starts With", "Ends With", "Equal To", and "Not Equal To" filters do not work on the Workflow Name and List columns.
• Set Field Value can incorrectly set a Person/Group (Person only) column to a SharePoint group name.

Limitations:

• Integrated task buttons in Microsoft Outlook are not available for SharePoint Foundation (Server only).
• A Bamboo KPI Custom Column field may show a blank value for a task list item if that item is updated using the Complete Task, Create Task, or Copy Item widgets.
• When editing a workflow template created in Workflow Conductor 1.6.1 after upgrading to 2.0, Create Item widget properties are not displayed correctly. Workaround: Re-enter the widget properties and save the template.
• After upgrading to Workflow Conductor 2.0, workflow solutions that were scheduled for deployment in the previous version but had not yet been deployed are not deployed at the scheduled time after the upgrade. This is because the workflow deployment method is changed to Simple Publishing in Conductor 2.0. The workflow can be manually deployed in the Workflow Solution Management page in the Workflow Conductor Control Panel.
• If a workflow with a Set Field Value widget is created on a Document Library and later associated to another list type, values set using the {Current Item:Name} lookup may not work correctly if the "Name" column in the new list was created manually and is not the default SharePoint "Name" column.
• An error page is displayed if a workflow is associated with a Bamboo workflow task content type.
• Some SharePoint site themes do not work well with Conductor Studio.
• The full account name must be used to lookup an FBA user in the Conductor Studio User Lookup form.
• Cannot assign a Request Approval or Request Feedback task to a user in another site collection who is not also in the current site collection.
• Create Item cannot create an item in a list name that includes an apostrophe (').
• Send Email does not work if the recipient property is a lookup to a SharePoint group or a Person/Group column allowing multiple selections that contains a group in another site collection.
• You must disable UAC Admin Approval Mode or turn off UAC to run Conductor on Windows Server 2008.

• Workflows that contain a Collect Data From User widget are canceled when run on a list in another site collection.
• If a Simple Publishing workflow uses a workflow initialization form field that contains a space in the form field name, any default value configured for the field will not be displayed in the workflow start page.
• If a workflow is in progress and a user clicks the "Workflow is committing..." message in the workflow status page, an error message is displayed.
• In the My Workflows and My Workflow Tasks Web Parts, version numbers will appear after the task name when a new version of a Simple Publishing workflow is published after the task is created.
• If a workflow that contains a lookup to a number or % column is deployed to a Document Library in a Meeting site, the workflow will be canceled if the column is empty.
• If a workflow initialization form Date and Time field is configured with a default value that includes a time, the time may not be displayed correctly in the workflow start page.
• If a Simple Publishing workflow with a Start Another Workflow widget is edited and published to a different scope, workflow initialization form values are not updated. For example, if the workflow was published to the list and then updated and published to the site, the Start Another Workflow widget retains its previous workflow initialization form values.
• After upgrading to Workflow Conductor 2.0, a workflow deployed in Workflow Conductor 1.5 that contains a Create AD Account widget configured with a lookup from an initialization form Choice drop-down field will add a "]" to the end of the lookup when the workflow runs.
• Workflow is canceled if a Remove AD Group widget attempts to remove a group in an OU level lower than the one specified in the LDAP path.
• In the Template Gallery, cannot filter for Created By when the filter contains special characters.
• If a Simple Publishing workflow is associated to a list with an association name different than the workflow  name, the workflow start page will display the workflow name instead of the association name.
• Workflow is canceled if a Send Email widget attempts to send an attachment 8MB or larger.
• If you attempt to attach a Document Set in a Send Email widget, the workflow will be canceled.
• Some Widgets and task forms may not work correctly on German-language installations.
• The Repeat For Each Item widget "Start Item" condition does not work when using the "Is Null" operator with a Date/Time or Person/Group column.
• When upgrading Workflow Conductor, workflows that are "In Progress" and waiting for Delay For, Delay Until, Wait For Field Change, Request Approval, Or Request Feedback widgets do not complete after upgrading to Conductor 1.5 or higher.
• Saved property values are not displayed when you edit the Access SP via REST widget properties.
• If a Set Approval Status widget is configured to Run As "Initiator" or "Other", the item shows as Modified By "System Account".
• In some cases, the Approval Status of an item is not set properly for workflows deployed with the Start Option "Start this workflow to approve publishing a major version of an item."
• In the View Workflow Status page, "Starts With", "Ends With", "Equal To", and "Not Equal To" filters do not work on the Workflow Name and List columns.
• Set Field Value can incorrectly set a Person/Group (Person only) column to a SharePoint group name.

• When editing a workflow template created in Workflow Conductor 1.6.1 after upgrading to 2.0, Create Item widget properties are not displayed correctly. Workaround: Re-enter the widget properties and save the template.
• After upgrading to Workflow Conductor 2.0, workflow solutions that were scheduled for deployment in the previous version but had not yet been deployed are not deployed at the scheduled time after the upgrade. This is because the workflow deployment method is changed to Simple Publishing in Conductor 2.0. The workflow can be manually deployed in the Workflow Solution Management page in the Workflow Conductor Control Panel.
• If a workflow with a Set Field Value widget is created on a Document Library and later associated to another list type, values set using the {Current Item:Name} lookup may not work correctly if the "Name" column in the new list was created manually and is not the default SharePoint "Name" column.
• An error page is displayed if a workflow is associated with a Bamboo workflow task content type.
• Some SharePoint site themes do not work well with Conductor Studio.
• The full account name must be used to lookup an FBA user in the Conductor Studio User Lookup form.
• Cannot assign a Request Approval or Request Feedback task to a user in another site collection who is not also in the current site collection.
• Create Item cannot create an item in a list name that includes an apostrophe (').
• Send Email does not work if the recipient property is a lookup to a SharePoint group or a Person/Group column allowing multiple selections that contains a group in another site collection.
• You must disable UAC Admin Approval Mode or turn off UAC to run Conductor on Windows Server 2008.

• Some Widgets and task forms may not work correctly on German-language installations.
• When upgrading Workflow Conductor, the database configuration may fail if the previous version's Widget Category settings were modified from the default. Details 
• When upgrading Workflow Conductor, workflows that are "In Progress" and waiting for Delay For, Delay Until, Wait For Field Change, Request Approval, Or Request Feedback widgets do not complete after upgrading to Conductor 1.5.
• If you start a workflow in Simulation Mode, the Repeat While widget Loop Delay property is not set to "0".
• In some cases, the Approval Status of an item is not set properly for workflows deployed with the Start Option "Start this workflow to approve publishing a major version of an item."
• If a Set Approval Status widget is configured to Run As "Initiator" or "Other", the item shows as Modified By "System Account".
• The Repeat For Each Item widget "Start Item" condition does not work when using the "Is Null" operator with a Date/Time or Person/Group column.
• Set Field Value can incorrectly set a Person/Group (Person only) column to a SharePoint group name.
• Saved property values are not displayed when you edit the Access SP via REST widget properties.
• In the View Workflow Status page, "Starts With", "Ends With", "Equal To", and "Not Equal To" filters do not work on the Workflow Name and List columns.

• You must disable UAC Admin Approval Mode or turn off UAC to run Conductor on Windows Server 2008. Details 
• Some SharePoint site themes do not work well with Conductor Studio.
• Send Email does not work if the recipient property is a lookup to a SharePoint group or a Person/Group column allowing multiple selections that contains a group in another site collection.
• Create Item cannot create an item in a list name that includes an apostrophe (').
• Cannot assign a Request Approval or Request Feedback task to a user in another site collection who is not also in the current site collection.
• The full account name must be used to lookup an FBA user in the Conductor Studio User Lookup form.
• The Wait For Field Change widget does not support lookups for Yes/No and Choice columns.
• This product can be migrated from SharePoint 2007 to SharePoint 2010. However, there are limitations to the migration procedure. Read KB.12627: How to Migrate Bamboo Products from SharePoint 2007 to SharePoint 2010 for more information.

• When upgrading Workflow Conductor, the database configuration may fail if the previous version's Widget Category settings were modified from the default. Details 
• When upgrading Workflow Conductor, workflows that are "In Progress" and waiting for Delay For, Delay Until, Wait For Field Change, Request Approval, Or Request Feedback widgets do not complete after upgrading to Conductor 1.5.
• If you start a workflow in Simulation Mode, the Repeat While widget Loop Delay property is not set to "0".
• In some cases, the Approval Status of an item is not set properly for workflows deployed with the Start Option "Start this workflow to approve publishing a major version of an item."
• If a Set Approval Status widget is configured to Run As "Initiator" or "Other", the item shows as Modified By "System Account".
• The Repeat For Each Item widget "Start Item" condition does not work when using the "Is Null" operator with a Date/Time or Person/Group column.
• Set Field Value can incorrectly set a Person/Group (Person only) column to a SharePoint group name.
• Saved property values are not displayed when you edit the Access SP via REST widget properties.
• In the View Workflow Status page, "Starts With", "Ends With", "Equal To", and "Not Equal To" filters do not work on the Workflow Name and List columns.

• You must disable UAC Admin Approval Mode or turn off UAC to run Conductor on Windows Server 2008. Details 
• Some SharePoint site themes do not work well with Conductor Studio.
• Send Email does not work if the recipient property is a lookup to a SharePoint group or a Person/Group column allowing multiple selections that contains a group in another site collection.
• Create Item cannot create an item in a list name that includes an apostrophe (').
• Cannot assign a Request Approval or Request Feedback task to a user in another site collection who is not also in the current site collection.
• The full account name must be used to lookup an FBA user in the Conductor Studio User Lookup form.
• The Wait For Field Change widget does not support lookups for Yes/No and Choice columns.
• This product can be migrated from SharePoint 2007 to SharePoint 2010. However, there are limitations to the migration procedure. Read KB.12627: How to Migrate Bamboo Products from SharePoint 2007 to SharePoint 2010 for more information.

• When upgrading Workflow Conductor, the database configuration may fail if the previous version's Widget Category settings were modified from the default. Details
• When upgrading Workflow Conductor, workflows that are "In Progress" and waiting for Delay For, Delay Until, Wait For Field Change, Request Approval, Or Request Feedback widgets do not complete after upgrading to Conductor 1.5 or higher.
• If you start a workflow in Simulation Mode, the Repeat While widget Loop Delay property is not set to "0".
• In some cases, the Approval Status of an item is not set properly for workflows deployed with the Start Option "Start this workflow to approve publishing a major version of an item."
• If a Set Approval Status widget is configured to Run As "Initiator" or "Other", the item shows as Modified By "System Account".
• The Repeat For Each Item widget "Start Item" condition does not work when using the "Is Null" operator with a Date/Time or Person/Group column.
• Set Field Value can incorrectly set a Person/Group (Person only) column to a SharePoint group name.
• Saved property values are not displayed when you edit the Access SP via REST widget properties.
• In the View Workflow Status page, "Starts With" and "Ends With" filters do not work on the Workflow Name and List columns.

Limitations:

• You must disable UAC Admin Approval Mode or turn off UAC to run Conductor on Windows Server 2008. Details 
• Some SharePoint site themes do not work well with Conductor Studio.
• Send Email does not work if the recipient property is a lookup to a SharePoint group or a Person/Group column that allows multiple selections.
• Create Item cannot create an item in a list name that includes an apostrophe (').
• Create Item can only set one value for a Lookup column that allows multiple selections.
• Cannot assign a Request Approval or Request Feedback task to a user in another site collection who is not also in the current site collection.
• The Wait For Field Change widget does not support lookups for Yes/No and Choice columns.
• The full account name must be used to lookup an FBA user in the Conductor Studio User Lookup form.
• This product can be migrated from SharePoint 2007 to SharePoint 2010. However, there are limitations to the migration procedure. Read KB.12627: How to Migrate Bamboo Products from SharePoint 2007 to SharePoint 2010 for more information.