Re: OSWorkflow - initial actionforsteps?

I don't agree with this, making it so that the first match is what's 
done seems an arbitrary solution, and is bound to confuse a lot of 
people....'I set my action to auto and I'm sure its condition passes, 
but it doesn't get called..help!'

On Friday, May 9, 2003, at 03:44 AM, Hubert Felber wrote:

>
> <I don't understand how "auto=yes" would cause actions to be invoked?
> Would
> <they just happen once the step that has that action is entered in the
> <workflow? What if there are two actions with auto=yes?
>
> Just some thoughts:
>
> Actions with "auto=yes" are are called every time a transition to that
> step is made. It's the programmers responsability to use restrictions
> that control execution of "auto" actions.
>
> <What happens if two conditions evaluate to true? Do you have a split?
>
> Same as for conditional-results, only the first "auto" action with
> restrictions that are fullfilled, is executed. Splits always must be
> defined in results.
>
> Does that make sense?
>
> Hubert
>
>
>
>>>> "Pat Lightbody" <[email protected]> 05/09/03 03:24am >>>
>
>> <but does it make sense to "auto"-call more than one action?
>>
>> You could have auto actions with different conditions.
>>
>> Hubert
>
> What happens if two conditions evaluate to true? Do you have a split?
>
> -Pat
>
>
>
> -------------------------------------------------------
> 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