Re: Nested Workflows....

This sounds like a good implementation for a rule engine. There has been
talk of adding a level above the normal Workflow interface that can help
with automating calls to the doAction() method based upon certain conditions
(such as rule evaluating to true). I'm hoping to address this stuff in 3.0.

-Pat

> Order Workflow:
> There are several step involved completing an order
> workflow..
>
> >From within the context of an order workflow there are
> 1 to N (unknown) elements of an order that must
> complete its own workflow.
> once all elements are completed the top level (order
> workflow) can continue.
> I do not know of any nested workflow tags from the
> DTD, nor any Loop logic.
>
> Currently i am implementing a class that i use as a
> condition to check if all elements associated to an
> order have completed their workflow, before allowing
> the wf to move to the next step.
>
> It seems that this would be a common pattern in a
> workflow and wondered if others had come up with a
> more elegant solution.  Or if 'nested' workflows or
> loops should be built into the workflow descriptor.
>
> Thoughts?
>
> Thanks,
> TJ
>
> __________________________________
> Do you Yahoo!?
> The New Yahoo! Search - Faster. Easier. Bingo.
> http://search.yahoo.com
>
>
> -------------------------------------------------------
> Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
> The only event dedicated to issues related to Linux enterprise solutions
> www.enterpriselinuxforum.com
>
> _______________________________________________
> Opensymphony-developers mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/opensymphony-developers



-------------------------------------------------------
Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
The only event dedicated to issues related to Linux enterprise solutions
www.enterpriselinuxforum.com