How do you funnel all transitions through 1 submittask?

Tbag

Hi,

Sorry for the n00b question, but here's what I'm trying to do: imagine a UserTask that can transition to group tasks "A" or "B". I want to submit all the files attached the job in between that transition. The 'dumb' way would be to have my UserTask transition to 2 separate submittasks (i.e. "Submit_Then_A" and "Submit_Then_B") which transition to A and B, respectively.

Graphically, before:

             /---> A
UserTask ---
             \---> B

Graphically, after (non-optimal):

             /---> Submit_Then_A --> A
UserTask ---
             \---> Submit_Then_B --> B

What I'd like to do is be able to do is have a single submit task with a variable success transition, something like this:

                              /---> A
UserTask --> SubmitTask---
                              \---> B

I assume you'd accomplish this with code like so:

    <submittask....>
        ...
        <success>
            <succ v="__INSERT__('$either_A_or_B')" />
        </success>
    </submittask>

But I'm not seeing how to "tie in" to the button click on the UserTask. How do I know what transition step the user clicks on and where/how can I manipulate the $either_A_or_B variable?

Tbag

I just sorta thought of a way to do this that is more work than I'd like to do, but I suppose from the UserTask, I could call an ExternalTask named "VariableSubmitTaskSetterUpper.ipl" or something, and have that ipl manipulate the successorset values in the SubmitTask.

Or, just do the submit itself and transition to some next task based off some %transition_map hash.

I'd prefer not to do that, because I like the concept of keeping the workflow transition logic encapsulated within the one *.wft file . . .I think it makes the workflow easier to map out, understand, and maintain.

Anyone have any ideas as to my original post? It's been 7 minutes and no responses. . . .where are fish, dave and nipper? Slacking off, as usual ;-)