What are the jcr:frozenNode and nt:frozenNode in the CRX repository? And versioning error during replication in Workflow

[avni27]

Hi Team,

I want to understand jcr:frozenNode or nt:frozenNode better in the CRX repository. I couldn't understand very well from the content available on the web.

Issue - There is a step in custom workflow to replicate one content is approved, Does the version information go along with the replicated page data to different environment? I think it should but it does not get updated in our use case which might be an issue.

[MayurSatav · Accepted solution]

Hi @avni27 ,

In AEM, jcr:frozenNode of type nt:frozenNode is used to store a snapshot of a node when a version is created. This node contains all properties and child nodes as they were at the time of versioning.

You can find these under /jcr:system/jcr:versionStorage in the CRX repository.

Regarding replication  when you replicate a page in AEM, only the current state of the node is sent to the publish environment, not its version history or jcr:versionStorage. This means the version information  including jcr:frozenNode does not get replicated by default. If you need version history on publish, you would need a custom solution.

[avni27]

Thank you @MayurSatav , We will work on creating something for version management between environments.