<?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: Deployment-IDs &amp; undeploy in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/deployment-ids-undeploy/m-p/193397#M146527</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Ideally deployment Id is exclusive to every process definition when you deploy it from activiti explorer but if you run a JUnit test to deploy the process definitions, it might allow you use to same deployment Id. This unique deployment id goes to ACT_RE_DEPLOYMENT table and ACT_RE_PROCDEF table which stores the process definition information has a link for this deployment Id. I think that's how undeploy logic works because it has reference of associated process definitions in ACT_RE_PROCDEF table. When you start the process from process definition, process instance info goes to ACT_RU_EXECUTION table (not ACT_RE_PROCDEF) and associated task entries goes to ACT_RE_TASK table.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 17 Jul 2014 16:28:11 GMT</pubDate>
    <dc:creator>sahusunil</dc:creator>
    <dc:date>2014-07-17T16:28:11Z</dc:date>
    <item>
      <title>Deployment-IDs &amp; undeploy</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/deployment-ids-undeploy/m-p/193395#M146525</link>
      <description>Hello,currently we are searching for a way to undeploy a process Definition and remove all references. The DeploymentManager along with the RepositoryManager seems to be a good point to start.- First get all deployed Processes of a certain key.- Then get the deployment id based on the actual process</description>
      <pubDate>Wed, 16 Jul 2014 11:13:59 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/deployment-ids-undeploy/m-p/193395#M146525</guid>
      <dc:creator>dognose</dc:creator>
      <dc:date>2014-07-16T11:13:59Z</dc:date>
    </item>
    <item>
      <title>Re: Deployment-IDs &amp; undeploy</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/deployment-ids-undeploy/m-p/193396#M146526</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;There is one deployment and a new record will be created in the ACT_RE_DEPLOYMENT table and every time u start a process a new process instance will be created and those records are in the ACT_RE_PROCDEF. There is good explanation in the user-guide. &amp;lt;link&amp;gt; &lt;/SPAN&gt;&lt;A href="http://www.activiti.org/userguide/#N165AD" rel="nofollow noopener noreferrer"&gt;http://www.activiti.org/userguide/#N165AD&lt;/A&gt;&lt;SPAN&gt; &amp;lt;/link&amp;gt;&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 16 Jul 2014 14:43:09 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/deployment-ids-undeploy/m-p/193396#M146526</guid>
      <dc:creator>sathish1</dc:creator>
      <dc:date>2014-07-16T14:43:09Z</dc:date>
    </item>
    <item>
      <title>Re: Deployment-IDs &amp; undeploy</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/deployment-ids-undeploy/m-p/193397#M146527</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Ideally deployment Id is exclusive to every process definition when you deploy it from activiti explorer but if you run a JUnit test to deploy the process definitions, it might allow you use to same deployment Id. This unique deployment id goes to ACT_RE_DEPLOYMENT table and ACT_RE_PROCDEF table which stores the process definition information has a link for this deployment Id. I think that's how undeploy logic works because it has reference of associated process definitions in ACT_RE_PROCDEF table. When you start the process from process definition, process instance info goes to ACT_RU_EXECUTION table (not ACT_RE_PROCDEF) and associated task entries goes to ACT_RE_TASK table.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 17 Jul 2014 16:28:11 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/deployment-ids-undeploy/m-p/193397#M146527</guid>
      <dc:creator>sahusunil</dc:creator>
      <dc:date>2014-07-17T16:28:11Z</dc:date>
    </item>
  </channel>
</rss>

