Adobe Experience Manager Forms

Hello,We are trying to install AEM Designer on Windows 11 laptop and getting 1722 error. Is there a new installer we should be using for Windows 11 systems? Please let us know.  

Hello Experts, I have issue with overflowLeader processing in pages other than first one. In my logic I am dynamically hiding some columns based on the data (zero columns are hidden). This is implemented and works very well but only on 1st page. Required columns are hidden in overflowLeader and data rows:I even changed the label of one of the columns from the code to check if specific data can be accessed. It looks good.But on the second page everything falls apart:Font sizes, .presence = "hidden" settings, even the simplest .rawValue = "TEST"; setting is not applied. Similar setting (font sizes, hiding of columns works fine for data rows - that is why the layout is broken on second page).I am looking for your kind support to help find a way of accessing overflowLeader properties on the second (and subsequent) pages as it seems that my: data.Body.Table.IM_TAB.overflowLeader::initialize is working for 1st page only. I tried all the events under it ... no luck 😞 All hints ar

Hi Team,One of our customer reported an issue where the checkboxes are not visible in the domain page. On checking it, the page has a adaptive form linked and that form uses Ultramarine theme. It works within AEM(author and publishers). Also, On checking further, we noticed the file name of that asset is not existing with an extension and it is not valid name.Attaching the screenshot of issue and path of the asset./etc/clientlibs/reference-themes/ultramarine/assets/1458282381866 If we change the theme to some other themes apart from Ultramarine (eg: Simple enrollment, Tranquil etc) and publish form, checkboxes are visible in the domain.It would be helpful if we get any suggestion on how we can allow these kind of files in AEM. Thanks in advance!

Hey All,So im working in a sandbox provided by my manager - with the task being to create an adaptive form POC for a client.Let me know if anyone has an idea of whats going on, or how to best go about creating a form like this one (if possible).Im learning forms currently, so I simply did the bare minimum of the following steps to see the "issue" im facing now:- Opened forms sandbox "Navigation" pane- Selected "Forms"- Selected "Forms & Documents"- Clicked "Create" -> "Adaptive Form"- In "Create Form" pane (see below pic) -> Clicked "Blank with core components"- It doesn't let me "create" yet, so went to "style" tab and clicked "Canvas" option (see below)-  Now I can click create, so did that and saved in default path "/content/dam/formsanddocuments"- It opens a new window with the created form, but i see nothing at all. And clicking edit or preview does nothing either. (see below).  

Is there any release notes for AEM Designer 6.5.23? I am not seeing anything and there is an upgrade release available. Would be nice to know what the release is for. Thanks!

Hello, I'm following the guide to enable form core components (https://experienceleague.adobe.com/en/docs/experience-manager-65/content/forms/adaptive-forms-core-components/enable-adaptive-forms-core-components) MVN build works ok, but when I go and create a new Adaptive Form, I get the below error:Compilation errors in org/apache/sling/scripting/sightly/apps/myform/components/adaptiveForm/page/customheaderlibs__002e__html.java: Line 43, column 2006 : com.adobe.cq.forms.core.components.models.form.FormStructureParser cannot be resolved to a type I'm using the below versions in my pom.xml:<core.wcm.components.version>2.24.6</core.wcm.components.version> <core.forms.components.version>1.1.66</core.forms.components.version> <core.forms.components.af.version>1.1.66</core.forms.components.af.version> Thanks,David

I have a customer form that is being rendered in 6.1 and the fields appears to be behaving like floating fields.  You can see the below picture that the <period> is flush against the word SCRUBBED12.    The same XDP rendered in 6.5 is as expected - fixed width. You can see in Designer, it is not a floating field.  It is a Text Field overlaid on to Static Text. What is unusual is that UNDER the field is the following static text. I have never seen this.  Is this some notation for floating fields? Thanks,Charles   

I have a small Quarkus application that uses the libraries<dependency><groupId>com.adobe.livecycle</groupId><artifactId>adobe-consulting-types</artifactId><version>10.0.2.20120224.1.313570</version></dependency><dependency><groupId>com.adobe.livecycle</groupId><artifactId>adobe-livecycle-client</artifactId><version>10.0.2.20120224.1.313570</version></dependency><dependency><groupId>com.adobe.livecycle</groupId><artifactId>adobe-usermanager-client</artifactId><version>10.0.2.20120224.1.313570</version></dependency><dependency><groupId>com.adobe.livecycle</groupId><artifactId>adobe-utilities</artifactId><version>10.0.2.20120224.1.313570</version></dependency>to convert documents to PDF. If I run the code in non-native mode, everything works correctly. However, if I run the project in native mode wit

Hi,We have a requirement to render accessible PDF from XDP (XFA based) from Adaptive form.We are able to render static PDF which is tagged from Adaptive form (using XDP custom template) using Output service API. The issue that we need help is with the tag structure. The tags structure generated in the static PDF has tags something like shown below:using <Div>, <Set>, <Form>.The expected tag structure is as shown below:Can we achieve this tag structure. Any help would be great.Thanks,   

Hi,We are trying to render tagged PDF using custom XDP (XFA based) from Adaptive form. As we need a static pdf, we are using doRService for rendering tagged PDF. The issue that we are facing is that the generated PDF from Adaptive form is not using custom XDP.Adaptive form has the following configuraiton:1. Adaptive form - open properties - Form Model - None     Document of Record template configuration - Associate form template as document of record template We have a custom button, which triggers the servlet to render PDF using DorService api. Please let me know why the PDF rendered is not picking the custom XDP

I am currently installed this workbench version(6.5.0.20220219.1.12345) on local. Also installed both 32-bit and 64-bit versions of the Microsoft Visual C++ Redistributable packages as prerequisite.Seeing below error while opening AEM forms designer post workbench installation. Chatgpt provides following root cause for this issue. The error code "0x000007b" typically indicates a problem with the application trying to start, often related to issues with system libraries or dependencies. This error can occur if there are mismatches between 32-bit and 64-bit versions of libraries or if required components are missing. Has anyone encountered this similar issue ?

Hi, I am new to Form Designer app and I have a requirement to make fields in an XDP file accessible. Is there any way to make fields accessible on an XDP file and not using a tagged PDF file. Thank you.

Hello,After upgrading our environment to AEM 6.5.20, we've encountered a critical issue where Adaptive Forms fail to load. Attempting to access any Adaptive Form results in a blank page, and the following error appears in the logs:org.apache.sling.scripting.sightly.render.ObjectModel Cannot access property 'xyz' on null object java.lang.NullPointerException: null at org.apache.jsp.libs.cq.gui.components.common.table.table_jsp._jspService(table_jsp.java:56) ...This issue is impacting our form-based workflows significantly. Has anyone else experienced this problem after the upgrade? Any insights or workarounds would be greatly appreciated.

We have an adaptive form that outputs a document of record. Currently the PDF that is produced by AEM is not tagged at all, i.e. heading, paragraph text etc. tags do not exist in the structure of the PDF.  I found this documentation about how to enable tagging via a custom CXI file, but the ;Services -> Forms' option that is mentioned in this document doesn't exist in AEM 6.5.  Am I just missing where this lives, or is the documentation incorrect? https://experienceleague.adobe.com/en/docs/experience-manager-65/content/forms/administrator-help/configure-forms/specifying-xci-configuration-options#:~:text=In%20administration%20console%2C%20click%20Services,%2C%20producer%2C%20and%20compressObjectStream%20settings.

Dear all,I have been struggling with this issue for more than 3 months and I am running out of solutions. I am currently working on old pdf forms encoded with an XFA format that was made with the old software Adobe Livecycle. I have to correct those forms, sometimes for just a "." and the only way I found is to print the form (as advised on the Adobe site). But this completely destroys the document and suppresses all the drop-down menus. Meaning that I have to re do all the form for just a ".". If it was not enough work already since these forms are used in more than 56 languages (languages using symbols (like Korean)) are creating issues later with date format (even when clicking on the drop-down&nbs

We are using XDP file and XML files to generate the PDF document.  We have check boxes in the PDF  and javascript included in the XDP file.  It is loosing the check box functionality in generated PDF.  Code Snippet  var file  = new java.io.File(templateFolder, pdfTemplate);var inDoc = new com.adobe.aemfd.docmanager.Document(new java.io.FileInputStream(file));     var xmlDoc = new com.adobe.aemfd.docmanager.Document(xmlDataPart.getInputStream());var xciDoc = new com.adobe.aemfd.docmanager.Document(xciTemp);     var pdfOptions  = new com.adobe.fd.output.api.PDFOutputOptions();//Set PDF properties using XCI template    pdfOptions.setXci(xciDoc);     //Flatten PDF    var outputService = sling.getService(Packages.com.adobe.fd.output.api.OutputService);    var result = outputService.generatePDFOutput(inDoc, xmlDoc, pdfOptions);

I am having difficulties to setup angular for AEM angular spa application. Tried with different versions but no help.can someone please help me with the angular setup and resolve build errors 

Hi,I have created the Sample Letter under correspondence management, but "Submit" button is not getting enabled even after filled all the values in form. Please suggest any possible solution. Additional Info : I'm using 6.5 aem on premise fellow packages installed(6.5.22 sp installed, adobe-aemfd-win-pkg-6.0.1328.zip , adobe-aemfd-compat-pkg-2.0.50). I can able to create the data dictionaries, data fragments (not getting any error).  Thanks in advance.

 AEM Forms Core Components - AF Core Bundlecom.adobe.aem.core-forms-components-af-core status is in installed state.seeing this issue from last week only , before that it was working fine     <core.wcm.components.version>2.23.4</core.wcm.components.version>    <core.forms.components.version>2.0.76</core.forms.components.version>  <core.forms.components.af.version>2.0.76</core.forms.components.af.version>    <aem.forms.sdk.api>2023.09.11.00-230901</aem.forms.sdk.api>    <bnd.version>5.1.2</bnd.version>    <aem.sdk.api>2023.10.13804.20231005T183332Z-230901</aem.sdk.api>   archtype detailsaemVersion=cloudsdkVersion=latestlanguageCountry=${languageCountry}includeExamples=nincludeErrorHandler=nfrontendModule=generalsingleCountry=yincludeDispatcherConfig=yincludeCommerce=nincludeForms=nincludeFormsenrollment=yincludeFormscommunications=n

When I am installing AEM Forms add ons package, Channel Core Implementation is not getting active. It's in installed state.It is showing msm api dependency missing while I am installing AEM Forms add ons package.com.day.cq.wcm.msm.api,version=[5.9,5.11) -- Cannot be resolvedAnd when I have checked, this version of msm.api dependency is also not there on maven repository.

I am working on Adaptive form core component (version:1.1.64). I am using grid gap to set the gaps between the form fields, however the components which are set to hide in the form are still taking up spaces.How to replicate the issue: Set hide component using the author dialog:In preview mode: I found that the display: none was set to the component, but not to the component wrapper. I tried to use cq:noDecoration to remove the wrapper element, but it broke the component edit functionality on author.Is there any other way to fix this ?  

Hi.  I created a new AEM server.  I changed the password, and changed it in OSGi.  However something has locked it and I cannot get it unlocked no matter what i do.  Without getting my server scrapped, is there another way to reset that administrator password?  Thx

I am getting the [AF] [AEM-Af-901-004] error while trying to submit the Adaptive form in AEM 6.5 publish instace, while trying to submit the Adaptive form. In author the submit request is reaching backend.

 Hi Team,We're looking for best practices for form development focused on performance and maintainability.Previous Approach (AEM 6.5.21 OSGi Forms):Created forms using XML SchemaXDP was mapped to this XML SchemaUsed foundational components, not AF core componentsDoR requirement: Used XDP for PDF generationCurrent Approach:Forms are based on JSON SchemaXDP still uses XML Schema (since AEM Forms Designer only supports XML Schema)We're uploading JSON Schema + XML Schema + XDPField names must match across all three for binding to workUsing AF core components for better performanceWhat We Need Help With:We’re considering using only JSON Schema and relying on bindRef (name-based binding) instead of uploading XML Schema.However, since AEM Forms Designer (for XDP) doesn’t support JSON Schema, is this a feasible and reliable approach?We’re generating the DoR using:DoROptions dorOptions = new DoROptions();dorOptions.setData(jsonString getting formdata); dorOptions.setFormResource(formResour

Hi TeamWe are currently developing a custom Adaptive Form component using Core Forms Components. However, we are unable to see the "Display Pattern" option, which is available in Forms Foundation (Legacy) Components. Problem:In AEM Forms (OSGi forms add-on on-premises), when using Adaptive Forms Core Components, the Display Pattern property is missing in the Core Component dialog.RegardsVara