Step 6: Set up tasks for web users

In addition to entering or modifying data, your custom app may require web users to perform other tasks.

Specifying the sort order

The Sort Records dialog box in FileMaker WebDirect displays only the fields on the current layout. You can also sort by fields that are not on the layout if they are specified in the Sort Records script step. To control which fields web users can sort by:

  • hide the menu bar and the status toolbar, then create buttons that are scripted to sort the data

  • use the Manage Security dialog box to restrict access to fields

Working with graphics, sounds, and movies

Container fields store and display pictures, sounds, movies, and files. Container data can be embedded inside the custom app itself or stored externally.

Note  FileMaker WebDirect does not support container data that is linked by reference. Referenced container data displays as a static icon and can't be exported.

You can optimize container fields for static content or for interactive content:

  • By default, container fields are optimized for static content. Web users can't open PDF files or play video or audio files. Web users see either a static graphic or a link to the container field object.

  • Container fields optimized for interactive content allow web users to play media files and to interact with PDF files. To optimize the container field as an interactive container, select the FileMaker Pro Inspector Interactive content option.

Note  In mobile browsers, users can't insert data by dragging a file into a container field. Consider creating scripts that use the Insert Picture, Insert File, Insert Audio/Video, or Insert PDF script step.

Web browsers provide inconsistent support for media files, and browser versions may vary on different operating systems. Some browsers may not correctly insert, display, or play certain media files.

Working with virtual windows

Web users can navigate between multiple virtual windows in a single web-browser window to view a custom app in different layouts, views, and modes. Only one virtual window displays in the browser window at a time, but inactive virtual windows remain open when they are not visible.

Virtual windows are opened, closed, and manipulated using script steps. See FileMaker Pro Help.

  • Script steps that affect windows work differently in FileMaker WebDirect than in FileMaker Pro. Because web browsers employ a single document interface, if your FileMaker WebDirect custom app uses the New Window script step, the new window is stacked in front of the current window within the same browser window. In many cases, using popovers or slide controls can provide a better user experience than using multiple windows.

  • FileMaker WebDirect supports the document and card window styles. For more information about window styles in FileMaker WebDirect, see FileMaker Pro Help.

  • If you open a new virtual window with the New Window script step, provide scripted buttons to navigate and close the virtual windows.

  • Close unused virtual windows with the Close Window script step.

  • If you design a script to perform an external script from a FileMaker data source and you want to return to the original window, add a Select Window [Current Window] script step immediately after the Perform Script script step in the original script.

  • If you use the Exit Application script step or close the last virtual window with the Close Window script step, the script ends the user's session and returns the user to FileMaker WebDirect Launch Center. If the custom app is hosted by FileMaker Cloud, the user is taken to the Claris Customer Console Home page in the same browser when the FileMaker WebDirect session ends.

Importing and exporting data

Web users may need to share data between the custom app and another application. In FileMaker WebDirect, web users can import and export the following file formats:

File Format Import Export

FileMaker Pro (FMP12)

Yes

 

Tab-separated values

Yes

Yes

Comma-separated values

Yes

Yes

DBF

Yes

Yes

Merge

Yes

Yes

Excel

Yes

 

HTML table

 

Yes

Notes 

  • Custom-separated values are supported in the Import Records script step.

  • Exported or saved files are downloaded to the web browser's default download location.

  • To import from a FileMaker Pro file, web users must have access to an account in the file.

  • Importing and exporting data is not supported in mobile browsers.

  • The Specify Field Order for Export dialog box in FileMaker WebDirect displays only the fields on the current layout. You can also export data from fields that are not on the layout if they are specified in the Export Records script step.

  • To import files in a text-based format, ensure that the files use UTF-8 character encoding. To import files in other character encodings, use the Import Records script step.

Printing records

Web users can print the current found set of records and scripted reports. The Print script step creates a PDF in a new web browser tab. Web users can then use the web browser's controls to print the PDF.

Notes 

  • To set print and page parameters, use the Print Setup script step.

  • If fonts don't display correctly in a PDF, make sure that all required fonts are installed on the primary machine and the secondary machines in your FileMaker Server deployment. See FileMaker Server Help.