@Santhan You must have got this issue post the component deployment steps in LCM so the components are This issue is specific to components are not in a good state. Here are some steps you can follow:1. Do a clean server restart of the WAS server i.e delete the tmp/cache, restart the complete the se...

@jezwn I recall a similar request was raised by another customer and it was concluded that this targeting uses mbox.js which was deprecated in August'2020, and further mbox.js reached EOL this February. Thus, A/B targeting is no longer working. Hope this answers. 

@PrasadGo This dependency can be resolved with the OOTB adobe-aemds-core-docmanager bundle (package com.adobe.aemfd.docmanager.source) provided with the AEM set-up so you can download this bundle on filesystem or you can use your code that can be deployed as a bundle on the server.

@srujan1981 Thanks; please DM the ticket#. Let's take up the discussion further there.

@srujan1981 If you're creating an AF logged in as a different user (other than admin), then the user must have ACL permissions to the /conf path i.e. where the template is created. 

@srujan1981  If you're following the steps mentioned in the official doc then you should see the custom template as expected.Can you check the template type property of the template created- is it /libs/settings/wcm/template-types/afpage ?Also, check the permissions of the user creating the AF. [0] ...

@sesmic When you associate a theme with an AF, the default theme css (from under /etc/clientlibs) is applied to the form.When you make any styling changes to the form fields, then those changes will reflect under the form path (/content/forms/af/[AF]/jcr:content/guideContainer/rootPanel/items/[field...

@satish_kumar_r1 Seems to be an issue with the path of the public certificate specified while configuring the service APIs on the Adobe Developer Console. Ensure there are no spaces in the certificate file name or the path to the certificate file. 

@Srinivas_Opti The locking feature for the Adaptive form was provided earlier with Classic UI (deprecated) but not Touch UI. Recently we received a similar request from another customer, and feature enhancement is logged. No ETA as of now.

@NirmalAEM Got a similar issue reported by another customer. Did you reach out to Adobe support for this issue yesterday?If not, check for OS level patches (or any other changes) that were applied on the system recently. That will help us narrow down the trigger point of this issue, if the conversio...