I am building a custom RAP application on ABAP cloud. I have defined some custom actions which are being controlled by instance feature and authorization behaviour implementations.

All works BUT

I noticed that the custom action buttons are either being 'enabled' or 'disabled' - based on the behaviour implementation outcome - but they are always visible.

That seems odd to me. When we disable eg a standard 'delete' action then that button is not shown at all.

I have the same requirements for custom actions. I do not want a user to see 'custom action' buttons if they are not supposed to be able to have that functionality. In addition if one has a larger number of actions then a whole row of disabled buttons is shown ... not quite user design friendly.

I would have thought that an 'instance authorization' implementation that returns back that a user is not authorized would basically do that ... but no .. the button remains visible but disabled. So there does not seem to be any difference in that respect between an instance feature and authorization result check.

I looked for annotations, different return results in the implemenations, etc but cannot find a way to control the visibility of a custom action button. Or am I missing something ?

Thanks,

Steven