At Bamboo this week, we continued rolling out a new release of SharePoint 2013 for the following products: Tree View Web Part, Alert Plus, List Bulk Import, KPI Column, Visual Indicator Column, List Search Simple, List Search Advanced, Project Portfolio Dashboard, and Workflow Conductor. For more details about the new set of SharePoint 2013 releases please see the list below.

HW03 Tree View Web Part for SharePoint 2013 Release 1.8.23.2013

Initial Release on Microsoft SharePoint Foundation 2013 and Microsoft SharePoint Server 2013.

This build runs on SharePoint Foundation 2013 and SharePoint Server 2013. This release contains the same functionality as the equivalent version number of the SharePoint 2010 build of this product.

See the Known Issues and Limitations section for the latest known issues and limitations related to this release. For information about using this product, read the Online Documentation.

Known Issues:

• Create a New Features folder, the folder is not added to Tree View on the left pane.
• New Features folder does not display on Tree View when I created a folder from a branch of Tree View.
• Left Tree View pane does not refresh after creating the New Features folder from the tree. Refresh the page will show the New Features folder in the tree.

Limitations:

None

HW05 Alert Plus for SharePoint 2013 Release 3.2.124.2013

Initial Release on Microsoft SharePoint Foundation 2013 and Microsoft SharePoint Server 2013.

This build runs on SharePoint Foundation 2013 and SharePoint Server 2013. This release contains the same functionality as the equivalent version number of the SharePoint 2010 build of this product.

See the Known Issues and Limitations section for the latest known issues and limitations related to this release. For information about using this product, read the Online Documentation.

Known Issues:

• The Last Run Date worked incorrectly after changing the time zone twice.
• When an alert job for Alert Plus is connected to Bamboo List Rollup Web Part, there is no support for Advanced Filtering (CALM Query) to filter on the metadata column.
• Alerts are not sent for documents if the Document Library option “Require documents to be checked out before they can be edited?” is set to “Yes”. Workaround: Create an “item exists” alert on the document library. Enter the CAML statement Created = [Today]. Set Follow-up Wait Days to 1 or 2.
• E-mail is not sent for “item created” alerts on a document library if the CAML query is checking a Date and Time column in the library.
• If an alert is created on a “My Tasks” view, the Last Run Status will display the following error: “Input string was not in a correct format.” This is because the view query is based on a user ID that is not available when Alert Plus runs.
• Alerts for items in an InfoPath Form Library selected using a CAML query may fail in some cases.

Limitations:

• In certain cases, Outlook will prompt for a login if the alert message contains images from a SharePoint Picture Library.
• In the Mail Format tab, the special token {ColumnName/Old} is only valid for the alert triggers “A specific column in the list changes” or “An item in the list is deleted”.
• Outlook clients cannot view images included in an Alert Plus e-mail body using Image Manager or the <IMG> tag if viewing the image link requires authentication.
• Alert Plus supports alerts on recurring items in a Calendar list. However, if the series is modified and a user has an “item modified” alert on the recurring item, the user will get an alert for each item in the series.
• When selecting alert recipients using the “Lookup an E-mail Address in another List (Advanced)” option, the columns linking the lookup list to the alert list must be the same data type.
• Column display names are no longer supported in CAML queries for alerts on List Rollup Schemas. Use the “Upgrade Alert Plus” tab in the Alert Plus Utilities to fix existing List Rollup Schema alerts that use display names in CAML queries.
• Some custom schedules from previous Alert Plus versions are not fully supported in Alert Plus 3.1. See “Upgrading Alert Plus” in the Online Documentation for more information.
• Column values containing URL to content in the same SharePoint site result in the URL changing from absolute path (http://servername/…) to relative path (../) resulting in an invalid URL in the e-mail message body. The recommended workaround is the user of TinyURL http://rrfreeman.blogspot.com/2010/12/emailed-relative-html-rich-text-column.html
• Alert Plus alerts are not triggered if based on the change of value for column Workflow Status as Workflow does not modify the item when it changes this column value.

HW18 List Bulk Import for SharePoint 2013 Release 3.0.29.2013

New Features:

• Extended Source and Target List authentication support:

SharePoint 2007

• Windows
  • Active Directory Services
  • NT Directory Services
• Forms
  • SQL Server membership provider
  • Active Directory membership provider

SharePoint 2010

• Windows (Classic Mode Authentication)
  • Active Directory Services
  • NT Directory Services
• Windows (Claim Based Authentication)
  • Active Directory Services
  • NT Directory Services
• Forms-Based Authentication
  • SQL Server membership provider
  • Active Directory membership provider

SharePoint 2013

• Windows (Classic Mode Authentication)
  • Active Directory Services
  • NT Directory Services

• Windows (Claim Based Authentication)
  • Active Directory Services
  • NT Directory Services

• Forms-Based Authentication
  • SQL Server membership provider
  • Active Directory membership provider
• SharePoint Online (Office 365)
  • Office 365 build-in authentication provider

Limitations:

• For SharePoint 2013 and SharePoint 2010, fail to import when the current target site is different from the target site in the Import Template.
• For SharePoint 2013, fail to import Related Items in the tasks list.
• When a new Calendar list is created from List Bulk Import, the Content-Type “Schedule” is not marked as the Default Content-Type, resulting in missing columns displayed in the New, Display, and Edit forms. To resolve, mark the “Schedule” content type as default.
• Only current versions of items are imported. This includes Multiple Lines of Text with Append Changes to Existing Text enabled. Excel as Source, supports only columns formatted as General; Number; Currency; Date [MM/DD/YYYY]; Text. CSV as the Source – Can only import Date formatted as [MM/DD/YYYY].
• When importing from a SharePoint List with content types enabled, the option “Allow management of content-type” is not enabled in the newly created target SharePoint List.
• Fail to import into target SharePoint Lists that contain the name “Discussion Board Plus”. To successfully update the read-only columns Created, Created By, Modified, Modified By in the target SharePoint List, the configured login account connecting to the target SharePoint List must have the permission level “Full Control” to the list.
• List Bulk Import does not support the following Bamboo custom columns as the source or target: Rating Column, Rich Text Column, and Visual Indicator Column.
• List Bulk Import does not support Bamboo File Share Library as the source or target.
• List Bulk Import does not support Bamboo Video Library connected to Bamboo File Share Library as the source or target.
• Fails to connect to SharePoint Online if the account configured in List Bulk Import is a member of a custom SharePoint Group.
• Importing to the target SharePoint List of type Calendar fails if an item in the source has recurrence enabled with the frequency of Year.
• List Bulk Import does not support SharePoint Lists of type Survey as either the source or the target list.

Known Issues:

• For SharePoint 2013 and 2010, Bulk Import does not support creating a new target list when that list has Gantt view.
• Fail to import “Created date, Modified, login account, and Editor” columns to multiple mapping target columns at the same time.

HW41J KPI Column for SharePoint 2013 Release 1.3.78.2013

Initial Release on Microsoft SharePoint Foundation 2013 and Microsoft SharePoint Server 2013.

This build runs on SharePoint Foundation 2013 and SharePoint Server 2013. This release contains the same functionality as the equivalent version number of the SharePoint 2010 build of this product.

See the Known Issues and Limitations section for the latest known issues and limitations related to this release. For information about using this product, read the Online Documentation

Known Issues:

None

Limitations:

• Bamboo KPI Column is not supported in Datasheet View or Document Information Pane (Microsoft Office). When displayed in Datasheet View or Document Information Pane, the user will see a read-only value.
• Bamboo Custom Columns are currently not supported in Project Server.

HW41D Visual Indicator Column for SharePoint 2013 Release 1.3.79.2013

Initial Release on Microsoft SharePoint Foundation 2013 and Microsoft SharePoint Server 2013.

This build runs on SharePoint Foundation 2013 and SharePoint Server 2013. This release contains the same functionality as the equivalent version number of the SharePoint 2010 build of this product.

See the Known Issues and Limitations section for the latest known issues and limitations related to this release. For information about using this product, read the Online Documentation.

Known Issues:

None

Limitations:

• This custom column does not support additional columns in the lookup list that can be added to the view when displaying the list item.
• Bamboo Custom Columns are currently not supported in Project Server.

HW11A List Search Simple for SharePoint 2013 Release 2.1.167.2013

Initial Release on Microsoft SharePoint Foundation 2013 and Microsoft SharePoint Server 2013.

This build runs on SharePoint Foundation 2013 and SharePoint Server 2013. This release contains the same functionality as the equivalent version number of the SharePoint 2010 build of this product.

See the Known Issues and Limitations section for the latest known issues and limitations related to this release. For information about using this product, read the Online Documentation.

Known Issues:

• Unable to customize search criteria layout using the Modify Layout option.
• When the option “Allow search all columns” option is disabled, the Modify Layout editor will not save layout changes unless the Keyword Control text box is added to the HTML. This control should not be required when the option is disabled.
• Unable to modify the CSS for the search results grid.
• Search results are incorrect when searching for a Choice or Lookup column value that contains a quotation mark (“”).
• Print and Export to Excel show raw data for Bamboo custom columns that visually display data, such as HW41J KPI Column, and for columns that enforce special rules, such as HW41E Bamboo Validator Column.
• Unable to show HW41D Bamboo Visual Indicator column tooltips in search results.
• Unable to display HW41I Bamboo Rating columns correctly in search results.
• List Search Simple Web Part R2.0 unable to provide data to other Web Parts using Web Part Connection feature.

Limitations:

• No default value is shown for Number, Choice, Yes/No, or Date/Time column types when the option “Display default column value” is selected.
• Search results are not retained when viewing or editing an item in the search results using the item Edit Menu. Workaround: Click on the item link to open the item in a pop-up window.
• “Search in all columns for” keyword search is unable to search in Date/Time, Number, Currency, or Yes/No columns.

HW11B List Search Advanced for SharePoint 2013 Release 1.8.121.2013

Initial Release on Microsoft SharePoint Foundation 2013 and Microsoft SharePoint Server 2013.

This build runs on SharePoint Foundation 2013 and SharePoint Server 2013. This release contains the same functionality as the equivalent version number of the SharePoint 2010 build of this product.

See the Known Issues and Limitations section for the latest known issues and limitations related to this release. For information about using this product, read the Online Documentation.

Known Issues:

• User interface of Rating column is broken when print preview.
• List Search Web Part incorrectly returns no results when a search is performed using “Not Null” or “Is Null” criteria where data actually exists.
• List Search Web Part does not inherit the “Group By” settings defined for the current list view.

Limitations:

None

SA35 Project Portfolio Dashboard for SharePoint 2013 Release 1.8.80.2013

Initial Release on Microsoft SharePoint Foundation 2013 and Microsoft SharePoint Server 2013.

This build runs on SharePoint Foundation 2013 and SharePoint Server 2013. This release contains the same functionality as the equivalent version number of the SharePoint 2010 build of this product.

See the Known Issues and Limitations section for the latest known issues and limitations related to this release. For information about using this product, read the Online Documentation.

Includes an updated version of the following component:

KPI Column 1.3.78.2013 (File version 10.3.78.2013)

Known Issues:

None

Limitations:

None

SA08 Workflow Conductor for SharePoint 2014 Release 3.0.1.2013

Initial Release on Microsoft SharePoint Foundation 2013 and Microsoft SharePoint Server 2013.

This build runs on SharePoint Foundation 2013 and SharePoint Server 2013. This release contains the same functionality as the equivalent version number of the SharePoint 2010 build of this product.

Note: Workflow Conductor for 2013 currently does not support the 2010 legacy UI. See the Limitations section below for more details.

See the Known Issues and Limitations section for the latest known issues and limitations related to this release. For information about using this product, read the Online Documentation.

Known issues:

• If a workflow is started in SharePoint 2010, then ported to 2013, workflow task hyperlinks in emails that have already been sent will point to the wrong location.
•Workflow instances that are still in progress in SharePoint 2010 when migrating to SharePoint 2013 may show up as “In Progress” even after successful workflow completion and workflows that were paused in SharePoint 2013 due to an error may not resume correctly even when the underlying cause of the error is addressed. In both cases, the workflow will need to be canceled (clicking on Workflow Status>End Workflow). Subsequent workflow instances should run correctly.
• If the workflow is paused due to an 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 on the workflow start page.
• If a workflow is in progress and a user clicks the “Workflow is committing…” message on 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 are configured with a default value that includes a time, the time may not be displayed correctly on 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 with 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:

•Legacy Office 2010 UI is not currently supported for the Workflow Conductor Studio in SharePoint 2013. To upgrade to the SharePoint 2013 UI after migrating from SharePoint 2010:

1.Go to Site Settings–> Site Collection Administration–>Site Collection Upgrade and upgrade to the SharePoint 2013 UI.
2.Go to Site Settings–> Site Collection Administration–>Bamboo 2013 Workflow Conversion and upgrade legacy workflows and the Workflow Conductor UI to SP2013

• You must disable UAC Admin Approval Mode or turn off UAC to run Workflow Conductor on Windows Server 2012 and Windows Server 2008.
• Workflows scheduled for later deployment using the Solution Deployment publishing method in SharePoint 2010 should either be deployed or canceled prior to migration to SharePoint 2013. These workflows will not deploy correctly in 2013 due to changes required in the stored packages awaiting deployment.
• 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.
• Workflow name disappears on share point list after de-active and re-active the WF name (SharePoint limitation)