<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Filtering activity types by site or node in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/filtering-activity-types-by-site-or-node/m-p/301853#M254983</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Alfresco already has a concept that allows extensions to be easily plugged in: behaviours / policies. Similar to the copy callback policy, the activity poster service could provide an activity callback policy hook. Such a callback could then&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;- reject an activity entirely&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;- filter / augment data collected for the activity&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;- trigger additional activities (if relevant)&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The callback for the policy would need to have an abstract API based on NodeRef (FileInfo is very restrictive, not everyone uses "only" files or folders) and the poster service would need to internally handle all the different API variants it provides to somehow be standardized on that policy API.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;The only thing that may be needed is some way to alternatively bind policies not on the type of nodes but sites, either by preset (best practice for functionally grouping) or short name (e.g. special bootstrapped-sites).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;But I may be biased towards adding a policy for this because I miss quite a lot of higher-level policies in various places…&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 23 Jun 2016 08:02:03 GMT</pubDate>
    <dc:creator>afaust</dc:creator>
    <dc:date>2016-06-23T08:02:03Z</dc:date>
    <item>
      <title>Filtering activity types by site or node</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/filtering-activity-types-by-site-or-node/m-p/301852#M254982</link>
      <description>As most of you will know, Alfresco 5 introduced two new activity stream event types, Downloaded and Previewed. Kev's blog https://www.alfresco.com/blogs/kevinr/2014/10/14/configuring-alfresco-activity-stream/ explains more on it. Initially, it was a bit hard to filter out certain types, but Loftux (</description>
      <pubDate>Wed, 22 Jun 2016 12:36:28 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/filtering-activity-types-by-site-or-node/m-p/301852#M254982</guid>
      <dc:creator>nickburch</dc:creator>
      <dc:date>2016-06-22T12:36:28Z</dc:date>
    </item>
    <item>
      <title>Re: Filtering activity types by site or node</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/filtering-activity-types-by-site-or-node/m-p/301853#M254983</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Alfresco already has a concept that allows extensions to be easily plugged in: behaviours / policies. Similar to the copy callback policy, the activity poster service could provide an activity callback policy hook. Such a callback could then&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;- reject an activity entirely&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;- filter / augment data collected for the activity&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;- trigger additional activities (if relevant)&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The callback for the policy would need to have an abstract API based on NodeRef (FileInfo is very restrictive, not everyone uses "only" files or folders) and the poster service would need to internally handle all the different API variants it provides to somehow be standardized on that policy API.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;The only thing that may be needed is some way to alternatively bind policies not on the type of nodes but sites, either by preset (best practice for functionally grouping) or short name (e.g. special bootstrapped-sites).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;But I may be biased towards adding a policy for this because I miss quite a lot of higher-level policies in various places…&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 23 Jun 2016 08:02:03 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/filtering-activity-types-by-site-or-node/m-p/301853#M254983</guid>
      <dc:creator>afaust</dc:creator>
      <dc:date>2016-06-23T08:02:03Z</dc:date>
    </item>
  </channel>
</rss>

