This week in Bamboo, we rolled out a new product Bamboo Essential Plus Suite for SharePoint 2013 to the storefront along with a new major release of Workflow Conductor Release 4.0 for SharePoint 2010. Patch for Password Expiration Web Part was also released at the same time.  Please check out our storefront for the latest releases and review the list below for more details about this week’s releases.

PB06 Bamboo Essentials Plus Suite for SharePoint 2013 Release 1.0.1.2013

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

Includes updated versions of the following components:

• Tree View Web Part R1.7.24.2013 (File version 10.7.24.2013) or newer version.
• Alert Plus R3.2.124.2013 (File version 30.2.124.2013) or newer version.
• Password Change Web Part R4.1.69.2013 (File version 40.1.69.2013) or newer version.
• User Account Setup Web Part R4.0.163.2013 (File version 40.0.163.2013) or newer version.
• User Directory Web Part R1.7.81.2013 (File version 10.7.81.2013) or newer version.
• Password Reset Web Part R2.4.70.2013 (File version 20.4.70.2013) or newer version.
• List Search Simple Web Part R2.2.45.2013 (File version 20.2.45.2013) or newer version.
• List Search Advanced Web Part R1.9.77.2013 (File version 10.9.77.2013) or newer version.
• Group Redirect Web Part R20.3.33.2013 (File version 20.3.33.2013) or newer version.
• User Redirect Web Part R1.5.27.2013 (File version 10.5.27.2013) or newer version.
• Group Email Web Part R1.7.47.2013 (File version 10.7.47.2013) or newer version.
• List Bulk Import R3.0.64.2013 (File version 30.0.64.2013) or newer version.
• User Profile Sync R2.0.20.2013 (File version 20.0.20.2013) or newer version.
• Calendar Plus Web Part R4.5.189.2013 (File version 40.5.189.2013) or newer version.
• List Rotator Web Part R2.5.101.2013 (File version 20.5.101.2013) or newer version.
• Mini-Calendar Web Part R2.8.86.2013 (File version 20.8.86.2013) or newer version.
• Password Expiration Web Part R1.6.49.2013 (File version 10.6.49.2013) or newer version.
• List Rollup Web Part R6.0.111.2013 (File version 60.0.111.2013) or newer version.
• Chart Plus Web Part R3.5.164.2013 (File version 3.5.164.2013) or newer version.
• Site Creation Plus R1.4.78.2013 (File version 10.4.78.2013) or newer version.
• User Profile Plus Web Part R1.4.78.2013 (File version 10.4.78.2013) or newer version.
• Virtual Map View Web Part R1.9.42.2013 (File version 10.9.42.2013) or newer version.
• List Bulk Export R2.0.21.1 (File version 20.0.21.1) or newer version.
• SharePoint Team Calendar R1.7.36.2013 (File version 10.7.36.2013) or newer version.
• Data-Viewer Web Part R3.6.103.2013 (File version 30.6.103.2013) or newer version.
• Poll Web Part R1.4.63.2013 (File version 10.4.63.2013) or newer version.
• Alerts Administrator R1.4.65.2013 (File version 10.4.65.2013) or newer version.
• My Alerts Organizer R1.4.56.2013 (File version 10.4.56.2013) or newer version.
• Column Level Security R1.3.48.2013 (File version 10.3.48.2013) or newer version.
• Custom Identifier Column R1.0.57.2013 (File version 10.0.57.2013) or newer version.
• KPI Column R1.3.80.2013 (File version 10.3.80.2013) or newer version.
• Lookup Selector Column R2.3.155.2013 (File version 20.3.155.2013) or newer version.
• Rating Column R1.1.63.2013 (File version 10.1.63.2013) or newer version.
• Rich Text Column R1.3.28.2013 (File version 10.3.28.2013) or newer version.
• Validator Column R1.3.42.2013 (File version 10.3.42.2013) or newer version.
• Visual Indicator Column R1.3.82.2013 (File version 10.3.82.2013) or newer version.
• SharePoint Task Master R3.6.138.2013 (File version 30.6.138.2013) or newer version.
• List Print R1.4.40.2013 (File version 10.4.40.2013) or newer version.
• Wiki Publisher R1.0.85.2013 (File version 10.0.85.2013) or newer version.
• Navigators R1.5.74.2013 (File version 10.3.57.2013) or newer version.
• User Manager for Sites R1.3.62.2013 (File version 10.3.62.2013) or newer version.
• SharePoint File Share Library R2.0.95.2013 (File version 20.0.95.2013) or newer version.
• Filters Collection  R1.3.37.2013 (File version 10.3.37.2013) or newer version.
• Cross-Site Display Web Part R1.2.44.2013 (File version 10.2.44.2013) or newer version.
• SharePoint Video Library R2.0.115.2013 (File version 20.0.115.2013) or newer version.
• List Consolidator for Users  R1.0.107.2013 (File version 10.0.107.2013) or newer version.

SA08 Workflow Conductor for SharePoint 2010 Release R4.0

New Features:

• New Workflow Studio design interface, with greatly improved performance when dragging and dropping widgets, especially in large workflows.
• Ability to easily rearrange the widgets in a workflow after their initial placement.
• A quick widget search function in the widget list in addition to the normal category browse.
• Improved zoom functions, including the ability to edit workflows while zoomed in/out.
• Visible anchor points to show where widgets can or will be dropped.
• Notification icons on the workflow diagram to show which widgets are missing required settings.
• Workflow settings have been moved to the ribbon, and widget settings are accessed by double-clicking a widget.

Resolved Issues:

• Content missing from task notification emails for the Request Approval, Request Feedback, Collect Data From User, and Custom User Task Form widgets when using lookups.
• An incorrect warning message is displayed when attempting to overwrite another user’s Shared Template.
• A Shared Template cannot be overwritten by the same user when attempting to save an updated version of the template.
• Lookups to an Approval Status field return a numeric value instead of text when comparing with other values in some widgets, including Conditional Branch, Repeat While, and Delay Until Condition Is Met.
• If more widgets are displayed within a category than will fit on the screen, there is no ability to scroll down to see the remaining widgets.
• Log To History widget – Inserted lookups to a YES/NO field always return a value of “No”.
• Cannot add a user to AD group when using workflow variable at Group field.

Known Issues:

• When using a workflow initialization form to collect a date value, the stored parameter includes a date and time value.
• Repeat For Each Item widget – When using a custom condition that includes a lookup to “Other Field” of a Date/Time type, the workflow may error if the regional settings of the site are then changed.
• Create Site widget- When using a multi-level lookup (two or more nested lookups), a JavaScript error may display when starting the workflow. Closing the error and refreshing the page fixes the issue.
• Repeat For Each Item widget – Workflow may encounter when Repeat Settings references a Date/Time initialization parameter or workflow variable, and regional settings for the server are later changed.
• Set variable widget – Date values pulled from a SharePoint date/time field and stored in a text variable may be saved as UTC time, while date/times stored in a workflow date variable show the local time.
• Custom User Task widget- After the initial publishing of a workflow, viewing a task on the Workflow Information page may result in a JavaScript error. Closing the error and refreshing the page fixes the issue.
• Compatibility Mode may need to be enabled for the site to successfully access workflow task forms from the out-of-the-box SharePoint workflow status page. Otherwise, a “critical error” warning may be displayed when accessing the forms via an “HTTP” URL on a single-server farm, or via “HTTPS” on a multi-server farm.
• Cannot publish workflows with names that contain special characters or end in “_files”.
• Some users may see occasional JavaScript errors when opening the workflow studio or double-clicking on a widget on certain browser versions. These messages do not affect product behavior or performance.
• Repeat For Each Item widget – Looping logic does not work as expected when the target list contains folders and subfolders.
• Custom User Task Form widget – When setting properties in the Custom Task form setting, copying and pasting data from MS Word to the field Title, Description, User Choices, Value’ does not work.
• When reassigning a custom user task, the date picker shows the time for on Reassign task in Task Form but does not allow a time to be assigned.
• Repeat For Each Item widget – When setting custom conditions for start and stop points, the list of available logical operators for conditions may not be complete for the initial field displayed. Changing the selected field will cause the list of operators to refresh correctly for the selected field type.
• Run Parallel – Setting workflow error handling to “Stop Workflow” or “Pause Workflow” within a parallel branch does not work correctly.
• Does not show workflow name button in some lists such as Asset, Links, Calendar, Project Tasks, Issue Tracking, Data Connection Library, Report Library, Announcement
• 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, 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.
• 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 is 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:

• Conditional Branch, Repeat While, Delay Until Condition is Met widgets – Alignment of button/icons in the Condition settings for these widgets may be off when opening a template created in version 3.5 or earlier.
• Workflow publishing will fail if variables are named “bamboo” or “Microsoft” due to namespace conflicts.
• The Run As function for PowerShell widgets does affect the permissions used when running the script. This setting only affects access to any SharePoint data using the script (ex. lookups within the script). Running the script with different permissions requires that credentials are supplied within the script itself, although those credentials within the script can also be stored in SharePoint for security, and accessed using lookups.
• Currently, only the Bar chart type is available in the workflow reporting Web Part.
• When changing the content of a Workflow Conductor default email template in Central Administration, IIS must be reset before the updated template is displayed in the related widgets in the workflow studio.
• The optional Workflow Start Feature may not display more than 4 custom workflow start buttons in the SharePoint item ribbon.
• The custom workflow start button name may not show up correctly when using the optional Workflow Start Feature in certain list types, including Asset Libraries, Link Lists, Calendar Lists, Project Task Lists, Issue Tracking Lists, Data Connection Libraries, and Report Libraries.
• 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 on 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 with 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 look up 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 contain 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 the SharePoint list after de-activating and re-activating the workflow name (SharePoint limitation).

HW23 Password Expiration Web Part for SharePoint 2013 Release 1.6.55.2013 

Bug Fixes:

• If a user belongs to a group/subgroup within an Organizational Unit (OU) and their username contains a slash (“/”), emails are not sent to the entire OU.
• In some cases, including when used in one-way trust domains, the expiration date is always shown as 0 days.

No New Known Issues or New Limitations