Scheduled Deployments
OttoFMS comes with the ability to schedule a Deployment to run at a later date and time. This is useful if you want to set up a deployment to run after hours when no one uses the system.
FileMaker Server Script Schedules
Rather than creating another way to schedule actions on a FileMaker Server, OttoFMS uses FileMaker Server's System Script Schedules feature to trigger the deployment.
How does it work?
When you send a deployment to OttoFMS, it checks a scheduled flag and timestamp. If it finds a valid flag and timestamp, it will create a system script schedule (opens in a new tab) on the FileMaker Server that will trigger the deployment at the specified time.
We generate a name for the schedule, but this name can be changed. If you need to change information about a schedule after it has been set up, you can edit the scheduled time and name from the FileMaker Server Admin Console.
Cancelling a Scheduled Deployment
If you need to cancel a scheduled deployment, you can do so from the Deployments List or Deployment detail view. Click the three dots menu and select "Delete". This will also delete the FileMaker Server schedule that was created for the deployment.
Scheduling Recurring Deployments
In OttoFMS version 4.4.0 or later, you can set up a recurring deployment. See the guide here for more details.
Editing the selected system script or the script parameters will break the schedule, ensure that they are not changed if you edit the name or scheduled time.
Running two schedules at the same time will cause one of the two to fail. Ensure that your schedules have enough buffer time between them for the entire deployment to run before another deployment begins.