Issue with Workflow task agent determination

[Kjetil Kilhavn]

Onsdag 24. februar 2010 07.48.50 skrev srinivas:
> Actually I missed out few points in my previous mail. My question is,before
> the step (What I have raised in my previous query)  there was a dialog step
> where in the user does the Invoice release via standard sap t-code.After
> executing that task the follwing step is lying only in one user inbox.I
> agree what you said is 100% right as the agent is hard coded
> as wf_initiator,in this case catherine is the user.
You have to describe your solution - otherwise it is all guesswork and the 
answer "because it was created on Tuesday" may be correct (if you have a 
responsibility rule depending on day of week).

> But my question is whydid the workitem went to Catherines inbox??
A plausible explanation is that it happened because you have instructed SAP to 
send it to the Workflow initiator, and Catherine is the workflow initiator. 

> Is that so,did she run the t-code??? This is where I am gettig confused.
Is the following correct for the step you are confused about?
- possible agents: Anyone
- excluded agents: No-one
- responsible agents: Workflow initiator

If so the executing agent of the previous step is not relevant, because 
workflow initiator is not the actual agent of the previous step, it is the 
agent that started the workflow. If the workflow is started by an event you 
must check the parameter binding for the event linkage - often it binds the 
event creator to the workflow initiator variable.

So, if you want the work item to go to the actual agent of the previous step I 
suggest you create a workflow container variable of type swhactor, bind the 
actual agent of the previous step to that and use the variable as responsible 
agent instead of using workflow initiator.

> Please let me know the possibilities and also request kindly dont 
> get annoyed if my query weired.Thanks in advance.
>
> On Tue, Feb 23, 2010 at 1:31 PM, Rick Bakker <rbakker at gmail.com> wrote:
> > Hello,
> >
> > Unless I've missed something here, the answer is that it is supposed
> > to work like that.
> > If you have a General task with no excluded agents and the agent is
> > specified as workflow initiator, then it will go to the workflow
> > initiator. It would only go to all users if no agent was specified.
> >
> > Setting a task as General makes everyone a possible agent. Setting the
> > agent as WF Initiator makes the workflow initiator the responsible
> > agent.
> >
> > If you want the task to go to everyone, then why are you specifying WF
> > Initiator as the agent?
> >
> > regards
> > Rick Bakker
> > Hanabi Technology
> >
> > On Mon, Feb 22, 2010 at 8:39 PM, srinivas <ootasrinivasreddy at gmail.com>
> >
> > wrote:
> > > Hi Experts,
> > >
> > > I am facing an issue regarding agent determination for a workflow
> >
> > task.The
> >
> > > task step is dialog step and it is General task.The major doubt I have
> > > is below the taskid in Agents, Wf_initiator is filled and excluded
> > > agents is blank.But the issue is this task is only going to one user's
> > > inbox.No one else is receving this task.My doubts are: Why is this task
> > > only going to
> >
> > one
> >
> > > user inbox not all?As it is general task,I think this task should be
> > > available in evry ones inbox.Please correct me if I am wrong and also
> >
> > please
> >
> > > let me know the reasons for the single agent determination inspite the
> >
> > task
> >
> > > is general.Thanks in advance.
> > >
> > > --
> > > Thanks and Regards
> > > Srini..
> > > SAP Technical Consultant
> > > BAS
> > > srinivas.oota at eds.com
> > > srinivas.oota at hp.com
> > > +919246647077
> > >
> > > _______________________________________________
> > > 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

-- 
Kjetil Kilhavn (+47 40220607)
Blue Consulting AS (http://www.bluec.no)