Factory Calendar Deadline - Multipe User Decisions

[Michael Pokraka]

Hi Cristina,
I've pondered the same situation at length and came to the same conclusion that seperate virtual attributes which return a deadline object is the way to go.
 
This kinda goes against the grain for development principles, but in the workflow at least it's neater (and easier to understand) to have a deadline  OBJ.MARKETINGDEADLINE.DAYS/HOURS, and definitely better performance than having a method with parameters to get the appropriate deadline, or instantiating a bunch of seperate deadline objects which live in the container.
 
HTH
Cheers
Mike
 
 
 
On Thu, Oct 09, 2003 at 10:16:07AM +1000, Cristiana D'Agosto wrote:
> G'day all,
>
> we are in 4.6c
>
> I am building a workflow that has several User Decision steps and each of
> the User Decision has a different requirement for deadline (e.g. 5 working
> days, 3 working days, etc).
>
> We have created the object type ZDEADLINE and The Book describes 2 ways of
> using the Deadine Object in the workflow.
>
> In my scenario, it would mean that I would need to instantiate ZDEADLINE
> as many times as the number of User Decisions, in the prior workflow step
> of the User Decision, is that correct?
>
> Would it work if I created a virtual attribute in my main object (in that
> case FIPP) and use the attribute ? Would I need to create one virtual
> attribute per User Decision as well?
>
> Any suggestions?
>
> Many thanks and regards
>
> Cristiana