Cross Browser Support:

All products are tested to work with IE 8 and higher.

Not all Bamboo products support all browsers that SharePoint 2016 supports. The products listed below offer cross-browser support for the following: Microsoft Edge, latest version of Google Chrome, latest and immediate previous release of Mozilla Firefox, and latest release of Apple Safari.

• Chart Plus
• Tree View
• Discussion Board Plus

Note: Bamboo products are not supported in an IIS Web garden configuration.

Technical Support, Maintenance Plans and Services

Thank you for choosing our SharePoint enhancement products. We are pleased to provide you with different support plans to meet the needs of your business. All support tickets shall be submitted in the My Bamboo portal or we cannot guarantee timely support.

Our official support business hours are 8 AM to 6 PM ET (GMT -5) Monday through Friday, however we have a team of engineering experts monitoring our help desk system from late Sunday evening through 6pm on Friday, barring holidays. Our highly qualified off-shore staff can answer many support questions and provide escalations to our US-based team when deemed necessary.

SUPPORT PLANS:

NOTE: Bamboo provides free support via My Bamboo during the free 30-day trial period.

Basic Annual Support & Maintenance (included for one year with the initial product purchase and requires annual renewal):

• Unlimited access to Bamboo’s Knowledge Base, Online Documentation and Product Forums.
• My Bamboo support for up to 6 support incidents per year.
• 2 business day initial response time for Severity 1 & 2 issues.
• One year of free maintenance and service pack update releases.
• Email support via the My Bamboo ticketing system.

Premium Annual Support & Maintenance (Please refer to each product’s description page for pricing information)

• Unlimited access to Bamboo’s Knowledge Base, Online Documentation and Product Forums.
• My Bamboo support for an unlimited number of incidents per year.
• 4 business hour initial response time for Severity 1 & 2 issues.
• When required for an issue, Bamboo may use “call-back” telephone support or web meeting tools from 9 AM to 5:30 PM ET (GMT -5).
• One year free maintenance and service pack update releases, as well as, major version update releases.
• Invitation to participate in beta release programs.

Bamboo Support includes:

• Problem isolation and identification as related to Bamboo products.
• Bamboo error message analysis and resolution.
• Bug reporting and follow up.
• General advice on product issues involving usage, implementation, licensing, operation, and functionality (please note that this does not include how to implement products for specific business use-cases, nor does it include step by step assistance with installing the product in a user environment).
• Up-to-date information on current releases, product compatibility, restrictions, enhancements, workarounds and fixes.

Bamboo Support specifically does NOT include:

• Installation Support Services for Bamboo products. For more information about available Installation Support Services, please click here.
• Bamboo Product Training for administrators or end users. For more information about available Bamboo Product Training, please click here.
• Design and Configuration Services for Bamboo products. For more information about available Design and Configuration Services for Bamboo products, please click here.
• System/SharePoint administration not related to Bamboo products.
• Debugging or inspecting non Bamboo products or implementations that contain user-written code
• Support of Bamboo products on non-standard or inadequate system environments.
• Technical support for end of life software releases, as defined by Bamboo .
• Please note that Bamboo’s support staff is trained to work with SharePoint Administrators, Developers and expert power users.

What You Can Expect

The time required to resolve support questions will vary based upon your specific SharePoint implementation. Our promise to you is to begin problem resolution within the response time period of your contract, and that we will make every reasonable attempt to diagnose and resolve issues in a timely manner. Bamboo Solutions does not guarantee a specific resolution time.

Bamboo will classify support issues and prioritize according to your support plan and the following severity levels:

• Severity One (Urgent): A severity one (1) issue is a production problem which is severely impacting the client’s production SharePoint environment or Bamboo products; systems are down and no procedural work around exists.
• Severity Two (Important): A severity two (2) issue is a production issue when service is degraded. While time sensitive, the overall business impact is minimal.
• Severity Three (Medium): A severity three (3) issue is a medium-to-low impact problem in which there are issues in the production or other environments which need to be resolved, but are not time sensitive. This severity may also be applied to questions about functionality.
• Severity Four (Low): A severity four (4) issue is a general usage question, recommendation or request. There is no impact to production or other environments.

The Support Process

Help us to help you better by using the My Bamboo portal to report issues to our Support Team. Include as much detail as possible when reporting issues, including exact error messages and specific steps to reproduce the issue. Please include screen shots and a current copy of the applicable web.config file if possible.

When you submit a ticket using My Bamboo you will receive an automated acknowledgment via email that may include links to Product Forums, the Knowledge Base and Online Documentation. If you do not receive the email, please check your spam/junk email folder for the message.

• A Bamboo Support Engineer will attempt to contact you within the time period designated by your support contract and the determined severity of your issue. We may be able to resolve your issue immediately, however, more commonly, we will request that you follow a particular course of action and then attempt to replicate and diagnose the issue.
• For customers with premium support, your Support Engineer may request to contact you via telephone or web meeting in order to more quickly collect information about the issue.
• For all customers, your Support Engineer may ask you to temporarily change your Bamboo configuration, SharePoint configuration and/or reinstall your Bamboo product as part of the troubleshooting process.
• If these steps do not result in a solution, your Support Engineer will escalate the issue to a Senior Support Engineer and then to our Engineering Team, who will again attempt to replicate the problem, diagnose the root cause, and make a recommendation.

Issue Resolution

Once an issue has been registered through My Bamboo, resolution is defined as accomplishing any one of the following:

• Providing a reasonable solution to the issue
• Providing a reasonable work-around to the issue
• Determination by Bamboo that the issue is an enhancement request and forwarding the request to Bamboo Product Management for future consideration
• Escalation by the Bamboo Support team of the incident/product defect to Bamboo Engineering for review.

See Also:

• How to Renew Support

When you purchase a Bamboo Suite, you are automatically subscribed to e-mail alerts for new product notifications. To manage the product alerts you receive, log in to My Bamboo and click the My Alerts link.

New products and product versions published in the past 15 days are also identified in the Toolkits, Suites and Libraries page. In the Individual Product Installation Packages section, look for New! next to the product name.

You can also view Release Notes about individual products from the product’s landing page here in the Bamboo Documentation area.

You will see two tabs when you click on the tile for Subscriptions.

The Bamboo Technical Library™ (TechLib) can help you achieve better SharePoint solution building results. With Bamboo’s entire set of products for SharePoint 2007, SharePoint 2010, and SharePoint 2013 at your disposal, you can quickly create application prototypes and test working pre-production solutions. All of your subscriptions will appear under this tab. See Tech Lib Subscription for more details.

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. This tab shows you which Cloud Parts you are subscribed to.

If you can’t find something you like in the pre-defined Chart Skins, you can create your own CSS using the Style Sheet tool. Select Custom Settings and click the Edit button to create a custom style sheet.

Tip: To customize an existing Chart Skin, select the skin first. When you click the Edit button, the settings for that skin are pre-populated in the edit screen.

If you create a custom CSS and then select a new Chart Skin later, your CSS will be overwritten with the new skin.

NOTE: Series colors cannot be defined in the custom Style Sheet. Use the Series Palette option or select custom series colors in the Chart Data Settings.

See also:

• Chart Title Settings
• Chart Orientation
• Pie Chart Diameter Scale
• Chart Size
• Language Settings
• Look & Feel Settings
• Chart Options
• Series Palette

This topic applies to all Bamboo products using WSS 3.0, MOSS 2007, SharePoint Foundation 2010, and/or SharePoint Server 2010. Below you will find information on the following procedures:

• Stopping and Starting the World Wide Web Publishing Service
• Restarting IIS

IIS and W3SVC Defined

• Microsoft Internet Information Services (IIS) is a web server providing a management platform for developing and hosting Web applications and services.
• The World Wide Web Publishing Service (W3SVC) manages the HTTP protocol and HTTP performance counters for Internet Information Services (IIS).

Either of these may need to be stopped or restarted during installation or upgrade of Bamboo Solutions products for system changes to take effect. Bamboo product installation’s Best Practices is to stop the World Wide Web Publishing Service during product installation.

Exception: On SharePoint 2010, when a web application is configured to use Claims Based Authentication, and the checkbox to Automatically Activate Features is checked in the Bamboo installer, and the World Wide Web Publishing Service (W3SVC) is stopped during the installation, the installation will fail because the features cannot be automatically activated. This is true whether Forms Based Authentication (FBA) or Windows Authentication is in use.

For more information, see: KB.12732 – HOWTO: SharePoint 2010 Solution Deployment when Claim Based Authentication is Configured (rewrite in DF)

Stopping and Starting the World Wide Web Publishing Service

When a Bamboo product is installed, system checks are performed to make sure the SharePoint server is ready for the installation to proceed. One of those checks is to confirm that the World Wide Web Publishing Service is stopped. If it is not stopped, the Bamboo product installer will display a warning. Installation may proceed without stopping the World Wide Publishing Service; however, Bamboo recommends that the World Wide Web Publishing Service be stopped to ensure that system files that need to be updated during installation are not locked. If you do not stop the service as recommended, installation may fail.

To stop and start the World Wide Web Publishing Service from the command line in your server console:

 sc stop w3svc 
 sc start w3svc 
 sc query w3svc (shows you the service status)

To stop and start the World Wide Web Publishing Service from the Control Panel:

1. Go to Start > All Programs > Administrative Tools > Services.
2. In the services list, right-click World Wide Web Publishing Service, and then click Stop (to stop the service) or Start (to start it after it has been stopped), or Restart (to restart the service when it is running).

Restarting IIS

After product installation, it may be necessary to restart IIS for all changes to take effect.

To restart IIS, type the following command at the command line:

iisreset /noforce

Additional installation troubleshooting steps can be found in Bamboo product installation Best Practices.

Step	Action	Result
1.	Launch Conductor Studio from your Expense Reports library by clicking Settings > Create or Edit Workflows.

Workflow Process Steps

• Step One – Set Up SharePoint
• Step Two- Launch Conductor Studio
• Step Three – Build the Workflow
• Step Four – Deploy the Workflow
• Step Five – Run the Workflow

This workflow will use four widgets.

1. Request Approval (used twice in this example)
2. Conditional Branch
3. Update Item
4. End Workflow

NOTE: After configuring each widget, make sure to click the Apply button at the bottom of the Widget Properties tab to save its settings.

Widget	Action	Result
Request Approval Widget	Since all expense reports have to be approved first by a manager, start by dragging a Request Approval widget to the Studio diagram. For the purposes of this scenario, the following properties are important: The Approvers property is a lookup to the “Manager” field in the Expense Reports library, which gets populated by the InfoPath form. The Allow Request Change property is set to Yes. If you’ve ever had an expense report rejected for something trivial, you know how frustrating it can be to have to start the whole process all over again. Allow Request Change lets the approver assign a new task for someone else to complete first, such as having the employee add that missing name to a meal expense. When that task is completed, the approver is notified and can pick up where he left off. Some basic information about the expense report is provided in the Task Name and Task Description properties. Since the approving manager needs a basic idea of what he is approving, several lookups to actual expense report data have been included in these properties.	TIP: Copy & Paste Widgets You can copy and paste the original Request Approval widget. Conductor will copy the widget properties too, so this will save you some configuration time. Right-click the widget and choose Copy, then right-click inside the Conditional Branch widget’s True branch and choose Paste. All the properties of the Request Approval widget are copied, including any widgets inside it, so be sure to delete the extra Conditional Branch widget by right-clicking on it and choosing Delete. The Request Approval widget is highly customizable. You can read about each property in detail in the Request Approval Widget topic. Learn more about Workflow Conductor Lookups, References, and Variables.
Conditional Branch Widget	You can force the workflow to check if an expense report needs additional approval using the Conditional Branch widget. Drag a Conditional Branch widget inside the Approved branch of the Request Approval widget. To set the dollar amount condition required by this scenario, click the next to the Condition property to display the Condition Builder, and configure it as shown here. With this condition, anything over $1,000 will follow the True branch, and anything $1,000 or less will follow the False branch. Learn more about Conditional Branch Widget.
Update Item Widget	Because employees want to see the status of the expense report, use Update Item. Workflow Conductor has two other widgets that perform a similar function: Update Item and Set Field Value. Either will work here, but this example is a little faster to configure if the field you want to update already has possible values in a Choice field. It will be used extensively within the workflow to give employees the updates they may need. TIP: Name That Widget As you get deeper into designing your workflow, you can make it easier to follow by renaming widgets, starting with the Update Items. Click on each one and change the Display Name property to something a little more descriptive, like the actual status name. (Don’t forget to click Apply!) You’ll see that the widget names now reflect whatever you name it. Do the same with the Request Approval widgets and the Conditional Branch widget, and your workflow will be simpler to follow.
Request Approval Widget (second pass)	You already have a Request Approval widget for manager approval. To set another approval, drop a new Request Approval widget inside the True branch of the Conditional Branch widget (remember, True matches anything more than $1,000). Configure it the same way as the original widget, but this time use a lookup to the “VP” field in the Approvers property. Tip: You can also copy and paste the original Request Approval widget. Conductor will copy the widget properties too, so this will save you some configuration time. Right-click the widget and choose Copy. Right-click inside the Conditional Branch widget’s True branch and choose Paste. All the properties of the Request Approval widget are copied, including any widgets inside it, so be sure to delete the extra Conditional Branch widget by right-clicking on it and choosing Delete.
End Workflow Widget	If an expense report gets rejected by the manager, the workflow simply updates the status and ends, since the workflow would follow the Rejected path of the first Request Approval widget and there are no widgets after it. However, if an expense report is over $1,000 and gets rejected by a VP, the workflow as it is currently configured would update the “Approval Status” column to Approved when it exits the Request Approval and Conditional Branch widgets. To prevent this from happening, drag an End Workflow widget to the Rejected branch of the second Request Approval widget.
	Now the workflow ends in case of a VP rejection.

Workflow Process Steps

• Step One – Set Up SharePoint
• Step Two- Launch Conductor Studio
• Step Three – Build the Workflow
• Step Four – Deploy the Workflow
• Step Five – Run the Workflow

Workflow Process Steps

• Step One – Set Up SharePoint
• Step Two- Launch Conductor Studio
• Step Three – Build the Workflow
• Step Four – Deploy the Workflow
• Step Five – Run the Workflow

Step	Action	Result
1.	Go to Publish > Deploy in the Conductor Studio menu, give your workflow a name and an optional description, and click Save.	Your workflow gets deployed and is now available in your Expense Reports library.
For reference, here is what your completed workflow will look like:

Workflow Process Steps

• Step One – Set Up SharePoint
• Step Two- Launch Conductor Studio
• Step Three – Build the Workflow
• Step Four – Deploy the Workflow
• Step Five – Run the Workflow