Variable deadlines...

[Michael Pokraka]

Hi Richard,
I like the theory, but one thing bothers... A minor requirement is that stats are quite important , which would be skewed if I understand this correctly - each task would be take at most one day, correct?
 
Thanks for the useful input,
Cheers
Mike
 
 
On Wed, Apr 02, 2003 at 12:41:50PM -0600, Richard Marut wrote:
> Michael,
>
> I'm ready to do the same thing where I have deadlines of 3, 5 and 8 days
> for the same task. My solution and design is:
>
> 1. Create a table that defines the deadlines. This is to allow additions
> if needed in the future.
> 2. Set the deadline at the task to 1 day.
> 3. Create a new method that reads the deadline table and determines if
> the actual deadline is reached.
> 4. Put the new deadline determination method/task after the task with
> the deadline.
>
> I'm going to manage this by using a container element that I increment
> each time the deadline is reached. If I find a match between the
> deadline element and one of the deadline table entries, then I do my
> escalation of notifying the appropriate person(s) otherwise I loop back
> to the task with the deadline.
>
> Richard...
>
>
> -----Original Message-----
>> From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of
> Michael Pokraka
> Sent: Wednesday, April 02, 2003 11:11 AM
> To: SAP-WUG at MITVMA.MIT.EDU
> Subject: Variable deadlines...
>
> Greetings all,
> I have a design issue with not-so-nice solutions and wonder if anyone
> may have better alternatives:
>
> Scenario: Many tasks, all call same method.
> Depending on an object attribute, different deadlines are to apply to
> each step (We have a 'deadline matrix' of flow type and task).
>
> Thus a 'Normal' obj will have 3 days, 2 days and 5 days for the first 3
> tasks.
> A 'Partial' obj will have shorter deadlines (2,1 and 3 days) and so on,
> a 'Rush' shorter again (not quite accurate - in reality we have 15
> different types).
>
> Since the methods are all the same, I would need to pass a parameter,
> thus requiring a seperate step before each task, calling a
> 'GetDeadlineForTask' method of sorts. At 30-odd steps, this becomes both
> annoying and ugly. Does anyone have an idea on how to accomplish this
> with an attribute? I could of course create 30 deadline virtual
> attributes but even that is not really all that nice either....
>
> Any ideas welcome...
> Cheers
> Mike