<?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: Activiti Engine compliance option in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/activiti-engine-compliance-option/m-p/154047#M108565</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;That's requires a lot of effort to implement: eg. modules used to generate BPMN are added as dependencies, which would force us to include multiple versions in the tool. So no, there is no change this will be implemented…&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 07 Nov 2013 10:14:05 GMT</pubDate>
    <dc:creator>frederikherema1</dc:creator>
    <dc:date>2013-11-07T10:14:05Z</dc:date>
    <item>
      <title>Activiti Engine compliance option</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/activiti-engine-compliance-option/m-p/154046#M108564</link>
      <description>Hello Activiti Designer developers,We meet the following problem especially when a new Activiti Engine is released: in the development environment we could and usually will allow ourselves to use all the features of the&amp;nbsp; most recent Activiti Engine. At the same time, though, environment we need to p</description>
      <pubDate>Mon, 04 Nov 2013 09:29:42 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/activiti-engine-compliance-option/m-p/154046#M108564</guid>
      <dc:creator>mmaker1234</dc:creator>
      <dc:date>2013-11-04T09:29:42Z</dc:date>
    </item>
    <item>
      <title>Re: Activiti Engine compliance option</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/activiti-engine-compliance-option/m-p/154047#M108565</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;That's requires a lot of effort to implement: eg. modules used to generate BPMN are added as dependencies, which would force us to include multiple versions in the tool. So no, there is no change this will be implemented…&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 07 Nov 2013 10:14:05 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/activiti-engine-compliance-option/m-p/154047#M108565</guid>
      <dc:creator>frederikherema1</dc:creator>
      <dc:date>2013-11-07T10:14:05Z</dc:date>
    </item>
    <item>
      <title>Re: Activiti Engine compliance option</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/activiti-engine-compliance-option/m-p/154048#M108566</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hello Frederik,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I meant not to switch the entire editor to a previous version, but to limit the available/displayed process design features to the proper set for a selected Activiti Engine version (usually you add design elements and features with each new version of the engine).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I understand that even this is also a lot of effort, though &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt; This was just an idea as I suppose that other developers meet the same problem.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 07 Nov 2013 12:55:51 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/activiti-engine-compliance-option/m-p/154048#M108566</guid>
      <dc:creator>mmaker1234</dc:creator>
      <dc:date>2013-11-07T12:55:51Z</dc:date>
    </item>
  </channel>
</rss>

