Well, not exactly. Some CDN configurations can be controlled by developers and deployed to AEMaaCS using a Config pipeline. Please check the following docs and examples to see what is possible to configure: https://adapt.to/2024/schedule/configurability-of-cdn-in-aem-cloud-servicehttps://experiencel...

Hi @RanjithR1, did you create a farm file in the Dispatcher configuration with example.com domain listed under /virtualhosts? Check the Dispatcher logs to make sure your request is hitting the correct farm. Something seems to be misconfigured on your end, as we use Akamai and the same approach of pa...

Hi @AMahdzich_Bayer, if that is the case, it sure sounds like a bug. Please report the issue to Adobe Support.   Daniel

Hi @AMahdzich_Bayer, yes, but there is also no API to delete CFs in build, AFAIK. So you would need to: Call the "List all Content Fragments" to get all CF IDs Then loop through them and for each CF: Call the "Get a Content Fragment" to get the Etag valueCall the "Delete a Content Fragment" with CF ...

Hi @AMahdzich_Bayer,   correct, sorry, get the Etag value from the response headers.   Good luck, Daniel

@AMahdzich_Bayer, I think you are just using the wrong ETag value in your request. Try to use the ETag value in the If-Match that you received in the response that failed with the precondition error. c647d94c-a91d-4be5-87a6-e52154f9c365   BR, Daniel

@Mahesh_Gunaje also check this https://medium.com/tech-learnings/aem-cloud-service-composite-multifield-in-content-fragments-editor-new-editor-8021bf11f8b6 just be careful now to use any reference fields in the custom MF, as those might create other problems for AEM Editors when they move/rollout co...

Do not mock the Resource Resolver yourself; the mocks from AEM Mocks work great. Use org.apache.sling.testing.resourceresolver.MockResourceResolverFactory.   Good luck, Daniel

Hi @Mahesh_Gunaje, check https://meticulous.digital/blog/f/migration-to-the-new-content-fragment-editor-in-aemaacs there is a section on "Nested Multifield" and why I would discourage developers from using those.   Good luck, Daniel