Deadline monotoring buggy ???

[Giesinger Marc]

hi folks=20
 
i have a little question using deadline monitoring on 46C/patch23
we created a helpdesk (customer service) scenarion via workflow within =
two
eskalations using a "selfmade" role resolution function module.
for the escaltion we use the deadline LATEST START and LATEST END.
 
we calculate for each workitem depending on the users location (getting =
the
factory calendar for germany, england, italy, ...) and the priority of =
the
message the escalation date and use this variable as expression in the =
tabs
for start / end.=20
escalation time is between 3 hours and 5 days.
 
everything is working fine (we get correct date / time information and =
the
monitoring is shown on the workitem in the log
when the "first level support" (normaly a couple of users) recieve the
workitem.=20
so i thougt if one of the members from the CS group catches the item =
first,
the monitoring should be over (for latest start) because the latest =
start is
pointing e.g. to 06.12.2001 but the user processed the item 05.12.2001
 
but im worng ... :-( the monitoring is going on and will send on =
06.12.2001
an (first) escalation message to the chief of the CS group saying =
nobody
processed the item !!!=20
so i think the WF system is buggy in this case, because the status of =
the
items changes from ready to started ???????
 
so please: anyone experience with this options and can give me a hint =
????
=20
thanks in advance=20
 
Marc
 
 
 
Mit freundlichen Gr=FC=DFen
 
Marc Giesinger
IT EDI&Workflow
 
Fritz Egger GmbH&CO
Spanplattenwerk
Weiberndorf 20
A-6380 St. Johann in Tirol
 
Tel:        +43/50600-10348
Fax:        +43/50600-90348
e-mail:     mailto:marc.giesinger at egger.com
Internet:   http://www.egger.com