Hi Barra,

This behavior changed over time, and the shortest string of information about behavior is the full version number (which is missing unfortunately in your description). Language is an important factor here as well... so even on a frozen baseline, you can still adapt translations as long as you are not adapting the source language... and in turn your user probably needs Administrator role to bypass checks... so yes the API is leading, and Publication Manager fully relies on the public API (but sometimes does extra "User eXperience" checks.

Best wishes,
Dave

Hi Dave, thanks for the reply. To clarify, yes I mean I can change the contents of a version of an object in a frozen baseline, not the version selection. I guess that explains it then if a frozen baseline essentially prevents changes to the version selections, but content changes are allowed. I can't say I find the rules clear though across user and API documentation, and Pub Manager and API behavior, and in particular the API errors when they state that a 'frozen baseline' is what's preventing changes at version level.

thanks,
Barra

Hi Dave, thanks for the reply. To clarify, yes I mean I can change the contents of a version of an object in a frozen baseline, not the version selection. I guess that explains it then if a frozen baseline essentially prevents changes to the version selections, but content changes are allowed. I can't say I find the rules clear though across user and API documentation, and Pub Manager and API behavior, and in particular the API errors when they state that a 'frozen baseline' is what's preventing changes at version level.

thanks,
Barra