<?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: Version migration of a running process in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/version-migration-of-a-running-process/m-p/120100#M84651</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;There is an INTERNAL command that you can run at you're own risk which does some minimal compatibility checking of old running activities: org.activiti.engine.impl.cmd.SetProcessDefinitionVersionCmd&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;CODE&gt;&lt;BR /&gt;/**&lt;BR /&gt; * {@link Command} that changes the process definition version of an existing&lt;BR /&gt; * process instance.&lt;BR /&gt; * &lt;BR /&gt; * Warning: This command will NOT perform any migration magic and simply set the&lt;BR /&gt; * process definition version in the database, assuming that the user knows,&lt;BR /&gt; * what he or she is doing.&lt;BR /&gt; * &lt;BR /&gt; * This is only useful for simple migrations. The new process definition MUST&lt;BR /&gt; * have the exact same activity id to make it still run.&lt;BR /&gt; * &lt;BR /&gt; * Furthermore, activities referenced by sub-executions and jobs that belong to&lt;BR /&gt; * the process instance MUST exist in the new process definition version.&lt;BR /&gt; * &lt;BR /&gt; * The command will fail, if there is already a {@link ProcessInstance} or&lt;BR /&gt; * {@link HistoricProcessInstance} using the new process definition version and&lt;BR /&gt; * the same business key as the {@link ProcessInstance} that is to be migrated.&lt;BR /&gt; * &lt;BR /&gt; * If the process instance is not currently waiting but actively running, then&lt;BR /&gt; * this would be a case for optimistic locking, meaning either the version&lt;BR /&gt; * update or the "real work" wins, i.e., this is a race condition.&lt;BR /&gt; * &lt;BR /&gt; * @see &lt;A href="http://forums.activiti.org/en/viewtopic.php?t=2918" rel="nofollow noopener noreferrer"&gt;http://forums.activiti.org/en/viewtopic.php?t=2918&lt;/A&gt;&lt;BR /&gt; * @author Falko Menge&lt;BR /&gt; */&lt;BR /&gt;&lt;/CODE&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 08 May 2013 07:32:09 GMT</pubDate>
    <dc:creator>frederikherema1</dc:creator>
    <dc:date>2013-05-08T07:32:09Z</dc:date>
    <item>
      <title>Version migration of a running process</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/version-migration-of-a-running-process/m-p/120099#M84650</link>
      <description>Hi,I need to migrate a running process instance to a new process definition version.I saw that I can achieve this directly updating the act_ge_bytearray table (bytes_ column) but I don't think this is a safe solution.Is there a right way of doing this thing? (an APi..maybe)Thank you for your help!</description>
      <pubDate>Mon, 06 May 2013 14:15:44 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/version-migration-of-a-running-process/m-p/120099#M84650</guid>
      <dc:creator>dp</dc:creator>
      <dc:date>2013-05-06T14:15:44Z</dc:date>
    </item>
    <item>
      <title>Re: Version migration of a running process</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/version-migration-of-a-running-process/m-p/120100#M84651</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;There is an INTERNAL command that you can run at you're own risk which does some minimal compatibility checking of old running activities: org.activiti.engine.impl.cmd.SetProcessDefinitionVersionCmd&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;CODE&gt;&lt;BR /&gt;/**&lt;BR /&gt; * {@link Command} that changes the process definition version of an existing&lt;BR /&gt; * process instance.&lt;BR /&gt; * &lt;BR /&gt; * Warning: This command will NOT perform any migration magic and simply set the&lt;BR /&gt; * process definition version in the database, assuming that the user knows,&lt;BR /&gt; * what he or she is doing.&lt;BR /&gt; * &lt;BR /&gt; * This is only useful for simple migrations. The new process definition MUST&lt;BR /&gt; * have the exact same activity id to make it still run.&lt;BR /&gt; * &lt;BR /&gt; * Furthermore, activities referenced by sub-executions and jobs that belong to&lt;BR /&gt; * the process instance MUST exist in the new process definition version.&lt;BR /&gt; * &lt;BR /&gt; * The command will fail, if there is already a {@link ProcessInstance} or&lt;BR /&gt; * {@link HistoricProcessInstance} using the new process definition version and&lt;BR /&gt; * the same business key as the {@link ProcessInstance} that is to be migrated.&lt;BR /&gt; * &lt;BR /&gt; * If the process instance is not currently waiting but actively running, then&lt;BR /&gt; * this would be a case for optimistic locking, meaning either the version&lt;BR /&gt; * update or the "real work" wins, i.e., this is a race condition.&lt;BR /&gt; * &lt;BR /&gt; * @see &lt;A href="http://forums.activiti.org/en/viewtopic.php?t=2918" rel="nofollow noopener noreferrer"&gt;http://forums.activiti.org/en/viewtopic.php?t=2918&lt;/A&gt;&lt;BR /&gt; * @author Falko Menge&lt;BR /&gt; */&lt;BR /&gt;&lt;/CODE&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 08 May 2013 07:32:09 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/version-migration-of-a-running-process/m-p/120100#M84651</guid>
      <dc:creator>frederikherema1</dc:creator>
      <dc:date>2013-05-08T07:32:09Z</dc:date>
    </item>
  </channel>
</rss>

