Help

Scheduling administrative tasks Running server-side scripts
F
ILEMAKER SERVER 9 HELP 131
Running ScriptMaker scripts
FileMaker Server can run ScriptMaker scripts that are defined in hosted databases. You create a
Run Script scheduled task
, specify the database and the FileMaker account to use to run the script,
choose a script defined in the database, and when to run the script. ScriptMaker scripts that run on
FileMaker Server can do simple or complex tasks, for example:
• perform a field recalculation across all records
• process and archive new transactions nightly
• remove duplicate records before a scheduled backup
You use the ScriptMaker feature in FileMaker Pro to build scripts by selecting from a list of web-
compatible FileMaker Pro commands, called script steps, and specifying options. To run a
ScriptMaker script on FileMaker Server:
• The script should include web-compatible script steps.
• The script must be defined in a database file that is hosted on FileMaker Server. See
Hosting databases
(page 31).
For information about creating ScriptMaker scripts with web-compatible script steps, see
FileMaker Pro Help.
Notes
• If 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.
• If the Allow User Abort script step option is enabled (On), unsupported script steps will
stop the script from continuing.
• If the Allow User Abort script step is disabled (default), unsupported script steps are
skipped over and the script continues to execute.
• If this script step is not included, scripts are executed as if the feature is enabled, so
unsupported script steps will stop scripts.
Some script steps have options that are skipped, such as an option to show a dialog box. The
Event.log
file contains detailed information about errors or script steps that are skipped when
FileMaker Server runs ScriptMaker scripts. See Tracking activity in log files
(page 110).
• Server-side ScriptMaker scripts run in separate sessions on the Database Server
, behaving
like they do for Custom Web Publishing
. Each session has a its own copy of global fields
and variables. Calculation functions return the same values as when scripts run under
Custom Web Publishing, with the following exceptions:
• Get(AccountName) initially returns the account name that the script was run under
(specified in the Schedule assistant
when the schedule is created).
• Get(UserName) returns the schedule name.
• Get(ApplicationVersion) returns the Database Server version string.
• Functions related to hardware, such as Get(SystemIPAddress), return information from
the Database Server.
Related topics
Creating schedules (page 134)
Running server-side scripts
(page 130)
Scheduling administrative tasks
(page 126)