Hi @PrakashBa2, Try below options whichever you think is best suitable according to your case   Option 1: Switch to RESOURCE_RESOLVER_MOCK Instead of JCR_MOCK, use: public final AemContext context = new AemContext(ResourceResolverType.RESOURCERESOLVER_MOCK); This is faster, more isolated, and doesn'...

Hi @PrakashBa2, Your test cases are failing due to incompatible or outdated test dependencies after moving to AEM 6.5 LTS. Try below steps steps to fix it Update test dependencies in your pom.xml: <dependency> <groupId>org.apache.sling</groupId> <artifactId>org.apache.sling.testing.sling-mock....

Hi @tushaar_srivastava, Let's understand your query by breaking it down: SELECT * FROM [nt:base]: This fetches all node types extending from nt:base, which includes all nodes in the JCR repository. WHERE [jcr:uuid] = $id: This filters nodes by their universally unique identifier (jcr:uuid). $id is...

Hi @NavyaVo, You can give this a try -  adding a few practical ways to manage this as below: 1. Use AEM page permissions to restrict replication AEM controls the visibility of the "Publish" buttons based on replicate permissions. Steps: Navigate to /content in Useradmin or CRXDE Lite. Deny the rep...

Hi @olsalas711, It should be EDS, based on Fastly - can strip or rewrite headers, block certain request types, or enforce rules (especially on POST) that differ from your AEM Publish instance. 403 Forbidden in this context usually means: A header or body modification by EDS is triggering security f...

Hi @OmarKh3, The query looks fine to me, but if you're getting empty or null values for relatedArticles, it's probably one of two things: No content has been linked yet.Even though the field exists in the model, if no related content fragments are actually selected in the authoring UI, the GraphQL ...

@ViaVu  Preview Tab Can’t Be Hidden Preview Tab is Injected Dynamically by the Editor FrameworkThe "Preview" tab isn't a typical child node under /libs or /apps like other page properties tabs. Instead, it's dynamically injected by the Page Editor Shell based on the editor context in AEMaaCS. That’...

Hi @Abbirami, 1. Grant Access to Audit Log Nodes I think Audit logs are stored under: /var/audit Permissions needed on /var/audit: jcr:read – Allows reading audit log entries. You can assign this via user/group permissions. 2. Grant Access to the Audit Log Report Tool The tool lives under: /apps/a...

Hi @Prashardan, This sounds like a very useful feature to improve the management of assets within AEM Assets (You could add this into the Idea's section of the community), especially when dealing with expiration dates. Below, I could share a few possible ways to approach this, leveraging AEM’s capab...

Hi @narendiran_ravi, I agree with @narendiran_ravi's suggestion that there is no out-of-the-box solution for dynamically setting a value in the CA editor, especially when the value needs to be generated dynamically and doesn't fit well into a predefined set. At the moment, these are the things comin...