How to hide New and Edit button based on roles. Urgent!!!!!

[madanm2103]

Hi All,

I need to hide New and Edit button for problem creator role in the Problem Task related list in Problem form.

I tried all the possible ways but still not working.

PLease help me on this.

Thanks,

Madan

[Ashish Kumar Ag]

In list view of table Personalize>List control.
Then add all the roles expect problem creator in edit roles glide list.
If you have script field for omit edit in your instance, you can also write proper condition.

[marcguy]

Personalizing Lists - ServiceNow Wiki

If your referring to the global ui actions then you don't want to mess with those but can control when they are visible on lists by using LIST Control.

there are fields for New and Edit roles or else you can script them by using the Omit New Condition field and Omit Edit Condition field.

Marc

[mitzaka]

In that manner of speaking - is there a way I can edit the base ITIL role?

What I want to achieve - I want ITIL users to be able only to READ configuration items, not create new ones and edit. I know that one way to do this is by setting up the list control on menus, so that I can omit the 'New' and 'Edit' buttons, but that solves the case only partially, as if an ITIL user opens a CI record, he will still be able to modify it.

Another approach would be to create a custom role for configuration editers and give that role ACL control so that they can view the Configuration tab.

Does anyone have any other brighter suggestions on that?

Thanks!

[marcguy]

Set up or modify the existing access control rule on cmdb_ci - CREATE and write if you don't want them editing them either) and ensure itil is not on the roles related list for this ACL, create another role like we have 'config_management' or something like that which you can then give to selected users whom you do want to have config access.

Itil will still be able to READ as the ACL for read will still contain ITIL.

Using Access Control Rules - ServiceNow Wiki

thanks,

Marc

[mitzaka]

mguythanks for that! I felt is thew better way to go, because the other approach with hiding the New & Edit buttons does not really take away the permission, but hides controls. On the side, it's much more work.

OK, so I guess I will go with the custom role, thanks again!