We want remove Next UI from all environments , so that SOW view is used primarily.

[vinnus]

The technical feasibility of removing the Next UI view.

The potential dependencies/risks and impacts on existing functionality.

Is it possible all useful features present on Next UI can we make sure all are present/absorbed on SOW?

Can we completely Next UI being decommissioned?

[Mark Manders]

What are you asking? SOW is Next Experience. What is your business case? What are you trying to achieve and most importantly: WHY??

[vinnus]

Hi Mark,

We have Scoped application and we are implemented Agent workspace in our application for the users for better UI experience with limited and basic configurations Like case, task and service task tables to handle the users their assigned cases and tasks.

Now the requirement is 

Is it possible all useful features present on Native UI can we make sure all are present/absorbed on Agent workspace?

The potential dependencies/risks and impacts on existing functionalities of all useful modules in Native view to build in Agent workspace

Can we completely Native being decommissioned and only agent workspace will available for the users.

Thanks for the response  

[Mark Manders]

Still not very clear what you are asking. What features are you talking about? What modules are you talking about? 

If you are talking about 'all', 'favorites', etc: no. Workspace is a view of the instance. Those items are menus. Yes, you can remove them and you will have an instance that won't function anymore, because no one can reach the tables anymore. And you will be creating huge technical debt. Upgrading will become your worst nightmare.

[vinnus]

If you are talking about 'all', 'favorites', etc,  "Yes" can we configure all of them in Workspace is a view  and is it feasible to do so and not meant to remove everything can we restrict the Native view for the users and they can only see Workspace view.