<?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: claim, setAssignee and taskAssignee in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/claim-setassignee-and-taskassignee/m-p/112103#M78872</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;CODE&gt;&lt;BR /&gt;It's a simple principle IMHO. All operations you perform on the task-service (e.g.. setAssignee and claim) are persisted immediately. &lt;BR /&gt;&lt;BR /&gt;Everything you do on the Task object, should be applied by saving that object, using saveTask().&lt;BR /&gt;&lt;/CODE&gt;&lt;BR /&gt;&lt;SPAN&gt;Sure, but logically why is there no claim|complete etc on task then ? This is the confusing bit, the fact that some operations are present on both sides but they work differently and some operations are only available on the task service. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;From a technical point of view i know of course why they are this way, but it's just slightly confusing as this post demonstrates.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 11 Oct 2012 13:25:09 GMT</pubDate>
    <dc:creator>heymjo</dc:creator>
    <dc:date>2012-10-11T13:25:09Z</dc:date>
    <item>
      <title>claim, setAssignee and taskAssignee</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/claim-setassignee-and-taskassignee/m-p/112099#M78868</link>
      <description>HelloI try to make my own experience with the APIs &lt;IMG id="smileyhappy" class="emoticon emoticon-smileyhappy" src="https://migration33.stage.lithium.com/i/smilies/16x16_smiley-happy.png" alt="Smiley Happy" title="Smiley Happy" /&gt;If I do // case 1Task myTask = lstCandidateTask.get(0);myTask.setAssignee(myUser);List&amp;lt;Task&amp;gt; lstTask = taskServ.createTaskQuery().taskAssignee(myUser).list();‍‍‍‍‍‍lstTask is emptyBut if I do // case 2Task myTask = lstCandidateTask.get(0);ta</description>
      <pubDate>Thu, 11 Oct 2012 08:23:35 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/claim-setassignee-and-taskassignee/m-p/112099#M78868</guid>
      <dc:creator>chantme</dc:creator>
      <dc:date>2012-10-11T08:23:35Z</dc:date>
    </item>
    <item>
      <title>Re: claim, setAssignee and taskAssignee</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/claim-setassignee-and-taskassignee/m-p/112100#M78869</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;CODE&gt;&lt;BR /&gt;Task myTask = lstCandidateTask.get(0);&lt;BR /&gt;myTask.setAssignee(myUser);&lt;BR /&gt;taskServ.saveTask(myTask);&lt;BR /&gt;List&amp;lt;Task&amp;gt; lstTask = taskServ.createTaskQuery().taskAssignee(myUser).list();&lt;BR /&gt;&lt;/CODE&gt;&lt;BR /&gt;&lt;SPAN&gt;i agree it is not very intuitive.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 11 Oct 2012 10:31:31 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/claim-setassignee-and-taskassignee/m-p/112100#M78869</guid>
      <dc:creator>heymjo</dc:creator>
      <dc:date>2012-10-11T10:31:31Z</dc:date>
    </item>
    <item>
      <title>Re: claim, setAssignee and taskAssignee</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/claim-setassignee-and-taskassignee/m-p/112101#M78870</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Yes indeed&amp;nbsp; !!&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thank you Jorg !&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 11 Oct 2012 12:32:47 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/claim-setassignee-and-taskassignee/m-p/112101#M78870</guid>
      <dc:creator>chantme</dc:creator>
      <dc:date>2012-10-11T12:32:47Z</dc:date>
    </item>
    <item>
      <title>Re: claim, setAssignee and taskAssignee</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/claim-setassignee-and-taskassignee/m-p/112102#M78871</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;It's a simple principle IMHO. All operations you perform on the task-service (e.g.. setAssignee and claim) are persisted immediately. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Everything you do on the Task object, should be applied by saving that object, using saveTask().&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 11 Oct 2012 12:40:23 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/claim-setassignee-and-taskassignee/m-p/112102#M78871</guid>
      <dc:creator>frederikherema1</dc:creator>
      <dc:date>2012-10-11T12:40:23Z</dc:date>
    </item>
    <item>
      <title>Re: claim, setAssignee and taskAssignee</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/claim-setassignee-and-taskassignee/m-p/112103#M78872</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;CODE&gt;&lt;BR /&gt;It's a simple principle IMHO. All operations you perform on the task-service (e.g.. setAssignee and claim) are persisted immediately. &lt;BR /&gt;&lt;BR /&gt;Everything you do on the Task object, should be applied by saving that object, using saveTask().&lt;BR /&gt;&lt;/CODE&gt;&lt;BR /&gt;&lt;SPAN&gt;Sure, but logically why is there no claim|complete etc on task then ? This is the confusing bit, the fact that some operations are present on both sides but they work differently and some operations are only available on the task service. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;From a technical point of view i know of course why they are this way, but it's just slightly confusing as this post demonstrates.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 11 Oct 2012 13:25:09 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/claim-setassignee-and-taskassignee/m-p/112103#M78872</guid>
      <dc:creator>heymjo</dc:creator>
      <dc:date>2012-10-11T13:25:09Z</dc:date>
    </item>
    <item>
      <title>Re: claim, setAssignee and taskAssignee</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/claim-setassignee-and-taskassignee/m-p/112104#M78873</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Setting the assignee is the claim… However, this does not alter the state of a task, nor a process. Completing does, so it won't make sense to make this available in the POJO, since it impacts more than meets the eye.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 11 Oct 2012 14:17:30 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/claim-setassignee-and-taskassignee/m-p/112104#M78873</guid>
      <dc:creator>frederikherema1</dc:creator>
      <dc:date>2012-10-11T14:17:30Z</dc:date>
    </item>
  </channel>
</rss>

