Actual Agent

[Kjetil Kilhavn]

Not really :-)
You'd have to explain your agent assignments to give me a significant
insight, and not least how and where you assign a value to
&ACTINGAGENT&. Your problem must be that subsequent assignments to
&ACTINGAGENT& fail, i.e. it isn't overwritten with the new value in
subsequent loops.
 
Have you tried just removing the &ACTINGAGENT& container element and
using the same role for both steps. I assume you are currently using the
container element &ACTINGAGENT& as an expression for the second step's
agent determination, otherwise it shouldn't have an effect on who
receives the work items. When you have advance with dialog in the first
step the second step should be reserved for the executor of the first
step. Don't use advance with dialog in the second step, and thus when
the second step has been completed and another loop is started the work
item is again available for all the agents. That's my theory at least -
I haven't tried it in the real world.
 
I can't say I am too impressed with the clarity of my answer here.... I
am sure if you try to explain your bindings and agent assignments this
case is quickly solved.
 
Winter and snow in Alberta yet? Here in the southwestern corner Norway
we are having an Indian summer. 25 degrees celcius here yesterday, and
we are on the same latitude as your border to the Northern Territories -
can't complain about the weather right now! Now, if any of you are
freezing your butts off and want to move here I might be able to get you
some property at unreasonable prices :-)
-- 
Kjetil Kilhavn, Statoil OFT GBS BAS DEV SAP
 



________________________________

	From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu]
On Behalf Of Hall, Jim
	Sent: 14. september 2006 15:24
	To: SAP Workflow Users' Group
	Subject: RE: Actual Agent
	
	
	Kjetil:
	 
	 Actually, that is correct.
	 
	 The first step is a User Decision.   There are 3 options, off
of this decision. It is set up to advance with dialog.
	 
	The whole WF has 2 user decisions.   Depending on the person
using the flow, they may or may not answer both questions.
	 
	What we want to happen is for the next step to be assigned to
the person who made the decision.   What seems to be happening when we
use &ACTINGAGENT&, is that the first person to interact with the WF is
the acting agent for the rest of the flow, even if a different person
answers the User Decision.
	 
	Does this clarify it any?
	 
	Thanks
	 
	 
	Jim Hall 
	Senior System Specialist
	Fortis Alberta Inc.
	Information Technology 
	

	 
	
	
________________________________

	From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu]
On Behalf Of Kjetil Kilhavn
	Sent: September 14, 2006 12:55 AM
	To: SAP Workflow Users' Group
	Subject: RE: Actual Agent
	
	
	I am not sure I have understood this correct, but my
understanding is that you have a loop in which the same two tasks are
processed over and over until some exit condition is met. Wouldn't the
step flag "advance with dialog" on your first action step in the loop
solve your requirement to reserve the next task (requiring manual input)
for the acting agent? Then the step requiring manual input should be
started immediately and would become reserved for the current user.
	-- 
	Kjetil Kilhavn, Statoil OFT GBS BAS DEV SAP
	 
	
	

________________________________

		From: sap-wug-bounces at mit.edu
[mailto:sap-wug-bounces at mit.edu] On Behalf Of Hall, Jim
		Sent: 13. september 2006 21:59
		To: sap-wug at mit.edu
		Subject: Actual Agent
		
		
		Hi:
		 
		 We have a WF where a loop at task is assigned to
several possible agents, based on roles assigned to the task.
		 
		The next step is to enter some text and in an effort to
keep it with the person who took the task over, we use an expression and
the field &ACTINGAGENT&
		The situation is such that someone makes a decision
(possible agents) and then the next task requires manual input hence the
idea around acting agent, to insure that it remains reserved for the
individual that acted on the previous step.
		 
		This does not seem to change, after the first person
touches the WF.    
		 
		This particular flow can be accessed at varying times,
due to choices made, by more than on responsible agent.
		 
		If I look at the container for the whole flow, which is
the only spot, I can see Acting Agent, it shows the first person to act
on the flow.
		 
		Should this not change as multiple people interact with
the flow, and if not, is there another field we can use, to ensure that
the steps remain linked with the person who
		chose to follow thru with the workflow?
		 
		 
		Thanks
		 

		Jim Hall 
		Senior System Specialist
		Fortis Alberta Inc.
		Information Technology 
		403-514-4159 
		Jim.Hall at fortisalberta.com 

		 

	

	
-------------------------------------------------------------------
	The information contained in this message may be CONFIDENTIAL
and is
	intended for the addressee only. Any unauthorised use,
dissemination of the
	information or copying of this message is prohibited. If you are
not the
	addressee, please notify the sender immediately by return e-mail
and delete
	this message.
	Thank you. 



-------------------------------------------------------------------
The information contained in this message may be CONFIDENTIAL and is
intended for the addressee only. Any unauthorised use, dissemination of the
information or copying of this message is prohibited. If you are not the
addressee, please notify the sender immediately by return e-mail and delete
this message.
Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20060915/e32d6b33/attachment.htm