Skip to main content

Core 7.4.3 Release Notes

Updated over 3 weeks ago

This release introduces smoother handling for expired users, improved search visibility, and enhanced system monitoring to support reliability at scale. It also brings key performance and stability improvements across Core for clients with large libraries and user bases, addressing edge cases in sharing, search, and user management.

Download Updates

  • Improved Download Share Settings
    Asset owners can now view all downloads options when sharing packages, ensuring better transparency and tracking.

  • Consistent Download Settings
    Corrected a bug where certain “source-only” download settings weren’t being respected, ensuring package configurations apply as expected.

  • Complete Zip File Options
    Fixed an issue where the “Download” option was missing from some ZIP files, restoring expected functionality.

Package & Sharing Fixes

  • Expired User Handling
    Expired user accounts are no longer listed as selectable recipients on shares and discussions, reducing confusion when sharing assets and packages.

  • Reliable Comment Display
    Comments and messages now appear consistently in package discussions, restoring normal functionality.

  • Fixed Navigation on Share Forms
    The navigation controls in the Skip & Share hare interface now behave correctly, making it easier to backtrack when working with files and shares.

General Improvements

  • Improved System Monitoring
    Sentry tracking has been updated to monitor user sessions more consistently, improving the accuracy of performance diagnostics.

  • Performance Enhancements to UI Loading
    Users are associated with all facets of assets across Core. When pages, packages, and assets load, so does any associated user data. Core has "lightened" this user load to improve overall UI loading and system performance.

  • Search Results Performance Enhancements
    Search queries now use a lighter option for displaying results, speeding up response times and improving overall usability.

Did this answer your question?