Home → How Do I... →

More Workflow woes

• Edit

T.S.Lindsey

01 Jun, 2010 03:45 PM

Here's what I want to do, and the attached xml looks like id should be doing that:
1. Reassign the workflow to the group if someone leaves a transition step hanging .
2. Place the workflow in an edit step that itself reassigns to group when left hanging.

The goal is prevent workflows from being 'stuck' on a specific user, should that user disappear or neglect to move a transition forward, by escalating the workflow to a system step that assigns ownership back to the group.
Assign to Specified Group trigger doesn't appear to be working, or I'm just doing it wrong. The workflow just keeps the current assigned owner for that step.

Cascade Server 6.2 - r12765

• wf.xml 2.97 KB

1. Support Staff 1 Posted by Tim on 01 Jun, 2010 08:07 PM

   

   Hi Lindsey,

   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 AssignToSpecifiedGroup trigger will not work when re-assigning steps which have already been assigned.

   Please be sure to cast your vote(s) for this related feature!

   Thanks

   • Edit

2. 2 Posted by T.S.Lindsey on 01 Jun, 2010 09:07 PM

   

   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.
   This makes the workflow very clunky, but it's doing what I've intended to do (prevent 'stuck' workflows).

   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.

   • wf2.xml 3.76 KB
   • Edit