<?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: Migrating to Activiti BPMN in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/migrating-to-activiti-bpmn/m-p/196558#M149688</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;In case when it is not possible to map legacy data to the ACT_HI_* tables you can:&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;1. Keep data in legacy system and get history from the legacy system before it is archived.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;2. Extend act tables to support your needs.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&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>Wed, 26 Nov 2014 07:13:35 GMT</pubDate>
    <dc:creator>martin_grofcik</dc:creator>
    <dc:date>2014-11-26T07:13:35Z</dc:date>
    <item>
      <title>Migrating to Activiti BPMN</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/migrating-to-activiti-bpmn/m-p/196556#M149686</link>
      <description>Hello,&amp;nbsp; we are implementing new system using Activiti and there is a requirement, to migrate all historic data from the old system. What would be the best way to perform migration? &amp;nbsp; For example, there is a Activiti bpmn process to issue some kind of licence. When the process is executed, I can coll</description>
      <pubDate>Tue, 25 Nov 2014 09:35:55 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/migrating-to-activiti-bpmn/m-p/196556#M149686</guid>
      <dc:creator>justass</dc:creator>
      <dc:date>2014-11-25T09:35:55Z</dc:date>
    </item>
    <item>
      <title>Re: Migrating to Activiti BPMN</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/migrating-to-activiti-bpmn/m-p/196557#M149687</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Assuming you can map all historic data from the old system to activiti, I don´t think stuffing act_hi_* tables with all that data is too bad, since it´s a one-time task after all. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;One thing that you can do in order to easily find old instances is to use a different process version for them. Just deploy your new process twice, and use the first&amp;nbsp; process id that you can use as a basis to populate historic tables.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 26 Nov 2014 01:12:11 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/migrating-to-activiti-bpmn/m-p/196557#M149687</guid>
      <dc:creator>pmsevestre</dc:creator>
      <dc:date>2014-11-26T01:12:11Z</dc:date>
    </item>
    <item>
      <title>Re: Migrating to Activiti BPMN</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/migrating-to-activiti-bpmn/m-p/196558#M149688</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;In case when it is not possible to map legacy data to the ACT_HI_* tables you can:&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;1. Keep data in legacy system and get history from the legacy system before it is archived.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;2. Extend act tables to support your needs.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&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>Wed, 26 Nov 2014 07:13:35 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/migrating-to-activiti-bpmn/m-p/196558#M149688</guid>
      <dc:creator>martin_grofcik</dc:creator>
      <dc:date>2014-11-26T07:13:35Z</dc:date>
    </item>
  </channel>
</rss>

