WebDirect Guide
Table Of Contents
- Chapter 1 Introducing FileMaker WebDirect
- Chapter 2 Designing a FileMaker WebDirect solution
- Step 1: Plan your FileMaker WebDirect solution
- Step 2: Understand the capabilities of FileMaker WebDirect
- Step 3: Optimize performance
- Step 4: Design layouts for mobile browsers
- Step 5: Set the solution icon and options for layouts, views, and tools
- Step 6: Set up tasks for web users
- Step 7: Enable users to log out of the solution
- Step 8: Review the functions, scripts, and script triggers in your solution
- Step 9: Set up external data sources
- Step 10: Document your solution
- Chapter 3 Publishing a FileMaker WebDirect solution
- Chapter 4 Testing, monitoring, and securing a solution
- Appendix A Design considerations
- Index
Appendix A | Design considerations 34
Container fields
1 Web users can insert a file of up to 300 MB into each container field. To insert files larger than
300 MB, use FileMaker
Pro.
1 Web users can work with files of up to 300 MB in interactive container fields. If a file is larger
than 300 MB, web users must export the contents of the container field to work with the file. To
work with files larger than 300 MB in interactive container fields, use FileMaker
Pro.
1 To allow web users to export data from container fields, set Available menu commands to All
in the Edit Privilege Set dialog box.
Panel controls
1 Minimize the use of custom styles applied to panel controls. If a custom style is applied to a
panel control, the custom style may appear on other panel controls on the same layout, even if
those controls have different styles.
1 Objects placed on the tab label of a tab control are rendered in the panel area.
1 Tab controls display with a line separating the tab label and the panel area.
1 When designing slide panels in your solution, select Show navigation dots to allow web users
to navigate between slide panels with the slide control’s dots. Slide controls do not support
swiping through panels in the web browser. As an alternative, you can define scripts to control
the navigation between slide panels.
Popovers
1 To update objects on the layout, use the Refresh Object script step or the Refresh Portal script
step. Refreshing the entire window closes all open popovers.
1 Popovers do not resize when the window resizes, so design popovers with the size of the web
browser window in mind. Resizing a browser window to be smaller than an open popover or
opening a popover that is larger than the current window could produce unexpected results.
1 When a user scrolls in List View, popovers do not close until the user enters another record.
Button bars
1 In List View, button bars may have different active segments for each record in the found set.
1 When a button bar resizes, the button bar displays its default active segment.
Web viewers
1 Some webpages may not load correctly because their authors implemented security features.
Test all webpages you intend to display in the web viewer.
1 Web users might be able to interact with web viewer content in a limited way, even if you clear
the Allow interaction with web viewer checkbox in the Web Viewer Setup dialog box. Limited
interaction can also occur even if a web viewer is defined as a button.
1 Webpages that load code—such as JavaScript or references to Java, ActiveX, Flash, or other
plug-ins—run that code within the user’s web browser. Some web technologies may not be
supported or may be supported differently with FileMaker
WebDirect. Security settings within
the user’s browser may also prevent the use of these plug-ins.