The approach I explained focuses more on building forms for end users, allowing them to submit different types of data, such as capturing lead information. Content Fragments, on the other hand, are mainly used to enable headless (content not bound to a page) structured content. The Content Fragment ...

If you don't want to proceed with an AEM Forms license (which enables extensive form capabilities), you can use the Core Form Components that are part of the AEM Core Components. You can find them here: AEM Core WCM Components - Form. Additionally, you can create custom components or override existi...

My recommendation is to proxy the call from the CDN layer itself. You should be able to set the required API keys at the CDN level, which allows you to use the same DNS to invoke the APIs at the browser level. This approach also helps hide the API keys and prevents unnecessary traffic from reaching ...

Refer to this post to understand the approach to capture last logged in time of the user in Author-https://medium.com/tech-learnings/adobe-experience-manager-reporting-on-users-last-login-date-e2035021cb9e?sk=1b8b8d9832fd096ba4946620249ba598 Please test this in your local or dev instance including e...

Yes, it is possible to set the traffic filter rules, including rate limits, in AEM as a Cloud OOTB Fastly CDN. Some of the advanced WAF-based rules require an additional WAF or advanced security license, but the basic filter rules can be used OOTB. Please refer to the URLs below for more details. Tr...

The translation integration rule needs to be updated to configure the new components. Refer to "Adobe Experience Manager(AEM) Content Translation — Deep Dive(Part1) | by Albin Issac | Tech Learnings | Medium, under the section "Translation Integration Configuration," for more details. Regards Albin ...

The user sync between publisher pods is handled out-of-the-box (OOTB) in AEM as a Cloud Service, but this configuration is not enabled by default. Please raise a support ticket to enable the user sync between publish pods. Regards,Albin https://myprofile.albinsblog.com

Based on my recent migration experience, you may need to migrate from the current platform to the cloud using a package approach. For ongoing changes, considering there is no design manager available now in the cloud, you should use a method like the tree activation workflow(or package replication) ...

Try installing through the package manager: install the package on the Author instance and replicate it to the Publishers. For additional details, refer to Key Learnings from Migration to AEM as a Cloud | by Albin Issac | Tech Learnings | May, 2024 | Medium Regards Albin https://myprofile.albinsblog...

Reverse proxy functionality through Dispatcher (Apache) is still supported in AEM as a Cloud. However, AEM as a Cloud now also supports the 'originselectors' feature via CDN, allowing connections to non-AEM servers (reverse proxy requests to different origins). Utilizing this feature through the CDN...