remove/restrict Next UI view from platform for AGENTS only SOW view

[vinnus]

remove/restrict Next UI view from SMT platform for ALL SMT AGENTS. The goal is to ensure that SOW view becomes the primary interface for all SMT users/agents, streamlining user experience and reducing confusion.

1.platform offers both Next UI & SOW UI that sometimes leads to confusion among users & requires double maintenance efforts by the Technical Team.

Restricting Menu modules on ALL Menu so that NO SMT Agent can access Native view and have to focus only on Modules on SOW Menu.

• only admins/super users should be able to access the ALL Menu modules.

[Peter Bodelier]

Hi @vinnus,

You could use Navigation Handlers for this. (sys_navigator)
For example; if an incident record is opened in the native UI, you can redirect non-admins on the fly to that incident in workspace.

Choose the table for which you want to restrict the backend view, and do your logic in the script.

For example:

(function() {

var sysId = g_request.getParameter('sys_id');
if (!gs.nil(sysId) && !gs.getUser().hasRole('admin')){

return '/now/sow/record/' + current.getTableName() + '/' + sysId;
}
return '';
})();

[vinnus]

Hi Peter,

we need to remove ALL  menu completely so that specific user groups have only sow view only admins and power users can see the  ALL  menu 

[Peter Bodelier]

You can do that by adding a role to each and every module, but to be honest... good luck maintaining that.

By using the solution I offered, you can leave the modules alone, and just make sure your users are dynamically redirected to the workspace.

In my example I used a record, however you could do the same for list views as well.

[vinnus]

Thanks Peter.

Can we redirect  list option like "Portal" that can redirect to service portal page in SOW