Why isn't CAB Workbench Next Experience

NT
Kilo Contributor

At Knowledge, I lost count of how many times I heard about the Next Experience and how they had gone through every single aspect of the platform to tune it up to work great in the new look.

Now, I'm subscribed. Ignoring that it was more about the necessity of moving to a modern UI and supported framework, I'm supportive. I like it. It's a big improvement. And I say that as a user and to stop people saying that 'the ticketing tool you think is good for broad enterprise use' still looks terrible.

But...Why is CAB Workbench, something very visible to business users, NOT updated? Did they forget or do I need to set a parameter somewhere? It's always been ugly as it doesn't follow branding so I'm hoping this is my mistake and someone will tell me how to make it look "Next"!

2 REPLIES 2

Ashley Snyder
ServiceNow Employee
ServiceNow Employee

The Service Operations Workspace release in San Diego was originally released to have parity to with ITSM Agent Workspace so that product can be eventually sunset. Each product team is building their new interfaces on the Next Experience UI Framework, but the Next Experience team is not responsible for which features products choose to release on the framework or for their roadmap. You may have better luck reaching out in the ITSM forum or checking the Idea Portal to see if communication on that feature has been released.

NT
Kilo Contributor

Thank you - I guess it'll just take a little time before all interfaces are updated or replaced. I was just checking that 'enabling Next Experience' is a truly global switch and that I didn't need to do it on a per product basis in some cases.