<?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 How to pospone a task in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/how-to-pospone-a-task/m-p/148125#M103395</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I'd like to design a subprocess for following real-world scenario: &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;1. As a user I claim a human task which includes calling the client.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;2. Client asks to be called later, e.g. at 5 PM.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;3. I postpone the task till 5 PM to call the client again and unclaim it.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;4. I claim another task from the queue and complete it.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;5. Later I have no more active tasks, so I want to see all postponed tasks with their follow-up dates and eventually complete some of them.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;6. At 5 PM the postponed task from step 1-3 is on the top of my queue again (if not resolved yet) and I claim it.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;7. I call the client and either resolve the task or postpone it again.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Is it possible to implement such scenario in Activiti BPMN and Java?&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;We're querying tasks using TaskService in Java and not using Activiti Explorer.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 17 Jun 2013 13:07:13 GMT</pubDate>
    <dc:creator>3on</dc:creator>
    <dc:date>2013-06-17T13:07:13Z</dc:date>
    <item>
      <title>How to pospone a task</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/how-to-pospone-a-task/m-p/148125#M103395</link>
      <description>Hi,I'd like to design a subprocess for following real-world scenario: 1. As a user I claim a human task which includes calling the client.2. Client asks to be called later, e.g. at 5 PM.3. I postpone the task till 5 PM to call the client again and unclaim it.4. I claim another task from the queue an</description>
      <pubDate>Mon, 17 Jun 2013 13:07:13 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/how-to-pospone-a-task/m-p/148125#M103395</guid>
      <dc:creator>3on</dc:creator>
      <dc:date>2013-06-17T13:07:13Z</dc:date>
    </item>
    <item>
      <title>Re: How to pospone a task</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/how-to-pospone-a-task/m-p/148126#M103396</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;You can leverage the due-date of a task. This can be set declaratively in the BPMN but also updated from our API. When the user want's to postpone the task, the due date is altered.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;In order to remove the task from the "task list", you can either unassign the task (and involve the original assignee in the task using your custom identity-link type "postponer". Another option is to have a special variable on the task, which indicates it's postponed or not. In you're&amp;nbsp; task-list API-call you do, you can include a taskVariableValueEquals(…) to only include non-postponed tasks, for example. You can also leverage the "dueBefore()" or "dueAfter()" on the TaskQuery to filter what tasks pop up in a user's inbox.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 18 Jun 2013 07:22:46 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/how-to-pospone-a-task/m-p/148126#M103396</guid>
      <dc:creator>frederikherema1</dc:creator>
      <dc:date>2013-06-18T07:22:46Z</dc:date>
    </item>
  </channel>
</rss>

