RSWUWFML - forwarded workitems not selected

[Soady, Phil]

Wouldn't be the first time I saw a customized version of RSWUWFML.
Check the logic in the code around the TIME calculation very carefully.
Now imagine what happens to the exact second... if a workitem was created
in the same second that the report claims to checked until.
 
ie READ UPTO 02:20:31 but the physically the system had just clicked to over
to 02:20:31  the second 31 is 1 second long. In this second  a new workitem could be
created.  On top of that, the system needs some physical time after building the
SWWWIHEAD  record with the timestamp, to physically create it.
 
ie the record with the time 02:20:31 my not physically be visible to
other processes for some seconds later due to the physical write commit work.
 
I made new version to actually work on a slight delay.
This also allows for the Workitems that may be processed immediately online,
or be terminated quickly by some event to be killed before sending them out.
 
So add you issue with the creation time of the record and other time points
ie when forwarded, you have room for improvement.
The logic gets tricky if the original person should NOT receive a new mail
telling them about the item they just forwarded !!!
 
Your problem I see as a weakness and not a bug. But you may care to argue otherwise.
regards
Phil.
 
Phil Soady
Senior Consultant
Business Technologies
SAP Australia
* : 0412 213 079
* : phil.soady at sap.com
 
 
 
 
 
-----Original Message-----
From: Robin Sahasranam [mailto:Rsahasranam at worldbank.org]
Sent: Saturday, May 24, 2003 12:00 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: RSWUWFML - forwarded workitems not selected
 
 
Greetings,
 
I have been testing the report RSWUWFML which sends emails to users when they have new workitems in their Inbox. One limitation I have run into is that if a user forwards a workitem to another user and the workitem was created prior to the job's latest run, then the item is not selected for the
email alert. The report apparently uses the creation timestamp of the workitem from SWWWIHEAD, which does not change when a workitem is forwarded. When a workitem is forwarded to a user, it is a "new" workitem for the user, regardless of when it was originally created. Not including forwarded
workitems in our email alerts would be seen as a serious shortcoming by our users.
 
As far as I know, the information on forwarded workitems is available in SWWLOGHIST. One way for us to include the forwarded items would be to modify the report and select from SWWLOGHIST using METHOD, METH_EDATE METH_ETIME. Unless we build a new index on these fields it will take too long to run.
 
Has any of you faced this issue and did you find a way to include forwarded workitems? Would love to hear your suggestions. Thanks in advance.
 
Robin Sahasranam
World Bank