Sort SharePoint alerts in My Alerts Organizer

Sort SharePoint alerts in My Alerts Organizer

Overview of My Alerts Organizer display
Step Action Result
1. Use the site tree to navigate to the site containing the alerts you want to delete
My Alerts Organizer site tree
The contents of the My Alerts Organizer will change to show alerts associated with the selected site
2. From the My Alerts Organizer display page click the header of the column you want to sort
Image of the column header in My Alerts organizer
With the first click the column will be sorted in ascending order.
Sort ascending
2. Click the column header a second time to change to sort from ascending to descending orderClick column header to change sort order Sort descending
3. Click the column header a third time to turn off sorting Alerts items will return to the default sort order

Release Notes for My Alerts Organizer

Release Notes for My Alerts Organizer

NOTE: Release Notes will open in a new browser tab

WSSv3/MOSS SharePoint 2010 SharePoint 2013
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.

Bamboo Solutions has also begun releasing Bamboo Apps to the SharePoint Store, for additional details, see the SharePoint Apps & Mobile products page where you can get the latest info about each of our Apps as they release to the Microsoft Store.

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

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:

Overview of the My Alerts Organizer User display

Overview of the My Alerts Organizer User display

Image of the My Alerts Organizer user display

Function
1. The site tree allows you to navigate to other sites in the site colletion to see alert items
HW40_Site_Tree.png
2. Image of site hyperlinkClicking the site name hyperlink will take you to the site’s home page
3. Image of Add button in the toolbarFrom the toolbar you can Add, Delete and Toggle alerts created on items in the selected site. The Delete and Toggle options will be greyed out until an item is selected in the console
4. Image of Grouping barSharePoint alerts will be displayed in the console for the selected site and can be Grouped and Sorted by column header

5. Image of select all checkbox in toolbarThe select all checkbox in the upper left allows you to quickly Delete or Toggle the alerts shown on the current page
6. Image of edit, delete and toggle controls associated with individual alert items Each item has icons that allow you to Toggle, Delete or Edit the alert

Overview of My Alerts Organizer

Overview of My Alerts Organizer

Microsoft’s Windows SharePoint Technology and Services, which includes SharePoint Portal Server (SPS) 2003, Microsoft Office SharePoint Server (MOSS) 2007, Windows SharePoint Services (WSS), SharePoint Foundation 2010, SharePoint Server 2010, SharePoint Foundation 2013 (New), and SharePoint Server 2013 (New), allows teams to create Web portals for information sharing and document collaboration that help increase individual and team productivity. It also serves as a platform for application development, providing IT resources such as portals, team workspaces, e-mail, presence awareness, and Web-based conferencing. SharePoint enables developers to quickly build collaborative applications based on a robust set of out-of-the-box functionalities.

Currently, SharePoint users can only see the alerts they’ve set up for a particular list or library, including down to individual items. With this fragmented view, it is easy to forget which alerts you’ve set up and which ones you need to set up. Users don’t have a way to manage all of their alerts, from a single location for each site within a site collection.

The Bamboo My Alerts Organizer feature provides users with the ability to view all the alerts they have setup for each site in a site collection from a single view. Users can access the My Alerts Organizer right from their SharePoint site through the user’s personal menu. This feature allows users to easily create new alerts, group alerts, enable /disable alerts, delete alerts, and perform inline editing of alert frequency settings. Add alerts from any List, Document Library, Picture Library or Discussion Board.

Migrating My Alerts Organizer from SharePoint 2007 to SharePoint 2010

Migrating My Alerts Organizer 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.13 Minimum SharePoint 2010 Product Release 10.4.40
In-Place Upgrade
Issues My Alerts Organizer migrates without any errors or additional steps required.
Resolution N/A
Database Attach Upgrade Method
Issues My Alerts Organizer migrates without any errors; however, existing SharePoint alerts from SharePoint 2007 Farm will not run. This is a SharePoint issue, not a My Alerts Organizer issue. Using the Database Detach/Attach migration method breaks existing SharePoint alerts because they store the static URL that references the original SharePoint farm URL.
Resolution To fix SharePoint alerts migrated from a SharePoint 2007 farm, refer to Update alerts by using Windows PowerShell (SharePoint Foundation 2010) from Microsoft.

Migrating My Alerts Organizer from SharePoint 2010 to SharePoint 2013

Migrating My Alerts Organizer 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.43 Minimum SharePoint 2013 Product Release 10.4.51.2013
Database Attach Upgrade Method
Issues The My Alerts Organizer 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.