multiple successor after a nested workflow

Hello,

I made a nested workflow, but the child workflow as two possible end :
- <endtask name="End" /> for a success in operation
- <endtask name="EndFail" /> for a failur in the operation

I define my nested worflow in the parent workflow as this :

<wftask name="NESTEDWFT">
<areavpath v="..." />
<successors>
<successorset description="second task">
<succ v="Second_Task_Author" />
</successorset>
<successorset description="third task">
<succ v="Third_Task_Reviewer" />
</successorset>
</successors>
<wftfile v="mynested.wft"/>
</wftask>

but the problem is that it is always going to the first successor.
How can I pass the "callback value" from the child to the parent? so it is automaticaly use for the successor (like in the external task)

Thank you

Benjamin

Find more posts tagged with

Comments

Migrateduser

I don't see how having 2 endtasks makes any sense. But I've been wrong before. I also don't think the <wftask> task gives you the same options as an externaltask or a cgitask as far as "calling back with an index" to select a particular successor. What you can do is, in your child workflow, assign a particular index to a workflow variable set up in the parent workflow, which relates to the successor index you need to activate upon return to the parent. After the parent's <wftask> have an externaltask whose script checks the value of that workflow variable and continues to the appropriate successor. Make sense?

Dave Smith
Sr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com

Bbeirnaert

thank you, it make sense and I though about this solution before, but I prefered to ask if there was a more "normal" way for doing this thing ...

But if nobody (from interwoven) can find me a better way, I'll go for this one.

Thank you for your help Dave

Benjamin

Migrateduser

Although nested workflow isn't in it's infancy, I do think it's only in its toddler stage, and so there are probably many improvements that could be suggested to make it work better. I think your idea of somehow having a child workflow return some kind of index to select a successor in the <wftask> is a very good idea. This is something I would hope Interwoven would note as a Feature Request (Ugh) and attach both our company names to so that it gets some interest over there.

Dave Smith
Sr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com

Migrateduser

I created a feature request. ID: 40144.
I assigned Nike as a customer name, but did not know the other company to add.

lissa

Bbeirnaert

I'm working for Electrabel (www.electrabel.be), and it is indeed a good feature request to support. You can count on us.

If you need more information from me for this request, I will send them to you lissa.

Benjamin

Skip Function.docx