Audit trail from background tasks

[Tom Peou]

Hi Richard,

WF-BATCH runs the background step that removes the billing block (all
background steps are run by WF-BATCH) - unfortunately, you cannot set a
dialog user to run Workflow background methods/tasks.
However, you can record the user that "Approves" the credit memo through the
"Decision" step by doing the following:
- On the binding from the decision task to the workflow, you should have an
element called _Workitem.
- Pass this to a container of business object type "WORKINGWI".
- Under B.O WORKINGWI you have the attributes: ExecutedByUser which contains
UserID (of the person that executed the last work item).

Or... You can always make a copy of the method that removes the billing
block. Make it a dialog step for a dialog user to execute in a task, thus
forcing it to be a foreground task requiring a user to execute and being
able to record their user ID. The main problem - this now becomes a two-step
process... Not very elegant.

Hope that helps.

Tom


 ------------------------------
*From:* sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] *On Behalf
Of *Smart, Richard
*Sent:* 17. august 2006 21:24
*To:* SAP Workflow Users' Group
*Subject:* Audit trail from background tasks
Hello,

>  We have a workflow for credit memo approval which is similar to the
> standard one. When the user approves the credit memo, using a decision step,
> a background step runs which removes the billing block. As expected, on
> looking at the change docs, it says that the block was removed by wf-batch.
> We can look in the wf logs to determine who really carried out the approval,
> but I'd like to know whether there's a way of forcing the block to be
> removed by the users user id.. if you see what I mean. I'm sure this is a
> common query but I couldn't find anything in the archives. I'm interested in
> knowing how you people have got round this.
>
>
>
> Thanks a lot
>
> Richard
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20060818/974ef68f/attachment.htm