Show or Hide Commands based on Users Folder Permission

[rehan_hoosien]

Hi. Hoping that somebody that can point me in the right direction for this:

I have created a new layout set, and allocated a Collection Command Group which has copies of the commands: new_file & delete_mass.

The problem is that even when the user has Read-Only access to a specific folder, the delete_mass command is still shown to the user.

On the other hand, the new_file command is displayed dynamically based on the current user's access permission to the folder (command is hidden if user does not have full access to the folder).

Can the delete_mass command be made to behave the same as the new_file command? Any ideas on a workaround or resolution for this will be greatly appreciated.

Thanks, Rehan.

[LJB · Accepted solution]

Hi Rehan,

This is in fact behaving correctly, I presume if you use this command to delete something for which you don't have it doesn't allow you to do this, so it is just the display of the command you are asking about, correct?

There is a difference between mass commands and other commands in that when commands that are executed for a single resource there is a check to see if the command is executable(permissions check) and this is done when the resource is being rendered.

Mass commands are however always shown as there is a possibility that when it is being used that items for which you don't have permissions may be selected(although you still won't be able to delete them), there is no check to see if the command is executable when each resource is rendered. There is no possibility to do this either as it would have to send an event to the command on each click when a resource is selected. There is however a check once the command is selected and you should get a message like "Delete failed for filename..." if you don't have the correct permissions.

Kind regards,

Lorcan.

[rehan_hoosien]

Hi Lorcan.

Thanks for the info, i had hoped for directions to a workaround where i could force a check against "high level user permissions" first...but the standard system logic as you have axplained it makes sense and explains why the system treats the two commands differently.

Cheers.

.

[Former Member]

Hi, Rehan.

This is not normal behaviour, it looks like a bug.

See the topic http://forums.sdn.sap.com/thread.jspa?threadID=96555.

What is SPS level of yor portal?

Mikhail.