Agent determination failure

[Mike Pokraka]

Hi Jacob, 
Check whether the agents are valid/exist. A special little 'feature' is that a nonexistent user USGHOST doesn't really constitute a "failure". Yet when workflow receives it and does the 'possible vs selected vs excluded' matching it drops the dodgy user. It's arguable whether this is a bug - part of the design is that you can send workflows to an employee due to join the company next week. 
Technically an agent is returned, but it is up to your FM to validate it isn't returning garbage. 

Cheers, 
Mike


Crane, Jacob wrote:
> Hi All,
>      More details about this issue.  The rule is set to terminate if no
> agents are found, yet is does not show up in error or in swi2_adm1.  I
> confirmed that the WFLOW ROLE entry in T77S0 is set to X.  Are there any
> other pieces of config that can cause this issue to happen?  I added
> code to the actual function run by the agent rule that sends me the
> input and output as it is run in the workflow and the function is
> returning agents.  The task is set to general.  Still, the workflow log
> shows no agents.  This only occurrs in our regression testing box (4.7,
> WAS 6.20) and is happening in both new and old development, but not to
> all tasks.
> 
> Thanks for any ideas on this,
> Jacob 
> 
> -----Original Message-----
> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
> Of Crane, Jacob
> Sent: Thursday, April 13, 2006 2:28 PM
> To: sap-wug at mit.edu
> Subject: Agent determination failure
> 
> Hi,
>      I have a weird issue where my agent determination is coming up with
> nobody in the workflow.  The rule that is used works fine when I test it
> with the data in the container as shown in the log.  Also, I wrote a
> debugging function to email me the contents of the fields in the agent
> rule when the workflow executes the rule and it showed that the same
> elements exist and are correct.  Lastly, the rule is set to terminate if
> there are no agents found and it does not, but simply shows up with
> noone assigned.  The task is set as general.  I haven't found anything
> in OSS about this and am stumped.  This workflow has worked fine in the
> dev and test systems and is now failing in our second test box.  Any
> ideas, gurus?
> 
> Thanks,
> Jacob
> 
> Jacob Crane
> Ext:  3-2629
> Cell:  678-642-8094
> 
> 
> 
> _______________________________________________
> 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