- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-28-2024 08:19 AM
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-28-2024 11:38 PM
The article I referred to contains some points on what's missing when working with workspaces, such as a limited support for the Service Catalog.
You can use those pointers as a starting point for listing your pros and cons.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-28-2024 10:08 AM - edited 01-28-2024 10:13 AM
Hi,
Although it's technically possible (most parts at least) it's still not recommended.
Some parts of Workspaces cannot be done, or have very limited support compared to ServicePortal/Employee center.
For reference:
https://www.servicenow.com/community/next-experience-articles/ui-builder-and-service-portal/ta-p/237...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-28-2024 11:04 AM - edited 01-28-2024 11:05 AM
Thanks @OlaN . I agree it is generally a good idea to go with prebuilt. But WS look good and seem to be easy to set up, not sure what we are missing by using them vs ESC.
So trying to define detailed pros and cons
PS thank you for the article, useful.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-28-2024 11:38 PM
The article I referred to contains some points on what's missing when working with workspaces, such as a limited support for the Service Catalog.
You can use those pointers as a starting point for listing your pros and cons.