sorry, do you mean the whole bindRef value or just the xml element?
for. e.g the bindRef for a field may be "/LeaveForm/applicantFirstName" , do you mean use "applicantFirstName"? what if there are 2 nodes in the xml having the same name?
after making that change, i am getting another exception, not sure whether its related:
Caused by: java.lang.Exception: 0 : Unhandled exception in PAexecute82
is there quality control issues with aem forms, as in its not properly tested before releasing?
HI Sachjain, I can confirm that if i use the schema name it fixes the problem.
Couple of unanswer questions:
- is there some mistakes in the documentation? if so pls let correct it
- what if in my xml schema, i happened to have 2 element with the same names?
- the above PAexecute82 exception, after i restart the author instance the issue is gone, do you know what's the root cause? in production we cannot afford to restart just to fix the error.
This is a workaround. Forms team is working on the fix.
If XML schema contains two elements with same names, workaround will not work.
Are you using verify component or rendering XDP as to why you are getting PAexecute82 exception? More details required to find out the root cause.
I am using in the submission of the form, the option to "send pdf with email", and when submitting the form, the exception was thrown.
when i receive the email, there will be pdf attached if its a successful submission.
maybe that's why the PAexecute82 error occurs. Could there be some timeout issue going on? cos after i restart the aem server, it will work again. But it could be i put my computer to sleep and didn't shutdown the aem server before putting it to sleep.