Step 8: Review the functions, scripts, and script triggers in your custom app

Some functions, scripts, and script triggers are not supported in FileMaker WebDirect, or they perform differently than in FileMaker Pro. Review all calculations and scripts in your custom app to make sure they perform correctly.

For information about individual functions, script steps, and script triggers, see FileMaker Pro Help.

Functions

• To create conditional behaviors based on the type of client, use the Get(SystemPlatform) function. If the function returns 4, the current user is accessing your custom app with FileMaker WebDirect.

• You can detect the operating system and web browser running your custom app by using the Get(SystemVersion) function. If you have difficulty identifying the device, use Get(WindowWidth) and Get(WindowHeight) to identify the appropriate layouts for the device.

Scripts, script steps, and script triggers

• Verify that the scripts only contain script steps compatible with FileMaker WebDirect, and only provide access to scripts that should be used from a web browser.

• If a script encounters an unsupported or unknown script step, the script step is skipped and the script continues to run.

• In FileMaker WebDirect, scripts can't access the client's file system. Web users must select files to import or insert, and exported or saved files are downloaded to the web browser's default download location.

• In FileMaker WebDirect, script steps can't enter a field if access to the field is restricted by either the Browse Mode or Find Mode option in the FileMaker Pro Inspector.

• If a web user closes a browser window or clicks the web browser's Refresh button, FileMaker WebDirect leaves the current session without signing out or activating the OnWindowClose and OnLastWindowClose script triggers. If the web user clicks the Refresh button, FileMaker WebDirect then creates a new connection to FileMaker Server or FileMaker Cloud, activating the OnFirstWindowOpen and OnWindowOpen script triggers.