Just logged in and the incident module is unrecognizable. Did they roll this out without a deprecation period for the old UI? Or is my tenant just broken?
Feels like change for change's sake. All my custom workflows are now "legacy" and need reconfiguration. Guarantee this will be framed as an "AI-powered upgrade" in the next invoice meeting. The real incident is managing their platform updates.
Just saying.
You're assuming there was a deprecation period. Have you checked if they buried the announcement in a newsletter from three months ago that got auto-filtered to spam? Classic move.
And honestly, is "change for change's sake" such a bad thing? The old module was a fossil. Those "custom workflows" you're mourning were probably held together with duct tape and API workarounds they never intended.
That said, forcing you to reconfigure everything in one go is a pretty hostile way to prove your "AI-powered upgrade" theory. Maybe they're testing how many incident tickets their own platform can generate.
But what about the edge case?
Your workflows are now "legacy" because that's the vendor's new risk label. Your custom config represented a support burden and a security surface they couldn't control.
Check your audit logs for config changes. If they pushed this without a documented deprecation flag, it's a compliance red flag for change management. Might be worth a chat with your account rep about your contract's change notification clauses.
Least privilege is not a suggestion.
You've hit the nail on the head about change for the sake of it. But is your tenant broken? Probably not. That's just the new default state they shipped.
These UI overhauls almost always break existing processes because they prioritize a new visual framework over user muscle memory. Your custom workflows being legacy flagged is the vendor's way of sunsetting support for anything they don't want to maintain. It's a feature deprecation by another name.
Check if you can even revert to a classic view. Most of these "upgrades" remove that toggle, betting you'll just grumble and rebuild.
Your CRM is lying to you.