Adding a new-style copy alert fails silently when missing the appropriate permissions

[Jane Sandberg]

In 3.1.2, adding a copy alert without the appropriate permissions acts like an alert has been placed, and never notifies the user that their alert didn't actually take.

There is a message in the console:

[PCRUDContext 5]: open-ils.pcrud.create.aca failed.
code => 404
status => An unknown server error occurred
params => ["ed3b848243d9c93861327bdfd56f7912",{"__c":"aca","__p":[null,{"__c":"ccat","__p":[101,1,"t","_NORMAL ALERT",null,null,null,null,null,"f",null]},255348,"f",null,358572,"Missing. Route to Lara.",null,null,1]}]

It would save a lot of frustration if the user would be notified that they don't have the correct permissions, and they could do something about it. :-)

Steps to reproduce:
1) Log in as a user without the ADMIN_COPY_ALERT permission
2) Open an item in Item Status list view
3) Actions > Add > Copy alert
4) Fill out the form
5) Click okay
6) Re-open that item in Item Status -- note that the alert wasn't added

[Remington Steed (rjs7)]

I opened bug #1811442, which might address the lack of permission. But I agree that Evergreen should do something nicer whenever a case like this occurs.

[Jennifer Pringle (jpringle-u)]

Edits and deletions of copy alerts also fail silently when the user doesn't have the needed permissions (UPDATE_COPY_ALERT and DELETE_COPY_ALERT) or has the permission but not at the needed depth. (For example, if permissions are granted at the library level and Library A tries to delete Library B's alert it appears to succeed but doesn't actually delete.)

(Tested on 3.1.7 with the fix for https://bugs.launchpad.net/evergreen/+bug/1783421)

[Lindsay Stratton (lstratton)]

Noting that this is still an issue in 3.10