Function userID is not allowed in scope sn_cmdb_ws Error display on workspace
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-17-2024 10:10 AM
I have created widget on workspace , but when one error is displayed on workspace and it is displayed on interaction table also
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-30-2024 03:14 PM
I am seeing this error just by going to the Data Manager in the CMDB Workspace and clicking on the Data Filter tab. (I did successfully import policies first, then tried to view a few of them - both published and draft policies are doing this). You have to navigate back to home on the top breadcrumb after you dismiss the error for it to come back.
Also, I am not seeing a way to execute a policy manually in the CMDB Data Manager workspace. Used to be a UI action in the Data Certification plugin...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-16-2024 02:20 PM
I am also seeing this error in the same locations as you @Asha Pathak and @rkolosky. We're on Washington DC release patch 4 and have all CMDB plugins up to date. I'm also seeing another one when attempting to create a Retire policy. Anyone also seeing the definitions error as well?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-31-2024 08:00 PM - edited 07-31-2024 08:09 PM
Greetings!
I'm facing the same error, but in a custom Application, so it's a custom Workspace. It's intermittent and sometimes also appears in Next Experience interface... 😕
I thought it could be related to the UI Builder, since it has caused errors before, but even after Cloning we keep getting this error message. Our CMDB workspace is inactive at the moment.
Any clues, tips, ideas, will be very appreciated!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-21-2024 12:30 PM
Greetings!
The solution to this cenario is to update 3 ACLs from On-Call User Contact Preference [on_call_user_contact_preference] and more 3 ACLs from On-Call User Preference [on_call_user_preference].
The ACLs are like these:
1) Type: record
Operation: delete
Fields options: None
2) Type: record
Operation: read
Fields options: None
3) Type: record
Operation: write
Fields options: None
One of those ACLs causing the error messages:
The code should be updated to this:
You must have the security_admin role to edit the ACLs. A definitive solution will be provided in Xanadu version.
I hope this can help others with the same issue.