tag:help-archives.hannonhill.com,2010-02-09:/discussions/how-do-i/37-more-workflow-woesCascade CMS: Discussion 2011-04-07T22:11:53Ztag:help-archives.hannonhill.com,2010-02-09:Comment/18254792010-06-01T20:07:10Z2010-06-01T20:07:10ZMore Workflow woes<div><p>Hi Lindsey,</p>
<p>I took a look at your workflow and I can see what you are
attempting to do. Unfortunately, there is no good way to re-assign
workflows in this manner since the <em>AssignToSpecifiedGroup</em>
trigger will not work when re-assigning steps which have already
been assigned.</p>
<p>Please be sure to cast your vote(s) for <a href=
"http://ideas.hannonhill.com/forums/52559-cascade-ideas/suggestions/784879-allow-for-workflow-steps-to-be-reassigned?ref=title">
this related feature</a>!</p>
<p>Thanks</p></div>Timtag:help-archives.hannonhill.com,2010-02-09:Comment/18254792010-06-01T21:07:51Z2010-06-01T21:48:23ZMore Workflow woes<div><p>I've found a bit of a workaround by escalating to
Initialization, which seems to make AssignToSpecifiedGroup work,
then explicitly call the ATSG trigger at every action.<br>
This makes the workflow very clunky, but it's doing what I've
intended to do (prevent 'stuck' workflows).</p>
<p>I have no idea why this works while anything else does not.
Between this and the above comment, this issue seems resolved as
well as it's going to be.</p></div>T.S.Lindsey