Service Operation Workspace Vs native/Platform View

[AKM1]

Hi, our instance upgraded to Washington with the latest patch, so we decided to use service operation workspaces instead of platform view or native view, but what we found challenging is that there are lots of differences between the default view and SOW (service operation work space). Here,  we have to use the same code for both. So to avoid cutomization and to avoid touching existing code, can we configure the same configurations for the service operation workspace, similar to the native/platform view?

[Simon Hendery]

Hi @AKM1 - yes you can!

SOW is highly configurable using UI Builder:

https://docs.servicenow.com/bundle/washingtondc-it-service-management/page/product/service-operation...

[AKM1]

Hi @Simon Hendery thanks for the reply,  but why existing code is only  supporting to platform view, it should support to service operation workspace space too, correct?

[James Hardy]

Workspaces do not support like 90% of client side code. You will end up having to use the nightmare drag and drop UI builder, or server side hacks. Don't use them. They will create technical debt and make future development take twice as long; as you will need things to work in both environments, and inevitably will have to maintain 2 seperate customizations. The organization I work with has decided to not support any customizations to workspaces. They are gimmicky low code sales tricks that make our lives as developers absolute H***. Native platform can do everything you need.