Is this working locally?

Hi,   You simply need to publish/activate the asset to make it publicly accessible through your domain. For example, if you have an asset under /content/dam/myasset.jpg, after publishing it, you should be able to access it at https://yourdomain.com/content/dam/myasset.jpg. Just be mindful that some ...

Hi, Is there any update made to the other 'DAM Update Asset' model that could potentially hit any of these limitations? https://adobe-consulting-services.github.io/acs-aem-commons/features/synthetic-workflow/index.html#supported-workflow-features. Are you seeing any errors in the logs? Have you trie...

Hi,    This is not an easy requirement to fulfill because it goes against the nature of how the components work. Ideally, you should avoid such situations. If you need to share data between components, extract the common data and place it in a shared, accessible location, such as a Content Fragment,...

Hi, You can download from here: https://github.com/magento/magento2/releases . Here is the official installation guide: https://experienceleague.adobe.com/en/docs/commerce-operations/installation-guide/overview Hope this helps

Hi,   Clearly, the issue lies with the token. Please debug and validate that the Authorization header is correctly formed, and confirm that the token you're using is valid. You can try hitting the author instance using the token via Postman or another tool to ensure it’s working properly.   Please c...

Hi, Typically, the request headers visible through the browser’s developer console are sufficient for most debugging needs. The next step I would recommend is to check your local dispatcher. By setting the log level to DEBUG, you’ll be able to see the headers, as shown below. Finally, you can adjust...

Hey, check that actually your project-global-spa-react/components/xfpage inherits from "PAGE" (the resourceType you are adding in the adapter section). Please check this example of how the resourceType and relationship is handled in order for the delegation to work properly: https://github.com/adobe...

Hi, Did you try this https://blog.arborydigital.com/how-to-do-a-tree-activation-on-aem-as-a-cloud-service? Are yo using that same step?  

Hi,   The current preference is to use Cypress; however, you can still use Selenium if you need or want to. One of the older versions of the AEM archetype used Selenium as the default E2E framework. This is the commit that introduced cypress as the preferred framework: https://github.com/adobe/aem-p...