Change layout controller for permissions in details command

[Former Member]

How can we change layout controller for permissions shown when you select any repository > details > settings > permissions. here only 5 users are shown in the table i wanted to change the layout to see if i can display more than 5 rows but i can not seem to find the iView corresponding to this pop up screen. Any ideas?

[detlev_beutner · Accepted solution]

Hi Firasath,

The layout controller has absolutely <i>nothing</i> to do with the permission screen!

Please check http://help.sap.com/saphelp_nw2004s/helpdata/en/82/80b1a12de07c48bf74c3983f42dcf1/frameset.htm and the constraints given.

Anyhow, you can always check how to alter such an implementation, but experience is needed. In your case, the magic number 5 is defined as a <i>private static int</i> variable within the class <i>com.sapportals.wcm.control.acl.AclControl</i> which is to be found within <i>...\WEB-INF\portal\portalapps\com.sap.km.cm.ui\lib\km.appl.ui.acl_api.jar</i>.

Hope it helps

Detlev

[Former Member]

Thanks Detlev

Are you suggesting that I hvae to import the corresponding par file into NWDS and change the code and deploy? If yes could you suggest an easy way of doing it?

Thanks

Firasath

[detlev_beutner]

Hi Firasath,

In the end, this is a modification of the standard, and there are several ways to do such things (and to avoid problems with it, for example when upgrading your installation).

As this is a complex task, I won't say this and that is the right direction. That's really an individual decision for each customer. I know customers who really have a lot of modifications (and they enjoy their extended functionality), others I know who never ever would touch the SAP code. And many ways are in between...

Just for a very fast shot (but not advised as a "clean" way), you could decompile the class itself, make it compilable as a Java project consisting of one class (extending the compile classpath to fit the classes needs), do the change, exchange the original class within the JAR by your modified version and restart the portal (for exchanging WinRAR for example can be used very easily).

A more clean approach would be to import the original PAR as a portal project, decompile the class in question, remove it from the compiled JARs (which have to be added manually into the PAR structure), recompile and redeploy (within the same original namespace).

A more complicated approach is to try to create a new PAR within a new namespace, so that in the end you are not modifying the original component but just "steal" code from the original component and deploy it independently. But this needs most experience.

Not understood everything in detail?! In this case, sorry, but: It's really an absolute non-trivial task which only should be done by people having the experience to understand these lines more or less in a second...

Hope it helps

Detlev