Using composite roles in agent assignment

[Paul.Bakker@osr.treasury.qld.gov.au]

Claude/Mark,

Thanks very much for that tip - I was going insane assigning 20 roles in
the Dev, Test and Prod environments. (I still haven't worked out how to
make these assignments transportable!).

Another good trick is to use Task Groups. The set of roles assigned to the
Task Group are inherited by each individual Task.

cheers!
Paul



|---------+-------------------------------->
|         |           "Claude Bourque"     |
|         |           <cbourque at bank-banque|
|         |           -canada.ca>          |
|         |           Sent by:             |
|         |           sap-wug-bounces at mit.e|
|         |           du                   |
|         |                                |
|         |                                |
|         |           26/07/2006 04:09     |
|         |           Please respond to    |
|         |           "SAP Workflow Users' |
|         |           Group"               |
|         |                                |
|---------+-------------------------------->
  >------------------------------------------------------------------------------------------------------------------------|
  |                                                                                                                        |
  |       To:       "SAP Workflow Users' Group" <sap-wug at mit.edu>                                                          |
  |       cc:                                                                                                              |
  |       Subject:  RE: Using composite roles in agent assignment                                                          |
  >------------------------------------------------------------------------------------------------------------------------|




Paul,

My 2 cents worth.

In a similar fashion, we needed to assign 8 roles to a task. We couldn't
use a composite role because they are NOT to be grouped (I wasn't aware of
your problem). I found it kind of annoying to do it using PFTC's agent
assignment since you have to repeat the step 8 times. However, using PPOMW,
we were at least able to use a wildcard search to bring up all 8 roles and
then use the check boxes to pick them all. So, if your 20 roles all have
part of their name the same you can select them all using a wildcard
search.

Claude
-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of
Mark Pyc
Sent: July 18, 2006 9:56 AM
To: SAP Workflow Users' Group
Subject: Re: Using composite roles in agent assignment

G'day Paul,

I believe you are correct. The role that is linked to the Task needs to be
assigned to agents. Having a composite role which brings together a number
of other roles doesn't link it to users who have any of the individual
roles and indeed you wouldn't want to. If this were the case and you had a
general role which gave basic access that was allocated to each composite
role, then linking any composite role would be the same as marking the task
as general.

One concept that I have used before where there are company code specific
roles and I wanted each company code linked to the same task was to have
the security people create a dummy role which was included in each of the
company code specifc roles. This way I could just link the task to the
dummy non-cocd specific role knowing that users within each CoCd would be
assigned this role. This is really just transfering maintenance effort to
the security team rather than a WF admin team, however I believe that the
security team can be quite sexy about it with help of some external
products.

Good luck. If you do come up with anything cunning please report back.

Have fun,
Mark


On 7/12/06, Paul Bakker <paulbakker at hotmail.com> wrote:

Hi,

 I need to assign about 20 roles to a task, to define the set of possible
agents. I was hoping to get around this by defining a COMPOSITE role, which
includes these 20 single roles.

I had never actually tried using composite before, but I always assumed
that it would work - I hoped task would 'inherit' the users assigned to
each single role.

But this turns out to be wrong - the workflow fails because the task has no
possible agents! When you navigate through the Agent maintenance screen,
you cannot drill down to any agents.

Can somebody confirm / deny that composite roles CANNOT be used for agent
assignment (except when the agents are directly assigned to the composite
role itself)?

thanks,
Paul







******************************************************************************************************************************************************

Only an individual or entity who is intended to be a recipient of this e-mail may access or use the information contained in this e-mail or any of its attachments.  Opinions contained in this e-mail or any of its attachments do not necessarily reflect the opinions of Queensland Treasury.

The contents of this e-mail and any attachments are confidential and may be legally privileged and the subject of copyright.  If you have received this e-mail in error, please notify Queensland Treasury immediately and erase all copies of the e-mail and the attachments.  Queensland Treasury uses virus scanning software.  However, it is not liable for viruses present in this e-mail or in any attachment.  

******************************************************************************************************************************************************