Configuring the Alfresco 5 Activity Stream

Showing results for 
Search instead for 
Did you mean: 

Configuring the Alfresco 5 Activity Stream

Established Member
1 11 8,587


In Alfresco 5 we have added two new types of events to the activity stream - for document Download and Preview events. Some concerns have been raised about the number of activities that may be added to the site or user streams and also concerns around privacy - seeing what documents other users have been downloading or previewing.

Firstly, the ability of the server to process activities has been improved considerably since Alfresco 4. The activity processing is now multi-threaded and also handles more activities per stream.

Secondly, the same ACL/permission enforcement that has always been present in Alfresco is still present in 5.0 - that has not changed! So the ability to see a public document is still the same for all users and if a document is private, it will remain private. For example if you add/modify/download a document that is private to you then activity events for the action will not appear on the public activity stream for other users in the site.


The activities which are processed by the system can be configured in the Alfresco repository. A config file change is needed to disable certain activities from the various summary processing options. For example if you are still concerned about the Download and Preview activities and want to disable them, then this is how you would do it.

RSS Summary Feeds

To disable them from the RSS summary feeds used by the Document Library components we need to override the bean that deals with processing that list.

In the Alfresco repository tomcat instance, in the tomcat/shared/classes/alfresco/extension folder create a spring context XML file called custom-web-context.xml. If you already have this extension file, then add the bean shown below to the existing file.

The beans that process activities for RSS feeds work against a list of known activity types - the types that are generated by applications such as Alfresco Share. To remove the Download and Preview activities we identify the IDs of those activities which are org.alfresco.documentlibrary.file-previewed and org.alfresco.documentlibrary.file-downloaded and remove them from the list for the documentLibraryActivitySummaryProcessor bean definition.

<?xml version='1.0' encoding='UTF-8'?>

<beans xmlns=''



<bean id='documentLibraryActivitySummaryProcessor' class=''>

<property name='registry' ref='activitySummaryParser' />

<property name='eventTypes'>



















Restart Alfresco then no more Download and Preview activities in RSS feeds. You can modify the bean config above to remove any other activity types you don't like from the list.

Removing from Activity Email Summary

Of course the Activity Email Summary is generated by something completely different and uses different configuration - anything else just wouldn't be Alfresco. To deal with that, we need to override the bean that handles the generation of the list of Activities for Email templates.

Fortunately that is not too hard either. Create the following folder path tomcat/shared/classes/alfresco/extension/subsystems/ActivitiesFeed/default/default and create a file called custom-activities-feed-context.xml. This specifically overrides configuration for the ActivitiesFeed sub-system. A sub-system in Alfresco is a powerful and highly configurable component that can be enabled/disabled and tweaked at run-time - however because of this flexibility comes some complexity with the configuration - which is why we have the strange looking folder path - see this wiki page for more info.

The file should contain the following bean override:

<?xml version='1.0' encoding='UTF-8'?>

<beans xmlns=''



<bean id='feedModelBuilderPrototype' class='org.alfresco.repo.activities.feed.DefaultActivitiesFeedModelBuilder' scope='prototype'>

<property name='ignoredActivityTypes'>








Again you can see the activity types specified in a list to be ignored during Activity processing.

Removing from Alfresco Share

To remove the activities from those made available to Alfresco Share dashlets add the following extension config files to your Alfresco Share Tomcat instance (which will be the same Tomcat instance if you are using a default installed package).




Both files are identical, so create and edit them to contain:



<filter type='today' label='today' />

<filter type='7' label='7days' />

<filter type='14' label='14days' />

<filter type='28' label='28days' />



<filter type='mine' label='mine' />

<filter type='others' label='others' />

<filter type='all' label='all' />

<filter type='following' label='following' />



<filter type='org.alfresco.profile.status-changed,org.alfresco.comments.comment-created,org.alfresco.comments.comment-updated,org.alfresco.documentlibrary.file-updated,org.alfresco.documentlibrary.file-added,org.alfresco.documentlibrary.files-added,org.alfresco.documentlibrary.files-deleted,org.alfresco.documentlibrary.files-updated,org.alfresco.documentlibrary.file-deleted,org.alfresco.documentlibrary.inline-edit,,,,,,,,,,' label='allItems' />

<filter type='org.alfresco.profile.status-changed' label='statusItems' />

<filter type='org.alfresco.comments.comment-created,org.alfresco.comments.comment-updated' label='commentItems' />

<filter type='org.alfresco.documentlibrary.file-updated,org.alfresco.documentlibrary.file-added,org.alfresco.documentlibrary.files-added,org.alfresco.documentlibrary.files-deleted,org.alfresco.documentlibrary.files-updated,org.alfresco.documentlibrary.file-deleted,org.alfresco.documentlibrary.inline-edit,,,,,,,' label='contentItems' />

<filter type=',,' label='membershipItems' />



The important bit is we are removing the same file-previewed and file-downloaded activities mentioned above from the filter-activities configuration.

This may also be a good time to review the above configuration - as it allows you to configure what filters are shown in the Activities summary dashlets, across what date ranges and what other Activities they will show. For instance if you don't want to see 'status' updates from users, then you could completely remove the org.alfresco.profile.status-changed references and filter section.