LiveCycle Enterprise Suite

Hide parameters from Mobile Form URL

In ES4, Mobile Form had a limitation that it could only hide the template references from the form URL exposed to the user. In ES4 SP1, one can overcome it using the new ways of passing parameters to Mobile Form render service.

To read more, visit Raghavendra Pandey's blog post.

Smart submission – part II : LiveCycle Process

In my last post on Mobile Form data submission, I discussed how to submit data directly to a LiveCycle process. In ES4 LiveCycle Mobile Form, one needed to deploy the custom package shared in this blog. In ES4 SP1, submission to any LC process is even more easier to do. Now you don’t need custom package any more.

To read more, visit Raghavendra Pandey's blog post.

LiveCycle PDF Generator ES4 SP1 provides Quick-Fix patch to take the advantage of Microsoft Windows hotfix 2815716

Microsoft released hotfix 2815716 to resolve the issue which restricted different users running in a single session (using runas command) to print from 32 bit applications. This restriction earlier forced the users to end the Splwow64.exe process manually before using the runas command to print from a 32-bit program with different user account in a single session.

This restriction required LiveCycle PDF Generator service to terminate splwow64.exe before Microsoft Office and other native conversions could be executed (though this termination was not done in case it was known that non-availability of Splwow64.exe would not cause a failure).

To know more about this development and its impact on LiveCycle, read Sudhanshu Singh's blog post.

Mobile Form smart submission

The workflows around Mobile Form generally involve rendering a form in the browser and then capture data and submit it back to the server. You cannot render the form if you are not connected to the server. In general, data capture step doesn’t need any connectivity from server except in case of running any script on server side or executing a web service. But connectivity is very critical in case of form submission. If you are not connected to the server and you submit the form, you would get just 404 error page and you data would be lost.

Read the complete post here.

Mobile Form Service Proxy

In the pre-release forum of ES4 and other customer forums of Mobile Form, one of the most sought after feature was to run all the Mobile Form workflows without directly exposing the LiveCycle server to the user accessing the forms in the browser. In ES4, the LC admin is required to open submission service “/lc/content/xfaforms/submission/default” to the whole internet as the Mobile Form needs to talk to it. The service url was embedded in the runtime model of the form. One way was to do URL mapping in webserver and proxy it but the restriction was one cannot change the URL path as it was in the runtime model.

To read the complete article, visit this blog post.

Mobile Form goes Right To Left

With ES4 SP1, we added support for Right To Left languages like Hebrew in Mobile Form. Now you can see html for your hebrew forms. Not only that but you can also fill the fields in Hebrew. We also support mix and match of English or any Left to Right script for that matter with Hebrew in form fields. Based on form locale we even show the date and days info in localized form.

Read the complete post here.

Passing parameters to Mobile Form

In LC ES4, we get this feedback from customers that they want to hide the parameters passed to Mobile Form profile to render a form. If you could see the There was only one way to pass parameters that is through request parameters (refer to Mobile Profile page). In ES4 SP1, we introduced couple more ways to pass parameters to Mobile Form.

Read the complete post here .

Create custom Mobile Form profile

Mobile Form renders the form based on profile. If you want to change the look and feel or do other customization, you are required to make modifications in the default profile. In ES4, Mobile Form profile script was one single monolithic jsp file. So if you want to modify the profile script you have to copy the whole script and then make the changes as suggested in ES4 Adobe documentation. This way, you loose the updates provided in the script over different patches.

To know more, read this blog post by Raghavendra Pandey.

Debugging Mobile Form

Logging in Mobile Form or any application for that matter is of utmost importance. It helps our customers in debugging the various issues in forms including performance. Mobile Form is a distributed application. It has a server component that generates data for the XFA runtime. XFA runtime is a javascript implementation of XFA reference that runs inside the browser and interprets the data generated by the Mobile Form server to render an XFA template and data in html5. In distributes scenario, logging helps a lot in keeping tab at what is going on at various sites.

Read the complete post here.

POST data size limit

A generic Mobile Form workflow involves rendering a form, filling up fields and then submit it for further processing. Mobile Form submits data to server on HTTP POST. If the form is very big or it is merged with large size data, sometimes there is chance that the submission payload exceeds the default limit of the server. In this case, you might see HTTP 500 error on form submission. If you inspect the server logs, you will see this exception – “Template is not specified”.

Read the complete post here.
Go to Top