FileMaker Cloud Release Notes

New features and enhancements

• In Admin Console > Configuration > General Settings, you can now change the time frame for daily automatic maintenance (Auto Maintenance Settings), allowing you to schedule maintenance when users will not be connected to the instance.

• In Admin Console > Configuration > General Settings, you can now enable weekly automatic maintenance (Auto Maintenance Settings). Enabling weekly automatic maintenance allows you to choose a day of the week to force the maintenance, during which all databases are stopped, all scripts are stopped, and all users are disconnected. Databases restart and users may reconnect after the weekly maintenance is complete. Daily automatic maintenance will continue to run on schedule.

• When restoring a database or downloading a backup, FileMaker Cloud now displays the progress.

• Performance has been improved for downloading databases and backups as archived zip files.

• In Admin Console > Backups > Backup Settings, you can now tailor backup configurations to suit your needs. This includes:

  • Deleted Databases Retention Policy: The default retention time for deleted databases has been reduced from 30 days to a maximum of 15 days, with a customizable range from 1 to 15 days. This change optimizes S3 storage usage and improves backup list loading performance.

  • Backups Retention Policy: The retention time for backups remains at 30 days, with a customizable range from 1 to 30 days. To optionally optimize S3 storage usage and improve backup list loading performance if users decide to reduce the retention policy.

  • Download Unencrypted Backups: You can now enable the download of unencrypted backups, ensuring all backups are unencrypted when downloaded. This feature facilitates runtime decryption for downloadable backups so there's no need to retrieve an EAR (encryption at rest) key. This only affects backups; downloading files from Admin Console > Databases is unchanged.

• In Admin Console > Backups, you can now perform backups on demand by clicking Back Up Now.

• In Admin Console > Backups > Backup Message Center, you can access real-time status updates on backup restoration tasks. This enhancement includes:

  • Progress Monitoring: You can monitor the progress of backup restoration tasks, which is particularly useful for downloading large backup files. This makes it easier to check when tasks are completed.

  • Task Categorization: The message center provides the following task categories that show the filename, time the task began, and status:

    • In Progress/Success: Tasks in progress or completed without errors. When download tasks are successful, you can download the backup.

    • Failed Task: Tasks that encountered errors or were interrupted, allowing you to retry failed tasks efficiently.

Addressed issues

• When using an OAuth 2.0 provider to send email, the email wasn't sent, and an error was returned saying the access token couldn't be generated. This happened when FileMaker Pro tried to send email or when FileMaker Server tried to send email notifications.

• When downloading logs from Admin Console, the archived logs failed to download.

• When directly downloading databases, if the storage was not mounted, the download failed to start. Now the storage mount is attempted if not already mounted.

• FileMaker script changes were not immediately available to FileMaker Data API clients until the FileMaker Data API session ended.

• FileMaker Admin API incorrectly displayed version 2.19 for FileMaker Cloud version 2.20.

New features and enhancements

• In Admin Console > Backups, you can now download backup for any backup type. In Admin Console > Backups > Deleted File, you can also now restore and show encrypted passwords for deleted files.

• Old logs are now rotated, kept for an extended period, and are accessible to download from Admin Console.

• The Admin API GET serverinfo call has been optimized to prevent repeatedly querying values that will not change.

Addressed issues

• In some extreme cases, restarting an instance of FileMaker Cloud failed to complete.

• After an upgrade FileMaker Cloud instances incorrectly restarted twice within a few minutes.

• FileMaker Pro 19.6.1 was unable to connect to FileMaker Cloud.

• Connecting to FileMaker Cloud using FileMaker Pro failed to open hosted apps due to corrupted local cache files.

• FileMaker Pro connections to FileMaker Cloud failed to reconnect when the local computer went to sleep and then was awoken from sleep.

• Database sign in was incorrectly required the second time a hosted file was connected to using FileMaker Pro if the "ForceReconnectSyncOfEverything" option was enabled on the local computer.

• Signing using external identity providers with upper case emails incorrectly displayed an error message instead of signing into valid accounts.

Addressed issues

• This update provides a number of important security fixes.

New features and enhancements

• In Admin Console > Backups > Hosted File and Deleted File, you can now restore backups by filename. You can choose which database to restore, then select which timestamp to restore.

Addressed issues

• In FileMaker Cloud Admin Console, downloading a FileMaker Pro file failed when the filename contained a double-byte character, such as a Japanese, Korean, or Chinese character.

• Downloading FileMaker Pro files in Admin Console stopped working after a few successful downloads.

New features and enhancements

• The Subscription tab in FileMaker Cloud Admin Console is removed. To manage your subscription, use the Subscription tab in Claris Customer Console.

Addressed issues

• The label for preserved backups inadvertently displayed Arabic characters.

New features and enhancements

Functions and scripts

• The ReadQRCode function is now available to use on FileMaker Cloud.

• The Execute FileMaker Data API script step now supports the dateformats parameter.

• Scripts run on FileMaker Cloud now support the Set Error Logging script step.

• The Save Records as PDF script step is now supported for the FileMaker Data API.

• FileMaker Cloud now stores the script events in the scriptEvent.log file instead of the Event.log file. You can view and download the scriptEvent.log file using the Logs tab in Admin Console.

Java

• Vaadin has been updated to version 8.18.0. Java has been updated to use version 17.

• Ubuntu: The Java Development Kit (JDK) 17 is now installed instead of the Java Runtime Environment (JRE).

OData

• SchemaVersion is now included in the $metadata response. The $schemaversion query option can now be used to determine whether the schema has changed, since a request for a non-current schema version will be rejected.

• OData now supports the PUT/POST/PATCH/DELETE $ref operations. It also supports aliases.

General

• New client connections are now blocked for databases in the process of being closed.

• You can now filter and sort the list of script schedules in Admin Console.

Addressed issues

FileMaker WebDirect

• Summary parts occasionally were not displayed when sorting records if there were no Body parts on the layout.

• List View objects didn't refresh when there were no records in a found set.

• In List View, the Footer part occasionally wasn't displayed during the initial layout load if a Navigation part existed.

• A cross-site scripting (XSS) vulnerability is resolved.

FileMaker Data API

• Table names were missing from responses to the FileMaker Data API layout names requests.

• The FileMaker Data API returned the incorrect foundCount and returnedCount values for portals when the initial row setting in the portal was greater than the number of records in the portal.

• The FileMaker Data API returned incorrect metadata about layouts with repeating fields.

OData

• Some OData query options returned errors if table names or field names contained Japanese characters.

• Line feeds in fields were not returned as "\n" and caused JSON parsing errors.

Performance

• Using the Set Session Identifier script step heavily to change session names caused the fmshelper process memory to increase unnecessarily.

General

• When a schedule failed, the timestamp for the Last Run value incorrectly reflected the last time the schedule completed successfully instead of the last time the schedule failed.

• Summary field content was missing when the hosted file data sources were set from the content of a global variable.

• Serial numbers were incorrectly incremented during a reverted transaction, and then serial numbers ceased to increment for normal record creation.

• Script triggers such as OnRecordCommit were not executed when called while a script transaction was running.

• Scheduled FileMaker scripts failed to run when a FileMaker scripts folder and a FileMaker script used the same name.

• Indexes created during transactions failed to include deleted records, even if the transactions were reverted.

• The GetContainerAttribute function returned a different date format than expected when performed on the server.

• Some trailing characters in fields were not exported when creating CSV files with FileMaker Cloud.

• Records failed to import from CSV files containing Shift JIS encoded data.

• The GetContainerAttribute function was unable to return photo details when calculated from the server.

• The Admin Console sign-in page didn't automatically refresh the browser after a version upgrade.

• The Hosts page in Admin Console didn't change the status of the instance to Online after clicking Restart Cloud Compute Temporarily.

• Admin Console: An exception occurred when the client IP address was not accessible.