URGENT: &_WORKITEM.CREATEDBYUSER.NAMEWITHLEADUS doesn't work properly

[Van der Burg, Jeroen JA SITI-ITPSEE]

He Jocelyn,
 
? That is precisely what I am doing and explaining to Robert (this is =
his problem). He recalled the mail you responded to as it is working =
fine now.
 
I am using this a lot where the first task in a group of tasks is =
assigned to a group of agents, but I want to be 100% sure that =
subsequent steps are the responsibility of the person who executed the =
first task and not all possible agents of the initial role assignment. =
Very common situation in HR workflows.
 
 
You'll have a great weekend!
 
 
Jeroen
Co-author of many books on how to enhance your pulling capabilities =
(sorry guys, it's Friday!).
 
-----Original Message-----
From: Dart, Jocelyn [mailto:jocelyn.dart at sap.com]
Sent: 28 March 2003 11:38
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: URGENT: &_WORKITEM.CREATEDBYUSER.NAMEWITHLEADUS doesn't
work properly
 
 
Hi Jeroen,
Why don't you try using the standard task container element =
_WI_ACTUAL_AGENT from the step to fill
your workflow container element Agent_0001 instead?
I assume you have made sure you are not picking this up from a =
background step.
Regards,
        Jocelyn Dart
Consultant (SRM, EBP, Workflow)
and co-author of the book
"Practical Workflow for SAP"
SAP Australia
email: jocelyn.dart at sap.com
phone: +61 412 390 267
fax:   +61 2 9935 4880
 
 
 
 
 
-----Original Message-----
From: Robert van den Berg [mailto:rvdb99 at hotmail.com]
Sent: Friday, 28 March 2003 9:28 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: URGENT: &_WORKITEM.CREATEDBYUSER.NAMEWITHLEADUS doesn't
work properly
 
 
Jeroen,
 
I have tried that, but still the wf_batch is filled in.
I have as optional task the ALLAGENTSOFTASKGETANDDISPATCH task.
 
Two situations:
1) I exectuted task 1-5 without sending the workitem to another user =
(via a
standard WF task ALLAGENTSOFTASKGETANDDISPATCH) and then want it to =
become
to me.
Result: the same user as the WF initiator is filled in
2) I executed task 1-5 with sending the workitem to another user (via a
standard WF task ALLAGENTSOFTASKGETANDDISPATCH) and then want it to =
become
to me.
Result: wf_batch is filled in....
 
 
 
 
 
>From: "Van der Burg, Jeroen JA SITI-ITPSEE"
><jeroen.vanderburg at shell.com>
>Reply-To: SAP Workflow Users' Group <SAP-WUG at MITVMA.MIT.EDU>
>To: SAP-WUG at MITVMA.MIT.EDU
>Subject: Re: URGENT: &_WORKITEM.CREATEDBYUSER.NAMEWITHLEADUS doesn't =
work
>properly
>Date: Fri, 28 Mar 2003 11:03:29 +0100
>
>Robert,
>
>On your previous dialogue step move the actual agent parameter into a
>workflow container element.
>
>You need to click the 'show all values' button here as this is a system
>parameter and not shown initially as an export parameter option for the
>task binding.
>
>
>Regards,
>
>
>Jeroen
>
>-----Original Message-----
>From: Robert van den Berg [mailto:rvdb99 at hotmail.com]
>Sent: 28 March 2003 10:53
>To: SAP-WUG at MITVMA.MIT.EDU
>Subject: URGENT: &_WORKITEM.CREATEDBYUSER.NAMEWITHLEADUS doesn't work
>properly
>
>
>I have a WF with several tasks.
>After the 5th task, I put the &_WORKITEM.CREATEDBYUSER.NAMEWITHLEADUS& =
in
>an
>container element "Agent_0001".
>
>My problem: the WF puts the creator of the workflow in this =
"Agent_0001".
>
>How can I make it possible that the user who executed the previous =
workitem
>is put in this "Agent_0001" container element??
>
>When I use &_WORKITEM.EXECUTEDBYUSER.NAMEWITHLEADINGUS&, it uses =
WF_BATCH.
>When I use &_WORKITEM.CREATEDBYUSER.NAMEWITHLEADUS&, it uses the user =
who
>created the workflow.
>
>Please help!
>
>Thnx!
>
>_________________________________________________________________
>MSN Zoeken, voor duidelijke zoekresultaten! http://search.msn.nl
 
 
_________________________________________________________________
MSN Zoeken, voor duidelijke zoekresultaten! http://search.msn.nl