Hi,we are designing a form for a client with some complicated logic etc. In testing we are having an issue. When the form is submitted and you are presented with the confirmation page, it takes a very long time to download the pdf receipt and for it to be delivered. It does eventually go through to being submitted and the receipt does download, but looking in the transaction details we have an error table with some errors referring to "Render Receipt Error - Not Serializable".After some trial and error with taking out sections and other logic, we still have the issue. I have attached the composer xml file for the form, a submission xml data for the form and a copy of the error.any ideas?
attachments to support question above:
This issue was caused by the execution of the validation code on the default date widgets when rendering pdf receipts using livecycle es 2.5. Specifically, functions that utilised the momentjs library that is embedded in the xdp on ES 2.5 take many orders of magnitude longer to execute in ES 2.5 than they do in ES3. We have an issue documenting this. To fix this we customized the Date widgets adding this code:
if (sfc.isReceipt()) return;
as the first line of the validation script.
A more general approach is to disable "Generate if Receipt" in the Nuts and Bolts -> Data Controllers section of Composer.
I presume the not serializable error was actually the result of a render receipt timeout because of the slowness of the date validation functions, which is why Don was seeing multiple attempts.
"Not Serializable" error is generally associated with a Adobe LiveCycle Output PDF receipt rendering error. TM makes a call to LC to perform this operation using Hessian. The LC Java Application server then dispatches a request to an native XMLForm process to render the PDF via EJB/CORBA. If the XMLForm process call fails, it will generally result in a "Not Serializable" error being returned to TM.Please check the Adobe LC server log file for more information. Invariable if this error continues, you will need to restart the Adobe LC server application, and ensure its tmp and work directories are cleared out when you do this.