| Section | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
Controls in Panels with 100% width
Any v4.x forms In previous versions of , grid layouts were accomplished by using panels + a custom theme. Forms containing panels with controls that have the width set to 100% will overlap each other when the form is migrated to v5. Since . In v4.x, the controls were sharp rectangles in v4.x, the so the display looked as though the controls were placed one after the other. Changes to
...
The rounded rectangles in v5.1.1 have caused the input controls set to 100% input width now overlap each other. make this behavior evident. Also the date control drops slightly downward. This causes a usability issue when data is entered into the field. If the user max fills the field, the last character is will be partially hidden from view. Fortunately the overlap is at the END (right side of the input) of the control not at the beginning. So it's only a problem when the user enters enough chars to completely fill the input area. This isn't very common.
...
| Note |
|---|
We now strongly recommend using the table control for grid layouts as it is a much easier way to create such layouts; it does not require a custom theme; and it is fully supported across all browser types. Replace all forms with grids using the panel and custom theme technique with the v5.1.1 table control as soon as possible. |
Length of Asset Names
If any of your 4.1.7+ forms/flows have assets that resolves to a resources path longer than 250 chars, edit the the forms/flows manually and re-add the image using a shorter name before performing the migration.
...
There are new strings present in the default locale properties file for forms/flows in v5. For example.: strings for mobile devices. You will need to manually add these new strings to your uploaded locale files for forms created in v4. New strings can be found by downloading the v5 default properties file for your form. Server wide customizations can be done by unzipping the <frevvo-home>/tomcat/webapps/frevvo.war. See this documentation for the details.
Data API
The browser doc feature in v4 is no longer supported. It introduced a new doc action that can be enabled by the API and where, on submission, the XML document would be sent back to the browser with the HTTP response. This enabled the capture of updated XML and make sure it updated their own systems in a single db transaction.
In 5.x, we have a new mechanism. It is possible now to submit forms using the API and receive back a DataSource? with multiple parts (multipart/form-data) one for each submission document: XML, snapshot, attachments, etc. This is above and beyond what the browser docs provide, but much simpler. See API's submitInstance() and Data Source documentation (coming soon...).
...