<?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: Modeling multiple user tasks in Activti in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/modeling-multiple-user-tasks-in-activti/m-p/87684#M59431</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;One option will be this.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Configure a user task "Await QA".&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;In the form of this task, user can specify one of the three actions of "Persist To GIS" etc,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;and save that action as a process variable.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Configure an exclusive gateway with conditions specified by the above variable,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;and it will go to "Await GIS Update Result" etc, based on this condition.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 01 May 2012 04:35:46 GMT</pubDate>
    <dc:creator>steve1</dc:creator>
    <dc:date>2012-05-01T04:35:46Z</dc:date>
    <item>
      <title>Modeling multiple user tasks in Activti</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/modeling-multiple-user-tasks-in-activti/m-p/87683#M59430</link>
      <description>Hello We are trying to migrate from JBPM 3.2 to Activiti, having a trouble finding equivalent functionality of "task-node" in Activiti. This is how it used to work in the old world :&amp;lt;task-node name="Await QA"&amp;gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;lt;task name="Persist To GIS"&amp;gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;lt;assignment pooled-actors="QA" /&amp;amp;</description>
      <pubDate>Mon, 30 Apr 2012 23:14:18 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/modeling-multiple-user-tasks-in-activti/m-p/87683#M59430</guid>
      <dc:creator>bhaskar1</dc:creator>
      <dc:date>2012-04-30T23:14:18Z</dc:date>
    </item>
    <item>
      <title>Re: Modeling multiple user tasks in Activti</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/modeling-multiple-user-tasks-in-activti/m-p/87684#M59431</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;One option will be this.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Configure a user task "Await QA".&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;In the form of this task, user can specify one of the three actions of "Persist To GIS" etc,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;and save that action as a process variable.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Configure an exclusive gateway with conditions specified by the above variable,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;and it will go to "Await GIS Update Result" etc, based on this condition.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 01 May 2012 04:35:46 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/modeling-multiple-user-tasks-in-activti/m-p/87684#M59431</guid>
      <dc:creator>steve1</dc:creator>
      <dc:date>2012-05-01T04:35:46Z</dc:date>
    </item>
    <item>
      <title>Re: Modeling multiple user tasks in Activti</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/modeling-multiple-user-tasks-in-activti/m-p/87685#M59432</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;what about an embedded subprocess?&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 01 May 2012 13:10:10 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/modeling-multiple-user-tasks-in-activti/m-p/87685#M59432</guid>
      <dc:creator>ronald_van_kuij</dc:creator>
      <dc:date>2012-05-01T13:10:10Z</dc:date>
    </item>
  </channel>
</rss>

