Backward compatibility configuration

Ensuring upgrade compatibility across LiveCycle versions is of prime importance for Adobe and our customers relish that. This means if a feature works in a certain way in a release it will continue to do so.
One can configure Mobile Form to get the behavior of a feature in older versions. You can browse through http://localhost:8080/lc/system/console/configMgr and search for “LC Forms Configuration”. On clicking, it should expand like the following:

version

If anyone is upgrading the Mobile Form specifically from ES4 to ES4 SP1, then to make sure the upgrade compatibility one should select “LiveCycle ES4″ from the browser. In ES4 SP1, we changed the way we submit the form for details refer to Mobile Form Service Proxy post. If you want to use the older way of submission, you can select “LiveCycle ES4″ version behavior.

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.
rtl

Limitations

Here comes the limitations. It works perfectly fine in all other supported browsers except IE. IE lacks basic support for Right To Left scripts so Mobile Form doesn’t support RTL in IE.

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.
You can pass parameters by using setAttribute(parameter_name, parameter_value) on the request object if you are forwarding a request from any other jsp/servlet to Mobile Form profile jsp/servlet. This will have highest precedence.
Another way to pass parameters is through profile node i.e. the node where request is made. For example, http://localhost:8080/lc/content/xfaforms/profiles/test.html /content/xfaforms/profiles/test is the profile node. You can specify parameters as node properties on this node using crxde.
profileNode

Mobile Form gives highest precedence to parameter values set using setAttribute then it falls back to profile node properties and in the last it reads values through request parameters.