Can someone explain HCM Actions

Experience Manager (PaaS/OnPrem)
1

Hi all,

I’m experiencing some unexpected behavior when working with HCM Actions in Bloomreach Experience Manager (BrXM). Specifically, I’ve set up my hcm-actions.yaml file to reload certain node paths, and while the nodes themselves seem to reload correctly, the actual files under these node paths are not being reloaded as expected. I have referenced the documentation here, Manage Content - Bloomreach Experience Manager (PaaS/Self-Hosted) - The Fast and Flexible Headless CMS.

Details:

  • The hcm-actions.yaml file is configured to reload paths like this:
action-lists:
  - 1.0:
      /content/documents/my-site/config: reload
      /content/gallery/my-site/assets: reload
  • After deployment, I see that the node paths defined under content/documents/my-site/config and content/gallery/my-site/assets are indeed reloaded, but the files (documents or assets) under those nodes do not seem to reflect the latest changes.
  • The files are properly checked into the code repository, and I expected them to be picked up by the reload action.

What I’ve Tried:

  • Verified that the files are correctly placed in the repository and have the right permissions.
  • Ensured the hcm-actions.yaml is properly formatted, and the paths match what I expect in the JCR repository.
  • I’ve also checked if the files are getting reloaded in a staging or development environment, and the behavior is consistent.

Question:

Is there something specific I might be missing in terms of how HCM handles the reloading of files under node paths? Do I need to define a different action for files to be reloaded, or is there a common issue that could be causing this behavior?

Any guidance or troubleshooting steps would be greatly appreciated!

2

HI,

reload actions reload from the content definition, which is the file included in the dist. I would check to make sure the file you are deploying is the changed version. Check the actual file in the distribution.

Actions are versioned. If you’ve done a 1.0 reload once before you will need to do a 1.1 reload or some higher number.

3

Hey @jasper.floor - sorry for not responding. You sparked something for me with your reply. I was seeing weird behavior due to me being lazy, I suspect.

I was creating the entries pointing at the folder containing the things I wanted to be reloaded/deleted. I was expecting that all children under those folders would also be reloaded. This was not the case. I had to also include an entry for the children.

So as an example, which worked for us, is below.

action-lists:
  - 2:
      /content/documents/a/folder-name: reload
      /content/documents/a/folder-name/footer: reload
      /content/documents/a/folder-name/header: reload

folder-name would be created and then the resource-bundle(footer) and value list (header) file would be created. The above is just to help with the visualization.

2 Likes
4

Hi @mkjp2011 ,

We are happy you are part of Bloomreach Developer’s Community.
Thank you for reaching out to us.
We hope we have answered your queries and therefore marking this thread for Closure.
Looking forward to your continuous contribution towards our vibrant Bloomreach Community.

Thank you