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

i have tested on my company instance also



but below steps are form my dev instance.



SUDHIR's Test Instance


userId- testincident


password- testincident



Login to Service now application with a new user (no roles).



search for incidents in left navigation.



find_real_file.png



create on new button.




find_real_file.png


Sudhir,



Tell me about - sys_script.do?sys_id=2bc2f9b1c0a801640199f9eb0067326e



would you be kind enough to disable this BR and try testing again?


Adam-- Still getting same issue.


Sudhir,



I was able to get to opening a new incident by modifying the URL like this:



dev17527.service-now.com/incident.do?sys_id=-1



This tells me that your "NEW" button has some functionality behind it that is not allowing the user to open a new incident.



In fact, it tries to take the user to another page




As expected - dev17527.service-now.com/incident.do?sys_id=-1&sys_is_list=true&sys_target=incident&sysparm_checked_items=&sysparm_ck=20d21b76db330300f2ad76efbf9619907a6109cf73f1e23971a02ac75487c0aa78d5ebcd&sysparm_fixed_query=&sysparm_group_sort=&sysparm_list_css=&sysparm_query=caller_id%3djavascript%3ags.getUserID()%5eactive%3dtrue&sysparm_referring_url=incident_list.do%3fsysparm_query%3dcaller_id%253Djavascript%253Ags.getUserID%2528%2529%255Eactive%253Dtrue%255EEQ%4099%40sysparm_view%3dess%4099%40caller_id%3djavascript%253Ags.getUserID%2528%2529%255Eactive%253Dtrue%4099%40sysparm_clear_stack%3dtrue&sysparm_target=&sysparm_view=ess




As testuser - dev17527.service-now.com/com.glideapp.servicecatalog_cat_item_view.do?sysparm_id=3f1dd0320a0a0b99000a53f7604a2ef9




So the reason your user is getting a "not authorized" message is because you are trying to direct them to the catalog item above.


Correct--- but is this mean my all the instances have same issue.....


becouse in my company page also--i am getting similar behaviour (DEV/UAT/PRO) (which are all new instances) still not used.



I am afraid--something we are missing with this explanation.