Ad Hoc agent assignment

[Dart, Jocelyn]

Margaret, 
Check your workflow is marked as "ad hoc agent assignment enabled" in
the basic data (you'll need to look through the version
dependent/independent tabs. 
Jocelyn  

-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Hilsbos, Margaret A
Sent: Saturday,5 March 2005 8:14 AM
To: SAP-WUG (E-mail)
Subject: Ad Hoc agent assignment 

Hello all,

I am wondering if anyone else has experienced this...

We have a workflow with ad hoc agent assignment.  When I test the ad hoc
assignment form within workflow builder, the container element is filled
correctly.  For example I have a value in Agent_0001.Agents like
USSOMEUSER.  However, when I start the workflow from SWUI and select the
same agent, then when I look at the container, Agent_0001.Agents is <not
set>. 

Also, the "Change agent" icon is visible in the Inbox, but disabled.
Regardless of whether I start the workflow as a test from within
workflow builder, or from SWUI.  That could be because the step with ad
hoc assignment kicks off immediately; but based on the Help
documentation, the function should be active anyway, and display the
actual agent rather than allowing a change.

I have refreshed buffers several times.

Has anyone else seen this situation?  

We are on a WAS 6.20 (CRM) system.   Thanks for any suggestions you can
give!

Margaret Hilsbos
Day & Zimmermann
(215) 299-5630


_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug