Deadline Monitoring - Multiple Occurences

[Sample, Rick]

This was working before and now is not? No changes to template?
 
If I understand correctly, sounds like you have a Sync task in a loop.
On this task is a branch with step to send an e-mail. 
With Sync tasks, every time you process it, it completes and if in loop,
creates a NEW task. i.e. NEW task ID, NEW deadline data, etc.  
 
What I would do, is switch to Async Task with 'terminating events' and
take it out of a loop. Do something in task, then your process will
raise event, catch it, terminate task. 
 
Do an approve, reject, or whatever and watch your event log to get an
idea of what to hang your hat on. 
 
Psst, the good news though, sounds like you DL monitoring is working
correctly. LOL
 
Rick Sample | Office (314) 573-5822 | Mobile (314) 952-2273 |
rick.sample at graybar.com 
www.graybar.com <http://www.graybar.com/>  - Graybar Works to Your
Advantage 
 

________________________________

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Dale Brown
Sent: Monday, May 11, 2009 12:02 PM
To: sap-wug at mit.edu
Subject: Deadline Monitoring - Multiple Occurences



 

We are on ECC 6.0 . 

We have a workflow that was created over 3 years ago that does FIPP
processing. We have deadline monitoring on the work item that allows the
user to approve / reject the parked document. We have on this task
(inbox work item), branches that lead to other tasks in the workflow.
Besides the approve, and the reject branch, we have a terminate release
branch that will re-circulate the work item back to the inbox agent.
When the user did the terminate release (green arrow back), the deadline
monitoring seemed to take this last touch date and then continue with
the deadline routine until the user either approves or rejects. Still
would only get one cycle deadline routine (email) at the latest touch
time. 

Now we are experiencing, besides the original deadline routine which
sends our email, any time a user goes into the work item and terminates
release, it starts a new deadline cycle, without ending the original
cycle, so it is now sending two emails, one from the original deadline
date and time, and another from the terminate release date and time. And
if the person went in a day later and did terminate release again, a
third deadline (email) cycle begins. 

Any ideas of the behavior change ? Just want the one deadline cycle
regardless of how many times a user may go in and out of the task
without approving or rejecting the FIPP document. 

We are using the requested end date tab using "expression"  fields from
attributes date and time of a  business object deadline that calls
function module END_TIME_DETERMINE using the unit 'DAY'.  

 

 

 

Dale R. Brown

Duke University

OIT Application and Database Services

919.684.5341

 

Because I care about you, I trust you will take the time to visit these
links: 

http://www.thisisthegeneration.com/page.cfm?id=140

http://www.somewhereforever.com/ 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20090511/0e7b2086/attachment.htm