Allow deletion/cancellation of inventory requests

[jkleinsc]

Right now there is no way to delete/deny/cancel an inventory request.

[stoyan-ekupov]

Hi @tangollama, @jkleinsc,
I'd like to work on this

[jkleinsc]

go for it @StiveK!

[stoyan-ekupov]

@jkleinsc Few questions regarding this feature.

• Do we need permissions for deleting an inventory request? If yes, which user roles will have such permissions?
• Are there any other conditions that will control who can delete a request, e.g. a requester can delete his/her own requests regardless of his/her roles?
• Anything else to be considered when building this feature?

[tangollama]

The rights to execute an action are governed by permissions / capabilities, which are mapped to roles by default but can be modified in the admin interface. So what you're looking for is the following: - users with the right to add_inventory_request should be able to delete their own request. - users with the right to fulfill_inventory should be able to delete any inventory request. You can find the list of permissions in this mixin: https://github.com/HospitalRun/hospitalrun-frontend/blob/master/app/mixins/user-session.js I hope that helps.

…

On Sun, Apr 23, 2017 at 3:28 AM, Stoyan Ekupov ***@***.***> wrote: @jkleinsc <https://github.com/jkleinsc> Few questions regarding this feature. - Do we need permissions for deleting an inventory request? If yes, which user roles will have such permissions? - Are there any other conditions that will control who can delete a request, e.g. a requester can delete his/her own requests regardless of his/her roles? - Anything else to be considered when building this feature? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#334 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA4t7XHBBCyijQk80AESWi0fq6-p4-MJks5ryv2AgaJpZM4Hq-M7> .

-- *Joel Worrall * @tangollama <http://twitter.com/tangollama> (c) 717.385.9970

[tangollama]

That same mixin has a helper function, currentUserCan to figure that out for you.