Hi @varaandeI would request you to raise a support case with us, as this will help us to review your current implementation and get your issues addressed.ThanksPranay

Hi @ShadanAa1, Can you please confirm which version of service pack you are trying to install. It might be some issue related to the installation.ThanksPranay

Hi @VinjamuriSh,Setting up an Angular SPA (Single Page Application) with Adobe Experience Manager (AEM) can be challenging if there are version compatibility issues or configuration problems. Here are some steps and resources that might help you resolve build errors and properly configure your Angul...

Hi @varaande,As you rightly pointed out, AEM Forms Designer does not support JSON Schema natively. It primarily relies on XML Schema Definitions (XSDs) for defining the structure of the form data. This poses a challenge if you are looking to use JSON Schema directly. Additionally the bindRef attribu...

Hi @SmrithiG1,Can you please let me know the exact use case you are trying to achieve as Accessibility for the form is not dependent on the field or form initialization. It is mostly concerned with the readability of the form and works at the form level.ThanksPranay 

Hi @SmrithiG1,If you want to make the form accessible then you can use the Accessibility tab to set the specific tooltip for the the specified fields on the forms. You can also select the screen reader preference to set the values for the form fields. ThanksPranay

Hi @aravindS,Please use the below example: https://experienceleague.adobe.com/en/docs/experience-manager-learn/forms/document-services/output-and-forms-services-article-develop ThanksPranay

Hi @aravindS,Thank you so much for your response. Based on the description, I have made some changes to the Sample.XML. Please find below the updated XML and try out the options. <?xml version="1.0" encoding="UTF-8"?><form1><fName>FirstName</fName><lName>LastName</lName></form1> Also, I tried to run...

Hi @makivelli,Thank you so much for sharing the information; the use case that you have specified is vert much feasible. To implement the use case you will need to write a custom JS, which will be called on the pre-sumitt event of the button. The sole purpose for the button will be to go through all...

Hi @aravindS,The XML that you are using is wrong as it is not able to recognize the template. I have updated the input XML and now I am able to see the prefil information.Sample XML:<xdp:xdp xmlns:xdp="http://ns.adobe.com/xdp/" timeStamp="2022-06-21T07:32:11Z" uuid="55226f44-34ad-4572-9ad5-23834f260...