How to find general task sent to all agents?

[Dart, Jocelyn]

Hi Michael,
There is an OSS note to make this happen - under the EBP stuff -
works in 6.10 - not sure if it is downgradable.
Can't remember the OSS note but look in component SRM-EBP-WFL.
 
Jocelyn
 
-----Original Message-----
From: Michael Pokraka [mailto:workflow at quirky.me.uk]
Sent: Friday, 21 February 2003 1:32 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: How to find general task sent to all agents?
 
 
Thanks Jocelyn, I do like the idea of testing who forwards, _that_ could
prove quite useful.
Though I would prefer the approach of desiging it such that the
situation can't occur to start with, unfortunately I don't design many
of the flows I'm working with - you should know the situation all too
well :)
What I do normally do is add WF_ADMIN as possible agents to _all_ tasks
as standard. This way anything that comes into the WF administrator's
inbox is automatically a red flag that something's wrong.
 
The main problem still remains that I can get caught out by a
workflow at a client and 'which one is it and where has it gone?'
often gets asked before 'can you fix it?' (which is usually the easy
part).
A nifty workaround is also a custom copy of RSWUWFML to flag these
things, but even this leaves a loophole in that it can miss the odd one
which gets created and executed between scheduled runs (not unlikely
since all users receive it...)
I'll see if I can find the time to write some report to match WI agents
against possible agents on a more generic level. This could be a good
'monitoring' type tool.
 
Cheers
Mike
 
On Thu, Feb 20, 2003 at 12:54:20AM +0100, Dart, Jocelyn wrote:
> Hi Mike,
> Have you considered changing your workflow to calculate the agents in advance, e.g. by a background
> step or virtual attribute, and then test them prior to starting the next step.
> You could also use this to save the selected agents to a workflow container element and
> then compare the actual agent of the work item with the originally selected agents - handy
> to track who is forwarding stuff instead of doing the work themselves also.
>
> For your existing workflow instances, you might be able to use one of the WAPIs to get
> the work item recipients and compare to who is determined by your rule for the same data.
> But a more permanent solution would be advisable.  At least change your rule to always go
> to a default agent, e.g. the business process owner or the workflow administrator, if no one specific can be found.
>
> Regards,
>         Jocelyn Dart
> Consultant (SRM, EBP, Workflow)
> and co-author of the book
> "Practical Workflow for SAP"
> SAP Australia
> email: jocelyn.dart at sap.com
> phone: +61 412 390 267
> fax:   +61 2 9935 4880
>
>
>
>
> -----Original Message-----
>> From: Kjetil Kilhavn [mailto:kjetilk at statoil.com]
> Sent: Tuesday, 18 February 2003 8:42 PM
> To: SAP-WUG at MITVMA.MIT.EDU
> Subject: Re: How to find general task sent to all agents?
>
>
> Check the roles used. One of them probably has the "Terminate if the role
> resolution has no result" unchecked.
>
> Select the checkbox and then you can follow the work items up through the
> "Work items without agents" list - transaction SWI2_ADM1
> That should make it easier to find out when the problem occurs and fix the
> problem.
> --
> Kjetil Kilhavn
>
>
>
>
>
>                     Michael Pokraka
>                     <workflow at quirky.me.        To:     SAP-WUG at MITVMA.MIT.EDU
>                     uk>                         cc:     (bcc: Kjetil Kilhavn)
>                     Sent by: SAP                Subject:     How to find general task sent to all agents?
>                     Workflow
>                     <Owner-SAP-WUG at MITVM
>                     A.MIT.EDU>
>
>
>                     17.02.2003 12:01
>                     Please respond to
>                     "SAP Workflow Users'
>                     Group"
>
>
>
>
>
>
> Hi all,
> I have an urgent requirement to find an instance of a general task.
> The problem is that some glitches occasionally cause a task to go ou to
> everyone. The problem is to find which one is the culprit, as by the time
> we notice someone's already reserved/executed it (most likely the wrong
> person).
>
> Any input greatly appreciated
> Cheers
> Mike
>
>
>
>
>
> -------------------------------------------------------------------
> The information contained in this message may be CONFIDENTIAL and is
> intended for the addressee only. Any unauthorised use, dissemination of the
> information or copying of this message is prohibited. If you are not the
> addressee, please notify the sender immediately by return e-mail and delete
> this message.
> Thank you.