CMDB Admin Unable to Access Records from Another Application Scope in CI Class Manager
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 hours ago
Hi all,
We're running into an issue with CMDB Class Manager and application scopes, and I'm curious if others have faced something similar.
Use case:
- We have users with the CMDB Admin role who manage CI classes and attributes.
- A particular CI class and/or attribute definition was created in a custom application scope.
- When a CMDB Admin is working in CI Class Manager, they need to update the conditions of a Health Inclusion Rule associated with that CI class.
- When they look for the fields in that particular CI Class they cannot find the fields in conditional builder because the CI class is in a custom scope. It does not notify or give any sort of message saying this is in a different scope. As an Admin, we can see the info message saying this record is in different scope....
Please let me know if anyone has workaround for it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 hours ago
If it's from a custom application that comes with a user/admin role you probably need to include the role to cmbd admin.
CSA | CAD | DF | DISCO | ITIL4
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 hours ago
@skuvvakulli the custom class which u have created in another scope must have a custom role created as well. Pls assign the custom read role of the class to the CMDB admins to help them see the fields.
The behaviour which u are observing is OOTB behaviour, because at the time of creating any table,servicenow ootb creates 4 custom roles with it. So unless you are an admin u won't be seeing that.
Thanks,
Danish