This Week in Bamboo (November 4th, 2012 – November 10th, 2012)

This week in Bamboo, Workflow Conductor Release 3.0 for SharePoint 2010 was released to the storefront with new improvements, new features and some resolved bugs along with the following patches: List Search Advanced, Bamboo Rating Column, Discussion Board Plus and Video Library. For more details about our latest releases of this week, please see below.

SA08 Workflow Conductor for SharePoint 2010 (Release 3.0)

New Features:

• Delay Until Condition is Met – A new widget that delays a workflow until a custom, designer-defined condition is met.
• Custom User Task Form – Assigns tasks for any number of users to complete a form that includes selecting from a set of designer-defined choices. Based on user responses and customizable business logic, a single outcome is stored that can be used to affect things like workflow branching.
• Email-based approvals – Some or all users can now manage approvals directly from email, without having to log into SharePoint.
• Required Fields – Fields in the Initialization and Collect Data from User forms can now force users to enter values for some or all fields.
• Repeat for Each Item – The targeted list items can now be limited to a specific list view rather than the entire list.
• Calculate – Even more math, date/time, and string functions, including “Find” and “Replace” functions.
• Approval and Feedback Attachments – Email attachments can now be added using lookups for Request Approval and Request Feedback, including “Current Item”.
• Improved lookups – Many lookup properties have been updated to provide text boxes that allow multiple lookups and text to be combined directly, and most User/Group lookups have been updated to allow lookups to be set directly from the widget settings pane. Lookups to multi-select choice fields are now supported as well.
• Create Column – This widget now supports Bamboo Custom Columns, as well as standard SharePoint columns.
• Send Email – Hyperlinks are now easier to add to emails, and email priority can be set using lookups.

Resolved Issues:

• Resolved issue where users upgrading from previous versions may experience problems publishing new workflows. This issue previous required manual deactivation/reactivation of certain features. Update Item/Set Field Value widgets will not work on a Bamboo Custom Identifier Column if the “Automatically Generate Unique ID” option is enabled.
• Links to tasks in task notification emails now properly link to “http://” or “https://” based on extranet configuration settings.
• Resolved an issue where some instances of the Run PowerShell widget would cause error messages to be displayed in the Log Viewer Web Part.
• The Check In Comments field is now available when selecting columns for lookups in widget properties.
• Resolved issue where error was displayed when the Request Approval task form on a sub-site was opened someone with permissions for the sub-site but not the parent site.

Known Issues:

• If workflow is paused due to error in a step with a user task form, an error message of “save conflict” may be shown when trying to resume. Attempting to resume a second time will allow the workflow to proceed normally.
• Links to customize Workflow Conductor InfoPath task forms will not work directly, but instead the paths need to be manually copied and opened in InfoPath Designer to edit forms.
• 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.
• 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.
• 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.
• Workflow name disappears on share point list after de-active and re-active the WF name (SharePoint limitation).

HW11B List Search Advanced for SharePoint 2007 (Release 1.8.91)

Bug Fxes:

• If the search criteria includes a column of type People and Group and SharePoint profile is formatted as “Lastname, Firstname”, search fails and displays source code in the people picker field.

No new Known Issues and Limitations

HW41I Rating Column for SharePoint 2010 (Release 1.1.43)

Bug Fixes:

• If SharePoint is using Forefront UAG authentication, Rating Column causes the pages scroll bars and action ribbon to become disabled.

No new Known Issues and Limitations.

SA75 Discussion Board Plus for SharePoint 2010 (Release 1.5.22)

Bug Fixes:

• When set up the Incoming Email Settings to allow items to be added to the Discussion Board Plus list through e-mail, the email address is stored. However, it is resulted in an error when click OK to save. And items are not saved to the list when incoming email are sent.

Known Issues:

• When viewing a discussion thread that resulted from the List Search Simple Web Part’s search results and clicking on the Quote Message, the Close icon for the window is hidden.

Limitations:

• The Lock Topic and Mark as Sticky options are not available in the ribbon if a Discussion Board Plus list is added to a Web Part Page. The options are available in the Edit Control Block (ECB) menu.
• The view count for a topic is displayed incorrectly if Content Approval is enabled for the Discussion Board Plus list.

Notes for Customers:

• Users must clear their browser cache using Control + F5 after upgrading from version 1.0 or 1.1 to 1.5 to resolve an error that displays.

HW69 Video Library for SharePoint 2010 (Release 2.0.87)

Bug Fixes:

• Some strings fail to translate based on the Language Resource files.
• In certain cases, when performing the test for Virtual Directory configuration, user will receive an error.

No new Known Issues.

New Limitation:

• In certain cases, playing videos within Video Library results in a login authentication prompt. To resolve this issue, open Windows Media Player on the client machine. Go to Tools -> Options and select Network tab. In the section “Streaming proxy settings” select HTTP, click Configure and select “Do not use proxy server”. Save all dialog windows. For more information, see the following article: http://blogs.isaserver.org/pouseele/2007/11/09/windows-media-player-authentication-prompts/