<?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: Process Instance Migration (JBPM 3.0-&amp;gt;Activiti 5.10) in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/process-instance-migration-jbpm-3-0-gt-activiti-5-10/m-p/112275#M78977</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I think because our use of the workflow framework under JPDL was so nieve, that the value of the information stored there is basically that there is a state (i.e. we make no use of the history, or even the path the objects has taken in the workflow). So it looks like my job will be to run our existing objects through the new workflow up to their current state (loosing the historical information – which was unused anyway).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;It's not a wonderful situation, but i think it's better then what we had. I guess i was just hoping i could forceably push an object to a given point in the workflow without going through any of the initial steps.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;If you have any suggestions as to why this (running the objects through the process artificially) would be a terrible idea it would be greatly appreciated.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 20 Nov 2012 14:21:52 GMT</pubDate>
    <dc:creator>izaak</dc:creator>
    <dc:date>2012-11-20T14:21:52Z</dc:date>
    <item>
      <title>Process Instance Migration (JBPM 3.0-&gt;Activiti 5.10)</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/process-instance-migration-jbpm-3-0-gt-activiti-5-10/m-p/112273#M78975</link>
      <description>Like many others we wrote our bpm in jpdl 3, and are looking to update to one of the more current frameworks. Our business processes tend to never end, migrating peice meal isn't a great option for us (i.e. leaving the old things on the old jbpm, and doing all new work in activiti). I've looked arou</description>
      <pubDate>Fri, 16 Nov 2012 20:12:21 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/process-instance-migration-jbpm-3-0-gt-activiti-5-10/m-p/112273#M78975</guid>
      <dc:creator>izaak</dc:creator>
      <dc:date>2012-11-16T20:12:21Z</dc:date>
    </item>
    <item>
      <title>Re: Process Instance Migration (JBPM 3.0-&gt;Activiti 5.10)</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/process-instance-migration-jbpm-3-0-gt-activiti-5-10/m-p/112274#M78976</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;We've tried to do it in the past, but we quickly understood it was a hell of a job to get right.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;The process xml is one which could be automised until a certain level … but the real pain is in the data.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;If you'd really want to do it, you will need to move the data using SQL itself. That is the only way to make sure that the process instance is in a certain state. That stuff won't be able through the API.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 19 Nov 2012 10:35:39 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/process-instance-migration-jbpm-3-0-gt-activiti-5-10/m-p/112274#M78976</guid>
      <dc:creator>jbarrez</dc:creator>
      <dc:date>2012-11-19T10:35:39Z</dc:date>
    </item>
    <item>
      <title>Re: Process Instance Migration (JBPM 3.0-&gt;Activiti 5.10)</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/process-instance-migration-jbpm-3-0-gt-activiti-5-10/m-p/112275#M78977</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I think because our use of the workflow framework under JPDL was so nieve, that the value of the information stored there is basically that there is a state (i.e. we make no use of the history, or even the path the objects has taken in the workflow). So it looks like my job will be to run our existing objects through the new workflow up to their current state (loosing the historical information – which was unused anyway).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;It's not a wonderful situation, but i think it's better then what we had. I guess i was just hoping i could forceably push an object to a given point in the workflow without going through any of the initial steps.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;If you have any suggestions as to why this (running the objects through the process artificially) would be a terrible idea it would be greatly appreciated.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 20 Nov 2012 14:21:52 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/process-instance-migration-jbpm-3-0-gt-activiti-5-10/m-p/112275#M78977</guid>
      <dc:creator>izaak</dc:creator>
      <dc:date>2012-11-20T14:21:52Z</dc:date>
    </item>
    <item>
      <title>Re: Process Instance Migration (JBPM 3.0-&gt;Activiti 5.10)</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/process-instance-migration-jbpm-3-0-gt-activiti-5-10/m-p/112276#M78978</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I think it makes sense if you can somehow automise it (depends on how many you have of course). Not needing the history is of course a big plus!&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 21 Nov 2012 07:56:49 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/process-instance-migration-jbpm-3-0-gt-activiti-5-10/m-p/112276#M78978</guid>
      <dc:creator>jbarrez</dc:creator>
      <dc:date>2012-11-21T07:56:49Z</dc:date>
    </item>
  </channel>
</rss>

