This Week in Bamboo (June 7th, 2015 – June 13th, 2015)

This week in Bamboo, major releases for Workflow Conductor release 4.0 and World Clock & Weather Web Part release 3.0 were rolled out to our storefront with many new features and many resolved bugs.  Patch for List Search Simple Web Part was also released at the same time.  For more information about the new releases please see below.

SA08 Workflow Conductor for SharePoint 2013 Release 4.0.1.2013 (File version 40.0.1.2013)

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 on 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 double-clicking a widget.

Resolved Issues:

•    Existing settings are not visible when reopening a previously configured lookup.
•    Field names in the Collect Data from User widget are limited to 25 characters (they can now be up to 128 characters in length).
•    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.
•    There is an error message when trying to save over another user’s Shared Template.
•    Shared Template is not overwritten when trying to save over another user’s Shared Template.
•    Lookups to an Approval Status field returns 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.
•    Unable to run workflows when operating in Windows Classic Authentication mode.
•    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.
•    If email-based approval is already in use and Workflow Conductor is upgraded from the previous version, the site feature for email approval must be manually deactivated and reactivated on any site using this approval method.
•    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 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.
•    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 in 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.
•    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 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.
•    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”.
•    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. 4815
•    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.

Known Issues:

•    Pausing a workflow due to an error in a document library where the stored file type is a site template (“.stp”) may result in missing buttons for “Repeat Step”, “Skip Step”, “Cancel Workflow” on the pause form for the workflow.
•    Migrating a workflow from SharePoint 2010 to 2013 that uses Bamboo Column Level Security in combination with a Copy Item, Set Field Value, Move Item, or Create Item widget results in an error when running or republishing.
•    Migrating a workflow with Subscribe User to Alert widget that uses the Run As feature with the setting of “Designer” or “Other” results in an error. These workflows must be republished.
•    Repeat For Each Item, Set Field Value 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.
•    If a workflow has errored and is paused prior to upgrading Workflow Conductor from the previous version, some widgets may show a status of “Failed to run” in the detailed workflow history after the workflow is restarted.
•    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 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.
•    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 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 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.
•    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.
•    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: 

•    Workflow publishing will fail if variables are named “bamboo” or “Microsoft” due to namespace conflicts.
•    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 update 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.
•    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.
•    You must disable UAC Admin Approval Mode or turn off UAC to run Conductor on Windows Server 2008 or later.
•    Workflow name disappears on SharePoint list after de-activating and re-activating the workflow name (SharePoint limitation).

HW17 World Clock & Weather Web Part for SharePoint 2010 Release 3.0.16 (File version 30.0.16) and SharePoint 2013 Release 3.0.16.2013 (File version 30.0.16.2013)

New Features:

•    Added the following new weather provider choices. Get API keys directly from feed providers to ensure scalability and enter into SLAs.

o         Weather Underground
o         OpenWeatherMap
o         Forecast.io

•    Add or subtract hours automatically per location from feed data if desired/needed.
•    Cache weather data location for a specified time to reduce calls and increase speed.
•    Adjust border color for locations.
•    Use classic weather icons, or pull stylized icons from provider feeds.

Bug Fixes:

•    Fixed intermittent issues with incorrect times being displayed after the start of Daylight Savings Time. Removed a provider feed that was occasionally causing the issue.

Known Issues and Limitations:

SharePoint 2010 Release 3.0.16:

•    No New Known Issues or Limitation

SharePoint 2013 Release 3.0.16.2013:

•    No New Known Issues
•    Limitations:

o    Firefox or Opera Browser: Unable to display rain special effect. Unable to use slider control in the tool part to change special effect density.
o    Opera Browser: Cannot show Analog/Digital Clock when using Silverlight option.

HW11A List Search Simple Web Part for SharePoint 2010 Release 2.3.25 (File version 20.3.25)

Bug Fixes:
 
•    Inserting a Field Control from the Modify Layout Editor may occasionally display an error.
•    Exported Date and Time column values cannot be sorted in Excel.
•    Searching Choice column values containing a plus (+) sign may not return the correct results.

New Known Issues:

•    In web parts configured with custom search layouts, selecting the Back button may cause the Print and Export to Excel buttons to appear.
 
No New Limitations


SharePoint

Applications

SharePoint apps are stand-alone applications that perform specific tasks on a SharePoint site. Apps can perform functions such as managing a discussion board or knowledge base, performing project management or time tracking tasks, or doing other workflow operations.

SharePoint

Product Suites

Experience greater power and savings by bundling our SharePoint apps and web parts.


Essentials


Essentials Plus


Bamboo Premier


Project Management Suite


Knowledge Management Suite


External User Manager


SharePoint

Web Parts

Extend SharePoint beyond its out-of-the-box capabilities by tailoring it to your requirements with Bamboo Solution’s growing portfolio of Web Parts. Web Parts are the building blocks of pages on a SharePoint site that can be used to customize the user interface and content of a site page. 

SharePoint

Product Suites

Experience greater power and savings by bundling our SharePoint apps and web parts.


Essentials


Essentials Plus


Bamboo Premier


Project Management Suite


Knowledge Management Suite


External User Manager


Office 365

Cloud Parts

Cloud Parts are functional components that extend your SharePoint environment whether it’s hosted, on-premises, or part of Microsoft Office 365. More than mere ports of existing software to the cloud, our Cloud Parts have been built from the ground up to take advantage of the best that the cloud has to offer.

SharePoint

Product Suites

Experience greater power and savings by bundling our SharePoint apps and web parts.


Cloud Parts Suite for O365/SP Onl.


Featured Services

SharePoint Health Check

A SharePoint Health Check will identify the causes of issues and risks associated with your specific environment, and is custom tailored to provide you with the best recommendations to optimize your SharePoint environment.

SQL Health Check

Document recommendations relating to performance, stability, availability, or a specific focus you request of your SQL Server database instances.

My SharePointXperts

The truth is that each SharePoint skill may not be a full time job for many organizations, and it is nearly impossible for one person to do everything you need – so augment your team with SharePointXperts; providing the skill sets you need when you need them!