Ad-hoc agent not found error in approval preview applet

[David Weston]

Just resending in case this was rejected previously.
 
 
Hi Jocelyn, thanks for the help. We have coded the Create method just as =
in
the Create method for ASBMANAGER using the l_nosave variable.
 
We have a role attached to the task, which has the user attached to
it....and the excluded agents doesn't match either.
 
We'll keep looking and work with OSS. But if you have any other ideas =
just
let me know.
 
Cheers
Dave=20
 
 
-----Original Message-----
From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of =
Dart,
Jocelyn
Sent: 28 September 2004 22:42
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Ad-hoc agent not found error in approval preview applet
 
 
Dave,
You have not most likely not coded your adhoc agent correctly for the
approval preview. Make sure you follow the pattern in ASBMANAGER and the
other examples for when the "save" flag is off.
 
Also check ... you have assigned a user id as agent, that user is a =
possible
agent of the relevant task, that user is not an excluded agent. Regards,
Jocelyn
 
-----Original Message-----
From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of =
David
Weston
Sent: Wednesday,29 September 2004 8:19 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: SRM: Ad-hoc agent not found error in approval preview applet
 
Hi folks,
 
We are using the ad-hoc agent functionality using a copy of the =
ASBMANAGER
business object, recreating the 'Create' method to fill the Agents
attribute. We have a 2 step workflow approval process and when  we =
create a
shopping cart and select 'Approval Preview' the first approval step
(TS10008069) displays 'no approval available' and the 'Ad-hoc agent not
found' error message in red. The second approval step displays our users
correctly, which also uses an adhoc agent object.
 
If we then select 'Order' or 'Hold' and go to Check Status for our =
shopping
cart and look at the applet via approval preview both approval steps are
displayed correctly !!
 
Anyone seen this type of behaviour before ?
 
Thanks for any help or tips to solve this one. By the way we have =
created an
OSS message as well to keep things official !!
 
Dave