The CreatorCon Call for Content is officially open! Get started here.

create incident without any role

SudhirOjha
Mega Guru

Which role is required to create a incident from self- service.

Whenever i opening a ticket --its saying not authorized.

the user is just created with no role assigned to it.

Could any one guide me on that.

find_real_file.png

When click on New -- it gaves Not authorized.

find_real_file.png

1 ACCEPTED SOLUTION

Ok, there is a LOT going on here.



I spoke with one of our subject matter experts and here's what she had to say.



Non-roled users CAN create incidents, but when they do from the standard view, there is a ui action named "new" (/sys_ui_action.do?sys_id=c9ce66b4d703120060faef637e610334) that redirects the user to a service catalog item called "Create Incident" (sys_id = '3f1dd0320a0a0b99000a53f7604a2ef9' which appears NOT to exist in your instance)



Screen Shot 2018-01-25 at 11.06.48 AM.png



In fact, the majority of OOB service catalog items do not appear to exist in your instance.


Mine:


Screen Shot 2018-01-25 at 11.07.27 AM.png



Yours:


Screen Shot 2018-01-25 at 11.08.28 AM.png




Which explains why when the user is redirected to the URL - /nav_to.do?uri=/com.glideapp.servicecatalog_cat_item_view.do%3Fsysparm_id%3D3f1dd0320a0a0b99000a53f7604a2ef9   there is nothing for them to view and as such, the message "Not Authorized" displays.




This file was deleted by the system. We can try to restore this file and then check if the functionality resumes.



https://dev17527.service-now.com/sys_metadata_delete.do?sys_id=09107e080c6d47b49068b600bd537244



There are 59 delete items with the update name of "catalog" - you might want to consider reviewing which of these needs restoration.



SUDHIR's Test Instance


View solution in original post

22 REPLIES 22

Pradeep Sharma
ServiceNow Employee
ServiceNow Employee

Hello Sudhir,



OOTB end users without role can create Incidents. Did you modify any ACL's on your instance?


No. --this is basically happening on all instances


the instance is quite new and i was just testing.


adamjgreenberg
ServiceNow Employee
ServiceNow Employee

I just tested this in a freshly provisioned out of box instance with a new user that has zero roles and it works as designed.



There is something about how you are testing that you have not told us, or you have some ACL or a specific role assigned to the module that is preventing the user from opening a new incident in the self service module.



Can you share which instance this is being tested in?