@rk39193348 Are you able to publish the page manually? The code that you shared seems ok.

@kushal_srivastava I don't think there is anything such OOTB. I suggest to create a custom component(if content is authorable). Use Intersection Observer to show the content on scroll. Below is API documentation.https://developer.mozilla.org/en-US/docs/Web/API/Intersection_Observer_API 

Welcome 

@Shaheena_Sheikh It is not like we are creating option nodes from Javascript. AEM will read the dialog nodes and will generate HTML markup from backend and also Javascript APIs provided to generate it from the frontend. You just need a parent node that should be coming from backend, we can inject op...

Because of repository restricting in 6.5. Check link https://experienceleague.adobe.com/docs/experience-manager-64/developing/extending-aem/extending-workflows/workflows-best-practices.html?lang=en#customization

@aembeginner1 You can update the OOTB DAM UPDATE ASSET workflow and add you custom thumbnail size.Tools > Work Flow > Models > DAM Update Asset > Select > Edit > Process Thumbnails > Thumbnails Tab > Add > 640:640:false > submit > syncNow go to /conf/global/settings/workflow/models/dam/update_asset/...

Try one thing, put a console.log in for loop and see what all options are injecting, only new or old + new

Should clear options before injecting, check optionItems.clear(); is added in your script.

@Shaheena_SheikhAre you calling that change function in dialog load as well?$(".cq-dialog").find("#country").on("change", setCitiesOptions); // Onchane Event setCitiesOptions(); // Call the set options function on dialog load If now calling setOptions function onload, try calling it. 

@bmohanty I can see the side panel.