Help with workflow deadlines

[Dart, Jocelyn]

Hi Sherman,
In your modeled deadline path, put the "send internet mail" step plus an
"add 3 days" container operation on your notification time within a
loop until.   Loop until the workflow container contains a valid
approve/reject value
or maximum notification time is reached.
This approve/reject value would be filled by the release requisition
workitem.
There is no need to loop back to the release requisition step as workflow
container elements
are available to all steps in the workflow.
Regards,
Jocelyn.
 
-----Original Message-----
From: Sherman S. Wright [mailto:swright at lsil.com]
Sent: Friday, 27 April 2001 11:05 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Help with workflow deadlines
 
 
Hi again -
 
So what suggestions do you have for making the loop work for the requested
end?
If we just put a requested end on the Release Requisition for WI created + 3
days, and then have a "Send Internet Mail" step, with a requested start of
WI
created + 3 days, that will just send the notice out 6 days after the
original
work item is created.  If we put in a "loop until" where do we loop back to?
The Release Requisition step?
 
Thanks for all your suggestions!  Please keep them coming!
 
Regards,
Sherman
 
 
"Dart, Jocelyn" wrote:
 
> Hi Sherman,
> As a variation on David and Peter's suggestions how about:
>
> 1) Using a modeled deadline on REQUESTED END after workitem + 3 days to
loop
> through
>    the send mail notification with requested start of workitem + 3 days.
> You could perhaps loop until a valid
>    approve/reject value has been returned to the workflow container.
>
> 2) Using a modeled deadline on LATEST END after workitem + 45 days to kill
> the original workitem (thereby triggering
>    the processing obsolete event) and set the status to rejected after
> processing obsolete. Setting the status to
>    rejected would then terminated the requested end loop.
>
> This is similar to Peter's approach but has the advantage of not starting
> the loop at all
> unless the agent fails the first deadline, resulting in less workitems
being
> created if the
> agent reacts in a timely manner in the first place.
>
> Regards,
>         Jocelyn Dart
> Consultant (BBP, Ecommerce, Internet Transaction Server, Workflow)
> SAP Australia
> Email jocelyn.dart at sap.com <mailto:jocelyn.dart at sap.com>
> Tel: +61 412 390 267
> Fax: +61 2 9935 4880
>
> -----Original Message-----
>> From: Roehlen, Peter [mailto:PRoehlen at powercor.com.au]
> Sent: Wednesday, 11 April 2001 3:39 PM
> To: SAP-WUG at MITVMA.MIT.EDU
> Subject: Re: Help with workflow deadlines
>
> Hi Sherman,
>
> You could create a fork with two parrallel branches (with one branch
> required to finish.)  In one branch you put your approval step with the
> deadline monitoring set to the 45 days maximum after which the workitem is
> cancelled.  In the other branch, you have a send mail step in a loop.  You
> need to create a date and time container that you initialise before and
> inside the loop to the current system date/time.  Then in your send mail
> step you have the requested start set to your container values + 3 days.
>
> Every three days the send mail step will be processed until the workitem
in
> the other branch is completed (which will terminate the fork).
>
> Hope this is of value.
>
> Cheers
>
> Peter Roehlen
> Team Lead - SAP Technical & Development
> Powercor Australia Ltd
> (03) 5430 4704 / 0409 950 263
>
> -----Original Message-----
>> From: Sherman S. Wright [mailto:swright at lsil.com]
> Sent: Wednesday, 11 April 2001 7:59
> To: SAP-WUG at MITVMA.MIT.EDU
> Subject: Help with workflow deadlines
>
> Hi -
>
> We have a workflow for approval of Purchase Requisition lines, that
> currently is set to send a deadline notification after 72 hours.  What
> we'd like to do is have it send a notification every 3 days (3, 6, 9,
> 12, 15, 18, 21, 24, 27, 30, 33, 36, 39, and 42 days) to someone who is
> not processing a work item.  Then we'd like the item automatically
> rejected if there is no activity (work item not completed) at 45 days.
> Anyone have any idea how we could accomplish both of these?  Any help
> would be greatly appreciated, since I'm trying to get this done in
> development by April 20...
>
> Regards,
> Sherman
> **********************************************************************
> Powercor Australia Ltd. This email and any file attachments are
> confidential and intended solely for the use of the individual or
> entity to whom they are addressed. If you have received this email in
> error please tell us immediately by return email and delete the
> document.
> **********************************************************************