<?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 Share-config for a mayor update of a workflow in Alfresco Forum</title>
    <link>https://connect.hyland.com/t5/alfresco-forum/share-config-for-a-mayor-update-of-a-workflow/m-p/61199#M21387</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have Alfresco&lt;STRONG&gt; AOI 5.2&lt;/STRONG&gt; (sdk 3). I deployed a new version of a workflow (activiti 5.19) with new features and paths. Older version of my workflow instance (in fly) keeps the old WF (thats ok) but the menus/forms they are using are from last and new version of share-config-custom... with controls (buttons) to paths that do not exists in the old version.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So when my users click on buttons they got a non I18n error msg &lt;img id="smileysad" class="emoticon emoticon-smileysad" src="https://connect.hyland.com/i/smilies/16x16_smiley-sad.png" alt="Smiley Sad" title="Smiley Sad" /&gt; I want people with old WF not to see the menus/forms made for the new WF verion. How can I achieve that?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If this is not possible, another option could be to customize the error msg. I found out the error msg is a gatewayActivitiException and it doesn't have a stacktraceprint in catalina. The msg is hardcoded in that class, i didn't found a properties file.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks a lot in advance for your help &lt;img id="smileyhappy" class="emoticon emoticon-smileyhappy" src="https://connect.hyland.com/i/smilies/16x16_smiley-happy.png" alt="Smiley Happy" title="Smiley Happy" /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 09 Mar 2018 09:31:10 GMT</pubDate>
    <dc:creator>aht</dc:creator>
    <dc:date>2018-03-09T09:31:10Z</dc:date>
    <item>
      <title>Share-config for a mayor update of a workflow</title>
      <link>https://connect.hyland.com/t5/alfresco-forum/share-config-for-a-mayor-update-of-a-workflow/m-p/61199#M21387</link>
      <description>I have Alfresco AOI 5.2 (sdk 3). I deployed a new version of a workflow (activiti 5.19) with new features and paths. Older version of my workflow instance (in fly) keeps the old WF (thats ok) but the menus/forms they are using are from last and new version of share-config-custom... with controls (bu</description>
      <pubDate>Fri, 09 Mar 2018 09:31:10 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-forum/share-config-for-a-mayor-update-of-a-workflow/m-p/61199#M21387</guid>
      <dc:creator>aht</dc:creator>
      <dc:date>2018-03-09T09:31:10Z</dc:date>
    </item>
    <item>
      <title>Re: Share-config for a mayor update of a workflow</title>
      <link>https://connect.hyland.com/t5/alfresco-forum/share-config-for-a-mayor-update-of-a-workflow/m-p/61200#M21388</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;In order to support distinct forms for distinct versions of your workflow, you have to use distinct workflow start / task types so you can actually differentiate between those different versions. There is no "workflow version" distinction in Alfresco Share by default, so you cannot simply configure it via share-config-custom.xml unless you are already using distinct task types.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 11 Mar 2018 10:19:06 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-forum/share-config-for-a-mayor-update-of-a-workflow/m-p/61200#M21388</guid>
      <dc:creator>afaust</dc:creator>
      <dc:date>2018-03-11T10:19:06Z</dc:date>
    </item>
  </channel>
</rss>

