Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Section
Column

Migration Consideration from v4

Warning

If you are upgrading from v4 to v5 please read and understand the following migration notes which may require your action.

Though most forms created on v4 will continue to run without any manual action on your part when upgraded to v5, there are a few migration items that you need to consider. Users of Online should read this information immediately as the SaaS/Hosted server http://www.frevvo.com is upgraded to v5.1 as of June 1, 2013.

If you have any questions please email support@frevvo.com

Column
width400px

On This Page:

Table of Contents
maxLevel3

...

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

...

Rules initializing Time and Date/Time controls will not work in a form.load rule unless you specify a timezone on the form's Url via the _formTz Url parameter. This is because the form server needs to know the timezone in which to return the date and time. If you do not specify a _formTz the methods will return null and the control values will remain blank. Timezone strings you can use in the parameter can be found here. For example, to specify Eastern time append &_formTz=America/NewYork to the form Url. This parameter is not needed if your form/flow only contains date controls.

Date Controls in a Migrated Flow

If you see a lightbox with the message "initializing form" and it never goes away when using a migrated flow that contains Date controls, edit the flow, then edit each activity and simply click "finish" (no changes needed). Finish the flow. This updates the formtype files and the flow will work properly in the updated version of .

...