Deadlines and forwarding....

Michael Pokraka workflow at quirky.me.uk
Mon May 19 08:22:16 EDT 2003


Hi,
Thanks for the input - we had tried something like this before. The problem with it was that _WI_actual_agent is blank until the agent executes it. This would make reminders ineffective if they don't touch it.
 
Though I'm still not sure if this solves it either: _WI_actual_agent is Joe. After two days, Joe forwards it to Mary. Mary doesn't do anything about it and Joe still keeps getting the reminders - because the modeled deadline was already in process by the time Joe forwarded the item.
 
Thanks
Mike
 
On Mon, May 19, 2003 at 02:12:15PM +0200, ???? ????? wrote:
> Hi mike
> You can take the container -> task and config that the _WI_actual_agent will go to a container element (wfsyst->agent)
> And send the modeled deadline to this container
>
>
> Best Regards
> Sharon Zinger
> Sap Basis & WorkFlow Developer
> McCann|Kesher-Barel
> *  Sharonz at McCann-kb.co.il
> (  :      +972 3 6938160
> Fax :      +972 3 6958230
> Mobile : +972 57 212118
>
>
>
>
> -----Original Message-----
>> From: Michael Pokraka [mailto:workflow at quirky.me.uk]
> Sent: Monday, May 19, 2003 11:36 AM
> To: SAP-WUG at MITVMA.MIT.EDU
> Subject: Deadlines and forwarding....
>
>
> Hi all,
> Here's an interesting one:
>
> An agent is determine and put into a container element. Task is sent out to this agent with a modelled deadline. The modelled deadline sends reminders, but if the agents forwards the item (s)he still gets the reminder.
>
> The obvious solution is to put the whole thing into a loop, but this is not an option (I think) because duration statistics are important. Thus if we were to e.g. put a one day deadline on the task and have it loop, then the longest any task would take is one day. Aside from that, forwarding still needs to be taken into account so that it doesn't loop back to the original agent.
>
> Any ideas welcome,
> Cheers
> Mike
 


More information about the SAP-WUG mailing list