Given your scenario with approximately 24,000 users logging into the site during events, along with multiple publishers and dispatchers, you may need to increase the number of connections in your connection pooling configuration to ensure adequate capacity during peak loads. However, it's essential ...

@SRK_1D It hard to answer as AEMaaCS is new. We should update AEM SDK in case of major feature release from Adobe. It is fine to have as is as this provide backward compatibility. Also, I think it doesn't matter as everything depends on AEMaaCS as it will be having backward compatibility always. In ...

@Uppari_Ramesh In short, there is no problem we can use and expose /bin path and it will work fine. It's all about best practices for not to use /bin path.

@Jniza Overlay below file to add delete button/libs/cq/gui/components/authoring/editors/clientlibs/core/js/ui/ui.ContentTree.js As it is a custom change project specific change we have been looking for. Please change below lines and try:line number 178 to add delete buttonChange line number 322 to a...

Yes, it must be a multifield having image URL, title, description, call to action, etc. if required. On click of particular image, FE team have global or component popup to show required data.

@goyalkritika Create custom component in place of overlaying OOTB component as your requirements are very specific to project and at the same time it will reduce code complexity.Image is a atomic component to render imageTeaser is for to show image having call to actionOOTB component doesn't suits y...

H @sricharan1 You can follow this article to configure Okta SSO using the admin console and login via federated IDhttps://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/setup-okta-sso-with-aem-as-cloud-on-author/m-p/555032

Complete overview, usage and how to implement Sling Dynamic Include as part of AEM

Complete understanding of OSGI configuration secret and environment-specific variables as part of AEM as a Cloud Service.

@SRC_AEM_DEV First setup a preview environment and than try to publish the URL will not give this error. Go to -> Clound Manager -> Ennvironments -> programme Overview -> IP allow list -> Select specific preview environment -> click View & Update -> provide ip or make publicly(0.0.0.0/32) available ...