Skip to content
Pathcore Upload Client Release Notes

Pathcore Upload Client Release Notes

v2.2 (2025-01-20)

New Features

File Deletion Policy

Version 2.2 of the Upload Client (re)introduces a file deletion policy. When enabled, images that are confirmed to be uploaded to your Repository are removed from the local system, freeing up storage space. The policy allows you to configure the amount of time the client waits after the upload completes before files are removed.

This feature is disabled by default, but can be enabled with the Delete After Upload setting. Also see the new Upload Verification feature.

Upload Verification

Upload Client uses the new verify option in the multi-file upload API to ensure the integrity of uploaded files before committing the data and making it available to users. Additionally, if it determines the file has been corrupted during transfer, it will restart the upload. This feature supports the file deletion policy, ensuring reliable upload processes.

Integrated Authentication

This release also includes a new workflow for logging in. Instead of typing your username and password directly into the Upload Client, your default web browser takes you to the login page for your PathcoreFlow service to complete authentication. This improved integration with the web service improves the security model, supports users who are members of multiple teams, and allows the Upload Client to be authenticated via your organization's Single Sign-On (SAML SSO) provider — including multi-factor authentication (MFA).

As this improved integration depends on recent updates to Pathcore services, this version of the Upload Client is only compatible with deployments running PathcoreFlow v4.0 and newer. This release is not compatible with PathcoreScholar (<= v2.0.3).

More details on how to log in using this new process can be found in the User Account section of the updated user manual.

Unicode Character Support

Unicode characters are now supported in filenames and paths. Previously, files with unicode characters were excluded by the upload process (i.e., skipped). The behavior of files with unicode characters in the Repository is unchanged by this update.

Automated Token Refresh

The Upload Client's authentication token lifetime has been reduced to 30 days, and the client will renew this token daily when uploading. This new pattern is expected to reduce user driven (manual) authentication steps, reducing maintenance and improving the security model. Previously, users were required to re-authenticate every 3 months to refresh the token.

Improvements

A number of updates were made to the Upload Client interface to make it easier to use and improve the user experience. These include:

Improved Main Window UI

  • The Active Uploads and Recent Uploads tables have been merged into a single Recent Activity table
  • The Upload History table now shows relative time of upload completion with the absolute time displayed on hover
  • The Recent Activity and Upload History tables now correctly resize when the Upload Client window is resized
  • The Team name of the logged in user name now appears in the window title
  • Updated the status bar text with more descriptive information about current operations

Improved Toolbar UI

  • Larger icons with improved color, labels, and tooltips
  • A dedicated "Log Out" button at the right-hand side of the toolbar
  • The "Resume" icon no longer grays out when uploads are disabled
  • The button to open the Repository is now a Pathcore logo

Improved UI Feedback

  • The Upload Client now reports files that were "Skipped" because they are already present on the server
  • Attempting to open an image now checks that it is ready to view in PathcoreFlow first
  • An icon will now be added to the desktop during install
  • When first launching the Upload Client, a user is now prompted to log in if they are not already
  • If configuration is needed for Upload Client operation, the Status Bar now displays a warning

Fixed in this Release

  • The Recent Activity table will display skipped files (i.e., files that could not be uploaded)
  • Upload History table will correctly show uploaded and skipped files
  • Closing the client now correctly closes the user interface instead of minimizing it. The background process will continue to run and transfer files as long as a user is logged in
  • Only one instance of the Upload Client will run at a time
  • The scan directory path is now normalized, which prevents a bug that would result in blank entries
  • Fixed an issue where the scanning process would continue running even if the Upload Client user was logged out
  • Addressed an issue where certain analysis files stored in a VSI were not uploaded to the Repository when using the Upload Client. This problem did not prevent the images from being viewed

Notes