Thanks for your reply. The purpose of experience fragment is different. I dont want to create a XF for just to keep navigation component. Any others solution we have ?
We are using editable template for building website. It has 10 templates in total and all follow same header and footer. As per editable template, if you create a design dialog in component and it's properties gets stored in polices, in the /conf location but the problem here is we have to maintain...
What you are mentioning it custom validation. I dont want to do any custom validation. just want to make it as required field. The OOTB required proper will do the job but just want to change the default error message to something else.
I know we can make use of required boolean property to make the field as required. If you dont enter any field in dialog, aem gives "Please fill out this field." as per the default implementation. Can we change this error message with any property? I referred this API link - https://helpx.adobe.com/...
I am doing some custom field level validation in touch UI. I can see the dialog-ready and foundation-contentloaded event fires before the dialog content is fully loaded which gives me empty value. I would want to know, Is there any event listener that i can use for triggering a call after my dialog ...
Chitra & Jorg - Like you said XF can not replace iparsys behaviour. I could not format the content in comment hence let me update the msg in summary of this ticket. Please check.
I heard that Iparsys component is not compatible in editable template and not recommended to use in editable template but I never seen any document from adobe on this. The fact is, Iparsys works in editable template in the same how it works in static template but it may not function properly when yo...