ddumas wroteRennur wroteMy guess is the standard AIM delete button ignores the PROTECT rule.
Create a 'process' called 'DeleteObject' and have it check if the AddedBy = LoggedInEmployee and if so DELETE ProjectApprovalStatusNote
In the form operations, add a button (icon only & next to the item) to start process & delete the object instead of usind the AIM 'Delete Object' function.
So, turns out that AWARE IM support thinks you may be right on thr PROTECT not covering a Delete. I got this to work by using a regular Delete operation, but then specifying the following in the Accessibility definition the Delete operation:
ProjectApprovalNote.AddedByLoginName=LoggedInEmployee.LoginName
AddedByLoginName is a shortcut, as Accessibility definition does not allow references.
Works now - Delete only shows up for the user that created the note.
Yea!
