Hi @SmrithiGo, You’re running into a issue with proxy and rewriting in front of AEM Forms: internal Adaptive Forms (AF) AJAX calls (such as guideContainer.af.internalsubmit.jsp or similar endpoints) do not automatically include your SI proxy path prefix (/abc/def). This causes problems when the clie...

Hi @SmrithiGo, Yes, you can absolutely use JavaScript or jQuery to dynamically set field values in Adaptive Forms based on browser cookies—but the key is to use the GuideBridge API. GuideBridge is the JavaScript API for AEM Adaptive Forms. It allows your custom code to interact with form fields—set/...

Hi @satish_puli, As you mentioned, this is not working for you.  How about trying with a relative path, like so: In the template, create a image fields with hrefs (not embedded) set to ./images/logos/<imagename.png> Place the images folder alongside the XDPModify the script to change the hostURL to ...

Hi @satish_puli, As far as I remember, the crx:/// protocol is no longer supported for security and architectural reasons. Cloud Service utilizes Asset APIs/CDA (Content Delivery API) for exposing DAM assets, and direct repository calls like crx:/// aren’t allowed. The image field in your XDP cannot...

Hi @Shreyas_tm,   Thank you so much for sharing the information.   Thank you for reporting the issue regarding users being automatically removed from groups on the PN instance in your AEM Forms JEE environment. We have analyzed the behavior, and here are our initial findings and next steps: Observat...

Hi @Shreyas_tm., Can you please confirm if this is related to AEM Forms on JEE or AEM Forms on OSGI. This information will help us to answer your question appropriately.   Thanks Pranay

Hi @NaionyMo,   Can you please share both the working and the non-working forms?   Thanks  

Hi @sarikajain,   Please use the command below to create the project. Also as you mentioned that you are using Archetype 45, I would request you use the latest one.   Command: mvn -B org.apache.maven.plugins:maven-archetype-plugin:3.3.1:generate -D archetypeGroupId=com.adobe.aem -D archetypeArtifact...

Hi @sarikajain,   I’ve analyzed the error logs from the failed AEM Forms submission. The failure occurs because the Sling Models used by the Forms Core Components expect a SlingHttpServletRequest, but the runtime is attempting to adapt from a JcrNodeResource. Since JcrNodeResource cannot be adapted ...

Hi @SmrithiGo, As I mentioned previously, the use case works perfectly fine. To me it seems to be an issue related to the artifacts that you are using. To Investigate this issue further request you to kindly share the artifacts and raise a support case with Adobe, as it seems to be an issue related ...