Brain fart on background tasks

[Claude Bourque]

Mike,
 
Thanks. I'll check that out. For now, if I put a 1 minute wait under Requested Start for the first task, it switches all subsequent workitems to WF-BATCH.
 
Regards
 
Claude

>>> Mike Pokraka <wug at workflowconnections.com> 2014/02/27 10:26 AM >>>
Hi Claude, 

Does it also do this if you start it manually in the SAPGUI? The behaviour is by design, though my memory is a bit foggy on exactly where or how to control it. If you scroll to the right you will see it is running under WF-BATCH in column 'user context'.
Have a play with the advance in dialog settings. Failing that, last resort big hammer approach is to force an RFC call by putting a background task in between.

Regards, 
Mike

On 21 Feb 2014, at 12:22, "Claude Bourque" <claude.bourque at rcmp-grc.gc.ca> wrote:

Hello everyone,

I haven't posted anything in at least 2 years so here it goes.

I've been asked to support a new WebDynpro App that starts a workflow, the WDA app uses Function Module ARCHIV_PROCESS_FAXINPUT to start WF.

Only problem is that this FM uses sy-uname as the creator.

As seen in the attached document, if I go to the Portal and start the process, I'm listed as the WF Initiator but the strange thing is that I'm also the creator of ALL tasks including all background tasks.

Here's a text snapshot of part of the log to show that. Full screenshot is in the included attachment.

Claude Bourque            Execution started automatically          2014/02/21 07:05:45
Claude Bourque            Background work item created           2014/02/21 07:05:45
Claude Bourque            Work Item Processing Complete        2014/02/21 07:05:45
Claude Bourque            Result Processing                             2014/02/21 07:05:45

We didn't noticed this until this week when I was asked to add an email step and the email comes from the user that start the process NOT WF-BATCH.

All the steps after approval return to "normal" and WF-BATCH creates and completed the background work items again.

A solution would be to have the WDA application be launched with WF-BATCH as the user but security is NOT crazy about that idea.

Any ideas/suggestions?

Thanks.

Regards

Claude
<Background workitem dilemma.docx>
_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug

_______________________________________________
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/20140227/f8f9ff04/attachment.htm