Agent assignment for a background task required

[Sample, Rick]

We switched from FileNet to Documentum last week. (What a chore!) 

The user is a Communication type sap_all sap_new and calling from their
eConnector Agent.
I would have thought this user type would still be able to start the BG
task, but it did not 
without jumping through the hoops.

It failed for this type user and a dialog user. After the below steps,
non issue at this point. 
I was just trying to figure out why a non dialog user could not start a
BG task. Seems to work 
same in 4.6c and ECC6. "It's not a bug... It's a feature!"

Thanks,
Rick



-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Mike Pokraka
Sent: Wednesday, August 15, 2007 2:59 AM
To: SAP Workflow Users' Group
Subject: RE: Agent assignment for a background task required

Hi Rick,
Sounds like something your should report to SAP. A background task
should start regardless.
One thing that *might* be an issue is that you are trying to start a BG
task directly as a dialog user which may not be permitted. In this case
it shouldn't work afterwards, so there's a bug in at least one of the
scenarios.
So we're back to reporting this to SAP. Please let us know what they
come back with as I'm also curious.
Cheers,
Mike


On Tue, August 14, 2007 6:52 pm, Sample, Rick wrote:
> I will have to test in 4.6c but in ECC6 I created a couple of local BG

> tasks and ran through the below steps. I refreshed buffs several 
> times.
>
> I create brand new BG task never touching the agent assignment, and 
> execute the SAP_WAPI_START_WORKFLOW. It fails every time with no agent

> assignment.
> I switch to FG, set as General and it starts fine.
> I switch back to BG type and try to remove the agent assignment but 
> never fails again due to no agent assignment. (Permanently set now?
> Seems to be)
>
>>>background task should always execute.
> This is what I thought was supposed to happen and I was testing 
> because it failed to start the BG task.
>
> If I do not change the agent assignment to General (at least in ECC6) 
> it will fail to start using SAP_WAPI_START_WORKFLOW.
>
> Any other clues?
> Rick
>
> -----Original Message-----
> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On 
> Behalf Of Mike Pokraka
> Sent: Tuesday, August 14, 2007 11:53 AM
> To: SAP Workflow Users' Group
> Subject: Re: Agent assignment for a background task required
>
> Rick,
> Sounds like the problem was in your original scenario - perhaps a 
> forgotten buffer refresh or something. The rest you describe behaves 
> as it should. A dialog task shouldn't error because of missing agents 
> and a background task should always execute.
> Why not create a new task based on same object and try it.
> Cheers,
> Mike
>
> On Tue, August 14, 2007 4:58 pm, Sample, Rick wrote:
>> We need to start a background task via SAP_WAPI_START_WORKFLOW.
>> If task is in background, it errors due to no Agent Assignment. Fine.
>>
>> I set to foreground, set task a General, save, set back to Background

>> and save and refresh buffers.
>> Now the background task starts as expected with agent.
>>
>> When I try to remove the General Task to make the task fail (because 
>> no
>> agent)
>> I can not get it to fail again. Ever!
>>
>> Anyone know how to set it back to org state? That is, without being 
>> set as General Task?
>>
>> Rick Sample
>> SAP Business Workflow Developer
>> Graybar, Inc.