That's a warning & submission should still work. I assume you are using post method for submission. You can probably enable HTTP Components log and see what is happening. May be wireshark or Charles with reverse proxy could help if call is orginating but failing on receiving end.

You can write a common API which is execute on valueCommit and does this.parent.validate([]). And if that returns true, enable the button else skip that.Alternate would be to listen to guideBridge event called elementValueChanged which wraps the field object in the event payload. And you could call ...

What kind of Form are you using? Is it XFA,XSD or None based Form Model?Let me get back to you on that.

You can use fillable text box in disabled mode(disable via rule).

Hi,You should put a bindRef on the Form Panel where the Fragment is associated. And for multiple use of same Fragment, this bindRef could be different.For example, for Business Address Panel having Address fragment, if you put bindRef as /root/businessAdress & for Home Address if you use bindRef /ro...

With the AEM Forms 6.1FP1 (or later patches), the validations get auto disabled for hidden fields/panels. Please check that.

Sightly support inclusion of jsp file as part of Sightly templates. So you'll need to move this statement to another jsp file and include that jsp file in sightly.

I think you can save partially filled data as Draft using Adaptive Forms draft feature and do custom submission which does payment gateway integration and signing. Post sign, you can fetch data from draft and remove the draft.

You should be able to install packages in following order:AEM Forms 6.0 JEE (aka 6.0 FP1)AEM 6.0 SP2 AEM Forms 6.0 SP2

Hi,you can take a look process reporting UI that is part of AEM FOrms JEE installation.Deepak