<P>Jihoon & Jocelyn, <BR><BR>That was a very good explanation to DM and I just wanted to add a possible trick you could use DM for that I used @ a client who was using a lnumerous steps in a loop to do this.<BR> If you have a WI that sits in a user's inbox & you would like to remind them a few times to go there, you could do that w/o leaving the task & leave the WI in the inbox. Set up the LATEST START, REQUESTED END & LATESTED END @ intervals of say 5, 10 & 15 days. At the end of each DM send out an email to the user to remind them. On the last LATESTED END DM, the WI can then be rerouted to someone else w/an email explaining to either, the original user where it went, or to the new dept. of why it's coming to them & how long it sat in the user's inbox. The only limitation is that you cannot have more than 3 reminders.</P>
<P>Jeffrey A. Rappaport Business Workflow, LLC Email: <A href="mailto:BusinessWorkflow@Consultant.com">BusinessWorkflow@Consultant.com</A> Web: <A href="http://www.Business-Workflow.com">www.Business-Workflow.com</A></P>
<P> </P>
<P><BR>-----Original Message----- <BR>From: "Dart, Jocelyn" <JOCELYN.DART@SAP.COM><BR>Date: Tue, 15 May 2001 12:44:16 +0200 <BR>To: SAP-WUG@MITVMA.MIT.EDU <BR>Subject: Re: The exact meaning of each deadline. <BR><BR><BR>> Hi Jihoon, <BR>> Ok yes you do have it a little confused. <BR>> <BR>> All deadlines need a period after which the deadline is activated, e.g. 2 <BR>> days, <BR>> and a time from which the deadline is measured, i.e. if your <BR>> deadline is 2 days, 2 days after WHAT? <BR>> <BR>> Normally workitem creation is fine. <BR>> E.g. 2 days after WORKITEM CREATION, means the agent has 2 days from the <BR>> time <BR>> it hits their inbox to do something about it. <BR>> <BR>> Using workflow creation time or some other date/time expression is less <BR>> usual. <BR>> An example using workflow creation: <BR>> Workflow starts with event "Form created". Workitem must be actioned <BR>> within <BR>> 2 days of form being created. <BR>> An example usin
g a date/time expression: <BR>> Customer has requested order to be delivered on a certain date. <BR>> Workitem must be actioned within 2 days of nominated delivery date. <BR>> <BR>> You've worked out when the deadlines work ok, but it might be helpful to <BR>> look at this way: <BR>> <BR>> REQUESTED START <BR>> This one's a little different from the other deadlines in that it's about <BR>> slowing things <BR>> down rather than speeding them up. <BR>> Don't show the workitem to the agent BEFORE this time. E.g. orders are <BR>> created throughout the day, but customers sometimes ring back shortly <BR>> afterwards <BR>> to change them, we want to give the customers are grace period to make <BR>> changes. <BR>> So don't process the order further until requested start time. <BR>> <BR>> LATEST START <BR>> This is a "hard" start. You MUST have started the workitem by this time or <BR>> we will <BR>> get very cross with you/beat you up/issue pink slip. <B
R>> <BR>> REQUESTED END <BR>> This is a "soft" end. We would LIKE you to have done it by requested end <BR>> time, <BR>> but there are no harsh penalties. <BR>> <BR>> LATEST END <BR>> This is a "hard" end. You MUST have completed the workitem by this time or <BR>> we will <BR>> get very cross with you/beat you up/issue pink slip. <BR>> <BR>> As a real life example of using more than one deadline on the same workitem: <BR>> <BR>> Approval workitem is created. <BR>> <BR>> REQUESTED END is set at WORKITEM CREATION DATE + 2 DAYS - at requested end <BR>> we issue <BR>> an escalation notice to the initiator to chase up the approver. <BR>> <BR>> LATEST END is set at WORKITEM CREATION DATE + 5 DAYS - at latest end we use <BR>> modeled <BR>> deadlining to kill the current workitem, and send a new workitem to their <BR>> boss <BR>> so that the boss can approve it and is also informed that the normal <BR>> approver has <BR>> failed to act. <BR
>> <BR>> I actually implemented something very similar to this in numerous workflows <BR>> at one of <BR>> my customers. <BR>> <BR>> Regards, <BR>> Jocelyn Dart <BR>> Consultant (BBP, Ecommerce, Internet Transaction Server, Workflow) <BR>> SAP Australia <BR>> Email jocelyn.dart@sap.com <?xml:namespace prefix = mailto /><mailto:jocelyn.dart@sap.com><BR>> Tel: +61 412 390 267 <BR>> Fax: +61 2 9935 4880 <BR>> <BR>> <BR>> -----Original Message----- <BR>> From: hoonkim0@naver.com [mailto:hoonkim0@naver.com] <BR>> Sent: Monday, 14 May 2001 6:45 PM <BR>> To: SAP-WUG@MITVMA.MIT.EDU <BR>> Subject: The exact meaning of each deadline. <BR>> <BR>> <BR>> Hi, experts. <BR>> <BR>> Is there anybody can explain the exact meaning and usage exmaple of <BR>> deadlines? <BR>> <BR>> The training material BC601 said <BR>> <BR>> Requested start ; <BR>> Earliest possible time for processing start; Introduced by the <BR>> system: <BR>> The
work item is not visible in the Business Workplace until this <BR>> time. <BR>> Requested end ; <BR>> Latest requested time for completion of processing of a workflow <BR>> Latest start ; <BR>> Latest deadline for workflow processing start <BR>> Latest end ; <BR>> Latest deadline for completion of processing of a workflow <BR>> <BR>> It's very confusing for me to understand the meaning and the usage of each <BR>> deadline. <BR>> <BR>> My understanding is .... <BR>> <BR>> requested start means <BR>> deadline for the interval between the appearing time of the workitem <BR>> in agent's inbox and the workitem creation time. <BR>> <BR>> requested end means <BR>> deadline for the inverval between the completion time and the workitem <BR>> creation time. <BR>> <BR>> latest start means <BR>> deadline for the interval between the workitem creation time and the <BR>> workflow instance start time. <BR>> <BR>> latest end means <BR>> deadline
for the interval between the workitem completion time and the <BR>> workflow instance start time. <BR>> <BR>> My confusing is .... <BR>> <BR>> Each deadline has two options for referencing time. They are workflow <BR>> creation and workitem creation. <BR>> I guess "requested end for referencing the workflow creation time" is same <BR>> as "latest end". <BR>> And, "latest end for referencing the workitem creation time" is same as <BR>> "requested end". Right? <BR>> What does the referencing time (workitem/workflow creation time) stands for? <BR>> <BR>> It's very confusing for me. Please let me understand. <BR>> <BR>> Any information will be very appreciated. <BR>> <BR>> Thank you and best regards, <BR>> Jihoon Kim <BR>> </mailto:jocelyn.dart@sap.com></P>
--
<BR>_______________________________________________
<BR>Make PC-to-Phone calls with Net2Phone.
<BR>Sign-up today at: <A HREF="http://www.net2phone.com/cgi-bin/link.cgi?121" TARGET="_new"><FONT COLOR="BLUE">http://www.net2phone.com/cgi-bin/link.cgi?121</FONT></A>
<BR>
<BR>
<BR>
<BR>