Have you ever been burdened by the huge amount of roles your portal implementation has? Are KM ACLs becoming a huge headache for you? Well, I have gone through the same and I know how troublesome it can be. With the growth in the need for very finely needed content segmentation, it has become necessary not to let the no. of roles get out of hand. Although , you can use the Standard Out of the box functionality in smaller organisations / requirements, but using the same can be hell for much larger organisations.
If you can think what it is like to manage about 50 roles, and then one day they grow to about 150! and then on and..on...and.on. SAP provides us the use of filter factories to minimise the number of roles needed in your implementation. These are custom code application filters that actually filter the content of a role for different users. You can actually have the same role seen differently by many users. Thus managment of roles and authorisations is reduced.
There are a few downsides.
The first is that there are some custom components required that are used to implement the functionality.
The second is that each folder, iView and page etc that is required to be seen based on the filter needs to have an extra attribute that will be interpreted at run time.
The last, and most important, downside is that unless the roles are well documented, it will not be clear why the role as seen by the administrator doesn't match what the end user sees.
No comments:
Post a Comment