コミュニティアチーブメントバーを展開する。

SantoshSai
SantoshSai
オンライン
タイプ
  • すべて
  • 質問
  • ディスカッション
  • アイデア
  • ブログ
ユーザー投稿による絞り込み
  • I would suggest: Use IAM Role with Web Identity (Recommended) Use AWS STS (AssumeRoleWithWebIdentity) to get temporary credentials securely. No hardcoded credentials in AEM. Use Environment Variables / Secrets Manager Store role ARN and config securely. Never embed secrets in code. Least Pr...

    タイプ

    質問

    表示

    307

    いいね!

    1

    返信

    0
  • Hi @VGKrish, Could you verify if the persisted query is published? Go to CRXDE and check if replicated: /conf/project123/settings/graphql/persistentQueries/productdata  Also, Verify that the GraphQL endpoint is accessible on Publish - Make sure you're using the correct endpoint on the Publish instan...

    タイプ

    質問

    表示

    157

    いいね!

    0

    返信

    0
  • Hi @SureshVadapalli, Could you pass the JUnit here to better understand you resolve your query?Try this: { "jcr:primaryType": "dam:Asset", "jcr:content": { "jcr:primaryType": "dam:AssetContent", "data": { "jcr:primaryType": "nt:resource" }, "metadata": { "jcr:primaryT...

    タイプ

    質問

    表示

    160

    いいね!

    1

    返信

    0
  • Hi @jakebowers, In Experience Fragments, it looks like Sling model adaptation resolves again to your CorporatePageImpl (possibly due to the resource type resolution in the XF context), creating an infinite loop until a null delegate is hit. Try adding a guard to prevent self-delegation and see if it...

    タイプ

    質問

    表示

    188

    いいね!

    1

    返信

    1
  • 1. Yes, the Groovy Console is part of ACS AEM Commons, not a standalone feature of AEM itself. When I mentioned "Groovy script via ACS AEM Commons", I meant running scripts using the Groovy Console provided by the ACS AEM Commons package. 2. Yes, to make querying on dam:failedRenditions performant, ...

    タイプ

    質問

    表示

    287

    いいね!

    2

    返信

    0
  • IMO, hiding or truncating the parent tag levels (like the tag category) requires deeper customization - particularly in how tags are rendered in: Content Hub Metadata forms Search interfaces or custom UIs Here is what you can do: Customize tag display in UI componentsIn your custom metadata sch...

    タイプ

    質問

    表示

    237

    いいね!

    0

    返信

    1
  • Hi @dmescia2, I don't think AEM does support true nested namespaces in the tagging system. As tags live under the JCR path: /content/cq:tags and each namespace is just a first-level node under that path, and AEM only recognizes this top-level node as the namespace. For example: /content/cq:tags/myco...

    タイプ

    質問

    表示

    272

    いいね!

    0

    返信

    3
  • Hi @PriyankaKh4, Try this: SELECT * FROM [cq:Page] AS p WHERE ISDESCENDANTNODE(p, '/content/ohip') AEM stores content and how JCR primary types work. Nodes like /content/ohip/home may appear as folders/pages, but their primary types are often nt:unstructured, not sling:Folder or cq:Page. If you’r...

    タイプ

    質問

    表示

    290

    いいね!

    1

    返信

    0
  • Hi @webera, The problem is you're using an XPath-like query to find assets where any dam:failedRenditions/*/reason != RenditionFormatUnsupported. This can be expensive because: dam:failedRenditions is a child node with nested properties, which makes this a deep tree traversal. The repository has t...

    タイプ

    質問

    表示

    328

    いいね!

    1

    返信

    2
  • Hi @narendragandhi, I recently created a new AEM project using AEM Maven Archetype 54, and as part of exploring SlingInternalRequest, I tried integrating it into the core bundle following the examples you referenced above. However, after including the dependency and importing the internal package, I...

    タイプ

    質問

    表示

    239

    いいね!

    1

    返信

    0