There are several miscellaneous form design issues that you should be aware of when creating forms for Webform Server.
- If you draw a line that overlaps a combobox or popup, the Viewer will show the line on top. However, Webform Server will show the combobox or popup on top, which will cause a portion of the line to disappear. To address this problem, ensure lines do not overlap combo boxes or popups.
- Scroll bars may appear on fields despite the scrollhoriz and scrollvert settings. This occurs when one of the scroll bars is set to appear but the other is not. If the user types beyond the constraints of the field, the other scroll bar will appear despite the settings.
- Webform Server does not respect the borderwidth setting in the printsettings option. This means that printed forms will never display a border.
- If you use the set function, the value you are setting must precede the set function itself in the form’s build order. For example, if a compute in Item A sets a value in Item B, then Item B must come before Item A in the build order. If the value you are setting follows the set function in the form’s build order, the value will not be updated properly.
Note: Using the set function to set a value in the same item will always work, regardless of build order.
- Submission buttons that are set to transmit the XML model do not work. No information is submitted.
- Action items that do not have a delay specified will not run. To correct this, add the delay option to the item.
- The datagroup option should always include the page reference. This allows forms to be fully compatible with both the Viewer and Webform Server. For example: PAGE1.group1
- The page reference in the datagroup option determines which page an attachment is associated with. Forms should be designed to manage all attachments from a single page.
Note: The attachments added by users are included in these data groups and are associated with the same page reference.
- Impact Bold fonts that are 48 points or larger will render slightly wider than normal. This may cause lines of text to wrap incorrectly.
- When using xforms:switch/xforms:case in a form that will be used with Webform Server, the xforms:switch element must define and use the xfdl:state attribute. The xfdl:state attribute must define a reference that will be used to store the current state of the xforms:switch in an XForms model. If not used, the behavior of the xforms:switch/xforms:case is undefined.
- The fonts included in the default Windows® East Asian Language Pack do not contain any kerning information. For the most consistent and readable text, use a 12 point font.