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

Access to scoped reports

shetzel
Mega Guru

Hello..

I have the following 5 reports below created by ServiceNow contained with Application scopes.   When I try to view these as an ITIL user using the 'Reports > View/Run' application and module they do not display.   Same for me as an Admin unless I change my scope to that listed.   For example to see the Issue Breakdown report I need to switch to the 'Audit' Application.

How do users get access to reports built within Application scopes when they can't switch between the different scopes?

Thanks!

scoped reports.bmp

1 ACCEPTED SOLUTION

shetzel
Mega Guru

I just tested within my demo instance and this works fine.   A properly rolled user can access the "Issues Breakdown" report.   The issue I reported can not be reproduced on a demo instance running Jakarta.



This looks to be an issue either on the version of Istanbul I'm working on or something with the instance.



Thanks,


Scott


View solution in original post

3 REPLIES 3

Scott Jordheim
Giga Guru

Do those applications have restricted access (ACLs, Business Rules, etc.)? Users would need to be able to view that data, otherwise the reports would return no data to display (or something similar). Besides the normal table data restrictions, it appears that you need those particular user roles to view the report as well. Did you try adding one of those roles to your user account to test it?



When you go "View/Run", where are you looking? Or are you searching in the reporting global search with something like "*risk"?


Not an ACL issue.   This happens with my account also as an "Admin".. but I can change Application scopes to view the report.



View/Run.. search for "risk" in All reports.   The two reports above with risk in their names will not appear in the returned results unless I change my Application scope to 'Risk'


shetzel
Mega Guru

I just tested within my demo instance and this works fine.   A properly rolled user can access the "Issues Breakdown" report.   The issue I reported can not be reproduced on a demo instance running Jakarta.



This looks to be an issue either on the version of Istanbul I'm working on or something with the instance.



Thanks,


Scott