<?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: Saving variables/data for incomplete user tasks in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/saving-variables-data-for-incomplete-user-tasks/m-p/194593#M147723</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Combine the two solution,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;When the user is submitting the task, break it in two parts, first make a rest call to save the variable and then form data submit to move on to the next task. The next task will validate the data. If data validation service throws the exception, you didn't moved to a next task and current data is being saved.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;In such cases one should always, create a draft copy of the variable, make changes in these and do validation over this only, so that old data can be reloaded at any time.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 18 Jun 2014 14:44:27 GMT</pubDate>
    <dc:creator>ashendra1</dc:creator>
    <dc:date>2014-06-18T14:44:27Z</dc:date>
    <item>
      <title>Saving variables/data for incomplete user tasks</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/saving-variables-data-for-incomplete-user-tasks/m-p/194592#M147722</link>
      <description>Hi,My usecase is following : I have a large form (User Task). I'm expecting the user to fill this form over a period of couple of days. I need the ability to save the local variables for the task even though the task might not be complete. There are two ways of doing this - a) Every time the user fi</description>
      <pubDate>Wed, 18 Jun 2014 11:24:24 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/saving-variables-data-for-incomplete-user-tasks/m-p/194592#M147722</guid>
      <dc:creator>texens</dc:creator>
      <dc:date>2014-06-18T11:24:24Z</dc:date>
    </item>
    <item>
      <title>Re: Saving variables/data for incomplete user tasks</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/saving-variables-data-for-incomplete-user-tasks/m-p/194593#M147723</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Combine the two solution,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;When the user is submitting the task, break it in two parts, first make a rest call to save the variable and then form data submit to move on to the next task. The next task will validate the data. If data validation service throws the exception, you didn't moved to a next task and current data is being saved.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;In such cases one should always, create a draft copy of the variable, make changes in these and do validation over this only, so that old data can be reloaded at any time.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 18 Jun 2014 14:44:27 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/saving-variables-data-for-incomplete-user-tasks/m-p/194593#M147723</guid>
      <dc:creator>ashendra1</dc:creator>
      <dc:date>2014-06-18T14:44:27Z</dc:date>
    </item>
  </channel>
</rss>

