Workspace UX labels objects as entities while classic tables still use older profile-oriented names. When designing architecture for a city IRM rollout, what should the answer emphasize?
Select an answer to reveal the explanation.
Short Explanation
Don’t get hypnotized by the chrome. Workspace says “entity,” some tables still whisper “profile,” but the framework still joins policies and risks to the same governable objects. Design for that common behavior, not for whichever label is painted on the screen today.
Full Explanation
ServiceNow IRM evolved naming from profile-centric classic GRC toward entity language in workspaces, while some table names retain legacy terms. Architecture decisions should focus on shared framework behavior—scoping, generation, hierarchy, and relationships—rather than treating UI labels or historical table names as different products. Understanding label drift prevents false redesigns and supports accurate configuration.