For this week in Bamboo, patches for Workflow Conductor, Tree View Web Part, Mini-Calendar Web Part, Bamboo Validator Column, and Cross-Site Display Web Part were released to the storefront. Details about this week’s releases can be found below.
SA08 Workflow Conductor for SharePoint 2010 Release 4.0.1
Resolved Issues:
• Viewing Workflow status’ on Internet Explorer and then exporting to Excel gives you the wrong file format when saving.
• The Send Email Widget does not include commas for large numbers. Example: 500000.
• Some large templates may fail when attempting to import in SharePoint Foundation environments.
• When using a workflow initialization form to collect a date value, the stored parameter includes a date and time value.
• 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.
• 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.
• 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.
• The Add User to SharePoint Group Widget errors when attempting to add a user via lookup.
• Initialization form fields do not always honor the new order when rearranged.
• In version 4.0, workflow templates with more than 3 Conditional Branch widgets may not publish successfully.
• If a 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 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.
• When inserting the text value for a lookup to a Date and Time field that is set to “Date Only”, the value is still returned in a “Date & Time” format.
• 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.
• 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 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.
• 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.
• In the Template Gallery, cannot filter for Created By when the filter contains special characters.
• 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 from an earlier version, 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 correctly.
• Set Field Value can incorrectly set a Person/Group (Person only) column to a SharePoint group name.
Known Issues:
• When opening a template created in 4.0 using 4.0.1 or later, reconfiguring some widget properties in Conditional Branch, Repeat While, or Delay Until Condition is Met may result in JavaScript errors. Widgets can still be configured after closing the error.
• 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.
• 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.
• 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.
• Run Parallel – Setting workflow error handling to “Stop Workflow” or “Pause Workflow” within a parallel branch does not work correctly.
• When using the optional “Workflow Start Feature”, the customizable workflow start button may not show up in certain list types, including Asset, Links, Calendar, Project Tasks, Issue Tracking, Data Connection Library, Report Library, and Announcement.
• 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.
• 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 that contains a look-up 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 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
• 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
• 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
Limitations:
• Cannot create a column named “level” using the Create Column widget. There is already a hidden column in SharePoint with that name.
• 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.
• Conditional Branch, Repeat While Delay Until Condition is Met widgets – Alignment of buttons/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 item URL in task notification emails and in error handling forms may start with “HTTP” instead of “HTTPS” if the workflow is set to “Start When New Item Created”. This is due to limited visibility into ISA proxy configuration settings in the workflow.
• 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 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 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 look-up 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 the SharePoint list after de-activating and re-activating the workflow name (SharePoint limitation).
HW03 Tree View Web Part for SharePoint 2010 Release 2.0.126
Bug Fixes:
• The relative path defined in the data source settings is incorrect after migrating from SharePoint 2010 to SharePoint 2013.
New Known Issues:
• The “Send To” context menu option has been removed due to a JavaScript error on the trigger.
No New Limitations
HW22 Mini-Calendar Web Part for SharePoint 2010 Release 2.8.97
Bug Fixes:
• The calendar tooltip placement may not display correctly on custom master pages.
No New Known Issues or New Limitations
HW41E Bamboo Validator Column for SharePoint 2010 Release 1.3.37
Bug Fixes:
• Internal bug fixes to support SA08 Workflow Conductor R4.0
No New Known Issues or New Limitations
HW63 Cross-Site Display Web Part for SharePoint 2013 Release 1.2.55.2013
Bug Fixes:
• Unable to see the “Edit in Datasheet” action on Internet Explorer version 11.
• Unable to create new documents inside a folder or Document Set.
• Clicking on a Document Set results in a blank window.
New Limitations:
• When used on a SharePoint Server site with anonymous access that also contains a News Feed Web Part, changing the list view may result in an error.
• When linked to a task list on an anonymous access site, switching to Gantt View results in no data being shown.
• When linked to a Document Library on a site that uses legacy SharePoint 2010 UI, attempting to create a Document Set inside a Folder fails.
New Known Issues:
• “The website declined to show this webpage” is displayed when a “My Tasks” or “Created Me” view is selected on an anonymous access site.
• Attempting to access the “Details” View of items in a folder of a Picture Library on a site with legacy SharePoint 2010 UI results in only thumbnails being displayed.
