I logged in this morning to document a minor privacy incident and the interface for the Incident Management module is completely different. The navigation, data entry forms, and even some core field labels appear to have been reconfigured without any prior communication from our account team.
My initial observations on the changes:
* The workflow progression is now represented horizontally instead of vertically, which alters our team's visual cue for incident stage.
* Several fields we customized for our GDPR breach reporting requirements (like "Data Subject Nationality" and "Likely Risk Threshold") have been moved to a secondary "Advanced" tab.
* The method for linking related incidents (a key part of our root cause analysis) seems to have changed from a direct searchable list to a manual ID entry.
I am primarily concerned with how this impacts our controlled procedures. Our SOX and HIPAA compliance narratives specifically reference the OneTrust interface paths for evidence collection. A sudden change like this could disrupt our audit readiness if our process documentation is now out of sync.
Has anyone else encountered this update? I'm trying to determine:
* If this is a staged rollout or a global platform update.
* Whether any configuration was lost or migrated incorrectly, particularly for custom dropdown values.
* How you are handling the necessary updates to internal process documentation and control narratives.
I am currently comparing screenshots against our last quarterly review package to catalog the specific discrepancies.
Ah, the classic stealth rollout. I've seen this movie before with a different CRM vendor last year. Your point about audit readiness is the real kicker, and it's often overlooked in these "exciting new interface" announcements they'll inevitably send next week.
The horizontal workflow is almost certainly about making it look better on a mobile dashboard for leadership, but it destroys the muscle memory for your actual ops team. When they moved our custom fields to an "Advanced" tab in a previous system, the compliance team's data capture completion rate dropped by about 30% for two months because people just didn't scroll. Manual ID entry for related incidents is a regression, full stop. It introduces human error into a process that's supposed to eliminate it.
Check your contract's change management clause. Sometimes there's language about "material changes to functionality" requiring notice. Moving custom fields you paid for into a secondary tab might qualify. It's a long shot, but it's gotten a vendor to concede free training credits for my team in the past.
That compliance team data capture drop is a chilling statistic, and exactly the kind of unintended consequence I worry about. When a key field gets buried, you're not just changing a screen, you're altering a business process and the integrity of your dataset. It makes me wonder if the 30% drop was ever fully recovered, or if that just became the new, lower baseline for data quality.
Your point about the contract clause is really smart, and something I wouldn't have considered. It seems like "material change" could be argued both ways: is it material if the field is still *there* technically, just harder to find? I'll have to pull out our agreement. Beyond training credits, would pushing for a temporary rollback on specific features ever be a realistic ask, or is that usually a non-starter once a vendor has flipped the switch?