<?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: workflow advances variables always undefined in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/workflow-advances-variables-always-undefined/m-p/241074#M194204</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Your workflow transition is probably just defaulting to the first decision, which is the "Yes" one.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;You can try setting the variable again in an "task-end" event before doing the transition and see if the variable persists.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&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;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 14 Apr 2010 02:05:16 GMT</pubDate>
    <dc:creator>hyperation</dc:creator>
    <dc:date>2010-04-14T02:05:16Z</dc:date>
    <item>
      <title>workflow advances variables always undefined</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/workflow-advances-variables-always-undefined/m-p/241073#M194203</link>
      <description>i have this decision in my workflow,&amp;lt;decision name="tiene email"&amp;gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;event type="node-enter"&amp;gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;action class="org.alfresco.repo.workflow.jbpm.AlfrescoJavaScript"&amp;gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;script&amp;gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;variable name="bpm_package" access="read" /&amp;gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;e</description>
      <pubDate>Mon, 12 Apr 2010 16:34:30 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/workflow-advances-variables-always-undefined/m-p/241073#M194203</guid>
      <dc:creator>haroldvera</dc:creator>
      <dc:date>2010-04-12T16:34:30Z</dc:date>
    </item>
    <item>
      <title>Re: workflow advances variables always undefined</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/workflow-advances-variables-always-undefined/m-p/241074#M194204</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Your workflow transition is probably just defaulting to the first decision, which is the "Yes" one.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;You can try setting the variable again in an "task-end" event before doing the transition and see if the variable persists.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&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;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 14 Apr 2010 02:05:16 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/workflow-advances-variables-always-undefined/m-p/241074#M194204</guid>
      <dc:creator>hyperation</dc:creator>
      <dc:date>2010-04-14T02:05:16Z</dc:date>
    </item>
  </channel>
</rss>

