Create New Reminder within an Incident - Permissions?

mattthompson
Kilo Contributor

I have enabled "Reminders" within an Incident by doing the following.  

This is all out of the box - no manipulation and we are on Fuji.

Added the "Follow up" field to the Incident form

find_real_file.png

Enabled "Reminder --> Task" as a Related List to the Incident

find_real_file.png

When I click "New" I get the following form. When testing in my dev environment all works as it should - email reminder is sent based on the date/time in the "Follow up" field.

find_real_file.png

Now, my questions is, I have the "New" button available to me because I am an admin.   What role/module do I need to give my user/group community to allow them to create a "New" reminder?

Thanks a lot,

Matt

18 REPLIES 18

Hey Sharon,



You have to create additional ACL on operation read and your issue will be resolved.


Please let me know if you have any questions.


Thanks Pradeep - that was it.  


AAUGH!!!   I had set this up in our Dev environment but never got any feedback from our managers if they wanted to implement it in Production.   We had since cloned back over Dev to do some testing and now they've asked to look at it again.     I'm going back through what I thought I had done before and it's not working so I need help again.  


This is what I currently have...


I added the Follow up field to the Incident form and enabled the Reminder related list.


From the Reminder List, I go to Configure-List Control and have set the New, Edit, Filter and Link Roles to include the Itil role.


ListControl.JPG


I have created Create, Read and Write ACL's for Reminder-Task with the Itil role.  


ACL.JPG


However unless you're an admin, you do not see the New button on the Reminder related list.   Was there also a UI Action that I needed to change as well?    


Hi Chuck,


Could I ask you a general question regarding this:


Since I have the same issue as Sharon, I found your advise very helpful - Thanks for that!


But I do not really understand why I need to create an ACL, so the ITIL user can see the button.


From my understanding, since was no ACL on the reminder table at the beginning (at least in our instance), I supposed that everybody should have been able to see the button!?


So why do we first have to restrict the access, only to then grant it again?


Could you briefly explain this? Maybe I just missed the logic of ACLs 🙂


Thanks in advance!


Best regards,


Christoph


At the time, we were on Fuji so maybe something has changed since then. We are currently on Helsinki and I've just tried deactivating those acl's and the button seems to work without them.





Sharon K. Janisch


Applications Engineer


Katten Muchin Rosenman LLP


525 W. Monroe Street / Chicago, IL 60661-3693


p / 312.577.8050 f / 312.902.1061


sharon.janisch@kattenlaw.com<mailto:sharon.janisch@kattenlaw.com> / www.kattenlaw.com<http://www.kattenlaw.com/>