<?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: Activiti History Customization Enhancement in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/activiti-history-customization-enhancement/m-p/238952#M192082</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi Sakumar,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;What I would propose:&lt;/SPAN&gt;&lt;BR /&gt;&lt;UL&gt;&lt;LI&gt;do not rely on the current HistoryManagement implementation&lt;/LI&gt;&lt;LI&gt;implement new one based on the event infrastructure &lt;A href="http://activiti.org/userguide/index.html#eventDispatcher" rel="nofollow noopener noreferrer"&gt;http://activiti.org/userguide/index.html#eventDispatcher&lt;/A&gt; and make the implementation pluggable.&lt;/LI&gt;&lt;LI&gt;outputs could be compatible with the current history service (same tables in the DB, the same queries…., backward compatible)&lt;/LI&gt;&lt;/UL&gt;&lt;SPAN&gt;Regards&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Martin&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 29 Jan 2016 08:10:25 GMT</pubDate>
    <dc:creator>martin_grofcik</dc:creator>
    <dc:date>2016-01-29T08:10:25Z</dc:date>
    <item>
      <title>Activiti History Customization Enhancement</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/activiti-history-customization-enhancement/m-p/238951#M192081</link>
      <description>Hi,We have multiple Workflow defined to perform difference Business Processing Activiti. However We want to track History for only Specific Set Activiti.Current Activiti provides Enabling and Disabling History at Global Level. This Results in a Lot of Insertion on History Tables, which in turn impac</description>
      <pubDate>Thu, 28 Jan 2016 17:47:01 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/activiti-history-customization-enhancement/m-p/238951#M192081</guid>
      <dc:creator>sakumar1</dc:creator>
      <dc:date>2016-01-28T17:47:01Z</dc:date>
    </item>
    <item>
      <title>Re: Activiti History Customization Enhancement</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/activiti-history-customization-enhancement/m-p/238952#M192082</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi Sakumar,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;What I would propose:&lt;/SPAN&gt;&lt;BR /&gt;&lt;UL&gt;&lt;LI&gt;do not rely on the current HistoryManagement implementation&lt;/LI&gt;&lt;LI&gt;implement new one based on the event infrastructure &lt;A href="http://activiti.org/userguide/index.html#eventDispatcher" rel="nofollow noopener noreferrer"&gt;http://activiti.org/userguide/index.html#eventDispatcher&lt;/A&gt; and make the implementation pluggable.&lt;/LI&gt;&lt;LI&gt;outputs could be compatible with the current history service (same tables in the DB, the same queries…., backward compatible)&lt;/LI&gt;&lt;/UL&gt;&lt;SPAN&gt;Regards&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Martin&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 29 Jan 2016 08:10:25 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/activiti-history-customization-enhancement/m-p/238952#M192082</guid>
      <dc:creator>martin_grofcik</dc:creator>
      <dc:date>2016-01-29T08:10:25Z</dc:date>
    </item>
  </channel>
</rss>

