Rename/Update value in AEM Tag console

[ShashankJa1]

If I rename a tag value in the AEM Tag Console in AEM Cloud, and the original tag value has been referenced in pages and content fragments:

1) Does the value get automatically updated in the referenced pages and content fragments?
2) Is there a need to republish the pages, or does AEM take care of it?
3) If it republishes automatically, how can we ensure that only live pages get published and not the pages in the draft mode?

Thanks,

Shashank

[SwetaB]

Hi @ShashankJa1 ,

When a tag is renamed or moved a new tag is created and in the new tag cq:backlinks property gets added which points to the old tag and in the old tag cq:movedTo gets added pointing to the new tag node.

1- This helps in resolving the tag references and it gets automatically updated in all pages.

2- once tag is renamed and published it will update in the published pages without the need to publish the page.

[partyush]

Hi @ShashankJa1 

Yes, when you rename a tag in the AEM Tag Console, AEM maintains a reference to the tag by its ID (namespace:path), not the display name or value.
1. Does the value get automatically updated in the referenced pages and content fragments ?.

Yes, but with context:

• What happens technically? Tags are stored by their tag ID (namespace:tag-name) in content (pages, fragments, assets).

• When you rename a tag in the Tag Console, AEM only changes the title property of the tag node, not the ID or path.

• So, display names are updated automatically (ID stays same).

2. Is there a need to republish the pages, or does AEM take care of it ?.

Yes, you need to republish. AEM does NOT do this automatically.

• Even though the display label changes in Author, the corresponding publish instance won't reflect the new label until the content that uses the tag is republished.

• This is because AEM does not automatically trigger replication for dependent content when a tag is renamed. This avoids unintentional publishing of pages (especially in workflows or drafts).

• So, yes. Pages/fragments must be manually republished.

3. If it republishes automatically, how can we ensure that only live pages get published and not the pages in the draft mode?
AEM does NOT auto-republish, so you’re in control of what gets published.

To selectively republish only live pages, Use workflows and Filter by cq:lastReplicationAction == Activate to get only live content.

Thanks

Partyush

[Sid_Gour · Accepted solution]

Hi @ShashankJa1 ,

It is recommended that Authors only be allowed to edit the tag's title or description.However when there is need for clean up the Tagging Taxonomy by moving the tag to new location or renaming it, then we can use Move option in tagging console.

1) Does the value get automatically updated in the referenced pages and content fragments?

- Yes, all the pages/CF gets automatically updated with new tag value which author can see immediately on the pages/CFs. But behind the scene, when tag is moved/renamed, actual orgial tag node will remain in the same location(in JCR) but cq:movedTo property will be added to the node with new location value and at the sametime copy of the node will be moved to new location. This node will have the property cq:backlinks[] which will be pointing to original location of the tag node. On Tagging console, you would see that moved tag in new location

If you observe the cq:tags on page/CF which would be pointing to your original tag node location only. There won't be any change in properties.
2) Is there a need to republish the pages, or does AEM take care of it?

- No need to publish the pages. You just need to publish the moved/renamed tags alone.
3) If it republishes automatically, how can we ensure that only live pages get published and not the pages in the draft mode?

- As it won't publish the page. You need not to worry about draft versions. 

Thanks,

[kautuk_sahni]

@ShashankJa1 Did you find the suggestions helpful? If you need more information, please let us know. If a response resolved your issue, kindly mark it as correct to help others in the future. Alternatively, if you discovered a solution on your own, we'd appreciate it if you could share it with the community. Thank you !