Capabilities.UpdateRestrictions

[writefayaz]

First, I want to express my appreciation for the excellent work on the cap-js/attachments plugin—it has been incredibly useful in our projects. However, I've encountered a challenge when using it. Specifically, when I annotate a service with Capabilities.DeleteRestrictions and Capabilities.UpdateRestrictions, these restrictions don't seem to apply to the plugin's upload functionality. This means that users are still able to upload new attachments or delete existing ones, even when such actions should be restricted.

It would be wonderful if the cap-js/attachments plugin could respect the Capabilities.DeleteRestrictions and Capabilities.UpdateRestrictions annotations. When these restrictions are present, I would like the plugin to prevent users from uploading new attachments or deleting existing ones, ensuring consistency with the specified permissions.

I've considered the option of manually overriding the plugin's functionality in the frontend to enforce these restrictions. However, having this feature built into the plugin would simplify the process and reduce the need for custom code, which I believe would be beneficial to many users.

Fayaz Mammoo

[RamIndia]

@writefayaz : Can you check if @readonly annotations works for you?
https://cap.cloud.sap/docs/advanced/fiori#prefer-readonly-mandatory