Custom Web Publishing Guide

14 Custom Web Publishing Guide
1 If your scripts contain steps that are unsupported, for example, steps that are not web-compatible, use the
Allow User Abort script step to determine how subsequent steps are handled.
1 If the Allow User Abort script step option is enabled (on), unsupported script steps will stop the script
from continuing.
1 If Allow User Abort is off, unsupported script steps are skipped over and the script continues to execute.
1 If this script step is not included, scripts are executed as if the feature is enabled, so unsupported script
steps will stop scripts.
1 Some scripts that work with one step from a FileMaker Pro client may require an additional Commit
Record/Request step to save the data to the host. Because web users don’t have a direct connection to the
host, they aren’t notified when data changes. For example, features like conditional value lists aren’t as
responsive for web users because the data must be saved to the host before the effects are seen in the value
list field.
1 Similarly, any script that modifies data should include the Commit Record/Request step, because all data
changes aren’t visible in the browser until the data is saved or “submitted” to the server. This includes
several script steps like Cut, Copy, Paste, and so on. Many single-step actions should be converted into
scripts to include the Commit Record/Request step. When designing scripts that will be executed from a
web browser, it’s a good idea to include the Commit Record/Request step at the end of a script to make sure
all changes are saved.
1 To create conditional scripts based on the type of client, use the Get(ApplicationVersion) function. If the
value returned includes “Web Publishing Engine 7.0v1” you know that the current user is accessing your
database with Custom Web Publishing. For more information on functions, see FileMaker
Pro Help.
1 After converting your files, you should open each script that web users might run and select Indicate web
compatibility
to ensure that the script will execute properly with Custom Web Publishing.
1 If you are using a script in an XSLT stylesheet that sets or modifies a state, you must use the Administration
Console to enable the XSLT Database Sessions option for the Web Publishing Engine. Otherwise, states are
not maintained between requests. See the
FileMaker Server Advanced Web Publishing Installation Guide.
The following script steps function differently on the web than in FileMaker Pro. For information on all script
steps, see FileMaker
Pro Help.
Script step Behavior in Custom Web Publishing solutions
Perform Script Scripts cannot perform in other files, unless the files are hosted on FileMaker Server and
Custom Web Publishing is enabled in the other files.
Exit Application Logs off web users, closes all windows, but does not exit the web browser application.
Allow User Abort Determines how unsupported script steps are handled. Enable to stop scripts from continuing,
and disable to skip over unsupported steps. See above for more details.
Set Error Capture This is always enabled with Custom Web Publishing, and prevents web users from aborting
scripts.
Pause/Resume script Although this script is supported in Custom Web Publishing, it should be avoided. When a
pause step is executed the script runtime pauses. Only a script containing the resume script step
can make it resume execution. If the script runtime remains in a paused state until the session
times out, then the script will not be completed.
Sort Records A specified sort order must be saved with the script step to execute in Custom Web Publishing.
Open URL This script has no effect in a Custom Web Publishing solution.