Change the current site for Alerts Administrator

Change the current site for Alerts Administrator

Overview of Alerts Administrator display

Alerts Administrator provides users, with the appropriate administrative permissions, the ability to quickly and easily create and manage SharePoint alerts.

Unlike out-of-the-box alert administration tools, Alerts Administrator allows you to work with alerts in a web application simply by changing the current site information displayed in the console.

Step Action Result
1.

To view the alerts associated with another site, click the edit icon next to the site path hyperlink on the Alerts Administrator display page
Current site1.png

NOTE: Clicking the hyperlink will return you to the sites homepage

The URL for the existing current site will be displayed
Alerts_Admin_Existing_Site_URL.png
2.

Replace the existing text with the URL to the desired site located in the same web application and click the Load button
Alerts_Admin_Enter_New_Site_URL.png

NOTES:
1. The new site must be in the same web application
2. You must have administrative permissions on the destination site to complete this action or you will see the following message:

HW39_Premissions_Error.png

HW39_New_Site_URL.pngThe Enter Site URL field will remain visible on the page and the console will display the alerts associated with the new site
Alerts_Admin_New_Site_Display.png

Sort SharePoint alerts in Alerts Administrator

Sort SharePoint alerts in Alerts Administrator

Overview of Alerts Administrator display
Step Action Result
1. From the Alerts Administrator console click
the header of the column you want to sort
Alerts_Admin_click_to_sort.png
With the first click the column will be sorted in ascending order.
Alerts_Admin_Sort_Asc.png
2. Click the column header a second time to change to sort from ascending to descending orderAlerts_Admin_click_to_sort_desc.png Alerts_Admin_Sort_Desc.png
3. Click the column header a third time to turn off sorting Alerts items will return to the default sort order

Release Notes for Alerts Administrator

Release Notes for Alerts Administrator

NOTE: Release Notes will open in a new browser tab

WSSv3/MOSS SharePoint 2010 SharePoint 2013 SharePoint 2016
Release Notes Release Notes Release Notes Release Notes
Microsoft ended mainstream support for SharePoint 2007 in October 2012. See Microsoft’s Lifecycle Support Policy.
At that time, Bamboo stopped enhancements to our SharePoint 2007 product line, but continues to provide support and bug fixes to customers with active support contracts until October 2017. Previously purchased licenses will continue to function after October 2017, but support for these products will end, and no additional bug fixes will be provided beyond that time. Bamboo plans to cease selling new licenses and annual support contacts for its SharePoint 2007 products in October 2016 to ensure customers will be eligible to receive support for at least one year after purchase.
Microsoft plans to end mainstream support for SharePoint 2010 in October 2015. See Microsoft’s Lifecycle Support Policy. At that time, we will stop any enhancements for our SharePoint 2010 product line but will continue to provide support and bug fixes for our SharePoint 2010 products to customers with active support contracts until October 2020. Previously purchased licenses will continue to function after October 2020, but support for these products will end, and no additional bug fixes will be provided beyond that time. Bamboo plans to cease selling new licenses and annual support contacts for its SharePoint 2010 products in October 2019 to ensure customers will be eligible to receive support for at least one year after purchase.

Visit our website where you can get the latest info about each of our products for SharePoint 2013.

A separate installation package and license key is required for SharePoint 2013 deployment. For additional details, review the following knowledge base articles:

Bamboo Solutions has also begun releasing products for SharePoint 2016. For additional details, check the product release notes in the link above, or contact us.

For details on migration, see the Knowledge Base Article “Migrate Bamboo Products from SharePoint 2013 to SharePoint 2016”

Understanding Bamboo Releases:

  • Bamboo offers Trial, Basic and Premium support.
    • Free Trial support expires after 30 days.
    • For more information about Basic and Premium support, please see the Support Plans page.
    • There may be a fee to upgrade from a major version to another.

See Also:

Disable a site’s SharePoint alerts in Alerts Administrator

Disable a site’s SharePoint alerts in Alerts Administrator

Overview of Alerts Administrator display

The toggle feature in Alerts Administrator allows an administrator to disable or enable selected alerts. Needless to say, green equals ON, and toggling an alert to OFF will change the associated toggle icon to red.

NOTE: The following actions can only be performed on alert items on the displayed page.

Step Action Result
1.

From the Alerts Administrator page click the Toggle button associated with the specific alert you want to toggle
Alerts_Admin_Individual_Toggle.png

OR

Toggle multiple alerts by selecting the desired alert items on the display page and clicking Toggle in the ribbon
Alerts_Admin_Bulk_Toggle.png

OR

Toggle all alerts on the display page by clicking Select All and Toggle Alerts_Admin_Select_All_Toggle.png

The alert’s toggle status indicator will reflect the change in alerts status.

Overview of Alerts Administrator display

Permissions required to use Alerts Administrator

Permissions required to use Alerts Administrator

Overview of Alerts Administrator display

When Alerts Administrator has been activated on the web application, the Alerts Administrator tool will be available to all users with the SharePoint Manage Alerts permission, which lets you manage alerts for all users on a web site. This permission is easily granted via Site Permissions.

Methods for granting SharePoint permissions: SharePoint 2007 SharePoint 2010 SharePoint 2013
The Grant Permissions option adds users to existing SharePoint
groups. The following default SharePoint Groups grant the required
Manage Alerts permission:
Alerts_Admin_Grant_Permissions.png
Full Control Full Control Full Control
The Grant permissions directly option grants permission levels
directly to a user. These Permission levels include the
Manage Alerts permission by default:
Alerts_Admin_Grant_Permissions_Directly.png
Full Control Manage Hierarchy
&
Full Control
Manage Hierarchy
&
Full Control

Overview of User Display Custom Identifier

Overview of User Display Custom Identifier

HW41H_UseCase_Identifier.jpgAs an end user, what you see depends on how your admin has configured the column. Custom Identifier Column can generate a unique identifier as illustrated here.

NOTE: Custom Identifier Column does not display on the New Item form or the Edit Item forms. It is only displayed in the Display form and List views (where assigned).

Migrating Alerts Administrator from SharePoint 2007 to SharePoint 2010

Migrating Alerts Administrator from SharePoint 2007 to SharePoint 2010

Be sure you have at least the Minimum SharePoint 2007 Product Release (shown in the table below) installed before migrating. If not, upgrade your Bamboo product release before migrating. For more information, see Upgrading your Bamboo Web Part. Also, the target SharePoint 2010 farm requires at least the Minimum SharePoint 2010 product release shown.

Icon-Warning IMPORTANT: When migrating from SharePoint 2007 to SharePoint 2010, you MUST select the option to change existing SharePoint sites to use the new user experience. Your Bamboo products will not perform as expected with the old look and feel.

Minimum SharePoint 2007 Product Release 1.4.12 Minimum SharePoint 2010 Product Release 10.4.30
In-Place Upgrade
Issues Alerts Administrator migrates without any errors or additional steps required.

Resolution N/A
Database Attach Upgrade Method
Issues Alerts Administrator migrates without any errors; however, existing SharePoint alerts configured on the SharePoint 2007 Farm will not run. Using the Database Detach/Attach migration method breaks existing SharePoint alerts. This is because SharePoint alerts store the static URL that references the original SharePoint farm URL.
Resolution To fix SharePoint alerts migrated from a SharePoint 2007 farm, refer to the following Microsoft article that describes Invoke-AlertFixup, a Windows PowerShell advanced function used to update the URL of a Web application used in alert e-mails after a Web application address changes.

Migrating Alerts Administrator from SharePoint 2010 to SharePoint 2013

Migrating Alerts Administrator from SharePoint 2010 to SharePoint 2013

Be sure you have at least the Minimum SharePoint 2010 Product Release (shown in the table below) installed before migrating. If not, upgrade your Bamboo product release before migrating. For more information, see Upgrading your Bamboo Web Part. Also, the target SharePoint 2013 farm requires at least the Minimum SharePoint 2013 product release shown.

Icon-WarningIMPORTANT: When migrating from SharePoint 2010 to SharePoint 2013, the Database Attach Upgrade Method is the only method supported.

Minimum SharePoint 2010 Product Release 10.4.52 Minimum SharePoint 2013 Product Release 10.4.62.2013
Database Attach Upgrade Method
Issues The Alerts Administrator migrates without any errors or additional steps required.
Resolution N/A

Localize Bamboo Applications or Custom Columns

Localize Bamboo Applications or Custom Columns

Overview of the localization process for Bamboo Products

Bamboo applications and custom columns are slightly different than web parts when it comes to localizing/translating. The user interface isn’t confined to a web part, but can exist as site definitions or other custom pages. For example, the configuration of a Bamboo custom column is within the SharePoint list settings area.
The text strings that require translation are located in different files than the strings that appear in a web part.

Changing the language or text for an application or custom column is a multi-step process:

Top

About the Language Files

Text displayed in a Bamboo application may be included in one or both of the following locations:

  • Provisioning Resources. These resources are located in the 12, 14, or 15 “Hive”, in the Resources folder. The number of the Hive depends on the version of SharePoint you are using (e.g., SP2007 has a 12 Hive, SP2010 has a 14 Hive, and SP2013 has a 15 Hive). 14Hiveresources.jpg

    The Bamboo.*.resx files include text used in site features, site definitions, list definitions, and other provisioning resource elements. Any changes you make in these files will apply to new product instances only.

  • Application/Runtime Resources. These are also located in the 12, 14, or 15 Hive, but in the CONFIGResources folder.The Bamboo.*.resx file in the CONFIG folder is different than the one included in the Resource folder.14HiveCONFIGResources.jpg This one includes text used in application pages, custom site menu actions, navigation elements, and other runtime resources. Any changes you make will apply to new and existing product instances only.

In each location, there may be multiple versions of Bamboo.*.resx files with identical content. The different files are provided for English (en-US), German (de-DE), French (fr-FR), and Spanish (es-ES). The content of all files is in English until you translate it to your language. If your site is configured to use a language that does not have a corresponding Bamboo product .resx file, copy an existing file and rename it to include the culture name for that language pack. For example, create a file for Italian by saving the default file as Bamboo.[Product].it-IT.resx. Make your changes to this new file. If your site is configured to use a specific language but you do not have a culture-specific file, the product will use the default Bamboo.[Product].resx file instead.

Icon-WarningIMPORTANT: If you customize one of the default resource files provided with the product, your changes will be overwritten when you upgrade.

To avoid losing customizations, copy the customized file to a different location (not the same folder) before upgrading. After the upgrade is finished, compare the new file with your customized file to incorporate any new entries. Then copy the merged file to the Resources folder. Culture-specific files created for languages that are not provided with the product will not be overwritten during an upgrade, but you still need to incorporate new resource entries.

Top

Editing text in resource files

Icon-WarningIMPORTANT: Before making any changes, back up your original file to a different folder.

To change text in a resource file, open it in a text editor and locate the text you want to change. Editable text is usually found between the <value></value> tags, as shown in the screen shot below. Do not modify the data tag. If you want to remove text completely, delete only the text; do not delete the <data> or <value> entries from the file, or the server will display an error message. In the example below, the editable text is highlighted in gray.

Common_resxEdit.jpg

When you are finished with your changes, save the file and copy it to the appropriate Resources *folder on *all Web front-end servers in your SharePoint farm. Follow the instructions below to make your changes take effect.

Top

Applying Language File Updates

To apply changes to Provisioning Resource Files:

If you modified the provisioning resources file, apply your changes by restarting Web services with the following command on all Web front-end servers.

iisreset

NOTE: changes to provisioning resources affect new instances of the Bamboo product only; existing instances of the product are not updated.

To apply changes to Application/Runtime Resource Files:

If you modified the application/runtime resources file, apply your changes by executing the following stsadm command on all Web front-end servers. This command copies the updated resource file to the App_GlobalResources folder of each Web application. Changes apply to existing product instances and any new instances you create.

stsadm -o CopyAppBinContent

NOTE: Changes apply to EXISTING product instances AND any new instances you create.

Important Notes About Manual Installation

Important Notes About Manual Installation

Options for Installing

Bamboo Web License Manager: Most Bamboo products include the Bamboo Web License Manager (Bamboo.Web.Licensing.wsp) in the install. It needs to be installed only once on the farm (regardless of the number of Bamboo products you are using) and should be added to the solution store on the server(s) running the Central Administration service, and deployed to the Central Administration Web application.

msi*.x64.msi: Some MSI installers in the msi installation folder have a 32-bit version and a 64-bit version. The 64-bit version will include .x64 in the file name. Run the version of the MSI that is appropriate for your operating system. Do not install both.

PackInstallation.wsp: Some products include an installation folder called PackInstallation.wsp. This folder is not needed during the manual installation process and can be ignored.

For manual installs in a SharePoint 2007 environment:

  • Shared Assemblies Library (SharePoint 2007): If a product includes the Shared Assemblies Library (msiBamboo.Core.V1.2.msi), you must install the MSI on all Web front-end servers in the farm.
  • Microsoft AJAX Extensions (SharePoint 2007): If a product includes the Microsoft AJAX Extensions (msiASPAJAXExtSetup.msi), you must install the MSI on all Web front-end servers in the farm. See Bamboo products that use AJAX if you are unsure if your product uses AJAX.
  • Bamboo AJAX Config (SharePoint 2007): If a product includes the Microsoft AJAX Extensions, the Bamboo AJAX Config (Bamboo.AJAX.Config.wsp) solution must also be deployed. Deploy the solution to all Web applications in the farm where the product will be installed. You may also need to deploy this solution to the Central Administration Web application. Consult the Online Documentation for the specific product for more information.
    See Bamboo products that use AJAX if you are unsure if your product uses AJAX.