Work Item - User Decision Step Issue

[Cooper, John M]

Hi Raja,
 
If you have a step that only sometimes needs to be executed, then add a
condition step before it to check the condition and avoid executing the
step.  In your case, check to see if the supervisor and the BGO are the
same.  If the condition is true, drop through to the step after.  If the
condition is false, execute the user decision step.
 
You may also have to add a background step to execute your business
logic to determine the supervisor and BGO prior to the condition to
ensure the data you want to check is available from the workflow
container.

________________________________

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Mark Pyc
Sent: Tuesday, August 16, 2005 10:27 AM
To: SAP Workflow Users' Group
Subject: Re: Work Item - User Decision Step Issue


G'day Raja,
 
Big tip that keeps getting repeated - don't tell us it's urgent. It has
the opposite effect than you'd hope.
 
You mentioned who it shouldn't go to, and that you don't want it going
to the 'wrong agent'. You never mention who it should logically go to
when Supervisor and Business Group Owner are same.
 
Your role either should return the desired agent or fail with error.
Otherwise it would normally go to the possible agents. 
 
I think you need to give us a bit more detail.
 
Have fun,
Mark

 
On 16 Aug 2005 15:02:57 -0000, Raja Sekhar <rajakmca at rediffmail.com>
wrote: 

	Hi,
	I had created one decision step, which had a rule, which is
defined by me. Well, I coded the rule such a way that if the Supervisor
and Business Group Owner are same then dont populate the ACTOR TABLE.
The rule is working fine ,as long as the SUPERVISOR is different from
Business Group Owner.(I used my own Business Logic to determine the
Supervisor and Business Group Owner) 
	
	But the real problem is when both the Supervisor and BGO are
same. The Actor Table is not getting populated with any entry, but the
work item is going to some UNDESITINED USER. Sometimes the work item is
coming to the WORKFLOW INITIATOR himself. This sounds quiet foolish. But
this is happening. 
	
	Now is there any way to continue the Workflow process to the
next step, when the Agent is not determined. My flow should not stop at
this point, due to lack of AGENT, and at the same time , it should not
go to the wrong user, but the flow should cooly goto the next step which
is present after this USER DECISION STEP... 
	
	Can anyone help me in this regards.
	It's pretty URGENT.
	
	Regards,
	Raja Sekhar  
	



	
<http://adworks.rediff.com/cgi-bin/AdWorks/sigclick.cgi/www.rediff.com/s
ignature-home.htm/1507191490 at Middle5?PARTNER=3>  
	_______________________________________________
	SAP-WUG mailing list
	SAP-WUG at mit.edu
	http://mailman.mit.edu/mailman/listinfo/sap-wug
	
	
	



------------------------------------------------------------------------------
This e-mail is intended for the use of the addressee(s) only and may contain privileged, confidential, or proprietary information that is exempt from disclosure under law.  If you have received this message in error, please inform us promptly by reply e-mail, then delete the e-mail and destroy any printed copy.   Thank you.
==============================================================================
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20050817/cbdc2925/attachment.htm