Please check below link and verify the steps one by one if we followed correctly as we don't require much changeshttps://medium.com/@toimrank/setup-aem-form-on-aem-as-a-cloud-service-426a8b52ec3a
@rajat168 Update ACL's at packages level /etc/packages will resolve the issuehttps://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/granting-access-to-package-manager/m-p/231290
@NitroHazeDev If you want to restrict access to the model.json data in a secure fashion without updating the host, you have a few options. Here are a couple of approaches you could consider:Restrict Access at the Servlet Level: You can create a custom servlet that serves the JSON data and then imple...
@SHIBANI06 Sorry, could you please elaborate on in which sense it got reordered? What is our basis for comparison? Are we comparing it with a particular version, or did they roll back the content pages using versioning?
@SHIBANI06 This should not be the case. It may occur that the content author changes the sequence in the live copy, but just after deployment, it gets reset in the live copy. The Language Master will never receive the update.
Please follow below link and allow path and extensionhttps://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/currentuser-json-always-returning-anonymous-in-publish-instance/m-p/553696
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