tag:help-archives.hannonhill.com,2010-02-09:/discussions/installation/69-versions-not-created-when-using-workflows-in-672Cascade CMS: Discussion 2012-03-20T19:42:56Ztag:help-archives.hannonhill.com,2010-02-09:Comment/40446222010-11-30T18:52:51Z2010-11-30T18:52:51ZVersions not created when using workflows in 6.7.2<div><p>Hi,</p>
<p>Try using the <a href=
"http://www.hannonhill.com/kb/Workflow-Trigger/available-workflow-triggers/version-trigger.html">
Version Trigger</a> in your Workflows and let me know if that does
the trick.</p>
<p>Thanks</p></div>Timtag:help-archives.hannonhill.com,2010-02-09:Comment/40446222010-11-30T18:59:20Z2010-11-30T19:02:07ZVersions not created when using workflows in 6.7.2<div><p>Here's the current workflow XML. The documentation on the
Version trigger is pretty sparse. Can you let me know where I
should be inserting the call.</p>
<pre>
<code><system-workflow-definition name="Testing - Becker Beta Approval for Production Publish" initial-step="initialize" >
<triggers>
<trigger name="publish" class="com.cms.workflow.function.Publisher" />
<trigger name="merge" class="com.cms.workflow.function.Merge" />
<trigger name="assignToWorkflowOwner" class="com.cms.workflow.function.AssignToWorkflowOwner" />
<trigger name="com.cms.workflow.function.PreserveCurrentUser" class="com.cms.workflow.function.PreserveCurrentUser" />
<trigger name="com.cms.workflow.function.Version" class="com.cms.workflow.function.Version" />
</triggers>
<steps>
<step type="system" identifier="publish-beta" label="Publish Beta" >
<actions>
<action identifier="publish" label="publish" type="auto" move="forward" >
<trigger name="merge" />
<trigger name="publish" >
<parameter>
<name>publish-working-copy</name>
<value>true</value>
</parameter>
<parameter>
<name>destination</name>
<value>/Beta</value>
</parameter>
</trigger>
<trigger name="assignToWorkflowOwner" />
</action>
</actions>
</step>
<step type="transition" identifier="contributor-review" label="Review changes on beta.becker.com" default-user="system-workflow" >
<actions>
<action identifier="contributor-review-approve" label="Publish to production" move="forward" />
<action identifier="contributor-review-make-changes" label="Make additional changes and update beta" next-id="edit-update">
<trigger name="com.cms.workflow.function.PreserveCurrentUser" />
</action>
</actions>
</step>
<step type="system" identifier="publish-live" label="Publish Live" >
<actions>
<action identifier="publish-live" label="Publish Live" type="auto" move="forward" >
<trigger name="merge" />
<trigger name="publish" >
<parameter>
<name>destination</name>
<value>/Production One</value>
</parameter>
</trigger>
<trigger name="publish" >
<parameter>
<name>destination</name>
<value>/Production Two</value>
</parameter>
</trigger>
</action>
</actions>
</step>
<step type="system" identifier="completed" label="Completed" />
</steps>
<non-ordered-steps>
<step type="edit" identifier="edit-update" label="Edit or update content" default-user="system-workflow" >
<actions>
<action identifier="edit" label="edit" next-id="publish-beta">
<trigger name="com.cms.workflow.function.PreserveCurrentUser" />
</action>
</actions>
</step>
</non-ordered-steps>
</system-workflow-definition></code>
</pre></div>jsmithtag:help-archives.hannonhill.com,2010-02-09:Comment/40446222010-11-30T19:06:44Z2010-11-30T19:06:44ZVersions not created when using workflows in 6.7.2<div><p>Sure. If you are looking to get a version when you publish it to
your production instance, try placing it in between your
<em>merge</em> and <em>publish</em> triggers:<br></p>
<pre>
<code> <trigger name="merge" />
<trigger name="com.cms.workflow.function.Version" />
<trigger name="publish" ></code>
</pre>
<p><strong>note:</strong> if you change the
<code><trigger></code> at the top of your workflow from:</p>
<pre>
<code> <trigger name="com.cms.workflow.function.Version" class="com.cms.workflow.function.Version" /></code>
</pre>
<p>to:<br></p>
<pre>
<code> <trigger name="version" class="com.cms.workflow.function.Version" /></code>
</pre>
<p>you can then do something like this:<br></p>
<pre>
<code><trigger name="merge" />
<trigger name="version" />
<trigger name="publish" ></code>
</pre></div>Timtag:help-archives.hannonhill.com,2010-02-09:Comment/40446222010-11-30T21:26:21Z2010-11-30T21:26:21ZVersions not created when using workflows in 6.7.2<div><p>I've updated our workflow as above placing the version trigger
between the merge and publish and a new version is created. The
problem is that now the previous versions content is being wiped
empty and the new version is still being created with the comments
entered on the edit screen. Also, both the current active and the
previous version are being updated with the same modified by user
and date. Should something be passed into the version trigger to
set the comments and to leave the previous version as is?</p></div>jsmithtag:help-archives.hannonhill.com,2010-02-09:Comment/40446222010-12-01T21:27:07Z2010-12-01T21:27:07ZVersions not created when using workflows in 6.7.2<div><p>Hmm, I may have goofed. Can you try swapping those tags so that
the <em>version</em> trigger comes before the <em>merge</em>
trigger:<br></p>
<pre>
<code><trigger name="version" />
<trigger name="merge" />
<trigger name="publish" ></code>
</pre>
<p>Let me know if that changes the behavior.<br></p></div>Timtag:help-archives.hannonhill.com,2010-02-09:Comment/40446222011-02-02T16:34:48Z2011-02-02T16:34:48ZVersions not created when using workflows in 6.7.2<div><p>Sorry for the delay in getting back with you. This fixed the
issue.</p>
<p>This issue can be closed out now.</p>
<p>Thanks,<br>
Jaime</p></div>jsmithtag:help-archives.hannonhill.com,2010-02-09:Comment/40446222011-02-02T16:35:53Z2011-02-02T16:35:53ZVersions not created when using workflows in 6.7.2<div><p>Good deal. Thanks for the update Jamie!</p></div>Tim