In a workspace a record still shows older ‘policy statement’ language while docs say ‘control objective.’ What should implementers focus on architecturally?
Select an answer to reveal the explanation.
Short Explanation
Names on the jar change; the jam’s job does not. Whether the UI says policy statement or control objective, the architectural role is the reusable requirement in the chain. Focus on that role, not the sticker.
Full Explanation
ServiceNow IRM labeling evolved in many workspaces from policy statement toward control objective. The architectural role remains the reusable definition linking obligations to generated controls. Implementers should configure and explain the object by that chain role. Label drift is not a second parallel content model and does not mean the feature is deprecated.