Table 1. Known limitations of Forms Experience Builder
Table 2. Forms Experience Builder Best Practices
|Form item size limitations.||When building a Forms Experience Builder application, you must not exceed the following size limits
It is important to note that items create database columns, and contribute to the 32-kb limit even when they are hidden on the form.
- You cannot have more than 1000 data items in your form
- DB2® has a page size limit for tables of 32kb.
- Each data item in a Forms Experience Builder application has a size limit. For example:
- Single Line – 200 bytes
- Multiple line – Forms Experience Builder uses a CLOB data type to store the value of each multiple line entry data item. The limit to the number of characters stored in a CLOB is dependent on language and character set. The English limit is approximately 1 million characters. If the content of any given multiple line field exceeds the database allowance, you see a "500 Internal Server Error" message, and form submission fails. The full message is stored in the system log files.
- Currency/Number – 8 bytes
- Attachment – 108 bytes
- Select One and Survey – size is based on the number of choices and questions
- If you receive the error The row length of the table exceeded a limit of 32677 bytes. (Table space .). SQLCODE=-670, your form exceeds the maximum size. You must remove items from the form, or break the application into multiple forms.
|Limit on the number of embedded sections.||When designing a form in Forms Experience Builder, you can embed sections within sections to achieve the wanted layout. Do not embed more than 5 sections within one another. |
When using more than five embedded sections, it becomes difficult to select the action icons for a specific section. Exceeding 5 sections also results in forms not rendering properly.
|Printing Forms Experience Builder content||Forms Experience Builder provides a print button. If there is no print button in the contents of your form, the web browser print function does not work well. To print out the contents shown in your browser, uses a screen capture. For more information, see Taking a screen capture in Windows. |
Table 3. Troubleshooting Forms Experience Builder errors
|Canonical URLs versus short URL in the ibm.nitro.NitroConfig.serverURI property of the Builder_Config.properties file||When accessing Forms Experience Builder, the ibm.nitro.NitroConfig.serverURI entry setting is different from the browser address base URI. If you are using a short URL format to design your application, you must set ibm.nitro.NitroConfig.serverURI entry with the canonical URL. For example, if your short URL is http://localhost:9080/forms, the canonical URL for the user is http://hostname:9080/forms. Using two different URLs means users must sign on twice, as the short URL is replaced by the canonical URL. It is a best practice to use the canonical URL whenever possible.|
|Web Link and Website form items.||When using the Web Link or Website form items in your application, ensure that you enter the correct URL to get the runtime result. If the link goes to an external site, you must enter the URL with a URL protocol. For example, enter the URL as http://www.ibm.com, rather than www.ibm.com.
When using the Website item in a Forms Experience Builder the URLs entered must begin with: http://, https://, ftp://, or ftps://
- If you enter the URL with no protocol, then the URL is considered relative the current location. The prefix for the relative URL is attached, which might result in errors.
- If you enter the URL with a single slash '/', it resolves to a URL relative to the root of the host.
|Forms Experience Builder users and groups||When using WebSphere® Application Server to directly maintain users and groups, it is important to maintain integrity between the WebSphere Application Server users and Forms Experience Builder. If you change a user definition in WebSphere Application Server, and that user is used in Forms Experience Builder, the relationship might be corrupted. The user would no longer be able to access Forms Experience Builder. |
|Circular references||You can populate the choices in a drop-down on one form from another form within the same application. For example, an application has two forms, FormOne and FormTwo. A drop-down on FormOne can be populated with data elements from FormTwo. It is important to ensure that you do not create a circular reference. In this example, if FormTwo also had a dropdown populated from FormOne, the results when rendering the form at run time would be invalid. To ensure data accuracy, do not create circular form references within a single application.|
|Uploading files in Forms Experience Builder ||If an application requires supplemental files, it is a best practice to use reference URLs, rather than uploading the files directly into the application. The option to include reference URLs is available in the Upload dialog from the Settings tab.|
|Forms Experience Builder Preview mode||To use the Forms Experience Builder Preview feature, you must ensure that your browser is configured to allow all pop-up windows. If your browser does not allow pop-up windows, users cannot see the preview window.|
|Forms Experience Builder unique identifiers||Ensure that all form item identifiers are unique. Having identical form item and page identifiers results in errors. |
|Browser cookies must be enabled.||To successfully log in Forms Experience Builder, you must have browser cookie enabled. If you have deployed Forms Experience Builder with WebSphere Application Server Community Edition as your application server, you must ensure that you have only one Forms Experience Builder window or tab running in your browser at any time. Attempting to log in to multiple Forms Experience Builder windows or tabs results in login errors. |
Table 4. General Forms Experience Builder information
|Java™ virtual machine error after installing Forms Experience Builder on WebSphere Application Server Network Deployment 188.8.131.52||If you see a Java virtual machine error, upgrade WebSphere Application Server to a newer version or fix pack. Or add -Xshareclasses:none to the generic Java virtual machine arguments for theForms Experience Builder server. |
|Building Forms Experience Builder applications in Safari with bidirectional languages ||Designing Forms Experience Builder applications with the Safari locale set to a bidirectional language results in extraneous horizontal scroll bars shown in each form cell. These scroll bars do not affect the rendering of the completed form at run time.|
|Allowing non-ASCII administrative login characters||If the Forms Experience Builder administrative user name or password contains non-ASCII characters, you must complete an additional configuration task.|
In WebSphere Application Server:
In WebSphere Application Server Community Edition, add the user name and password. For more information, see Changing the .
- Log in to WebSphere Application Server administrative console, and select the server.
- On the settings page for the selected application server, go to Server Infrastructure -> Java and Process Management.
- Go to Process Definition -> Java Virtual Machine, and specify -Dclient.encoding.override=UTF-8 for Generic JVM Arguments.
- Click OK, then Save
- Restart the application server
Parent topic: Troubleshooting
If data elements were removed in the new version, or their unique identifiers changed, the data associated with those elements is not migrated to the new application. Data elements that did not exist in the previous version, but were added in the new version, are added as columns to existing data records with a NULL value.
|Forms Experience Builder login page.||Forms Experience Builder has two unique login screens. The first is the general product login screen that is shown when using the URL to build applications or View Responses. The second login screen is specific for each application, and is shown when using the Launch Form URL. The second login screen is not available if you are using IBM® WebSphere Application Server Community Edition as the application server for Forms Experience Builder. When using WebSphere Application Server both login screens are available.|