Re: [OSWF] Associating additional information to the Steps

You are correct.

Travis had wanted to see a new transientVars key called "step", but Hani and
I decided that adding it to the WorkflowContext would make more sense, which
is still planned before the 2.5 released. Keep an eye out for it.

-Pat

----- Original Message -----
From: "Aníbal Rojas" <[email protected]>
To: <[email protected]>
Sent: Friday, April 25, 2003 1:22 PM
Subject: [Opensymphony-developers] [OSWF] Associating additional information
to the Steps


> Hi,
>
>     Using OSWorkflow 2.5.0 from CVS, I need to associate _persistent_
> information to steps. I saw a previous dicussion ( Due Date feature )
where
> Hani suggested to use the PropertySet inside a function to accomplish this
> kind of behavior.
>
>     My question is, Do I know from wich Step (or Steps) I am coming from
in
> the Function, or the Steps where I am "going to"? I think I need this In
> order to associate the Step with the Information.
>
>     The infomation I need to add is similar to the discussed in the "Due
> Date" Thread, is a Comment or Justification, for the Action. Of course we
> are trying to avoid the grow of the signature of methods adding this
> "message" parameter and reworking the whole AbstractWorkflow.
>
>     Regards,
>
> Aníbal Rojas
> [email protected]
> 58+212+242.66.62 / 43.79
> Fax: 58+212+243.68.09
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Opensymphony-developers mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/opensymphony-developers



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf