tag:help-archives.hannonhill.com,2010-02-09:/discussions/general/22614-workflow-sending-duplicate-e-mailsCascade CMS: Discussion 2015-09-18T16:05:51Ztag:help-archives.hannonhill.com,2010-02-09:Comment/379654822015-09-18T13:50:40Z2015-09-18T13:50:40ZWorkflow sending duplicate e-mails<div><p>Hi,</p>
<p>When the step immediately following the <a href="http://www.hannonhill.com/kb/Workflow-Trigger/available-workflow-triggers/email-trigger.html">
email trigger</a> is a transition step, the trigger will send an
email to the owner or owning group, which in this case would be the
<strong>draft</strong> step and the owning group is
<strong>Editors</strong>. The duplicate email is more than likely
due to you also specifying a group within the email trigger's
parameters in the <strong>initialize</strong> step.</p>
<p>When you have a moment, try the following adjustment to your
<strong>initialize</strong> step:</p>
<pre>
<code><step type="system" identifier="initialize" label="Create" >
<actions>
<action identifier="draft" label="Draft Notification Email" move="forward" >
<trigger name="com.cms.workflow.function.EmailProvider" />
</action>
</actions>
</step></code>
</pre>
<p>Note: I removed the <code>merge</code> trigger because you don't
want to merge the working copy with the current version until the
very end. Additionally, you want to use a <code>version</code>
trigger to create a new version of the asset after the changes have
been merged. I would recommend adjusting your
<strong>publish</strong> step to the following:</p>
<pre>
<code><step type="system" identifier="publish" label="Publish" >
<actions>
<action identifier="publish" label="Publish" move="forward" >
<trigger name="merge" />
<trigger name="com.cms.workflow.function.Version" />
<trigger name="publish" />
<trigger name="com.cms.workflow.function.EmailProvider" >
<parameter>
<name>mode</name>
<value>completed</value>
</parameter>
<parameter>
<name>recipient-groups</name>
<value>Editors</value>
</parameter>
</trigger>
</action>
</actions>
</step></code>
</pre>
<p>Note: If the <strong>publish</strong> step ends up generating
multiple emails as well, try removing the parameters from that
email trigger.</p>
<p>Please let me know if you have any questions.</p>
<p>Thanks!</p></div>Ryan Griffithtag:help-archives.hannonhill.com,2010-02-09:Comment/379654822015-09-18T15:46:13Z2015-09-18T15:46:13ZWorkflow sending duplicate e-mails<div><p>That seemed to work great. It appears I needed to remove the
parameters on publish as well. Thank you as always for the fast
& excellent response!</p>
<p>Slightly off topic of the main subject, is it possible to add an
action in the Draft step to allow someone to relinquish ownership
and put the ownership back to the group so someone else can assign
the asset to themselves to edit?</p></div>webteamtag:help-archives.hannonhill.com,2010-02-09:Comment/379654822015-09-18T16:03:21Z2015-09-18T16:03:21ZWorkflow sending duplicate e-mails<div><p>Thank you for following up, I am glad to hear that adjustment
resolved the duplicate email issue.</p>
<blockquote>
<p>Slightly off topic of the main subject, is it possible to add an
action in the Draft step to allow someone to relinquish ownership
and put the ownership back to the group so someone else can assign
the asset to themselves to edit?</p>
</blockquote>
<p>At the moment, there is no way to re-assign (or un-assign) the
workflow step, but we do have <a href="http://ideas.hannonhill.com/forums/52559-cascade-cms-ideas/suggestions/784879-allow-for-workflow-steps-to-be-reassigned">
a related suggestion</a> on our Idea Exchange.</p>
<p>I believe your only option would be to have the user go into the
Edit step, don't make a change, and initiate the workflow again so
it goes back into the Draft step.</p>
<p>Please let me know if you have any questions.</p>
<p>Thanks!</p></div>Ryan Griffith