Publish Experience fragments using publish content tree process | Community
Skip to main content
Level 2
August 12, 2024

Publish Experience fragments using publish content tree process

  • August 12, 2024
  • 2 replies
  • 1009 views

In Aemascs dev environment (2024.07 version), I have created a custom workflow using publish content tree step. Now I am facing issues when publish the experience fragment using the workflow.

Scenario:

1. create a new experience fragment. Select the parent folder, publish the XF using the custom workflow.  Now parent and master node both are publishing

2. After adding some content, select the parent, publish the XF. Now the parent only published.  master node is deleted in publish environment.

 

 

I am not able to replicate this issue in my local. In error log, nothing is printed related 

Could any one help me to resolve this issue. 

 

Thanks

Kamaraj

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

2 replies

TarunKumar
Community Advisor
Community Advisor
August 12, 2024

HI @kamaraj_aem ,

Check the additional parameters in the Arguments field in the process tab. Look for the arguments that you have provided there in your custom workflow. For example:

enableVersion=true,agentId=publish,includeChildren=true,filters=onlyModified

 

You can try to add "filter" argument 

  • filters (string value, default means that all paths are activated). Available values are:

    • onlyActivated - only activate pages that have (already) been activated. Acts as a form of reactivation.
    • onlyModified - activate only paths which are already activated and have a modification date later than the activation date.
    • The above can be ORed with a pipe “|”. For example, onlyActivated|onlyModified.

 

For more details please follow this link:

https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/operations/replication#publish-content-tree-workflow

 

-Tarun

Level 2
August 12, 2024

Thanks for your reply @tarunkumar.

These parameters will help to publish child nodes.

But my worry is that why it is deleting the master node if I publish again.

TarunKumar
Community Advisor
Community Advisor
August 13, 2024

Hi @kamaraj_aem ,

Can you test this in any other environment and also double check your custom workflow process steps.

kautuk_sahni
Community Manager
Community Manager
August 21, 2024

@kamaraj_aem Did you find the suggestions from users helpful? Please let us know if you require more information. Otherwise, please mark the answer as correct for posterity. If you've discovered a solution yourself, we would appreciate it if you could share it with the community. Thank you!

Kautuk Sahni