Hi @jezwn As Vaishali mentioned, the replication part has changed from replication agents to SCD. Also, to move the content from dev to prod, you might be using packages only in past as well. So here you can create the package from DEV and deploy it to Prod via pipeline. For environments above DEV, ...

Hi kendalls5216292 , Every page i.e a node of type cq:page in AEM is associated with a template that defines the page component used to render the page. This page component would contain the default HTML code which would be rendered when the page is called. You can refer to https://helpx.adobe.com/i...

Hi @joannaj49016259, There is extensive testing involved as part of the update and it will create an image first. If there are some issues then the instance is kept to the previous state. Also as mentioned in the doc, since AEM as a Cloud Service evolves on a daily basis, based on the projects imple...

Hi @bhatkarp  Seems you are using OOTB authentication only and not relying on SAML. In that case when you logout, doesn't it redirect you to AEM login screen again? If that's not the case, I would suggest raising a daycare ticket with a screencast of the issue so that the support team can help you.

Hi,AFAIU, The extra node seems to be getting created as you are forcing the profile node in your curl command itself that should not be done in the request. You just need to pass the values of properties like givenname, lastname, email etc in the command and internally a profile node is created to s...

Hi Rohit,If it is really slow for some basic operations then feel free to raise a support ticket here: https://daycare.day.com/home/createaticket.html with clear detailed use case to replicate the slowness and thread dumps if specific to your environment.

You can try recompiling the JSPs from host:port/system/console/slingjsp to see if helps. In case you still see the issue, please raise a support ticket here : https://daycare.day.com/home/createaticket.html to investigate the NullPointerException.

Adding to what @bharath said above, Make sure you are not using scheduled activation for replication as it internally uses the workflow-process-service user to replicate.

You can refer to [1] to see the list of deprecated APIs in 6.5. Feel free to change the version number in the URL to see deprecated APIs in each version.[1] Deprecated List (The Adobe AEM Quickstart and Web Application.)

It could be possible that the existing form is dependent on the clientLib category which is not needed. To remove the clientLibrary it would be better if you can raise the daycare support ticket and share the clientLib details and nodepath from where you are removing it.