Administrator comments to workflow log

[Martin Aldrich]

Hi All,
 
 
 
My approach is not to build too much tracking into the workflow itself -
if any update can be done in the application document this is preferable
to trying to build it into the workflow. In principle it means that you
will have a underlying business object to update. Manual steps relevant
to active workflows should fire a terminating event which should also be
recognized by the workflow in order to cancel/complete the workflow/step
in an orderly fashion. At one of my clients, workflow has gotten a bad
name precisely because of the tendency of workflows to be somewhat
isolated from the actual application document - manual changes to
documents are not picked up by the workflow and the workflows do not
build on existing functional strengths.
 
Regards,
 
Martin
 
-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Scheinoha, John
Sent: Monday, October 30, 2006 11:55 PM
To: SAP Workflow Users' Group
Subject: RE: Administrator comments to workflow log
 
   Another way of documenting workflow logs that are "Logically Deleted"
is to create an Excel sheet listing the date, Time , work item deleted,
document affected 
(ex: Debit/Credit Memo) person who created the workflow document, why
the work item was logically deleted.  I have used this approach for the
last few years. our Debit/Credit application process is to withdraw the
memo, then cancel the memo via the "Withdraw" work item.  Some of our
users do not want to execute the "Withdraw" work item.  Instead they
delete the memo directly via VA02 which creates an error in the workflow
log.
 
Hopes this helps,
   John
 
________________________________

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Alon Raskin
Sent: Monday, October 30, 2006 2:18 PM
To: SAP Workflow Users' Group
Subject: RE: Administrator comments to workflow log
Why not create a text attachment to the work item before forwarding or
completing it?
 
Alon 
 
 
________________________________

From: sap-wug-bounces at mit.edu on behalf of Zavier, Johnson
Sent: Mon 10/30/2006 15:09
To: sap-wug at mit.edu
Subject: Administrator comments to workflow log
All,
 As a workflow administrator, if I am taking some manual action to a
workflow task(eg: Manual forward, Manual complete etc), is there any way
I can document  the details why I took this action for later reference
or audit purpose?. I am looking for a way to attach e-mail, or write
details and attach to the workflow item so that I can go back in future
and show the auditing?.

Thanks in advance for your response.

Johnson Zavier
SAP ABAP/Workflow


------------------------------------------------------------------------
This e-mail contains confidential information.  If you are not the
intended recipient or have received this e-mail in error, please notify
the sender immediately and destroy this e-mail.  Any unauthorized
copying, disclosure or distribution of the e-mail or the information it
contains, is strictly forbidden.

_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20061031/e5496ef9/attachment.htm