Hi @PriyaNair1,Try changing the first line where you fetch the tags like this: def existingTags = modifiable.get("cq:tags") as List ?: [] That should handle cases where cq:tags is already a list. Hope that helps!

Hi @Sku4, Have you tried using ModelFactory.canCreateFromAdaptable() and cast to SlingModel interface? Refer below example where I have tried to modify your code: package com.project.core.models; import com.fasterxml.jackson.annotation.JsonProperty; import org.apache.sling.api.resource.Resource; im...

@ViaVu - That's right!

Hi @georhe6, Given that the business team previously used Salesforce forms directly without any backend integration and the form submissions were handled entirely by Salesforce, the most appropriate and straightforward approach in AEM would be to use the Embed component to include the Salesforce for...

Hi @sai_charanAr, Please refer to the similar question here: https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/sling-dynamic-include-on-aem-cloud/td-p/750977ACS Commons SDI - it  does not fully worked in AEM as a Cloud Service because in AEMaaCS, you don’t have direct Dispatc...

Hi @VijayRa10, Try this { "definitions": [ { "title": "Tabs", "id": "tabs", "plugins": { "xwalk": { "page": { "resourceType": "core/franklin/components/block/v1/block", "template": { "name": "Tabs", "model"...

Hi @VishnuRe3, Yeah, Netcentric ACL Tool doesn't support conditional rule evaluation based on node properties like jcr:content/visibility. It's limited to path- and node-type-based rules. If metadata-based filtering is critical for folders, here are a few approaches that come to mind at the moment: ...

Hi @MatthewDa19, I think you missed adding Jackson exporter annotations on the nested model (AuthorModel) @Exporter(name = "jackson", extensions = "json") Nested models need the @Exporter annotation because Sling’s Jackson exporter only serializes models explicitly registered for export. Without it...

@ViaVu  To conditionally display or hide tabs in the Page Properties dialog based on the page template, follow these steps:​ Overlay the Dialog: Navigate to your editable template's structure and overlay the cq:dialog node if it doesn't already exist. This is typically located at: /conf/<your-site>...

Hi @ViaVu, Recommended Approach to Hide Tabs for specific page templates, use the editable templates framework and override the page properties dialog only under the template structure - this ensures the changes apply only to selected templates and are safe for upgrades. You can also use a granite:r...