<?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 Deployment Design and Management Best Practice Question in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/process-deployment-design-and-management-best-practice-question/m-p/180769#M133899</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi Gavin,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BLOCKQUOTE class="jive-quote"&gt;the upgrade or transfer of currently running processes to an newly deployed flow.&lt;/BLOCKQUOTE&gt;&lt;SPAN&gt;see &lt;/SPAN&gt;&lt;CODE&gt;org.activiti.engine.impl.cmd.SetProcessDefinitionVersionCmd&lt;/CODE&gt;&lt;BR /&gt;&lt;BLOCKQUOTE class="jive-quote"&gt;Are there any suggested approaches or clever flow design patterns that would better handle this situation&lt;/BLOCKQUOTE&gt;&lt;SPAN&gt;There are many possibilities to handle this situation - versioning of services,&amp;nbsp; bounding services with process definitions (jBPM class loader), decoupling services from process definitions… . It really&amp;nbsp; depends on what is the best solution for you.&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>Mon, 04 Aug 2014 09:22:45 GMT</pubDate>
    <dc:creator>martin_grofcik</dc:creator>
    <dc:date>2014-08-04T09:22:45Z</dc:date>
    <item>
      <title>Process Deployment Design and Management Best Practice Question</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/process-deployment-design-and-management-best-practice-question/m-p/180768#M133898</link>
      <description>Hi,I have a implementation of Activiti that has a growing number of bpmn flows that are deployed and used to manage the permit application process for the Government of Puerto Rico.&amp;nbsp; As much as possible the coupling between a flow design and web interaction is minimal however every now and then an e</description>
      <pubDate>Thu, 31 Jul 2014 18:29:00 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/process-deployment-design-and-management-best-practice-question/m-p/180768#M133898</guid>
      <dc:creator>gavnunns</dc:creator>
      <dc:date>2014-07-31T18:29:00Z</dc:date>
    </item>
    <item>
      <title>Re: Process Deployment Design and Management Best Practice Question</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/process-deployment-design-and-management-best-practice-question/m-p/180769#M133899</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi Gavin,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BLOCKQUOTE class="jive-quote"&gt;the upgrade or transfer of currently running processes to an newly deployed flow.&lt;/BLOCKQUOTE&gt;&lt;SPAN&gt;see &lt;/SPAN&gt;&lt;CODE&gt;org.activiti.engine.impl.cmd.SetProcessDefinitionVersionCmd&lt;/CODE&gt;&lt;BR /&gt;&lt;BLOCKQUOTE class="jive-quote"&gt;Are there any suggested approaches or clever flow design patterns that would better handle this situation&lt;/BLOCKQUOTE&gt;&lt;SPAN&gt;There are many possibilities to handle this situation - versioning of services,&amp;nbsp; bounding services with process definitions (jBPM class loader), decoupling services from process definitions… . It really&amp;nbsp; depends on what is the best solution for you.&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>Mon, 04 Aug 2014 09:22:45 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/process-deployment-design-and-management-best-practice-question/m-p/180769#M133899</guid>
      <dc:creator>martin_grofcik</dc:creator>
      <dc:date>2014-08-04T09:22:45Z</dc:date>
    </item>
  </channel>
</rss>

