<?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 dynamic number of user tasks with accept/reject features in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/dynamic-number-of-user-tasks-with-accept-reject-features/m-p/163264#M117071</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;We have a workflow requirement in which we have dynamic number of Roles(approvers) based on client location where we deploy this app,&amp;nbsp; so we defined a User Task as a multi-instance so that we can run a loop for number of approvers(configured at deployment time).&amp;nbsp; Lets say for a given workflow we dynamically defined 4 levels of approvals(serially) in the order below&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Role_1 –&amp;gt; Role_2 –&amp;gt; Role_3 –&amp;gt; Role_4&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;So our multi-instance task will run a for-loop 4 times, I have some questions below&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Q1) If any one approver(other than Role_1) Rejects then control should go back to previous Approver for data correction and re-approval and continue further in&amp;nbsp; same sequence defined above. Does multi-instance task supports this functionality ??. If not then what are the workarounds ??&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Q2) If any user under Role_2 is working on task and he is also a member of Role_3 then we want Activiti to skip the Role_3 and and jump to Role_4. And if he is&amp;nbsp; also a member of Role_4 then that should be skipped too. Is that doable using multi-instance tasks and/or using some workarounds.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 16 Sep 2013 14:50:40 GMT</pubDate>
    <dc:creator>chimu</dc:creator>
    <dc:date>2013-09-16T14:50:40Z</dc:date>
    <item>
      <title>dynamic number of user tasks with accept/reject features</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/dynamic-number-of-user-tasks-with-accept-reject-features/m-p/163264#M117071</link>
      <description>We have a workflow requirement in which we have dynamic number of Roles(approvers) based on client location where we deploy this app,&amp;nbsp; so we defined a User Task as a multi-instance so that we can run a loop for number of approvers(configured at deployment time).&amp;nbsp; Lets say for a given workflow we dyn</description>
      <pubDate>Mon, 16 Sep 2013 14:50:40 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/dynamic-number-of-user-tasks-with-accept-reject-features/m-p/163264#M117071</guid>
      <dc:creator>chimu</dc:creator>
      <dc:date>2013-09-16T14:50:40Z</dc:date>
    </item>
    <item>
      <title>Re: dynamic number of user tasks with accept/reject features</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/dynamic-number-of-user-tasks-with-accept-reject-features/m-p/163265#M117072</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Multi instance is really nothing more than a for-each loop. So no you won't get this functionality out-of-the-box. From your description I think it would be better to have a user task and based on some conditions loop back to this user task. Then you are building your own multi instance task and you can control the logic yourself using a Java service task or a script task.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Best regards,&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 17 Sep 2013 10:49:53 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/dynamic-number-of-user-tasks-with-accept-reject-features/m-p/163265#M117072</guid>
      <dc:creator>trademak</dc:creator>
      <dc:date>2013-09-17T10:49:53Z</dc:date>
    </item>
  </channel>
</rss>

