<?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: Content Status aspect and Simple workflow in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/content-status-aspect-and-simple-workflow/m-p/202582#M155712</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;If you starting a workflow, based on a space, you obtained the current space id via navigator. Store this as variable into the processinstance. When you approve the worklfow(or reject) you have the already set variable in place.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Outcomes of transition being taked are available on task-leave events. After that, over workflowservice can those tasks retrieved and checked for this value(e.g. outcome="approved"). But if you have 2 tasks, the second task does not remember which decision being taked (if you have no delegation right there). Therefore you should store the outcome into the processinstance, using TaskController or via processdefinition "write, read" variables. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Once being set, you obtain the property via javascript as this is a normal property being transmitted to the next task(must be set on the second task as "readable").&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 16 Feb 2009 09:47:14 GMT</pubDate>
    <dc:creator>cheffilet</dc:creator>
    <dc:date>2009-02-16T09:47:14Z</dc:date>
    <item>
      <title>Content Status aspect and Simple workflow</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/content-status-aspect-and-simple-workflow/m-p/202581#M155711</link>
      <description>Hey guys! I need some assistance…I have simple workflows enabled on different spaces with Accept/Reject scenario that moves the contents to their respective spaces. So in my scenario, there is only one 'Rejected' space that accepts contents from various other spaces when 'Reject button' is clicked.</description>
      <pubDate>Fri, 13 Feb 2009 11:26:02 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/content-status-aspect-and-simple-workflow/m-p/202581#M155711</guid>
      <dc:creator>sbsrulz</dc:creator>
      <dc:date>2009-02-13T11:26:02Z</dc:date>
    </item>
    <item>
      <title>Re: Content Status aspect and Simple workflow</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/content-status-aspect-and-simple-workflow/m-p/202582#M155712</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;If you starting a workflow, based on a space, you obtained the current space id via navigator. Store this as variable into the processinstance. When you approve the worklfow(or reject) you have the already set variable in place.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Outcomes of transition being taked are available on task-leave events. After that, over workflowservice can those tasks retrieved and checked for this value(e.g. outcome="approved"). But if you have 2 tasks, the second task does not remember which decision being taked (if you have no delegation right there). Therefore you should store the outcome into the processinstance, using TaskController or via processdefinition "write, read" variables. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Once being set, you obtain the property via javascript as this is a normal property being transmitted to the next task(must be set on the second task as "readable").&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 16 Feb 2009 09:47:14 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/content-status-aspect-and-simple-workflow/m-p/202582#M155712</guid>
      <dc:creator>cheffilet</dc:creator>
      <dc:date>2009-02-16T09:47:14Z</dc:date>
    </item>
  </channel>
</rss>

