@PrasadGo Filesystem based invocations would work for local builds but for remote, as mentioned earlier, the package com.adobe.aemfd.docmanager.source is exported by the adobe-aemds-core-docmanager bundle as well so you can run the tests deployed as a bundle. Haven't tested the same but you can give...

@AbhinavDi Recently we have observed some performance gains for some customers w.r.t XMLform service conversions when the XMLFormService.maxreusecount is reduced (by 50% or lesser) and increasing the XMLFormService.poolmax based on the number of cores on the server. Also, you may want to establish w...

@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_puli 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.