- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-01-2023 04:48 AM
Hi all,
Can you please suggest a possible reason why a user may not be able to view a Catalog item in SOW? I clicked on the Create Request button from the Incident in SOW form.
A user has itil role and workspace_user.
Thank you!
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-01-2023 07:20 AM
Thank you so much!
I have the 'swp' portal. And found that the sw_sc_cat_item had User Criterian in the Can View related list. So I removed it and now everything is working properly.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-01-2023 05:03 AM
Hi @Nadia7 ,
Please refer to the doc: https://docs.servicenow.com/bundle/utah-it-service-management/page/product/service-operations-worksp...

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-01-2023 06:18 AM
That is the Service Portal 404 page, and SOW uses an iframe to call a specific service portal (I think it's swp) it uses to handle the catalog. Your screenshot makes me think it doesn't exist in your instance. I would make sure you've installed this app and make sure the Service Portal with the url suffix "swp" exists in your instance. If you've confirmed those things and still getting the 404 you might need to open a support ticket.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-01-2023 07:20 AM
Thank you so much!
I have the 'swp' portal. And found that the sw_sc_cat_item had User Criterian in the Can View related list. So I removed it and now everything is working properly.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-14-2023 09:26 AM
I didn't see any User criteria blocking access myself, but you can see the Roles field has the "workspace_user" in it - I found my users didn't have this role and that was causing the 404.
I had set up a view from the Asset Management Workspace for stuff like the Hardware Inventory Stock Order request for inventory_user users, and they were getting a 404.