Web part configuration
Activity Stream web part
Setting Default Filter of the Activity Stream
The personal activity stream always defaults to the My Newsfeed filter (except for users who have no events to see – where the filter switches to All Public Microblogs).
Companies can choose which activity stream filter is displayed by default whenever a user opens a page containing the activity stream web part.
Allowed choices for this default filter selection are:
- My Newsfeed,
- All Public Microblogs,
- Top News.
This organization-widefilter choice is made by editing the web part, and changing the "Default Filter" dropdown.
Narrow View of Activity Stream (Custom CSS Property)
The default activity stream web part is about 450 pixels wide. In some cases, customers want to render a more narrow view (for example, to fit in a narrow web part zone).
To accommodate this case and other cases where customers want to control the display of the activity stream part, a property is available on the personal activity stream web part, in the NewsGator section. It is called Custom Css File Path.
To display the activity stream web part at 300 pixels wide, provide the location of the narrow CSS which comes with Aurea Social. This is located at:
Community Activity Stream web part
Community Roll-up (Hierarchical Communities)
In many organizations, communities have a natural hierarchy. In those situations, it can be very useful to show the activity from communities at a lower level on the “parent” community’s activity stream.
The community activity stream part has two settings to enable and control this rollup behavior.
The “Rollup Child Communities” causes events from communities below (in SharePoint site structure) this community to display on the community activity stream web part.
The second setting (“Exclude Child Communities that are not Followed”) determines whether all sub-community activities are shown or whether only the activities from the sub-communities that the viewer is following are displayed.
The diagram below illustrates how this works:
In this example case, the Product Org community is above Dev, Product Operations, and Product Mgt.
Product Operations has QA, Support, and IT as child communities.
If rollup is enabled on Product Org and the view is not restricted to communities that are actually followed, a visitor to Product Org sees activities from all these communities.
If the view is restricted to only followed communities, then a visitor who is only following QA and Product Mgt would see QA, Product Mgt and Product Org events when visiting the Product Org community.
- SharePoint security is always followed. If a user does not have access to a sub-community, he will not see activities from that community (regardless of what settings are chose on the activity stream web part).
- If a child site is restricted but has a public community below it (this would not be a recommended configuration), the events from the public community will not be rolled up unless the viewing user has access to the restricted site.
- There is no limit to the number of levels that can be rolled up.
- Rollup can be enabled on any community. Product Operations could have the rollup setting on as well in this example to rollup the events from the communities below it.
- The rollup behavior affects the view on the community site but does not change the view on the personal activity stream web part (typically placed on the My Site).