<?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: Aspects in workflow in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/aspects-in-workflow/m-p/300720#M253850</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hello,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I am sorry, but this is actually not possible as you already presumed. The data model for workflows is a one-time declarative definition of the workflow / task data and cannot be enhanced with dynamic aspects (as nodes can be). You CAN add any arbitrary property to the data of a workflow / task, but that will not be exposed to the outside world (i.e. forms) unless it has been defined via the type or a mandatory aspect. This is due to the fact that Alfresco services use the type and mandatory aspects to look up "expected" data and don't process any other data they "don't know of".&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Regards&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Axel&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 10 Sep 2014 10:19:33 GMT</pubDate>
    <dc:creator>afaust</dc:creator>
    <dc:date>2014-09-10T10:19:33Z</dc:date>
    <item>
      <title>Aspects in workflow</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/aspects-in-workflow/m-p/300719#M253849</link>
      <description>Hi All,I was just wondering if it is possible to have non mandatory aspects in Activiti workflow so that the workflow properties can grow depending on previous properties that are set along the flow. From what I have read I don't think this is possible as all the examples I have seen online seem to</description>
      <pubDate>Wed, 10 Sep 2014 09:42:27 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/aspects-in-workflow/m-p/300719#M253849</guid>
      <dc:creator>buje85</dc:creator>
      <dc:date>2014-09-10T09:42:27Z</dc:date>
    </item>
    <item>
      <title>Re: Aspects in workflow</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/aspects-in-workflow/m-p/300720#M253850</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hello,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I am sorry, but this is actually not possible as you already presumed. The data model for workflows is a one-time declarative definition of the workflow / task data and cannot be enhanced with dynamic aspects (as nodes can be). You CAN add any arbitrary property to the data of a workflow / task, but that will not be exposed to the outside world (i.e. forms) unless it has been defined via the type or a mandatory aspect. This is due to the fact that Alfresco services use the type and mandatory aspects to look up "expected" data and don't process any other data they "don't know of".&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Regards&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Axel&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 10 Sep 2014 10:19:33 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/aspects-in-workflow/m-p/300720#M253850</guid>
      <dc:creator>afaust</dc:creator>
      <dc:date>2014-09-10T10:19:33Z</dc:date>
    </item>
  </channel>
</rss>

