| Section | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
In previous versions of , grid layouts were accomplished by using panels + a custom theme were used for grid layouts. Forms containing panels with controls that have the width set to 100% will overlap each other when the form is migrated to v5. In v4.x, the controls were sharp rectangles so the display looked as though the controls were placed one after the other.
...
If you see this error message, when using a flow, then the Element Name field on the Flow Properties Panel is most likely empty. You must edit your form/flow, explicitly set the form/ flow 'Element name' in the properties panel back to the default value 'form' or to the value that was set to before. This value must match what is in your database or loading the flow from an old submission will not work (including performing a task).. The error in the image occurred when the manager tried to access a task from the Task List in a flow with an empty element name field:
If you have been using the name attribute in v4 forms, it will not be available when creating v5 forms post-migration. Code which uses the submission xml in your integrations will need to be modified to use the root element name instead of the name attribute in the root element.
Internationalization
New Strings in Default Locale Properties File
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...).
...
Time and Date/Time Control Initialization in a form.load Rule
Rules initializing dates & time 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 .
Internet Explorer 8
IE8 is deprecated in this release and support will be dropped in the Fall 2014 Live Forms Release. Wet Signatures are not supported on Internet Explorer 8 as IE8 is not capable of supporting this feature.