Skip to content

Flywheel Core 18.0

February 2024

18.0.0

DEPRECATIONS

End-of-Support Schedule Extension for Legacy API Keys

  • Support for using Legacy API Keys has been extended into the 18.0 release.
  • Support will end with the 19.0 release of Flywheel Enterprise, scheduled for release in July of 2024.
  • Once a site is upgraded to version 19.0 or later, that Flywheel site will reject all authentication attempts that use Legacy API Keys.
  • All users should migrate to using Enhanced API Keys (instructions) as soon as feasible.

FEATURES

  • BETA Permalink URL Support for Extension Apps

  • Project Export is now generally available to all customers.

    • Project Export allows you to export files from Flywheel to a number of different types of external storage for further analysis or processing.
    • See the Project Exports documentation for more details
  • A new option is available in the fw-beta CLI for controlling how the Project Import process should handle conflict (duplicate) scenarios.
    • The option is named --conflict-strategy and is available when running the fw-beta import run command
    • The option has three choices: skip, update, and review
      • skip means the incoming file will be ignored and the existing data already in Flywheel will be unaffected. The conflict will not be considered an error and will not cause the import to fail.
      • update means the incoming file will be imported into Flywheel, effectively ignoring the conflict scenario. The conflict will not be considered an error and will not cause the import to fail.
      • review means the incoming file will be rejected and the existing data already in Flywheel will be unaffected. The conflict be considered an error and will cause the import to fail. In the future, new tools will be provided for reviewing and resolving conflicts without failing the import.
    • The default choice is skip
  • The fw-beta CLI displays error messages received from Flywheel Core in a more concise and user-friendly manner. The full, detailed error is recorded in the log file.

FIXES

  • Resolved the issue with jobs finder malfunctioning.
  • Resolved issue where bookmarks were unable to scroll on the manage bookmark screen
  • Resolved issue where moving sessions one after another results in unchecked sessions being moved.
  • Resolved issue where async / async_ argument was in get_usage_report()
  • The SDK fw.search() now returns subject_id when return_type is subject

  • Project Exports

    • Fixed an issue where Project Exports could not be scheduled on a recurring basis due to an authentication error.
    • Fixed an issue with Project Exports where rerunning a previous export would cause a new snapshot to be created and exported instead the existing snapshot from the original export run.
    • Fixed an issue with Project Exports where users were allowed to enter incomplete rules (no logical operator specified) for filtering which containers to export.
  • Project Imports
    • Fixed an issue with fw-beta import where error messages printed in the Import Audit Log referenced source file paths relative to an internal temporary directory instead of the proper source location.
    • Fixed an issue with Project Imports where the dropdown menu for filtering imports by status contained an extra choice called "Retry", which is not a valid state for import jobs.
    • Fixed an issue with Project Imports where the audit report was occasionally unavailable for cancelled import jobs.
  • External Storages
    • Fixed an issue with fw-beta admin storages where error messages returned when creation of an External Storage fails contain the storage credentials provided by the user in clear text. The storage credentials affected are only those that the user provided as input to the storage creation command which resulted in an error.
    • Fixed an issue with External Storages where, after correcting a storage configuration for which the status check previously failed, the system continues to consider the storage status as "failed" even after new status checks pass successfully.
  • fw CLI
    • Fixed an issue where the fw CLI recorded the user's API key in clear text in a log file on user's local machine. The API key affected is only the key provided by the user when using the fw login command.
    • Updated 3rd-party dependencies used in the fw CLI.