10-04-2007 5:45 AM
Hi,
Can some one throw light, from their experience, when you were designing the roles for your project , how many end users were there ? this had how many single roles ? how many composite roles ?
Thanks
10-04-2007 6:44 AM
this all depends on the design and business need so i don't think there is a standard answer to your questions.
10-04-2007 7:10 AM
I agree with Auke, it is all down to the business requirements, their attitude to risk & scope of the implementation, not to mention your preferences for building roles.
3 recent implementations I have been involved with
1. zero composite roles, approx 10000 single roles, 8000 users
2. zero composite roles, 60 single roles, 1000 users
3. 30 composite roles, 180 single roles, 16000 users
10-04-2007 11:19 AM
Thanks for the answer.
Now , for each of this project on an average how many transaction did the end user have.
Can you shed some light as to how inspite of these many single roles why it was not able to map into the composite?
10-07-2007 8:17 PM
> Thanks for the answer.
>
> Now , for each of this project on an average how many
> transaction did the end user have.
It was so variable that average transaction access is irrelevant. One company had a wide open data access policy with display access to 400+ transactions - far more than the functional access they had (10 - 50 transactions)
Another project had approx 50 or 60 transactions (including display) but an accountant would have far greater
>
> Can you shed some light as to how inspite of these
> many single roles why it was not able to map into the
> composite?
It was possible to map them to composites but it was decided that the drawbacks to using them outweighed the positives. The extra level of complexity afforded by composites has to be considered
10-07-2007 10:56 PM
10-08-2007 7:52 AM