We are using the guidedateinput component in a lot of our forms and we are looking for best practices to provide the basic date validation (ie Is it a valid date) It is looking like out of the box there is no validation in that it allows the 31st February to be entered. We do not want or expect the ...

On our regular AEM components through Sites we use Readme.md files in each component and point the helpPath property to the documentation page in components section.We have tried to do the same in Adaptive forms but no link appears in the dialog editor.Anyone know of a way to do this?

I have tried that but it does not 'force' the uppercase, it just tells them they have got it wrong. We want the user to enter as they like and for us to convert to uppercase, for display and for the binding to the data.  

The approach we are testing today is using a guideBridge event handler. guideBridge.on("elementValueChanged" , function(event, payload) { var component = payload.target; // Field whose value has changed if (component.cssClassName.includes("uppercase")) { var uValue = payload.newText....

This is just the type of feature in needing. Though I'm wondering how to make this at the component level. Say we a dedicated competent for a particular reference number and that we wanted to always need it to be uppercase.Guessing we could at your rule into the rule script mode of the content.XML f...

We are building some AEM adaptive form components derived from the ootb ones. We are doing this because our client has specific CSS and HTML structure for form elements.We have a text component where we want to define our own display and validation patterns. We have managed to do this ok, but the oo...

Thanks workflowuser - your post pointed me to https://experienceleague.adobe.com/docs/experience-manager-learn/forms/document-services/using-fragments-in-output-service.html?lang=en From where I found a couple of zip files with Local and repository files.   Like so often the solution to my problem w...

This is how we have it - if we Preview as HTML form1.xdp in AEM id does not pull in the fragments unless we modify the original rendition to add a 4th parent reference ..\..\..\..\common-fragments    

Hi, We are migrating a load of XDP forms from LIvecycle to AEM. There are many Common Fragment XDPs for items like headers, footers, field types etc which are referenced relatively in AEM Designer and currently rendered through LCServer perfectly.   When we load all the XDP files (Fragments and Form...

It does drag a schema field and adds a component to the form with the correct binding etc. What we would like to do is add our custom component not a foundation component. So we have slightly extended some of the core components to include additional html and CSS classes, so when we add a string bas...